PCX Review

Author: Oxyjun

src/content/docs/email-service/api/route-emails/email-handler.mdx

@@ -15,7 +15,7 @@ Process incoming emails using the `email()` handler in your Cloudflare Workers.
 
 Add the `email` handler function to your Worker's exported handlers:
 
-```typescript
+```ts
 interface Env {
 	EMAIL: SendEmail;
 }
@@ -36,11 +36,11 @@ export default {
 | `env`     | `object`                  | Worker environment bindings (KV, EMAIL, etc.) |
 | `ctx`     | `object`                  | Execution context with `waitUntil` function   |
 
-## ForwardableEmailMessage interface
+## `ForwardableEmailMessage` interface
 
 The `message` parameter provides access to the incoming email:
 
-```typescript
+```ts
 interface ForwardableEmailMessage {
 	readonly from: string; // Sender email address (envelope MAIL FROM)
 	readonly to: string; // Recipient email address (envelope RCPT TO)
@@ -61,7 +61,7 @@ interface ForwardableEmailMessage {
 <Tabs>
 <TabItem label="Basic properties">
 
-```typescript
+```ts
 export default {
 	async email(message, env, ctx): Promise<void> {
 		// Access email metadata
@@ -84,7 +84,7 @@ export default {
 </TabItem>
 <TabItem label="Reading content">
 
-```typescript
+```ts
 export default {
 	async email(message, env, ctx): Promise<void> {
 		// Read raw email content
@@ -115,7 +115,7 @@ export default {
 </TabItem>
 <TabItem label="Parse email content">
 
-```typescript
+```ts
 // Helper function to parse email content
 async function parseEmailContent(
 	message,
@@ -177,7 +177,7 @@ Forward incoming emails to verified destination addresses:
 <Tabs>
 <TabItem label="Simple forwarding">
 
-```typescript
+```ts
 export default {
 	async email(message, env, ctx): Promise<void> {
 		// Forward to a single address
@@ -189,7 +189,7 @@ export default {
 </TabItem>
 <TabItem label="Conditional forwarding">
 
-```typescript
+```ts
 export default {
 	async email(message, env, ctx): Promise<void> {
 		const recipient = message.to;
@@ -213,7 +213,7 @@ export default {
 </TabItem>
 <TabItem label="Multiple forwarding">
 
-```typescript
+```ts
 export default {
 	async email(message, env, ctx): Promise<void> {
 		const subject = message.headers.get("subject") || "";
@@ -239,7 +239,7 @@ export default {
 
 Add custom headers when forwarding:
 
-```typescript
+```ts
 export default {
 	async email(message, env, ctx): Promise<void> {
 		// Create custom headers
@@ -262,7 +262,7 @@ Send automatic replies using the Email Service binding:
 <Tabs>
 <TabItem label="Simple auto-reply">
 
-```typescript
+```ts
 interface Env {
 	EMAIL: SendEmail;
 }
@@ -293,7 +293,7 @@ export default {
 </TabItem>
 <TabItem label="Smart auto-reply">
 
-```typescript
+```ts
 export default {
 	async email(message, env, ctx): Promise<void> {
 		const sender = message.from;
@@ -357,7 +357,7 @@ Reject emails with a permanent SMTP error:
 <Tabs>
 <TabItem label="Simple rejection">
 
-```typescript
+```ts
 export default {
 	async email(message, env, ctx): Promise<void> {
 		const sender = message.from;
@@ -380,7 +380,7 @@ export default {
 </TabItem>
 <TabItem label="Content-based rejection">
 
-```typescript
+```ts
 export default {
 	async email(message, env, ctx): Promise<void> {
 		const subject = message.headers.get("subject") || "";
@@ -416,7 +416,7 @@ export default {
 
 Handle errors gracefully in email processing:
 
-```typescript
+```ts
 export default {
 	async email(message, env, ctx): Promise<void> {
 		try {

src/content/docs/email-service/api/send-emails/rest-api.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 import { Tabs, TabItem } from "~/components";
 
-The REST API allows you to send emails from any application using standard HTTP requests. Use it from any backend, serverless function, or CI/CD pipeline — no Cloudflare Workers binding required.
+The REST API allows you to send emails from any application using standard HTTP requests. Use it from any backend, serverless function, or CI/CD pipeline — no Cloudflare Workers binding is required.
 
 For the full OpenAPI specification, refer to the [Email Sending API reference](https://developers.cloudflare.com/api/resources/email_sending/methods/send).
 
@@ -143,9 +143,9 @@ A successful response returns the delivery status for each recipient:
 }
 ```
 
-- `delivered` - Email addresses to which the message was delivered immediately.
-- `permanent_bounces` - Email addresses that permanently bounced.
-- `queued` - Email addresses for which delivery was queued for later.
+- `delivered` - Email addresses to which the message was delivered immediately
+- `permanent_bounces` - Email addresses that permanently bounced
+- `queued` - Email addresses for which delivery was queued for later
 
 ## Error handling
 

src/content/docs/email-service/api/send-emails/workers-api.mdx

@@ -27,13 +27,13 @@ allowed_sender_addresses = ["noreply@yourdomain.com", "support@yourdomain.com"]
 
 </WranglerConfig>
 
-## send() method
+## `send()` method
 
 Send a single email using the `send()` method on your email binding.
 
 ### Interface
 
-```typescript
+```ts
 interface SendEmail {
 	send(message: EmailMessage | EmailMessageBuilder): Promise<EmailSendResult>;
 }
@@ -73,7 +73,7 @@ interface EmailSendResult {
 <Tabs>
 <TabItem label="Simple email">
 
-```typescript
+```ts
 interface Env {
 	EMAIL: SendEmail;
 }
@@ -82,7 +82,7 @@ interface Env {
 </TabItem>
 <TabItem label="Multiple recipients">
 
-```typescript
+```ts
 // Send to multiple recipients (max 50)
 const response = await env.EMAIL.send({
 	to: ["user1@example.com", "user2@example.com", "user3@example.com"],
@@ -96,7 +96,7 @@ const response = await env.EMAIL.send({
 </TabItem>
 <TabItem label="With CC and BCC">
 
-```typescript
+```ts
 const response = await env.EMAIL.send({
 	to: "customer@example.com",
 	cc: ["manager@company.com"],
@@ -117,7 +117,7 @@ const response = await env.EMAIL.send({
 <Tabs>
 <TabItem label="PDF attachment">
 
-```typescript
+```ts
 const response = await env.EMAIL.send({
 	to: "customer@example.com",
 	from: "invoices@yourdomain.com",
@@ -137,7 +137,7 @@ const response = await env.EMAIL.send({
 </TabItem>
 <TabItem label="Inline image">
 
-```typescript
+```ts
 const response = await env.EMAIL.send({
 	to: "user@example.com",
 	from: "marketing@yourdomain.com",
@@ -169,7 +169,7 @@ Handle email sending errors gracefully:
 <Tabs>
 <TabItem label="Single send errors">
 
-```typescript
+```ts
 export default {
 	async fetch(request: Request, env: Env): Promise<Response> {
 		try {
@@ -253,11 +253,11 @@ The following error codes may be returned when sending emails:
 | `E_HEADERS_TOO_LARGE`           | Headers payload too large               | Total custom headers exceed 16 KB limit                       |
 | `E_HEADERS_TOO_MANY`            | Too many headers                        | More than 20 whitelisted (non-X) custom headers               |
 
-## Legacy EmailMessage API
+## Legacy `EmailMessage` API
 
-The existing EmailMessage API remains supported for backward compatibility:
+The existing `EmailMessage` API remains supported for backward compatibility:
 
-```typescript
+```ts
 import { EmailMessage } from "cloudflare:email";
 import { createMimeMessage } from "mimetext";
 
@@ -286,7 +286,7 @@ export default {
 
 ---
 
-**Next steps:**
+## Next steps
 
 - See the [REST API](/email-service/api/send-emails/rest-api/) for sending emails without Workers
 - See [practical examples](/email-service/examples/) of email sending patterns

src/content/docs/email-service/concepts/deliverability.mdx

@@ -6,7 +6,7 @@ sidebar:
   order: 3
 ---
 
-import VerifiedEmails from "~/content/partials/email-service/_sandboxing.mdx";
+import {DashButton, Render} from "~/components";
 
 Email deliverability ensures your emails reach recipients' inboxes. Cloudflare Email Service handles bounces automatically and manages sender reputation to maximize delivery success.
 
@@ -37,7 +37,7 @@ Soft bounces are temporary failures that may succeed if retried:
 
 Cloudflare automatically retries soft bounces with exponential backoff over an extended period.
 
-<VerifiedEmails />
+<Render file="sandboxing" product="email-service" />
 
 ## Reputation management
 

src/content/docs/email-service/concepts/email-authentication.mdx

@@ -27,7 +27,7 @@ SPF works by:
 
 ## DKIM (DomainKeys Identified Mail)
 
-DKIM ensures that emails haven't been tampered with during transit by cryptographically signing them with your domain's private key.
+DKIM ensures that emails have not been tampered during transit by cryptographically signing them with your domain's private key.
 
 **How DKIM works:**
 

src/content/docs/email-service/concepts/email-lifecycle.mdx

@@ -36,7 +36,7 @@ flowchart LR
    - **SPF (Sender Policy Framework)**: Verifies that the sending IP address is authorized to send emails for the domain by checking DNS TXT records. This prevents domain spoofing and improves deliverability.
    - **DKIM (DomainKeys Identified Mail)**: Validates the email's cryptographic signature to ensure message integrity and authenticate the sender domain. This builds trust with recipient servers.
    - **DMARC (Domain-based Message Authentication)**: Applies domain owner policies for handling emails that fail SPF or DKIM checks, helping prevent phishing and brand impersonation while providing feedback reports.
-   
+
    These authentication mechanisms work together to establish sender legitimacy and protect against email fraud. Senders with low reputation scores may experience throttling or delayed processing.
 
 4. **Suppression list check:** The system checks the recipient against global suppression lists that include bounces, complaints, and unsubscribes. Recipients found on these lists are blocked from receiving the email.

src/content/docs/email-service/concepts/suppressions.mdx

@@ -9,7 +9,7 @@ sidebar:
 
 import { Tabs, TabItem } from "~/components";
 
-Suppression lists prevent emails from being sent to addresses that shouldn't receive them, protecting your sender reputation and ensuring compliance with anti-spam regulations.
+Suppression lists prevent emails from being sent to addresses that should not receive them, protecting your sender reputation and ensuring compliance with anti-spam regulations.
 
 ## Suppression lists
 
@@ -41,7 +41,7 @@ Cloudflare will automatically add email addresses to your account suppression li
 
 You may also manually add or remove email addresses from your suppression list as needed. The removal of email addresses that have been automatically added to your suppression list as a result of a spam complaint is limited to avoid abuse.
 
-## How does Email Service's automatic suppression work
+## Automatic suppression logic
 
 Cloudflare automatically suppresses addresses that:
 

src/content/docs/email-service/configuration/domains.mdx

@@ -379,10 +379,10 @@ Removing a domain will:
 
 ### Domain status indicators
 
-- **🟢 Active**: All records configured correctly
-- **🟡 Warning**: Some records missing or misconfigured
-- **🔴 Error**: Critical configuration issues
-- **⚪ Pending**: DNS propagation in progress
+- **Active**: All records configured correctly
+- **Warning**: Some records missing or misconfigured
+- **Error**: Critical configuration issues
+- **Pending**: DNS propagation in progress
 
 ### Automated monitoring
 
@@ -421,17 +421,15 @@ async function checkDomainHealth(domain: string): Promise<boolean> {
 
 Proper domain configuration is essential for Email Service functionality:
 
-- ✅ **DNS records** enable sending and routing
-- ✅ **Verification** ensures proper setup
-- ✅ **Advanced settings** provide flexibility and security
-- ✅ **Monitoring** maintains domain health
+- DNS records enable sending and routing
+- Verification ensures proper setup
+- Advanced settings provide flexibility and security
+- Monitoring maintains domain health
 
 ## Next steps
 
 - **[Send emails API](/email-service/api/send-emails/)**: Workers binding and REST API reference
 - **[Domain authentication (DKIM and SPF)](/email-service/concepts/email-authentication/)**: Learn about SPF, DKIM, and DMARC
 - **[Deliverability](/email-service/concepts/deliverability/)**: Optimize email delivery
 
----
 
-_Need help with domain configuration?_ Contact support.

src/content/docs/email-service/configuration/email-routing-addresses.mdx

@@ -5,6 +5,8 @@ sidebar:
   order: 1
 ---
 
+import {DashButton} from "~/components";
+
 In Email routing, an email rule is a pair of a custom email address and a destination address, or a custom email address and an associated Worker. You can route emails to either:
 
 - Verified email addresses
@@ -16,6 +18,9 @@ This allows you to route emails to your preferred inbox, or apply logic with Wor
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
 2. Go to **Email** > **Email Routing** > **Routes**.
+
+   <DashButton url="/?to=/:account/email-service/routing" />
+
 3. Select **Create address**.
 4. In **Custom address**, enter the custom email address you want to use (for example, `my-new-email`).
 5. In the **Action** drop-down menu, choose what this email rule should do. Refer to [Email rule actions](#email-rule-actions) for more information.
@@ -42,16 +47,22 @@ To prevent spamming unintended recipients, all email rules are automatically dis
 
 ### Disable an email rule
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
-2. Go to **Email** > **Email Routing** > **Routes**.
+1. In the Cloudflare dashboard, go to **Email Routing**.
+
+   <DashButton url="/?to=/:account/email-service/routing" />
+
+2. Select **Routes**.
 3. In **Custom addresses**, identify the email rule you want to pause, and toggle the status button to **Disabled**.
 
 Your email rule is now disabled. It will not forward emails to a destination address or Worker. To forward emails again, toggle the email rule status button to **Active**.
 
 ### Edit custom addresses
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
-2. Go to **Email** > **Email Routing** > **Routes**.
+1. In the Cloudflare dashboard, go to **Email Routing**.
+
+   <DashButton url="/?to=/:account/email-service/routing" />
+
+2. Select **Routes**.
 3. In **Custom addresses**, identify the email rule you want to edit, and select **Edit**.
 4. Make the appropriate changes to this custom address.
 
@@ -61,8 +72,11 @@ When you enable this feature, Email Routing will catch variations of email addre
 
 To enable Catch-all addresses:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
-2. Go to **Email** > **Email Routing** > **Routes**.
+1. In the Cloudflare dashboard, go to **Email Routing**.
+
+   <DashButton url="/?to=/:account/email-service/routing" />
+
+2. Select **Routes**.
 3. Enable **Catch-all address**, so it shows as **Active**.
 4. In the **Action** drop-down menu, select what to do with these emails. Refer to [Email rule actions](#email-rule-actions) for more information.
 5. Select **Save**.