Closed Bug 550276 Opened 15 years ago Closed 14 years ago

tags applied to emails disappear after restart (IMAP)

Categories

(SeaMonkey :: MailNews: Message Display, defect)

SeaMonkey 2.0 Branch
x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: skuhn, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.8) Gecko/20100205 SeaMonkey/2.0.3 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.8) Gecko/20100205 SeaMonkey/2.0.3 Tags (like "urgent to do" etc.) applied to stored email messages in my "Inbox" disappear from one launch of "SeaMonkey" to the next. This may be a problem specific to IMAP servers (I don't have this problem with my POP email account); however, it didn't USE to be there: I still have a few 2-year old email messages from the same IMAP account in my "Inbox" that have RETAINED their tags all this time; just any more recent tags that I try to apply disappear (they remain during any given session, but apparently don't get stored and are gone when restarting SeaMonkey). Reproducible: Always Steps to Reproduce: 1. Select email message in "Inbox" 2. Apply tag (like "urgent to do") 3. Quit and restart SeaMonkey -> tag is gone. Actual Results: Tag is gone Expected Results: Tag should be permanent until changed by me. MacBookPro 2 GB
Duplicate of MailNews Core bug 542137?
Build identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.8) Gecko/20100205 SeaMonkey/2.0.3 Works For Me. Please try in Safe mode ( http://kb.mozillazine.org/Talk:Safe_Mode#Safe_Mode_in_SeaMonkey_2 ). Have it import from profile on SeaMonkey 1.1.x?
Version: unspecified → SeaMonkey 2.0 Branch
Might be a server problem. Some servers only allow a predefined list of tags. Closing as there has been no feedback from the original reporter in a year. Please reopen if the problem still happens.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.