ioerror / torbirdy Public

In theory we can allow all images but in the context of Thunderbird, blocking
third-party images should be fine. Earlier we were blocking all images but
that isn't really required.

When TorBirdy is uninstalled or disabled, the status bar text and colour is
updated to reflect TorBirdy's current state. Prior to this commit, if a user
uninstalled/disabled TorBirdy, the status bar text would still say "TorBirdy
Enabled". Now the status bar is updated as TorBirdy's state changes to avoid
confusing the user.

The current version (0.1.4) supports Thunderbird 10.0 - 31.*. We now support
Thunderbird 38.* - 45.* and so remove the backward compatibility code.

For Gmail, the authentication type is set to OAuth2 instead of the default
"normal password" which is what most providers use (Google doesn't allow
non-OAuth2 logins). To make this work with the manual configuration wizard in
TorBirdy, the authorization step takes place when the user checks the account
for the first time, and is not done automatically. We can probably improve
this but it's better to wait for the patches that secure the automatic
configuration wizard to be merged upstream.  See bugzilla 669238.

This is a patch proposed by Chris Knadle chris.knadle@coredump.us
to make torbirdy compliant with RFC 5821 §4.1.3.
Also see Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812115

Also look at which has a related issue:
https://trac.torproject.org/projects/tor/ticket/13006

It's not necessarily the case that users have an HTTP proxy running on
port 8118, and if they do it may be a non-torified Privoxy instance.

Using the Tor SOCKSPort will always work, and be torified.

- Ensure for new accounts that login_at_startup and download_on_biff are set to
  false.

- Clear the network.proxy.no_proxies_on preference.

…n TorBirdy