Remove default SPF?

wav3front

Hi,

I've added the mailbaby SPF record in the DNS zone template.

But enhance also adds the default record:
v=spf1 a mx _all

This needs to be removed. The option "Override conflicting" does not work with this.

How can I remote the default SPF on newly created websites?

Thanks
Alex

mike

if you add a txt record v=spf1 a mx include:whatever... -all

it does not override ?

wav3front

mike yes, actually it does.

thanks.

mike

🫶🏻

Andreas

That is interesting, because it does not for me neither.
I have v=spf1 a mx include:relay.mailbaby.net _all added in the "DNS zone templating" and every new account I create it only has the that one SPF record, no more.

wav3front

Andreas

You should only have one spf record.
if you create a new website, does it include the "v=spf1 a mx include:relay.mailbaby.net all" txt record?

slimx

There's a checkbox to override there?

Also..
That's the wrong spf record for mailbaby, IT should be spf-c or something?

nqnoc

slimx

Lately, there is some confusing information about Mail.Baby SPF due to wrong information on their website. I already talked with their team and there are 2 valid SPF records:

relay.mailbaby.net
spf-c.mailbaby.net

Still the recommended one is: include:relay.mailbaby.net

Do not use the _spf-c.mailbaby.net that is present on their website. Is a mistake.

Andreas

wav3front
Yes I only have one.
Yes I have it set to be default SPF. So any new accounts created automatically get that SPF record.

adil

nqnoc Do not use the _spf-c.mailbaby.net that is present on their website. Is a mistake.

I am using spc-c on new domains and its working fine, its even has better delivery to INBOX than relay!

slimx

nqnoc

Support said "relay.mailbaby.net" is the recommended? one This cannot be right. They have said the exact opposite to me and it is clearly stated on their FAQs page that relay.mailbaby.net is the older one.

They just said they'll continue to update it, but naturally it'll eventually be phased out.

nqnoc

adil
You are using spf-c.mailbaby.net and not _spf-c.mailbaby.net, correct?

Andreas

I see this new one on their website too. Odd I was never informed from them about this. I will email them about this and see what they say.

@adil How do you do know it has better delivery? Are you seeing less email in spam folder?

adil

Andreas How do you do know it has better delivery? Are you seeing less email in spam folder?

Yes, I saw someone mention that after he contacted their support they said the spf-c has the new and updated IPs list of MailBaby.

But, idk maybe it was just luck 😃

adil

nqnoc

nqnoc You are using spf-c.mailbaby.net and not _spf-c.mailbaby.net, correct?

Yes!

quags

Relay.mailbaby.net includes all the needed ips and if set up already, this record will continue to work. New set ups should use spf-c.mailbaby.net

nqnoc

slimx

There seems to be different information coming from Mail.Baby staff. Also their website shows in some places “_spf-c.mailbaby.net” that I was told is a mistake.

As you can see on the screenshot from their helpdesk, they told me just a few days ago I should use: “relay.mailbaby.net”: https://ibb.co/4VSN97X

But this is confusing… If you check a DIG test at:
https://digwebinterface.com/?hostnames=relay.mailbaby.net%0D%0Aspf-c.mailbaby.net%0D%0A_spf-c.mailbaby.net&type=TXT&ns=resolver&useresolver=9.9.9.10&nameservers=

You will see that:

“spf-c.mailbaby.net” does not has any ips on its own, just includes the “relay.mailbaby.net”.
“_spf-c.mailbaby.net” the one they say not to use, seems to be the one that includes more IPs.

For now I’m using “relay.mailbaby.net”. Mail.Baby team should put their act together, correct website information and provide just 1 SPF record not to cause confusion.

If anyone has better/updated information from them, please say.

[EDIT / UPDATE] Mail.Baby has updated a page of their website with the current and correct SPF information. This page shows Updated on 14 September, 2024: https://www.mail.baby/tips/spf/