Getting Around SMTP Blocks |

I am spending the week in Beckley, WV visiting Treah’s parents. They have Suddenlink for there cable tv and internet provider.

I fired up my laptop this evening, got on there wireless, and went to reply to a couple emails. All of them failed to send. I tried telnet’ing to port 25 on my smtp server, it never connected. I though this was odd. I ssh’d over to my web host and tried the same thing. It connected right away.

I’m not hell bent on using my own smtp server, I just want to use thunderbird to send my email so I can avoid using a slow/clunky webmail app. So I thought I would try to use Suddenlink’s smtp server (smtp.suddenlink.net). Wouldn’t you know they make you authenticate to use there smtp server. Since I’m not one of there customers I don’t have an account to authenticate with. They’re sure making this hard.

I turned to trusty google and found out they are indeed blocking port 25 to all hosts except there own, to help prevent spam and viruses. You can read there “Unsolicited Email Spam FAQs” for yourself if you want more information on this. I’m not sure this is the best approach, but that’s a different story.

To get around this policy I decided to try and connect via SSL encryption rather than TLS encryption. This changes the port you connect to from port 25 to port 465.

After making the change my mail sent out right away. So if you’re having problems sending mail through your own SMTP server give this a try. You may also have success just changing the port your SMTP server listens on.

No Responses to 'Getting Around SMTP Blocks'

Leave a Reply


July 2019
« Jan