lnemail
LNemail

We had some downtime today, sorry for the inconvenience.
We self host the server handling the emails and the payments. And we use a VPS from a privacy friendly company (@nprofile…3j25 ) in front of it.
This means it's very hard for anyone to get your emails, and trust is as minimized as it can technically be.
But whenever the VPS fails or our self hosted server needs maintenance, there is downtime. At least you now know that it's for a good reason.
Thanks for your support!

2026-05-07 15:12:49 UTC

- reply

It's back now, sorry for the inconvenience.

2026-04-29 16:19:52 UTC

LNemail improvements just dropped:
- Recover token option from the inbox page.
- Simpler token format. Easier to store and without potentially confusing charcaters (l I). Example: lne_17Z1E-1V87W-VNGCH-KW9BD-3ENE2 (Crockford Base 32).
- Improved login/sign up flow so that password managers automatically suggest to store email and token.
Thanks to all for the ideas!

2026-04-13 06:26:22 UTC

Our VPS provider will do maintenance that will affect LNemail's availability.
The maintenance window is scheduled for April 17, 2026, from 12:00 to 15:00 CET

2026-03-16 08:34:47 UTC

- reply

They might be your provider's IPs. In any case, all we know is that the simple request `curl -v https://lnemail.net` does not work from LNVPS machines but does work from everywhere else. So there is a problem, just can't tell you what it is exactly. Any ideas?

2026-03-03 09:17:57 UTC

- reply

@nprofile…04za this still doesn't work.
MTR from an external server to our VM reaches your internal routers successfully but then hits a dead end inside your network:
```
5.|-- 185.116.108.126 0.0% ← your router
6.|-- 185.116.108.137 0.0% ← your router
7.|-- ??? 100.0% ← dropped inside your network
```
Separately, MTR from our VM outbound shows 25–45% packet loss at hops 7–8 through Hurricane Electric (195.66.224.21, 184.104.197.185) toward the same destination range. Inbound packets reach your network but are not delivered to the VM. Please investigate internal routing and your HE peering toward 94.156.119.0/24.
FYI @nprofile…3j25

2026-03-01 10:42:38 UTC

Undergoing some maintenance, we'll be right back!

2026-02-25 13:28:52 UTC

- reply

LNemail is way better for privacy than those!

2026-02-25 13:27:23 UTC

- reply

Should be fixed now!

2026-02-24 13:53:41 UTC

- reply

Nothing special on our side. Hosted at @nprofile…3j25
LNemail does work well from any other place and has no special configuration(s). Any ideas on what could be going on?

2026-02-24 06:15:42 UTC

- reply

The curl to the Debian extrafiles now works, but `curl https://lnemail.net/api/v1/health -v` still doesn't.
All valid HTTP(s) requests should work, regardless of the TLS key agreement used. Otherwise it indicates that there's still a network misconfiguration.
Thanks for the progress!

2026-02-23 21:37:55 UTC

- reply

Thanks for the hint! Should be fixed: https://clawhub.ai/lnemail/lnemail
Added the skill file at https://lnemail.net/skill.md

2026-02-23 21:01:48 UTC

- reply

Nice progress. Not sure what distro the original report users were using:
nevent1qqs8vvsux6lj6m49atqxpul8tnlpxpy769ywyclemnwyqwh0cvwcatqfytcvd
And also @nprofile…g5jd from another VM.

2026-02-23 20:05:35 UTC

- reply

I've created a fresh VM with Debian 13 and without running anything else, reproduced the error:
```
debian@VM1159:~$ curl -v https://deb.debian.org/debian/extrafiles
* Host deb.debian.org:443 was resolved.
* IPv6: 2a04:4e42:4b::644
* IPv4: 151.101.62.132
* Trying [2a04:4e42:4b::644]:443...
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS alert, decode error (562):
* TLS connect error: error:0A000126:SSL routines::unexpected eof while reading
* closing connection #0
curl: (35) TLS connect error: error:0A000126:SSL routines::unexpected eof while reading
debian@VM1159:~$ ping -M do -s 1422 94.156.119.69
PING 94.156.119.69 (94.156.119.69) 1422(1450) bytes of data.
1430 bytes from 94.156.119.69: icmp_seq=1 ttl=61 time=18.7 ms
1430 bytes from 94.156.119.69: icmp_seq=2 ttl=61 time=18.6 ms
1430 bytes from 94.156.119.69: icmp_seq=3 ttl=61 time=18.8 ms
1430 bytes from 94.156.119.69: icmp_seq=4 ttl=61 time=18.6 ms
1430 bytes from 94.156.119.69: icmp_seq=5 ttl=61 time=18.5 ms
1430 bytes from 94.156.119.69: icmp_seq=6 ttl=61 time=18.5 ms
1430 bytes from 94.156.119.69: icmp_seq=7 ttl=61 time=18.6 ms
1430 bytes from 94.156.119.69: icmp_seq=8 ttl=61 time=18.7 ms
^C
--- 94.156.119.69 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7013ms
rtt min/avg/max/mdev = 18.536/18.632/18.762/0.070 ms
debian@VM1159:~$ ping -M do -s 1423 94.156.119.69
PING 94.156.119.69 (94.156.119.69) 1423(1451) bytes of data.
^C
--- 94.156.119.69 ping statistics ---
9 packets transmitted, 0 received, 100% packet loss, time 8189ms
```

2026-02-23 13:32:47 UTC

- reply

A few users have reported this from different instances. It should be possible to reproduce from any VPS in the IE region, with the curl command to the large debian file.

2026-02-21 23:22:47 UTC

https://blossom.primal.net/c080706e55cb2f76e37eae259a14098f7a75ddbacd6a022730d068cabd933d0c.png
https://www.mail-tester.com
https://blossom.primal.net/7341c5c4a75d02da74137e121bbda6786c80e5f9f8cf5764c72d5dec44e8ab8c.png

2026-02-21 22:38:55 UTC

- reply

The website and API are also available trough Tor, maybe with even better uptime: http://lnemailv7hfb2txbk7qihz32p4j376wv7pn2xa3nmfwj6lrdhs5nf3ad.onion/

2026-02-21 21:36:01 UTC

- reply

FYI @nprofile…etsy @nprofile…g5jd

2026-02-21 21:34:46 UTC

@nprofile…04za there's a networking issue affecting LNVPS instances that's blocking connectivity to several external hosts.
Root cause: ICMP "Fragmentation Needed" messages (type 3, code 4) are being dropped before reaching tenant VMs, breaking Path MTU Discovery (PMTUD).
Details:
- LNVPS VMs have an effective path MTU of 1450, not 1500
- When a VM sends packets exceeding this MTU, the network correctly drops them, but never sends back the ICMP type 3/code 4 "Fragmentation Needed" response that TCP relies on to detect the limit
- Without these ICMP messages, TCP sessions stall or reset when talking to peers with MTU < 1500 (e.g. during large downloads or `iperf -R`)
- The filter appears to be somewhere between the hypervisor uplink and the VM's `eth0`, likely at the VXLAN/GRE tunnel layer or upstream border
Reproduced via:
```
ping -M do -s 1422 94.156.119.69 → 4/4 received (within MTU)
ping -M do -s 1423 94.156.119.69 → 0/4 received (exceeds MTU, silently dropped)
tcpdump 'icmp[0] == 3' during probe → 0 packets (no ICMP unreachables arriving at eth0)
```
You can reproduce this directly: `curl -v https://deb.debian.org/debian/extrafiles` from any LNVPS machine will stall. `apt` on Debian is broken for the same reason.
Fix (either of):
1. Allow ICMP type 3 code 4 through to tenant VMs
2. Configure MSS clamping at the hypervisor level for all tenant VMs on this host
This is what's preventing OpenClaw instances from reaching LNemail, and many other places!

2026-02-21 16:37:16 UTC

- reply

Yes, we arrived to the same conclusion. Added the agent recipe to https://clawhub.ai/lnemail/lnemail

2026-02-21 15:46:58 UTC

- reply

Added! https://clawhub.ai/lnemail/lnemail

2026-02-21 14:12:44 UTC

- reply

It's only meant for LLMs, see the landing page for humans. The mix between a .txt extension but with MarkDown format comes from this spec: https://llmstxt.org/

2026-02-21 13:54:05 UTC

- reply

Big thanks for the idea @nprofile…etsy!

2026-02-21 13:53:34 UTC

AIs welcome! Easiest platform to get a fully functional email account paid in Bitcoin through the Lightning Network. Just 1000 sats per year. Fully programmable and accesible through API.
Here are the instructions for our LLM friends: https://lnemail.net/llms.txt
#OpenClaw #AI #LLM #agents

2026-02-21 13:50:21 UTC

- reply

Of course we don't! There is not WAF or any fingerprinting done. Can be used with curl as described in the front page: https://lnemail.net/
Not sure what the error could have been, can you share the request or timestamps?
In any case, we have just added the llms.txt as suggested: https://lnemail.net/llms.txt
Thanks!

2026-02-21 13:33:21 UTC

- reply

On it! Thanks for the idea.

2026-02-15 20:26:23 UTC

- reply

Our VPS provider has small outages from time to time. We monitor the service and are aware of the downtime.
If it ever lasts too long please ping us!

2026-02-15 20:24:33 UTC

New update is out. Features:
- HTML email rendering (easier to click on links and more)
- Downloading received attachments and previewing them if plaintext
- Sending attachments up to 8MB
Thanks for your support and ideas :-)

2026-02-15 14:56:07 UTC

- reply

Good point. Working on it!

2026-02-15 14:51:07 UTC

- reply

yes!

2025-11-25 07:58:18 UTC

We had some downtime in the last hours. Everything is back to normal now :-)

2025-11-23 21:57:38 UTC

We have improved the feedback when sending emails, so that you get confirmation on the email being delivered.
Additionally, you can also see a send history and their status for the recently sent ones. All logs and sent emails are cleaned up after 30 days.
We also support WebLN everywhere to trigger browser plugins and facilitate payments. Apart from that there have been some bug fixes and minor improvements.
What should we improve next? Support for sending attachments?
Here are some screenshots:
https://blossom.primal.net/2492f5def916203115fcc803af6dc3341582758838fb86cc2025c08f33403e7c.png https://blossom.primal.net/4b6ca80db4d2fbb0c54c3c4d0bf6553688aa5d3f65cd9e9105f6ade43d846ecf.png https://blossom.primal.net/1e2a52ed38891264de24147652c20097cb008bb71567b72d797d40fcb394203d.png https://blossom.primal.net/af7b827f5c2f8d927f9a98f626b8ff1fa78dceb38c94f9725bf903d642f8d91f.png

2025-11-17 08:29:18 UTC

- reply

It must have been a hiccup! LNemail is here to stay 😎

2025-10-30 19:27:50 UTC

LNemail now supports responding to emails! An important feature that you've requested.
Feel free to drop more ideas here or as issues: https://github.com/lnemail/lnemail/issues/

2025-09-11 12:24:32 UTC

- reply

Have a look at https://lnemail.net/ 😎

2025-09-09 10:04:04 UTC

If you forgot to copy your access token when creating an LNemail account, don't worry!
**There are several ways to get your access token:**
1. From the LN invoice memo
2. Run `localStorage.getItem('lnemail_access_token')` in browser console (right-click page > inspect > console > paste & enter)
3. Check API requests in Network tab - look for Authorization header after `Bearer `
The token is safely stored in your browser's local storage. It's not a cookie that expires so you will always be able to login with that browser as long as you don't delete the site data.

2025-08-23 20:00:27 UTC

- reply

Happy to hear!

2025-08-23 19:57:34 UTC

- reply

Working now, thanks for the warning.
Must have been sporadic downtime. The service is monitored and we get notified whenever something is down.
Currently at 99.93% uptime for the last 30 days.

2025-08-23 15:15:47 UTC

LNemail: Improved inbox frontend
https://lnemail.net
Hi folks!
@Alice_and_the_Wonderland has developed an improved LNemail web client. And we have now made it the official inbox. See https://stacker.news/items/1023808 for the original post.
Here's a screenshot:
![screenshot](https://m.stacker.news/105501)
Way better than the original one. Many thanks!
Feel free to open feature/improvement requests and pull requests at https://github.com/lnemail/lnemail
https://stacker.news/items/1091364

2025-06-29 08:24:42 UTC

If you've enjoyed the service, please leave a review! https://kycnot.me/service/lnemail
Let's increase the anonymity set by getting to more users😝

2025-06-16 20:31:57 UTC

- reply

What's the use case?

2025-06-13 15:18:09 UTC

- reply

LNemail now supports removing emails (single or bulk). The overall design has also been improved.
Thanks for the idea!
#nevent1q…8dye

2025-06-12 19:14:14 UTC

LNemail is up and chilling 😎
We don't use Cloudflare, CDNs, ...

2025-06-11 17:15:46 UTC

- reply

Good idea!
Automatically after some time or just a button next to each email to manually click on? I'm guessing the latter but just to be sure.

2025-06-10 13:26:08 UTC

We're Back Online🚀
Our email services have been fully restored. The networking issue at Mynymbox has been resolved and all systems are now operational.

2025-06-10 07:53:02 UTC

LNemail is down.
There seems to be a networking problem at @npub1y69…wae6 (our VPS provider).

2025-06-08 20:49:42 UTC

LNemail got listed on https://bitcoin-vps.com/#Email-providers !

2025-06-06 20:47:49 UTC

- reply

Out of Beta! Stable and monitored. Web UI is complete and all features implemented (receiving, sending, marking as read).
Anything left?

2025-06-06 07:30:06 UTC

LNemail has been approved on https://kycnot.me (@npub188x…gcqf)!
https://kycnot.me/service/lnemail

2025-06-03 15:53:04 UTC

If anyone wants a full fledged email account (IMAP/POP3 + SMTP) with unlimited sending, feel free to reach out.
The idea has been suggested multiple times but it's not clear if there's enough demand for it. It can be enabled manually as an experiment for now.

2025-06-01 20:02:38 UTC

- reply

Thanks!
100 sats per message sent. The service is mostly oriented for signing up to places or have a “burner phone” private email address.
We'll see how the service evolves. Maybe people want a regular email with IMAP/POP3 and a subscription or maybe something like this is enough.
For now, this is an easy way of preventing service abuse for sending spam.

2025-06-01 19:49:28 UTC

Two great news:
- Added support for SENDING emails.
- LNemail is now officially out of beta. Stable and monitored.
Thanks you all for your ideas and support. Enjoy the service!

2025-06-01 10:33:58 UTC

📧 LNemail just got better!
New features:
• **Read/Unread status** - see which emails are new at a glance
• **Attachment support** - view text attachments directly in emails (useful for GPG signatures)
• **Smart sorting** - newest emails show first

2025-05-27 17:13:59 UTC

> No KYC, Ever: We will never require or collect personal identification information from our users.
> Anonymous Operation: The service operators remain anonymous and are not subject to any specific jurisdiction, operating under natural law principles.
https://lnemail.net/tos

2025-05-25 20:52:00 UTC

LNemail is now open source! https://github.com/lnemail/lnemail
There is a pretty cool development environment that sets up a Bitcoin node with a testnet, mines, and funds some lightning nodes to be able to test payments during development. Apart from the actual LNemail server stack and mail server.
More improvements to come soon™. Check the issues to see what's next.

2025-05-20 15:17:46 UTC

- reply

Nice. In any case I'll set up better monitoring to maintain high uptime before going out of the Beta stage.

2025-05-20 15:11:28 UTC

- reply

Great!
The nice thing about SMTP is that other servers retry the delivery until it works. So small downtimes don't lead to data loss.

2025-05-20 14:49:50 UTC

- reply

Fixed it! Something related to networking got stuck.
Thanks for the report. Feel free to DM if you need further assistance.

2025-05-19 18:40:07 UTC

- reply

Oh right... The new drama.
Thanks :-)

2025-05-19 16:15:30 UTC

- reply

2025-05-19 16:14:33 UTC

- reply

yes😎

2025-05-19 16:11:40 UTC

- reply

Might enable sending as well soon. Some other users showed interest as well. It's amazing how many problems disappear (service abuse) when the incentives are aligned by paying sats for a service.

2025-05-19 13:39:56 UTC

- reply

I didn't know that, thanks for the info.
This would then mean becoming a full-fledged email provider, but that's OK if there's the demand for it.
As a user, do you prefer a “premium” account that grants you unlimited IMAP access for receiving and sending. Or just the option in the “standard” account to pay for sending each time from the web UI?
Thanks a lot for your input BTW!

2025-05-19 12:53:21 UTC

- reply

Proton or Tuta offer full no-KYC email accounts for free. Limited to one free account per individual by their T&C. It takes a few more clicks to create one and they are harder to automate (creation and usage). But they are probably better if you plan on using them regularly.
Do you think sending emails from LNemail still make sense anyway?

2025-05-19 06:07:22 UTC

- reply

Thanks for the suggestion!
The server is technically ready for sending emails, and a small sats payment per email could deter spam.
But it would shift LNemail from a disposable inbox to a more full-featured email service though, which wasn't the original focus.
Did you have a specific use case in mind for sending?

2025-05-18 17:34:39 UTC

LNemail just launched! - a private inbox that lasts 1 year for 1,000 sats (renewable).
Features:
- No personal info required
- Plain text emails only (no HTML/attachments)
- Access via web or API
- Receive-only inbox
Perfect for account verification, 2FA, and newsletter subscriptions without the 10-minute limitation of other disposable services.
⚠️ Currently in BETA - use at your own risk
Try it: https://lnemail.net
Feedback welcome!