>> Den 2012-07-26 17:26, Nißl Reinhard skrev:
>>> reading the manuals, I've discovered that the AWL plugin isn't
>>> loaded anymore in spamassassin 3.3. Therefore I put the
>>> following lines into local.cf:
> On Fri, 27 Jul 2012 02:57:26 +0200 Benny Pedersen wrote:
>> oh no, do not put loadlugin
@spamassassin.apache.org
Betreff: Re: How do I reenable AWL on spamassassin 3.3 after upgrade from 3.1
Den 2012-07-26 17:26, Nißl Reinhard skrev:
> reading the manuals, I've discovered that the AWL plugin isn't loaded
> anymore in spamassassin 3.3. Therefore I put the following lines into
> local
Den 2012-07-27 03:14, RW skrev:
It seems inelegant, but is there a practical reason why this
shouldn't
be done. Some optional plugins such as Botnet and iXhash load
themselves
from their own .cf files.
did --lint not show it ?
On Fri, 27 Jul 2012 02:57:26 +0200
Benny Pedersen wrote:
> Den 2012-07-26 17:26, Nißl Reinhard skrev:
>
> > reading the manuals, I've discovered that the AWL plugin isn't
> > loaded anymore in spamassassin 3.3. Therefore I put the following
> > lines into local.cf:
>
> oh no, do not put loadlugi
Den 2012-07-26 17:26, Nißl Reinhard skrev:
reading the manuals, I've discovered that the AWL plugin isn't loaded
anymore in spamassassin 3.3. Therefore I put the following lines into
local.cf:
oh no, do not put loadlugin into *.cf files its wrong pr design, but so
much wiki and bad behavior s
Hi,
reading the manuals, I've discovered that the AWL plugin isn't loaded anymore
in spamassassin 3.3. Therefore I put the following lines into local.cf:
loadplugin Mail::SpamAssassin::Plugin::AWL
use_auto_whitelist 1
but the file auto-whitelist hasn't been touched since the upgrade from 3.1 to
