Why does my domain stay at Authentication Pending in Catalyst Mail after I add the SPF and DKIM records?
In Catalyst CloudScale Mail, a domain is authenticated only when Catalyst finds both the SPF and the DKIM record it generated for that domain in public DNS, exactly as the console shows them. The usual causes are a DKIM record with the wrong host name or value, a second SPF record on the domain, or an SPF value typed by hand.
-
In the Catalyst CloudScale console, go to Notify → Mail → Domain and click Validate for the domain to see its SPF and DKIM codes.
-
Add the DKIM record exactly as shown.
-
Copy the SPF value from the console, not from an example, because it can differ by data center.
-
A domain can have only one SPF record. If one exists for another mail service, add the Catalyst
include:value to it instead of adding a second record, keeping oneallterm at the end. SPF also limits DNS lookups per record, so remove includes you no longer use. -
Check both records with a public DNS lookup tool, wait for them to propagate, then click Authenticate in the Authenticate Domain pop-up.
Note: If both records are publicly visible and match the console but the domain stays pending, contact Catalyst support with the domain, the project and your data center.
Refer to the Domains help page for more information.
Updated
Yes
No
Send your feedback to us
Ask AI about this answer