https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7826
--- Comment #37 from AXB <[email protected]> --- (In reply to Kevin A. McGrail from comment #36) > I just committed a second version of the proof of concept for whitelist_to: > > svn commit -m 'changing whitelist_to to welcomelist_to including backward > compatibility stubs and add a feature check instead of using a version test > for rules.' > Sending MANIFEST > Sending lib/Mail/SpamAssassin/Conf.pm > Sending lib/Mail/SpamAssassin/Plugin/WLBLEval.pm > Sending rules/30_text_de.cf > Sending rules/30_text_fr.cf > Sending rules/30_text_pl.cf > Sending rules/30_text_pt_br.cf > Sending rules/50_scores.cf > Sending rules/60_whitelist.cf > Sending rules/active.list > Sending rules/v343.pre > Sending t/whitelist_to.t > Transmitting file data ............ > Committed revision 1879735. > > As noted in the commit log, this uses welcomelist, has stubs for > compatibility and uses if > can(Mail::SpamAssassin::Conf::feature_blocklist_welcomelist) for the rule > encapsulation. > > Using WelcomeList and BlockList will allow all acronyms like WLBLEval and > RBL to remain the same. > > As with before, if this proves to work, we will start on whitelist_from and > move on to more routines until finished. why is a POC put in trunk? - PLEASE, PLEASE put the playpen in a branch -- You are receiving this mail because: You are the assignee for the bug.
