Changes between Version 20 and Version 21 of doc/TorifyHOWTO/EMail/Thunderbird

May 22, 2018, 1:39:00 AM (2 years ago)

Old advice wipe, mild changes


  • doc/TorifyHOWTO/EMail/Thunderbird

    v20 v21  
    55Thunderbird is a free and open-source mail, RSS, news and chat client originally released in 2003 by the Mozilla Project. It is available for download on Windows, MacOS and Linux, and is commonly found in the repositories of many major UNIX distributions. Thunderbird largely follows the principals Mozilla originally inscribed for the Mozilla Firefox web browser.
     7Official site: []
    79== Using Thunderbird with Tor ==
    3133'''Warning:''' Using email over Tor is not enough to protect sensitive communications!
    33 For enhanced privacy and security, it is advised to use Enigmail in conjunction with Torbirdy. Enigmail is an open-source encryption / decryption and signing tool for Thunderbird originally released in 2001. Enigmail facilitates very simple use of [ GnuPG] keys in order to securely transmit plaintext communications over the internet.
     35For enhanced privacy and security, it is advised to use Enigmail in conjunction with Torbirdy. Enigmail is an open-source encryption / decryption and signing tool for Thunderbird originally released in 2001. Enigmail facilitates very simple use of [ GnuPG] keys in order to securely transmit communications and files over the internet.
    35 For more information on Enigmail and how to install it, see their [ official documentation].
     37The process of installing Enigmail is largely done the same as Torbirdy; simply search for it in the add-on menu, and click 'Install'.
    37 [[br]]
    38 == Outdated Advice ==
     39For information on using Enigmail, see their [ official documentation].
    41 This section simply exists for historical value and should not be followed. These instructions are no longer necessary with the introduction of Torbirdy.
    43 Thunderbird has native SOCKS5 support that can be enabled through the '''Tools''' / '''Options''' / '''Advanced''' / '''Network & Disc Space''' Tab.  Click on the '''Connection''' button and then select '''Manual Proxy Configuration'''.  Enter the details for the Tor server you wish to use, (probably on Port 9050).  Thunderbird should now be working, (for all suported protocols).  It's best to test it at this point, although bear in mind that it might be leaking DNS information.
    45 As of Thunderbird 3.1 the instructions below work, except that the menu location has changed to '''Edit''' / '''Preferences'''.
    47 {{{
    48 #!html
    49 <a name="Config_Editor"></a>
    50 }}}
    51 Assuming you now have Thunderbird working through Tor, the last step is to ensure that DNS resolves aren't leaking
    52 information.  Select the '''Tools''' / '''Options''' / '''Advanced''' / '''General''' Tab and then click on '''Config Editor'''.  This will present you with a huge list of all the potential configuration options in Thunderbird.  The list can be narrowed by typing ''proxy'' into the filter box.  Find the option '''network.proxy.socks_remote_dns''' and make sure it's set to '''true'''.  If not, double-click it to toggle the setting.  That's it, Thunderbird should now be fully configured for use with Tor.
    54 '''Warning:''' If you're using a proxy autoconfig file, [ Mozilla Bug 351163] will make Thunderbird bypass Tor after every startup.
    56 Warning: Do not use same Thunderbird for accessing your personal (or private) emails, and your "Anonymity" based (or purpose) emails.  Few possible solutions: obtain [ Portable Thunderbird] (''then match & compare the "MD5 Hash" code shown on PortableApps site, though it is not safer to use MD5 hash anymore, MD5 is better than no hash at all''), or, install full-edition Thunderbird again, but on a different folder.  If you are going to use multiple Portable Thunderbird(s), then apply or modify startup option ( ''AllowMultipleInstances=true'' in "ThunderbirdPortable.ini" file ) to allow running multiple (Portable) Thunderbirds at the same time.
    58 Warning: Unless, you are using system-wide [wiki:doc/TransparentProxy transparent-proxy] (''linked info/page is now considered to be insecure in general cases, either use better software & technique, or use special-cases where a Transparent-proxy server still can be used''), or, you are using Thunderbird inside a [wiki:doc/VM VM] (secure) and all TCP (including DNS) network traffic is forwarded through Tor-socks-proxy, otherwise do not use "Webmail" plugin.  If mentioned tools or software are not used, then "Webmail" by default will use plain (non-encrypted) HTTP through system's default network adapter's internet connection, not the Tor socks proxy, and will not use a secured & encrypted connection either.  More configurations are required before Webmail can be used safely, so avoid it.
    60 Look at [ ***Experimental***] and below for suggestions for possibly making thunderbird stop leaking info.
    62 === Common Fingerprint ===
    63  * use NTP
    64  * use SSL/TLS if available (instead of STARTTLS)
    66 See instruction few section [#Config_Editor above] on how to start "Config Editor" in Thunderbird, and then apply below settings in it:
    67 {{{
    68 network.cookie.cookieBehavior=2
    69 mail.smtpserver.default.hello_argument=[]
    70 network.proxy.socks_remote_dns=true
    71 general.useragent.override=
    72 ...compose_html=false
    73 mailnews.send_default_charset=UTF-8
    74 mailnews.send_plaintext_flowed=false
    75 mailnews.reply_header_type=1
    76 mailnews.reply_header_authorwrote=%s
    77 mailnews.start_page.enabled=false
    78 }}}
    80 === Enigmail ===
    81 Enigmail is a Thunderbird addon (aka, plugin), it allows to view (decrypt) and send (encrypt) PGP, GPG, X.509(SSL/TLS) certificate & keys protected & secured emails, end-to-end.  Enigmail works by using [ GnuPG] software, so you must install a suitable GnuPG package for your OS(operating system) if your OS does not have one already.  Enigmail's gpg settings over-rides GnuPG's default settings.  Most Linux systems have GnuPG pre-installed. In Windows & MacOSX, it is better to install the latest stable edition of Gpg4win or GnuPG.
    82  * set an HKP (HTTP Keyserver Protocol) server including port (e.g. "hkp://")
    83  * better: use an HKP server that runs as hidden service
    84 {{{
    85 extensions.enigmail.addHeaders=false
    86 extensions.enigmail.useDefaultComment=true
    87 extensions.enigmail.mimeHashAlgorithm=5
    88 extensions.enigmail.agentAdditionalParam=--no-emit-version
    89 }}}
    90 Note: For further level of accuracy & security, keyservers which support HKPS (Secured HTTP Keyserver Protocol) should be used over HTTPS or TLS/SSL protected connections, (instead of, HTTP based HKP, which is non-encrypted and less-secured communication with keyserver), because, "unknown" proxies and middle nodes and gateways (and possible MITM) exists in the path (of Web of Trust(WoT)), with "unknown" level of chance of alteration at various stages & components, DNS cache poisoning, etc.  Try alternative WoT paths: goto sender's (or author's or signer's) website directly, connect over HTTPS (SSL/TLS), and find GPG fingerprint (if sender or author has shared it over https website), (or visit sender's or author's site multiple time via using multiple different Tor-circuits by utilizing Vidalia's Tor Network Map).  Many authors also share fingerprint over the phone, visiting-card, etc as well.  DNSSEC signed keyserver, DNSSEC-supported DNS-Resolver, etc can help greatly for even further accuracy & security.
    92 == Required Further Information  ===
    93 Download the fine paper "Towards a Tor-safe Mozilla Thunderbird - Reducing Application-Level Privacy Leaks in Thunderbird" below for further information on Tor and Thunderbird.
    94  * This paper recommends avoiding PGP/MIME, apparently because of the identifiable message part boundaries.  [ dkg reported the paper's concerns about identifiable MIME boundaries to enigmail upstream, with a patch].
    95  * Recommending the use of inline PGP is not a responsible recommendation, given that inline PGP doesn't adequately conceal the structure of the message or the names of any attachments, and that it allows undetectable tampering of the content-type of each message part, which might cause arbitrary misinterpretations of signed material.