> I moved to 20050322 CVS version and it's working for 24 hours now, so i hope
> it's solved and looking forward for stable release.
Hi,
still working after 5 days, it seems it's solved...
this is really blocking bug in stable release, are you planning to release a
new one?
thanks,
Jakub
--
--
> >i think you are right. strange is, that as mailq says, these two mails are
> >not
> >mailing list digests, but ordinary emails...
>
> An example was sent to this list, it was a digest with 92 regular messages.
> Perhaps an ordinary message with a lot of sections (attachments, images,
> text
Jakub Suchy wrote:
i think you are right. strange is, that as mailq says, these two mails are not
mailing list digests, but ordinary emails...
An example was sent to this list, it was a digest with 92 regular messages.
Perhaps an ordinary message with a lot of sections (attachments, images, text
> No, it's probably the first reason given by Stephen: long mail list digests
> make clamdscan 0.83 fall into a loop.
>
> When that happens clamscan/clamdscan grab the CPU and you can easily see
> them as the problem. The solution, as Stephen said, is to use a more
> recent version from CVS.
On Mon, 2005-03-21 at 18:39, Renà Berber wrote:
> No, it's probably the first reason given by Stephen: long mail list digests
> make
> clamdscan 0.83 fall into a loop.
No it doesn't. It takes a long time to scan, but it does NOT loop.
___
http://lu
Jakub Suchy wrote:
now we tried to debug clamav again and started it and it works...It's really
strange, because we didn't changed anything in configuration.
Is it possible, that the problem was caused by some malicious mail in mailq?
No, it's probably the first reason given by Stephen: long mail l
Jakub Suchy wrote:
[snip]
Mar 13 06:41:54 service amavis[12311]: (12311-03) Clam Antivirus-clamd: Can't
connect to UNIX socket /var/run/clamav/clamd.ctl: Connection refused, retrying
(2)
"connection refused", but when i check if clamav is running (ps ax | grep
clam), it is...
It might have reached
> >orig_to=, relay=none, delay=357, status=deferred (delivery temporarily
> Is that delay in seconds? Sorry, I'm used to sendmail's way of showing
> delays in time format hh:mm:ss.
yep i think...
> Why do you say "amavis can't connect to clamd"?
Mar 13 06:41:54 service amavis[12311]: (12311-03
Jakub Suchy wrote:
[snip]
Mar 11 16:54:19 service postfix/qmgr[8669]: 9454B1A3660: to=,
orig_to=, relay=none, delay=357, status=deferred (delivery temporarily
suspended: connect to 127.0.0.1 [127.0.0.1]: read timeout)
Is that delay in seconds? Sorry, I'm used to sendmail's way of showing delays
i
