大网数据广告活动
服务器运维问答

How does blocking port 25 prevent spam (but not 587)?

· 52CE 我爱测

It is common practice for ISPs and cloud providers to block outgoing traffic on port 25. I understand this is to prevent spam; e.g. a person could launch an Amazon EC2 instance, and send a million emails. But for example, port 58…

问题原文

原帖链接 · CaptainCodeman · CC BY-SA 4.0

It is common practice for ISPs and cloud providers to block outgoing traffic on port 25.

I understand this is to prevent spam; e.g. a person could launch an Amazon EC2 instance, and send a million emails.

But for example, port 587 can be used to send email as well, and it is not commonly blocked. So why can't a person send a million emails through port 587?

Basically, I'm asking, what is special about port 25 that makes it more prone to abuse than 587?

已采纳解答

原帖链接 · anx · CC BY-SA 4.0

You are right it does not completely prevent spam, but from a business perspective what matters for the cloud provider is something slightly different than trying to prevent all spam.

Cloud hosters do not have strong incentives not to take money from spammers. The thing that hurts them is being the owner of the IP space the spam is delivered from. They do not want to be that cloud hoster everyone blocklists. That would be a less useful & thus less profitable cloud hoster!

For spammers, these are just two paths to the same goal:

  1. abusing some random companies cloud servers to send spam via port 25, potentially directly to the victim
  2. abusing some random companies mail (service provider) credentials to send spam via an authenticated smtp session on port 587, relayed by some other party

But for the cloud hoster, there is a huge difference:

  1. in option 1, the complaints and mitigations are directed at the company providing the server, the cloud hoster
  2. while in option 2 people will blame & take action against the person having their smtp credentials compromised and/or the last relay that accepted the compromised credentials. The cloud hoster does not lose (as much) credibility&reputation in that case.

Someone spamming port 25 is someone I can put on a blocklist. If the cloud hoster recycles network addresses quickly, my mitigation will cause collateral damage for his next customer, and thus for him.

If someone is spamming me via abused smtp logins on port 587, his spam will enter my systems mixed with other, clean mail. I can less effectively use network-level blocking there - and if I do, I will more likely target a later relaying party.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2020-12-14)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。