Closed
Bug 361744
Opened 19 years ago
Closed 19 years ago
Return Receipt request is lost when using SendLater features
Categories
(SeaMonkey :: MailNews: Backend, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
seamonkey1.1final
People
(Reporter: sgautherie, Assigned: Bienvenu)
References
(Blocks 1 open bug)
Details
(Keywords: dataloss, regression, Whiteboard: [regression timeframe: MAS v1.7.13 <-> SM v1.0.6])
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.1.1pre) Gecko/20061123 SeaMonkey/1.1b] (nightly) (W98SE)
I'm doing some tests on 1.8 branch, so without the recent (cleanup) patch from bug 131190.
(I can't use "recent" Trunk builds on W98.)
[The following quotes are from that bug.]
I send a msg to me:
it has
[
Disposition-Notification-To: Serge Gautherie <gautheri@noos.fr>
]
which looks fine.
(In reply to comment #3)
> It turns out that it's not a problem because we already have the final header
> generated.
I use the SendLater feature:
[
X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=0; uuencode=0
]
and no "final header": the RR request has already been lost;
nonetheless, I actually send it: no "Disposition-Notification-To:" header.
Then, the RR+SendLater feature seems broken (= dataloss) in the first place :-/
(May be a regression sometime after that 2002 comment ??)
(In reply to comment #11)
> looks OK, as long as drafts that are sent later still request mdn properly.
Saving a message as Draft:
[
X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=1; uuencode=0
]
which looks fine.
But double-click to edit it further:
the UI/menu does not show the checkmark;
and if I save it again
[
X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=0; uuencode=0
]
the RR request has actually been lost too.
Then, the RR+SaveAsDraft seems broken/dataloss too.
Reporter | ||
Comment 1•19 years ago
|
||
This regressed between MAS v1.7.13 and SM v1.0.6:
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.0.8) Gecko/20061030 SeaMonkey/1.0.6] (release) (W98SE)
Bug already there.
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.13) Gecko/20060414] (release) (W98SE)
[
Disposition-Notification-To: Serge Gautherie <gautheri@noos.fr>
X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=1; uuencode=0
]
which looks fine.
[Netscape® Communicator 4.8 : en-20020722] (W98SE)
[
Disposition-Notification-To: Serge GAUTHERIE <gautheri@noos.fr>
X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=2; uuencode=0; html=0; linewidth=0
]
which looks fine.
Flags: blocking-seamonkey1.1?
Flags: blocking-seamonkey1.0.7?
Keywords: 4xp,
regression
Summary: Return Receipt request is lost when using SaveAsDraft or SendLater features → Return Receipt request is lost when using SendLater features
Version: 1.8 Branch → Trunk
Comment 2•19 years ago
|
||
> I'm doing some tests on 1.8 branch, so without the recent (cleanup)
> patch from bug 131190.
> (I can't use "recent" Trunk builds on W98.)
Erm, are you saying bug 131190 fixed this on trunk?
Reporter | ||
Comment 3•19 years ago
|
||
No, I can't know that: someone else would have to test Trunk builds...
I was saying that that bug couldn't be responsible for the branch regression.
Then, that was confirmed by the comment 1 regression timeframe.
I was also saying that it could be "needed" to test that bug/patch again after fixing this one.
Whiteboard: [regression timeframe: MAS v1.7.13 <-> SM v1.0.6]
Reporter | ||
Comment 4•19 years ago
|
||
I'm lost now.
I tried
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7a) Gecko/20040219] (release) (W98SE)
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b) Gecko/20050217] (release) (W98SE)
which worked fine.
Then I tried
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b4) Gecko/20050910 SeaMonkey/1.0a] (release) (W98SE)
with a first message,
which seemed to have this bug.
Then I tried with a second message,
and since then I can't reproduce with v1.0a / v1.0.6 / v1.1b-current :-<
R.WorksForMe :-/
Status: NEW → RESOLVED
Closed: 19 years ago
Flags: blocking-seamonkey1.1?
Flags: blocking-seamonkey1.0.7?
Resolution: --- → WORKSFORME
Component: MailNews: Return Receipts → MailNews: Backend
QA Contact: return-receipts → offline
You need to log in
before you can comment on or make changes to this bug.
Description
•