[AMaViS-user] How to preserve X-DSPAM-Signature in detected spam email?

Hi, Let me rephrase the subject line... ^_^ Is there anyway I can preserve the X-DSPAM-Signature in the headers when an email is tagged as spam? I'm just using SA's static rules and DSPAM's bayesian capability. Thanks, Peter --- This SF.Net

Re: [AMaViS-user] final_virus_destiny

Andrea, > I set $final_virus_destiny=D_BOUNCE ... > ... What happen if I put > $warnvirussender=0 (will not the notify be sent to the sender ?) Don't let $warnvirussender confuse you. It is best to pretend that this option does not exist - it is a relict from past versions, kept for compatibilit

Re: [AMaViS-user] amavisd-new 2.4.0-pre7 is available

> Anyway, here is a mail with a patch to 5.419 from the hand > of David F. Skoll. Fixing that one line and bumping the $VERSION > in MIME/Entity.pm to 5.420 fixes the problem and makes it work with > amavisd-new-2.4.0 (and with 2.3.3, which just doesn't notice the problem, > but it exists neverthe

RE: [AMaViS-user] amavisd-new 2.4.0-pre7 is available

> > # /usr/sbin/amavisd.new > > MIME::Entity 5.419 breaks quoted-printable encoding, please > upgrade to > > 5.420 or later (or use 5.418) at /usr/sbin/amavisd.new line 8768. > > > > But a CPAN search yields no 5.420 version: > > http://search.cpan.org/dist/MIME-tools/lib/MIME/Entity.pm > > I in

Re: [AMaViS-user] Re: amavisd-new 2.4.0-pre7 is available

Heute (17.03.2006/21:16 Uhr) schrieb Mark Martinec ([EMAIL PROTECTED]), > Jim, >> /usr/sbin/amavisd-new[14896]: Net::Server: Accept failed with 2 >> tries left. Mar 17 17:34:44 server2.art-domains.de >> /usr/sbin/amavisd-new[14896]: Net::Server: Accept failed with 1 >> tries left. Mar 17 17:34:45

Re: [AMaViS-user] amavisd-new 2.4.0-pre7 is available

> > http://www.ijs.si/software/amavisd/amavisd-new-2.4.0-pre7.tar.gz > Holy shit! What is this? > > # /usr/sbin/amavisd.new > MIME::Entity 5.419 breaks quoted-printable encoding, please upgrade to > 5.420 or later (or use 5.418) at /usr/sbin/amavisd.new line 8768. > > But a CPAN search yields no

Re: [AMaViS-user] amavisd-new 2.4.0-pre7 is available

* Mark Martinec <[EMAIL PROTECTED]>: > Here is a next 2.4.0 pre-release, expected to be the last one of pre-releases: > > http://www.ijs.si/software/amavisd/amavisd-new-2.4.0-pre7.tar.gz It seems to work here. I like that! -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] C

Re: [AMaViS-user] RH9 sendmail 8.12.8 and Petr Rehor's amavis-milter

> $unix_socketname = "$MYHOME/amavisd.sock"; > $protocol=>'AM.CL'; Cut/paste mistake, should be: $protocol='AM.CL'; (the '=>' is to be used within policy banks, an '=' outside). Mark --- This SF.Net email is sponsored by xPML, a groundbreak

Re: [AMaViS-user] amavisd-new 2.4.0-pre7 is available

* Ralf Hildebrandt <[EMAIL PROTECTED]>: > But a CPAN search yields no 5.420 version: > http://search.cpan.org/dist/MIME-tools/lib/MIME/Entity.pm > > Grmbl... Went back to 5.418, but does 5.420 really exist or is Marc merely postulating it's existence? -- Ralf Hildebrandt (i.A. des IT-Zentrums)

Re: [AMaViS-user] amavisd-new 2.4.0-pre7 is available

* Mark Martinec <[EMAIL PROTECTED]>: > Here is a next 2.4.0 pre-release, expected to be the last one of pre-releases: > > http://www.ijs.si/software/amavisd/amavisd-new-2.4.0-pre7.tar.gz Holy shit! What is this? # /usr/sbin/amavisd.new MIME::Entity 5.419 breaks quoted-printable encoding, plea

Re: [AMaViS-user] Re: amavisd-new 2.4.0-pre7 is available

Jim, > /usr/sbin/amavisd-new[14896]: Net::Server: Accept failed with 2 > tries left. Mar 17 17:34:44 server2.art-domains.de > /usr/sbin/amavisd-new[14896]: Net::Server: Accept failed with 1 > tries left. Mar 17 17:34:45 server2.art-domains.de > /usr/sbin/amavisd-new[14896]: Net::Server: Accept fai

Re: [AMaViS-user] RH9 sendmail 8.12.8 and Petr Rehor's amavis-milter

Adam, > Anyone know the proper setup for the old amavis-milter.c with > amavisd-new 2.3.x or 2.4.0-pre7? > > With 20030616 version of amavisd-new you would just define: > $forward_method = undef; > $unix_socketname = "$MYHOME/amavisd.sock"; Should still work the same way. The default protocol in

Re: [AMaViS-user] RH9 sendmail 8.12.8 and Petr Rehor's amavis-milter

Martin Svensson wrote: Hi Adam, We're using Amavis-milter with RHEL 3.0's Sendmail version 8.12.11 and it's working great. 80,000 emails/day on 2 servers with SA (incl. network tests, DCC and Bayes SQL) and 2 virusscanners. No such luck with the milter at http://amavisd-milter.sourceforge.ne

Re: [AMaViS-user] final_virus_destiny

Andrea wrote: > I don't understand $final_virus_destiny, $warnvirussender and > $warnvirusrecip. > I will explain you. > I set $final_virus_destiny=D_BOUNCE and the definition is: > mail will not be delivered to its recipients, a non-delivery notification > (bounce) will be sent to the sender by a

Re: [AMaViS-user] $banned_admin

Gary, > I tested a few things and failed to find any issues. Good. > I found it interesting however that it appears %virus_admin requires the > full recipient email address on the Left Hand Side: > read_hash(\%virus_admin, '/var/lib/amavis/virus_admin'); > contents of /var/lib/amavis/virus_admin

Re: [AMaViS-user] RH9 sendmail 8.12.8 and Petr Rehor's amavis-milter

Hi Adam, We're using Amavis-milter with RHEL 3.0's Sendmail version 8.12.11 and it's working great. 80,000 emails/day on 2 servers with SA (incl. network tests, DCC and Bayes SQL) and 2 virusscanners. Regards, Martin Adam Gibson wrote: Has anyone tried the newer amavis-milter with RedHat9's

[AMaViS-user] RH9 sendmail 8.12.8 and Petr Rehor's amavis-milter

Has anyone tried the newer amavis-milter with RedHat9's sendmail 8.12.8? I have not had any problems with any other milter so I am really just curious if this is a hard requirement or just a recommendation because it has not been tested with 8.12.8. If the answer is that it does require 8.13.

Re: [AMaViS-user] $banned_admin

Mark wrote: >> in amavisd.conf-defaults are shown defaults for the following: >> >> # $banned_admin = [EMAIL PROTECTED]; # for compatibility with >> pre-2.2.1 # $bad_header_admin = [EMAIL PROTECTED]; # for compatibility >> with pre-2.2.1 >> >> # @banned_admin_maps= (\$banned_admin); >> #

Re: [AMaViS-user] bug in 2.3.3 ??

Charles, > at the bottom is debug output coming from the amavisd-2.3.3 tarball that > i just downloaded > is this serious? i don't remember seeing it in past versions ... > [EMAIL PROTECTED] ~]# amavisd -u amavis -g amavis debug-sa > Use of uninitialized value in split at /usr/sbin/amavisd line 8

[AMaViS-user] Re: amavisd-new 2.4.0-pre7 is available

Heute (17.03.2006/13:36 Uhr) schrieb Mark Martinec ([EMAIL PROTECTED]), > Here is a next 2.4.0 pre-release, expected to be the last one of pre-releases: > > http://www.ijs.si/software/amavisd/amavisd-new-2.4.0-pre7.tar.gz > I seized the last opportunity to reshuffle modules around a bit, > to

[AMaViS-user] final_virus_destiny

I don't understand $final_virus_destiny, $warnvirussender and $warnvirusrecip. I will explain you. I set $final_virus_destiny=D_BOUNCE and the definition is: mail will not be delivered to its recipients, a non-delivery notification (bounce) will be sent to the sender by amavisd-new; What happen if

[AMaViS-user] Patches for FREEBSD ports for SA 3.11 for the impatient

Patches for SA 3.11 (released 3/6/2006) Notes for fixes include fixed for incompatible DomainKeys.pm (hence the dependency in makefile. I hope I have it right) Tested in portupgrade on 4.11 and 5.4 Tested in deinstall/reinstall on 4.11 and 5.4 Not tested in greenfields install, or system with ol

[AMaViS-user] Preserve X-DSPAM-Signature in detected spam email

Hi, Is there anyway I can preserve the X-DSPAM-Signature in the headers when an email is tagged as spam? I'm just using SA's static rules and DSPAM's bayesian capability. Thanks, Peter --- This SF.Net email is sponsored by xPML, a groundbrea

Re: [AMaViS-user] amavisd, spamassassin 3.1.1 and sa-update

> Can you edit config and put new rules in same directory as your > local.cf? > /etc/spamassassin/local.cf? Or > /usr/local/etc/mail/spamassassin./local.cf? Not really. Rules in this directory replace the one of /usr/share/spamassassin. man 1 spamassassin: Default configuration data

[AMaViS-user] bug in 2.3.3 ??

hi all, hi mark, at the bottom is debug output coming from the amavisd-2.3.3 tarball that i just downloaded is this serious? i don't remember seeing it in past versions ... cheers charles [EMAIL PROTECTED] ~]# amavisd -u amavis -g amavis debug-sa Use of uninitialized value in split at /usr/sbi

Re: [AMaViS-user] amavisd-new 2.4.0-pre7 is available

> I expect to make a pre-release in few days, probably this Monday. ... a release candidate, that is. And a final release by the end of the coming week. Mark --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language tha

Re: [AMaViS-user] $banned_admin

> in amavisd.conf-defaults are shown defaults for the following: > > # $banned_admin = [EMAIL PROTECTED]; # for compatibility with > pre-2.2.1 # $bad_header_admin = [EMAIL PROTECTED]; # for compatibility > with pre-2.2.1 > > # @banned_admin_maps= (\$banned_admin); > # @bad_header_admin_ma

[AMaViS-user] amavisd-new 2.4.0-pre7 is available

Here is a next 2.4.0 pre-release, expected to be the last one of pre-releases: http://www.ijs.si/software/amavisd/amavisd-new-2.4.0-pre7.tar.gz I seized the last opportunity to reshuffle modules around a bit, to make modules like Amavis::Out::SMTP, Amavis::Out::Pipe, Amavis::Out::BSMTP and Ama

RE: [AMaViS-user] amavisd, spamassassin 3.1.1 and sa-update

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Cedric Foll > Sent: Thursday, March 16, 2006 8:17 AM > To: amavis-user@lists.sourceforge.net > Subject: [AMaViS-user] amavisd, spamassassin 3.1.1 and sa-update > > > Hi, > > since spamassassin 3.