Hum...
I have another profile on a Linux machine and in pref.js I have :
Code: Select all
user_pref("mail.server.server1.directory", "/media/<username>/Maxtor/private/Mozilla/Thunderbird/profile/Mail/professionnel.com");
user_pref("mail.server.server1.directory-rel", "[ProfD]../../../../media/<username>/Maxtor/private/Mozilla/Thunderbird/profile/Mail/professionnel.com");
The [ProfD] path is the relative one, but it goes back up to the root folder ! This is useless in that case...
Perhaps TB has some excuses : 'Maxtor' name above refers to a USB drive plugged in a Linux machine, and the profile is reached via a symbolic link. I thought TB would have known the path as "
/home/<username>/.thunderbird/myprofile" (here 'myprofile' is a link to '
/media/<username>/Maxtor/private/Mozilla/Thunderbird/profile')... So TB retrieves the real name instead of the one I supposed...
I wanted TB to store only relative paths to have more flexibility (change the USB hard drive for instance ?)
On the other (windows) pref.js, I have something much more relevant :
Code: Select all
user_pref("mail.root.imap", "I:\\private\\Mozilla\\Profiles\\ImapMail");
user_pref("mail.root.imap-rel", "[ProfD]ImapMail");
And I checked all absolute paths in the file, and all have their proper relative counterpart just below. So here it's perfect.
There is another file then, specific to add-ons OR specific the TBsync add-on, containing an absolute path and no relative (or not a proper relative)...
I keep digging and will put the results here...
Charly