Bug #11226

I2P email in Thunderbird will not work with our default Tor proxy settings

Added by starscream 2016-03-13 11:25:51 . Updated 2019-11-29 10:59:52 .

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2016-03-13
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
I2P
Deliverable for:

Description

I2P Mails (xxxxx@mail.i2p) and Icedove will not work with TorBirdy enabled.

Solution right now is to disable TorBirdy to receive I2P Mails.

TorBirdy should not be disabled by the User or is this behavior expected?

It used to work before with Clawsmail and an older Tails Version.

Subtasks

History

#1 Updated by Anonymous 2016-05-16 08:17:45

Thanks for reporting this.

I confirm that this happens. It’s logical, Torbirdy wants to send all your mail traffic to localhost’s SOCKS proxy port, whereas i2p mail wants to connect to localhost 7660 (POP3) aand 7659 (SMTP).

I’m not sure how to handle this exactly. I don’t think it’s possible to configure Torbirdy to use i2p instead. From what i’ve seen it’s possible to use TorBrowser to access i2p websites, using proxy settings but i don’t think this is applicable for the mail use case.

So probably our best bet is either to disable Torbirdy in Tails when i2p is enabled or to document this at least.

#2 Updated by intrigeri 2016-05-16 10:43:41

> So probably our best bet is either to disable Torbirdy in Tails when i2p is enabled

Note that this would disable all protections provided by TorBirdy even for I2P users who happen to use Icedove, even if they use I2P for non-email use cases only. It can be a problem if they use Icedove for email (over Tor).

#3 Updated by Anonymous 2016-05-17 09:06:33

intrigeri wrote:
> > So probably our best bet is either to disable Torbirdy in Tails when i2p is enabled
>
> Note that this would disable all protections provided by TorBirdy even for I2P users who happen to use Icedove, even if they use I2P for non-email use cases only. It can be a problem if they use Icedove for email (over Tor).

So, that’s not a solution. I lack complete understanding of how i2p works, but i guess that in this case we’d need to configure TB to use another port to talk to i2p instead of talking to Tor.

#4 Updated by intrigeri 2016-05-17 10:13:24

  • Status changed from New to Confirmed

> i guess that in this case we’d need to configure TB to use another port to talk to i2p instead of talking to Tor.

FWIW, back in the days we were using the FoxyProxy add-on so that Tor Browser uses different proxies depending on the requested URL. It certainly brought some security issues, and we dropped it when we introduced the I2P browser. Something similar might be doable for I2P in Icedove (either such an add-on, or an email client dedicated to I2P). Anyway, formally speaking, I2P support is best effort, so don’t bother too much: if the I2P community wants this to be supported in Tails, we’re welcoming good patches :)

#5 Updated by Anonymous 2018-08-17 16:17:49

  • Subject changed from I2P and Icedove will not work with TorBirdy enabled to I2P and Thunderbirdd will not work with TorBirdy enabled

We don’t ship i2p currently, but as somebody is working on it, I’ll leave this ticket open, to be revisited in ~6 months.

#6 Updated by intrigeri 2019-11-29 10:59:52

  • Subject changed from I2P and Thunderbirdd will not work with TorBirdy enabled to I2P email in Thunderbird will not work with our default Tor proxy settings