Selfhosted

40296 readers

301 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Question about Mailcow on Netbird (lemmy.world)

submitted 4 months ago by forestgoat@lemmy.world to c/selfhosted@lemmy.world

7 comments fedilink hide all child comments

I set up Netbird with Nginx Proxy Manager to reach my self-hosted servers. But I can't get it to configure Mailcow. Does anyone have an idea how I can make Mailcow work with Netbird and NPM?

top 7 comments

sorted by: hot top controversial new old

[–] Capillary7379@lemmy.world 3 points 4 months ago

It should be easier to port forward SMTP to the mailcow installation for incoming mail and only use NPM for the web interface.

If netbird has enough DNS support you might be able to setup all the mailcow recommended settings there so you have auto discovery from mail-clients on the netbird VPN.

Incoming mail is pretty easy to get working anywhere, but outgoing is restricted if your IP adress is in any way suspicious. Using sendgrid, authsmtp, or something similar is the easy way.

For the hardcore, finding a VPS with a company that blocks outgoing smtp as default but will unblock if you convince them you're responsible can be fun and/or frustrating. You'll have a mail relay there for outgoing email at the minimum but can also get incoming email via that server. The smallest possible server should be enough.

[–] forestgoat@lemmy.world 1 points 4 months ago

Apart from that, I'd like to host Mailcow myself. I tried to do this via the option stream in NPM but that doesn't work.

[–] Decronym@lemmy.decronym.xyz 1 points 4 months ago* (last edited 4 months ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters	More Letters
DNS	Domain Name Service/System
HTTP	Hypertext Transfer Protocol, the Web
IP	Internet Protocol
SMTP	Simple Mail Transfer Protocol
VPN	Virtual Private Network
VPS	Virtual Private Server (opposed to shared hosting)
nginx	Popular HTTP server

6 acronyms in this thread; the most compressed thread commented on today has 7 acronyms.

[Thread #836 for this sub, first seen 29th Jun 2024, 07:05] [FAQ] [Full list] [Contact] [Source code]

[–] JohanWillemsen@feddit.nl -1 points 4 months ago (1 children)

Its not recommended to put Mailcow on a home network. You also need PTR set, witch you normally do at your vps hoster.

[–] Goodtoknow@lemmy.ca 3 points 4 months ago (2 children)

What's wrong with it on a home network?

[–] JohanWillemsen@feddit.nl 2 points 4 months ago

Sending email from home connections is extremely difficult because almost all providers blacklist home ISPs. You also need PTR to be accepted by Gmail. And with tunnels or VPN you most likely get network issues.

[–] toastboy79@kbin.earth 0 points 4 months ago

it used to run pretty well on one, but the lead dev made significant changes making it a bitch to run without doing it "his way". What I ended having to do was change my nginx configuration so that I was using the one in his docker-compose directly as opposed to running my own that would point to his for mail related needs.

I forgot what exactly broke but when I reported that breakage I basically got told "tough shit, it works on my set up", I don't remember being demanding or impolite just reporting the issue and asking if he was aware of/had plans to fix it. Not too long after the product was acquired and I chalked it up to enshittification and shitty dev being a shitty dev.

TLDR; good luck and ymmv