Closed Bug 243229 Opened 20 years ago Closed 20 years ago

Return receipts process cannot work if sender's outbound and inbound addresses don't match

Categories

(Thunderbird :: Preferences, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 154014

People

(Reporter: atroschka, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.2; Linux) (KHTML, like Gecko)
Build Identifier: all

A very limited implementation of the Return-receipt process has been made on 
most MUA including Thunderbird. 
So far I can remember, the RFCs don't specify how to manage this particular 
but very spread case: 
 
.The sender's outbound address doesn't match with his inbound address. 
 
What exactly happens: 
 
Peter uses the address peter.outbond@foo.com for sending his e-mails. 
Peter uses his public address peter.inbound@foo.com for receiving e-mails. 
Jane uses the unique address jane@foo.gov for both sending and receiving 
e-mails. 
 
a. Peter sends an e-mail to Jane with return-receipt request set 
  
peter.outbound@foo.com -------[RR-REQ]---> Jane@foo.gov 
 
b. Jane receives the e-mail and sends the return-receipt back to the 
originating address of Peter's e-mail. But he cannot receive the 
acknoledgement because his inbound address differs from the originating one in 
the e-mail he sent 
 
peter.outbound@foo.com X<-----[RR-ACK]-----Jane@foo.gov 
peter.inbound@foo.com ??? 
 
 
 

Reproducible: Always
Steps to Reproduce:
 
Actual Results:  
 

Expected Results:  
Correct results can be reached if the inbound address can be specified in case 
it differs from the default one. 
An editable field should be added to the "Return-receipts" panel in the 
"Account-Settings" menu. 
 
Another way to reach the same result is to get the destination address for the 
Return-receipts from the "Reply-To:" field (when it is left blank the "From:" 
field address will fit the requirement). 
 
Regards 
 
Andreas Troschka
 

*** This bug has been marked as a duplicate of 154014 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.