Support for custom email domains

[ajhalili2006]

About this issue

It may be a bad idea to mess around DMARC to allow sending emails via Nest and use Cloudflare Email Routing to forward emails to there, especially there will be a chance it is a future abuse vector, so I would recommend adding support for custom email domains via nest email CLI commands, a la Uberspace.

Prior art / related resources

• Original message on Slack: https://hackclub.slack.com/archives/C056WDR3MQR/p1728919849781559
• Deliverability report when sending from custom domain via Roundcube: https://mxtoolbox.com/deliverability/fdaa3e3a-7dda-4817-ad85-01dac1c48581
• Put customs domains in a queue for DNS checking instead of domain spamming  #78

[MathiasDPX]

a la Uberspace

You're french ?

[ajhalili2006]

a la Uberspace

You're french ?

@MathiasDPX Nah, it's just my autistic vocabulary being cooked right now. Also Uberspace might be those who want to looking for a hosting platform and a pubnix/tilde-like Linux experience.

[MathiasDPX]

@ajhalili2006 Lul ok "a la" is similar to "like" in french

[ajhalili2006]

Let me drop some replies from the original Hack Club Slack thread:

On 2025-03-25 at 17:25:19 (GMT+8), 9pfs (@hello-smile6) said:

We could automatically provision DKIM, but that'd be an extremely large pain, and other than that it's hard to beat the status quo, I think.

On 2025-03-25 at 17:34:46 (GMT+8), Andrei Jiroh Halili (@ajhalili2006 - OP) said:

Another option might be reuse Nest's DKIM keys via CNAME records

[dispherical]

I think this is supported manually now