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 2017/08/10 01:53:05 UTC
[Bug 7455] New: AWL and TxRep Need Documentation and Feature Parity
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7455
Bug ID: 7455
Summary: AWL and TxRep Need Documentation and Feature Parity
Product: Spamassassin
Version: 3.4 SVN branch
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: Plugins
Assignee: dev@spamassassin.apache.org
Reporter: kmcgrail@apache.org
Target Milestone: Undefined
With AWL, you could whitelist/blacklist an email with the spamassassin
executable:
Specifically
--add-addr-to-whitelist=addr Add addr to persistent address whitelist
--add-addr-to-blacklist=addr Add addr to persistent address blacklist
--remove-addr-from-whitelist=addr Remove addr from persistent address list
Those commands need to be clarified as AWL only (for now)
And extend them for all persistent blacklist/whitelist engines (AWL and/or
TXrep and/or xyz)
We should also clarify that the command for whitelist, weights the address in
the whitelist to the extreme. However, new emails could evolve the entry.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7455] AWL and TxRep Need Documentation and Feature Parity
Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7455
--- Comment #5 from RW <rw...@googlemail.com> ---
(In reply to RW from comment #4)
> it's SAGrey that needs to be updated rather than TxRep.
Actually that's not quite correct because TxRep can do score averaging for IP
addresses etc, so it would exempt more than an AWL hit.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7455] AWL and TxRep Need Documentation and Feature Parity
Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7455
--- Comment #2 from Kevin A. McGrail <km...@apache.org> ---
I've never even heard of that plugin so I doubt there is any work planned
around supporting TXRep with SA-Grey. Perhaps open a ticket and if you can
submit even a framework of code, that would be helpful
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7455] AWL and TxRep Need Documentation and Feature Parity
Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7455
Kevin A. McGrail <km...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7455] AWL and TxRep Need Documentation and Feature Parity
Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7455
Kevin A. McGrail <km...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kmcgrail@apache.org
Target Milestone|Undefined |Future
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7455] AWL and TxRep Need Documentation and Feature Parity
Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7455
RW <rw...@googlemail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rwmaillists@googlemail.com
--- Comment #4 from RW <rw...@googlemail.com> ---
SAGrey checks for AWL like this:
($permsgstatus->get_names_of_tests_hit() =~ /\bAWL\b/)
it's SAGrey that needs to be updated rather than TxRep.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7455] AWL and TxRep Need Documentation and Feature Parity
Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7455
Karsten Bräckelmann <gu...@rudersport.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #6 from Karsten Bräckelmann <gu...@rudersport.de> ---
(In reply to Kevin A. McGrail from comment #0)
> With AWL, you could whitelist/blacklist an email with the spamassassin
> executable:
>
> Specifically
>
> --add-addr-to-whitelist=addr Add addr to persistent address whitelist
> --add-addr-to-blacklist=addr Add addr to persistent address blacklist
> --remove-addr-from-whitelist=addr Remove addr from persistent address list
These are implemented in SA 4.0.x (and since 3.4.1 when TxRep was first
included) as
sub blocklist_address
sub welcomelist_address
sub remove_address
and called from SpamAssassin.pm / spamassassin executable via call_plugins().
spamassassin executable options' documentation seems appropriate, and overall
TxRep plugin documentation extensive.
Closing RESOLVED FIXED.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7455] AWL and TxRep Need Documentation and Feature Parity
Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7455
--- Comment #3 from Benny Pedersen <me...@junc.eu> ---
link to current hopefully
https://github.com/szepeviktor/spamassassin-sagrey
i can provide what i do, just not commit it to sa
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7455] AWL and TxRep Need Documentation and Feature Parity
Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7455
Benny Pedersen <me...@junc.eu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |me@junc.eu
--- Comment #1 from Benny Pedersen <me...@junc.eu> ---
also that TxRep does not support SA-Grey 3dr party plugin, is this planned to
be added to TxRep
--
You are receiving this mail because:
You are the assignee for the bug.