On 2015-01-18 23:51, wie...@porcupine.org wrote:
m...@ruggedinbox.com:
and the header is still there.
By default, Postfix REMOVES Return-Path headers from email messages.
The default setting is:
message_drop_headers = bcc, content-length, resent-bcc, return-path
You claim that you removed all the pipe "R" flags. You can verify
that by temporarily configuring the pipe daemon to deliver the mail
to the command
/usr/bin/logger -p mail.info
Then you can see all the headers and content in the maillog file.
The discussion has focused on the pipe with the content filter, but
there are other places where the header may be added.
If there are other places in the mail flow that invoke a pipe daemon,
you also need to temporarily configuring the pipe daemon to deliver
the mail to the command
/usr/bin/logger -p mail.info
Again, convince yourself that Return-Path is absent.
Wietse
We tried to use the 'message_drop_headers' parameter in both main.cf and
master.cf (under the 'cleanup' line) but always get the error:
[....] Reloading Postfix configuration.../usr/sbin/postconf: warning:
/etc/postfix/master.cf: unused parameter:
message_drop_headers=bcc,content-length,resent-bcc,return-path
can we have a working example of how to use it ?
Also, at the end of the main.cf file, we have:
mime_header_checks = pcre:/etc/postfix/header_checks
smtp_header_checks = pcre:/etc/postfix/header_checks
and in the 'header_checks' file we have a number of regexp to strip
headers, for example:
/^\s*X-Mailer/ IGNORE
/^\s*X-Originating-IP/ IGNORE
maybe this conflicts with the default parameters of
'message_drop_headers' ?
Anyway we tried to add 'Return-Path' to the 'header_checks' file but the
header is still there.
Finally we tried to comment the line in main.cf which calls our custom
script
and the return-path is correct:
Return-Path: <m...@ruggedinbox.com>
so it looks like the problem is around the script or its invocation.
Thank you.
