On Wed, Jan 09, 2008 at 20:45:12 +0100, Mark Martinec wrote:
Is there a way to configure Amavisd-new so that big mails (for example
bigger as 10 MB) do not get virus-scanned? If not, is it possible to
implement it with a custom hook?
Not configurable, but can be done through a custom
Hello Mark, hello Petr, hello list.
A few days agao I came across this problem. I am afraidI am stuck, having
looked through the READMES the archive and googled the problem. There
doesn't seem to be a solution, that works for me.
Any help or direction would be appreciated.
Many thanks in
David,
Cool! Thank you.
I am using the AM.PDP interface (amavisd-milter).
Is it also going to work with that?
I believe it will, although I haven't tested it extensively in this setup.
Mark
-
Check out the new
Peter Huetmannsberger wrote:
I am running sendmail with Petr Rehor's amavisd-milter and on this new
machine I am storing spam and the rest in a mysql database.
If I add the following to amavisd.conf:
$policy_bank{'SMTP_AUTH'} = {
originating = 1,
bypass_banned_checks_maps = [1],
Hello Mark,
thank you for your reply.
How do you load this policy bank? Through a policy_bank=... attribute
in AM.PDP request?
No, the following is the only change in amavisd.conf, which leads to the
error message. (but it works, apart from the sql part)
$policy_bank{'SMTP_AUTH'} = {
Thank you!
Now it works flawlessly.
All the best,
.peter
On Thu, 10 Jan 2008, Mark Martinec wrote:
Could you please try the following patch:
--- amavisd~ Wed Dec 12 12:28:26 2007
+++ amavisd Thu Jan 10 14:51:53 2008
@@ -13164,5 +13164,5 @@
for my $bank_name
Hello.
I have a frontend SMTP gateway that serves serveral domains. The frontend
spans trhough several server. Every server has the same
configuration/hardware. The platform of every server is
Postfix+MySQL+Amavisd-new.
I would like to enhanche my system implementing a shared quarantine
Benedict,
[...] I could have sworn that adding the +spam
on to an address only used to happen when you reached the ultimate cutoff.
It now seems to happen at tag level 2, at the same time that the subject is
changed.
Right.
This was changed in amavisd-new-2.0
(but broken in 2.4.0, fixed
Dear all,
Suddenly in the maillog of one our mail servers, the following error
message was appeared continuously. At ths time no mail delivery has
happend. Then I restarted Amavisd-new daemon and error was
disappeared.
I have amavisd-new-2.5.2 installed in this mail server. Any reason for
