Re: SMTP store and forward requires DSN for integrity (was Re:Clueless anti-virus )

["Edward B. Dreger" <eddy+public+spam () noc everquick net>]

DO> Date: Fri, 9 Dec 2005 15:08:49 -0800
DO> From: Douglas Otis

DO> This is a third-party acting in good faith, albeit performing a check better
DO> done within the session.  In your view, there is less concern about delivery
DO> integrity, and so related DSNs should be tossed.  Being done within the
DO> session would be ideal, of course.  When their architecture does not support

Let's use some hyperbole:

Say that the latest megaworm chucks out spam at speeds resembling SQL 
Slammer.  The return-path specified is your email address.  Millions of 
MXes send _you_ bogus DSNs "in good faith".

Is this acceptable?  If not, where do you draw the line -- and does that 
line apply to others, too?


Eddy
--
Everquick Internet - http://www.everquick.net/
A division of Brotsman & Dreger, Inc. - http://www.brotsman.com/
Bandwidth, consulting, e-commerce, hosting, and network building
Phone: +1 785 865 5885 Lawrence and [inter]national
Phone: +1 316 794 8922 Wichita
________________________________________________________________________
DO NOT send mail to the following addresses:
davidc () brics com -*- jfconmaapaq () intc net -*- sam () everquick net
Sending mail to spambait addresses is a great way to get blocked.
Ditto for broken OOO autoresponders and foolish AV software backscatter.