5 ms·
This is the lamest approach to fighting spam. A better approach is for the ISP to block outgoing port 25 from their network, and force their users to use their
by josho 12y ago
This is the lamest approach to fighting spam.
A better approach is for the ISP to block outgoing port 25 from their network, and force their users to use their mail relay that requires authorization. Any accounts that are caught spamming can then simply be terminated as customers. This approach is also quite common.
- bsder 12y agoThis is the lamest approach to network security. Now I can't reach MY email server which sits in a colo on port 25. So, now I have to put my mail server on port 80 just so I can get out of the network. Some of us don't trust the email servers run by the ISP.
- brongondwana 12y agohttps://www.ietf.org/rfc/rfc2476.txt https://www.ietf.org/rfc/rfc2476.txt December 1998 It's hardly your ISP's fault that you are 16 years behind best practice.
- nitrogen 12y agohttps://www.ietf.org/rfc/rfc2476.txt https://www.ietf.org/rfc/rfc2476.txt December 1998 It's hardly your ISP's fault that you are 16 years behind best practice. Could you be so kind as to point to the relevant section of RFC2476?
- tedunangst 12y ago> Port 587 is reserved for email message submission as specified in this document.
- bsder 12y agoIt is my ISP's fault for BLOCKING THOSE PORTS. And, since I don't really have a choice of ISP, I can't change that. Some of us live in the real world where we wind up having to do things like put mail servers on port 80 or 25 because that port doesn't get blocked. Thanks for playing.
- arjie 12y agoDoes that actually change anything? If everyone used 587 for MSAs, then the ISPs would have to block 587 and use their own relay to prevent spam (under GP's solution). I mean, it doesn't change anything, does it?
- jauer 12y agoUsing 587/MSA implies[1] authentication which implies that the client is using a server that is responsible for the email sent through it. [1]: http://en.wikipedia.org/wiki/SMTP_Authentication http://en.wikipedia.org/wiki/SMTP_Authentication
- jitix 12y agoYou cannot enforce something just because it's 'best practice'. Why should the ISP restrict a user form running HTTP on port 25 and SMTP on port 80?
- rakoo 12y agoIt is my ISP's fault if my ISP blocks a port and doesn't let me any way to unblock it, whatever I do with my port. My ISP's job is to forward packets, not something else.
- cm2187 12y agoA third of the ISP don't even support TLS/SSL on their outgoing traffic. Gmail publishes some interesting stats on that. Having to go through your ISP smtp is nearly as bad as no encryption at all.
- dingaling 12y ago> A better approach is for the ISP to block outgoing port 25 from their network No thanks! My ISP's job is to provide internet access. Blocking ports violates that. Would you condone an ISP relaying all port 80 traffic to reduce forum spam?
- CamperBob2 12y agoTo keep you from denying internet (i.e, email) access to everyone else, they should block the port by default, then unblock it if you demonstrate that you know what you're doing by calling them up and asking them to unblock it. Seems harmless enough. Agreed?