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/05/06 19:39:34 UTC

[Bug 7021] TxRep - suggested replacement of Mail::SpamAssassin::Plugin::AWL

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

--- Comment #29 from Joe Quinn <jq...@pccc.com> ---
Finally got around to testing TxRep and I have some thoughts:

1 - Update your documentation for the txrep MySQL table to include a timestamp
field as below. It enables future expansion with things like aging over time,
and users can cull very old entries as an optimization.

CREATE TABLE txrep (
   username varchar(100) NOT NULL default '',
   email varchar(255) NOT NULL default '',
   ip varchar(40) NOT NULL default '',
   count int(11) NOT NULL default '0',
   totscore float NOT NULL default '0',
   signedby varchar(255) NOT NULL default '',
   last_hit timestamp NOT NULL default CURRENT_TIMESTAMP on update
CURRENT_TIMESTAMP,
   PRIMARY KEY (username,email,signedby,ip),
   KEY last_hit (last_hit)
 ) ENGINE=MyISAM;


2 - Installation and configuration is really easy - most AWL configuration
options can stay as-is, but auto_whitelist_factory needs to be renamed. Perhaps
you can have the plugin support that option as a fallback if txrep_factory
isn't defined?

3 - We'll be checking our database later this week for issues we had with AWL.
However, so far mail is flowing and nobody has complained, and everything seems
to behave as it should.

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