OT: ?? Comcast blocked my port 25

[Rick]

On Tue, Jan 27, 2009 at 8:33 AM, Michael Hipp <Michael at hipp.com> wrote:

> Rick Bowers wrote:
>
> Blocking outbound port 25 has become defacto standard for most ISPs I deal
> with (AT&T, Suddenlink, Verizon). I'm also not surprised they might block 25
> inbound. It's all an attempt to stop spam and generally for the good, if a
> pain.


I think this answers my previous question: which port does the server listen
on? It must listen on port 25.

>
> Options:
> - For inbound, switch to using fetchmail to get your email from the various
> servers that are receiving your email (pull rather than push).
> - If you're hosting the email domain on your own box, you are stuck you'll
> have to upgrade to some higher tier of service where they won't block
> things.


I host the server here. So I guess I'm screwed or I have to plead with
Comcast to not block the inbound calls. I only run the server for myself,
but I setup accounts for various services to which I subscribe, so I have
several mail addresses. I like to use Rick-<service>@mydomain.tld. I can do
this, and setup a catch-all account for random messages.

>
>
> The reason that "only one account works" probably is that the one account
> you're hosting at comcast. Just because they allow you to use 587 doesn't
> mean your other email providers are doing the same. Contact them and find
> out what alternate ports they offer. Almost all of them offer alternate
> ports these days.


I have  a couple of Comcast addresses. The primary one works, the two
secondary ones do not. So Comcast either only validates on the primary, or
my mail client is only sending the primary set of credentials. But, I can
send/receive mail using GMail where each account has different credentials.
I'll have to have a chat with Comcast. I just wanted to get an understanding
of how the mail server actually works port-wise. I'm by no means an expert.

>
> Michael
>
Thanks,

~Rick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/linux-users/attachments/20090127/79dfe50d/attachment-0002.html