Open Bug 97928 Opened 19 years ago Updated 8 years ago

Address book files should be in a subfolder of the profile folder


(MailNews Core :: Address Book, enhancement)

Not set


(Not tracked)


(Reporter: mpt, Unassigned)


(Blocks 1 open bug)


Build: 2001083008, Mac OS 9.1

To reproduce:
1.  Create a lot of address books.
2.  Quit Mozilla.
3.  Try to select these address books in your profile folder -- for backing up
    to a floppy disk, or importing to another mail program, or whatever.

What happens:
*   You have to wade through unrelated cookie, bookmarks, preference files etc,
    and have to know the secret that address book files are those with `.mab' in
    the name. (`.mab'? What is this, DOS?)
What should happen:
*   All the address books should be in an `Address Books' subfolder of your
    profile folder.
reassignig to cavin
Assignee: chuang → cavin
*** Bug 103857 has been marked as a duplicate of this bug. ***
Not only that, but the folder involved should be described by a pref (Hidden
pref, if need be.).

This way power users can share addressbooks among multiple OSs (people that
dual-boot Linux and Windows) and take advantage of backup schemes (I keep my
family's bookmarks.html and mail folders on a partition/directory that gets
automatically backed up every 2 weeks.).
Blocks: 143451
Product: Browser → Seamonkey
Assignee: cavin → nobody
Component: Address Book → MailNews: Address Book
Product: Mozilla Application Suite → Core
QA Contact: nbaca → addressbook
Also the name of the .mab should be that same as the name given to it in the adressbook field. not the current abook-1.mab ect...
Product: Core → MailNews Core
Having the default location be different seems like adding complexity and potential additional failure point for the majority of users, who have no need to share ABs.  So I'm not particularly in favor of this without strong (additional) advantages for making the change.

if bug 143451 is delivered, is there a need for this?  And if there is, I think this more correctly is blocked, and not the blocker?
You need to log in before you can comment on or make changes to this bug.