Yahoo、Gmail、Hotmail 和 AOL 是否有白名单？
在我的网站（正在开发中）中，成员可以互相发送消息，这些消息会直接发送到他们的电子邮件，现在我担心某些成员可以向其他成员发送垃圾邮件（我有一个垃圾邮件过滤器，但它没有提供如您所知，100% 保护），我担心我的域可能会被 Yahoo、Gmail、Hotmail 或 AOL 列入黑名单，这将导致从我的域发送的任何邮件最终进入垃圾邮件文件夹，这就是我想添加的原因将我网站的域名添加到他们的白名单（如果存在）。
PS 我不想使用会员在网站上查看的私人消息，我这样做是有我的理由的。
谢谢
In my website (under development), the members can send messages to each other which are sent directly to their email, now I'm worried that some members can send spam to other members (I have a spam filter but it doesn't give 100% protection as you know), I'm worried that my domain might get blacklisted on Yahoo, Gmail, Hotmail or AOL which will cause any messages sent from my domain to end up in the spam folder, this is why I want to add the domain of my website to their whitelists (if they exist).
P.S. I don't want to use private messages that members check on the site and I have my reason for this.
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您的电子邮件可能不会被视为“批量”，因为它听起来像是“一>一”而不是“一>多”，但这些批量邮件帮助资源可能仍然有帮助：
正如 Bevan 提到的，您的任务将是一项持续的任务，以保持您的网站在各种服务上的清洁。
不确定您是否已经在考虑这一点，但您可以“代表”请求用户发送电子邮件（即将发件人和回复字段设置为发送消息的用户）。
Your email might not be considered "bulk" because it sounds like it's one->one as opposed to one->many, but these bulk mail help resources might still be helpful:
As Bevan mentioned, your task will be an ongoing one to keep your site clean on various services.
Not sure if you're already considering this, but you can send the email "on behalf of" the requesting user (i.e., set the from and reply-to fields to the user who is sending the message).
虽然这些网站可能使用白名单，但我怀疑它们只会对正在使用的评分系统做出贡献 - 列入名单本身还不够。
总体控制因素将是您网站的“声誉” - 您需要努力确保声誉保持良好。
不幸的是，对于您的工作量来说，我认为这将是一项持续的任务，而不是一次性的。
While there may be whitelists used by those sites, I suspect that they only contribute to whatever scoring system is in use - being on the list won't be sufficient in itself.
The overall controlling factor will be the "reputation" of your site - you need to work to ensure that reputation stays sound.
Unfortunately for your workload, I think this will be an ongoing task, not a one-off.