Jari Fredriksson wrote:
[EMAIL PROTECTED] wrote:
If port 25 were blocked from consumers and they were forced to talk to
servers on port 587, even without authentication, then a server could
distinguish consumers from other servers. I think this kind of
configuration could be used to help isolate virus infected computers
from spamming and spreading.

What would prevent virus infected computers from using the port 587 of that would be the common usage?



Nothing. You should be running your outgoing SMTP with authentication and encryption. So the virus sending code wouldn't know what the user name and password is to get through. The software could of course sniff the password out of the email applications running and share user name and passwords for those machines on the same network. Not everyone is going to have an email client they use, but ISPs don't care which IP the user name and password came from.

You could just as well lock down 25 on your outgoing and call it good. Only problem is 25 is blocked at the edge of some networks and you users won't be able to send to you. There is nothing inherently more secure about using the submission port.

Reply via email to