Chris,
Is it possible to log *only* quarantined mails, and not all mails
passing through amavis? From what I can see, setting @storage_sql_dsn
will cause logging of all mails.
Not possible without tweaking the code. The @storage_sql_dsn is global.
It might be possible to tweak entries in
Chaminda Indrajith,
I need to setup Amavisd-new to send notifications when a message is
blocked due to SPAM, VIRUS or BAD HEADER to intended recipients.
Possible (through a configuration setting), but it is really pointless
to replace one junk with an even less informative junk, so I won't go
On Fri, October 19, 2007 9:42 pm, Richard Bishop wrote:
On Fri, 19 Oct 2007 21:18:24 +1000 (EST), Voytek Eymont
I'm now looking at 'enhancing' the system with providing per domain
or even per user controls and user 'self management tool'
I suggest you take a look at MailZu which will
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Chaminda Indrajith
Sent: Friday, October 19, 2007 12:49 AM
To: amavis-user@lists.sourceforge.net
Subject: [AMaViS-user] How to send notifications to intended
recipients
Dear All,
I need
Here is my problem: I have an entry which produces an infinitely running
amavisd process. The reason why is not clear up to now. The problem
disappears when setting $bypass_decode_parts = 1;, therefore I think
that the problem is probably related to spamassassin. I will have to
examine the
On 10/19/07, Voytek wrote:
there is a section about having '[EMAIL PROTECTED] - [EMAIL PROTECTED] ';
is there a way to have [EMAIL PROTECTED]'s spam delivered to his IMAP 'spam'
folder??
--
Voytek
To get amavisd-new to rewrite the address to user+spam, in amavisd.conf, set:
At 01:45 AM 10/19/2007, Claude Frantz wrote:
Here is my problem: I have an entry which produces an infinitely running
amavisd process. The reason why is not clear up to now. The problem
disappears when setting $bypass_decode_parts = 1;, therefore I think
that the problem is probably related to
I have Postfix 2.4 /amavis 2.5.2 /mysql 4.1
/clam with virtual domains/users;
it all works very well, with 'one size fits all' approach;
with just badh/virus/spam/forbidden_lovers as only individual exceptions
I'm now looking at 'enhancing' the system with providing per domain
or even per user
