Randy McMurchy wrote these words on 08/25/05 02:18 CST:

> Moving on to Thunderbird, I was expecting the worst, and of course,
> it was just as I expected. I have had issues with TBird for quite a
> few versions now. I'll summarize what I know (which ain't much):

Playing around I discovered many of the issues I'm seeing are easy
to fix. Googling showed me that the extensions issue in T-Bird is
real. Many folks are recommending to wait until T-Bird-1.1 before
attempting to reliably install global extensions.


> 1. If you build the installer method, then you get the
>   a) Movemail
>   b) RSS News & Blogs
> account setup options. I don't know what these are used for, but I
> know folks have asked about the RSS account stuff. These two options
> do *not* appear if you build using the book method and 'make install'.

Sorry if I appear stupid about this stuff and spewing stuff everyone
probably already knows. Oh well. Anyway, Movemail accounts are cool.
Used to move any local spooled mail (/var/mail type stuff) into T-Bird.
RSS/Blog is just what I thought it was. Access to those type
subscriptions.

Easy to make these active in the current T-Bird build method. This
one is a done deal. Just have to update the book.


> 2. Enigmail sucks. Using the book method and 'make install' when you
> run Thunderbird for the first time you get a shitty message about
> "All existing extensions will be disabled" and then Enigmail is not
> available. You have to manually edit the
> ~/.thunderbird/*.default/chrome/chrome.rdf file and remove the lines
> which disable Enigmail. It did *not* used to be like this. It used
> to just work.

Yes, it did. Some research showed the changes were put in after the
0.8 release. Now when the nsExtensionManager javascript is run when
you run T-Bird for the first time (not the root user first time
thing, but individual users after installation has been completed),
it disables Enigmail because it thinks it is a pre-0.8 extension
that doesn't conform to the new installation method.

Deleting a couple of lines in your
~/.thunderbird/*.default/chrome/chrome.rdf file makes Enigmail
come alive and best as I can tell, work properly. However, I'm
not sure the book should recommend to do this. It may have actually
been disabled because the Moz devs *wanted* it disabled.

I'm leaning to just doing a 'make xpi' to create an Enigmail
extension and install that in the /usr/lib/Thunderbird hierarchy
somewhere. Then advise folks to just install the Enigmail extension
into their profile if they want it. It's a pain in the ass for a
multi-user system, but just a one-time deal if the system is just
someone's primary desktop.

-- 
Randy

rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3]
[GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686]
14:42:00 up 145 days, 14:15, 3 users, load average: 0.00, 0.02, 0.14
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to