Thanks a lot, will check with my config.
Though, the distro is my own distro :) Sonicle XStream OS, illumos based.
So I bring updates :)
My question was about compatibility with older config files.
Inviato da iPad
> Il giorno 11/set/2015, alle ore 21:06, Thomas Spuhler
> ha scritto:
>
>> On F
Subject: SOLUTION for white-listing senders for banned files.
So, I've created some perl code to handle white-listing senders in relation to
banned files [attachments]. [It's a little more capable than this - but that's
a good start for a summary.]
I've seen the request to white-list banned fil
On Friday, September 11, 2015 10:34:40 AM Gabriele Bulfon wrote:
> Hi,
> I'm running an old server with amavis 2.7.0 and spamassassin 3.4.0 on perl
> 5.14.2. I found a lot of evident spam coming in (e.g. containing evident
> urls in russia while claiming to be the italian telco...), and I can't say
I'm not sure there is a simple way to do this, but...
When email is detected as spam, I add "+spam" to the address
and then it is filtered into the users spam folder via a sieve script
with dovecot deliver. The problem is that anyone who is also
forwarding their email on to another host (
Hello All,
I was trying to add another spam filter to Amavis, using @spam_scanners array
defined in amavisd-new code.
But, I soon realised reading Amavis code that Amavis has support only for the 4
Spam filters (SpamAssassin, DSPAM, CRM114, Bogofilter).package
Amavis::SpamControl::ExtProg; sub
Hi,
I'm running an old server with amavis 2.7.0 and spamassassin 3.4.0 on perl
5.14.2.
I found a lot of evident spam coming in (e.g. containing evident urls in russia
while claiming to be the italian telco...),
and I can't say why it does not get sucked.
I'm thinking to upgrade to latest amavis.
