Don't kick the monster!
Program a robot to smash it, Shoot it, Spear it or even Throw something at it (preferably a grenade), but NEVER kick the monster!
NOTE: does not apply to BLACK BELTS.
Since the new Alpha 1.1, I have noticed that the profile on Windows is stored in:
C:\Documents and Settings\user\Application Data\Thunderbird\Profiles\0nt8ipuj.default
This contains all the files that comprise the profile.
but when Thunderbird runs, a profile directory is also created in:
C:\Documents and Settings\user\Local Settings\Application Data\Thunderbird\Profiles\0nt8ipuj.default
This second profile directory simply contains a single file xul.mfl which gets rebuilt every time T'bird is started.
Anybody on Windows seeing this?
I assume this is a bug.. the xul.mfl should be created in the correct profile directory but for whatever reason it is being created beneath the "Local Settings" dir.
It's the cache folder, see <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=291033" title="Enable support for profile temp directory on local filesystem">bug 291033</a>.
I've read that bug and I don't see what putting this file into Local Settings achieves apart from fragmenting these files into multiple locations. If this file is meant to be temporary then why is it not (a) deleted when the program exits and
(b) put it under C:\Documents and Settings\user\Local Settings\Temp
Just noticed that I when I send and receive emails with 6/3 build, I am not getting the 'paperclip' showing the presence of attachments.
Anybody confirm?
"Improved UI under Account Settings for managing multiple SMTP accounts. If you have an account with multiple identities, you can even configure an SMTP server for each identity."
This may be picking a nit, but the inline spell checker in the 20050531 build of Tb 1.0+ thinks "Thunderbird" is misspelled. That should probably be fixed before it goes out to the general public.
if THUND~1.exe or thunderbird.exe are showing in task manager then use task manager to kill the process .. then delete your profile and try again
I had the same problem a few times on the 1.1 alpha 1 and that fixed it everytime .. until the next time I installed it that is but for me the newer builds don't do that anymore
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.