Closed
Bug 379943
Opened 18 years ago
Closed 18 years ago
MDN : Preference "Always send" doesn't work (when Return-Path missing)
Categories
(Thunderbird :: Preferences, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: eballetbaz, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2
Build Identifier: version 2.0.0.0 (20070507)
For return receipts, default preference "Always Send" doesn't work. When receiving a message with a return receipts, Thunderbird always ask "The sender of this message has asked to be notified ..."
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1•18 years ago
|
||
WFM on linux, tested on an IMAP account, with Always send if outside domain.
Version: unspecified → 2.0
| Reporter | ||
Comment 2•18 years ago
|
||
For information, I tested this on Windows with a POP3 account.
Comment 3•18 years ago
|
||
To BALLET BAZ Eric(bug opener):
Where do you set the option?
A) Tools/Options/Advanced/General/Return Receipts
B) Account Settings/Return Receipts
| Reporter | ||
Comment 4•18 years ago
|
||
In Account Settings/Return Receipts :
I choose "Allow return receipts for some messages"
and set "Aways send" for the three choices...
Comment 5•18 years ago
|
||
To BALLET BAZ Eric(bug opener):
What is set in "Tools/Options/Advanced/General/Return Receipts"?
Do you use Global Inbox for the account?
If yes, changing of the choice at Tools/Options is a warkaround?
(Please don't change settings in Account Settings/Return Receipt when test.)
| Reporter | ||
Comment 6•18 years ago
|
||
I don't use Global Inbox for the account.
In "Tools/Options/Advanced/General/Return Receipts"
I choose "Allow return receipts for some messages"
and set "Aways send" for the three choices...
Comment 7•18 years ago
|
||
Bug 137888 was listed in Dependency tree for meta Bug 134040.
> Pop only: No Return Receipt prompt for newly created folder/filter until quit/restart
This looks to be applicable to "Always", instead of "Ask" only.
To BALLET BAZ Eric(bug opener): Is this the case?
| Reporter | ||
Comment 8•18 years ago
|
||
No it's the opposite ! the prompt always pops up ...
Don't you reproduce this bug ?
Comment 9•18 years ago
|
||
Nope, tried the settings Always send on both global settings and account settings with a pop account. Worked fine.
Was this for the default identity, or?
Comment 10•18 years ago
|
||
(In reply to comment #8)
> No it's the opposite ! the prompt always pops up ...
No, no. My comment was for "until quit/restart" part, not for "promt" part.
Sorry for my unclear question.
| Reporter | ||
Comment 11•18 years ago
|
||
Finally I have found the source of this bug : the nsMsgMdnGenerator class has a function named ValidateReturnPath which looks for an header named "Return-Path".
If this header is not present (which is my case) the automatic reply is disabled.
Comment 12•18 years ago
|
||
How come Return-Path isn't set? I see as first header in all mails.
| Reporter | ||
Comment 13•18 years ago
|
||
Maybe my SMTP server isn't very compliant ...
Comment 14•18 years ago
|
||
RFC clearly says: ( http://www.faqs.org/rfcs/rfc2298.html )
> 2.1 The Disposition-Notification-To Header
>(snip)
> MDNs SHOULD NOT be sent automatically if the address in the
> Disposition-Notification-To header differs from the address in the
> Return-Path header (see RFC 822 [2]). In this case, confirmation
> from the user SHOULD be obtained, if possible. If obtaining consent
> is not possible (e.g., because the user is not online at the time),
> then an MDN SHOULD NOT be sent.
INVALID?
Comment 15•18 years ago
|
||
yes, Thx, WADA - I was pretty sure we were doing that because the RFC said to. Yes, I'd say INVALID.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
Comment 16•18 years ago
|
||
Only a note that Return-Path seems to be missing from a lot (all?) mails received through Exchange (pop).
Summary: MDN : Preference "Always send" doesn't work → MDN : Preference "Always send" doesn't work (when Return-Path missing)
You need to log in
before you can comment on or make changes to this bug.
Description
•