John McPherson wrote:
Not really answering your main question in any way, but one gotcha that I've encountered: thunderbird includes its own copy of an ldap library, and if you have 'ldap' in /etc/nsswitch.conf for resolving user IDs then thunderbird will crash on startup. (Basically thunderbird's ldap library is binary-incompatible with the system's openldap, and if nsswitch is using ldap then thunderbird will be dynamically linked against both).
Ooooh yes, that's a good one. The following works, FSVO, YMMV, no promises as to what the next upgrade may do: # getent passwd ldap_user_name >> /etc/passwd This'll leave something like the following at the foot of /etc/passwd: jbloggs:x:1017:1017:jbloggs:/home/jbloggs:/bin/bash Which I think is enough for the TB ldap library to get started, while forcing it to fall back on openldap if it tries and fails to match the password. (I apparently failed to bookmark the page that suggested this solution, and could easily be completely misremembering the explanation, if indeed there was one.) I don't -know- of any nasty pointy teeth attached to this, but if anyone does please let me know, so's I can have another stab at reinstalling TB 2. butting