# (Archive) Unblock Port 25: Getting Schooled by a sysadmin

Contents

If you didn't know, I host my own mail server here at mail.simonxiang.xyz (don't try to type that into your browser). Although setting it up is usually a long and forlorn process (or so I've heard), for me it was actually quite simple. There's a YouTuber out there that goes by Luke Smith that wrote a nice script to easily set up mail on your new server. If you just read the README and make sure you have all the requirements set up on your domain registrar and VPS provider, it's a two minute process to run the script and be on your merry way with a fancy new email server.

However, after setting it up I couldn't send mail for some strange reason. After testing two possibilities (domain on a spam list, postfix configuration issue), my cocky self decided that I didn't mess up anywhere when installing and that my VPS provider, Vultr, had blocked the port that allows me to send email (port 25) so I couldn't use their VPS to send spam emails or something like that. So I sent them a slightly condescending support ticket that went something like this:

Hello Vultr, Can you unblock Port 25? I know y'all are blocking it because you think I'll send spam emails or something, but I promise I wont.

Regards,
Simon

In 57 seconds, a system administrator at Vultr responded with this (not verbatim):

Hello Simon,

We're not blocking port 25 access. Check your instances firewall rules and listening services, you can do this by running netstat -uplnt | less. Furthermore, also run iptables -L for firewall rules, and iptables -F to flush rules from the chain: to test outbound port 25 access, run telnet portquiz.net 25. Thanks,

[omitted for privacy],