Gerald Galster via Postfix-users:
>
> > Wietse Venema via Postfix-users:
> >> I'll add some logging for the case that a bounce message
> >> is rejected for whatever reason.
> >>
> >> But this won't reach Postfix 3.5.25.
> >
> > Quick experiment:
> >
> > Dec 10 14:40:00 wzv postfix/cleanup[330595]: 4dRQzN6pXBzVHYR:
> > message-id=<4dRQzN6pXBzVHYR...
> > Dec 10 14:40:00 wzv postfix/qmgr[330587]: 4dRQzN6pXBzVHYR: from=<...
> > Dec 10 14:40:03 wzv postfix/smtp[330599]: 4dRQzN6pXBzVHYR:
> > to=<doesnotexist@...
> > Dec 10 14:40:03 wzv postfix/bounce[330605]: 4dRQzN6pXBzVHYR: sender
> > non-delivery notification: message content rejected
> > Dec 10 14:40:03 wzv postfix/qmgr[330587]: 4dRQzN6pXBzVHYR: status=deferred
> > (bounce failed)
> >
> > For this experiment I repurposed the existing logging:
> >
> > old-queueid: sender non-delivery notification: new-queueid
>
> Can you implement that in a backwards compatible way, as it may
> break mailflow applications that parse queue-ids to track bounces?
Please clarify. For this specific case, Postfix has never logged
a bounce message queue ID.
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
