don't allow user to accidentally classify as junk a piece of mail from someone in address book



14 years ago
13 years ago


(Reporter: jedmondson, Unassigned)


Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b) Gecko/20050217
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b) Gecko/20050217

This is a suggestion for an enhancement.

Currently, when scrolling through your list of email in the Inbox and clicking
off what is junk and what is not, it is possible to accidentally classify an
email as junk even if it is from someone in your address list.  It would be nice
to grey out the junk button or the junk column in these situations so that email
cannot be accidentally junked.  This would only apply when the option in junk
mail settings is chosen to exempt mail from people in your address book.

Reproducible: Always

Steps to Reproduce:
1.  Select Junk Mail Control "Do not mark messages as junk if the sender is in
my address book
2.  Highlight an email from someone in your address book
3.  'Accidentally' click on Junk button
4.  Email will be moved or deleted according to junk mail controls settings

Actual Results:  
see above

Expected Results:  
Option 1:
Junk button/column would be inaccessible if sender is in your address book

Option 2:
Warning message would be generated if sender is in your address book.
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.