5 messages in net.sourceforge.lists.courier-users[courier-users] Re: Invalid argument?
FromSent OnAttachments
Alexei Batyr'Mar 11, 2001 8:11 am 
Alexei Batyr'Mar 11, 2001 12:15 pm 
Alexei Batyr'Mar 12, 2001 1:14 am 
Sam VarshavchikMar 12, 2001 4:47 am 
Alexei Batyr'Mar 12, 2001 7:52 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Re: Invalid argument?Actions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Mar 12, 2001 4:47:09 am
List:net.sourceforge.lists.courier-users

Alexei Batyr' writes:

Sam Varshavchik writes:

On Sun, 11 Mar 2001, Alexei Batyr' wrote:

Sam Varshavchik writes:

When Courier is sending or receiving mail from them?

Yes.

Which one?

Sometimes when sending and sometimes when receiving.

0.32.0 of 28.02.01, but there was no significant changes in that respect in comparison with previous versions. Looks like these overloaded servers introduce some delays in ESMTP communication with courier and its reaction is not always adequate. Unfortunately it's very difficult to catch these situations - they are absolutely stochastic.

I'm wondering if Courier times out while sending mail to them, the socket gets closed, but then, for some reason, it tries to write something to the closed socket...

Could you advise me how to find out what really happens?

stracing the process is really the only way. You could attach strace to the listening couriertcpd process, with the -f flag. Then, once something got deferred, stop the trace and go back and find the actual process in the log.

Make sure you have plenty of disk space.