I recently switched to policyd from tumgreyspf hoping I'd find a solution to one of the more annoying challenges of greylisting in general. Policyd doesn't yet support what I'm hoping to find, but maybe someone knows of a clever solution to a problem we all face.
Scenario: you send a message to someone at a domain that has never contacted you in the past, and no grey/whitelist entry exists for them on your mail server. They receive your message quickly, reply immediately, but despite being from someone with whom you know you want to communicate, their message is relegated to going through the normal greylisting process. Generally this doesn't add significant delay, but sometimes it does, and sometimes even a reasonably short delay is more than it should be. I'd love to see a solution where recipients of outbound messages could have some combination of the server(s) MX'd for their domain - or in policyd fashion, a configurable number of quads of that/those server's IP addresses - automatically greylisted/whitelisted? Maybe you go simple and only use the address of the server that actually receives the message as the basis for auto(g/w)listing, or maybe you expand all available MX or A records for the RHS of the address. Has anyone played with this idea? Thanks. -- Eric A. Litman +1-703-852-0582 (voice, fax) http://www.litman.org/ AIM: EricAustinLitman | Skype: EricLitman ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
