|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PLUG] Comcast and port 25
|
Yes, I had the same problem with running a smtp server. Port 25 is blocked to
incoming and outgoing traffic. To send eMail, I had to have my mail server
connect to Comcast's server on port 587. Thye would gladly relay my mail as
long as I was a customer.
Incoming mail is impossible, unless you use one of the redirecting services
which receives your mail, then redirects it to you on another (unblocked)
port.
BTW, I don't think comcast blocks everybody on port 25. It (the blocking)
apparently is triggered somehow, or maybe they've been gradually blocking it
for more and more customers.
On Friday 23 January 2009 12:09:08 pm jeff wrote:
> Our sister work office had 2 complaints about not being able to access
> POP mail from home. In both cases, Comcast (the remote provider)
> claimed it was because they closed port 25 `due to spam'.
>
> I am a Comcast customer and haven't had any problems.
>
> I have heard that Comcast meters traffic and that they're simply
> blocking the port period. People here have stated that they can't run
> servers because of this.
>
> Something about this isn't right.
>
>
> Anybody know anything more about this?
>
>
> Thanks,
> -jeff
--
Casey Bralla
Chief Nerd in Residence
The NerdWorld Organisation
___________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|