I hadn't thought of that! That sounds like a bug to me then.. surely my company isn't the only one that has the letters opt in their name?!
Actualy the "OPT_HEADER" rule isn't just looking for "opt" in the domain name. It's looking for things like opt, followed (optionally) by any single character, followed by in, out, oem, ed, ion-in, @, or a number, followed by a word boundary, another number, or an @.
Specificaly, the 2.60 regex is:
header __OPT_HEADER_ALL ALL =~ /opt.?(?:in|out|oem|ed|ion-in|[EMAIL PROTECTED])(?:\b|\d|\@)/i
Is there a process I should go through to report this?
There is a bugzilla system for such things. Check out the "bugs" page of the SA webpage, and you can generate a bug report for it. Be sure to mention the rule that is misfiring by name. Something like "OPT_HEADER causing false positives".
If you want to make the SA-devs really happy, make a quick email that demonstrates the issue so they can test against it, and attach it to the bug, but please don't copy-paste it into the bug report. (Note: you attach files after you create the bug, you won't be able to add the attachment on the first form, don't worry.)
as far as bugfixes go my suggestion to the SA-devel team would be to try to modify the regex slightly, to look for a non-word character after the "opt" string, instead of any character. Allowing alpha characters in there is too ambiguous imo.
/opt\W?(?:in|out|oem|ed|ion-in|[EMAIL PROTECTED])(?:\b|\d|\@)/i
Of course, someone with a decent spam corpus would have to run a quick test and see if that change had a significant impact on the spam hitrate.
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
