Selfhosted

39458 readers

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

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

Can i use mailcow on a dynamic IP with DDNS-updater for my usecase? (self.selfhosted)

submitted 9 months ago by kylian0087 to c/selfhosted

11 comments fedilink hide all child comments

Hello everyone,

I am currently running a server with the Pterodactyl panel for various game servers, and it has been working great for several years. However, I would like to set up a system for Pterodactyl to send out password reset emails when necessary. I am considering using Mailcow on the same host specifically for this purpose. Currently, I am using an application named DDNS-Updater to automatically update all records on Cloudflare when my IP changes. While my IP doesn't change often, it can happen; it occurred once this year. Would this pose an issue for a mail server? If the emails end up in the spam folder, it is not a major concern since they are only password reset emails. However, it is crucial that the emails reach the intended recipients.

Thank you.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 9 months ago (1 children)

You need to create an MX record in the DNS zone of your domain. Something like:

@ IN MX 10 my.zome.
@ IN MX 20 server1.my.zome.

You can create 1 MX record or more. 10 and 20 server priority for input mails.

Then you need to create an spf record. There are several options here. For example

@ IN TXT "v=spf1 +a +mx -all"

allows you to send emails from A domain records, then from MX domain records and prohibits from all other hosts.

Theoretically, you can only create an SPF record with A but without MX and dont create MX DNS records. Although I have not tried this configuration.

This is the minimum set after which you will get into spam, but at least the letters will reach.

You also need to make a PTR record to avoid spam folder, but this is not possible on a dynamic IP.

[–] [email protected] 1 points 9 months ago

If A and MX point to the same server you do not need the MX record.

Quite a few mail providers will also just blacklist all dynamic IPs in general.

I would recommend sending the mails via a smarthost (i.e. some authenticated SMTP connection).