I use outlook as my email manager. When comcast moved away from port 25 i lost the ability to send out bound emails through my company's server for my business franchise. i can receive but can not send. It will just hang up in the outbox. When I contacted the company there help desk said they are not equipped to help with outlokk and i have to contact comcast to get an alternate port. Does this make sense and if so what configuration should i use?
The recommended settings can be found in this clickable link: LINK
Need Email Help? Please post the following information in your post. Do you use XfinityConnect? The Full or Lite version? Do you use an email client? Which one? (Eg; Windows Live mail, Outlook, a smartphone etc.) Which browser/version do you use? And- have you cleared your browser cache? Which operating system? XP, Vista, Windows 7, Mac OS X Details of the problem you are having.
Your company's email server should be supporting authenticated send (it is an internet standard after all), especially since many ISPs are implementing Port 25 blocks. Port 25 does not require authentication, therefore it is easily compromised by spammers. Check with your IT dept. to see if they support Port 587 with plain text authentication over an encrypted connection, or port 465 with authentication and SSL encryption. If they do not support one of these alternative ports, your only option is to use Comcast's SMTP for outgoing mail until your company changes their policy.
Your company's email server should be supporting authenticated send (it is an internet standard after all), especially since many ISPs are implementing Port 25 blocks. Port 25 does not require authentication, therefore it is easily compromised by spammers.
That's not quite the right slant on things. Comcast could require authentication when connecting to their outgoing servers on port 25 just by twiddling a knob or two. And, in any case, the outgoing Comcast servers are rate limited, so they're not very attractive to spammers. Yes, we've seen instances where accounts have been compromised and spammers have used webmail to send spam to the address book contacts, but that's not the norm, and it has nothing to do with port 25, anyway.
The reason port 25 gets blocked isn't because it's "easily compromised by spammers.", it's because it's the port that every MX server on the Internet "listens" on, and ISPs don't want their spambots to be able to send email to the outside at a rate that's limited only by the bandwidth that's available.
Comcast arbitrarily took action without regard to the consequences of their end users.
Not "ALL" ISP's block 25, they often permit port 25 usage, but block inbound 25 connections to their own servers.
There are home monitoring systems that send alerts via port 25 e-mail messages ( I have one ) as well as a slew of other alerting devices and software that Comcast has rendered useless.
Comcast could have put up an "opt out" web page or program with a few hoops to jump through to discourage most casual users. That followed with a warning about potential problems with Port 25 and the termination of support for port 25 from their own servers, would take care of 99.9% of the complaints and issues they have.
As it is, port 25 blocking is just another Draconian move.
And Steve is correct that many ISPs block port 25 entirely from customer connections.
That's not what I said, and I don't think that's true. I think that most "home" ISPs block *outgoing* port 25, but allow users to reach the ISP's SMTP servers on port 25. Which would be fine for the "notification" scenarios that Anon154847 mentioned.