David, On Wednesday, March 19, 2003, David Calvarese wrote in <mid:[EMAIL PROTECTED]>:
DC> however, it doesn't scan outgoing emails... FWIW, I think that scanning outgoing e-mail is a complete waste of resources and time. If I take sufficient precautions, the chances are slim that I as a sender would be sending out malicious code inadvertently; when I am the recipient, someone else's statement that their e-mail has been scanned on its way to me is meaningless. How recent were the definition files that were used? How truthful is the statement? Through what intermediate servers did it pass? For what specific types of code did the sender scan? And, more to the point, what do you do differently when you get a supposedly pre-scanned message? It's not like you turn off your own scanner or exclude the message from future scans. For all those reasons and more, I think that outgoing code scanning is meaningful only, and only to a limited degree, if it is performed by a web mail service on a regular basis and, therefore, might justify an exception to an otherwise tight spam filter. I'd be interested in others' comments on this. -- JN ________________________________________________ Current version is 1.62 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
