Bug #11481

Alert TorBirdy devs about Thunderbird upstream patch prefs

Added by Anonymous about 9 years ago. Updated about 6 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2016-05-24
Due date:
% Done:

0%

Feature Branch:
Type of work:
Communicate
Blueprint:

Starter:
Affected tool:
Email Client
Deliverable for:

Description

When the Icedove patches land upstream we should alert TorBirdy devs about :

  • mailnews.auto_config.ssl_only which is set by default in Icedove and
  • the need to se mailnews.auto_config.dns_mx_lookup.enabled to False in Torbirdy.

The latter is done in Tails already.


Subtasks


History

#1 Updated by Anonymous about 9 years ago

  • blocked by Feature #6156: Upstream secure Thunderbird autoconfig wizard added

#2 Updated by BitingBird about 9 years ago

  • Status changed from New to Confirmed

#3 Updated by Anonymous about 8 years ago

This depends on https://bugzilla.mozilla.org/show_bug.cgi?id=971347
Currently we are unable to run upstream’s test suite, so we’re somewhat stuck with testing our own patch.

#4 Updated by Anonymous about 7 years ago

  • Subject changed from Alert TorBirdy devs about Icedove upstream patch prefs to Alert TorBirdy devs about Thunderbird upstream patch prefs

#5 Updated by Anonymous about 6 years ago

  • Assignee set to intrigeri

@intrigeri: I think this should be part of FT work, along with Feature #6156.

#6 Updated by Anonymous about 6 years ago

#7 Updated by intrigeri about 6 years ago

  • blocks deleted (Feature #6156: Upstream secure Thunderbird autoconfig wizard)

#8 Updated by intrigeri about 6 years ago

#9 Updated by intrigeri about 6 years ago

  • Status changed from Confirmed to Rejected
  • Assignee deleted (intrigeri)

TorBirdy is mostly unmaintained upstream so we’ll see, once Feature #6156, where is the best place to set these prefs for Tails and possibly more. I don’t think having a ticket to track this will achieve much so I’m closing this one.