DMARC DNS records for outgoing mail settings.

[BrutalBirdie]

@whiskerpickles
Thanks for that! Sounds good to me
@staff check this out, might be a good idea.

[whiskerpickles]

@brutalbirdie Don't fret, big guy. If you're using Cloudron to manage your incoming e-mail then you are covered. DMARC is implemented in Cloudron... it's just in the wrong place. So if you're an inbound or inbound AND outbound user then you are safe. Outbound only users should create a DMARC policy manually to take advantage of this feature until it's resolved.

[girish]

@whiskerpickles It's this way because we didn't want to trample of the user's existing DMARC record (or add a new record just like that) given that outgoing email is the default for all domains that are added. The user is of course free to add their own DMARC record directly in the DNS, it's just not automated when using outbound only.

When a user chooses "incoming email" as well, we simply set everything up, since it seems like they chose Cloudron to manage all their email. So, we have a bit more "freedom" in creating new records. In fact, if there is an existing DMARC record and you enable incoming email, we don't change it.

Is your idea that Cloudron should add a DMARC record when a domain is added (this is even at installation time)?

[whiskerpickles]

@girish Your logic really opens this up and I get it. You guys know your users and if "outbound-only" folks are managing their own DNS, then it definitely would't make sense. I was just concerned for the less experienced.

I'd say we could close out this thread.

[A Former User]

I have an "Outbound only" (from the outset) domain at Gandi, with a DMARC record created by the Cloudron:-

_dmarc	TXT	300	"v=DMARC1; p=reject; pct=100"

So, looks like DMARC records are already created for both 2-way and outbound only domains.

Confusion may arise because https://my.domain.tld/#/email shows the existence of a DMARC record for 2-way domains only.

[girish]

Whoops, indeed, I stand corrected. What @Hillside502 noticed is correct. It seems we setup DMARC policy for outbound mail as well (but only if there is no existing record). For some reason, I thought this wasn't the case.

[girish]

@pintudaso are you a real user or is this some very creative spam ? apologies if you are a real user but the amount of spam on this forum is crazy.

[pintudason]

Before creating DMARC records it's a good idea to test DKIM and SPF. Testing can be found here: https://emailauth.io/dkim

[micmc]

@pintudason said in DMARC DNS records for outgoing mail settings.:

Testing can be found here: https://emailauth.io/dkim

Hi thanks for the share.
However, it seems to me that this is not working very well, unless I'm missing something. I've DKIMs for all my domains and this thingy responds with a "No DKIM record found for: xxx" message for all domains I've tried and I know for a fact that DKIMs are implemented a long time ago. Anyone else have tried this?

I manage my DNS through Cloudflare, maybe it's the reason why. (?)

[whiskerpickles]

@micmc Can you share one of the domains so I can have a look?