I2P email can hide network location from ordinary internet observers and support communication inside the I2P network. It does not make the contents of every message end-to-end encrypted, and it does not erase the trust you place in the mail service, client, operating system, or recipient.
The safest setup is to treat I2P as the transport layer and OpenPGP as an optional content-encryption layer for correspondents who manage keys correctly.
What you need
- A current I2P router from the official I2P project.
- An account with an I2P mail provider, created through its current I2P site.
- Thunderbird on the same computer as the I2P router.
- The exact SMTP and POP3 tunnel ports shown in your own I2P Router Console.
Older guides often copy local ports such as 7659 and 7660. Those may be defaults for a particular bundle, but verify the live tunnel configuration instead of assuming.
1. Confirm that I2P is healthy
Open the I2P Router Console, normally on the local machine, and wait until the router is integrated into the network. Check that the mail client tunnels are running.
On Linux you can also inspect listeners:
ss -ltnp | grep -E '7659|7660'
If the ports differ, use the values from the console in every later step.
2. Add the account to Thunderbird
Open Account Settings → Account Actions → Add Mail Account and choose manual configuration.
Use the provider's current account name and these connection principles:
Incoming mail
- Protocol: POP3 if that is what the I2P mail tunnel exposes
- Hostname: 127.0.0.1
- Port: the local POP3 tunnel port
- Connection security: None on the loopback hop, unless your tunnel explicitly provides TLS
- Authentication: Normal password only if required by the provider
Outgoing mail
- Protocol: SMTP
- Hostname: 127.0.0.1
- Port: the local SMTP tunnel port
- Connection security: None on the loopback hop, unless documented otherwise
- Authentication: use the provider's required method
Using 127.0.0.1 matters: Thunderbird talks only to the local I2P router, which carries the connection onward through I2P.
3. Test in stages
First send a message to your own I2P address. Then test with another I2P user. If the provider offers clearnet delivery, test that separately; cross-network gateways introduce another trusted party and can expose metadata.
Check the I2P tunnel status and Thunderbird's error console before changing multiple settings at once.
Mobile warning
An Android phone's 127.0.0.1 is the phone itself, not the I2P router running on your desktop. K-9 Mail works only if an I2P router and suitable mail tunnels are running locally on the phone or you deliberately expose a tunnel—which creates additional security risk. Do not point a phone at unauthenticated mail ports on your LAN or the public internet.
What this setup does not protect
- Subject lines and mail headers may remain visible to service operators.
- A compromised endpoint can read messages before encryption or after decryption.
- Writing style, timing, contacts, and message content can identify you.
- Forwarding mail to ordinary internet addresses leaves the I2P environment.
- Opening remote images can reveal that a message was read.
Disable automatic remote content in Thunderbird and separate identities that must not be correlated.
Optional OpenPGP
Thunderbird includes OpenPGP support. Verify a correspondent's fingerprint through a separate trusted channel before encrypting sensitive mail. Encryption protects content, not all metadata, and a lost private key can make old messages unreadable.
The useful rule is simple: I2P can protect the route; OpenPGP can protect message content; disciplined endpoint and identity practices protect the user. None of those layers replaces the others.
For a broader privacy architecture, read using I2P inside Whonix.