Cloudflare Temp Email

Cloudflare Temporary Email allows you to build a free temporary email service using Cloudflare. Key capabilities include:

• Private Deployment: Deploy using only a domain name with free hosting on Cloudflare. Features include password-protected mailboxes, user registration, and attachment support.
• High-Performance Email Parsing: Uses Rust WASM for extremely fast email parsing that supports various RFC standards and attachments.
• Notifications & Integration: Supports forwarding emails to Telegram or via Webhooks. The Telegram Bot includes mailbox binding, email viewing, and a Telegram Mini App.
• Email Sending: Supports sending text or HTML emails via UI, API, or SMTP, with DKIM signature support.

The project is built on the Cloudflare ecosystem using the following architecture:

System Configuration

• Database: Cloudflare D1
• Frontend Deployment: Cloudflare Pages
• Backend Deployment: Cloudflare Workers
• Email Routing: Cloudflare Email Routing

Technology Stack

• Frontend: Vue 3 + Vite + TypeScript
• Backend: TypeScript + Cloudflare Workers
• Mail Parsing: Rust WASM (mail-parser-wasm)
• Database: Cloudflare D1 (SQLite)
• Storage: Cloudflare KV + R2 (or S3)
• Proxy Service: Python SMTP/IMAP Proxy Server

Key Components

• Worker: Core backend service
• Frontend: Vue 3 user interface
• Mail Parser WASM: Rust email parsing module
• SMTP Proxy Server: Python email proxy service
• Pages Functions: Cloudflare Pages middleware
• Documentation: VitePress documentation site

To deploy the Cloudflare 一時メール service, you can use the official documentation or the GitHub Actions deployment guide.

For a quick deployment to Cloudflare Workers, use the provided deployment button which directs you to the Cloudflare Workers setup process.

• Official Documentation: https://temp-mail-docs.awsl.uk
• GitHub Actions Deployment Guide: https://temp-mail-docs.awsl.uk/en/guide/actions/github-action.html

To enable saving and downloading email attachments via S3 (or Cloudflare R2), you must configure an S3-compatible storage bucket and set the corresponding credentials as secrets in your Cloudflare Worker.

1. Create a Bucket: Create a bucket in Cloudflare R2 or another S3-compatible service.
2. Configure CORS: Ensure your R2 bucket has the correct CORS policies configured via the Cloudflare dashboard.
3. Generate Credentials: Obtain your ENDPOINT, Access Key ID, and Secret Access Key using Cloudflare R2 S3 tokens.
4. Set Secrets: Add the credentials to your Cloudflare Worker environment using wrangler secret put.

cd worker
pnpm wrangler secret put S3_ENDPOINT
pnpm wrangler secret put S3_ACCESS_KEY_ID
pnpm wrangler secret put S3_SECRET_ACCESS_KEY
# Note: Replace bucket with your bucket name
pnpm wrangler secret put S3_BUCKET

For UI deployment workers (v0.7.6 and later), you must modify the Compatibility flags in the Cloudflare dashboard:

1. Navigate to Settings -> Runtime.
2. Add the nodejs_compat compatibility flag.

When configuring your Cloudflare Worker environment variables, you must generate a secure JWT_SECRET. Use the following command to generate a 32-byte hex string:

openssl rand -hex 32

Create an application at Linux Do Connect to obtain your Client ID and Client Secret.

Note: Linux Do returns a user ID instead of an email. You must enable the Email Format Transformation feature to convert this ID into a valid email address for account registration.

To use the full AI extraction capabilities (including link extraction), you must provide a Workers AI binding to your Cloudflare Worker.

Option 1: via wrangler.toml Add the following configuration:

[ai]
binding = "AI"

Option 2: via Cloudflare Dashboard In your Worker settings, add a variable with:

• Variable name: AI
• Type: Workers AI

Fallback Behavior: If ENABLE_AI_EMAIL_EXTRACT is enabled but no AI binding is found, the system falls back to a built-in regex extractor. This fallback only extracts verification codes (auth_code) and does not extract links.