Rackspace Email is the sensible sedan of business mail. It starts every morning. Nobody writes about it. Many of the domains parked on it were set up years ago by a consultant whose invoice is the only surviving documentation, and they have run without complaint ever since.
Then the rules changed around them. Large mailbox providers now expect a domain to authenticate its mail, and a domain with no DMARC record is one that any stranger can impersonate without resistance. The good news: Rackspace gives you everything required. There are three records to publish, in a fixed order, and none of them is difficult.
Before you start: find your DNS
Every step below happens in DNS, and your DNS may not be at Rackspace. It lives wherever your nameservers point: often the registrar, sometimes Cloudflare, occasionally a web host no one remembers choosing. Find out before you begin. A record added to the wrong provider’s panel is a record no one will ever read.
Start by taking stock. Run your domain through the domain health check. It reports your current MX, SPF, DKIM, and DMARC records in one pass, so you know what exists before you change it. Then confirm that mail is actually routed to Rackspace. The MX lookup should show:
example.com. MX 10 mx1.emailsrvr.com.
example.com. MX 20 mx2.emailsrvr.com.MX records govern incoming mail and have no part in DMARC. But if they point somewhere else, you are reading the wrong guide, and it is better to learn that now.
Step 1: Publish one SPF record
SPF is a published list of the servers allowed to send mail using your domain in the envelope sender. For a domain that sends only through Rackspace, the record is short:
example.com. TXT "v=spf1 include:emailsrvr.com ~all"The include authorizes Rackspace’s outbound servers. The ~all at the end tells receivers to treat everything else as suspect.
Now the rule that catches people. A domain may have exactly one SPF record. If a record beginning v=spf1 already exists, do not add a second. Two records produce a permanent error, and receivers treat that as no valid SPF at all. Edit the one you have. If you also send through a newsletter service or a CRM, the result looks like this:
"v=spf1 include:emailsrvr.com include:_spf.newsletter-tool.example ~all"The second include is a placeholder; use the value your other provider documents. The SPF record generator will merge senders into a single record, and the SPF checker will count your DNS lookups against the limit of ten. For background on how the mechanism works, see What Is SPF?
For mail sent from a Rackspace mailbox, SPF tends to align without extra effort. The envelope sender is the user’s own address, on your own domain, so the domain SPF checks is the same one in the From line.
Step 2: Enable DKIM in the control panel
SPF has a known weakness: it breaks when mail is forwarded, because the forwarding server is not on your list. DKIM does not have that weakness. It attaches a cryptographic signature to each message, and the signature travels with it.
Rackspace does not sign your mail until you ask. DKIM is enabled per domain in the Cloud Office control panel:
- Sign in to the Cloud Office control panel as an administrator.
- Open the domain settings and find the DKIM (sender authentication) section.
- Select your domain and enable DKIM. The panel generates a selector and a public key.
- Copy the TXT record it shows you: a hostname and a long value.
- Publish that record at your DNS host, then return to the panel and verify.
The record has this shape:
Host: selector._domainkey.example.com
Type: TXT
Value: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A...The selector name and the key are generated for your domain. Copy both exactly from the control panel. We will not guess at them here, and neither should you.
The value is long, and long values are where the trouble is. A single string in a TXT record cannot exceed 255 characters, so a 2048-bit key must be stored as two or more quoted strings in one record. Most DNS hosts split it for you. A few make you do it by hand, and a few silently cut the key short. After publishing, enter the selector in the DKIM checker. It reports whether a key was found, how long it is, and whether it parses. If the result is odd, the guide to common DKIM errors lists the usual suspects.
Repeat this for every domain and domain alias on the account. Signing is per domain. The one you forget is the one that fails.
Step 3: Publish a DMARC record that only watches
With SPF and DKIM in place, publish DMARC. Begin with a policy of none, which changes nothing about how your mail is delivered and asks receivers to send you reports:
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"The record goes at the hostname _dmarc. The rua address receives aggregate reports. Send them to a dedicated mailbox, because they arrive daily, as compressed XML, from every participating receiver that handled your mail. The DMARC record generator builds the record, and How to Configure DMARC explains each tag.
A policy of none is not protection. It is a census. Run it first anyway, because you cannot enforce rules on senders you have not counted.
Step 4: Verify with a real message
Send an email from a Rackspace mailbox to an account at a large provider, then view the original message. Paste the headers into the email header analyzer. You want three results:
| Header result | What it means | If it is missing |
|---|---|---|
spf=pass | Rackspace’s server is on your list | Check for two SPF records or a missing include |
dkim=pass header.d=example.com | Signed with your key, under your domain | DKIM not enabled, or the TXT record is wrong |
dmarc=pass | At least one aligned pass | Fix whichever of the two above failed |
Test from webmail and from a desktop client. If someone’s mail program is configured to send through an internet provider’s SMTP server instead of Rackspace’s, their messages skip Rackspace entirely, and so does your authentication.
The senders that are not Rackspace
Here is where the tidy picture gets complicated. Your mailboxes are at Rackspace. Your mail is not all sent from there. The website contact form sends from a web server. The accounting package sends invoices from its own cloud. The office copier scans to email through whatever SMTP relay the installer typed in.
Each of these uses your domain, and none of them is covered by the three records above. Aggregate reports are how you find them. Upload one to the DMARC report analyzer, or point your rua at SpoofKiller’s DMARC monitoring and get a named list of sources with pass and fail counts. Each legitimate one needs its own SPF entry or DKIM key. The illegitimate ones are the reason you are doing this.
Step 5: Move toward enforcement
Leave p=none in place for at least two to four weeks. A full month catches the monthly billing run and the quarterly newsletter. When every legitimate source shows an aligned pass, raise the policy to quarantine, then to reject. The differences between the three are laid out in None vs Quarantine vs Reject, and the full procedure is in How to Reach p=reject.
Do not stop watching once you get there. Records get edited, vendors change their sending infrastructure, and someone will sign up for a new email tool without telling you. The setup is a day’s work. Keeping it true is the long part.

