Reinaldo de Carvalho wrote:
2009/8/13 Eduardo Júnior <ihtrau...@gmail.com>:
Right.
For this I wanted more information about debug level of the daemons,
of the cleanup in special, to analyze the actions from my expressions.
With header_checks, some choices are to add it to main.cf and remove
matching headers from all mail, define a separate cleanup service for the
after amavisd smtpd reinjection, or use multiple postfix instances with
different header_checks.
But if you have postfix 2.5 or newer, the easy solution is
http://www.postfix.org/postconf.5.html#smtp_header_checks
which can be added as a -o option to your outgoing smtp transport.
I have two daemons smtp, one to incoming messages, other to outgoing mesages.
So, in master.cf I did that:
-o smtp_header_checks=regexp:/path/header_checks
smtpd (listener) is not smtp (client).
Again, isn't required any aditional configuration than header_checks.
You need a regular expression to match exactly with local amavis server.
You can test with postmap:
postmap -q - regexp:/path/header_checks < /path/to/sample-message
Testing header_checks with postmap may not give the results
you expect unless you either 1) use postfix 2.6 or newer and
use the postmap -h flag, or 2) manually fold multi-line
headers into a single line before testing.
http://www.postfix.org/postmap.1.html
-- Noel Jones
