John, I have no clue what the "legal implications" would be, as long as both my customers know that I'm using it and the sender is notified appropriately via SMTP. I use greylisting via IMGate/Postfix and it works like a charm. It takes a good couple of weeks to build up decent whitelist (both manual whitelisting and automated whitelisting are recommended), but after that it is pretty much smooth sailing. I've yet to have a single complaint from my users over greylisting, other than the fact that it delayed their e-mails by around 5 minutes for the first couple of weeks. If I had planned it better, even those delays would largely not have occurred.
I know of no way to implement greylisting on a Windows box. See greylisting.org for more info. William Van Hefner Network Administrator Vantek Communications, Inc. 555 H Street, Ste. C Eureka, CA 95501 707.476.0833 ph > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of John T (Lists) > Sent: Friday, October 14, 2005 12:55 PM > To: [email protected] > Subject: RE: [sniffer] Large amounts of spam still getting through > > > There has been a good amount of discussion about temporarily > "grey listing" an e-mail message and there are many questions > surrounding it, one of which is legal. > > John T > eServices For You > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] > On > > Behalf Of Mike Nice > > Sent: Friday, October 14, 2005 12:43 PM > > To: [email protected] > > Subject: Re: [sniffer] Large amounts of spam still getting through > > > > > getting much better at what they do. When a spammer uses > Geocities > links, > > > hijacks real accounts on major providers to send spam through, and > changes > > > their techniques every few hours, it makes it difficult > for Sniffer > > > to proactively block them, and the delay between rulebase updates > > > means a delay in catching things that have been tagged. > > > > This brings to mind a technique with optional adaptive delay - > > enabled > by > > the user. Each mail is assigned a 'triplicate': (To_Email, > From_Email, > > and domain_of_sending_server). Previously unknown triplicates are > > held for a period of time before being examined for spam. > The delay > > is long enough that SpamCop, Sniffer, and InvURIBL mailtraps see > > copies of the spam and update the blacklists. > > > > This would be hard to do with the stock IMail, but > possibly could > > be > done > > by Declude with the V3 architecture and a database. > > > > It still doesn't provide a good answer to the problem of > spammers > > hijacking a computer and sending spam through legitimate servers. > > > > > > This E-Mail came from the Message Sniffer mailing list. For > > information > and > > (un)subscription instructions go to > > http://www.sortmonster.com/MessageSniffer/Help/Help.html > > > This E-Mail came from the Message Sniffer mailing list. For > information and (un)subscription instructions go to > http://www.sortmonster.com/MessageSniffer/Help/Help.html > This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
