You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2014/09/15 22:06:19 UTC

[Bug 7082] New: possible loose check in URI_HEX

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7082

            Bug ID: 7082
           Summary: possible loose check in URI_HEX
           Product: Spamassassin
           Version: 3.3.1
          Hardware: PC
                OS: Mac OS X
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Rules
          Assignee: dev@spamassassin.apache.org
          Reporter: apache.org@veggiechinese.net

I have certain emails from some automated reports we send that are flagging
messages that have a line like this in the body for URI_HEX:

96.57.230.174       ool-6039e6ae.static.optonline.net

Sep 15 12:58:39.259 [42617] dbg: rules: ran uri rule URI_HEX ======> got hit:
"http://ool-6039e6ae"

This is easily reproducible (and I see the behavior with 3.4.0 as well).

I realize that it's important to match these encoded URLs, as spammers often
use them, but is it possible to make the check a little tighter?

Also, the debug statement put 'http://' in front of it, even though in this
case, it's not specified as a URI in the actual email message.

May be somewhat related to
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5664

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7082] possible loose check in URI_HEX

Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7082

--- Comment #1 from AXB <ax...@gmail.com> ---
this rule is scored very low

score URI_HEX 2.800 1.313 1.206 1.122

please post a sample message which shows how this can be  a problem

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7082] possible loose check in URI_HEX

Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7082

apache.org@veggiechinese.net <ap...@veggiechinese.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |apache.org@veggiechinese.ne
                   |                            |t

--- Comment #2 from apache.org@veggiechinese.net <ap...@veggiechinese.net> ---
Correct - it's not causing us issues with FPs at this time, and I'm seeing it
as 1.313 on our system, AFAIK, however, it would seem that the check itself may
match things other than a HEX encoded URI. Feel free to close if this is not
something that can be adjusted.

-- 
You are receiving this mail because:
You are the assignee for the bug.