Yes, for your Comcast emails, but not for anything else. I have multiple domains and you can't use 587 to send mail for those domains even with proper authentication. They admitted to me that this is often the case and the only workarounds are: 1. See if your host has an alternate port other than 25 (none of mine do). 2. Use webmail (not a big help) for those. 3. Upgrade to a business account where you get unlimited access to port 25.
Nope, but I got tagged by this problem a while ago and got frustrated by dealing with them. For home usage, it was easy enough to switch Outlook to use a different port. Certainly easier than navigating the Port 25 crew at Comcast, which doesn't seem to be a part of the normal customer service. Port 25 was never really resolved until I got a new modem when I upgraded to VoIP. Then it came back up without a hitch. I would think that you could change the default port for Exchange Server, but I have a fairly low level of expertise on it (just enough not to break things). I've been happy with the performance of my Comcast service overall, but I wish they would have their customer support up on the whole blocking Port 25 situation. That would be a hell of a lot easier than trying to rearchitect your mail service to work around it.
unless that dude gave you permission to post his work address and tell the world he's the guy to contact...that is really uncool to post his email address. r e a l l y uncool. do you even understand that?
I understand that, and he has no problem with it. It has also been posted by the tech people from the chronicle and other papers. You can also google his name since he is all over twitter. http://blogs.chron.com/techblog/arc...ast_following_you_on_twitter_i_doubt_i_1.html Mr. Eliason also gives his email in the comment section of this blog on the chron.. do you even understand that?
I'm confused by #1. You can send to port 25. they wouldn't care. What they are blocking is *your* port 25...not your ability to send to someone else's port 25. From your original post, I thought you were hosting sendmail on your machine. If that is the case, you don't need to use Port 25. You can change it. If you have clients using your machine for smtp services, just change the port number in sendmail and tell your clients to change it in their email client. You might also need to change your MTA in bind to specify the port, but I'm not sure what your setup is. as for #3, that's really what you need to do. Think about it. While you are not using as much upload bandwidth as a 24/7 bittorrent user, you are in a position to charge your clients for your hosting. Maybe I'm not understanding your situation correctly. If you are providing smtp hosting services for clients, bill them for your increased costs in going with a legit business account.
When they block, they block port 25 in both directions from your IP. Nothing at all ingoing or outgoing on port 25 on your IP.
Yo camCost, geT oFf my ManG J BoNeS IP coCkBlockiN'. hE Ain't NevEr SenT SpaM MaleZ. HiZ boAt dUn FloAt dat WaY. He LiKes dA LaDies. FrEe J Bones - SiCk KikiMama
That was not the case with me. I could get mail on Port 25 just fine, but I couldn't sent anything outbound.
I was under the impression that when an ISP blocks Port 25, it prevents the user from sending any mail through any remote mail server. You're forced to send everything through the ISP's servers and authentication protocalls.
Same here. The problem is that they block ALL outgoing mail from your location unless you use 587 and authenticate. According to them, it will sometimes work for people using an alternate domain if you set up the port, change your settings to require authentication and enter in your username and password for Comcast into those settings. It doesn't always work, however, and it didn't work for me.
rocketlaunch, It has happened to me and a couple of friends. I'm a wee bit sensitive to posting batphone-level email address. Apparently, so sensitive I didn't read the thread further, or I wouldn't have figured out that is a fairly public address. my bad and my apologies. k?
No problem Hp.. I feel the same way about private emails. I would not give it out if it was not so readily available etc.
those bastids. lol. guess i was going by outdated info roadrunner told me 3 yrs ago when they mistakenly thought i was misusing bandwidth when i was actually developing smtp server apps...testing/debugging/etc. I didn't have problems with outgoing...but they blocked incoming until i called them to explain. i guess it's a spam thing. it's probably for the best that they block 25 if they see excessive usage...making you upgrade to biz class.
I've actually been lucky and have had no problems with Comcast. Although as soon as FIOS becomes available, I plan on getting that.
yeah, i pretty much hate comcast too. tw never gave me that much trouble, but lately, comcast has been realllllllllllllllllllllllllly slow. i mean dialup speed slow.
About 5 minutes after first reading this thread this morning I got a call from Comcast asking me if I wanted to upgrade to the bundle package (add phone service). I declined. I haven't had any big problems, but I have noticed slower speeds a lot lately.
