Do I need to add Dubsado to my SPF or DMARC record?

Which address does Dubsado send from?

Until you connect an account, emails sent to your clients come from [email protected] , which is more likely to end up in a client's spam folder since it doesn't appear to come from you directly.

Dubsado says in its own documentation that this email comes from [email protected]. That is Dubsado's own domain, so the email is checked against Dubsado's records, not yours.

Why does my DMARC record not cover these emails?

Author Domain: The domain name of the apparent author, as extracted from the RFC5322.From field.

DMARC is read for the domain in the From address a reader sees. When that domain is Dubsado's, the check uses Dubsado's records.

So your policy, from p=none to p=reject, has no effect on these emails. There is nothing to add to your SPF record for them.

Can Dubsado send from my own domain instead?

Once you connect an email account, anything you send from Dubsado is delivered from your own email address.

Once you connect your own email account, anything you send from Dubsado is delivered from your own email address.

If you turn that on, the email is sent as your domain, and your SPF, DKIM and DMARC records then apply to it. Publish the records Dubsado shows you before you raise your DMARC policy.

Dubsado advises setting up deliverability records for the address you connect.

What should I watch for with Dubsado email?

A forged email can copy the look of a Dubsado message from any address. Read the address it came from, not the name shown, before you open a link or make a payment.