Thunderbird 2.x and 3.x have problems with Archiveopteryx 3.1.2 and earlier, because the Mozilla TLS library and the Cryptlib TLS library don't play well. We have no idea who's at fault. Archiveopteryx 3.1.3 evades the issue by using OpenSSL instead of Cryptlib.
Thunderbird 3.0.0 has a bug which results in messsage flags being displayed incorrectly; we recommend using 2.x, 3.0.1 or later.
Thunderbird 3.0.1 and later have interoperability problems with Archiveopteryx 3.1.2, mostly our fault. 3.1.3 works well.
Thunderbird's Sieve editor
does not support self-signed certificates. It works with
Archiveopteryx if Archiveopteryx has a proper certificate, or if
Thunderbird is configured to not use TLS. Its
feature also suffers from a parsing bug, and should remain disabled.
Note that Archiveopteryx defaults to port 4190 for editing Sieve scripts, while Thunderbird defaults to port 2000. Either or both have to be reconfigured. (Archiveopteryx follows the finished RFC, Thunderbird follows the older Internet-drafts.)
Apart from the problems noted above, Thunderbird and Archiveopteryx work well together.
In case of questions, please write to email@example.com.
Last modified: 2010-11-19