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 2020/04/18 23:00:36 UTC

[Bug 7809] New: unwhitelist broken

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

            Bug ID: 7809
           Summary: unwhitelist broken
           Product: Spamassassin
           Version: 3.4.2
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: spamassassin
          Assignee: dev@spamassassin.apache.org
          Reporter: stephen-spamassassin@digitalnexus.org
  Target Milestone: Undefined

Attempting to undo a "def_whitelist_auth" by using "unwhitelist_auth" has no
effect.


/var/lib/spamassassin/3.004002/updates_spamassassin_org/60_whitelist_auth.cf:
def_whitelist_auth *@*.getresponse-mail.com

/etc/spamassassin/whitelist.cf
unwhitelist_auth *@*.getresponse-mail.com


E-mail test using "spamassassin -D -t" produces:

-7.5 USER_IN_DEF_SPF_WL     From: address is in the default SPF
                            white-list

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

[Bug 7809] unwhitelist broken

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

Henrik Krohns <ap...@hege.li> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |apache@hege.li
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Henrik Krohns <ap...@hege.li> ---

- unwhitelist_auth now also removes def_whitelist_auth entries

- SPF: add unwhitelist_from_spf to remove both whitelist_from_spf and
  def_whitelist_from_spf entries

Sending        spamassassin-3.4/UPGRADE
Sending        spamassassin-3.4/lib/Mail/SpamAssassin/Conf.pm
Sending        spamassassin-3.4/lib/Mail/SpamAssassin/Plugin/SPF.pm
Sending        spamassassin-3.4/t/spf.t
Sending        trunk/lib/Mail/SpamAssassin/Conf.pm
Sending        trunk/lib/Mail/SpamAssassin/Plugin/SPF.pm
Sending        trunk/t/spf.t
Transmitting file data .......done
Committing transaction...
Committed revision 1876710.

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

[Bug 7809] unwhitelist broken

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

--- Comment #5 from Henrik Krohns <ap...@hege.li> ---
(In reply to Benny Pedersen from comment #4)
> thanks for screwing it up :)

Could you please stop filling bugs with rambling nonsense?

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

[Bug 7809] unwhitelist broken

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

RW <rw...@googlemail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rwmaillists@googlemail.com

--- Comment #1 from RW <rw...@googlemail.com> ---
The documentation says that unwhitelist_auth cancels whitelist_auth entries not
def_whitelist_auth entries, so it's not broken as such or even unexpected, but
there should be a way of cancelling def_* entries. Originally these contained
uncontroversial senders like paypal, but it's been expanded enormously.

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

[Bug 7809] unwhitelist broken

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

Benny Pedersen <me...@junc.eu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |me@junc.eu

--- Comment #2 from Benny Pedersen <me...@junc.eu> ---
hopefully auth is done in dmarc in future with AuthRes plugin, the current auth
approc is to simple to fit user cases with double pass/fails

if def scores begin to be unstable adjust scores then, eg -7.5 could be changed
to -6.5

and i think its begin to be more needed to make local corpus score scanning so
spammers have to live with local generated scores

its all to easy to know what spamassassin will do if its common rules

todo: Mail::DKIM could be updated to handle openARC sealing so it helps to
track more deeply whar happens upstream, and dmarc can then possible be done in
AuthRes plugin with is not gone stable yet imho

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

[Bug 7809] unwhitelist broken

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

--- Comment #4 from Benny Pedersen <me...@junc.eu> ---
thanks for screwing it up :)

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