Closed
Bug 1292364
Opened 9 years ago
Closed 8 years ago
Since jsmime.js, no longer possible to use Disposition-Notification-To in mail.compose.other.header (port bug 1250376 to SeaMonkey)
Categories
(SeaMonkey :: MailNews: Composition, defect)
Tracking
(seamonkey2.45 fixed, seamonkey2.46 fixed, seamonkey2.47 fixed, seamonkey2.48 fixed)
RESOLVED
FIXED
seamonkey2.48
People
(Reporter: rsx11m.pub, Assigned: rsx11m.pub)
References
Details
(Keywords: regression)
Attachments
(1 file)
1.49 KB,
patch
|
philip.chee
:
review+
iannbugzilla
:
approval-comm-aurora+
iannbugzilla
:
approval-comm-beta+
iannbugzilla
:
approval-comm-release+
|
Details | Diff | Splinter Review |
+++ This bug was initially created as a clone of Bug #1250376 +++
A long, long time ago, in a galaxy before jsmime.js was integrated into the mail composition code path, I provided these instructions to the users of my Send Later add-on for how to add a Disposition-Notification-To header manually to outgoing messages:
1. Open the Thunderbird options dialog with Tools > Options… or Edit > Preferences…
2. Click “Advanced” and then “Config Editor…” and click the “I’ll be careful, I promise!” button if it asks you to.
3. Enter “mail.compose.other.header” in the filter box.
4. Double-click on the mail.compose.other.header setting and set it to “Disposition-Notification-To”. If it already has a non-empty value, add a comma and then “Disposition-Notification-To” to the end of it.
5. Quit from and restart Thunderbird.
6. When you are composing a message for which you want a return receipt and which you want to schedule to be sent later, then click on an empty line in the message header in the compose window, select “Disposition-Notification-To” in the drop-down, and then enter your email address as the value of the header.
This worked just fine. Now, it does not. When you follow step 6 above and then try to save the resulting draft, you get this:
JavaScript error: resource:///modules/jsmime.jsm -> resource:///modules/jsmime/jsmime.js, line 3074: TypeError: invalid 'in' operand addr
I don't know if the attached patch is the _correct_ fix to this problem (in fact, I'd wager good money it isn't), but it works, and at least points to the source of the problem.
I suspect bug 1180209 may be related to this.
Assignee: nobody → rsx11m.pub
Status: NEW → ASSIGNED
Attachment #8778000 -
Flags: review?(philip.chee)
![]() |
||
Comment 2•8 years ago
|
||
Comment on attachment 8778000 [details] [diff] [review]
One-line patch
a=me for checkin
Attachment #8778000 -
Flags: review?(philip.chee) → review+
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
status-seamonkey2.45:
--- → affected
status-seamonkey2.46:
--- → affected
status-seamonkey2.47:
--- → affected
status-seamonkey2.48:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.48
Comment on attachment 8778000 [details] [diff] [review]
One-line patch
[Approval Request Comment]
Regression caused by (bug #): JS Mime
User impact if declined: custom headers aren't available in composition window
Testing completed (on m-c, etc.): works on c-c, landed on c-esr45 for Thunderbird
Risk to taking this patch (and alternatives if risky): low
String changes made by this patch: none
Attachment #8778000 -
Flags: approval-comm-release?
Attachment #8778000 -
Flags: approval-comm-beta?
Attachment #8778000 -
Flags: approval-comm-aurora?
Comment on attachment 8778000 [details] [diff] [review]
One-line patch
a=me
Attachment #8778000 -
Flags: approval-comm-release?
Attachment #8778000 -
Flags: approval-comm-release+
Attachment #8778000 -
Flags: approval-comm-beta?
Attachment #8778000 -
Flags: approval-comm-beta+
Attachment #8778000 -
Flags: approval-comm-aurora?
Attachment #8778000 -
Flags: approval-comm-aurora+
You need to log in
before you can comment on or make changes to this bug.
Description
•