BREAKING: Clerk MINOR 🔴 Development instances only - Apple rejecting emails [01M3M9SSWNTTRMRDFV59B28GCB]

Clerk authentication service experiencing email delivery failures in development environments. Apple mail servers rejecting outbound messages. Workarounds available now.

BREAKING: Clerk Email Delivery Issue - Development Instances

Status: IDENTIFIED | Severity: MINOR | Impact: Partial | Last Updated: Now

---

WHAT'S DOWN

Clerk's development instances are experiencing email delivery failures specifically when Apple mail servers (iCloud, Mail.app) are receiving verification emails. Production instances appear unaffected at this time.

Who's impacted:

Indie hackers using Clerk in dev/staging with Apple email testers

Teams testing authentication flows with @icloud.com, @me.com addresses

Anyone relying on dev instance email verification for demos

Production deployments are not currently affected.

---

IMMEDIATE WORKAROUNDS (DO THIS NOW)

Workaround 1: Switch Email Domains in Dev

Use non-Apple email addresses for testing immediately:

Gmail accounts (@gmail.com)

Outlook accounts (@outlook.com)

Temporary email services (Mailtrap, MailHog)

Company domains (not Apple-hosted)

Workaround 2: Disable Email Verification Temporarily

In your Clerk dashboard → Settings → Email → toggle off "Email verification required" for development.

Warning: Only for dev—re-enable before production.

Workaround 3: Use Clerk's Test Email Codes

Clerk provides hardcoded test codes in development: ``` Email: test@example.com Code: 424242 (standard test code) ```

This bypasses email entirely during dev testing.

Workaround 4: Route Through Alternative SMTP

Temporarily configure custom SMTP in Clerk settings:

SendGrid (free tier available)

Mailgun (developer friendly)

AWS SES

This bypasses Clerk's default mail infrastructure.

---

HOW TO CHECK IF YOU'RE AFFECTED

1. In dev environment: Send a test email to an @icloud.com or @me.com address 2. Check Clerk logs: Dashboard → Logs → filter for "Email delivery failed" 3. Error message pattern: Look for "SMTP rejection - Apple mail server" or similar 4. Still working? If non-Apple emails deliver fine, you have this issue

---

ALTERNATIVE TOOLS TO CONSIDER

While you're testing:

Auth0 - Similar feature set, different infrastructure

Supabase Auth - Open source, self-hostable option

Firebase Auth - Google's managed solution (no email issues reported)

Stytch - Passwordless specialist, solid email delivery

Magic - Email-link focused, reliable delivery

For just email delivery:

Resend (indie-friendly, great deliverability)

Loops (marketing + transactional)

PostmarkApp (gold standard, pricier)

---

MONITORING RECOVERY

Real-time status:

Check [Clerk Status Page](https://status.clerk.com) (bookmark this)

Watch this incident thread for updates

Subscribe to Clerk's status updates via email

How to test recovery: 1. Retry Apple email test after 30 minutes 2. Check Clerk's incident timeline for "resolved" message 3. Verify one non-Apple email still works (baseline) 4. Only then re-enable in production pipelines

Expected resolution: Clerk's team identified the issue. Apple's SMTP rejection is typically cleared within 1-4 hours. Will update when confirmed resolved.

---

BOTTOM LINE

This is not a security issue. Your authentication is intact. This is an email delivery problem in dev environments only. Use the workarounds above immediately—your indie project doesn't need to stop.

Don't wait for fixes when you can work around in 2 minutes.

Stay in the loop: Follow @ClerkDev on X for real-time updates.