Comcast decided to start blocking my smtp connections last week. I had an amusing talk with the technical service rep. I told him what had happened, and that they were firewalling port 25. He responded that I needed to send all email through comcast's smtp server (and into their archive I'm sure), but they hadn't implemented any recent changes. He suggested that I contact the Thunderbird corporation to ask for support. I was really polite and explained to him that thunderbird was an open source email client - I think it worked partially, but trying to get my smtp access restored seems like a losing battle. Back to pine on my server I guess, hopefully they won't firewall off 22 anytime soon :)
Re:Port 587
Phred on 2008-01-23T17:21:53
I have not - I was pretty unhappy yesterday about this, but I will probably compromise today and try it out
:) I understand the spam concerns, but I pay for the line and should be able to use it as I see fit. Re:Port 587
merlyn on 2008-01-23T18:11:10
Yeah, you should be able to use it as you see fit. Unfortunately, for 97% of America out there running windows on home Comcast lines, they're running Windows and are running zombies, and I for one, am very happy that Comcast is blocking port 25 outbound, and wonder why they didn't start sooner.but I pay for the line and should be able to use it as I see fitRe:Port 587
Phred on 2008-01-23T21:09:52
Ok 587 is working great now with a change to my qpsmtpd configuration
:) I wonder how long before the spammers start flooding that port...
Re:Clarification
rjbs on 2008-01-23T14:42:33
#2 is also very common.
Add -2 for safety if neither end prevents proto v1. OpenSSH may need -n and -N, but busybox version doesn't.ssh -L2110:pop.hostname.com -L2025:smtp.hostname.com:25 -l myid shell.hostname.com &