Closed
Bug 273838
Opened 20 years ago
Closed 19 years ago
No option to prevent unread message notification on XP Welcome screen
Categories
(Thunderbird :: Preferences, enhancement)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: billsull, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla Thunderbird Version1.0 (20041206) also installed:Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 In the dark times before Thunderbird, I had manually set the registry value MessageExpiryDays to zero in order to not have to look at a summary of new and unread Outlook messages on the Welcome screen every time I logon to Windows XP. When I installed Thunderbird, the value was removed and the new and unread message status re-appeared. There is no setting under Tools>Options... to manage this registry entry. I think it should be added with the default set to mimic display status prior to install. The value can be found under the following subkey: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\UnreadMail\ Reproducible: Always Steps to Reproduce: 1. Uninstall Thunderbird 2. Set MessageExpiryDays DWord value to zero under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\UnreadMail\ 3. Confirm message status off on XP Welcome screen 4. Re-install Thunderbird Actual Results: Email message status will re-appear on the XP Welcome screen. Expected Results: Install should check for presence of registry settings that affect display of message status on XP Welcome screen and leave them unchanged while adding necessary reg entries for Thunderbird. In addition, Tools>Options... should contain a control to manage the display of email status on the Welcome screen for the current user.
Comment 1•20 years ago
|
||
Text associated with one Windows XP Home account login icon shows 4 unread messages that never showup in Thunderbird. Unusual case was caused when the Thunderbird mail account setup was mistyped as *@centurytel.com instead of *@centurytel.net. This was corrected quickly, and 2 messages were bounced back to the senders who forwarded them again with the correct address. Apparently 4 more messages were incorrectly sent with the *.com suffix instead of *.net. CenturyTel swears the messages are no longer in their system, but the notice still appears at the XP login icon. A right-click on the notice identifies the 4 messages to have the proper ID except the ISP is identified incorrectly as *centurytel.com CenturyTel says it is a Windows problem, Toshiba says it is a CenturyTel problem. We would be happy just to be able to clear [erase] the notice.
Comment 2•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 3•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
•