SendGrid

SendGrid = full-featured, $0.10/email ($10/mo minimum), excellent templates + webhooks, great for transactional + marketing hybrids. Amazon SES = cheapest ($0.10/1K emails), no-frills API, fine for high-volume purely transactional, requires IP warming. Mailgun = developer-friendly, similar pricing to SendGrid, strong reputation management. Rule: startups use SendGrid (templates save 10h/wk), enterprise/high-volume use SES (cost), developers love Mailgun (API). Pick SendGrid unless cost is existential or you live in AWS ecosystem.

IP warming = gradually increasing email volume sent from a new IP address to establish sender reputation. ISPs (Gmail, Outlook, Yahoo) monitor new IPs for spam behavior; if you blast 100K emails from a fresh IP on day 1, 30-50% land in spam. Standard warmup: day 1-3 (500/day), day 4-7 (5k/day), week 2-4 (50k/day), then full volume. Monitor bounce rates (stay <3%) and complaints (<0.1%) during warmup. SendGrid's IP warming guide is solid; follow it. Skipping this costs deliverability for 3-6 months, not worth it.

SPF (Sender Policy Framework) = DNS record saying 'mail from example.com can come from these IPs/servers'. Receiver validates: is this email's IP in my SPF list? DKIM (DomainKeys Identified Mail) = cryptographic signature proving the email came from your server, not a spoof. DMARC (Domain-based Message Authentication) = enforcement policy: if SPF/DKIM fail, quarantine or reject (not just flag as suspicious). Modern ISPs require all three: Gmail DMARC p=reject on high-volume senders; Yahoo enforces DKIM. Without DMARC, your domain leaks into attacker hands and phishing increases. Set up all three day 1, not month 6.

Transactional = triggered by user action (password reset, order confirmation, receipt, shipping notification). Low volume, high importance, low unsubscribe rate. Marketing = bulk campaigns (newsletters, promotions, announcements). High volume, lower importance, CAN unsubscribe. ISPs treat them differently: transactional gets higher reputation threshold (lower bounce = OK), marketing is scrutinized (any unsubscribe = reputation risk). SendGrid/SES let you send both from one API, but split suppression lists and monitor bounce/complaint rates separately. Don't mix lists or your marketing sender gets flagged.

Bounce = email returned as undeliverable. Hard bounce (mailbox doesn't exist) = permanent, suppress forever. Soft bounce (server temporarily unavailable) = retry later. Complaint = recipient marked as spam. ISPs track your bounce + complaint ratio: >5% bounce rate = sender reputation damage, >0.1% complaint = blacklist risk. Suppression lists = auto-exclude bounced/complained emails from future sends (prevents worsening reputation). Set up suppression automation: hard bounce = remove from list, soft bounce = retry 3x then remove, complaint = remove + mark as spam. Automate or burn.

Webhooks = HTTP POST callbacks SendGrid makes to your server when an email event occurs: sent, delivered, bounce, complaint, open, click. Configure in SendGrid dashboard (Settings > Event Webhook); point to your server (e.g., POST /api/email-events). SendGrid fires immediately after each event. Benefits: real-time tracking (update user status), bounce handling (suppress user), engagement tracking (track opens/clicks for analytics). Gotchas: webhooks may fire out-of-order, may retry (idempotency key required), may take 1-30 min to deliver under load. Expect 99% coverage, not 100%. Use for monitoring, not for critical business logic (sync DB post-send instead, webhooks are fire-and-forget).