Add automated Cloudflare Email Worker for VoidOne

[mohammedmk3900-rgb]

Summary

• Add a dedicated Cloudflare Email Worker under email-worker/ for inbound VoidOne support aliases.
• Add routing policy, sender/domain blocklists, attachment policy checks, structured audit logs, optional Slack alerts, and optional KV persistence.
• Add policy unit tests.
• Add a GitHub Actions workflow that tests on PR changes and deploys to Cloudflare after the changes are merged to main, once the required Cloudflare repository secrets exist.

Deployment requirements

Set repository Actions secrets:

• CLOUDFLARE_API_TOKEN
• CLOUDFLARE_ACCOUNT_ID

After first deployment, configure GMAIL_INBOX (and optional route-specific destinations) in Worker Variables and Secrets before enabling Email Routing rules. See email-worker/README.md.

Safety notes

This is a policy-based attachment filter, not antivirus. MIME parse failures are forwarded with a warning by default; STRICT_MIME_SCAN=true changes that to reject. No message body or subject is written to audit logs.

Validation

The workflow runs Node policy tests. Live delivery still requires Cloudflare account configuration and end-to-end testing.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.