Can not check I2P mail with Torbirdy activated (sending I2P mail works fine)

[lunokhod]

I am trying to configure Torbirdy to check an email account at a Tor hidden service, as well as a second account on i2p (127.0.0.1 port 7660).

When torbirdy is not activated, I can both send and receive mail via i2p (on 127.0.0.1, ports 7559 and 7660). However when torbirdy is activated, I can only send i2p mail, but not check it. I have verified 100 times that the ports are correct, and that 127.0.0.1 is in the "no proxy" list when torbirdy is activated.

I can only imagine that this is bud with torbirdy.

[sukhbir]

Just a thought: TorBirdy disables automatic checking of emails. Can this be an issue? If not, what happens when you click on the "Get Messages" button? Is there some error or nothing happens?

[anonimal]

Replying to sukhbir:

Just a thought: TorBirdy disables automatic checking of emails. Can this be an issue? If not, what happens when you click on the "Get Messages" button? Is there some error or nothing happens?

Automatic checking does not appear be the issue. Clicking "Get Messages" also produces the same result: no errors, nothing happens.

A tcpdump reveals that, when attempting to receive mail on a local port, a socket connection is never successfully made - nor does it appear to be attempted (at the socket level). Though, as lunokhod reported, sending mail is successful. With that said, this ticket appears to not be specific to I2P (e.g., app-agnostic; same results with ssh, etc.).

Site-note: when adding 127.0.0.1 or localhost to the No Proxy for: list, the value is not saved after restarting Thunderbird. Could this be related to #10684 or #16935? If not, perhaps a new ticket is in order.

[sukhbir]

Replying to anonimal:

Replying to sukhbir:

Just a thought: TorBirdy disables automatic checking of emails. Can this be an issue? If not, what happens when you click on the "Get Messages" button? Is there some error or nothing happens?

Automatic checking does not appear be the issue. Clicking "Get Messages" also produces the same result: no errors, nothing happens.

A tcpdump reveals that, when attempting to receive mail on a local port, a socket connection is never successfully made - nor does it appear to be attempted (at the socket level). Though, as lunokhod reported, sending mail is successful. With that said, this ticket appears to not be specific to I2P (e.g., app-agnostic; same results with ssh, etc.).

Site-note: when adding 127.0.0.1 or localhost to the No Proxy for: list, the value is not saved after restarting Thunderbird. Could this be related to #10684 or #16935? If not, perhaps a new ticket is in order.

Let's revisit this issue. I know very little about I2P, so help me in reproducing this. What I2P mail service should I test this with?

[anonimal]

Hi sukhbir, for whatever reason I didn't get an email notification so I'm just reading this now.

I don't think you need I2P to test this. For example, try setting up two local socat instances on 127.0.0.1 (with the text output switch flipped) that forwards to your mail service, then create a Thunderbird account pointing to 127.0.0.1 and your respective local ports. Example:

socat -v TCP4-LISTEN:12345,fork TCP4:smtp.mail-host.tld:<their smtp port>
socat -v TCP4-LISTEN:23456,fork TCP4:pop3.mail-host.tld:<their pop3 port>

would mean you point your Thunderbird account to 127.0.0.1, port 12345 for SMTP, port 23456 for POP3, and using whatever encryption methods required. This will probably give you certificate warning/errors (I don't know, I haven't tested this with clearnet mail) but you'll (should) at least see that there's no output with the SMTP socat instance.

If instead you want to test with I2P, create an account at ​hq.postman.i2p then setup a Thunderbird account to point to 127.0.0.1 port 7659 for SMTP, port 7660 for POP3, no SSL/TLS/STARTTLS needed, transmit plain password for authentication (the transmitted "insecurely" option). If using ​Kovri, the current default ports will be 7661 for SMTP and 7662 for POP3.