Quick answer: Email deliverability is about whether your emails reach the inbox rather than the spam folder or nowhere at all. For automated emails, the most important steps are: send through a proper email service rather than your web server, set up SPF, DKIM and DMARC records for your domain, use a real from address on your own domain, keep lists clean and permission-based, separate transactional emails from marketing, and monitor bounces, complaints and your sender reputation with tools such as Gmail Postmaster Tools.
Automation only pays off if the emails arrive. A booking confirmation that lands in spam leads to a confused customer and a phone call. A lead notification that never arrives is a lost enquiry. A follow-up sequence that goes straight to junk does nothing. Many businesses set up automations carefully and then never check whether the emails are actually being delivered. This guide covers the technical setup and good habits that keep automated emails in the inbox.
Why automated emails end up in spam
Email providers such as Gmail, Outlook.com and Yahoo filter messages based on many signals. The main ones are:
- Authentication: can the provider confirm the email really comes from your domain?
- Sender reputation: does the sending server and domain have a history of sending wanted email, or spam?
- Engagement: do recipients open, reply and move messages out of spam, or delete and report them?
- Content: does the email look like typical spam?
- List quality: are you sending to addresses that bounce or spam traps?
Automated emails often fail on the first two, because they are sent from a website or app with little thought about how they leave the server.
Stop sending from your web server
By default, WordPress and many web applications send email using PHP’s mail function through the web server. This is a common cause of problems:
- Shared hosting servers send email for many sites, some of them spammy, so the server’s reputation may be poor.
- Emails are often not authenticated properly for your domain.
- There is no record of what was sent or delivered.
The fix is to send through an SMTP service or transactional email provider. For WordPress, an SMTP plugin can route all site email through a proper service. Form notifications are a frequent casualty, so if you rely on WordPress forms for enquiries, this step matters.
Choosing an email sending service
Transactional email services
These are built for automated, one-to-one emails such as receipts, password resets and notifications:
- SendGrid: popular, with a free tier, good documentation and plugins for many platforms.
- Mailgun: developer-focused, with a straightforward API and detailed logs.
- Amazon SES: very low cost per email, suited to developers comfortable with AWS.
- Mandrill: now an add-on for paid MailChimp accounts rather than a standalone free service, which suits businesses already on MailChimp.
Marketing email platforms
For newsletters and automated marketing sequences, use a marketing platform such as MailChimp or Campaign Monitor. They handle unsubscribes, list management and compliance features that transactional services do not.
Keep transactional and marketing separate
If possible, send transactional emails and marketing emails through different services or at least different subdomains, for example mail.yourdomain.com for marketing. That way, a marketing campaign that draws complaints does not damage delivery of order confirmations.
Authenticate your domain
Authentication tells receiving servers that you have authorised a service to send email on behalf of your domain. Three DNS records matter.
SPF
Sender Policy Framework lists the servers allowed to send email for your domain. It is a TXT record in your DNS. If you use Google Apps for business email and SendGrid for your website, your SPF record must include both. Only have one SPF record per domain, and keep it within the limit on DNS lookups.
DKIM
DomainKeys Identified Mail adds a digital signature to each email, which receiving servers check against a public key published in your DNS. Your sending service provides the DKIM record to add. Set it up for every service that sends on your behalf.
DMARC
DMARC, published as RFC 7489 last year, ties SPF and DKIM together. It tells receiving servers what to do if an email fails authentication (nothing, quarantine to spam, or reject) and where to send reports. Start with a monitoring policy, p=none, and a reporting address. Review the reports to find all your legitimate sending sources, then gradually move to quarantine and eventually reject once everything passes.
DMARC also protects your domain from being used in phishing emails that pretend to come from you.
Use a sensible from address
- Send from an address on your own domain, not a free email address. Providers increasingly reject emails claiming to be from Yahoo or AOL addresses sent through other servers, because those domains publish strict DMARC policies.
- Avoid
noreply@where you can. A real address that accepts replies encourages engagement and lets customers respond. - Use a recognisable from name, such as your business name or a person’s name at the business.
Keep your lists clean
Sending to bad addresses damages your reputation quickly.
- Get permission. Only email people who have asked to hear from you or who have a direct transactional relationship with you.
- Validate addresses at signup. Use double opt-in for marketing lists, or at least check address format on forms.
- Remove hard bounces immediately. Most services do this automatically.
- Remove long-term inactive subscribers from marketing lists, or send a re-engagement email first.
- Never buy lists. Bought lists contain old addresses and spam traps.
Write emails that do not look like spam
Content matters less than authentication and reputation, but it still plays a part:
- Write clear, honest subject lines.
- Avoid all capitals, excessive exclamation marks and spammy phrases.
- Keep a reasonable balance of text and images. An email that is one big image is suspicious.
- Include a plain text version alongside HTML.
- Make links point to your own domain where possible, and avoid link shorteners.
- Include your business address and, for marketing emails, a clear unsubscribe link.
Watch engagement
Mailbox providers pay attention to how recipients react. Automated sequences that keep emailing people who never open them can drag down your reputation. In drip campaigns, stop or slow the sequence for people who do not engage, and make it easy to unsubscribe. An unsubscribe is far better than a spam complaint.
Monitor deliverability
Check regularly rather than assuming all is well:
- Sending service dashboards: watch delivery rate, bounces, spam complaints and blocks.
- Gmail Postmaster Tools: launched last July, it shows your domain and IP reputation with Gmail, spam rates and authentication results, once you send enough volume.
- DMARC reports: show which servers are sending as your domain and whether they pass.
- Blacklist checks: tools such as MXToolbox show whether your sending IP or domain appears on major blacklists.
- Test emails: send automated emails to test accounts at Gmail, Outlook.com and Yahoo, and check where they land.
FAQ
Why do my website form emails go to spam?
Usually because they are sent from the web server without proper authentication. Send through an SMTP service and set up SPF and DKIM.
Do I need DMARC as a small business?
It is worth having, starting with a monitoring policy. It helps deliverability and protects your domain from being spoofed.
Should I use a dedicated IP address?
Only if you send large volumes consistently. For most small businesses, a shared IP from a reputable service is better, because a new dedicated IP has no reputation.
Make sure your automations arrive
Automated emails save time only if they reach people. If you want help setting up email sending, authentication and automations that work reliably, see how we help businesses automate the busywork.
