Skip to content

Domains and DNSFix domain problems

Fix domain problems

Compare the record in your dashboard with the record DNS publishes. Shipmail checks MX, SPF, DKIM, and DMARC separately, so a pending record shows where to start.

Last updated

Compare the expected and published records

Use the exact DNS value in your Shipmail dashboard for your domain. The examples below show common differences and what they mean.

RecordExpectedObservedWhat to fix
MX@ → 10 mx1.shipmail.to@ → 10 aspmx.l.google.comThe old provider still receives mail. Remove or replace its MX records before you expect Shipmail to receive mail.
SPFOne TXT value that includes include:spf.shipmail.toTwo TXT values that both start with v=spf1SPF has more than one policy. Merge the sending services into one TXT value, then remove the extra SPF record.
DKIMshipmail._domainkey → the full dashboard valueshipmail._domainkey.example.com.example.comThe DNS provider added the domain to a host that already included it. Enter only shipmail._domainkey when the provider appends your domain.
DMARC_dmarc → v=DMARC1; p=reject@ → v=DMARC1; p=rejectThe record is at the root instead of the _dmarc host. Move it to _dmarc and keep one DMARC TXT record there.

Fix host field errors

DNS providers use different names for the host field. They usually add your domain name after the value you enter.

  • Use @ or an empty host for a root record, as your provider requires. Do not enter www for MX or root SPF.
  • Enter shipmail._domainkey for DKIM when the provider appends the domain. Do not enter the full domain twice.
  • Enter _dmarc for DMARC when the provider appends the domain. DMARC does not work from the root host.

If the provider asks for a fully qualified name, use the full name instead. Its help text normally says whether it appends your domain.

Merge SPF safely

Publish one SPF TXT record at the root of a domain. If another service still sends mail from the same domain, keep its permitted mechanisms and add Shipmail's include before the final policy.

v=spf1 include:_spf.google.com include:spf.shipmail.to -all

Keep one final -all or ~all mechanism. Do not append another policy after it, and do not publish a second TXT value that starts with v=spf1. Use the merged value in the dashboard when it is available.

If you do not know which services still send as your domain, do not remove their SPF mechanisms. Check the existing record with the SPF checker first.

Check the record that is still pending

DNS can take time to publish. Shipmail keeps checking in the background. Use these checks to see the public record while you wait.

Email delivery

Emails going to spam

Check that SPF, DKIM and DMARC all pass, then check your domain reputation in the dashboard. A new domain may need to warm up before more of its email reaches the inbox.

Emails not arriving at all

Look for bounce or reject events in the analytics dashboard. Make sure the recipient address is valid and the receiving server isn't blocking your domain or IP. The sending policy page lists the rate limits.

Sent folder not showing sent mail

Most email clients save sent mail over IMAP on their own. If yours doesn't, check the sent folder path in its settings. JMAP clients handle this for you.

Email client connections

Cannot connect to IMAP or SMTP

Copy the exact hostname, port and TLS settings from the connection details page. IMAP uses port 993 with SSL/TLS. SMTP uses port 465 with SSL/TLS by default, or port 587 with STARTTLS if your client explicitly asks for STARTTLS.

Authentication failed

The username is the full email address (user@domain.com), not just the part before the @. The password is the one you set when you created the mailbox.

Still stuck?

If you still can't tell what is wrong, check the DNS setup steps for your provider and the DNS record reference. For delivery problems, see the email authentication guide or IMAP and SMTP settings for setup steps. You can also reach us through the chat widget in the dashboard.