Sam Varshavchik wrote:
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?
I guess I don't understand why that's a problem. If courier happens to know that the two original addresses have the same destination, and decides not to only list that destination in the recipients file, what breaks?
Any resulting DSN will report a one of the addresses only, not both.
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.
Sounds OK to me. I expect that I'm not grasping what you're trying to tell me.
If the forward address bounced, the bounce should read:
Final-Recipient: rfc822; [EMAIL PROTECTED] Original-Recipient: rfc822; [EMAIL PROTECTED] Action: failed Status: 5.0.0 Diagnostic-Code: unknown; mailbox not found.
Final-Recipient: rfc822; [EMAIL PROTECTED] Original-Recipient: rfc822; [EMAIL PROTECTED] Action: failed Status: 5.0.0 Diagnostic-Code: unknown; mailbox not found.
The sender's mail agent would then know that both [EMAIL PROTECTED], and [EMAIL PROTECTED] bounced (both recipient addresses had the same forward address, which bounced).
If one of the address is eliminated, the DSN would only record a bounce for one of the two original recipients, and the sender's mail agent would believe (probably temporarily) that the other recipient did go through.
With DSN you have some kind of an assurance -- as best of an assurance as the unreliable SMTP delivery mechanism can provide -- that the message is either going to go through, or the message bounced, or the message went to a relay that does not support DSNs. In this somewhat pathological case the sending agent would not receive any notification for the other forwarding address, and has no reason to suspect that the message to that address did not go through.
pgp00000.pgp
Description: PGP signature
