[svlug] Comcast is now blocking inbound port 25 - any suggestions?

[Rick Moen]

Quoting Florin Andrei (florin.andrei at gmail.com):

> port 25/tcp.
> 
> I had a long and unenlightening chat with Comcast support today, during
> which I was given such "advice" as "switch to port 465" or "contact IT
> Support of your DNS server to change the allowable port to 25".
> 
> I was eventually told that port 25 inbound is now blocked for all Comcast
> customers "to keep your computer and emails secure". 

(Residential service, as others have noted.)

You should be aware that Comcast residential service simply comes with
that limitation, and will need to switch to something better (i.e. just
about anything) if you wish to send mail directly out 25/tcp to
Internet end-destinations.

By the way:

> I was also informed that "this will also happen soon to other internet
> and email providers to secure all customers' internet and emails".

Bullshit (theirs).  However, what they've done is arguably justifiable
given the storm of rubbish malware-generated SMTP their predominantly
unsophisticated home users are generating.  Which is a problem you would
avoid if you decided to use a provider with a different customer focus.

You can if you wish configure your MTA to relay your outbound mail via
Comcast's MXes using the 587/tcp SMTP submission port or the 465/tcp
ssmtp port.

About 587/tcp:
http://www.justatheory.com/computers/mail/postfix-and-comcast.html 

One drawback of those two approaches is that, then, you inherently are
trusting Comcast's diligence in handling your outbound mail for you.  I
wouldn't, but pick your own poison.