Prev: avoid bouncing of rejected messages [secondary MX, spam filters on primaries]
Next: Does anyone have an example of how to make LUSER_RELAY and preserve_luser_host work?
From: Andrzej Adam Filip on 12 Feb 2010 09:59 Xavier Roche <xroche(a)free.fr.NOSPAM.invalid> wrote: > Dietmar Rieder wrote: >> At the MX, we are using several anti-Spam techniques that reject >> messages based on different rules and Spam that passes that rules gets >> tagged but we (legally) have to forward it to the downstream servers. > > Why ? If you reject the spam during the SMTP transaction, you refuse to > take the responsibility of the delivery. It is up to the sender to > ensure that the original sender knows that his message was not delivered. > > You do not "delete" nor "bounce" the message in this situation: you just > do not want to take it. This clears any responsibility, including risks > of bounding a message to an innocent recipient whose email address was > forged. > >> But, unfortunately some of our downstream server use Spam-fighting tools >> to reject spammy messages, which in turn leads to a bounce generation at >> our MX. > > You choose to get the "hot potato", and you are screwed. Do not take it. Dietmar: Does your secondary MX acts merely as delivery backup? Can your make it e.g. *when* primary is available can you use greylisting or generate 4?? replies? -- [pl>en Andrew] Andrzej Adam Filip : anfi(a)onet.eu : Andrzej.Filip(a)gmail.com Open-Sendmail: http://open-sendmail.sourceforge.net/ Flattery is like cologne -- to be smelled, but not swallowed. -- Josh Billings |