4 ms·
The obvious downside of greylisting is that the first contact takes some minutes. Another downside is that some poorly written applications try to deliver mail
by seven 17y ago
The obvious downside of greylisting is that the first contact takes some minutes.
Another downside is that some poorly written applications try to deliver mail on their own, instead of using a real mailserver.
It is somehow required that the mail user knows about the greylisting setup so that he can request the other application to send the same mail again after some minutes.
One real world example are those registration links you get via mail to confirm your account. It happens very often to me that I have to re-request the mail, to get it into my mailserver.
- merrick33 17y agoGood points. I used to do enterprise IT consulting and we couldn't integrate many spam cutting techniques without getting a large dose of complaints saying "where is my spam". In our case, it's just two of us, and the level of spam was overwhelming. I accept the trade-off.
- jrockway 17y agoHeh, I always assume I've broken my mailserver when I don't get any spam. Unfortunately, I am usually right.
- pkulak 17y agoI don't think many (if any) web services work that way. I know that at my company we set up a Postfix daemon on one of our servers which all of our web servers connect to to send mail. So, when you get your password emailed to you, it's Postfix doing the actual sending, and Postfix will retry for hours, let alone 5 minutes. Same thing for all my personal projects.
- jrockway 17y agoOne real world example are those registration links you get via mail to confirm your account. It happens very often to me that I have to re-request the mail, to get it into my mailserver. 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.
- merrick33 17y agoThe Gmail issue you highlight I believe would only happen when the original outbound smtp server goes dark before it reattempts delivery. I say this because I have been receiving emails from Gmail with greylisting on for a week now.
- jrockway 17y agoLook at the logs and you will notice a lot of initial attempts that are never "followed through" on, and these are from Google's IPs. And BTW, spammers have figured out RFC822 now, so this doesn't even prevent a lot of spam.
- seven 17y agoI was talking about registration mails from 'poorly written' applications. Mail comes after one hour. I am cool. 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. :)
- seven 17y agoAaahh.. google is inside my whitelist. :) That explains it. btw: anybody needs to see a list of 'no-retry' servers, check out: /etc/postgrey/whitelist_clients
- jrockway 17y agoThe issue there being that if Google ever changes their internal network structure, you lose mail until someone notices. Personally, I don't like coupling myself to other networks that tightly, and I also don't like losing email. So no greylisting for me.
- FlorinAndrei 17y agoSpam from @gmail.com is increasing nowadays, AFAICT.
- 17y ago