jester121
Premium
join:2003-08-09
Lake Zurich, IL
 ·surpasshosting
 ·ViaTalk
| reply to pnh102
Re: Thanks Idiots!
said by pnh102  :
Second, its mail.comcast.net, not smtp.comcast.net 
Third, you're welcome to spend all the time you want trying to send SMTP traffic through Comcast's POP3 server, but you'll find it rejects connections to port 25. Just as it should... 
The correct address is smtp.comcast.net
said by pnh102 :
True, but still it begs the question, why should someone who is not part of the problem be inconvenienced?
Still don't see how it inconviences you to change a setting once, especially given the positive upside. |
|
dilettante
join:2002-01-01
Haslett, MI
| reply to pnh102
I've often thought that licensing (certifying) users might be a reasonable tactic. Something where you'd agree to random external audits of your network (scans and other penetration tests, monitoring traffic over an interval).
But there are cost and privacy issues I suppose, and it would really cut into the lucrative "granny (grandpaw?) AOL" market of low-use, unsophisticated users.
But I have to wonder... wouldn't it make economic sense to offer high bandwidth to "certified" users and lower bandwidth and blocked ports to those "potential problem users" who are likely to get hijacked - at the same or similar prices? If you keep your network clean and properly isolated and your boxes secure and use adequate throttling mechanisms... [takes a breath] any real hazard from running services is minimal. Violations or complaints and you'd get dropped back to the "wild west" service with ports blocked.
Sort of a "being responsible grants privileges" policy.
But maybe that's precisely where those high-cost commercial offerings come in: you pay for the privilege of being responsible. Everyone else "swims with the fishes" wearing a hardsuit. |
|
RARPSL
join:1999-12-08
Suffern, NY
| reply to ChrisN4BSA
said by ChrisN4BSA :
This isn't totally true. I'm net admin for a company here in Tampa, and was able to use our company SMTP server (port 25) via my home Roadrunner connection.
However - just today we have implemented a new non standard inbound SMTP port that will allow us to get around the port 25 filtering for those employees that are lucky enough (or is that unlucky?) to be on an ISP that blocks port 25 SMTP traffic.
And - as much as it sucks, amen for the ISP's blocking port 25. I hate to be punished for clueless users, but if it helps slow down the spread of viruses that spread via email, I'm all for it. I'm sick & tired of having to spend hours every day checking our mail quarantine because of all spam zombies in the wild.
The DESIGNATED port to use to inject Email (ie: Send it from a Mail Client) is 587 NOT 25. The problem is that many ISPs are too lazy to activate this port and require SMTP AUTH to access it. Most just say use Port25 and block out-going Port25 to other servers. IMO, ANY ISP that blocks outgoing (to non-ISP Owned SMTP Servers) that DOES NOT accept incoming Email from their customers (while those customers are using Non-ISP Connectivity) on Port 587 is a Hypocrite. |
|
pnh102
Reptiles Are Cuddly And Pretty
Premium
join:2002-05-02
Mount Airy, MD
 ·Comcast
| reply to jester121
said by jester121 :
The correct address is smtp.comcast.net
Oops... you are indeed correct, my bad! Goes to show you how often I use my Comcast email LOL.
--
Do the world a favor, Saddam. Kill yourself. |
|
