MDN: Pop only: No Return Receipt prompt for newly created folder/filter until quit/restart

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Backend
RESOLVED EXPIRED
17 years ago
8 years ago

People

(Reporter: grylchan, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
Using commercial trunk builds:
2002-04-16-06-trunk NT 4.0
2002-04-16-07-trunk linux 2.2
2002-04-16-03-trunk mac 9.2.2

I noticed then when testing out bug 136476

I noticed if you create a new folder and a new filter for a pop
account, you won't be prompted to send a read receipt after
reading the mesg.

But if you quit/restart and try again, you will be prompted.

Only for pop accounts as I tried this same scenario w/imap
and it worked fine.

Steps to reproduce:
1.Created a new profile
2.Create a pop mail account
3.check the prefs: (probably not needed but documenting just in case)
  - check for new mesg every 1 min
  - automatically download any new mesgs
  - leave mesgs on server
  - delete mesg on server when deleted locally
4.Save it, quit mozilla and then restart mozilla
5.Login to pop mail account
6.Set MDN prefs either Global or Customized MDN for the mail acnt:
  Check the box 'When sending mesgs, always request a Return Receipt'
  When I receive request for a return receipt
   - Ask me
7.Set up a filter (I had a filter that filtered based on subject line
  containing the word 'foo')
8.Compose a mesg to yourself
9.add the subect/body,date etc that the mesg will be filtered on
10.Go to the Menu for compose window
   -Options|Return Receipts and unselect it
   -no arrow should be next to the word 'Return REceipt'
   -yes we are turning off Return Receipts for this one mesg only
11.Send it and do a GetMsg
12.Noticed the mesg gets filtered to the proper folder
13.Repeat steps 8 & 9 again
14.This time keep Return Receipt option ON
15.Send the mesg
16.Get Msg
17.It gets filtered to proper folder
18.Click on it

result: once you 'read it'/click on it, no prompt to
        ask you to send a return receipt mesg

expected: prompt to send return receipt mesg

If I quit mozilla/restart and try again it works fine.
Initially for some reason RR doesn't work.

I hope I'm clear enough.
(Reporter)

Comment 1

17 years ago
adding myself as qa
QA Contact: gayatri → gchan
(Reporter)

Updated

17 years ago
Blocks: 134040
(Reporter)

Comment 2

16 years ago
changing component to return receipt
Component: Mail Back End → Return Receipts
Product: Browser → Seamonkey

Updated

10 years ago
Component: MailNews: Return Receipts → MailNews: Backend
QA Contact: grylchan → offline
Assignee: jt95070 → nobody
QA Contact: offline → mailnews-backend

Comment 3

9 years ago
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

Comment 4

8 years ago
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
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.