Law Firm Emails Going To Spam Folder
Summary
This guide helps you troubleshoot and resolve: Law Firm Emails Going To Spam Folder. Follow the steps below to fix the issue.
Common Causes
Troubleshooting Law Firm Emails Going to Spam
When a law firm relies on website contact forms, automated notifications, and direct email to manage client inquiries and court correspondence, email deliverability is critical. Messages originating from web servers or third-party platforms are frequently flagged as spam or rejected entirely by recipient mail servers when domain authentication records are missing, incorrectly configured, or incomplete. For legal practices, this can result in missed client enquiries, overlooked court communications, and a breakdown in professional correspondence that may have confidentiality and compliance implications.
This article outlines how DNS authentication protocols—specifically SPF, DKIM, and DMARC—work together to verify that email sent from your law firm's domain is legitimate. It explains how to align your website hosting, legal practice management software, and email routing so outgoing messages reach client inboxes securely. If you require assistance configuring these records, Open a Ticket.
Quick Fix Steps
- Identify your domain registrar and DNS hosting provider (for example, GoDaddy, Crazy Domains, or VentraIP).
- Log in to your registrar account and open the DNS management or zone editor for your law firm's domain.
- Verify that an SPF record exists and includes all authorised senders, including your website host, email provider, legal practice management software, and any email marketing tools.
- Check that DKIM is enabled in your email administration console and published as a DNS TXT record.
- Add a DMARC record to instruct receiving mail servers how to handle unauthenticated email and where to send aggregate reports.
- Configure your website contact form to send via authenticated SMTP rather than the web server's default PHP mail function.
- Send a test email from your website contact form to an external address (such as Gmail or Outlook) to confirm delivery.
Understanding SPF, DKIM, and DMARC for Law Firms
These three DNS records work together to prevent email spoofing and improve deliverability. For legal practices handling confidential client information, proper authentication helps ensure that court correspondence and client emails are not intercepted, altered, or misdirected.
- SPF (Sender Policy Framework): A
TXTrecord that lists the mail servers and IP addresses authorised to send email on behalf of your domain. For a law firm, this should include your email provider (Google Workspace or Microsoft 365), your website host, and any integrated platforms such as LEAP, Actionstep, or Clio if they send email on your domain's behalf. - DKIM (DomainKeys Identified Mail): Adds a digital signature to outgoing email headers, allowing receiving servers to verify that the message was not altered in transit. This is particularly important for law firms sending retainer agreements, court filings, or sensitive client updates.
- DMARC (Domain-based Message Authentication, Reporting & Conformance): A
TXTrecord that tells receiving mail servers what to do if SPF or DKIM checks fail, and where to send aggregate reports. DMARC reporting helps your IT team identify unauthorised senders attempting to impersonate your firm's domain.
Checking and Adding an SPF Record
- Log in to your domain registrar control panel.
- For GoDaddy: select Domains, click Manage next to your domain, then choose Manage DNS. For Crazy Domains: log in to Account Manager, select Domains, click Manage, and open DNS Settings.
- Locate the DNS Management or Zone Editor section.
- Look for an existing
TXTrecord with a value beginning withv=spf1. - If no SPF record exists, create a new
TXTrecord with the host set to@. Set the value to include your authorised senders. Example for Google Workspace:v=spf1 include:_spf.google.com ~all. Example for Microsoft 365:v=spf1 include:spf.protection.outlook.com ~all. Adjust based on your email provider and any additional authorised services. - If you use email marketing tools such as Mailchimp or Campaign Monitor, include their SPF mechanisms in the same record rather than creating a separate record. Example:
v=spf1 include:_spf.google.com include:servers.mcsv.net ~all. - Save the record and allow time for DNS propagation.
v=spf1 TXT record. Instead, combine all authorised senders into a single SPF record.Enabling DKIM
- Log in to your business email suite administration console.
- For Google Workspace: go to Admin console > Apps > Google Workspace > Gmail > Authenticate email. Select your domain and click Generate new record. Copy the generated TXT record value.
- For Microsoft 365: go to the Microsoft 365 Defender portal > Email & collaboration > Policies & rules > Threat policies > DKIM. Select your domain and choose Sign messages for this domain with DKIM signatures. Copy the published CNAME or TXT values as directed.
- In your DNS zone editor, create a new
TXTrecord (or CNAME, depending on provider requirements). The host name will typically be something likedefault._domainkey. - Paste the public key value into the record value field and save.
- Return to your email administration console and activate DKIM signing for your domain.
Adding a DMARC Record
- In your DNS management panel, create a new
TXTrecord. - Set the host name to
_dmarc. - Set the record value to a DMARC policy. A common starting point for law firms is:
v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com.au - Replace the email address with one monitored by your organisation or IT support provider.
- Save the record.
p=none tells receiving servers to monitor and report failures without blocking email. Once you confirm SPF and DKIM are working correctly, you can tighten the policy to p=quarantine or p=reject to protect your domain from spoofing attempts.Troubleshooting Common Deliverability Issues
Emails Going to Spam Despite SPF, DKIM, and DMARC Being Present
Authentication records may exist but still fail if they are misconfigured or incomplete. Check the following:
- Confirm your SPF record does not exceed the 10 DNS lookup limit. Too many
includemechanisms can cause SPF validation to fail. - Verify that your DKIM public key matches the private key used by your email provider. A mismatched key will cause DKIM validation to fail.
- Review DMARC aggregate reports sent to your
ruaemail address. These reports show which sources are sending email on your domain's behalf and whether they pass authentication. - Check email headers from messages that landed in spam. Look for
spf=fail,dkim=fail, ordmarc=failresults to identify which check is failing.
Third-Party Email Marketing Tools Missing from SPF
If your law firm uses Mailchimp, Campaign Monitor, or similar platforms to send newsletters or client updates, those services must be included in your SPF record. Emails sent through these platforms using your domain will fail SPF if the sending server is not authorised.
- Obtain the SPF include value from your email marketing provider's documentation.
- Edit your existing SPF
TXTrecord rather than creating a new one. - Add the provider's include mechanism to the record value. Example:
v=spf1 include:_spf.google.com include:servers.mcsv.net ~all. - Save the record and allow time for propagation.
Website Contact Forms Using PHP Mail Instead of SMTP
Many website contact forms default to the web server's PHP mail function. These messages often originate from the web server's IP address, which is not listed in your domain's SPF record, causing them to be marked as spam.
- Install an SMTP plugin on your website (for example, WP Mail SMTP for WordPress).
- Configure the plugin to send via your authorised email provider (Google Workspace or Microsoft 365) using authenticated SMTP credentials.
- Set the From address to an email address hosted on your domain (for example,
inquiries@yourlawfirm.com.au). - Send a test submission through your contact form and verify the message arrives in the recipient's inbox, not the spam folder.
DMARC Report Analysis
DMARC aggregate reports are XML files sent to the email address specified in your rua tag. These reports can be difficult to read manually.
- Ensure a monitored mailbox receives DMARC reports.
- Use a DMARC report analyser service to parse the XML data into readable charts and tables.
- Review the reports for unauthorised senders using your domain. If you identify legitimate services missing from your SPF record, update the record accordingly.
- Once you are confident all legitimate senders are authenticated, consider moving from
p=nonetop=quarantineorp=reject.
Misconfigured Email Routing
If your website is hosted on one server but your email is hosted elsewhere (for example, Microsoft 365 or Google Workspace), ensure your MX records point to the correct email provider. Incorrect MX records can cause automated notifications from your website to be rejected or marked as spam.
External Deliverability Failures
If emails reach some recipients but not others, the receiving organisation may have stricter spoofing prevention policies. Ask the recipient's IT team to check their spam quarantine and confirm whether your domain is passing authentication checks.
Preventing Email Disruption When Altering Web Settings
Before changing web hosting settings, nameservers, or DNS records, document your current configuration. Sudden changes to A records, CNAME records, or nameservers can interrupt both website traffic and email flow. If you are unsure, Open a Ticket and our team can review the changes with you.
Related Articles
Still Having Issues?
💻 Open a Ticket