What is a good minimum email infrastructure setup for a small product team?

For a small product team, a solid minimum email infrastructure setup separates transactional/app email from team/operational email to protect deliverability and domain reputation.

Here is the ideal minimal, production-ready stack:

1. Domain Strategy & DNS Authentication

Never send all email types from a single unauthenticated setup. Configure these DNS records on your primary domain (yourproduct.com):

• SPF (Sender Policy Framework): Authorizes which servers can send emails on behalf of your domain. Keep it under the 10-DNS-lookup limit.
• DKIM (DomainKeys Identified Mail): Cryptographically signs emails to prove they weren't altered in transit. Generated by your email service providers.
• DMARC (Domain-based Message Authentication, Reporting, and Conformance): Tells receivers what to do if SPF or DKIM fails. Start with a monitoring policy:

Plaintext

v=DMARC1; p=none; rua=mailto:dmarc-reports@yourproduct.com;

• Use Subdomains for Transports:

• Primary domain (yourproduct.com) → Corporate/human email.

• Subdomain (notify.yourproduct.com or mail.yourproduct.com) → Transactional app emails (magic links, password resets).

• Subdomain (marketing.yourproduct.com) → Product updates & newsletters.

2. Primary Service Stack

Role	Recommended Tools	Purpose	Key Feature / Minimum Need
Workspace / Corporate	Google Workspace or Microsoft 365	Human-to-human email, team calendar, single sign-on (SSO).	Clean IP reputation, native workspace integration.
Transactional Email API	Resend, Postmark, or AWS SES	Programmatic transactional emails (signups, receipts, auth).	High delivery speed, developer-friendly API/SDKs.
Inbound Support / Shared Inbox	Help Scout or Front (or Google Group)	Customer support, contact-us forms, bug reports.	Shared inbox prevent collision; simple ticket tracking.

Pro Tip on Transactional Providers:

• Resend: Best modern developer experience (React Email support, fast setup).
• Postmark: Best delivery speeds for time-sensitive emails like magic links and OTPs.
• AWS SES: Cheapest option if you already run on AWS, but requires manual IP warming and compliance approval.

3. Basic Operational Practices

1. Suppression List Handling: Ensure your transactional provider automatically handles hard bounces, spam complaints, and unsubscriptions. Sending to dead addresses will ruin your IP sender score.
2. Dedicated App Sending Address: Use clear role-based senders (e.g., alex@yourproduct.com for transactional onboarding, notifications@yourproduct.com for system alerts).
3. Local Development Setup: Never send real emails from local localhost or staging environments. Use tools like Mailtrap, Mailhog, or mock webhooks during development.