TorBirdy is not compatible with Thunderbird 68.
Quoting from #17149 (comment 1509):
Thunderbird 68 already only supports MailExtensions, but legacy
extensions can supposedly be converted to MailExtensions relatively
easily: It requires converting the old RDF manifest to a JSON manifest,
and then in the JSON manifest the legacy key can be used to load the
legacy XUL extension.
In either Thunderbird 72 or 78, the support for loading a legacy XUL
extension via the JSON manifest will be removed. I still don’t
understand in which version that will be removed, the page is titled
“Updating Legacy Extensions for Thunderbird 78” but it then says “it
should be [removed] whitin the Thunderbird 72 time frame - so by end
So we could spend some time to convert the manifest and try getting TorBirdy to work in Thunderbird 68, but that would only work for a few months. I think that instead we should try to implement and test a Tails-specific solution ASAP.
It would be great if other privacy distributions could reuse our solution (we should communicate with them about this).
Feature Branch: feature/17219-replace-torbirdy