And this time, only one recipient is added to the message, as it should be. I'm not sure what the proper fix is, since I'm not clear on why the DSN options would affect how you look for duplicates. I'm also not sure why you'd ever bother to consider the original recipient when looking for duplicates in the list of actual recipients.
I'm beginning to remember how this logic was worked out. This stuff goes back a couple of years.
You can have a situation where the original message was addressed to different recipients, but each one forwarded the message to the same forwarding address.
Although 99.9% of the time this situation simply results in two copies of the same message coming in, one from each forward, theoretically it's possible that -- depending on the addresses involved, and the intermediate mail relay logic, you can end up with both forwards coming in as a single message, with two RCPT TO: addresses naming the same recipient address, but a different original recipient address. Now what?
Drop one of them as a dupe? Can't do that. What if you'll end up forwarding this message? You received it with two RCPT TO: addresseses, and a different original recipient address, and after forwarding you're going to send a single RCPT TO: address, with whatever was the original recipient address in the first RCPT TO: statement. That definitely doesn't sound right.
In any case, I hope that clarifies why it's happening, and I don't expect that fixing the problem will prove difficult.
Technically, no. But logically, the question is whether you really want to do it. For simple, local alias, the answer is pretty clear. It's more murky when external aliasing enters the picture.
pgp00000.pgp
Description: PGP signature
