Comcast just started blocking port 25 outgoing. I have several computers at home configured to send email reports of cron jobs. Of course they do this by trying to send mail on port 25 from inside the house to my mail server outside. Now that Comcast is blocking that, I need some other way for my emails to be delivered.
The easiest solution I could come up with was to tell my mail server to listen on another port such as 587, and have my firewall route requests for port 25 to port 587. Here is the iptables rule to do that!
iptables -t nat -A PREROUTING -p tcp -i eth0 -d xx.xx.xx.xx --dport 25 -j DNAT --to-destination :587
Where xx.xx.xx.xx is the IP address of my mail server. Now all the computers inside think they are communicating with my mail server on port 25, but the firewall secretly passes the request on to port 587 instead.
#1 by Rebecca Whetstine on January 8th, 2010
This is not working. I spent over two hours on the tel with ComCrap yesterday. Canadian call center chick refused support, did not even know this was happening, US-side fellow spent a huge amount of time. Port 587 and some other setting changes does not fix the “send” problem experienced for three days now using Microsoft Outlook. Their answer? It’s MIcrosoft’s fault. And: since you can use our website, we aren’t going to spend time on this.
Microsoft does not address this. Unable to send email from my home PC now.
Could someone please help with this? I prefer to use mail.softhome.net as my default, but can no longer connect to that server since this arose. Mail.comcast.net only receives mail, will not ship outgoing mail.
HELP!