Ubuntu
thunderbird package

  1. Bug #1899485
  2. Comment #55

Comment 55 for bug 1899485

Revision history for this message
In , Edo (etirta-a) wrote :

(In reply to Jorg K (GMT+2) from comment #47)
> Edoardo, many thanks for the information. ldap_2.servers.history.filename is
> set by default to history.mab. Instead of removing you mean resetting it,
> right? I tried setting my preference to history1.mab and could still send.

I shutdown TB and remove the line in my prefs.js. But reset it in about:config should do the same. I didn't try to change it on the fly, try to restart TB after change it and make sure you send to address that doesn't exist in any of your local address books you have.

(In reply to :Dossy Shiobara from comment #50)
> (In reply to Edoardo Tirtarahardja from comment #46)
> > Ok, I think I figure out how to reproduce this.
> >
> > As soon as the 'ldap_2.servers.history.filename' preferences is defined
> > (which in my case is pointing to other file name, we have the issue in such
> > we can ONLY send email if ALL recipient are listed in one of local address
> > books (doesn't have to be in history.mab).
>
> Is it possible that the file that is being pointed to got corrupted somehow?
> If you have that preference defined and pointing to some other file, can you
> rename that file on disk out of the way temporarily so that TB will create a
> new file, and see if the problem persists?
>
> Trying to decide whether the issue has to do with the use of that preference
> setting, or the specific mork db file you have it pointing to.

I don't think so, because I can modify that file. I actually try to set it to a brand new file 'abc.mab' (in prefs.js while TB is closed). The file is created and can't send it. As soon as I add the recipient to this new 'abc.mab' I can. The I delete the entry and can't send it again.

In my case, the original setting is 'HISTORY.MAB', I used capital letter instead of lower case. This enough to invoke the issue. Simply removing this, hence point to 'history.mab' and since I'm on Win7, the HISTORY.MAB file is still actually used (I can see the new recipient is added to it, because Windows's file name is not case sensitive) it works. So my HISTORY.MAB surely is not corrupted.