https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7354
--- Comment #5 from Steadramon <[email protected]> --- (In reply to Kevin A. McGrail from comment #4) > How would this change help you? What is the goal? What's a rule(s) that > uses it? Hi, I find this extra function quite handy when adding rules which match headers or body uris, quite a bit easier to set up and cleaner looking that a regex expression. I have reffered to this BZ a few times on the mailing list: http://spamassassin.1065346.n5.nabble.com/Blacklist-for-reply-to-td150498.html http://spamassassin.1065346.n5.nabble.com/Ends-with-string-td139774.html http://spamassassin.1065346.n5.nabble.com/top-and-other-spammy-TLDs-td124063.html I have mostly used this to have a list of suspicious TLDs example in first commit shows : enlist_addrlist (SUSTLDS) *@*.top enlist_addrlist (SUSTLDS) *@*.download enlist_addrlist (SUSTLDS) *@*.science header __FROM_SUS_TLD eval:check_from_in_list('SUSTLDS') In KAM.cf we have a similar rule: header __KAM_SOMETLD_ARE_BAD_TLD_FROM From:addr =~ /\.(pw|stream|trade|bid|press|top|date)$/i --- When this comes to matching more complex patterns in an email address I've seen people on the mailing list with long regexes where a more simple enlist_addrlist could be used, an example I have seen, but can't find at the moment is where someone was wanting to match their own domains, with several TLD variants... enlist_addrlist (MYDOMAIN) *@example.com enlist_addrlist (MYDOMAIN) *@example.org enlist_addrlist (MYDOMAIN) *@example.co.uk header __FROM_MYDOMAIN eval:check_from_in_list('MYDOMAIN') header __REPLYTO_MYDOMAIN eval:check_replyto_in_list('MYDOMAIN') --- I don't think it totally replaces From:addr regex but I do think adds a completeness to the WLBLEvals eval ruleset and add an easily understandable, readable set of features for SA. -- You are receiving this mail because: You are the assignee for the bug.
