On Wed, Jul 12, 2017 at 10:55:29AM -0400, Viktor Dukhovni wrote:
> That is not how Postfix generally works. No further information is possible
> without the relevant logs, and any relevant transport table and master.cf
> settings.
>
> [...]
>
> "unknown mail transport error" is a serious problem, which indicates a
> delivery agent crash or similar failure to report delivery status to the
> queue manager. You will find the cause in your logs:
>
> http://www.postfix.org/DEBUG_README.html#logging
On Thu, Jul 13, 2017 at 03:01:43AM -0700, Tom Hudson wrote:
> I've attached our master.cf file to this message.
>
> [...]
>
> Below is an example error message I am seeing in our postfix mail logs.
No, that's not the logging of the actual problem, that is logging
from the "postfix/smtp" (not "postfix/smtpd") process that crashed
while attempting delivery, and "postfix/master" reporting an abnormal
exit from an "smtp" process.
Without the relevant logs, no further help is possible.
> Jul 12 17:18:21 mes-l2-rly-01 postfix/error[21315]: 2412B80170667:
> to=<REDACTED>, relay=none, delay=92009, delays=92009/0/0/0, dsn=4.3.0,
> status=deferred (unknown mail transport error)
This is just a symptom of the fact that mail to the destination is
subsequently deferred.
> Let me know if you need anything else.
# ### #### #####
# # # # # # #
# # # # #
# # # # #
# # # # #####
# # # # #### #
# # # # # #
# # # # # # #
####### ### #### #####
--
Viktor.
