Eventonomy

How to Keep Eventonomy Emails Out of Spam

Eventonomy sends real, expected email - RSVP confirmations, magic links, order receipts, reminders, and attendee blasts. If those messages land in spam (or never arrive), the cause is almost never the plugin: it is how your WordPress site sends mail. This guide explains why, and how to fix it in about 15 minutes.

Why WordPress Mail Lands in Spam

Out of the box, WordPress sends email through PHP's mail() function on your web server. That means:

  • Your web server is not a mail server. Shared-hosting IPs send mail for thousands of sites, so they carry poor sending reputation - many are already on spam blocklists.
  • Nothing proves the mail is really from you. Without SPF/DKIM authentication, Gmail, Outlook, and Yahoo treat the message as forgeable and file it accordingly. Since 2024, Gmail and Yahoo require authentication for reliable delivery.
  • Failures are silent. mail() reports success as soon as the server accepts the message - if it is dropped two hops later, neither you nor the attendee ever finds out.

Fix 1: Send Through SMTP or a Transactional Service (Recommended)

Install an SMTP plugin and route all WordPress mail - Eventonomy's included - through a real mail service. Any of these work well:

  • WP Mail SMTP - the most popular; connects to Gmail, Outlook, SendGrid, Mailgun, Amazon SES, and generic SMTP.
  • FluentSMTP - free, supports multiple connections and logs every email so you can see exactly what was sent.

For attendee-facing mail at any real volume, prefer a transactional email service (SendGrid, Mailgun, Postmark, Amazon SES, Brevo) over a personal Gmail/Outlook account - mailbox providers rate-limit personal accounts quickly, and a reminder sweep to 300 attendees will hit that ceiling.

Eventonomy needs no configuration for this: it sends through the standard wp_mail() pipeline, so whatever the SMTP plugin is configured to do applies to every Eventonomy email automatically.

Fix 2: Authenticate Your Domain (SPF, DKIM, DMARC)

Add three DNS records for the domain you send from. Your email service's dashboard gives you the exact values; conceptually:

  • SPF - one TXT record listing who may send for your domain, e.g. v=spf1 include:sendgrid.net ~all. Only ONE SPF record per domain - if one exists, merge the include: into it.
  • DKIM - a TXT (or CNAME) record publishing the public key your mail service signs each message with. Copy it from the service's domain-authentication screen.
  • DMARC - one TXT record at _dmarc.yourdomain.com telling receivers what to do when SPF/DKIM fail, e.g. v=DMARC1; p=quarantine; rua=mailto:postmaster@yourdomain.com. Start with p=none to monitor, tighten later.

Verify all three with a free checker such as MXToolbox or by emailing a mail-tester.com address from your site.

Fix 3: Match the From Address to Your Domain

Go to Eventonomy → Settings → Notifications → Email and set:

Setting What to use
From name Your site or organization name - what attendees see in their inbox.
From address An address on the domain you authenticated above (e.g. events@yourdomain.com).

The default From address is your WordPress admin email. If that is a @gmail.com or other third-party address, mailbox providers see mail claiming to be Gmail arriving from your web server - an instant authentication failure. Always use your own domain, and make sure it is the same domain your SPF/DKIM records cover.

How to Test

  1. RSVP confirmation - RSVP to a test event with a real mailbox (Gmail is the strictest free test). The confirmation should land in the inbox, not spam.
  2. Reminders - Eventonomy sends automatic reminders 1 day and 1 hour before an event starts. Create an event starting ~1 hour out, RSVP, and confirm the reminder arrives (the sweep runs hourly).
  3. Attendee blast - send yourself a message through the Email attendees panel (see How to Message Your Attendees); blasts go out in background batches, so allow a few minutes.
  4. Score it - send any of the above to a mail-tester.com address; aim for 9/10 or better. The report names any missing SPF/DKIM/DMARC record.

For developers: on a local site, point SMTP at Mailpit (bundled with Local, or run standalone) and every Eventonomy email - confirmations, reminders, blasts - is captured in its web inbox at http://localhost:8025, no real sending involved.

Good to Know

  • Unsubscribe is built in. Notification emails carry a one-click unsubscribe link and Eventonomy honors suppressions at send time - good deliverability hygiene you get for free. See Unsubscribe & Suppression.
  • Transactional email still sends. Receipts, magic links, and other must-arrive mail are exempt from suppression by design.
  • Pro templates inherit all of this. Custom email templates (Pro) change the body, not the sending path - the same SMTP + authentication setup applies.

Next Steps