Closed Bug 210893 Opened 21 years ago Closed 19 years ago

Junk Mail Controls ignores alternate addresses (additional email) in Address Book

Categories

(MailNews Core :: Filters, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1511833

People

(Reporter: k3pbu, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425

In Junk Mail Controls, I checked the box that says "Do not mark messages as junk
if sender is in my address book". Some messages are erroneously being marked as
junk, even though the sender's address is listed as an "alternate" address in my
address book. Apparently the filter is checking only the primary addresses, not
the alternates.

Reproducible: Always

Steps to Reproduce:
1. See details, above.
2.
3.

Actual Results:  
See details, above.

Expected Results:  
When the box that says "Do not mark messages as junk if sender is in my address
book" is checked, the junk filter should check the "alternate email" entries in
the address book, in addition to the primary entries.

I haven't checked, but this bug probably exists in all platforms.
ME too :)
Reporter, please do not report bugs without checking against a current version;
1.4 has been out since three days before your bug report.

Check bug 198731 or its dependents for a potential duplicate.
*** Bug 227372 has been marked as a duplicate of this bug. ***
Product: MailNews → Core
bug 187239 claims that this should work (but I'm not sure that this works for
the Junk Mail scenario), duped bug was with 1.5 (after the fix)

So can anyone confirm this bug with current builds?

OS: Linux → All
QA Contact: laurel
Summary: Junk Mail Controls ignores alternate addresses in Address Book → Junk Mail Controls ignores alternate addresses (additional email) in 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:
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/
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
Product: Core → MailNews Core
Assignee: sspitzer → nobody
Resolution: EXPIRED → DUPLICATE
You need to log in before you can comment on or make changes to this bug.