|Main Archive Page > Month Archives > spamassassin-dev archives|
--- Comment #14 from AXB <email@example.com> 2011-08-12 16:39:50 UTC ---
(In reply to comment #12)
> What percentage of legit emails were passing SPF and DKIM when rules for them
> were added?
quite alot. There were milters and filters and it was a standard quite a while
before SA adopted it.
> (In reply to comment #9)
> > I'm sorry but this was beaten to death long time ago on the users list. But as
> > long as it never will be on by default I don't care either way. It's ridiculous
> > to assume people would adopt this just because SA uses it.
> Why is it ridiculous to assume people would adopt this just because SA uses it?
> That's not quite exactly what I'm suggesting. What's wrong with adding it to
> SA to see if it increases adoption and ends up very useful?
90% of the SA setups are on auto-pilot (Think Cpanel/Plesk and all the other
millions of shared hosting shps using SA)
Having it installed doesn't automatically mean anybody will understand it,
mantain it locally or even notice the value.
> (In reply to comment #11)
> > Plugins don't get added coz we like them or they've been written by friends.
> > They get added because they prove themselves efficient and do something worth
> > while.
> And what if the best chance something has to prove itself efficient and worth
> while is to add it to SA?
> > First, it should be added to
> > http://wiki.apache.org/spamassassin/CustomPlugins and allow potential users to
> > test and comment.
> > It can be also placed in a samnbox and allow masschecks to use it and if the
> > results are convincing , it will be reviewed, discusses, tested, taken apart
> > and maybe it gets added to mainstream code.
> So I should create a patch to create a rulesrc/sandbox/darxus directory in
> trunk containing MTX.pm, a .pre to load the module and a .cf to set the scores?
IIrc, put the MTX plugin as sandbox-darxus.pm plugin in
rulesrc/sandbox/darxus as other sandbox have their test plugins
(hstern/felicity, etc) create the rules and set the rules to "tflags nopublish"
and wait for results.
-- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.