http://bugzilla.spamassassin.org/show_bug.cgi?id=4163





------- Additional Comments From [EMAIL PROTECTED]  2005-05-06 05:29 -------
Subject: Re:  RFE: add reporting support to spamd/spamc

> ------- Additional Comments From [EMAIL PROTECTED]  2005-05-06 03:26 -------
> 
> As I consider this again. I think it won't be a good idea to learn 
> automatically 
> if triggered for report/revoke.
> - report/revoke would produce some (network) overhead if done everytime a 
> message is learned (especially no one remembers that report/revoke happens 
> when 
> learning is done)
> - no need for a seperate spamc switch (-L already implemented)

> I'am not amused not to overthink the user part.
> Please introduce to query the 'use_Razor2' (and other) settings from SQL/
> userpref and use that for reporting!? I think it should be!
> Sorry, but I've another opinion about that :-)

The code will use all of the same mechanisms that it does now, so
there is nothing to think about here.  If -L is specified then it
won't be available, period.  If use_razor2 is set to 0 then we won't
report/revoke fomr razor, so on and so forth.

Learning either as spam for reporting or as ham for revoking is just
how that code works.

Like I said, I think you are overthinking.


> 
> >We could go simple and do something like:
> >Reported: Yes
> >Reported: No
> 
> I vote for that. +1 :-)
> 
> >Did you pick out command line options?
> 
> Not as you considered. I've simply add an switch (-W) to spamc! Too, there 
> are 
> some others free. Not perfectly but it works.

Works for me, it is easily changed if for some reason it doesn't work
out.

FYI, here is the output I just got from spamd:
2329] dbg: markup: removing markup
[2329] dbg: plugin: Mail::SpamAssassin::Plugin::Razor2=HASH(0x8dadbd4) 
implements 'plugin_revoke'
[2329] dbg: info: entering helper-app run mode
[2329] dbg: info: leaving helper-app run mode
[2329] dbg: reporter: spam revoked from Razor
[2329] info: spamd: revoked ham message for parker:1000 in 0.7 seconds, 2569 
bytes

Michael




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

Reply via email to