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...@spamassassin.apache.org on 2024/07/06 06:23:26 UTC

[Bug 8266] New: Whitelisted host fails GTUBE test

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

            Bug ID: 8266
           Summary: Whitelisted host fails GTUBE test
           Product: Spamassassin
           Version: unspecified
          Hardware: PC
                OS: Mac OS X
            Status: NEW
          Severity: normal
          Priority: P2
         Component: spamc/spamd
          Assignee: dev@spamassassin.apache.org
          Reporter: monochromec@gmail.com
  Target Milestone: Undefined

When processing a mail with a GTUBE string
("XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL*C.34X") SA
fails to recognise a whitelisted host, ie. the score of the flagged mail is 999
regardless of the host being whitelisted. 

Is this intended behaviour?

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

[Bug 8266] Whitelisted host fails GTUBE test

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

Bill Cole <bi...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |billcole@apache.org
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from Bill Cole <bi...@apache.org> ---
This behavior is normal. GTUBE is designed to be an absolute override that
*always* triggers the 'spam' detection of a filter. The default configuration
of SpamAssassin assures that if a message contains GTUBE it will be considered
spam. It is supposed to be a test of fundamental functionality: if SA does not
mark GTUBE as spam, it's broken.

You can locally override the scores, priorities, and shortcircuiting parameters
of the relevant rules as you like to change this, e.g. if you want domain-wise
welcomelist/whitelisting to override everything else, you can give the relevant
rules implementing the list high negative scores, high priority, and make them
shortcircuit.  If you want to discuss how to do that in more depth, please use
the SpamAssassin Users mailing list. Obviously you should not include the
literal GTUBE string in email that you wish to be delivered. (Ever.) 

If you have some need to absolutely exempt some source of mail from
SpamAssassin even in the face of GTUBE mail, you should probably just use
whatever tools your MTA provides to simply bypass SA for that source. SA is a
waste of effort for mail that you can be sure that you want.

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

[Bug 8266] Whitelisted host fails GTUBE test

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

monochromec@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |monochromec@gmail.com

--- Comment #1 from monochromec@gmail.com ---
SA version is 4.0.0-6 running on Bookworm.

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