是否有专门针对顶级域、SaaS Web 应用程序的 SMTP/POP 提供商
我们正在构建一个多租户、SaaS 类型的 Web 应用程序。应用程序部分的一切都已设置完毕，但在电子邮件方面却出现了问题。
应用程序的每个租户/用户都有一个基于子域的帐户。但是，该租户可以选择将顶级域与其帐户关联。这就是我们的问题所在。
基本上，如果用户将其 DNS 设置为指向我们的 SaaS Web 应用程序，那么应用程序前端的一切都会正常运行，只是现在我们还要负责处理他们的电子邮件。传入和传出。
处理这个问题的最佳方法是什么？我真的希望他们是一个第三方网站，可以处理一个公司名称下的多个顶级域的传出和传入电子邮件，但我不确定。
始终可以选择使用我们自己的 SMTP/POP 服务，但我们确实希望摆脱电子邮件的责任。
谢谢大家
~kvq
We are in the process of building a Multi-Tenant, SaaS type web app. Everything is set to go on the application part but when it comes to email there is a problem.
Each tenant/user of the application has a subdomain based account. However, there will be the option for that tenant to associate a top level domain to their account. Here is where the problem comes for us.
Basically, if the user sets up their DNS to point to our SaaS web app everything works good on the app front except that it now makes us responsible for handling their Email as well. Incoming and Outgoing.
What is the best way to handle this? I really was hoping their is a 3rd party site that handles outgoing and incoming email for multiple top level domains under one company name but am unsure.
There is always the option of doing our own SMTP/POP service, but we would really like to steer away from the responsibilities of email.
Thanks everyone,
~kvq
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
他们不能只设置一条 A 记录或 CNAME 来指向您的服务器吗？
如果他们做了 A 记录，则只允许 webapp.theirdomain.com 访问您的服务器，而其他所有内容都可以保留在他们的 DNS 上。
另一个选择（也许是更好的选择）是他们设置 CNAME。然后您只需设置companyA.yourdomain.com，然后他们只需设置一个CNAME，将webapp.theirdomain.com 指向companyA.yourdomain.com
您真的不想对他们的所有DNS 负责。他们可以将其 DNS 保存在任意位置，并按原样保存 MX 记录。
我希望这有帮助
Can't they just setup an A record or a CNAME to point to your servers?
If they did an A record it would allow just webapp.theirdomain.com to go to your severs and everything else can just stay on their DNS.
The other option and maybe a better option is for them to setup a CNAME. Then you can just setup companyA.yourdomain.com and then they can just setup a CNAME that points webapp.theirdomain.com to companyA.yourdomain.com
You really do not want to be responsible for all of their DNS. They can keep their DNS where ever they want and keep their MX records the way they are.
I hope this helps