129416 - MDN: report generation should be able to handle host name aliases

Status: NEW

(MailNews Core :: Backend, defect)

Description

[Jeff Tsai]

For example, ip address of the mail server and the mail server hostname should
be handled correctly. user@192.168.1.111 should be treated as within the same
domain [e-mail] if myhostname.domail.com ip address is
192.168.1.111. Other cases of hostname aliases should be handled too.

Comment 1

[scottputterman]

Can you give an example of how this would show up?

Comment 2

[grylchan]

hmm I tried sending a mesg with to prompt of:
  gchan@123.456.789 (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  [e-mail].

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; [e-mail]
Original-Message-ID: <[e-mail]>
Disposition: manual-action/MDN-sent-manually; displayed

Final part was the header of the original mesg (which I didn't include)

Comment 3

[Jeff Tsai]

Accepting ...

Comment 4

[Jeff Tsai]

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.

Comment 5

[scottputterman]

How many people are likely to run into this?

Comment 6

[Jeff Tsai]

Very rarely. May be academic users are more prone for this kind of problems. 

Comment 7

[scottputterman]

moving to future.