Am 01.08.2016 um 23:36 schrieb sha...@shanew.net:
Others could probably add to that list, but that's just off the top of my head. But, even if a spam source retries and successfully makes it past the greylisting, the greylisting still provides potential benefits, like: - While it was waiting to retry, its IP has been added to BLs, which my other filters will score appropriately - While it was waiting to retry, the phishing URL in it has been reported and taken down (or the URL shortener link it used has been removed) - While it was waiting to retry, the virus it carries has been identified and pushed out to my virus definitions - While it was waiting to retry, its registered domain has been removed - While it was waiting to retry, others who received the spam have reported it to services like Razor and DCC, which other filters will act on
excatly that's the point whe had last month 1212 greylistings a majority was blacklisted later, bet it RBL or URIBLwell, 1212 is not much of the overall mailflow, the reason is just "knowing what you are doing" and have greylisting only as last resort before contentfllters and skip it if the sender matches SPF or is on any known DSNWL
finally that means zero bad impact for regular mailif only *one* phishing mail which would have trapped a user was rejected with *zero* costs on a wise setup it has done it's job
again: the point is not to delay everybody, it's about to delay pure junk senders wihouth touching anything which has a single reputation sign and that goal won't change at any point of time - just becasue of the zero-cost and zero-impact for any regular mailflow
signature.asc
Description: OpenPGP digital signature
