docs: remove internal details, pricing, quarantine refs, and WIP labels

- Remove all quarantine system references (email-lifecycle, logs)
- Remove '(work in progress)' from page titles (domains, metrics, postmaster)
- Remove internal timeline note and fix typo in sandboxing partial
- Generalize retry intervals and suppression thresholds (internal details)
- Reword IP reputation to not expose tiered pool architecture
- Remove specific pricing figures
- Remove 'not available' contradiction from local dev sending page

Author: thomasgauvin

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

@@ -35,15 +35,15 @@ Soft bounces are temporary failures that may succeed if retried:
 - Email server temporarily down
 - Rate limiting or greylisting
 
-Cloudflare automatically retries soft bounces with exponential backoff (15min → 1hr → 4hr → 12hr → 24hr) for up to 72 hours.
+Cloudflare automatically retries soft bounces with exponential backoff over an extended period.
 
 <Sandboxing />
 
 ## Reputation management
 
 Cloudflare automatically manages:
 
-- **IP reputation**: Shared pools with tiered promotion based on sending quality
+- **IP reputation**: Managed sending infrastructure optimized for deliverability
 - **Domain authentication**: DKIM signing, SPF alignment, DMARC compliance
 - **Feedback processing**: ISP complaint handling and suppression list management
 

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

@@ -20,7 +20,7 @@ flowchart LR
     A[Request Received] --> B[Rate Limit Check] --> C[Authentication & Reputation] --> D[Suppression Check] --> E[Delivery Attempt]
     E --> G{Success?}
     G -->|Yes| F[Final Status & Metrics]
-    G -->|No - Soft Bounce| H[Retry with Exponential Backoff<br/>Up to 3 attempts]
+    G -->|No - Soft Bounce| H[Retry with Exponential Backoff]
     G -->|No - Hard Bounce| F
     H --> E
     H -->|Max retries exceeded| F
@@ -42,7 +42,7 @@ flowchart LR
 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.
 
 5. **Delivery attempt:** The system connects to the recipient's mail server and attempts message delivery via SMTP. When delivery fails, the system applies different retry logic based on the failure type:
-   - **Soft bounces (4xx responses)**: The system retries delivery up to 3 times using exponential backoff timing
+   - **Soft bounces (4xx responses)**: The system retries delivery using exponential backoff timing
    - **Hard bounces (5xx responses)**: The system marks the email as permanently failed with no retry attempts
 
 6. **Server response handling:** The system processes SMTP response codes from the recipient server to determine the final email status:
@@ -53,8 +53,6 @@ flowchart LR
 7. **Final status and metrics:** Based on the server response, the system assigns emails one of these final statuses:
    - **Delivered**: The email was successfully accepted by the recipient server
    - **Bounced**: The email permanently failed delivery (hard bounce) or exceeded the maximum retry attempts (soft bounce)
-   - **Quarantined**: The email is held for review due to content analysis or reputation concerns
-
 ---
 
 Understanding the email lifecycle helps you build robust email applications that handle all possible outcomes and provide excellent user experiences through proper status tracking and error handling.

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

@@ -46,7 +46,7 @@ You may also manually add or remove email addresses from your suppression list a
 Cloudflare automatically suppresses addresses that:
 
 - **Hard bounce**: Invalid or non-existent email addresses are immediately added to the Cloudflare global suppression list.
-- **Repeated soft bounces**: Addresses that fail delivery 3-5 times within a 48 hour period are temporarily suppressed. Emails that soft bounce more than 5 times are added to the global suppression list.
+- **Repeated soft bounces**: Addresses that repeatedly fail delivery are temporarily or permanently suppressed based on the frequency and pattern of failures.
 - **Spam complaints**: Recipients who mark emails as spam are added to your account suppression list.
 
 ## Best practices

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

@@ -1,5 +1,5 @@
 ---
-title: Domain configuration (work in progress)
+title: Domain configuration
 pcx_content_type: concept
 summary: |
   Configure domains for Cloudflare Email Service, manage DNS records, and verify domain setup for both email sending and routing.

src/content/docs/email-service/local-development/sending.mdx

@@ -10,13 +10,6 @@ import { WranglerConfig } from "~/components";
 
 Test email sending functionality locally using `wrangler dev` to simulate email delivery and verify your sending logic before deploying.
 
-
-::: Note
-
-Local development is **not available** at this time.
-
-:::
-
 ## Prerequisites
 
 - [Wrangler CLI](https://developers.cloudflare.com/workers/wrangler/install-and-update/) installed

src/content/docs/email-service/observability/logs.mdx

@@ -19,7 +19,6 @@ For outbound emails sent through Email Service:
 - **Sent**: Email successfully accepted and queued for delivery
 - **Delivered**: Email successfully delivered to recipient's mail server
 - **Bounced**: Email bounced (hard or soft bounce)
-- **Quarantined**: Email held for review due to reputation or content analysis
 - **Failed**: Email failed to send due to configuration or authentication issues
 
 ### Email routing logs
@@ -104,16 +103,14 @@ Use the Activity Log filters to find specific emails:
 
 - Authentication failure rates
 - Bounce patterns and trends
-- Quarantine frequency
 - Delivery success rates
 
 ### Troubleshooting workflow
 
 1. **Identify the issue**: Use logs to pinpoint failure types
 2. **Check authentication**: Verify SPF, DKIM, DMARC configuration
-3. **Review content**: Look for patterns in quarantined emails
-4. **Adjust configuration**: Make necessary DNS or routing changes
-5. **Monitor improvement**: Track metrics after changes
+3. **Adjust configuration**: Make necessary DNS or routing changes
+4. **Monitor improvement**: Track metrics after changes
 
 ---
 

src/content/docs/email-service/observability/metrics-analytics.mdx

@@ -1,6 +1,6 @@
 ---
 pcx_content_type: concept
-title: Metrics and analytics (work in progress)
+title: Metrics and analytics
 sidebar:
   order: 1
 ---

src/content/docs/email-service/platform/pricing.mdx

@@ -11,18 +11,12 @@ Cloudflare Email Service pricing is based on your Cloudflare plan and email usag
 
 Email Service is available on Free and Paid Cloudflare plans:
 
-|                                                         | Free             | Paid                                                         |
-| ------------------------------------------------------- | ---------------- | ------------------------------------------------------------ |
-| **Outbound emails (Email Sending)**                     | ❌ Not available | 10,000 emails included <br /> + $0.50 per 1,000 emails above |
-| **Outbound emails to Account-owned verified addresses** | ✅ Unlimited     | ✅ Unlimited                                                 |
-| **Inbound emails (Email Routing)**                      | ✅ Unlimited     | ✅ Unlimited                                                 |
+|                                                         | Free             | Paid             |
+| ------------------------------------------------------- | ---------------- | ---------------- |
+| **Outbound emails (Email Sending)**                     | ❌ Not available | ✅ Available     |
+| **Outbound emails to Account-owned verified addresses** | ✅ Unlimited     | ✅ Unlimited     |
+| **Inbound emails (Email Routing)**                      | ✅ Unlimited     | ✅ Unlimited     |
 
 Email Routing Workers is billed according to [Workers pricing](/workers/platform/pricing/).
 
-### Volume discounts
-
-Volume discounts available for high-volume senders. Contact sales for custom pricing on large volumes.
-
-:::note[Volume Discount Application]
-Volume discounts apply only to overage emails, not included quotas.
-:::
+For details on Email Sending pricing, refer to the [Cloudflare dashboard](https://dash.cloudflare.com/).

src/content/docs/email-service/reference/postmaster.mdx

@@ -1,6 +1,6 @@
 ---
 pcx_content_type: reference
-title: Postmaster (work in progress)
+title: Postmaster
 sidebar:
   order: 1
 head: []

src/content/partials/email-service/_sandboxing.mdx

@@ -1,15 +1,8 @@
 ## Sandboxing system
 
-:::note
-
-The sandboxing system is not currently present in the Email Service public beta. It will be implemented by the release of the public beta.
-
-:::
-
 When you first onboard onto Email Service, you are given a **sandbox access**. **Sandbox access** only allows you to send emails to **verified emails** in your account.
-This provides you with a sanboxed environment for testing and developing your application without affecting your domain's reputation.
+This provides you with a sandboxed environment for testing and developing your application without affecting your domain's reputation.
 
 When you are ready to move to production and send emails to any email address, you must fill out the **Production Access Form** to provide additional details about your planned usage.
-The Cloudflare Email Service team will review your planned usage, as well as your historical usage of Workers or other Cloudflare products and other factors.
 
 At this time, only transactional email use cases are permitted for use with Email Service and this will be verified during onboarding and during your usage of Email Service.