On Saturday, Nov 8, 2003, at 01:41 US/Eastern, Jaana Jarve wrote:
you can ask for advice, but don't take it blindly. in using any blocklist, you're handing the decision of who can send you mail off to someone elses hands. read every blocklist's homepage you are considering using. read all documentation. decide for yourself if their policies suit you and if youtrust them.
Great advice there.I've got a set of pages describing my experience with DNSBLs and SpamAssassin (mostly positive) on our Qube3 at <http://bluebird.sinauer.com/~morse/cobalt/>. It includes step-by-step instructions for adding DNSBLs to the sendmail.mc (and regenerating the sendmail.cf), and a walk-through on adding SpamAssassin. We use The Sanitizer to scan for email viruses etc., it has been very good for us and I describe its setup as well.
Do look through the mailscanner route as well; the way I've done it has worked for us so far, but it's definitely not the only way.
Keep a close eye on your incoming mail for the first few days after you set up each new list. It might help to customize the error messages so you can tell which list rejected each connection, in the event you reject mail you wanted. We include a link to a page explaining our email policy, along with links to the DNSBLs we use in order to allow the sender to check the lists for their host.
pjm
Attachment:
PGP.sig
Description: This is a digitally signed message part