Hi all; I was thinking about the main "issue" with graylisting, that is, the fact that if a given sender retries sending messages to an ASSP box using different IP at each attempt, the delaying mechanism may cause the message to be "rejected" after a given number of attempts
Now, ASSP already deals with this by using the "noDelay" list which allows to specify IPs which should never be delayed; the "problem" is that, those IP owner may from time to time change their sending IP pool and this means trying to keep the "noDelay" list as up to date as possible; also, in some cases it's difficult to know which IPs may belong to a given "problem" sender and then btw, the delay will always kick in for whatever "unknown" IP even if it belongs to a "good" sender or in any case to a perfectly legit mailserver My idea is the following; we already have "three" caches which build-up while ASSP is running, that is "MX", "A" and "SenderBase"; now, when an IP connects to our box, ASSP may perform a cache ONLY lookup to see if the IP is a valid mailserver (MX/A) or belongs to an organization we trust (SenderBase) and, in such a case the delaying will be skipped (same goes in case the sender passes the SPF check) I think that, while the above won't impact on processing time (the lookup is only performed on local caches so it's almost immediate) it will help avoiding issues due to hosts which "don't like" the delaying mechanism ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
