Open
Bug 430319
Opened 17 years ago
Updated 8 years ago
request for option to save outgoing return receipts (acknowledgments) in sent folder
Categories
(SeaMonkey :: MailNews: Backend, enhancement)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: 20004632, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.11) Gecko/20071128 SUSE/1.1.7-5.1 SeaMonkey/1.1.7
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.11) Gecko/20071128 SUSE/1.1.7-5.1 SeaMonkey/1.1.7
I consider return receipts as any other message send on my request. However, I notice return receipts are not saved to the sent folder and I can not find any option to do so by default.
Reproducible: Always
Steps to Reproduce:
1. receive email with Disposition-Notification-To in header
2. confirm sending the return receipt to sender
3. check mail folders for sent return receipt, no sent return receipt found
Actual Results:
Return receipts are not saved as send message
Expected Results:
Return receipt saved as send message in such mailfolder.
Did not try this for return receipts send by default when a message with Disposition-Notification-To is received
Comment 1•17 years ago
|
||
I expect this bug will be WONTFIXed but not by me -- the decision has to come from higher up. I'm not really sure who though. Bienvenu? Standard8? Someone else? (Please add him/her if (s)he doesn't already receive this bugmail.)
OS: Linux → All
Hardware: PC → All
Version: unspecified → SeaMonkey 1.1 Branch
Comment 2•17 years ago
|
||
Expressing more clearly in Summary what comment #0 is asking for
Summary: request for option to save return receipts in sent folder → request for option to save outgoing return receipts (acknowledgments) in sent folder
Component: MailNews: Return Receipts → MailNews: Backend
QA Contact: return-receipts → offline
Updated•16 years ago
|
Assignee: bienvenu → nobody
QA Contact: offline → mailnews-backend
Comment 3•8 years ago
|
||
I wonder why this option has never been implemented. Is it some kind of a security issue or something like that?
You need to log in
before you can comment on or make changes to this bug.
Description
•