Re: Command line option to disable AWL?
On Sun, Feb 04, 2007 at 12:45:31PM -, Alexis Manning wrote: > Do you know if that option will be supported by spamc as well? If so > I'll probably hang fire until 3.2.0 is released. spamd doesn't take configuration from spamc, so no. -- Randomly Selected Tagline: "I don't think Microsoft is evil in itself; I just think they make really crappy operating systems."- Linus Torvalds pgpNJHMeHBnRO.pgp Description: PGP signature
Re: Command line option to disable AWL?
[EMAIL PROTECTED] says... > Matt Kettler writes: > > But you can use the command-line to force an alternate user_prefs file, > > and have that file contain a "use_auto_whitelist 0". Assuming you're > > using the "spamassassin" command line script for your second scan, the > > -p option will over-ride the user_prefs file with any other file you > > specify. > > for what it's worth, in 3.2.0 you can also use a new "--cf" switch: > > spamassassin --cf "use_auto_whitelist 0" ... Do you know if that option will be supported by spamc as well? If so I'll probably hang fire until 3.2.0 is released. -- A.
Re: Command line option to disable AWL?
Matt Kettler writes: > Alexis Manning wrote: > > I use SA as an enduser. In my setup, messages in a certain score range > > arenât delivered to the mailbox but are held for a few hours so they can > > be > > resubmitted, giving DNSBLs/DCC a chance to pick up on new spam. The idea > > here is that very high scoring messages (for me >15) are dumped in a folder > > that is never reviewed but intermediate scoring messages are put in a folder > > that is reviewed, so a recheck allows the effort of manually checking mail > > to be minimised. > > > > This works pretty well for me but the AWL sometimes gets in the way: the > > second time messages are processed they are often scored higher because of > > the DNSBL hits but the AWL averaging causes lots of points to be taken off! > > > > Is there any way of either undoing the effect of AWL after the message is > > first processed and I decide it needs to be rescanned later, or a > > command-line option to stop AWL being applied the second time round? > > > > > No, there is no command line option at all. > > But you can use the command-line to force an alternate user_prefs file, > and have that file contain a "use_auto_whitelist 0". Assuming you're > using the "spamassassin" command line script for your second scan, the > -p option will over-ride the user_prefs file with any other file you > specify. for what it's worth, in 3.2.0 you can also use a new "--cf" switch: spamassassin --cf "use_auto_whitelist 0" ... --j.
Re: Command line option to disable AWL?
Matt Kettler wrote: > But you can use the command-line to force an alternate user_prefs file, > and have that file contain a "use_auto_whitelist 0". Assuming you're > using the "spamassassin" command line script for your second scan, the > -p option will over-ride the user_prefs file with any other file you > specify. Ah! Interesting thought - hadn't occurred to me at all. I usually use spamc, where -p doesn't seem to be supported, but perhaps the additional overhead of calling the spamassasssin command won't matter too much given the number of messages that need to be reprocessed. Cheers, -- A.
Re: Command line option to disable AWL?
Alexis Manning wrote: > I use SA as an enduser. In my setup, messages in a certain score range > aren’t delivered to the mailbox but are held for a few hours so they can be > resubmitted, giving DNSBLs/DCC a chance to pick up on new spam. The idea > here is that very high scoring messages (for me >15) are dumped in a folder > that is never reviewed but intermediate scoring messages are put in a folder > that is reviewed, so a recheck allows the effort of manually checking mail > to be minimised. > > This works pretty well for me but the AWL sometimes gets in the way: the > second time messages are processed they are often scored higher because of > the DNSBL hits but the AWL averaging causes lots of points to be taken off! > > Is there any way of either undoing the effect of AWL after the message is > first processed and I decide it needs to be rescanned later, or a > command-line option to stop AWL being applied the second time round? > > No, there is no command line option at all. But you can use the command-line to force an alternate user_prefs file, and have that file contain a "use_auto_whitelist 0". Assuming you're using the "spamassassin" command line script for your second scan, the -p option will over-ride the user_prefs file with any other file you specify.
Command line option to disable AWL?
I use SA as an enduser. In my setup, messages in a certain score range arent delivered to the mailbox but are held for a few hours so they can be resubmitted, giving DNSBLs/DCC a chance to pick up on new spam. The idea here is that very high scoring messages (for me >15) are dumped in a folder that is never reviewed but intermediate scoring messages are put in a folder that is reviewed, so a recheck allows the effort of manually checking mail to be minimised. This works pretty well for me but the AWL sometimes gets in the way: the second time messages are processed they are often scored higher because of the DNSBL hits but the AWL averaging causes lots of points to be taken off! Is there any way of either undoing the effect of AWL after the message is first processed and I decide it needs to be rescanned later, or a command-line option to stop AWL being applied the second time round? I would rather not disable AWL altogether because I do get a fair few messages from people which discuss spam and may have spammy content. Any thoughts appreciated, -- A.
