Cloudflare Email Service Skill 安全审计

45For full CLI reference, run `npx wrangler email --help`. For Dashboard setup, see the [getting started docs](https://developers.cloudflare.com/email-service/get-started/).6

45Read the documentation for the selected task before implementing. Inspect the project's installed Wrangler and Agents SDK versions, configuration, and existing conventions first. Run `wrangler types` through the project's package manager after changing bindings; use its generated types instead of handwritten email interfaces. See [Workers TypeScript](https://developers.cloudflare.com/workers/languages/typescript/) for matching types to the project's compatibility date and flags. Do not upgrade dependencies just to match an example.6

125126export class MailboxDO extends DurableObject {127  async storeEmail(from: string, to: string, subject: string, body: string,128                   messageId: string, inReplyTo: string | null) {129    this.ctx.storage.sql.exec(130      `INSERT INTO emails (sender, recipient, subject, body, message_id, in_reply_to, date, read)131       VALUES (?, ?, ?, ?, ?, ?, datetime('now'), 0)`,132      from, to, subject, body, messageId, inReplyTo133    );134  }

126export class MailboxDO extends DurableObject {127  async storeEmail(from: string, to: string, subject: string, body: string,128                   messageId: string, inReplyTo: string | null) {129    this.ctx.storage.sql.exec(130      `INSERT INTO emails (sender, recipient, subject, body, message_id, in_reply_to, date, read)131       VALUES (?, ?, ?, ?, ?, ?, datetime('now'), 0)`,132      from, to, subject, body, messageId, inReplyTo133    );134  }

144145    await stub.storeEmail(146      message.from,147      message.to,148      parsed.subject || "(no subject)",149      parsed.text || parsed.html || "",150      message.headers.get("message-id") || "",151      message.headers.get("in-reply-to") || null,152    );153

173174  await env.EMAIL.send({175    to: original.sender,176    from: original.recipient,177    subject: `Re: ${original.subject}`,178    text: replyBody,179    html: `<p>${replyBody}</p>`,180    headers,181  });182}

3334```bash35npx wrangler email sending enable yourdomain.com36npx wrangler email sending dns get yourdomain.com   # Verify records37```38

102103## Sending from CLI / Agents104105```bash106npx wrangler email sending send \107  --from "agent@yourdomain.com" \108  --to "developer@company.com" \109  --subject "Deployment Complete" \110  --text "Your Worker was deployed successfully."111```112

114115```bash116curl "https://api.cloudflare.com/client/v4/accounts/${CLOUDFLARE_ACCOUNT_ID}/email/sending/send" \117  --header "Authorization: Bearer ${CLOUDFLARE_API_TOKEN}" \118  --header "Content-Type: application/json" \119  --data '{120    "to": "developer@company.com",121    "from": {"address": "agent@yourdomain.com", "name": "Build Agent"},122    "subject": "Deployment Complete",123    "text": "Your Worker was deployed successfully."124  }'125```

4041Add `"remote": true` to send real emails during `wrangler dev`:4243```jsonc44{ "send_email": [{ "name": "EMAIL", "remote": true }] }45```4647```bash48npx wrangler dev49```5051Emails are actually sent — use test addresses you control. Remove `"remote": true` before deploying.52