this post was submitted on 06 Jul 2023
11 points (78.9% liked)

Selfhosted

40439 readers
789 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud
Loki
CannaVet
devve
HybridSarcasm
[email protected]
11
[Abandoned all hope] Trying to self-hosting a mail server, but port 25 is blocked by my ISP (dandroid.app)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/selfhosted
22 comments fedilink hide all child comments
 

So, I spent the last few days researching and then finally setting up mailcow. I got my domain name, my wildcard certificate, got all the containers up, disabled ipv6 (I don't have it set up on my home router and am too lazy to set it up tbh), created a domain and an mailbox, etc.

Well, when testing it late last night, I found that I could receive mail but was getting timeouts when sending mail. After some googling, I found out that this will happen if port 25 is not open. Using traceroute, I found that port 25 traffic is not going outside my home network. And sure enough, I found on my ISP web site that I need to have a business account to unblock port 25, which costs twice what I am paying for internet now.

So what are my options? Is there any way around this? Do I need to host this elsewhere, such as AWS? Can I use a proxy or something that can translate it to a different port for me?

Edit: Yeah, so I just set up an alias to my existing email address. It isn't what I wanted to do, but as many have pointed out, I'm fighting a losing battle here. :(

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 1 year ago

I'll be repeating what's said already but coming from someone who hosts his own non critical email

VPS Either with a TCP reverse proxy back home comming in on an other port (seems most compatible with mailcow at home)

Or hosting postfix on the vps, you could still do IMAP at home