spamhaus.org 上列出的 heroku 公共 IP
我在 heroku 上托管一个客户网站。客户端将其自定义域名（A 记录）指向 heroku 的公共 IP 之一。现在，我的客户联系我并抱怨说，由于 www.spamhaus.org (http://www.spamhaus.org/sbl/sbl.lasso?query=SBL107993 ）。现在垃圾邮件发送者是一些网址缩短器，与我客户的业务无关。
我在谷歌上做了很多搜索，但发现很少。只是问题与共享 IP 有关。但解决办法是什么？由于 Heroku 托管大型应用程序，肯定还有其他人遇到同样的问题？或者有一个简单的技巧可以解决这个问题吗？
干杯 缺口
I'm hosting a client site on heroku. The client is pointing their custom-domain-name (A-record) to one of the public IPs of heroku. Now, my client contacted me and complained that their emails are being rejected by one of their biggest clients due to a sbl-listing of the same IPs on www.spamhaus.org ( http://www.spamhaus.org/sbl/sbl.lasso?query=SBL107993 ). Now the spammer is some url-shortener and has nothing to do with my clients business.
I did a lot of searches on google, but found little. Just that the problems have to do with shared IPs. But what is the solution? And as heroku is hosting big applcations there must be others having the same issue? Or is there one simple trick to solve this?
Cheers
Nick
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
遇到同样的问题，这里没有简单的技巧。以下是 Heroku 对此事的支持回应：
参考
我们来自 Spamhaus 的链接：http://www.spamhaus.com spamhaus.org/SBL/sbl.lasso?query=SBL107992
摘要
更新
Heroku 支持人员表示可能需要数周时间才能解决该问题。
Have the same problem, no simple trick here. Here is Heroku's support response to the matter :
Reference
Our link from Spamhaus : http://www.spamhaus.org/SBL/sbl.lasso?query=SBL107992
Summary
Update
Heroku support says it may take weeks to resolve the issue.
这是影响许多托管公司的普遍问题。垃圾邮件发送者可能正在使用 Heroku 发送垃圾邮件，并玷污了 Heroku 的 IP 地址空间。解决这个问题确实需要几周的时间，因为 Heroku 必须向 Spamhaus 证明他们已经制定了限制垃圾邮件的政策和程序。
您可能建议 Heroku 查看有关出站垃圾邮件控制的 Wikipedia 内容：http://en.wikipedia .org/wiki/Anti-spam_techniques#Outbound_spam_protection
这是一个复杂的问题，特别是对于 PaaS 提供商来说，他们当然正在尝试使应用程序的托管变得自动且简单——这对垃圾邮件发送者很有吸引力。
This is a general problem that affects many hosting companies. Spammers are probably using Heroku to send spam, and have tarnished Heroku's IP address space. It will indeed take weeks to resolve this, because Heroku will have to prove to Spamhaus that they have put in place policies and procedures to limit spam.
You might suggest that Heroku review the Wikipedia content regarding outbound spam control: http://en.wikipedia.org/wiki/Anti-spam_techniques#Outbound_spam_protection
It's a complex issue, particularly for PaaS providers, who are of course trying to make hosting of apps automatic and easy - something that appeals to spammers.