User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030214 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030214 If a user takes mail from their inbox, and drags it into the designated Junk folder, Mozilla should automatically proccess it as if it were junk. Reproducible: Always Steps to Reproduce:
Sounds sensible to me. Marking NEW, Cc'ing jglick.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Kind of obvious, but... vice versa if mail is dragged out of junk folder into the inbox, trash (since people like me keep their old mail in the trash to look back), etc.
A move directly to the trash should constitute non-spam. This way it trains both ways.
> 1.4a? Maybe. It's been added to the spec. http://www.mozilla.org/mailnews/specs/spam/
Always cool to see something you thought of go through the system into a product.
Not sure if this is a good idea. If a person uses the trash folder to hold both trash and junk with the option to delele junk after x days, they would expect the messages marked as junk deleted but not the trash only messages. Jen?
Perhaps a UI option is needed to decide if it should delete trash... or delete junk? If delete junk... then only those marked as junk (which is what I perfer). If delete trash... purge the trash.
Orig plan was to not allow users to set up the Trash as the "Junk" folder. http://www.mozilla.org/mailnews/specs/spam/#JMC Just creates a lot of potential for problems and confusion (like this bug, what is really junk and what is really trash). Users can choose to Delete JM or Move it to the Junk folder. If we stick with that plan, this bug shouldn't cause any conflicts.
Assignee: mail → nobody
QA Contact: esther → message-display
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
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: 9 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.