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 (val
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
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
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 se
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
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
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.*\@'
:-)
On Wed, 2009-04-22 at 23:58 +0200, sebast...@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
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
selectiv
> On Wed, 2009-04-22 at 23:35 +0200, sebast...@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
On Wed, 22 Apr 2009, sebast...@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
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, sebast...@debianfan.de wrote:
> Hello,
>
> how to deactivate the AWL for the whole ser
On Wed, 2009-04-22 at 23:35 +0200, sebast...@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="
Hello,
how to deactivate the AWL for the whole server ?
tnx
Sebastian
14 matches
Mail list logo
