The following is a rather unhelpful bounce message.
In case you are wondering, the recipient address was directed to a pipe
transport, that generated a EX_TEMPFAIL every time it was attempted. Even
though I have "log_output", and "return_fail_output" set in the transport,
the output of the command does not attached if retry timeout is exceeded.
Also, the enclosed messages "Retry time not yet reached", and "message
retry timeout exceeded" are misleading at best, and at worst,
contradictory. Should the "Retry time not yet reached" bit even be
attached? It is mainly an internal message, right?
Is their anything I can do about this?
Tom
---------- Forwarded message ----------
Date: Sat, 4 Oct 1997 21:54:27 -0700
From: Mail Delivery System <Mailer-Daemon@???>
To: tom@???
Subject: Mail delivery failed: returning message to sender
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to all of its recipients. The
following address(es) failed:
dave@???:
Retry time not yet reached:
message retry timeout exceeded
------ This is a copy of the message, including all the headers. ------
Return-path: <tom@???>
Received: from tom by misery.sdf.com with local (Exim 1.71 #1)
id 0xGGYx-0001uy-00; Tue, 30 Sep 1997 21:39:03 -0700
To: dave@???
Subject: Test
Message-Id: <E0xGGYx-0001uy-00@???>
From: Tom <tom@???>
Date: Tue, 30 Sep 1997 21:39:03 -0700
test
--
* This is sent by the exim-users mailing list. To unsubscribe send a
mail with subject "unsubscribe" to exim-users-request@???
* Exim information can be found at http://www.exim.org/
