154014 - Returning recept confirmation fails if Inbound/Outbound addresses are different

Status: NEW

(SeaMonkey :: MailNews: Backend, defect)

Description

[Andreas Troschka]

Suppose:

[e-mail]        his inbound address
[e-mail]   his outbound address

(also good against SPAM!!!)

He sends you an e-mail requesting a reception confirmation.

Now, with such a setup the return receipt function doesn't work correctly!!!

Your receipt confirmation is sent to [e-mail] and he will never
receive mails from his outbound account.

Solution:

It has to be sent to the address specified in his Reply-to: field instead:

[e-mail]

and if no address is specified in this field than, and only than, the address
specified in the sender or return-path fields have to be used (this should be
the last resource!).

Comment 1

[Jeff Tsai]

Attachment: Patch to fix the problem.

Good catch. Here is the patch to fix the problem.

Comment 2

[Jeff Tsai]

Adding putterman and bienvenu to the cc list... David, I put up a patch to fix
the problem. Please review and have someone to check it in. Thanks,

Comment 3

[David :Bienvenu]

Comment on attachment 89081 [details] [diff] [review]
Patch to fix the problem.

sr=bienvenu

Comment 4

[Andreas Troschka]

Patch applied and tests concluded without problems.

Comment 5

[grylchan]

Reopening bug.

Andreas, the patch actually hasn't landed in the trunk yet
so we can't change the status to 'resolve fixed'.

but thanks for testing the patch.

Comment 6

[Andreas Troschka]

Sorry, I'm new to Bugzilla and I don't have the process completely in my hands. 
I apologies for the inconvenient and was short to write you to request the
reopening of the bug, also due to the fact that I'd like to add a vector to the
second side of the medal, Bug 168959, as a completion to this issue.

Andreas.

Comment 7

[Andreas Troschka]

This bug has to be completed also to include the other peer' action (sender of
e-mail with Disposition-Notification).
The sender must be able to specify a different Return-Receipt-To address while
composing his message (willing to set a Disposition-Notification).

This, actually, is not possible in Mozilla due to an incomplete iplementation of
the Mail notification process (see RFC2298 and RFC822).

The process may flow as follows:

a)Open new mail composer
b)Check box "Disposition Notification"
c)Write Destination address(es) in field To: 
d)Approve proposed Return-Receipt-To address(es) (automatically taken from
address book for the destination addresses specified)
d2)Otherwise select from listbox or edit directly
e)compose message and send.

So far...

Comment 8

[Andreas Troschka]

*** Bug 243229 has been marked as a duplicate of this bug. ***

Comment 9

[Tony Mechelynck [:tonymec]]

What is the status of this bug?

No comments since May 2004.

Is the problem still happening?

Jeff, Andreas, are you still working on this?

Comment 10

[Andreas Troschka]

A simple test on T'Bird and other mozilla derived MUAs (as on most MUAs around) shows nothing has been done since I've opened this bug.
You or anybody else are welcome to work on this, and to produce the necessary patches on the actual sources.

Differentiating inbound and outbound mail addresses is still one of the most effective countermeasures against SPAM reception!
It is a shame that the Reception Confirmation protocol part isn't correctly implemented yet.

Comment 11

[Tony Mechelynck [:tonymec]]

Mozilla1.2alpha is long past; retargeting to Future.

Comment 12

[Tony Mechelynck [:tonymec]]

Resetting A+QA as current (nondefault) values seem out-of-date.

Comment 14

[Wayne Mery (:wsmwk)]

is this core backend?