Joe Maimon wrote:
I have been having the same as well.
I added some more verbosity into the syslog statement and got this logged
write failure to clamd, nbytes: -1, quarantine_dir: (null), error: Bad
file descriptor
Any ideas?
OK I think I know what the problem is. Large attachments.
this
Joe Maimon wrote:
Joe Maimon wrote:
I have been having the same as well.
I added some more verbosity into the syslog statement and got this
logged
write failure to clamd, nbytes: -1, quarantine_dir: (null), error:
Bad file descriptor
Any ideas?
OK I think I know what the problem is.
The evidence points to incoming connections taking a long time (minutes) to send the
first
line of header after establishing a connection.so clamd gives up waiting. Increasing
clamd's timeout
will help. I have seen 4-5 minutes between an SMTP connection being established and
the conversation
On Fri, 2004-03-26 at 15:44, Nigel Horne wrote:
The evidence points to incoming connections taking a long time (minutes) to send the
first
line of header after establishing a connection.so clamd gives up waiting. Increasing
clamd's timeout
will help. I have seen 4-5 minutes between an SMTP
Nigel Horne wrote:
The evidence points to incoming connections taking a long time (minutes) to send the
first
line of header after establishing a connection.so clamd gives up waiting. Increasing
clamd's timeout
will help. I have seen 4-5 minutes between an SMTP connection being established
Trog wrote:
On Fri, 2004-03-26 at 15:44, Nigel Horne wrote:
The evidence points to incoming connections taking a long time (minutes) to send the
first
line of header after establishing a connection.so clamd gives up waiting. Increasing
clamd's timeout
will help. I have seen 4-5 minutes
On Fri, 2004-03-26 at 17:03, Joe Maimon wrote:
# Thread (scanner - single task) will be stopped after this time (seconds).
# Default is 180. Value of 0 disables the timeout. SECURITY HINT:
Increase the
# timeout instead of disabling it.
ThreadTimeout 600
Still happening.
Besides
Trog wrote:
On Fri, 2004-03-26 at 17:03, Joe Maimon wrote:
# Thread (scanner - single task) will be stopped after this time (seconds).
# Default is 180. Value of 0 disables the timeout. SECURITY HINT:
Increase the
# timeout instead of disabling it.
ThreadTimeout 600
Still happening.
On Fri, 26 Mar 2004, Joe Maimon wrote:
Nigel Horne wrote:
The evidence points to incoming connections taking a long time (minutes) to send
the first
line of header after establishing a connection.so clamd gives up waiting.
Increasing clamd's timeout
will help. I have seen 4-5 minutes
I have been having the same as well.
I added some more verbosity into the syslog statement and got this logged
write failure to clamd, nbytes: -1, quarantine_dir: (null), error: Bad
file descriptor
Any ideas?
---
This SF.Net email is
Hi,
when i receive bigger mails i got the folowing error:
reject=451 4.7.1 Please try again later
please help !
thank u
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and
On Fri, 19 Mar 2004, Andrei Bucur wrote:
when i receive bigger mails i got the folowing error:
reject=451 4.7.1 Please try again later
I can see same things in my logs. It's sendmail
8.12.10+clamd+clamav-milter v 0.70-rc on Solaris9 (sparc).
It happens only for few sender adresses (always the
Mar 19 13:37:36 topaz clamav-milter[17382]: [ID 910239 mail.error] write
failure to clamd
That reads to me that clamd has gone away
-Nigel
--
Nigel Horne. Arranger, Composer, Typesetter.
NJH Music, Barnsley, UK. ICQ#20252325
[EMAIL PROTECTED] http://www.bandsman.co.uk
On Friday 19 March 2004 16:12, Andrei Bucur wrote:
when i receive bigger mails i got the folowing error:
reject=451 4.7.1 Please try again later
please help !
I write about it 25/02/2004 10:56. I not set purpose to check
all mails and I use --dont-scan-on-error
--
Regards,
Sergey
4.7.1 Please try again later
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http
I was seeing those to, they seem to go with a message:
clamav-milter[55529]: write failure to clamd
I added --dont-scan-on-error to the clamav-milter args, which stopped
the rejections, but obviously doesn't solve the underlying problem.
MaxThreads is 1000 and MaxConnectionQueueLength 100
On Fri, 19 Mar 2004, Nigel Horne wrote:
Mar 19 13:37:36 topaz clamav-milter[17382]: [ID 910239 mail.error] write
failure to clamd
That reads to me that clamd has gone away
No, it's still alive, as I said, next mails are received properly.
Andrei Bucur says the same.
On Fri, 19 Mar 2004 22:48:05 +0100 (CET)
Krzysztof Snopek [EMAIL PROTECTED] wrote:
On Fri, 19 Mar 2004, Nigel Horne wrote:
Mar 19 13:37:36 topaz clamav-milter[17382]: [ID 910239 mail.error]
write failure to clamd
That reads to me that clamd has gone away
No, it's still alive, as
18 matches
Mail list logo
