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?
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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
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.