Re: Forwarded bounce messages coming from MAILER-DAEMON
David Jonas wrote: When a bounce message from is going to an address that is in virtual_alias_maps the sender gets rewritten to MAILER-DAEMON, or at least that is what seems to happen. Some mail servers reject MAILER-DAEMON as a sender due to the lack of domain (att.net, comcast.net). You'll need to show evidence so everyone knows what you're referring to. How can I control this? What is the proper thing to do in this case? Show logging demonstrating the problem, and postconf -n output. I can't seem to figure this out. I tried setting empty_address_recipient = mailer-dae...@$myhostname, but that had no noticeable effect. ... as expected. http://www.postfix.org/postconf.5.html#empty_address_recipient -- Noel Jones
Re: Forwarded bounce messages coming from MAILER-DAEMON
On Thu, Apr 23, 2009 at 05:15:52PM -0700, David Jonas wrote:
When a bounce message from is going to an address that is in
virtual_alias_maps the sender gets rewritten to MAILER-DAEMON, or at
least that is what seems to happen. Some mail servers reject MAILER-DAEMON
as a sender due to the lack of domain (att.net, comcast.net). How can I
control this? What is the proper thing to do in this case?
The pipe(8) daemon by default passes MAILER-DAEMON as ${sender} in place
of the empty address. If your argv setting is robust, you can ask it
to not do that. Usually, pipe(8) leads to final delivery and the envelope
sender is not significant. If you are using pipe(8) content filters, set
it up to not break the envelope.
Also Postfix does not send unqualified addresses to remote servers unless
you turn off append_at_myorigin, which you should never do.
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
mailto:majord...@postfix.org?body=unsubscribe%20postfix-users
If my response solves your problem, the best way to thank me is to not
send an it worked, thanks follow-up. If you must respond, please put
It worked, thanks in the Subject so I can delete these quickly.
Re: Forwarded bounce messages coming from MAILER-DAEMON
David Jonas:
When a bounce message from is going to an address that is in
virtual_alias_maps the sender gets rewritten to MAILER-DAEMON, or at
least that is what seems to happen. Some mail servers reject
MAILER-DAEMON as a sender due to the lack of domain (att.net,
comcast.net). How can I control this? What is the proper thing to do in
this case?
If you use the simple content filter approach as described in
http://www.postfix.org/FILTER_README.html with Postfix 2.3 and
later, use:
/etc/postfix/master.cf:
filterunix - n n - 10 pipe
null_sender=
flags=Rq user=filter argv=/path/to/script -f ${sender} -- ${recipient}
This prevents the null sender from being replaced.
Wietse
Re: Forwarded bounce messages coming from MAILER-DAEMON
Victor Duchovni:
On Thu, Apr 23, 2009 at 05:15:52PM -0700, David Jonas wrote:
When a bounce message from is going to an address that is in
virtual_alias_maps the sender gets rewritten to MAILER-DAEMON, or at
least that is what seems to happen. Some mail servers reject MAILER-DAEMON
as a sender due to the lack of domain (att.net, comcast.net). How can I
control this? What is the proper thing to do in this case?
The pipe(8) daemon by default passes MAILER-DAEMON as ${sender} in place
of the empty address. If your argv setting is robust, you can ask it
to not do that. Usually, pipe(8) leads to final delivery and the envelope
sender is not significant. If you are using pipe(8) content filters, set
it up to not break the envelope.
Also Postfix does not send unqualified addresses to remote servers unless
you turn off append_at_myorigin, which you should never do.
As of Postfix 2.3, filtered mail is re-injected with sendmail -G
to prevent signature damage due to address rewriting. Thus,
MAILER-DAEMON is no longer qualified as it used to be.
I'll update the FILTER_README document.
Wietse
