Just for the record, I agree with everything Sam says here. (Not that it matters much ;) )
Sam Clippinger wrote: > spamdyke has no flaws, I thought everyone knew that. :) Perhaps I > should update the FAQ. > > To answer your questions: > > Once enabled, spamdyke's graylist filter will block anything that isn't > explicitly whitelisted, including newsletters, mailing lists, etc. Some > mailing lists (depending on the mailing list software) use "tagged > senders", which means that every message appears to come from a > different sender. This is done so that bounced messages can be more > easily matched with a specific mailing list and recipient. (Ezmlm and > Yahoo lists both use tagged senders. Mailman does not. I'm not sure > about Listserv and Majordomo.) For those kinds of lists, every message > is graylisted. This isn't really a problem however, as the remote > server will simply retry delivery and the message will be received. The > QMT list uses tagged senders and I receive its messages just fine. Some > users may complain about the (small) delay, however. I'll probably > incorporate some heuristics in a future version of spamdyke to allow > mailing lists with tagged senders to bypass graylisting (but it may be a > while before that's done). > > Online ticket orders, receipts, password verifications and other > automated messages should pass the graylist filter as long as they are > being sent from a real mail server. In other words, as long as the > remote server attempts to redeliver the message, it will be received. > > Graylisting works fine with all of the major email hosts and every mail > server I've ever encountered. > > An SSL certificate is only needed for using TLS (an encryption protocol > that allows email to be sent securely). Only one certificate can be > installed on a server (one per domain is not possible) but you don't > have to pay for it -- a self-signed certificate works just fine. > > The sender and recipient blacklists are just text files, so editing them > is very easy. The graylist system uses a directory structure that > contains files named after the senders and recipients. It's not as easy > to edit manually (nor is it difficult) but you shouldn't ever need to. > > spamdyke has no mechanism for saving rejected messages. It works by > rejecting the message before the remote server even sends it, so > spamdyke never sees its content. For that reason, it is not possible to > recover rejected messages. However, spamdyke does log the sender and > recipient addresses for every message (accepted or rejected), along with > the reason the message was rejected. This does make it possible to > determine if a delivery was attempted and why it failed. > > Obviously, I've been using spamdyke for years now with no problems. > spamdyke has an active mailing list (subscribe at www.spamdyke.org) with > many helpful and responsive people. You should probably pose these > questions there to see what they have to say. > > -- Sam Clippinger > > Kent Busbee wrote: >> I've heard so many good things about spamdyke, I am wondering what flaws >> it might have. From my understanding greylisting is the key to its >> success. >> >> -Will it block wanted newsletters, email lists, email subscriptions? Or >> will it greylist the first attempt and then deliver the next a day, week, >> or month later. >> >> -Will it unintentionally prevent things like online tickets orders, >> receipts from online orders, password verifications, etc. >> >> -Does it work well with the major online email systems accepting emails >> from gmail, yahoo, hotmail, etc. >> >> -Do you need an Certificate SSL for your site? For each site hosted? >> >> -Is it easy to tweek the lists? Move an address/domain from greylist to >> whitelist or blacklist? >> >> -If a message is lost/rejected/greylisted, is it possible to pull it back >> and deliver it? >> >> -What other problems/unexpected results did you get from installing? >> -- -Eric 'shubes' --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]