Hi, Indeed I was a bit unclear.
Okay, so the thing with DSN's is this: if my email client requests a DSN on success when sending a mail, my Postfix server will honour that request. Postfix does this in one of two possible ways: 1. either the remote mail server indicates that it offers DSN capability; in this case my mail server will relay the request and leave it at that. 2. or the remote mail server does not indicate such capability; in this case my mail server will create the DSN itself. The problem with #1 is, that even though some mail servers do indicate DSN capability, they don't always actually send a DSN. Or they try to but something goes wrong, you name it. So in that case my email client never sees a DSN. Even though the original email was relayed to a remote mail server just fine and/or even correctly arrived at its destination. It would be swell if my mail server would notice the absent DSN after a while and create one with the original details of the relay. I understand that this is a very stateful and rather complex feature, so I don't suppose this is easily done. However a workaround could be for my mail server to simply always create a DSN if a client requests it, regardless of the capabilities of a remote mail server. The downside of such a workaround is that a client may receive two DSN's - in fact they usually will. However for a client who thinks two DSN's is better than zero, this would be a nice feature. Is this possible? Kind regards, Erik Logtenberg. On 04/23/2014 05:33 PM, Michael Storz wrote: > Am 2014-04-23 13:39, schrieb Erik Logtenberg: >> Hi, >> >> If I request a (success) DSN from my Postfix server, my server responds >> as expected. Usually my mail server has to deliver the mail remotely and >> I would like Postfix to request a DSN from the remote server as well if >> the user asked for one. Is that possible? >> >> Kind regards, >> >> Erik. > > Do you mean, > > - you are sending to a remote address or > - you are sending to a "local" address which is then forwarded to a > remote address? > > In the first case the request for a success DSN ist transmitted to the > next MTA in case it offers DSN capability. If not, your Postfix > generates a success DSN with action relayed. > > In the second case it seems that Postfix strictly implements "the > confidentiality of a forwarding address" without any user/administrator > choice in opposit to what RFC 3464 says > > MTA authors are encouraged to provide a mechanism which enables the > end user to preserve the confidentiality of a forwarding address. > Depending on the degree of confidentiality required, and the nature > of the environment to which a message were being forwarded, this > might be accomplished by one or more of: > > ... >
