http://www.policyd.org/tiki-index.php?page=Greylisting&s...
I still had the same problems others have mentioned though, where crappy registration systems were sending their confirmation mails directly from their PHP application, rather than relaying it through a smart MTA that actually understood the SMTP protocol and would do the retry.
Ultimately, too many users complained about mail delays and missing email. This is one of those scenarios where the cost of not delivering an important email may outweigh the benefits of blocking a few more invalid ones.
I am aware that most prominent site do this the right way, but just wanted to mention that some do not.
About the problem with gmail, I was not aware of that. Thanks for the info. I will go grep my logs now. :)
btw: anybody needs to see a list of 'no-retry' servers, check out:
/etc/postgrey/whitelist_clients
So no greylisting for me.
And BTW, spammers have figured out RFC822 now, so this doesn't even prevent a lot of spam.
Oh, you'll get those in an hour or so, when their mailer retires. I have never had a problem.
I did kill greylisting, though, because it breaks when the mail server that first tried to send the message is not the one that tries to send it again. Gmail does this, for example, and unless you keep up to date on Google's internal architecture, you are going to lose mail from Gmail users. Combined with being tired of waiting an hour or more for every email, this killed greylisting for me. Now I let the spammers deal with spamassassin, which is quite nice if you bump up the scores on the content and URI blacklists.