Closed
Bug 958522
Opened 11 years ago
Closed 11 years ago
The request for the confirmation of receipt does not work.
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 955830
People
(Reporter: u.glombitza, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0 SeaMonkey/2.23 (Beta/Release)
Build ID: 20131210201652
Steps to reproduce:
Sending Emails as usual.
Actual results:
I was wondering why I did not got the confirmation of receipt of my mails of the last days. So I checked it with some colleagues and friends:
The checkbox "always order a confirmation of receipt" (I don't know the exactly English text of this checkbox) is checked but there is no request for a confirmation. This happens with my mails, the mails of my colleagues and friends too. I think - but I'm not sure - it's a problem / bug of the new version (we all using SeaMonkey v2.23).
Expected results:
The recipient of the message should be asked to send a request ...
Comment 2•11 years ago
|
||
This bug is not limited to Windows. It's also occurring on SeaMonkey for Mac OS X, as reported in Bug 960849.
Comment 3•11 years ago
|
||
Additional Information:
I have determined that recipients whose Return Receipt preferences are set to "Always" rather than "Ask me" will send a receipt. Of course, SeaMonkey isn't asking them whether they want to send a receipt; it just sends it when they display the message. But at least that's a temporary workaround. If you and your co-communicants must have receipts, then use "Always" and the receipts will work. It's not ideal, but it's better than no receipts at all.
Also, I have determined that recipients who are using SeaMonkey v2.20, 2.21, and 2.22.1 are seeing the receipt request prompt, and if they click "OK", the receipt does go back to the sender, even if the sender sent the message in SeaMonkey v2.23.
![]() |
||
Comment 4•11 years ago
|
||
Ah apologies. This appears to be Bug 955830. If so this problem will be fixed in SeaMonkey 2.24.
Bug 633937 would be the bug that caused this regression.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•