Hi all,

Once in a while I receive an email that stays in the queue of my relay for
days, and cannot be delivered to the internal Exchange server. Mailq reports
'broken pipe', and every morning I receive these kind of messages:

Unusual System Events
=-=-=-=-=-=-=-=-=-=-=
Mar 29 03:24:38 validmst04 sendmail[89198]: m2PFSVuS078681: SYSERR(root):
timeout writing message to valaps04.valid.loc.: Broken pipe
Mar 29 03:24:38 validmst04 kernel: Mar 29 03:24:38 validmst04 sendmail[89198]:
m2PFSVuS078681: SYSERR(root): timeout writing message to valaps04.valid.loc.:
Broken pipe
Mar 29 03:24:38 validmst04 sendmail[89198]: m2PFSVuS078681: 0: fl=0x0,
mode=20666: CHR: dev=255/33554432, ino=26, nlink=1, u/gid=0/0, size=0
Mar 29 03:24:38 validmst04 sendmail[89198]: m2PFSVuS078681: 1: fl=0x1,
mode=20666: CHR: dev=255/33554432, ino=26, nlink=1, u/gid=0/0, size=0
Mar 29 03:24:38 validmst04 sendmail[89198]: m2PFSVuS078681: 2: fl=0x1,
mode=20666: CHR: dev=255/33554432, ino=26, nlink=1, u/gid=0/0, size=0
Mar 29 03:24:38 validmst04 sendmail[89198]: m2PFSVuS078681: 3: fl=0x4002,
mode=100600: dev=0/90, ino=1013068, nlink=1, u/gid=0/1, size=4557
Mar 29 03:24:38 validmst04 sendmail[89198]: m2PFSVuS078681: 4: fl=0x0,
mode=100644: dev=0/85, ino=47446, nlink=1, u/gid=0/0, size=16384
Mar 29 03:24:38 validmst04 sendmail[89198]: m2PFSVuS078681: 5: fl=0x0,
mode=100640: dev=0/85, ino=47427, nlink=1, u/gid=0/0, size=65536
Mar 29 03:24:38 validmst04 sendmail[89198]: m2PFSVuS078681: 6: fl=0x0,
mode=100600: dev=0/90, ino=1012975, nlink=1, u/gid=0/1, size=256723
Mar 29 03:24:38 validmst04 sendmail[89198]: m2PFSVuS078681: 7: fl=0x0,
mode=100644: dev=0/85, ino=47447, nlink=1, u/gid=0/0, size=65536
Mar 29 03:24:38 validmst04 sendmail[89198]: m2PFSVuS078681: 8: fl=0x2,
mode=140666: SOCK localhost->[[UNIX: /var/run/logpriv]]
Mar 29 03:24:38 validmst04 sendmail[89198]: m2PFSVuS078681: 9: fl=0x6,
mode=140444: SOCK (Connection reset by valaps04.valid.loc.)->(Socket is not
connected)
Mar 29 03:24:38 validmst04 sendmail[89198]: m2PFSVuS078681: 10: fl=0x6,
mode=140444: SOCK (Connection reset by valaps04.valid.loc.)->(Socket is not
connected)
Mar 29 03:24:38 validmst04 sendmail[89198]: m2PFSVuS078681: 11: fl=0x0,
mode=100644: dev=0/85, ino=47448, nlink=1, u/gid=0/0, size=16384
Mar 29 03:24:38 validmst04 sendmail[89198]: m2PFSVuS078681: MCI@0x0: NULL

Is this fixable, and if so: how?

Sendmail runs on FreeBSD, together with MimeDefang.

TIA

Peter

--
http://www.boosten.org

Mail: peter at boosten dot org

On Sat, 29 Mar 2008 07:09:44 +0100, Peter Boosten wrote:

> Once in a while I receive an email that stays in the queue of my relay
> for days, and cannot be delivered to the internal Exchange server. Mailq
> reports 'broken pipe', and every morning I receive these kind of
> messages:
....
> Mar 29 03:24:38 validmst04 sendmail[89198]: m2PFSVuS078681: 10: fl=0x6,
> mode=140444: SOCK (Connection reset by valaps04.valid.loc.)->(Socket is
> not connected)
....
> Is this fixable, and if so: how?

Fix the "Exchange server".

Greg Russell <me@privacy.net> wrote:
> On Sat, 29 Mar 2008 07:09:44 +0100, Peter Boosten wrote:
>
>> Once in a while I receive an email that stays in the queue of my relay
>> for days, and cannot be delivered to the internal Exchange server. Mailq
>> reports 'broken pipe', and every morning I receive these kind of
>> messages:
> ...
>> Mar 29 03:24:38 validmst04 sendmail[89198]: m2PFSVuS078681: 10: fl=0x6,
>> mode=140444: SOCK (Connection reset by valaps04.valid.loc.)->(Socket is
>> not connected)
> ...
>> Is this fixable, and if so: how?
>
> Fix the "Exchange server".

Greg, thanks for your answer, although I tast some cynism in your answer.
Why would that Exchange server be doing this, and especially for some, by far
not all emails?

TIA

Peter

--
http://www.boosten.org

Mail: peter at boosten dot org