Port 587 is mostly used for TLS encrypted SMTP. Blocking outgoing 25 is
madness. Email is one rudimentary service everyone expects from their
Internet connectivity and not everybody uses web mail interfaces.
machines from spamming. Why do you think yours stopped incoming port
25? Probably just easier to block it in both directions?
I guess because terms of service for a home user do not cover serving from
the user's site. Ron Minnich said it's his home machine so I assume he has
paid for a plan with the word "home" somewhere in the plan title or the
ToS. ISPs like to distinguish "servers" from "clients" so that they can
safely cram as many little "clients" into one big channel as possible.
"Clients" don't expect quality of service--most of them don't _understand_
quality of service.
A dial-up ISP I once bought services from used to block ICMP. When I
complained they said it was to safeguard the users against Smurf attacks. I
knew it was to safeguard themselves against users snooping into their
poorly configured internal network. I went as far as getting a prompt from
one of their routers--it had a never-configured telnet server running--but
I didn't know what to do next. It was no use anyway.
--On Monday, November 10, 2008 9:59 AM +0000 jfmxl <[EMAIL PROTECTED]> wrote:
My ISP was blocking port 25 outgoing, so I could send mail to my own
mailserver. It turned out that sendmail was listening on port 587 as
well, so I use that instead.
I assumed my ISP was blocking outgoing port 25 to stop captured
machines from spamming. Why do you think yours stopped incoming port
25? Probably just easier to block it in both directions?
