Re: problem confirming delivery of a deferred message in PostFix logs

2018-03-28 Thread Viktor Dukhovni
> On Mar 28, 2018, at 1:15 PM, /dev/rob0 wrote: > > If/when 745EC6AC49 is finally delivered or permanently bounced for > some reason such as maximal_queue_lifetime, the queue ID will be > mentioned in logs describing the final disposition. The queue file was deleted when virtual expansion fa

Re: problem confirming delivery of a deferred message in PostFix logs

2018-03-28 Thread /dev/rob0
On Wed, Mar 28, 2018 at 02:16:47PM +, l carr wrote: > Our other question is there a way to link the error message in > the logs to the original message that was deferred. The queue ID is always logged after it has been assigned. Also set enable_long_queue_ids = yes in any supported Postfi

Re: problem confirming delivery of a deferred message in PostFix logs

2018-03-28 Thread l carr
temp fail even when we remove the soft bounce. many thanks again, =lc From: owner-postfix-us...@postfix.org on behalf of Wietse Venema Sent: Wednesday, March 28, 2018 8:55 AM To: Postfix users Subject: Re: problem confirming delivery of a deferred message in PostFi

Re: problem confirming delivery of a deferred message in PostFix logs

2018-03-28 Thread Wietse Venema
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