Thanks for the suggestion on using proxy:ldap, we will look into that. We
already believed the LDAP error was an issue at the LDAP side, or communication
to the LDAP server, and not an issue with how Postfix was working. We were just
trying to get a little more information on what Postfix was seeing when it
connected to the LDAP, to assist with troubleshooting on the LDAP side. (thus
the LDAP log question.)
Our other question is there a way to link the error message in the logs to the
original message that was deferred. (Even if it requires turning on additional
logging.)
As it is logged currently, there doesn't appear to be a unique value that we
could key on that is provided in both the error log entry and the message log
entry. So we can only 'assume' the message was re-delivered successfully by
searching the logs for an email from the same sender, to the same recipient,
after the error occurred.
As for the actual error transaction itself,
> In: DATA
> Out: 354 End data with <CR><LF>.<CR><LF>
> Out: 451 4.3.0 Error: queue file write error
that all makes perfect sense to us.
And thanks for confirming that the error will continue to be treated as a temp
fail even when we remove the soft bounce.
many thanks again,
=lc
________________________________
From: owner-postfix-us...@postfix.org <owner-postfix-us...@postfix.org> on
behalf of Wietse Venema <wie...@porcupine.org>
Sent: Wednesday, March 28, 2018 8:55 AM
To: Postfix users
Subject: Re: problem confirming delivery of a deferred message in PostFix logs
l carr:
> Mar 27 16:20:54 redactedServer postfix/cleanup[24237]: warning:
> ldap:/etc/postfix/ldap-aliases.cf lookup error for "redacted@domain"
> Mar 27 16:20:54 redactedServer postfix/cleanup[24237]: warning: 745EC6AC49:
> virtual_alias_maps map lookup problem for redacted@domain -- deferring
> delivery
And:
> In: DATA
> Out: 354 End data with <CR><LF>.<CR><LF>
> Out: 451 4.3.0 Error: queue file write error
The mail delivery transaction failed due to some LDAP error, therefore
Postfix replied with a 451 (try again alter) status. Postfix removed
the queue file because the transaction failed. This is how SMTP works.
It's up to system administrator to fix the LDAP error, and it is
up to the client to resend the message.
To fix the LDAP error, I suggest that you use "proxy:ldap:" instead
of "ldap:". This reduces the number of concurrent connections to the
LDAP server.
As the error message says, "deferring delivery", this will defer
delivery (the soft-bounce safety net is implemented elsewhere).
Wietse
