Ask HN: 面向多智能体外展系统的邮件身份隔离？
1 分•作者: kumardeepanshu•5 个月前
我一直在构建一个用于外发邮件的 AI 代理管道，并遇到了一个基础设施问题，这个问题似乎很少有人讨论。
当您并行运行多个代理进行外展时，大多数人默认的设置是让所有代理共享一个电子邮件域名和发件人身份。这种设置在规模化时会以多种方式失效：
1. 声誉隔离：如果一个代理因激进的发送行为或触发垃圾邮件过滤器而被标记，整个域名的声誉就会下降。即使其他代理运行良好，其邮件送达率也会受到影响。
2. 回复归属：所有收到的回复都进入同一个收件箱，无法清晰地将它们路由回发起对话的特定代理。这使得转化跟踪几乎不可能实现。
3. 每个代理的 A/B 测试：当所有代理共享一个身份时，无法在代理级别测试不同的消息传递方法。
正确的模式似乎是为每个代理分配其自己的专用发送地址，这样声誉就可以在每个代理之间隔离，并且回复可以正确路由回去。但是，干净地做到这一点的工具——尤其是入站路由部分——似乎并没有以即插即用的方式存在于代理工作流程中。
很想知道其他人是如何解决这个问题的。您是手动管理单独的身份，使用我错过的现有工具，还是暂时接受共享域名的限制？
查看原文
Been building an AI agent pipeline for outbound email and ran into an infrastructure problem that I haven't seen discussed much.<p>When you run multiple agents doing outreach in parallel, the default setup most people land on is having all agents share one email domain and sending identity. This breaks in a few ways at scale:<p>1. Reputation isolation: if one agent gets flagged for aggressive sending or trips spam filters, the entire domain reputation degrades. Every other agent's deliverability takes the hit even if they're running fine.<p>2. Reply attribution: all inbound replies land in one inbox with no clean way to route them back to the specific agent that initiated the conversation. Makes conversion tracking nearly impossible.<p>3. Per-agent A/B testing: impossible to test different messaging approaches at the agent level when they all share an identity.<p>The pattern that seems right is giving each agent its own dedicated sending address so reputation is isolated per agent and replies route back correctly. But the tooling to do this cleanly - especially the inbound routing piece - doesn't seem to exist in a plug-and-play way for agent workflows.<p>Curious how others have solved this. Are you managing separate identities manually, using some existing tool I've missed, or just accepting the shared domain limitations for now?