Closed Bug 212312 Opened 21 years ago Closed 21 years ago

Return Receipt notifys self from IMAP Sent folder

Categories

(SeaMonkey :: MailNews: Backend, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: unique_id, Assigned: Bienvenu)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030703
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030703

Assuming after sending mail with an IMAP account, the mail gets copied to the
Sent folder. If you then browse the Sent folder and read that mail, Mozilla asks
to notify sender.

Reproducible: Always

Steps to Reproduce:
1. Set Mozilla options to copy sent messages to Sent folder for IMAP account
2. Send mail from IMAP account with Return Receipt requested
3. Browse to Sent Folder
4. Read mail

Actual Results:  
Mozilla asks to notify sender

Expected Results:  
Nothing

Additionally, the same thing happens if you move the message from say Sent to
Trash. It'll reappear everytime you move it to a new folder. Doesnt seem to
happen for POP messages.
Summary: Return Receipt notifys sender from IMAP Sent folder → Return Receipt notifys self from IMAP Sent folder
I can confirm this behaviour in 1.4 release. Why has this bug not been confirmed
and processed by someone???
I am using Mozilla 1.4 final release and I've noticed this behaviour too.
I can confirm this behaviour in Mozilla 1.5 Beta - Released August 27, 2003.

Why has nobody confirmed this bug?
20031003
I cant reproduce this
sent email, had return receipt to "ask me" and then read mail in sent folder. no
dialog.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
I am using Mozilla 1.5 final release - the bug is here.
To comment #4 - was options->return receipt on when you were sending that message?
Product: Browser → Seamonkey
Component: MailNews: Return Receipts → MailNews: Backend
QA Contact: grylchan → offline
You need to log in before you can comment on or make changes to this bug.