For example, ip address of the mail server and the mail server hostname should be handled correctly. email@example.com should be treated as within the same domain firstname.lastname@example.org if myhostname.domail.com ip address is 192.168.1.111. Other cases of hostname aliases should be handled too.
Depends on: 134040
No longer depends on: 134040
Can you give an example of how this would show up?
hmm I tried sending a mesg with to prompt of: email@example.com (example) and I came back with error mesg from the server "invalid address syntax" The ip number I used was ip # from nslookup of that particular computer hosting that mail server. Also tried send an email from a test mail server to nsmail-1 (aka judge) and it worked and I got the return recepit back: This is a Return Receipt for the mail that you sent to firstname.lastname@example.org. Note: This Return Receipt only acknowledges that the message was displayed on the recipient's computer. There is no guarantee that the recipient has read or understood the message contents. Reporting-UA: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.9+) Gecko/20020325 Final-Recipient: rfc822; email@example.com Original-Message-ID: <3CA3AD83.firstname.lastname@example.org> Disposition: manual-action/MDN-sent-manually; displayed Final part was the header of the original mesg (which I didn't include)
Status: NEW → ASSIGNED
I guess this would be more easier to set it up on a linux machine. Try to create an account on a linux machine and then create a few alias for the machine. Then send mail messages with request for return receipt to user@alias1, user@alias2, and user@machine. Some MTA may masquerade user's address too.
How many people are likely to run into this?
Very rarely. May be academic users are more prone for this kind of problems.
moving to future.
Target Milestone: --- → Future
Summary: MDN report generation should be able to handle host name aliases → MDN: report generation should be able to handle host name aliases
Assignee: jt95070 → nobody
Status: ASSIGNED → NEW
QA Contact: grylchan → backend
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.