Thanks, that's what I have read. Which is why this make things more awkward.
I cannot see that holding a recipient list is a solution. If, for instance, you relay for thousands of domains all going to different MTA's that hold each individual domains recipient list, its not really that straight forward and may impact performance? On Tue, Sep 15, 2009 at 10:28 AM, Ansgar Wiechers <li...@planetcobalt.net>wrote: > On 2009-09-15 Dan Slay wrote: > > I'm looking for some information on preventing the sending of > > backscatter from a Postfix gateway mail server. > > > > The server itself does not and will not hold a recipient list, > > Then you can't avoid sending backscatter. Period. RFC 2821 clearly > states: > > | If an SMTP server has accepted the task of relaying the mail and > | later finds that the destination is incorrect or that the mail > | cannot be delivered for some other reason, then it MUST construct > | an "undeliverable mail" notification message and send it to the > | originator of the undeliverable mail > > > therefore I don't know what the best way forward would be? > > Maintain a recipient list. > > Regards > Ansgar Wiechers > -- > "Abstractions save us time working, but they don't save us time learning." > --Joel Spolsky >
