KLaM Postmaster a écrit :
> I am having a problem with some legitimate emails being rejected by
> header and/or body checks. Both the header and body checks are from
> Jeffrey Posluns' write up,without any mods.
> Among the stuff being rejected is the output of pflogsumm, I run a daily
> a report and email it to postmaster. I was not getting the reports so I
> checked the maillog and found that these messages, among others, were
> being rejected with "Your email is not using a proper character set.
> ...". 


if header/body checks reject legitimate mail, then something is wrong.

> In the case of pflogsumm, and some of the other automatic email, I
> really don't have much say in its internal format.
> 
> 1) As I try to control spam by using amavisd, spamassassin, clamv,
> postgrey and so far seem doing OK (touch wood), are header and/or body
> check worthwhile as an anti-spam measures. Could they be dropped.
> 

header and body checks can be used to reject some spam (forged received
headers, "banned" attachment types, ...), but not as a general content
filter.

> 2) If they are worthwhile, is there a way of not applying them to all 
> mail except that destined for postmaster.

you can't. but they can be skipped for mail submitted via the sendmail
command. for that, define a specific cleanup and use it in pickup (in
master.cf).

but this is not a good idea. The fact that these checks are catching
your legitimate mail is an indication that they could reject legitimate
mail from others and to other users.

> If I understood the
> documentation it would seem that  these checks are applied by "cleanup"
> after the other checks have been completed and are not susceptible to
> access checks. If this is the case, is there some other way of making
> them conditional on recipient, something like an access list to these
> checks.
> 
> =============
> 
> As I administer a very small number of virtual users I put the attached
> script together to help me. Any thoughts, ways of doing the same thing
> only better etc.
> 
> TIA
> JLA
> 
> 

Reply via email to