Closed
Bug 194236
Opened 22 years ago
Closed 14 years ago
[junk] problems for imap users when switching profiles
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: sspitzer, Unassigned)
Details
problems for imap users when switching profiles it's less of a problem for pop, since users have to retrain. but for imap, since the server keeps track of the junk status, this might be problematic. some issues: 1) can't choose existing junk mail folder (esther has already logged a bug) 2) what will manual anaylsis do on messages already marked as junk or not junk, or messages already analyzed? (won't the user expect it to re-analyze, no matter what, even if the manually set it? what will that mean for the training.dat file if the re-analysis changes?) 3) what if I try to train messages already labeled as junk (or not junk) on the server? will we properly update training.dat? these might not be the issues twalker was seeing when he moved from win32 to mac, but these are still issues to worry about.
Comment 1•21 years ago
|
||
When I use the "Switch profiles" feature, one profile that had junk mail filtering turned off, appears to have it turned on and sweeps nearly all mail into the junk mailbox. I've had to stop using the "Switch Profiles" feature because of this. I'm using Mozilla 1.4 final on Mac OS X.
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•19 years ago
|
Assignee: sspitzer → mail
Updated•16 years ago
|
QA Contact: esther → search
Comment 2•15 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
Updated•15 years ago
|
Assignee: mail → nobody
QA Contact: search → message-display
Comment 3•14 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
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•