| |||||||||||||||||||||||||||||||
|
> Gang, > > It's probably easier to give some background first, then ask my > question. > > We're sending messages through a postfix system with the > 'sendmail -Nsuccess,failure -f<someuser>' command from some automated > scripts. DSNs are processed by another script by way of a pipe from > /etc/aliases, e.g: > > <someuser>: "|/path/to/script" > > > What I'm looking for, is a way to keep the DSN on the queue if > the script fails for whatever reason. Is there a exit/return code that > the script can spit back that will keep the message on-queue and retry > the DSN delivery after a time period? Right now if the script isn't > executable, or has some sort of error, the DSN message is lost. Test outside the production system, then deploy, but if you really must: master.cf: # Non-bounce clone of local transport. nblocal unix - n n - - local -o soft_bounce=yes transport: # This address should not bounce someuser nblocal:localhost main.cf: transport_maps = hash:/etc/postfix/transport -- 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:majordomo?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.
| ||||||||||||||||||||||||||||||
© 2004-2008 readlist.com