List Mail User wrote on Mon, 12 Dec 2005 16:29:05 -0800 (PST): > I "trust" all the RFCI lists,
I don't ;-) I fear that may have too many FPs. But I haven't tried them. I also look at the cost:benefit ratio and I don't feel that they would add much extra benefit for the extra cost of querying them as well. I tested quite a few RBLs for "effectivity" and found out that SBL+XBL already catches most of the unwanted mail. All other RBLs only add marginal extra rejections. The most of them are done by SORBS, that's why I use it as well. I also use NJABL, but that's just historical, it doesn't add much and I'm probably going to skip it with the rollout of the next .mc file. but was > blasted (Hi Matt) for using "postmaster" at the MTA level (and don't any > more). The issue is not all lists are intended to be "spam" lists, even > though they may have a high correlation with spam content. Indeed. And I'm sure > that I'm still stricter than > 95% of the people on this list (though you've > mentioned local rules that would cause me problems, with my own domain and > others - e.g. a single '.' FQDN rule for HELO/EHLO - my case is a "corner" > case at best, but look at ibm.com, sgi.com and microsoft.com - who all do > or have sent mail with the domain as the HELO/EHLO argument, I haven't gotten any mail from mailers for these domains that heloed like this, at least not that I know of. > Also, for anyone who does have access to the MAPS lists, along with > the RCVD_* (or MTA level) rules, also consider using a DSN_FROM_* rule for > the "RBL" (that is the only one for which it is likely appropriate). Also > a URI_* rule on the "RBL" may be helpful: Neither of these additional rules > is easily done at the MTA level. URI is a completely different kind of beast and I always encourage using them. It's content-based rule, that's why it is best placed after MTA. > > I do generally agree about the RCVD_IN_* rules *usually* being both > cheaper and more effective to use at the MTA level (but not all sites can > afford even low FP rates I can, and I guess that you can also). Still, there > will always be some exceptions that the administrator may have to work around. Again, agreed. That's what whitelisting is for, you can also whitelist at MTA level. That's for all the broken configurations out there. Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com
