You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by "sebastian@debianfan.de" <se...@debianfan.de> on 2009/04/22 23:35:36 UTC
AWL - deactivate
Hello,
how to deactivate the AWL for the whole server ?
tnx
Sebastian
Re: AWL - deactivate
Posted by Duane Hill <d....@yournetplus.com>.
On Wed, 22 Apr 2009, sebastian@debianfan.de wrote:
> how to deactivate the AWL for the whole server ?
Place:
use_auto_whitelist 0
in the local.cf. By default it is turned on. Therefore you may not see the
entry. Otherwise, if you do, just set it to zero. You will have to restart
whatever is running SA (i.e. spamd, amavis-new).
Re: AWL - deactivate
Posted by Duane Hill <d....@yournetplus.com>.
On Wed, 22 Apr 2009, Matt Kettler wrote:
> Duane Hill wrote:
>> Additional comment below. I should have checked docs before I
>> initially responded.
>>
>> On Wed, 22 Apr 2009, Duane Hill wrote:
>>
>>> On Wed, 22 Apr 2009, Matt Kettler wrote:
>>>
>>>> Interesting. use_auto_whitelist used to be an admin-only option (valid
>>>> only in local.cf). But I guess if the admin wants to make sure no users
>>>> can turn it on, then they can comment out the loadplugin.
>>>
>>> It probably changed when AWL became a plugin. Our setup allows the
>>> end user to choose whether they want to use the option or not through
>>> SquirrelMail. The default set up in local.cf has the option turned off.
> Yes, the fact that it probably changed during the plugin conversion was
> part of what I was implying.
>
>>
>> I could be wrong on this. Looking back at the docs for 2.6x, 3.0.x and
>> 3.1.x, the use_auto_whitelist option is not listed under the
>> administrator settings section. Therefore, I would have thought it
>> would have been allowed under user_prefs.
>>
> You need to look closer :)
>
> 2.6x didn't have the option, it was a command-line parameter.
>
> 3.0.x did have the option, and it was an administrator setting:
>
> http://spamassassin.apache.org/full/3.0.x/dist/doc/Mail_SpamAssassin_Conf.html#administrator_settings
>
> By the time 3.1.0 was released, the AWL was already pluginized, so it,
> and all versions after, have behaved the same.
Thanks for the clarification.
Re: AWL - deactivate
Posted by Matt Kettler <mk...@verizon.net>.
Duane Hill wrote:
> Additional comment below. I should have checked docs before I
> initially responded.
>
> On Wed, 22 Apr 2009, Duane Hill wrote:
>
>> On Wed, 22 Apr 2009, Matt Kettler wrote:
>>
>>> Interesting. use_auto_whitelist used to be an admin-only option (valid
>>> only in local.cf). But I guess if the admin wants to make sure no users
>>> can turn it on, then they can comment out the loadplugin.
>>
>> It probably changed when AWL became a plugin. Our setup allows the
>> end user to choose whether they want to use the option or not through
>> SquirrelMail. The default set up in local.cf has the option turned off.
Yes, the fact that it probably changed during the plugin conversion was
part of what I was implying.
>
> I could be wrong on this. Looking back at the docs for 2.6x, 3.0.x and
> 3.1.x, the use_auto_whitelist option is not listed under the
> administrator settings section. Therefore, I would have thought it
> would have been allowed under user_prefs.
>
You need to look closer :)
2.6x didn't have the option, it was a command-line parameter.
3.0.x did have the option, and it was an administrator setting:
http://spamassassin.apache.org/full/3.0.x/dist/doc/Mail_SpamAssassin_Conf.html#administrator_settings
By the time 3.1.0 was released, the AWL was already pluginized, so it,
and all versions after, have behaved the same.
Re: AWL - deactivate
Posted by Duane Hill <d....@yournetplus.com>.
Additional comment below. I should have checked docs before I initially
responded.
On Wed, 22 Apr 2009, Duane Hill wrote:
> On Wed, 22 Apr 2009, Matt Kettler wrote:
>
>> Interesting. use_auto_whitelist used to be an admin-only option (valid
>> only in local.cf). But I guess if the admin wants to make sure no users
>> can turn it on, then they can comment out the loadplugin.
>
> It probably changed when AWL became a plugin. Our setup allows the end user
> to choose whether they want to use the option or not through SquirrelMail.
> The default set up in local.cf has the option turned off.
I could be wrong on this. Looking back at the docs for 2.6x, 3.0.x and
3.1.x, the use_auto_whitelist option is not listed under the administrator
settings section. Therefore, I would have thought it would have been
allowed under user_prefs.
Re: AWL - deactivate
Posted by Duane Hill <d....@yournetplus.com>.
On Wed, 22 Apr 2009, Matt Kettler wrote:
> Interesting. use_auto_whitelist used to be an admin-only option (valid
> only in local.cf). But I guess if the admin wants to make sure no users
> can turn it on, then they can comment out the loadplugin.
It probably changed when AWL became a plugin. Our setup allows the end
user to choose whether they want to use the option or not through
SquirrelMail. The default set up in local.cf has the option turned off.
Re: AWL - deactivate
Posted by Matt Kettler <mk...@verizon.net>.
Karsten Bräckelmann wrote:
> On Wed, 2009-04-22 at 16:47 -0500, Luis Croker wrote:
>
>> Hi.. You have to disable the plugin. I put a comment in this line in
>> v310.pre file and restart the daemons...
>>
>> #loadplugin Mail::SpamAssassin::Plugin::AWL
>>
>
> That is actually not necessary -- and limits the ability for users to
> selectively enable it, if they choose to.
>
Interesting. use_auto_whitelist used to be an admin-only option (valid
only in local.cf). But I guess if the admin wants to make sure no users
can turn it on, then they can comment out the loadplugin.
Which way you go depends on if you want users to have that choice or not
(ie: limited disk, therefore you want to be sure it's off).
> The AWL options may be set both site-wide and in the user-specific
> user_prefs files. If at least the plugin is loaded. ;)
>
>
>
>
Re: AWL - deactivate
Posted by Karsten Bräckelmann <gu...@rudersport.de>.
On Wed, 2009-04-22 at 16:47 -0500, Luis Croker wrote:
> Hi.. You have to disable the plugin. I put a comment in this line in
> v310.pre file and restart the daemons...
>
> #loadplugin Mail::SpamAssassin::Plugin::AWL
That is actually not necessary -- and limits the ability for users to
selectively enable it, if they choose to.
The AWL options may be set both site-wide and in the user-specific
user_prefs files. If at least the plugin is loaded. ;)
guenther
--
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: AWL - deactivate
Posted by Luis Croker <lc...@megacable.com.mx>.
Hi.. You have to disable the plugin. I put a comment in this line
in v310.pre file and restart the daemons...
#loadplugin Mail::SpamAssassin::Plugin::AWL
Regards.
On Wed, 2009-04-22 at 23:35 +0200, sebastian@debianfan.de wrote:
> Hello,
>
> how to deactivate the AWL for the whole server ?
>
> tnx
>
> Sebastian
>
>
Luis Croker
SCSA - SCNA
Administrador de Sistemas
Megacable Comunicaciones
GPG Key1024D/48C1764B
Key fingerprint = E8B6 E84F ECE4 661E 30C7 7208 042D BD09 48C1 764B
Re: AWL - deactivate
Posted by Karsten Bräckelmann <gu...@rudersport.de>.
On Thu, 2009-04-23 at 00:21 +0200, Yet Another Ninja wrote:
> On 4/23/2009 12:13 AM, Karsten Bräckelmann wrote:
> > My bet is... You will see spam to thisisonlytestmessage@ and mangled
> > variants thereof. :)
>
> don't forget 'akstc.*\@'
>
> :-)
Hah, seriously? *grep* Nah, you just made that up. ;)
I definitely was serious about mine. I've recently had a look at a
catch-all again, and did spot that old, long known pattern high up in
the stats.
I'd be happy to make a bet with Sebastian. :) Since you appear to be
located in Germany, too -- crate of beer, to be drunk at the winners
place? :)
guenther -- who still got some fraud to review for sought
--
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: AWL - deactivate
Posted by Yet Another Ninja <sa...@alexb.ch>.
On 4/23/2009 12:13 AM, Karsten Bräckelmann wrote:>
> My bet is... You will see spam to thisisonlytestmessage@ and mangled
> variants thereof. :)
don't forget 'akstc.*\@'
:-)
Re: AWL - deactivate
Posted by Karsten Bräckelmann <gu...@rudersport.de>.
On Wed, 2009-04-22 at 23:58 +0200, sebastian@debianfan.de wrote:
> > May I ask, why? Just curious.
>
> I bet with a friend about spammers and i have an virtual server which i
> don't need anymore - the contract ends in may - so i used some domains for
> spam honeypots because their mx-records are not in use.
Ah, thanks -- I see.
> I don't get any viruses - nothing - only mails for small blue ..... (i
> can't use this word because of spam filters) and mails for investments
> into stocks.
Hmm, weird. Spammers do use malware to acquire their bot-nets. Moreover,
they do use the very same network for spreading the malware just as they
send out spam -- at the very least, malware drop-off links.
Anyway, yes, you can say pills. Pills, pills, pills! ;) You can even
talk about Viagra. At least with a system like SA.
I am pretty confident though that I will get a bad bounce by that one
user of the braindead, bare-word scanner Microsoft Antigen. Time to get
him off our list, I guess...
> The configuration is only spamassassin - no rbl - no virus scanners - the
> domains are set all on catch all.
My bet is... You will see spam to thisisonlytestmessage@ and mangled
variants thereof. :)
> It is an experiment - only for 1 month.
What's the bet?
guenther
--
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: AWL - deactivate
Posted by "sebastian@debianfan.de" <se...@debianfan.de>.
> On Wed, 2009-04-22 at 23:35 +0200, sebastian@debianfan.de wrote:
>> Hello,
>>
>> how to deactivate the AWL for the whole server ?
>
> use_auto_whitelist 0
>
> Also see the docs.
> http://spamassassin.apache.org/full/3.2.x/doc/Mail_SpamAssassin_Plugin_AWL.html
>
> May I ask, why? Just curious.
>
>
I bet with a friend about spammers and i have an virtual server which i
don't need anymore - the contract ends in may - so i used some domains for
spam honeypots because their mx-records are not in use.
Much spam - you are able to fight with uceprotect, ix-manitu and uribl -
you don't need more.
I don't get any viruses - nothing - only mails for small blue ..... (i
can't use this word because of spam filters) and mails for investments
into stocks.
The configuration is only spamassassin - no rbl - no virus scanners - the
domains are set all on catch all.
It is an experiment - only for 1 month.
Re: AWL - deactivate
Posted by Karsten Bräckelmann <gu...@rudersport.de>.
On Wed, 2009-04-22 at 23:35 +0200, sebastian@debianfan.de wrote:
> Hello,
>
> how to deactivate the AWL for the whole server ?
use_auto_whitelist 0
Also see the docs.
http://spamassassin.apache.org/full/3.2.x/doc/Mail_SpamAssassin_Plugin_AWL.html
May I ask, why? Just curious.
--
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}