On 12/30/2010 08:56 PM, [email protected] wrote:
Hi
It's broken because it demonstrably fails, by it's very design, to work
reliably in a very real and valid scenario.
"very real" - for spammers and misconfigured setups.
gmail is a misconfigured setup and/or a major spam source? News to me.
"valid scenario" - really?
Very.
quote from http://tools.ietf.org/html/rfc5321#section-4.5.4.1 :
"
A client SHOULD keep a list of hosts it cannot reach and
corresponding connection timeouts, rather than just retrying queued
mail items.
"
Sure. And when it eventually retries the IP it does so from may not be
the same one it tried from previously. Nowhere in the RFC does it say
that the sender must re-try from the same IP. If the IP is different,
this will fall foul of greylisting. The quote you pasted is in no way
relevant, it doesn't talk about the same case I was talking about.
It seems to me that you are erroneously (solipsistically?) concluding
that a problem doesn't exist just because you haven't noticed it. I can
only conclude that the reason for your not having noticed is either lack
of vigilance or the system you are dealing with is sufficiently small
that you were statistically lucky and haven't seen it yet (or
disregarded it as a glitch). Try with a user-count in the
100,000-500,000 range and this sort of thing starts to come up all over
the place.
If you think I'm making this up, google "greylisting gmail" and you'll
see that a lot of mail admins have bumped into this problem with
greylisting.
Gordan
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
