The From line on an email is a text field. Your property management software writes whatever address you typed into its settings, and nothing verifies you were entitled to use it. The check happens at the far end, and it does not take the From line at its word. It reads your DNS.
That gap is where rent reminders and entry notices go missing.
What the receiving mailbox checks
Since February 1, 2024, Google has required every sender to a personal Gmail account to set up SPF or DKIM authentication on its sending domain. Senders of more than 5,000 messages a day to Gmail accounts need SPF, DKIM and DMARC, with the From domain aligned to either the SPF domain or the DKIM domain. Google's email sender guidelines say unauthenticated messages might be marked as spam or rejected with a 5.7.26 error.
Microsoft draws a similar line. Once a domain sends 5,000 or more messages to Microsoft consumer mail from the same From domain, it expects SPF and DKIM to pass, a DMARC record to exist, and DMARC to validate through one of them. Mail that fails comes back as 550 5.7.515 Access denied.
Both thresholds describe bulk senders, and a landlord with 30 doors is nowhere near 5,000 a day. Read the floor, not the ceiling: SPF or DKIM is the minimum for reaching any Gmail address, and that is most of your tenants.
Your vendor cannot publish these records for you
Microsoft's guidance for mail a service sends on your behalf reads like a checklist. Your domain belongs in the MailFrom address, DKIM should sign with your domain, your SPF record should carry the include value the service gives you, and DMARC should validate against your domain. Every one of those is an edit to your DNS zone, and only whoever controls the domain can make it. So switching on tenant email in a new tool is two steps. You configure the tool, then you authorize it in DNS. Skip the second and the tool works from its own side while its mail fails at Gmail.
Where to look
- SPF is a TXT record at your domain root.
- DMARC is a TXT record at _dmarc in front of your domain.
- DKIM is a TXT record at a selector, then _domainkey, then your domain. Guessing will not find it: the selector is a short string each vendor picks, so ask each one for theirs.
On Windows or macOS, nslookup -type=txt yourdomain.com returns the first two. The DKIM lookup needs the selector, which is why most self-audits stop after SPF.
Two ways a growing portfolio breaks its own SPF
Both are set out in RFC 7208, and both surface around the third or fourth sending vendor.
A domain gets one SPF record. The spec says multiple SPF records are not permitted for the same owner name, and a check that finds more than one returns permerror, a failure for all of them. Each vendor hands you a record, so adding a second one breaks the first.
SPF evaluation also allows a total of 10 DNS-querying terms, and passing that limit returns permerror too. Include values nest, pulling in records you never see, so four vendors can exceed 10 between them. Count the includes before you add another.
The quiet part
None of this reports itself. A message filed in junk produces no bounce, and the tenant who never saw the entry notice will not write to say so. The first symptom is an argument about whether anything was sent.
Those records are also the only thing between your domain and a stranger sending a payment-redirection notice with your address in the From line. Microsoft's example value is v=DMARC1; p=none, which asks for no enforcement at all. Publish that, add a reporting address so the data comes back, read a month of it, then decide how far to tighten.
