Hello Wietse, option 1 is actually a pretty good idea - hadn't thought of this. The disadvantage of handling the return mail is that not only bounces are returned but also automatic responders, etc. and thus I would have to parse the content of the email to find out if it is a real bounce. So I think parsing the mail.log is actually much easier...
Options 2 and 3 are interesting ideas as well but - as you said yourself - aren't reliable enough. So in the end I still think a custom field in the mail.log when the bounce is reported would make most sense. Steffen -----Original Message----- From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] On Behalf Of Wietse Venema Sent: Donnerstag, 4. Oktober 2012 14:26 To: Postfix users Subject: Re: AW: How to change queue id? Steffen Schebesta: > If that doesn't work though then maybe I could work around this > problem. I thought about adding the message-id to the bounce message > but that probably Postfix has lots of options to identify a returned message. 1) You can encode the unique identifier in the envelope sender address (as an address extension). This works even when mail is returned by a remote MTA. 2) Your unique Message ID is already returned in the bounce message. See RFC 3462. This may or may not work for mail that is returned by a remote MTA. 3) You can specify your own unique ENVELOPE ID via SMTP (see RFC 3461) or via the Postfix "sendmail -V" option. This ENVELOPE ID is also returned in the bounce message. See RFC 3464. This works only if all MTAs in the forward path implement RFC 3461. I suggest that you study the many RFCs and non-RFC features that Postfix already implements, before tinkering with internals. But first, as Stan mentioned, you should describe your problem, instead of your proposed solutions. There are likely better solutions that already exist. I already mentioned three of them. Wietse
