0 Fork 0

Files

T

History

Ariel Yu f6d82ffd01 chore(cloudflare-email-relay): Add ignore of node_modules (#138 )

node_modules in cloudflare-email-relay should be ignored as well.

Signed-off-by: Ariel Yu <ariel@ariels.xyz>

2026-10-14 15:53:15 +07:00

src

improve email attachments

2026-09-28 14:54:46 +07:00

package-lock.json

chore(cloudflare-email-relay): Add ignore of node_modules (#138 )

2026-10-14 15:53:15 +07:00

package.json

feat(self-host): run Mailflare as a Docker container on any host

2026-09-12 14:34:11 +03:00

README.md

feat(self-host): run Mailflare as a Docker container on any host

2026-09-12 14:34:11 +03:00

tsconfig.json

feat(self-host): run Mailflare as a Docker container on any host

2026-09-12 14:34:11 +03:00

wrangler.jsonc

feat(self-host): run Mailflare as a Docker container on any host

2026-09-12 14:34:11 +03:00

README.md

Mailflare email relay

A small Cloudflare Worker for self-hosted Mailflare installs that want to keep receiving mail through Cloudflare Email Routing (no port 25, no MX changes).

npm install, then npx wrangler secret put MAILFLARE_URL (your server's public URL, e.g. https://mail.example.com) and npx wrangler secret put INBOUND_WEBHOOK_SECRET (the same value as in the server's .env.docker).
npm run deploy.
In the Cloudflare dashboard, under Email Routing for your zone, route the catch-all, or the addresses you want, to the mailflare-email-relay Worker.

Each message is posted to /api/inbound on your server with an HMAC signature. The server stores it and replies with the routing decision, so reject rules and forwarding rules still act at Cloudflare's edge. If the server is unreachable the message is rejected with a retry hint.