Jan,
> Thanks. That worked. And now indeed the result was 'Blocked BAD-HEADER'
> as i expected it to work. Strange however that yesterday when i received
> an e-mail via the postfix mailinglist (Precedence: bulk), with exactly
> the same config as this test message, the result was 'Passed BAD-HEADER'.
> [...]
> When i add the field 'Precedence: bulk' to this test message the result
> changes again into Passed BAD-HEADER.
>
> Is this expected behaviour? From the documentation i interpreted this
> differently. Thought that the Precedence value only controlled weather
> or not to send the bounce message, not the forwarding part to the
> recipient?
It is intentional. Most people won't notice it because
by default the setting for $final_bad_header_destiny is D_PASS;
As the 'bad header' is mostly a nuisance and does not pose a
serious security risks, the following is a section of amavisd code:
} elsif ($fd == D_BOUNCE && (defined $is_bulk || $sender eq '') &&
ccat_maj($r->contents_category) == CC_BADH) {
# have mercy on bad headers from mailing lists and in DSN: since
# a bounce for such mail will be suppressed, it is probably better
# to just let a mail with bad header pass, it is rather innocent
do_log(1, "allow bad header from %s<%s> -> <%s>: %s",
$is_bulk eq '' ?'' :"($is_bulk) ", $sender,$recip,$bad_headers[0]);
}
Mark
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
