Hi Wrolf,
I don't suppose you could share the code you have used to do this. It sounds very similar to something I have tried to do, and for the same reasons, the DNSBL lists are sometimes too aggressive. My perl is pretty weak, and although I'm managing to add domains, like you to the access.db file, I feel I could go about it in a better way.
Cheers,
Richard
For a long time now (before implementing MIMEDefang) I have implemented site-wide whitelisting of the to address of any outbound e-mail.
It is reasonable to assume that if one of my users sends someone mail, then they want a reply.
Since my users are a community of interest (corporation), it is also quite likely that someone else here would want e-mails from that person.
I implemented this using the access.db feature of Sendmail, with scripts every five minutes scanning the logs and adding new entries. It really got around the problem of overly aggressive DNSBLs - I used to get into explaining what a DNSBL (RBL) is to administrators at our customers and suppliers, had to manually whitelist their server, etc.
Users very rarely call me over this now, since if they fail to get an initial e -mail sent to them from a customer, they first try sending one out. This is a good strategy anyway (customer may have typoed their address, etc.)
I would love to see this integrated into MIMEDefang.
Wrolf
_______________________________________________ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
-- Richard Whelan Senior Systems Administrator PIPEX
Direct: +44 (0) 1865 381568 Mobile: +44 (0) 7786 276020
website: http://www.pipex.net/
This e-mail is subject to: http://www.pipex.net/disclaimer.html
_______________________________________________ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
