On 12/13/19 9:02 PM, Mark Sapiro wrote:
As postgrey learns, it will remember triplets (sender, sending IP, recipient) and not delay them and in addition will whitelist domains that retry successfully more than a few times.
The bigger senders are doing things now (more than ever) that they weren't doing 15+ years ago. Now farms of servers will try to contact you. The message may first try from one IP, then from another IP, then from a 3rd.... It may eventually try from the same IP and make it through.
I think most grey list solutions have an option to specify the network (frequently configured a a /24) for the sending IP. This significantly helps with different servers in the same server farm trying to resend messages.
Another option that doesn't have this (state based) limitation is nolisting. (TCP RST from first MX and subsequent MX(s) accept email.)
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
