Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Encrypted/signed emails are not supported in Thunderbird 115.x #2006

Open
Tracked by #2021
Standard8 opened this issue Aug 29, 2023 · 3 comments
Open
Tracked by #2021

Encrypted/signed emails are not supported in Thunderbird 115.x #2006

Standard8 opened this issue Aug 29, 2023 · 3 comments

Comments

@Standard8
Copy link
Collaborator

Standard8 commented Aug 29, 2023

Due to the impact of the changes from Thunderbird 102 to Thunderbird 115 (all of which have been good improvements for the future of Thunderbird), Conversations has required significant parts rewriting to continue working. Unfortunately due to lack of time, not all of it currently supports 115. Given that 115 is now out, it was considered better to release something that mainly works, and re-add support for the remaining parts as time becomes available.

This issue is for tracking the lack of encryption/signed email support with Thunderbird 115.

The work here is to go through Thunderbird's UI and extract the relevant parts necessary to provide the appropriate display and encryption routines, and figure out how to fit those into Conversations' architecture. I have one bit partially figured out, but it is being inconsistent and will need investigating further.

The workaround is to view the emails using the classic reader.

@laurentS
Copy link

I just landed here after being bitten by a signed email that appeared to have no attachments (in TB 115). Can I suggest adding a warning in the conversation view, something like "warning, this email is signed/encrypted, it may not display correctly, use the classic reader if needed." until the features are back?

Thanks for all your work on this neat extension!

@Standard8
Copy link
Collaborator Author

Unfortunately to detect enough to know that it is signed or encrypted is pretty much most of the way to fixing this issue. Hopefully I'll get time to look at it in more detail soon.

@almereyda
Copy link

almereyda commented Sep 30, 2023

Here encrypted messages are displayed just fine with v4.1.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants