[Mis] Adventures in Raspberry Pi Web Server

So I’ve been trying to get this server to work for about a week now. Certain things I can work out quickly because of my past hosting experience, others I have to research for hours – crazy Postfix/Dovecot config files 🙂

It turns out that my ISP, Comcast, blocks port 25 across the board. No incoming or outgoing traffic, period, not even for those who call and nicely request it. Port 25 is what all email servers operate on – at least at first. Usually there’s a quick handshake before the two clients hop on over to port 587 or 993 for a “private” session that is more secure. But since the initial interaction takes place on port 25, it’s impossible to have an email server – either receiving or sending – without that port.

After spending so much time on this, it really made me a bit frustrated. All that time where things weren’t working was really just my monopolizing ISP denying me services that I should have access to.

Whether they have a right to do this is the subject of much debate. It’s similar to the “net neutrality” issue. What rights do ISPs have to limit bandwidth or services? Can they eavesdrop on your connection and keep track of where you visit? Do they provide a “backdoor” so that the government can spy on you if they suspect you of being a “terrorist”?

The answers to these questions may shock you.

The trickle-down effect this policy has though… that’s what I hate. The result. Geeks like me can’t be geeks at home the way we should be able to. I am dependent on my server company (and they aren’t cheap) when I could be doing everything I need myself. The technology for hosting email servers and websites has existed for decades for free!

You could just say “get a new ISP”. Yeah, but due to increasingly fewer ISP choices, many areas are down to one or two options. Some people would call this a monopoly. Maybe I’ll start my own ISP someday 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *