| |||||||||||||||||||||||||||||||
|
> Quoting Victor Duchovni <Victor.Duchovni>: > > > On Fri, Jun 15, 2007 at 08:42:45AM +0100, nick wrote: > > > > > maillog.1:Jun 14 10:58:17 hpukhxdmz79 postfix/smtp[10019]: warning: Write failed in network_biopair_interop with errno=104: num_write=-1, > > > provided=4133 > > > > Assuming that your's is a similar Linux system to the one on which I ran > > this Perl one-liner: > > > > $ perl -le '$! = 104; print "$!\n";' > > Connection reset by peer > > > > The problem is that the remote end closed the TCP connection. Note that > > they > > I have no idea how that perl one liner relates to postfix, but yes I get the same message from it as you. Look for "with errno=104: num_write=-1" in the log entry you reported. When the Unix write(2) system call fails, it returns -1 (or sometimes 0) and sets "errno" to a numeric value that indicates the reason. See the write(2) manpage (and lots of others) for detail. -- Viktor. Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the "Reply-To" header. To unsubscribe from the postfix-users list, visit http://www.postfix.org/lists.html or click the link below: <mailto:majordomo?body=unsubscribe%20postfix-users> If my response solves your problem, the best way to thank me is to not send an "it worked, thanks" follow-up. If you must respond, please put "It worked, thanks" in the "Subject" so I can delete these quickly.
| ||||||||||||||||||||||||||||||
© 2004-2008 readlist.com