IIS 6.0 SMTP NDR 垃圾邮件反向散射
我们在 AWS EC2 上有一个 IIS 6.0 服务器，它正在接收电子邮件并转发到另一个 IIS 盒子上，我们无意中通过 SMTP 服务将 NDR 电子邮件发送到伪造的 From: 标头，并附加了垃圾邮件。
关于 IIS 6.0 SMTP 的一些简单问题
- 从阅读中我们没有看到要停止 NDR（这是设计用于满足 RFC 要求）
- 当我们接受发送到我们地址的所有电子邮件并在单独的计算机上离线处理时，有人可以建议吗为什么首先要交付 NDR？他们是否还利用其他漏洞强制 SMTP 服务器生成延迟和未送达报告？
任何人都可以推荐可以阻止此类攻击的软件。例如 Toriss，来自 Vamsoft 的 ORF
We have a IIS 6.0 server on AWS EC2 that is receiving emails and forwarding onto another IIS box, we are inadvertently sending NDR emails via the SMTP service to the forged From: header with the spam attached.
A few quick questions regarding IIS 6.0 SMTP
- From reading we don't see a was to stop NDRs (this is by design to meet RFC requirements)
- As we accept all emails sent to our address and process off line on a seperate machine can someone advise why NDR's are been delivered in the first place? Is there some other loophole they are using to force the SMTP server to generate Delayed and Non Delivery Reports?
Also can anyone recommend software that can stop this type of attack. e.g. Toriss, ORF from Vamsoft
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您必须在接收计算机上使用 SPF，这样它就不会接受带有伪造反向路径的邮件。稍后在邮件服务器链中无法真正解决该问题。 （请注意，SMTP 反向路径不一定与 From 标头中的地址相同，例如，它们在列表邮件中总是不同。如果 IIS 确实将退回邮件发送到 From 地址而不是反向路径，那么它就会严重损坏.) 如果 IIS 不知道 SPF，那么您必须使用不同的邮件服务器或 SMTP 代理。
You have to use SPF on the receiving machine so it does not accept mails with forged reverse-paths. There is no way to really fix the issue later in the mail server chain. (Note that the SMTP reverse path is not necessarily the same as the address in the From header, for example they always differ in list mails. If IIS does send bounce mails to the From address instead of the reverse-path then it is horribly broken.) If IIS does not know SPF, then you have to use a different mail server or an SMTP proxy.