Hi,
I've read 2.4.2 docs and past messages, but found not a real answer.
Is there a performance reason, future (un)support, cleaniness, ... to
switch from
time_iso char(16) NOT NULL,
to
time_iso TIMESTAMP NOT NULL DEFAULT 0,
??
I can't see a good reason, except for a more
somehow, whilst doing a Perl CPAN updates, my Perl got out of sync,
causing Amavis failure.
in the interim, I've diabled amavis from /etc/postfix/main.cf, so, my mail
works again
before I look at fixing my problems:
how do I get all the 'stuck' mail out:
#mailq
...
F0D99238A2E11257 Tue Jul
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gary V
Sent: Monday, July 03, 2006 8:40 PM
To: amavis-user@lists.sourceforge.net
Subject: Re: [AMaViS-user] Getting new backscatter with 2.4.2
This looks like D_REJECT, not D_BOUNCE. Grep
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Voytek Eymont
Sent: Tuesday, July 04, 2006 3:50 AM
To: amavis-user@lists.sourceforge.net
Subject: [AMaViS-user] recovering from Perl failure:
transport unavailable
somehow, whilst doing a
Dear Mark and others,
I'm implementing Kaspersky AV version 5.5 in AMaViS version 2.4.1.
The config out-of-the-box contains:
-8-
### http://www.kaspersky.com/ (kav4mailservers)
['KasperskyLab AVP - aveclient',
['/usr/local/kav/bin/aveclient','/usr/local/share/kav/bin/aveclient',
-8-
### http://www.kaspersky.com/ (kav4mailservers)
['KasperskyLab AVP - aveclient',
['/usr/local/kav/bin/aveclient','/usr/local/share/kav/bin/aveclient',
'/opt/kav/5.5/kav4mailservers/bin/aveclient','aveclient'],
'-p /var/run/aveserver -s {}/*', [0,6,8],
* Jakob Curdes [EMAIL PROTECTED]:
That is good news, I hesitated updateing my KAV installations because I
feared the detection code would break. BTW, in newer KAV workstation
and mail packages I miss the Client-Server binaries. Does anybody know
if they are still provided with one of the KAV
Michael wrote:
try
grep -r D_REJECT /etc
Maybe amavisd-new is reading a different file.
I did mention that it worked fine(tm) with 2.3.3 ...
Yep.
If amavisd-new bounces it, the DSN will be from amavisd-new (although
there should not be one in this case), if D_REJECT is used, your MTA
will
Dear Jakob,
You wrote:
-Original Message-
From: Jakob Curdes [mailto:[EMAIL PROTECTED]
Sent: dinsdag 4 juli 2006 16:04
To: Overdijk, H. (Harrie)
Cc: amavis-user@lists.sourceforge.net
Subject: Re: [AMaViS-user] Kaspersky AV entry in amavisd.conf
-8-
###
Ralf Hildebrandt schrieb:
Yes, in the mail server product. Oh, the coincidence!
Did I miss the Client ? I found the aveserver but no aveclient in there.
JC
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to
* Jakob Curdes [EMAIL PROTECTED]:
Ralf Hildebrandt schrieb:
Yes, in the mail server product. Oh, the coincidence!
Did I miss the Client ? I found the aveserver but no aveclient in there.
Don't you have to build that from source therE?
--
Ralf Hildebrandt (i.A. des IT-Zentrums)
You can do that already with amavis using
*$banned_filename_re *patterns.
Please explain... I do not intend to ban .zip files.
From amavisd-conf.sample :
# # block if any component can not be decoded (is encrypted or bad archive)
# qr'(?# BLOCK IF UNDECIPHERABLE ) ^ (.*\t)? A=U
Michael wrote:
And just to be complete:
Postfix is version 2.2.8
master.cf has these changes:
smtp inet n - n - - smtpd
-o receive_override_options=no_address_mappings
lmtp-amavis unix - - n - 4 lmtp
-o
Gary wrote:
Mailq empty
This is curious. I would think if spam was getting rejected, at least
some of the DSNs would not be deliverable. Have you maybe set
bounce_queue_lifetime 0 ?
If so, that would explain.
Or maybe it's just that the buck is passed to another server.
Gary V
Using
And, ONLY sites with 2.4.2 are doing this:
grep -c '1 Rejected' /var/log/maillog
99.99% of the 'Blocked SPAM' is also logging '554 5.7.1 Rejected' and
bouncing.
On sites without 2.4.2:
Even zgrep -c '1 Rejected' /var/log/maillog* doesn't show anything.
(maybe one or two over the last month)
Gary wrote:
I used your entries in master.cf and I could reproduce this.
lmtp-amavis unix - - n - 2 lmtp
-o lmtp_data_done_timeout=1200
-o lmtp_send_xforward_command=yes
-o disable_dns_lookups=yes
-o header_checks=regexp:/etc/postfix/remove_headers
Paolo wrote:
Hi,
I've read 2.4.2 docs and past messages, but found not a real answer.
Is there a performance reason, future (un)support, cleaniness, ... to
switch from
time_iso char(16) NOT NULL,
to
time_iso TIMESTAMP NOT NULL DEFAULT 0,
??
I can't see a good reason, except
lmtp-amavis unix - - n - 2 lmtp
-o header_checks=regexp:/etc/postfix/remove_headers
smtp-amavis unix - - n - 2 smtp
-o header_checks=regexp:/etc/postfix/remove_headers
Note that header_checks are performed by the postfix
cleanup service and
18 matches
Mail list logo
