Closed
Bug 272674
Opened 20 years ago
Closed 19 years ago
new mail does not appear in current IMAP folder
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: nixon049, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 Build Identifier: Thunderbird 0.90 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) IMAP account. thunderbird filters mail upon arrival in inbox; filtered messages are sent to subfolders of the inbox. New mail notification shows up when mail is sorted, but if currently browsing the folder the mail is sorted into, the new message does not appear. Choosing view --> unread does not help, resorting messages in folder does not help. Clicking on Inbox and then back to folder causes new message to appear. This does not happen to mail that is left in inbox, only to mail sorted into a subfolder by Thunderbird. Looks like failure to refresh message header list when mail arrives. Reproducible: Sometimes Steps to Reproduce: 1. start thunderbird, make filter to send incoming message into a subfolder of inbox 2. open subfolder to view mail (sorted newest mail first) 3. send message that should be filtered into that folder: watch for new mail notification Actual Results: new mail notification popup and new mail notify in folder list both work fine, but new message does not appear in list of message headers for that folder. Expected Results: new message should show up at top of folder. note that inbox itself seems to work fine, but subfolders don't get refreshed; all subfolders are subscribed and are on IMAP server, not local folders; local copies are made for offline use though. all folders including inbox are sorted reverse-date (newest messages at top of list).
Updated•20 years ago
|
Summary: new mail does not appear in current folder → new mail does not appear in current IMAP folder
Comment 1•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 2•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•