Opened 10 months ago

Last modified 4 months ago

#21433 new enhancement

TorBirdy: Respect user preferences for header_type and message body type

Reported by: jflory7 Owned by: sukhbir
Priority: Medium Milestone:
Component: Applications/TorBirdy Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Summary

Whenever Thunderbird restarts, TorBirdy resets the values for header_type and what type format to view emails, irrespective of user preference.

Description

Something I noticed quickly after using TorBirdy is that it changes two settings forcibly whenever Thunderbird starts. The two settings I always change back after Thunderbird restarts are:

  • View > Message Body As… > Original HTML: While I am aware there are potential security risks by enabling this, I prefer to view emails with the original HTML and subjectively choose to change this setting for a specific email as needed.
  • mailnews.reply_header_type: After restarting, the value is adjusted to 1 from the default, 2. I prefer to have the full reply header type when I reply to emails.

While I respect the reasons the TorBirdy developers have for changing these settings, it's annoying for me as the user to have my preferences overruled every time Thunderbird restarts, and then I have to go and change this manually every time it restarts.

Implementation

  1. Start Thunderbird
  2. User changes settings from default TorBirdy configuration, e.g. message body type and reply_header_type
  3. User closes Thunderbird
  4. User restarts Thunderbird, adjustments to settings preserved

Child Tickets

Change History (2)

comment:1 Changed 10 months ago by sukhbir

I see that you have already read why HTML emails are disabled, so let's skip that discussion.

As of now there is no way to override the settings, because of the design decision and the architecture of the extension. For now there is no timeline but I do plan to work on it.

comment:2 Changed 4 months ago by jflory7

I see this is also similar to #10684.

Note: See TracTickets for help on using tickets.