From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <aafb68ba6e0fa33801e9c06b8c5ad4dd@plan9.bell-labs.com>
From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Failure notice by smtp
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="upas-gqepfulhjmpybcqbqgzljzvrma"
Date: Mon, 10 Nov 2003 10:31:28 -0500
Topicbox-Message-UUID: 84ebceb4-eacc-11e9-9e20-41e7f4b1d025

This is a multi-part message in MIME format.
--upas-gqepfulhjmpybcqbqgzljzvrma
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

I just looked at the dates a little more closely.  For runq to remove the mail
the same day that it was delivered implies that it thought that the mail
was successfully delivered (or that the clock on the file server is 3 days
off).

The fact that the message was removed without an accompanying smtp.fail message
with the same timestamp implies that the smtp succeeded.  However, there should
have been a log entry in smtp should that have been true.  Your original
message shows:

#
#	Looking /sys/log/smtp we can confirm these two mails have not been delivered
#
term% tail smtp
...
term%

I'm not sure what this means, but I'm assuming it means that there was
nothing in the smtp log?  This is all just a bit wierd.  Have you changed
the /mail/lib/remotemail script?  It really looks like the script did not
return an error code as if the smtp had succeeded.

If there is inded nothing in /mail/lib/smtp, it sounds like either the
remotemail script is broken or smtp is.  Either way, I think you need to
start debugging.
--upas-gqepfulhjmpybcqbqgzljzvrma
Content-Type: message/rfc822
Content-Disposition: inline