请问HN：多代理外联系统中的电子邮件身份隔离？
我正在构建一个用于外发邮件的人工智能代理管道，但遇到了一个我没有看到过太多讨论的基础设施问题。
当你同时运行多个代理进行外联时，大多数人默认的设置是让所有代理共享一个电子邮件域名和发送身份。这在规模化时会出现几个问题：
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?