MWR2NY
join:2002-02-06
Edgewood, MD
| reply to jester121
Re: Thanks Idiots!
I'm on Comcast and last November when Comcast decided to block port 25 they didn't tell anybody including their own tech support. I went about a week without being able to send mail through my own domain. It took a couple days of tech support at my web host to figure out a work around. Comcast and other ISP's should of posted something to let everyone know what they were doing. |
|
Nice Try5
join:2003-04-17
Silver Spring, MD | I don't believe comcast is blocking 25 in my area. I can still send and receive mail. |
|
pnh102
Reptiles Are Cuddly And Pretty
Premium
join:2002-05-02
Mount Airy, MD
 ·Comcast
| reply to MWR2NY
said by MWR2NY  :
I'm on Comcast and last November when Comcast decided to block port 25 they didn't tell anybody including their own tech support.
This is somewhat off-topic but there was a time when I thought Comcast had done the same thing to me. I contacted Comcast through a support email and they told me they had not started blocking port 25. The problems turned out to be the result of me changing the MAC address of my router and not changing some settings therein to make it work right. Once I changed the MAC address to the original one, my email worked fine.
--
Do the world a favor, Saddam. Kill yourself. |
|
purdyturdy
@207.46.x.x
| reply to Nice Try5
Same here, Seattle area and can send mail through Comcast to my own SMTP server at another ISP (which uses SMTP auth).
-template-
I say they should block port X, because a virus/trojan/worm/backdoor/spammer/hax0r could pass traffic through that port to do naughty things.
-endtemplate- |
|
