126022 - Collected addresses should not include/add entries already in LDAP

Status: NEW

(MailNews Core :: Address Book, defect, P2)

Description

[Ian Neal]

Compose an email to someone with an entry in that LDAP server

Actual behaviour
Check collected addresses and that person is now listed

Expected behaviour
Person is not added to collected addresses

This also happens with incoming e-mail, people on the LDAP server sending you an
e-mail get added to the collected addresses even though they're already in one
of the other address books.

Comment 1

[Nathan Bidwell]

Is this related to bug 118388 ?

Comment 2

[Ian Neal]

Bug 118388 WFM now but I'm still getting the problem of addresses being
collected that already exist in an LDAP address book.

Attempting to flag up to LDAP people by marking as a blocker to bug 36557

Comment 3

[Ian Neal]

Bug 118388 WFM now but I'm still getting the problem of addresses being
collected that already exist in an LDAP address book.

Attempting to flag up to LDAP people by marking as a blocker to bug 36557

Comment 4

[GA]

this is a sub-set of functionality decribed in bug #104863.   

Some major work needs to happen with "Collected Abook" functionality.  As it
stands today, the collected address book becomes a repository of JUNK (ie. dupe
records (from LDAP and Personal Abook), bad formats).

Main priorities:
1)  entries destined for collected abook should first be checked against LDAP
and Personal Abook (and Abook on Address Book Server -- ref. Netscape Enterprise
Abook Server).

2)  allow user to specify domains to include/exclude from Collected Abook

3)  verify email addresses should follow basic format (as specified by user). 
There should be a way to insure fat-fingered email addresses don't go in
Collected Abook (eg.  "[e-mail]")

4)  expirations rules for Collected Abook.   Allow user to specific TTL for
entries in Collect Abook (so **** doesn't stay forever).

Comment 5

[Ian Neal]

Priority one is the major concern for me, it would remove 70-80% of the
addresses that end up in my collected address book and that is what this bug
should deal with.

Comment 6

[(not reading, please use [e-mail] instead)]

mass re-assign.

Comment 7

[Ben]

Please update Summary field to:
Collected addresses includes entries already in LDAP or other address books
or something similar. Thanks!

Comment 8

[Ben]

It should be an option to not collect addresses that are present in an LDAP
server. Personally I want to collect addresses that are present in an LDAP
server, but not those that are present in a local address book.

Comment 9

[Jim Booth]

Note: The OTHER ADDRESS BOOK issue is addressed in bug 58769 - don't collect
addresses into CAB that occur in other AB's  

Comment 10

[Tom Schneidereit]

As a quick and dirty work-around it might be usefull to be able to set the max number of collected addresses to 1 or any higher number. Guess Netscape 7.0 had this feature.

Comment 11

[James B. Higgs]

Hello,

98% of what ends up in my "collected addresses" abook are already in one or
another of my other address books. The contents of these should be screened
out.

Also, I see the purpose of a "collected addresses" abook, in the long run,
is to collect them for *filing* into these other address books, so an easy
way to do so should be provided. (Right-click, Move to, List-of-Address-Books)

Jim H. (aka CuriousJ)

Comment 12

[Mark Banner (:standard8)]

Restricting to just LDAP, other address books covered by bug 58769.

Comment 13

[tibey]

This bug should really be fixed. What is the point of setting up an ldap if you end-up with outdated adresses all over your adress book ?

Especially when using auto-fill it's getting really confusing for users. Generally they are trusting their local domain adresses because ldap is supposed to be always up to date, but because of this bug they can be presented old emails from deleted accounts and whatsoever...this deserve a patch.

Comment 15

[Thomas D. (:thomas8)]

Thanks to Magnus for quickly finding a starting point in code (from 'Thunderbird Developers' chat on Matrix today):

https://searchfox.org/comm-central/rev/69d6f790cef76552cd5b132997531252cb575a05/mailnews/compose/src/MessageSend.jsm#1080
but yes we should probably do that before closing the compose window instead

Comment 16

[Thomas D. (:thomas8)]

(In reply to tibey from comment #13)

This bug should really be fixed. What is the point of setting up an ldap if
you end-up with outdated adresses all over your adress book ?

+1. This bug makes using LDAP address books pretty pointless, which is a significant fallout for enterprise LDAP users (which include some of our biggest institutional consumers iiuc).

Especially when using auto-fill it's getting really confusing for users.
Generally they are trusting their local domain adresses because ldap is
supposed to be always up to date, but because of this bug they can be
presented old emails from deleted accounts and whatsoever...this deserve a
patch.

True!