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 2015/09/16 22:56:02 UTC

[Bug 7248] New: Please fix TO_NO_BRKTS_* misleading description

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7248

            Bug ID: 7248
           Summary: Please fix TO_NO_BRKTS_* misleading description
           Product: Spamassassin
           Version: 3.4.2
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: trivial
          Priority: P2
         Component: Rules
          Assignee: dev@spamassassin.apache.org
          Reporter: grin@grin.hu

There are open tickets debating about scores of those rules so I don't even
want to mention it again.

However it has been pointed out since 2011 that bracketless To: is absolutely
valid RFC-wise. It was shunned by sying "we're not an rfc validator", which is
abvsolutely true, however the rule description (which actually gets included in
reports to admins and users) misleadingly says:

"To: misformatted and ..."

No, it is not misformatted, it is completely valid - just hints spamminess. I
accept. A better description would be

"To: addresses lack brackets and ..."

As a sidenote it seems to be generated by various dipshitâ„¢ tools like phpmailer
and most lusers cannot fix it, so telling them "you better fix your stuff"
won't help since it's not their stuff, and it's php anyway, they cannot code at
all. :-)

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

[Bug 7248] Please fix TO_NO_BRKTS_* misleading description

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

John Hardin <jh...@impsec.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jhardin@impsec.org
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #1 from John Hardin <jh...@impsec.org> ---
Revision 1703478

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