I noticed that, in some cases, *legit* emails coming from "postmaster" (e.g. some MLs and other services use such an address to send the confirmation request email) are rejected due to "MSGID-sig check failed for bounce sender" now, while ASSP already has the "noBackSctrAddresses" to deal with such issues; it's a royal PITA having to add all those "postmaster" addresses there, not to say that such a thing may (and will) defeat the backscatter filter... now... I kept thinking about this and I came out with an idea, maybe it's stupid, I don't know but...
Let's say ASSP has two additional parameters in the backscatter section, that is IsBackScatter IsNotBackScatter the two fields will allow to enter some regexps (or file names containing regexp) which will work just like the ones used for the HELO checking, that is If a given message is identified as "backscatter" by current filters, it will then be checked against the two regular expressions and, in case it matches the first or doesn't match the second, then it will be rejected as backscatter, otherwise it will be passed on The idea is to allow ASSP to perform a first, quick check on messages and then a second, stricter one only on those which "smell like" backscatter and, at the same time, help avoiding false-positives just due to the fact that a given message comes from the "postmaster" address for a given domain What do you think ? ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
