Wietse wrote:
> However, message_strip_characters has no effect when mail is received with
>
> receive_override_options = no_header_body_checks ...
>
> This is set either in master.cf or main.cf.
And indeed, I have no_header_body_checks specified in my master.cf file --
for "smtp", and also for port 10025 (reinjection of mail after scanning by
AMaViS).
I understand (from the postconf.5 page) that no_header_body_checks is
"typically specified AFTER an external content filter" -- so I'm guessing
it does need to stay in the configuration for port 10025.
I'm not really sure at this point why I have no_header_body_checks as part
of my "smtp" configuration in master.cf. Is this appropriate? Or should
I remove it? Aside from this null-stripping issue, what (if any) changes
in behaviour should I expect to see if I do remove no_header_body_checks
from "smtp"?
I'm including a copy (see below) of the "smtp" configuration stanza from
my master.cf file.
Rich Wales
ri...@richw.org
==========================================================================
smtp inet n - n - - smtpd
-o smtpd_client_restrictions=
-o smtpd_helo_restrictions=
-o
smtpd_recipient_restrictions=check_client_access,hash:/etc/postfix/smtp_access,check_client_access,cidr:/etc/postfix/block_spam_ipaddrs,permit_mynetworks,sleep,1,reject_unauth_pipelining,reject_invalid_helo_hostname,reject_unauth_destination,reject_unlisted_recipient,reject_rbl_client,zen.spamhaus.org
-o smtpd_delay_reject=yes
-o receive_override_options=no_header_body_checks
==========================================================================
