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

Status: RESOLVED DUPLICATE of bug 154014

(SeaMonkey :: MailNews: Backend, defect)

Description

[Andreas Troschka]

PSE see (fixed) Bug #154014

As seen in the referenced bug, who receives a Disposition-Notification must be
able to distinguish (and act consequently) when the sender uses different
addresses for inbound and outbound.
 
This new Bug is related to the other peer (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...

Andreas Troschka.

Comment 1

[Jo Hermans]

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

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.