Email Delivery Problems

Use this guide when an Eventixa email is not received, arrives in spam, uses the wrong sender, shows incorrect content, misses expected dynamic information, or looks different from the configured email design.

Eventixa email problems should be separated into two stages:

Eventixa email generation

and

WordPress email delivery

Eventixa controls the supported email trigger, template, subject, heading, message content, sender configuration, and global email wrapper.

WordPress and the site’s mail environment control the actual delivery of the message.

This distinction is important because a correctly generated Eventixa email can still fail to reach the recipient if WordPress mail, SMTP, DNS authentication, hosting restrictions, or the recipient’s mail provider blocks it.

Before You Begin

Before changing email settings:

1. Identify the exact Eventixa workflow that should send the email.
2. Confirm the related booking, payment, RSVP, attendee, or other Eventixa action actually occurred.
3. Note which recipient should receive the message.
4. Check whether the problem affects one email template or all Eventixa emails.
5. Check the recipient’s Spam, Junk, Promotions, and Quarantine folders.
6. Confirm the recipient email address is correct.
7. Review Eventixa email settings before changing WordPress mail configuration.
8. Use a controlled test booking when possible.

If another WordPress plugin also fails to send email, the problem is more likely related to the site’s mail-delivery environment than Eventixa itself.

Quick Diagnosis

Symptom	First Check
No Eventixa emails arrive	WordPress mail/SMTP delivery
Only one Eventixa email type is missing	Relevant Eventixa email template and trigger
Customer email is missing but admin email works	Customer recipient address and customer template
Admin email is missing but customer email works	Administrator template/recipient configuration
Email goes to spam	Sender identity, SMTP, SPF/DKIM/DMARC
Wrong From name or address	Email Sender Settings
Wrong subject or heading	Email Templates
Placeholder text appears literally	Supported placeholders/template content
Email looks unstyled	Email Styling
Booking exists but no confirmation email	Booking workflow + relevant email template + WordPress mail
Resent ticket/email still does not arrive	Delivery environment and recipient mailbox

Check Eventixa Email Settings

Go to:

Eventixa → Settings → Emails

The current Eventixa email settings are divided into:

• Senders
• Templates
• Styling

These correspond to:

• Email Sender Settings
• Email Templates
• Email Styling

The Email Sender Settings section controls sender details and global email behavior.

The Email Templates section manages booking email triggers, subjects, headings, and message templates.

The Email Styling section controls the global wrapper used when supported booking and ticket emails are rendered.

Check Email Sender Settings

Open:

Eventixa → Settings → Emails → Senders

Review the sender information used by Eventixa.

Use a recognizable sender identity associated with the website or event organization.

If the sender address is rejected or emails disappear, compare the configured sender with the address allowed by your SMTP or transactional email provider.

Some mail providers require the From address to use a verified domain or mailbox.

Wrong Sender Name or Email

If an Eventixa email arrives from the wrong sender:

1. Open Eventixa → Settings → Emails → Senders.
2. Review the sender details.
3. Save the settings.
4. Trigger a new test email.
5. Inspect the newly received message.

Previously sent emails will not change after the sender setting is updated.

Check Email Templates

Open:

Eventixa → Settings → Emails → Templates

Eventixa email templates can control:

• Email trigger
• Subject
• Heading
• Message content

If only one type of Eventixa email is not being sent or contains incorrect content, start with the corresponding template rather than changing the site’s entire mail configuration.

Template Is Disabled or Not Triggered

If a specific email does not arrive:

1. Confirm the relevant Eventixa workflow occurred.
2. Open the related email template.
3. Confirm its supported trigger is active.
4. Review the recipient context.
5. Save the template.
6. Repeat the workflow with a new test.

Do not expect a template to send merely because it exists. The corresponding Eventixa action must occur.

Check the Underlying Eventixa Workflow

An email is usually a result of another Eventixa action.

For example, a booking-related email depends on the booking workflow reaching the appropriate state.

If the booking itself failed, remained pending unexpectedly, or did not reach the state expected by the email trigger, the email may not be generated.

Before troubleshooting delivery, verify the related Eventixa record under:

Eventixa → Bookings

and, where relevant:

Eventixa → Attendees

Booking Created but Confirmation Email Is Missing

If the booking exists but the expected confirmation email did not arrive:

1. Open the booking.
2. Confirm the booking reached the expected state.
3. Verify the purchaser email address.
4. Open Eventixa → Settings → Emails → Templates.
5. Review the relevant booking email template.
6. Confirm the template is active where applicable.
7. Trigger a new controlled booking.
8. Check WordPress/SMTP mail logs if available.
9. Check the recipient’s spam/junk folders.

If WordPress reports that the email was sent but it never reaches the inbox, investigate the mail-delivery layer.

Payment Email Is Missing

Payment-related communication depends on the payment workflow reaching the relevant state.

If a paid booking remains pending or the payment did not complete, the expected payment confirmation email may not be generated.

Check:

• Booking status
• Payment status
• Payment provider result
• Relevant email template

If payment itself is incorrect, use the Payment Problems guide before changing email settings.

Customer Email vs Administrator Email

Customer and administrator emails serve different recipients.

A customer-facing email can be generated correctly while an administrator email fails, or vice versa.

When only one side is missing, compare:

• Relevant template
• Recipient address
• Trigger
• Booking/payment state

Do not assume that successful delivery to one recipient proves every Eventixa email template is configured correctly.

Recipient Address Is Wrong

Verify the actual email address stored in the relevant Eventixa record.

Depending on the workflow, the recipient may come from:

• Purchaser information
• Attendee information
• Administrator configuration
• Booking-related data

If the email address was entered incorrectly during checkout, changing the email template will not fix the recipient record.

Logged-In User Email

When a logged-in visitor completes checkout, Eventixa can use the authenticated WordPress account email where applicable.

If the email is being sent to an unexpected address, confirm the WordPress user’s account email and the purchaser information stored with the booking.

Attendee Email vs Purchaser Email

The purchaser and attendee are not always the same person.

For a multi-ticket booking:

1 purchaser can register multiple attendees.

When troubleshooting recipient expectations, confirm whether the email workflow targets:

• Purchaser
• Attendee
• Administrator

Do not assume every email is sent to every attendee.

Check Subject and Heading

If an email arrives but the subject or heading is wrong:

1. Open Eventixa → Settings → Emails → Templates.
2. Open the relevant template.
3. Review the Subject.
4. Review the Heading.
5. Save the template.
6. Trigger a new email.

The inbox subject and the heading shown inside the rendered email are separate values.

Check Message Content

If an email arrives with outdated or incorrect wording, edit the relevant template under:

Eventixa → Settings → Emails → Templates

Update the supported message content and trigger a new test email.

Previously delivered emails are not updated retroactively.

Placeholder Appears as Raw Text

Eventixa templates can use supported placeholders to insert dynamic information.

If a placeholder appears literally in the email instead of being replaced:

1. Confirm the placeholder is supported by Eventixa.
2. Check spelling and formatting.
3. Confirm the required booking/event/attendee data exists.
4. Test the relevant template again.

Use the dedicated Email Placeholders documentation for the supported placeholder reference.

Do not invent or assume unsupported placeholder names.

Dynamic Information Is Missing

If the email sends but a dynamic value is empty, confirm that the underlying Eventixa record contains the corresponding information.

For example, missing attendee information can occur when attendee collection was not enabled or completed for the ticket.

The template cannot insert data that does not exist in the relevant booking, attendee, ticket, or event record.

Check Email Styling

Open:

Eventixa → Settings → Emails → Styling

The Email Styling section controls the global wrapper used by Eventixa email templates.

These settings are applied when supported booking and ticket emails are rendered.

If the email content is correct but the design is wrong, review Styling rather than editing each template individually.

Email Looks Unstyled

If an Eventixa email arrives without the expected appearance:

1. Open Eventixa → Settings → Emails → Styling.
2. Confirm the styling settings are saved.
3. Trigger a new test email.
4. Test with more than one supported Eventixa email type.

If the new emails still appear incorrectly, check whether the receiving email client strips or modifies some HTML/CSS.

Email clients do not always render identical HTML in the same way.

Email Looks Different in Gmail, Outlook, or Mobile

Some visual differences between email clients are normal.

Email clients can apply their own HTML/CSS restrictions.

When testing Eventixa email styling, review the message in:

• Desktop email client
• Webmail
• Mobile email client

Focus on readability and correct content rather than expecting pixel-identical rendering across all clients.

Eventixa Email Generation vs WordPress Delivery

A useful diagnostic split is:

Eventixa creates the email → WordPress sends the email → Mail server accepts/rejects it → Recipient mail provider delivers/filters it

Problems after Eventixa hands the message to WordPress are not normally solved by changing Eventixa templates.

WordPress Mail Delivery

WordPress commonly sends mail through its configured mail environment.

Depending on the site, this can involve:

• Default PHP mail behavior
• SMTP plugin
• Transactional email service
• Hosting mail server
• External mail API

Eventixa does not replace this transport layer.

If no WordPress emails are delivered from any plugin, configure or repair the site’s mail system.

SMTP

Using authenticated SMTP or a transactional email service can improve reliability compared with an unconfigured default mail environment.

If SMTP is already configured, verify:

• SMTP host/service
• Authentication
• From address
• Port/security settings
• Provider connection
• Send logs
• Delivery errors

Do not place SMTP passwords, API keys, or secrets in public screenshots or support messages.

Email Sent in WordPress but Not Received

If a mail log indicates that WordPress successfully passed the message to the mail service but the recipient does not receive it, check:

• Spam/Junk folder
• Mail provider suppression
• Recipient mailbox rules
• Domain authentication
• Sender reputation
• Bounce logs
• Transactional email provider logs

A successful WordPress send attempt does not guarantee inbox delivery.

Spam and Junk Folder

If Eventixa emails consistently arrive in spam, review the site’s sender identity and mail authentication.

Important domain-level email authentication can include:

• SPF
• DKIM
• DMARC

The exact configuration depends on your domain and email provider.

Eventixa itself does not configure these DNS records.

Sender Domain Does Not Match

Some SMTP/transactional providers reject or rewrite mail when the Eventixa From address does not match an authenticated sender or verified domain.

Use a sender address permitted by your mail provider.

For example, if the provider verifies example.com, a sender using an unrelated domain can fail provider validation.

Hosting Mail Restrictions

Some hosts limit or block PHP mail, external SMTP ports, or high-volume sending.

If Eventixa email works on staging or another server but not on production, compare hosting mail restrictions.

Check the hosting control panel or provider logs where available.

Email Delivery Works for Other Plugins but Not Eventixa

If other WordPress emails arrive successfully but Eventixa emails do not:

1. Confirm the Eventixa workflow actually occurred.
2. Review the relevant Eventixa template.
3. Confirm the recipient address.
4. Confirm the template trigger.
5. Trigger a new Eventixa test.
6. Review mail logs for the Eventixa message.

This suggests the problem may be before the WordPress mail transport stage.

Eventixa Emails Work but Bulk Emails Do Not

Automated Eventixa email templates and Bulk Emails are separate workflows.

If booking emails work but Bulk Emails do not, review the Bulk Emails workflow, selected audience, and sending behavior rather than changing the automated booking template.

Use the dedicated Bulk Emails documentation.

MailPoet or Mailchimp Does Not Receive Contacts

MailPoet and Mailchimp synchronization are integrations, not the same as Eventixa’s native transactional email delivery.

If contacts are not being added to MailPoet or Mailchimp, use the corresponding integration documentation.

Do not troubleshoot marketing-list synchronization as a WordPress email-delivery failure.

Resent Ticket or Booking Email Still Does Not Arrive

If the resend action succeeds in Eventixa but the recipient still gets nothing:

1. Verify the recipient address.
2. Check WordPress/SMTP logs.
3. Check spam/junk.
4. Check mail provider suppression/bounce logs.
5. Test sending to another mailbox/domain.
6. Confirm the sender domain is authenticated.

Repeatedly resending the same message will not solve an underlying mail-delivery problem.

Test with a Different Recipient

A single mailbox can have local filtering rules.

When troubleshooting, send the same workflow to a controlled test address on another provider.

For example, compare delivery to two different mailbox providers.

If one receives the message and the other does not, the Eventixa generation step is likely working and the difference is in downstream filtering/delivery.

Email Delays

Some email providers queue or delay messages.

If an Eventixa action just occurred, check provider/mail logs before assuming the message was never generated.

Large queues, rate limits, or transactional service throttling can delay delivery.

Rate Limits

Bulk or high-volume event activity can encounter provider rate limits.

If emails deliver normally at low volume but fail or delay during a large registration spike, review the mail provider’s sending limits and logs.

This is a transport concern rather than an Eventixa template problem.

Email Works on Staging but Not Production

Compare:

• Sender address
• SMTP configuration
• Domain authentication
• Hosting environment
• Mail provider account
• Security plugins
• DNS
• WordPress configuration

A staging site can use a different mail transport even when Eventixa settings look identical.

Security Plugin or Firewall Interference

Security plugins can sometimes interfere with external mail APIs or SMTP connections.

If mail stops after a security configuration change:

1. Review blocked requests/logs.
2. Use a controlled staging test.
3. Temporarily adjust the specific rule.
4. Retest.
5. Re-enable protection with a narrow exception if needed.

Do not disable security permanently as a general workaround.

Example: Booking Confirmation Not Received

Suppose a customer completes checkout successfully and the booking exists, but no confirmation email arrives.

Check:

1. Open Eventixa → Bookings.
2. Confirm the booking state.
3. Verify the purchaser email.
4. Open Eventixa → Settings → Emails → Templates.
5. Review the relevant booking template.
6. Trigger a new controlled booking.
7. Check WordPress/SMTP logs.
8. Check spam/junk.
9. If mail was sent but not delivered, review the mail provider.

This separates Eventixa generation from downstream email delivery.

Example: Every Eventixa Email Goes to Spam

If Eventixa emails are consistently generated but delivered to spam:

1. Confirm the sender domain.
2. Verify SMTP/transactional email authentication.
3. Review SPF.
4. Review DKIM.
5. Review DMARC.
6. Check mail-provider reputation/bounce logs.
7. Retest to multiple mailbox providers.

Changing the Eventixa email body alone is unlikely to fix a domain-authentication problem.

Recommended Diagnostic Workflow

When an Eventixa email is missing:

1. Confirm the underlying Eventixa action occurred.
2. Identify the expected recipient.
3. Verify the recipient email address.
4. Open Eventixa → Settings → Emails → Senders.
5. Review sender configuration.
6. Open Eventixa → Settings → Emails → Templates.
7. Review the relevant template and trigger.
8. Confirm dynamic data exists.
9. Trigger a new test.
10. Check WordPress/SMTP logs.
11. Check spam/junk.
12. Check mail provider logs/bounces.
13. Verify SPF/DKIM/DMARC when deliverability is poor.
14. Test another recipient/domain.
15. If the issue affects all WordPress mail, troubleshoot the site’s mail transport rather than Eventixa templates.

Important Notes

• Eventixa email settings are located under Eventixa → Settings → Emails.
• Email settings are divided into Senders, Templates, and Styling.
• Sender settings control sender details and global email behavior.
• Email Templates manage triggers, subjects, headings, and message templates.
• Email Styling controls the shared wrapper used when supported Eventixa emails are rendered.
• Eventixa email generation and WordPress email delivery are separate stages.
• A valid Eventixa template does not guarantee inbox delivery.
• Booking/payment state can determine whether an email trigger occurs.
• Purchaser and attendee email addresses can represent different people.
• MailPoet/Mailchimp synchronization is separate from Eventixa transactional email delivery.
• SPF, DKIM, DMARC, SMTP, and sender reputation are outside Eventixa’s template configuration.
• Never expose customer emails, SMTP passwords, API keys, provider credentials, or other confidential information in screenshots or support requests.

Troubleshooting

No Eventixa Emails Are Received

Check:

• WordPress mail/SMTP configuration
• Eventixa sender settings
• Spam/junk
• Mail provider logs
• Domain authentication

If all WordPress mail is failing, fix the site mail environment first.

Only One Email Type Is Missing

Check the relevant template and trigger under:

Eventixa → Settings → Emails → Templates

Also confirm the corresponding Eventixa workflow reached the correct state.

Customer Email Is Missing but Admin Email Arrives

Check the customer’s stored recipient email and the relevant customer template.

Admin Email Is Missing but Customer Email Arrives

Review the administrator email template/recipient configuration.

Wrong Sender Is Used

Review:

Eventixa → Settings → Emails → Senders

Then trigger a new test email.

Email Goes to Spam

Review:

• SMTP
• Sender domain
• SPF
• DKIM
• DMARC
• Mail provider reputation

Placeholder Is Not Replaced

Confirm the placeholder is supported and spelled correctly, and confirm the related Eventixa data exists.

Email Styling Is Missing

Review:

Eventixa → Settings → Emails → Styling

Then trigger a new email.

Booking Exists but Confirmation Email Does Not

Confirm the booking state, recipient email, relevant template, and WordPress mail logs.

Resent Email Still Does Not Arrive

Check the downstream mail-delivery system rather than repeatedly resending.

Related Documentation

• Troubleshooting Overview
• Email Notifications Overview
• Customer Emails
• Email Templates
• Email Placeholders
• Email Settings
• Bulk Emails

Frequently Asked Questions

Why did Eventixa create the booking but no email arrive?

Booking creation and email delivery are separate stages. Check the relevant Eventixa template first, then WordPress/SMTP delivery and the recipient mailbox.

Does Eventixa configure SMTP?

No. Eventixa controls its supported email content and sender settings, while actual transport depends on the WordPress mail environment or configured SMTP/transactional email service.

Why does the email go to spam?

Spam placement is usually related to sender authentication, reputation, content filtering, or the receiving mail provider. Review SMTP plus SPF, DKIM, and DMARC.

Why does a placeholder appear as text instead of showing booking data?

The placeholder may be unsupported, incorrectly entered, or the required Eventixa data may not exist for that email context.

Why do emails look different in different mail apps?

Email clients apply different HTML/CSS rules. Small rendering differences between Gmail, Outlook, mobile clients, and other mail apps are normal.

---