Emails are e2e encrypted if you send to an other nostr user.

Of course, WKD is the protocol to use for this.

I was talking about creating the WKD entry and others things like folders, labels, signatures...

Are you writing specifications so people can easily understand your protocol without doing some kind of reverse engineering?

Hello, I would like to implement PGP in Nmail. Are you publishing your protocol specification somewhere ? It would be useful so we can discuss about it and converge. You can use Openspecsif you want 😉
https://openspecs.uid.ovh/

Private aliases were never migrated to the new bridge architecture. Thank you for this precious information, it's now resolved.

I enabled DNSec for both domains. About the emails that were never reaching the inbox, I fixed it today.

Github was connecting to the bridge but my bridge was refusing the email because the from address was too long (above 64 characters before the "@"). Typically, the issue occurred when using the base36 hex or npub format as your address.

Here is a documentation to self host a bridge https://nostrmail.org/self-host

Does the server responded or it is an empty screen ?

I created it because no others relays care about DM privacy. I updated NIP 59 yesterday to fix a privacy issue. And implemented the updated spec today inside the relay.

https://openspecs.uid.ovh/spec/npub1kg4sdvz3l4fr99n2jdz2vdxe2mpacva87hkdetv76ywacsfq5leqquw5te/nip-59

Not at the protocol level. I see 2 solutions:

Remote signer, run a bunker on your key and give the other npub a connection scoped to nip44_decrypt only. They read your mail, they never hold your nsec, and you can revoke the connection any time. Closest thing to real read delegation today.

Auto-forward. Your client or a script decrypts and re-wraps incoming mail to their npub. Works with any client on their side, but the copy is signed by you, so the original sender proof is lost.