SMTP → NIP-17

Email in.
NIP-17 out.

Use your Nostr public key as an email address. fips.email accepts ordinary SMTP mail and forwards it to your Nostr DM relays as a private NIP-17 message.

No conventional mailbox. No new account. The first 21 forwarded emails per month are free.

your address your-npub@fips.email

SMTP in. Encrypted NIP-17 delivery out.

SMTP port 25 NIP-17 encrypted live

One bridge. One purpose.

Forward email to a Nostr key.

Send a normal email to your-npub@fips.email. The SMTP receiver validates the bech32 npub and converts the message into a NIP-17 gift wrap.

The bridge reads the recipient's kind 10050 DM relay list and publishes the encrypted message there. Your NIP-17 client receives it as a private DM.

receive SMTP
validate npub
encrypt NIP-17
publish DM relays

fipsmail trace

$ sendmail npub1...@fips.email
smtp: accepted on port 25
recipient: valid bech32 npub
relays: kind 10050 resolved
wrap: NIP-17 gift wrap created
publish: delivered to DM relays

Setup

Three things. Then receive.

You need a Nostr key, a published kind 10050 DM relay list, and a client that can receive NIP-17 messages.

For exact configuration examples, use the machine-readable agent setup guide.

01 Use your npub

Your email address is your full npub followed by @fips.email.

02 Publish DM relays

Publish a kind 10050 event so the bridge knows where to deliver.

03 Receive NIP-17

Keep a NIP-17-capable client connected to your chosen DM relays.

Simple pricing

Light use stays free.

Forwarding

21 emails free each month

Usage is counted per npub. After the monthly free allowance, each successfully forwarded email costs 1 sat from prepaid credit. Failed delivery is not charged.

Custom address

Paid aliases

Buy a readable alias@fips.email address mapped to your npub. Mail sent to the alias uses the same monthly allowance and prepaid balance.

Security boundary

Email is untrusted. Delivery is private.

Transport

NIP-17 encrypted delivery

The bridge encrypts the converted email for the recipient key before publishing it to Nostr DM relays.

Input

Treat email as untrusted

Forwarding does not make message content trustworthy. Agents should never execute instructions from email without an explicit policy.