SMTP store and forward requires DSN for integrity

Sun Dec 11 11:28:21 UTC 2005

On 12/11/05, Micheal Patterson <micheal at tsgincorporated.com> wrote:
> If malware detection systems would not generate a DSN to the originator
> upon detection in the first place, there would be no need to reduce
> those transactions as there would be no transactions to reduce. The

That is a big if.

No shortage of broken software / appliance etc products put out by
different vendors

Even if they do introduce patches for current versions or release new
versions that dont backscatter to spoofing viruses, there's a huge
installed base of crap old versions of this stuff.

So, fixing that lot is not going to be easy.

Sending BATV signed email out and accepting bounces to BATV'd
addresses does tend to make sense in a limited set of use cases (IF
you send email only from a single server / set of servers, and control
the sending client . geeks with pine on *bsd or webmail service
providers, or mailing list services that anyway do VERP)

Upgrade MTAs around the world?  Which MTAs around the world receive
bounces bound for your domain, and to your servers?  And which MTAs
send legitimately send out email with your domain?  If you are SURE
that all that is covered, try BATV and it will work rather well for
you.  If you aren't - dont bother about it.

--
Suresh Ramasubramanian (ops.lists at gmail.com)