Gmail mata custom domain (seu agente quebra January 2027)

Gmail mata custom domain (seu agente quebra January 2027)

Você é founder/CEO de SaaS.

Seu SaaS: agente IA (atendimento, vendas, suporte).

Sua atual arquitetura de email:

• Email provider: Gmail ou Google Workspace (cheap, convenient)
• Authentication: Custom domain "send as" (customers receive emails from your domain, not Gmail)
• Assumption: "Google won't kill this (too many people use it)"
• Reality: "Google discontinued custom domain 'send as' (effective January 2027)"
• Timeline: 4 months until deadline (January 2027)
• Impact: Your agente can't send emails from custom domain (breaks January 1)

Google's announcement (September 2026, 30 HN points, 28 comments = real concern):

What Google did:

• Feature: Gmail/Workspace custom domain "send as" (send emails from custom domain via Gmail)
• Status: DISCONTINUED (effective January 1, 2027)
• Reason: Google shifting to official email forwarding (more secure, better compliance)
• Impact: Anyone using custom domain "send as" = email breaks January 1, 2027
• Signal: 30 HN points, 28 comments = market sees this as infrastructure crisis

What happens January 1, 2027:

BEFORE (now, September 2026): ├─ Your agente sends email via Gmail ├─ Custom domain configured ("send as") ├─ Customer receives email from: noreply@yourcompany.com ├─ Gmail handles: Sending, delivery, compliance └─ System works fine

AFTER (January 1, 2027): ├─ Custom domain "send as" feature GONE ├─ Your agente tries to send from: noreply@yourcompany.com ├─ Gmail rejects: "Feature no longer supported" ├─ Customer receives: Nothing (email bounces, or sends from Gmail address) ├─ System breaks: Your agente can't send emails └─ Result: Production emergency (emails not being sent)

IMPACT: "Your agente can't send emails to customers. Customers don't receive: Password resets, confirmations, notifications, alerts. Customers can't onboard, can't use product. Support tickets explode ("why didn't I get email?"). Churn accelerates ("your product is broken"). Fire drill: Migrate email infrastructure (too late, January 1 is here)."

---

O problema (seu agente usa Gmail, email quebra)

Scenario 1: Your agente email infrastructure (Gmail-based)

Current setup (common pattern):

Your agente email architecture: ├─ Email provider: Gmail (cheap, free, everyone has it) ├─ Authentication: Custom domain "send as" (seems official) ├─ Sending method: Gmail SMTP (smtp.gmail.com:587) ├─ From address: noreply@yourcompany.com (via custom domain) ├─ Use cases: Transactional emails, notifications, alerts │ ├─ PROS (why you chose Gmail): │ ├─ Cost: Free or cheap ($6/month per user, Google Workspace) │ ├─ Simplicity: Already have Gmail account, just configure "send as" │ ├─ Reliability: Gmail servers are reliable (99.9% uptime) │ └─ No setup: No need to learn SendGrid, Mailgun, etc │ └─ CONS (problems when custom domain "send as" dies): ├─ Authentication breaks (custom domain "send as" = GONE January 1) ├─ Email fails (agente can't send from custom domain anymore) ├─ Deliverability hurt (emails might bounce or send from Gmail address) ├─ Brand damage (customers receive from "noreply@gmail.com" instead of your domain) ├─ Support explodes ("why did I get email from Gmail?") └─ Churn risk (broken email = broken product)

Why this is critical:

Email is core to agente functionality:

1. Password resets (customer can't login without email)
2. Confirmations (customer can't verify account without email)
3. Notifications (agente sends alerts, customer misses them)
4. Transactional (agente sends orders, confirmations, invoices)
5. Marketing (agente sends campaigns, updates, announcements)

If email breaks = agente is broken. If agente is broken = customers leave.

Scenario 2: What happens January 1, 2027 (if you don't migrate)

Timeline to crisis:

November 2026: ├─ You're aware of deadline (30 days away) ├─ You know you need to migrate (but haven't done it yet) ├─ Status: Procrastinating ("we'll do it next week") └─ Risk: Getting tight, but doable

December 2026 (1-2 weeks before deadline): ├─ You realize: Migration is urgent ├─ You start: Researching alternatives (SendGrid, Mailgun, AWS SES) ├─ Problem: All require setup, testing, integration ├─ Timeline: 1-2 weeks is NOT enough time ├─ Status: Starting to panic └─ Risk: Impossible to migrate properly (can't test enough)

December 30, 2026 (1 day before deadline): ├─ Realization: You're not ready ├─ Status: Full panic mode ├─ Action: Try to migrate in 24 hours (bad idea) ├─ Problem: No testing, high risk of breaking things ├─ Risk: Migration fails, emails don't send (production emergency) └─ Result: New Year's Day = your agente is broken

January 1, 2027 (DEADLINE): ├─ Custom domain "send as" officially dies ├─ Your agente tries to send email (fails) ├─ Customer doesn't receive password reset (can't login) ├─ Support tickets explode ("broken product!") ├─ Churn starts (customers leave for working alternatives) └─ You're in fire-drill mode (emergency migration, customer crisis)

January 2-31, 2027 (aftermath): ├─ Damage control (customers angry, churn accelerating) ├─ Emergency migration (rushed, high-risk work) ├─ Reputation damage ("your product broke on New Year's") ├─ Lost revenue (churn offsets any savings from Gmail) └─ Lesson learned (don't procrastinate on infrastructure)

Market signal (Google killing feature = consolidation)

Why Google is doing this:

1. Security concern: ├─ Custom domain "send as" = weak security (Gmail can impersonate your domain) ├─ Google shifting to: Official email forwarding (stronger security) ├─ Implication: Google prioritizing security over backward compatibility └─ For you: Need to migrate to secure solution (SendGrid, Mailgun, etc)

2. Compliance pressure: ├─ GDPR, compliance regulations = need better email security/auditing ├─ Custom domain "send as" = doesn't meet compliance standards ├─ Google shifting to: Enterprise email solutions (better compliance) ├─ For you: Need to migrate to compliant solution (audit trails, encryption, etc) └─ Implication: If you want compliance, need professional email service

3. Market consolidation: ├─ Gmail = free, but limited (custom domain "send as" is hack) ├─ SendGrid, Mailgun, AWS SES = professional (proper email infrastructure) ├─ Google killing hack = forcing users to professional solutions ├─ Implication: Market moving from free hacks to paid professional services └─ For you: Upgrade from Gmail to professional email service (cost: $20-100/month)

4. Timeline signal: ├─ 4 months notice (September → January) = standard corporate timeline ├─ But also: Aggressive timeline (not 12 months, just 4) ├─ Signal: Google prioritizing this (wants it done ASAP) ├─ For you: This is urgent (not optional, not flexible) └─ Implication: Must migrate by January 1 or face production break

---

A solução (migrate email to professional service, January 2027)

Step 1: Audit current email infrastructure (1-2 weeks, R$ 10-15K)

Goal: Understand what breaks, what stays

How to audit:

1. Email flows inventory: ├─ List all emails agente sends (password reset, confirmation, notification, etc) ├─ Count: How many emails/day does agente send? ├─ Frequency: When are emails sent? (real-time, batch, scheduled?) ├─ Volume spike: What's max emails/day? (Black Friday, launch day?) └─ Deliverability: What's current delivery rate? (Gmail bouncing any emails?)

2. Gmail configuration audit: ├─ Document: Current Gmail custom domain "send as" configuration ├─ Identify: Which agente systems use this? (which services send emails?) ├─ Check: Any other Gmail features you depend on? (forwarding, filtering, etc) ├─ Assess: What's actually custom domain "send as"? (how critical is it?) └─ Result: List of systems that will break January 1

3. Deliverability assessment: ├─ Check: Are Gmail emails reaching customer inboxes? (or spam folder?) ├─ Test: Send test emails, check inbox vs spam ├─ Analyze: Why are some emails spam? (SPF, DKIM, DMARC configured?) ├─ Problem: Gmail often lands in spam (no proper authentication) └─ Insight: Moving to professional service will IMPROVE deliverability

4. Alternative assessment: ├─ Research: SendGrid, Mailgun, AWS SES, Postmark (main providers) ├─ Compare: Price, features, deliverability, support ├─ Estimate: Migration effort (APIs, testing, rollback plan) ├─ Identify: Best fit for your agente (price vs features) └─ Recommend: Which service to migrate to

5. Risk assessment: ├─ Identify: What happens if migration fails? (customer impact?) ├─ Plan: Rollback strategy (can you revert if something breaks?) ├─ Timeline: How long is migration? (1 week? 2 weeks? Can you afford downtime?) ├─ Testing: How much testing is needed before production? (2 weeks? 1 month?) └─ Buffer: Do you have enough time before January 1? (should be 2-4 weeks buffer)

Deliverables:

• Email flows inventory (all emails, volume, frequency)
• Gmail configuration audit (what uses custom domain "send as")
• Deliverability assessment (current inbox vs spam rates)
• Alternative comparison (SendGrid vs Mailgun vs AWS SES vs Postmark)
• Migration plan (effort, timeline, risk, rollback)
• Recommendation (which service, why, timeline)

Step 2: Choose migration target (1 week, R$ 5-10K)

Goal: Pick professional email service

How to choose:

1. SendGrid (market leader, most popular for SaaS): ├─ Price: $9.95-4995/month (based on email volume) ├─ For 10K emails/day: ~$30/month ├─ Features: Email API, webhooks, deliverability tools, reporting ├─ Pros: Simple, reliable, good documentation, great for developers ├─ Cons: Can be expensive at scale (high volume = high cost) └─ Best for: Most SaaS agentes (good balance of price, features, reliability)

2. Mailgun (developer-friendly, good pricing): ├─ Price: $0 (free tier), $20-349/month (paid) ├─ For 10K emails/day: ~$45/month ├─ Features: Email API, webhooks, email validation, reporting ├─ Pros: Free tier (good for testing), flexible pricing, good documentation ├─ Cons: Lower market share (less trusted than SendGrid) └─ Best for: Startups, cost-sensitive SaaS (free tier is valuable)

3. AWS SES (cheapest at scale): ├─ Price: $0.10 per 1000 emails (cheapest!) ├─ For 10K emails/day: ~$3/month (incredible value) ├─ Features: Email API, webhooks, reputation dashboard ├─ Pros: Cheapest at scale, AWS integration (if already using AWS) ├─ Cons: Steeper learning curve, need AWS knowledge, slower to set up └─ Best for: High-volume agentes (10K+ emails/day), AWS-native companies

4. Postmark (premium, focused on transactional): ├─ Price: $15-750/month (based on volume) ├─ For 10K emails/day: ~$100/month ├─ Features: Transactional email, templates, analytics, support ├─ Pros: Best-in-class deliverability, great support, active postmaster ├─ Cons: Most expensive option └─ Best for: When deliverability is critical (regulated industries, high-trust apps)

How to decide: ├─ Volume: <5K/day = SendGrid, Mailgun OK ├─ Volume: 5-20K/day = AWS SES best (cost) ├─ Volume: >20K/day = AWS SES definitely (cost at scale) ├─ Priority: Deliverability > cost = Postmark (best deliverability) ├─ Priority: Cost = AWS SES (cheapest) ├─ Priority: Ease of use = SendGrid (most straightforward) └─ Recommendation: Most SaaS agentes should use AWS SES or SendGrid

For most agentes: AWS SES (cheapest, reliable, integrates with AWS services)

Step 3: Migrate email infrastructure (2-3 weeks, R$ 25-40K)

Goal: Move from Gmail to professional email service

How to migrate:

1. Set up new email service: ├─ Create account (SendGrid, Mailgun, AWS SES, or Postmark) ├─ Verify domain (add DNS records, TXT/CNAME to prove ownership) ├─ Configure authentication (SPF, DKIM, DMARC - improves deliverability) ├─ Set up API credentials (API key, access tokens) ├─ Test sending (send test email, verify it arrives) └─ Timeline: 2-3 days

2. Update agente code: ├─ Replace: Gmail SMTP (smtp.gmail.com:587) ├─ With: New service SMTP or API (depends on service) ├─ Update: From address (noreply@yourcompany.com stays same) ├─ Update: API credentials (in config, environment variables) ├─ Add: Error handling (new service might fail differently than Gmail) └─ Timeline: 3-5 days (depending on code complexity)

3. Comprehensive testing: ├─ Unit tests: Can you send email? (does API work?) ├─ Integration tests: Do emails arrive? (do they land in inbox or spam?) ├─ Load tests: Send 1000s of emails, check throughput (can system handle it?) ├─ Failure tests: What happens if email service is down? (graceful fallback?) ├─ Spam tests: Check if emails land in inbox (not spam folder) └─ Timeline: 1-2 weeks (thorough testing is critical)

4. Staging deployment: ├─ Deploy: To staging environment (not production) ├─ Test: All email flows in staging (password reset, confirmation, notification) ├─ Verify: All emails work correctly (arrive, content correct, links work) ├─ Monitor: Watch staging for 3-5 days (any issues?) └─ Timeline: 1 week

5. Production migration: ├─ Plan: Migration window (best during low-traffic time) ├─ Communicate: Tell customers "email service upgrading, expect no downtime" ├─ Deploy: New email service to production (switch from Gmail to SendGrid/AWS SES) ├─ Monitor: Watch email deliverability closely (first 24 hours critical) ├─ Support: Be ready if customers report email issues (have rollback plan) ├─ Verify: Check sample of emails arriving (password resets, etc) └─ Timeline: 1-2 days (go-live + 24hr monitoring)

6. Post-migration validation: ├─ Monitor: Email metrics (delivery rate, bounce rate, spam rate) ├─ Compare: Before vs after (is new service better?) ├─ Optimize: If issues, tweak configuration (SPF, DKIM, DMARC) ├─ Customer feedback: Ask customers if they notice any issues ├─ Document: What you learned, what worked, what didn't └─ Timeline: Ongoing (2-4 weeks post-launch)

Total timeline: 3-4 weeks (audit + setup + code + testing + deployment) Must complete by: December 20, 2026 (2-week buffer before January 1)

Step 4: Optimize email deliverability (ongoing, R$ 5-10K/month)

Goal: Make sure emails keep arriving in inbox

How to maintain deliverability:

1. SPF/DKIM/DMARC configuration: ├─ SPF: Tell mail servers what's allowed to send from your domain ├─ DKIM: Sign emails with cryptographic key (proves authenticity) ├─ DMARC: Policy for handling failed SPF/DKIM (stop impersonation) ├─ Setup: Add DNS records for each (takes 1-2 hours) ├─ Benefit: Improves deliverability (emails more likely to land in inbox) └─ Requirement: Must do this after migrating (SPF/DKIM point to new service)

2. Monitoring: ├─ Daily: Check delivery rate (% of emails delivered vs bounced) ├─ Weekly: Check spam rate (% of emails landing in spam folder) ├─ Monthly: Analyze bounce reasons (hard bounce? Soft bounce? Invalid?) ├─ Alert: If delivery rate drops below 95%, investigate └─ Action: Adjust configuration or email content if needed

3. List hygiene: ├─ Remove: Hard bounces (email doesn't exist) ├─ Track: Spam complaints (if recipients mark as spam) ├─ Suppress: Unsubscribes (never email again if they unsubscribe) ├─ Monitor: Complaint rate (stay below 0.1% to avoid reputation damage) └─ Action: Clean list regularly (every month) to maintain sender reputation

4. Reputation management: ├─ Track: Sender reputation (SendGrid, Mailgun provide reputation dashboard) ├─ Monitor: If reputation score drops, address it immediately ├─ Check: Are you on spam blacklist? (check MXToolbox, Spamhaus) ├─ Action: If blacklisted, work with service to delist └─ Prevention: Follow best practices (send relevant emails, monitor complaints)

Cost: Professional email service $20-100/month + ongoing monitoring time

Total: 3-4 weeks, R$ 40-65K initial + $20-100/month ongoing

---

Conclusão: Gmail mata custom domain (você tem 4 meses)

Signal (Google announcement):

• Gmail discontinues custom domain "send as" (effective January 1, 2027)
• 30 HN points, 28 comments = market sees this as infrastructure crisis
• Deadline: 4 months away (September → January)
• Impact: Agentes using Gmail can't send emails January 1

Your current exposure:

• Agente likely uses Gmail SMTP (cheap, common pattern)
• Custom domain "send as" probably configured (how agente sends emails)
• January 1, 2027 = your agente email breaks (unless migrated)
• Impact: Production emergency, customer churn, support explosion

Your options:

Opção 1: Do nothing (hope January 1 never comes)

• Keep using Gmail custom domain "send as"
• Hope Google doesn't actually kill it (unlikely)
• Result: January 1 = agente breaks, customers can't receive emails, churn explodes

Opção 2: Migrate to professional email service (3-4 weeks, R$ 40-65K) - RECOMMENDED

• Audit current Gmail infrastructure (1-2 weeks)
• Choose migration target (SendGrid, Mailgun, AWS SES, or Postmark)
• Migrate agente code, test thoroughly (2-3 weeks)
• Deploy to production (with buffer before January 1)
• Result: Agente email works perfectly, improves deliverability, future-proof

Your decision window: THIS MONTH (September = maximum time to prepare)

If you migrate THIS MONTH:

• You have 4 months to test, validate, optimize (plenty of buffer)
• You avoid New Year's crisis (no emergency migration)
• You improve email deliverability (professional service > Gmail)
• You gain compliance benefits (audit trails, authentication, encryption)
• Result: Smooth transition, zero customer impact, improved reliability

If you wait until December:

• You have 1 month to migrate (rushed, high-risk)
• Testing is rushed (can't validate thoroughly)
• Production migration during holidays (risky timing)
• If something breaks = customer emergency during Christmas/New Year
• Result: Production crisis, churn, reputation damage

At OpenClaw, ajudamos SaaS agentes migrate email infrastructure:

• AUDIT: Current Gmail setup (what uses custom domain "send as", what breaks)
• PLAN: Migration strategy (which service, timeline, risk mitigation)
• EXECUTE: Code migration (update SMTP/API, test thoroughly, deploy safely)
• OPTIMIZE: Deliverability (SPF/DKIM/DMARC, monitoring, reputation management)
• SUPPORT: Ongoing monitoring (make sure email keeps working, catch issues early)

Result: Seu agente email é bulletproof (works January 1 and beyond). Customers receive all emails (password resets, confirmations, notifications). Deliverability improves (professional service > Gmail). You're future-proof (compliant with security standards).

Seu agente usa Gmail custom domain?

Você sabe o que quebra January 1? (audited?)

Você já escolheu email service alternativo? (SendGrid? AWS SES?)

Você tem 4 meses pra migrar?

Quer audit + migration plan + code update em 3-4 semanas?

Quer garantir agente email funciona January 1?

Se não sabe por onde começar OU quer audit + migration plan + execution em 3-4 semanas:

Migrate agente email de Gmail AGORA (3-4 semanas, R$ 40-65K, audit + SendGrid/AWS SES migration + code update + testing + deployment, agente email bulletproof January 1, zero customer impact, improved deliverability, compliance-ready) →