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
Port 587 (Score:1)
Re: (Score:1)
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: (Score:2)
Re: (Score:1)
Ok 587 is working great now with a change to my qpsmtpd configuration :) I wonder how long before the spammers start flooding that port...
Just because I enjoy being a pedant (Score:2)
Clarification (Score:1)
Both are retarded and obnoxious, though #1 is a well known policy, blocking #2 though.... sigh.
Re: (Score:1)
rjbs
ssh can rescue smtp (Score:1)
Add -2 for safety if neither end prevents proto v1. Open
Bill
# I had a sig when sigs were cool
use Sig;