Open Bug 180012 Opened 22 years ago Updated 2 years ago

junk mail whitelist by LDAP addressbook doesn't work

Categories

(MailNews Core :: Filters, defect)

defect

Tracking

(Not tracked)

People

(Reporter: sspitzer, Unassigned)

References

(Depends on 1 open bug)

Details

filter by LDAP addressbook doesn't work

I think we have to decide if we want it to work, as it might be slow

for now, we should probably just remove it from the picker (make it so the xul 
template rule won't list them)
I haven't debugged, but here's the place to start:

WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file c:/builds/buffy/mozilla/m
ailnews/base/search/src/nsMsgSearchTerm.cpp, line 869

Seems to be the same as  #177441 and  #215958  

*** This bug has been marked as a duplicate of 215958 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
I beg to differ - this is NOT a dup of bug #215958.

215958 is about filtering LDAP searches.

This bug is about using an LDAP addressbook AS A FILTER for spam.

At least, that is how I read it, and why I voted for it.
David: re-reading, I think you're right.  Good catch.  Reopening.
Status: RESOLVED → REOPENED
OS: Windows 2000 → All
Hardware: PC → All
Resolution: DUPLICATE → ---
Summary: filter by LDAP addressbook doesn't work → junk mail whitelist by LDAP addressbook doesn't work
Not sure if this is the same but it may be closely related:

I recently reorganized my address book (non-LDAP) into Personal and
Business as separate address books.  I left the "personal" addresses
in the default "Personal Address Book" and moved all my business
contacts into a new address book.  I've started seeing occasional 
mails from people in my business address book being flagged as 
SPAM, something that NEVER used to happen when everything was in
the same address book.
(In reply to comment #6)

Jim, you should try voting on bug 187771. I think that is what you're looking for.
Product: MailNews → Core
taking dependency from bug 209551 comment 2
Status: REOPENED → NEW
Depends on: 187771
QA Contact: laurel
*** Bug 209551 has been marked as a duplicate of this bug. ***
Just as a side note, I think the option should be checkboxes (where you can 
select multiple address books), not a drop-down box (where you can only select 
one address book - how it is now).  Most of our employees have multiple 
address books other than just their ldap.  It'd be helpful to us if this bug 
were fixed because currently we have filters set up for everyone for 
@emcins.com senders to stay in the inbox AND be marked as not junk, but lots 
of people are getting messages from @emcins.com marked as junk anyway.  Since 
the @emcins.com people are all in our ldap, that should resolve this problem.

*** Bug 250601 has been marked as a duplicate of this bug. ***
Has there been any progress on fixing this?
No longer depends on: 187771
A year later: is anybody working on this?
*** Bug 363509 has been marked as a duplicate of this bug. ***
Sadly, based upon the age of this defect and the new defect that I have opened against T'Bird Version 2 #363509, it seems that there is little to no interest in T'Bird providing any depth of support for LDAP. Not having provided this in T'Bird Version 2 is a serious deficiency if there is any intent of spreading T'Bird to a wider audience instead of focusing on the 'home' user.  

If there is no intent to address this - then I would suggest that you close this defect out as a dead issue.,
Depends on: 359352
sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
The same applies to the system address book on OS X. Mark, could this be solved with the work on 359352? Or isn't it related?
Status: NEW → RESOLVED
Closed: 21 years ago16 years ago
Resolution: --- → DUPLICATE
Sorry for the spam, hit the wrong button :-(
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Status: REOPENED → NEW
QA Contact: filters
Product: Core → MailNews Core
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.