EmailDeliverability

TL;DR I built a Chrome extension for cross-border sourcing, then built an inbox-native AI agent next to it. After 6 months running both in production, the Chrome extension wins for real-time page-anchored research (the 45-second sidebar loop), and the inbox agent wins for relationship-driven work (the 5-year email memory data flywheel). The pattern: the extension is the daytime tool, the inbox agent is the always-on tool. If you build only one, build the inbox agent first — its value compounds with every email it reads. ...

TL;DR A mail transfer agent (MTA) is the server software that moves email from sender to recipient across SMTP hops — the layer where queue policy, retry logic, throttling, and authentication decide whether your message reaches the inbox or quietly collapses to spam. Most foreign-trade teams below 50,000 messages per month should start with a managed cloud relay (SES, Postmark, Mailgun, Resend) and move to self-hosted Postfix or Exim only when they hit a compliance wall, a deliverability ceiling, or a volume tier where the per-message cost crosses a clear threshold. Treat deliverability as a CI problem: per-domain pacing, 72-hour retry cap, 5 soft bounces in 7 days suppression, and continuous SPF/DKIM/DMARC alignment checks. ...