Closed Bug 211703 Opened 22 years ago Closed 15 years ago

Return Receipt occasionally shrinks subject

Categories

(SeaMonkey :: MailNews: Backend, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: nigel.jewell, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 If I send a message to myself with subject=(no subject) and request a return receipt, the return receipt subject is incorrect. So an initial subject of "(no subject)" becomes: "Return Receipt (displayed) - no subject)" Note the missing bracket! Reproducible: Always Steps to Reproduce: 1.Hit compose 2.Type in your email address 3.Ask for a return receipt 4.Hit send 5.Recieve the email 6.Acknowledge the receipt 7.Receive the receipt 8.Look at the subject Actual Results: Return receipt subject incorrect Expected Results: Correct subject, "Return Receipt (displayed) - (no subject)"
confirmed. not really sure where the ) is stripped from the subject the new subject is made at: http://lxr.mozilla.org/mozilla/source/lib/libmsg/msgmdn.cpp#682 where the old subject (m_subject) is inserted perhaps the ) is stripped in strip_continuations: http://lxr.mozilla.org/mozilla/source/lib/libmime/mimehdrs.c#2895 ?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Product: Browser → Seamonkey
Component: MailNews: Return Receipts → MailNews: Backend
QA Contact: grylchan → offline
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Assignee: bienvenu → nobody
QA Contact: offline → mailnews-backend
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.