Changes between Version 45 and Version 46 of torbirdy


Ignore:
Timestamp:
May 22, 2013, 4:03:08 AM (7 years ago)
Author:
sukhbir
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • torbirdy

    v45 v46  
    6767 * On Windows and OSX download and install the [https://www.torproject.org/download/download.html.en Vidalia Bundle] and make sure Vidalia starts automatically at system boot.
    6868 * On Unix, Linux and BSD you should use your distributor's packages or if available the ones [https://www.torproject.org/download/download-unix.html.en provided by the torproject].
    69  * Regardless of the OS, make sure Tor is running with default client settings (`SocksPort` is listening on `127.0.0.1:9050`).
     69 * Regardless of the OS, make sure Tor is running with default client settings (`SocksPort` is listening on `127.0.0.1:9150`).
    7070
    7171 2. Install the TorBirdy extension:
     
    7979If things don't work for you:
    8080
    81  1. Make sure Tor is running and listening on `127.0.0.1` (`localhost`) on port `9050`.
     81 1. Make sure Tor is running and listening on `127.0.0.1` (`localhost`) on port `9150`.
    8282 1. Use Vidalia's "Tor Network Map" to confirm that something is trying to use the Tor instance to connect to an SMTP/ POP3/ IMAP port while sending/fetching emails. If nothing is using your running Tor instance, Thunderbird is not connecting to your running Tor instance correctly. This could have the following reasons:
    8383  * tor is not running
    84   * tor's `SocksPort` is not running on the expected port `127.0.0.1:9050`.
    85   * TorBirdy was configured to connect to something else then `127.0.0.1:9050`
     84  * tor's `SocksPort` is not running on the expected port `127.0.0.1:9150`.
     85  * TorBirdy was configured to connect to something else then `127.0.0.1:9150`
    8686 1. If you see Thunderbird connecting to Tor and it is still not working, try hitting the "New Identity" button in Vidalia; it might be the case that the mailserver you are trying to connect to does not like your source IP address (bad exit node)
    8787