Bug 2194 - Address Collector should not create multiple copies of the same address book
Summary: Address Collector should not create multiple copies of the same address book
Status: NEW
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: UI/Address Book (show other bugs)
Version: 3.13.0
Hardware: All All
: P3 enhancement
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2010-05-05 17:45 UTC by Patrick Dickey
Modified: 2017-07-14 14:32 UTC (History)
0 users

See Also:


Attachments
This is a picture of my address book list. (56.29 KB, image/jpeg)
2010-05-05 17:45 UTC, Patrick Dickey
no flags Details

Description Patrick Dickey 2010-05-05 17:45:43 UTC
Created attachment 842 [details]
This is a picture of my address book list.

When you use the Collect Addresses option in the Tools menu, there are multiple issues.  The first is that it should allow you to check which address book you want to put the collected addresses in.  Short of that, if you enter the name of an existing address book in the text box, it shouldn't create a new copy of that book.

Due to the way the address book works, I have 20 "INBOX" address books, and four "Personal Address Book" address books.  And each time I collect addresses on the same folder (as new ones come in, I run the collection function), it creates a new copy of that same address book with the same entries (plus the new ones).  This is a bad case of disorganization.

I'm not sure if it exists in the latest version (as I have the latest available with GPG4Win), and I'm not sure if it exists in the other OS Ports (as I haven't tried it in Linux yet). But it is definitely a feature that needs improving.
Comment 1 Andrej Kacian 2015-10-28 15:34:05 UTC
This behavior is still there in newest version, regardless of the platform.
Comment 2 Ricardo Mones 2017-07-14 14:32:06 UTC
The dialog corresponding to that option would need an additional "Append to address book" or similarly named checkbox to avoid creation of a new one.

Note You need to log in before you can comment on or make changes to this bug.