Amavisd-new errors

2004-04-19 Thread R. Zoontjens
Hi,

This question does not concern FreeBSD only, I know... But here it goes.

I am working on a mailserver that has antispam and antivirus 
functionality. I gathered some courage and read articles at O'reilly and 
Daemonnews to build-my-own. Also did some extensive Googling.

The stuff I use: Postfix + Courier-IMAP + Amavis-new + ClamAV + 
Spamassassin (and probably Mimedefang). Of course on FreeBSD ;)

Postfix runs just fine. Courier Imap-ssl and pop3-ssl too.
Clamscan and Clamd are running fine.
I have amavisd running in debug mode (/usr/local/sbin/amavisd debug).
Normal mail gets scanned and all works well.
But when I send a mail with a test virus (eicar), it is recognized by 
clam/amavis and the mail doesn't get trough. But I do want a 
notification mail to be sent to the user. This doesn't happen.

The messages I get from Amavis debug output:

lookup: (scalar) matches, result="[EMAIL PROTECTED]"
Apr 19 17:11:48 blabla.xs4all.nl amavisd[403]: (00403-03) TROUBLE in 
check_mail: virus_or_banned quar+notif FAILED: can't build entity: no 
body, and not multipart at /usr/local/sbin/amavisd line 4700,  
line 79.

Looks like a perl error? I upgraded perl to 5.6.1 and recompiled Amavis 
+ dependencies from ports. But I still get these errors. Running FreeBSD 
4.8 - Security (using freebsd-update).

Anyone who saw this error before? I looked in the amavisd code, but that 
didn't help me much.

With kind regards,

Richard Zoontjens.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: amavisd-new errors after portupgrade

2004-03-22 Thread Jeff Maxwell
Yes, apparently P8 is not compatible with early versions of perl.

On Mar 22, 2004, at 2:35 AM, Leo Lapousterle wrote:

On 21/03/04 22:09 -0500, Jeff Maxwell wrote :

The same thing just happened to me.
amavisd-new, the newest version will not run with perl 5.005 that 
comes
with 4.9. You have upgrade to perl 5.6 or better. I upgrading to 5.8 
with
the port /usr/ports/lang/perl5.8/
Errr, I upgraded to amavisd-new(p8) yesterday without any problems.
Was it the p8 version for you too ?
--
Léo Lapousterle
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
"[EMAIL PROTECTED]"


Jeff Maxwell
POS Department Manager
Uni-Marts, Inc.
508 Blackman St
Wilkes-Barre, PA 18702
570-829-0888
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: amavisd-new errors after portupgrade

2004-03-21 Thread Leo Lapousterle
On 21/03/04 22:09 -0500, Jeff Maxwell wrote :

> The same thing just happened to me.
> amavisd-new, the newest version will not run with perl 5.005 that comes
> with 4.9. You have upgrade to perl 5.6 or better. I upgrading to 5.8 with
> the port /usr/ports/lang/perl5.8/

Errr, I upgraded to amavisd-new(p8) yesterday without any problems.
Was it the p8 version for you too ?


-- 
Léo Lapousterle
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: amavisd-new errors after portupgrade

2004-03-21 Thread Jeff Maxwell
The same thing just happened to me.

amavisd-new, the newest version will not run with perl 5.005 that comes 
with 4.9. You have upgrade to perl 5.6 or better. I upgrading to 5.8 
with the port /usr/ports/lang/perl5.8/

Follow the directions to change you default perl installation after you 
install the port. You then have to install all the missing modules.

It took me a couple of hours to get it back up, but it works great now.



On Mar 21, 2004, at 8:26 PM, albi wrote:



here's the error with the upgraded amavisd-new :

/usr/local/etc/rc.d/amavisd.sh restart
Stopping amavisd.
Waiting for PIDS: 976.
Starting amavisd.
ERROR: MISSING REQUIRED BASIC MODULES:
  Carp::Heavy
BEGIN failed--compilation aborted at /usr/local/sbin/amavisd line 124.
after using Google for a while i couldn't find which port "Carp::Heavy"
comes from (or should come from)
copying back the previous /usr/local/sbin/amavisd over the new one,
makes it work OK
any ideas how to resolve this (that is, make the newer amavisd-new 
work)

tia!

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
"[EMAIL PROTECTED]"


Jeff Maxwell
POS Department Manager
Uni-Marts, Inc.
508 Blackman St
Wilkes-Barre, PA 18702
570-829-0888
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


amavisd-new errors after portupgrade

2004-03-21 Thread albi


here's the error with the upgraded amavisd-new :

/usr/local/etc/rc.d/amavisd.sh restart
Stopping amavisd.
Waiting for PIDS: 976.
Starting amavisd.
ERROR: MISSING REQUIRED BASIC MODULES:
  Carp::Heavy
BEGIN failed--compilation aborted at /usr/local/sbin/amavisd line 124.

after using Google for a while i couldn't find which port "Carp::Heavy"
comes from (or should come from)

copying back the previous /usr/local/sbin/amavisd over the new one,
makes it work OK

any ideas how to resolve this (that is, make the newer amavisd-new work)

tia!

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


amavisd-new errors after upgrade

2004-03-17 Thread Jeff Maxwell
I had amavisd running for just over one month. I just upgraded and now it 
wont run.

This is the error that I get:
mercury# /usr/local/sbin/amavisd debug
ERROR: MISSING REQUIRED BASIC MODULES:
  Carp::Heavy
BEGIN failed--compilation aborted at /usr/local/sbin/amavisd line 124.
I searched cpan and found some items but not that

Jeff Maxwell
POS Department Manager
Uni-Marts, Inc.
Voice   570-829-0888 Ext. 421
Fax 570-829-4390
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"