This is the code for the Cloudflare Workers that handle the sending and receiving of emails for EmailThing.
This worker is responsible for receiving emails sent to the domain. It uses the fetch API to send the email to the front-end app.
To set this up, you need to add a route in your Cloudflare dashboard to point to this worker. You then will need to create a Cloudflare Worker to handle this route. Make sure to add the auth environment variable to the worker with the same value as the custom domain settings gave. You will also be able to add the forward environment variable to the worker and if provided, Cloudflare will also forward the email to the given address.
If self hosting and you want a default domain, you will need to add the zone and internal query parameter to the route and set it to the domain you want to (ie riskymh.dev + 1 respectively).
For anyone curious, all this is doing is receiving the email and then sending the raw body to the front-end app.
Note: This worker is what is recommended to use for custom domains (even if not self hosting).
Warning
This no longer works and is only left for documentation purposes.
Only needed if you are selfhosting EmailThing (if you found this page while trying to add your domain, you don't need this worker)
This worker is responsible for sending emails. It uses the fetch API to send the email to the MailChannels API. You can think of this as a proxy as thats all it is doing. Make sure to add the auth environment variable to the worker with the same value as the EMAIL_AUTH_TOKEN in the front-end app.
Refer to the Mailchannels Transactional API documentation for more information on how to send emails.
As you have full control with the emails, you can decide which mailbox to send to (if any). This means you can have multiple mailboxes for one domain.
Note: This is more or less abusing the free deal that was given to Cloudflare workers.