I recently moved and had to start using a new residential ISP (my old one doesn't serve the new address yet). To my dismay, the new ISP has no option of unblocking the TCP/25 port even when you buy a static IP address, so my home server currently has no inbound/outbound email capability.

Assuming I can install a Raspberry Pi box at work where no ports are filtered, how could I proceed with working around this issue? Tunneling all my traffic through VPN is an overkill, I think.

closed as off-topic by joeqwerty, Michael Hampton Mar 9 at 20:56

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions on Server Fault must be about managing information technology systems in a business environment. Home and end-user computing questions may be asked on Super User, and questions about development, testing and development tools may be asked on Stack Overflow." – joeqwerty, Michael Hampton
If this question can be reworded to fit the rules in the help center, please edit the question.


Managing your own mail server is a more complicated task than running the tunnel between your work and home servers.
Here is the explanation from DigitalOcean why you should think twice before setting up your own mail server: https://www.digitalocean.com/community/tutorials/why-you-may-not-want-to-run-your-own-mail-server

  • 1
    Read that link and do think twice about this plan. If the mail server gets exploited for spam, your employer is going to get blacklisted. Depending on where you work and how well you documented their consent (you are planning to get written consent, right?) you may also be charged with and convicted of a felony. – Oh My Goodness Mar 9 at 13:42
  • Thanks, I appreciate the advice. While the technical solution of setting up a smarthost sounds like a fun exercise, I spent less then half an hour to set up everything I needed (inbound/outbound email + forwarding to GMail) with mailgun.com. They're really good so far, set them up as my smarthost - works like a charm. Fortunately, TCP/587 isn't blocked by my ISP. – dpq Mar 9 at 15:16

My answer was ... How about other ports? There is a chance that if you require encryption on your server, you can work around using port 25.

Not the answer you're looking for? Browse other questions tagged or ask your own question.