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

[Florin Andrei]

I live in South Bay. My little Linux server at home is connected to the
Internet via Comcast. I've a little dynamic DNS domain associated with its
public IP which I use for email, a blog, etc.

Two days ago, inbound email stopped. I did a few tests - iptables is fine,
Postfix is listening on all interfaces, etc. However, when I tried to
initiate a connection from the outside to my server on port 25, tcpdump did
not register anything, not even the SYN packet. Other ports work fine,
including 80. This is consistent with something upstream blocking incoming
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". I was also informed
that "this will also happen soon to other internet and email providers to
secure all customers' internet and
emails". I replied I think blocking malware-infected computers and open
relays is a good thing, but I don't see why I should be punished with a
crippled Internet link for someone else's bad behavior. No avail.

Anyway. Any suggestions? I'd really like to get my port 25 unblocked,
that's by far the preferred solution.

Thanks.

-- 
Florin Andrei

http://florin.myip.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.svlug.org/archives/svlug/attachments/20130319/a942f312/attachment.htm