Re: [AMaViS-user] (!!)TROUBLE in check_mail, but must continue (1)

2009-06-29 Thread Mark Martinec
Sébastien, > Here is the diff -u from your 2.5.4 source tarball and from my rpm. > I wonder how this could have been changed, I'll ask my teammates why. I > think that is a human mistake, and that is not from rpmforge packagers. > It's seems that with your original code everything is OK. Thanks a

[AMaViS-user] mysql partitioning setup cheat sheet?

2009-06-29 Thread Michael Scheidell
I looked at the readme's and some of the stuff Thomas Gelf wrote about mysql partitioning and amavisd partitioning, and tried a couple of them without much success. Did anyone write a 'setup/ quarantine cleanup' cheat sheet for mysql partitioning and amavisd? -- Michael Scheidell, CTO Phone:

Re: [AMaViS-user] (!!)TROUBLE in check_mail, but must continue (1)

2009-06-29 Thread Sébastien AVELINE
Mark, Here is the diff -u from your 2.5.4 source tarball and from my rpm. I wonder how this could have been changed, I'll ask my teammates why. I think that is a human mistake, and that is not from rpmforge packagers. It's seems that with your original code everything is OK. Thanks a lot for hel

Re: [AMaViS-user] Out of Memory! How?

2009-06-29 Thread The Doctor
On Mon, Jun 29, 2009 at 01:11:14PM +0200, Mark Martinec wrote: > Doctor, > > > su -m clamav -c '/usr/contrib/sbin/amavisd debug' > > Jun 28 22:15:08.330 mail.nk.ca /usr/contrib/sbin/amavisd[18551]: starting. > > /usr/contrib/sbin/amavisd at mail.nk.ca amavisd-new-2.6.3 (20090422), > > Unicod

Re: [AMaViS-user] Out of Memory! How?

2009-06-29 Thread The Doctor
On Mon, Jun 29, 2009 at 06:21:02PM +0900, Jorgen Lundman wrote: > > > You sure it is not just process limit, ulimit/limits depending on your > sehll. > > > Clifton Royston wrote: > > On Sun, Jun 28, 2009 at 10:36:00PM -0600, The Doctor wrote: > >> Right I have > >> > >> su -m clamav -c '/usr/c

Re: [AMaViS-user] (!!)TROUBLE in check_mail, but must continue (1)

2009-06-29 Thread Mark Martinec
Sébastien, > Acutally I run a postfix 2.5.4 and amavisd-new 2.5.4 on a centos 4 box. > We got these error : > /(!!)TROUBLE in check_mail, but must continue (1): main_log_entry > FAILED: Can't use stri > ng ("1") as a HASH ref while "strict refs" in use at /usr/sbin/amavisd > line 3134, line 648.

Re: [AMaViS-user] Out of Memory! How?

2009-06-29 Thread Mark Martinec
Doctor, > su -m clamav -c '/usr/contrib/sbin/amavisd debug' > Jun 28 22:15:08.330 mail.nk.ca /usr/contrib/sbin/amavisd[18551]: starting. > /usr/contrib/sbin/amavisd at mail.nk.ca amavisd-new-2.6.3 (20090422), > Unicode aware > Jun 28 22:15:08.386 mail.nk.ca > /usr/contrib/sbin/amavisd[185

[AMaViS-user] (!!)TROUBLE in check_mail, but must continue (1)

2009-06-29 Thread Sébastien AVELINE
Hello, Acutally I run a postfix 2.5.4 and amavisd-new 2.5.4 on a centos 4 box. We got these error : /(!!)TROUBLE in check_mail, but must continue (1): main_log_entry FAILED: Can't use stri ng ("1") as a HASH ref while "strict refs" in use at /usr/sbin/amavisd line 3134, line 648. /In our logs,

Re: [AMaViS-user] Out of Memory! How?

2009-06-29 Thread Jorgen Lundman
You sure it is not just process limit, ulimit/limits depending on your sehll. Clifton Royston wrote: > On Sun, Jun 28, 2009 at 10:36:00PM -0600, The Doctor wrote: >> Right I have >> >> su -m clamav -c '/usr/contrib/sbin/amavisd debug' >> Jun 28 22:15:08.330 mail.nk.ca /usr/contrib/sbin/amavis

Re: [AMaViS-user] Out of Memory! How?

2009-06-29 Thread Clifton Royston
On Sun, Jun 28, 2009 at 10:36:00PM -0600, The Doctor wrote: > Right I have > > su -m clamav -c '/usr/contrib/sbin/amavisd debug' > Jun 28 22:15:08.330 mail.nk.ca /usr/contrib/sbin/amavisd[18551]: starting. > /usr/contrib/sbin/amavisd at mail.nk.ca amavisd-new-2.6.3 (20090422), Unicode > aware

Re: [AMaViS-user] amavid-release in a sql based environent

2009-06-29 Thread ml
Mark, thanks a lot! > > Seems you have a protocol on a Unix socket set to AM.CL, instead of > AM.PDP. > Add the following to your amavisd.conf: > > $interface_policy{'SOCK'} = 'AM.PDP-SOCK'; that line was commented out. Now it woks. > > $policy_bank{'AM.PDP-SOCK'} = { > protocol => 'AM.PDP',