Understanding Postmark and Email Sending at BionicWP

BionicWP provides Postmark as a premium email delivery service to improve the reliability and deliverability of outgoing emails, such as form notifications and transactional messages. However, it’s important to understand what Postmark does, what it doesn’t do, and the options available to you for managing email on your WordPress site.

Even without Postmark, our servers are fully capable of sending emails using our built-in SMTP system. Postmark simply adds an extra layer of deliverability and logging for easier troubleshooting.

Postmark is an optional email relay service that integrates with your WordPress site through DNS records and an installed plugin.

• DKIM Authentication
  Postmark relies primarily on DKIM for authentication. When setting up Postmark, you’ll need to add the TXT and CNAME records provided by Postmark to your domain’s DNS. Once added and verified, these records confirm that your domain is authorized to send emails through Postmark.

• Simplified Troubleshooting
  Postmark provides easy-to-read logs of every email sent, making it much simpler to track and verify delivery issues compared to parsing raw server logs.

• Improved Deliverability
  Postmark is optimized to reduce the likelihood of emails being flagged as spam or rejected by mail providers like Outlook, Yahoo, and Gmail.

If Postmark is not installed or set up:

• Emails will still send through our default server-side SMTP.

• Our built-in SMTP automatically authenticates the domain as soon as it’s added to our platform, providing a secure sending path.

In other words, Postmark is not required for emails to work. It simply adds higher deliverability and better reporting.

It’s important to set realistic expectations for Postmark:

• Postmark does not fix incorrect site configuration.
  If form notifications are not set up properly or the “From” domain does not match the authenticated domain, deliverability issues can still occur.

• Postmark cannot override strict spam filters at the recipient’s end.
  Providers like Outlook, Yahoo, and Gmail have strict rules. Even with Postmark, emails can be blocked or filtered if authentication policies like DMARC are not aligned.

• DKIM
  Required and handled automatically by Postmark once DNS records are added. Our team verifies this during setup.

• SPF
  While no longer strictly required for Postmark, we recommend keeping SPF records in place. Some external services still use SPF for filtering or reporting.

• DMARC
  Not required to send emails but strongly recommended to reduce filtering and improve alignment with modern email policies.

Our team will verify DKIM alignment during setup and confirm that form notifications are configured to send from the live site domain.

Every client is free to set up and use their own SMTP solution instead of Postmark. Some common options include services like Mailgun, SendGrid, or Amazon SES.

We’re happy to assist with the initial setup or transition to another provider. However, ongoing support for third-party SMTP services will remain the responsibility of the client.

BionicWP offers three flexible approaches for email delivery:

1. Built-in SMTP (Default)
   This requires no setup. Emails automatically send as soon as your domain is added to our platform. It provides a good level of deliverability and security by default.

2. Postmark
   This is our recommended enhancement for clients who want the highest deliverability and easy access to email logs. It requires adding the provided DNS TXT and CNAME records and installing the Postmark plugin.

3. Client-Provided SMTP
   If you prefer to use your own SMTP provider, you can configure it directly on your site. While we can assist with the initial switch, ongoing management and troubleshooting will be handled by your team.

Pro Tip:
When troubleshooting email delivery issues, always start by verifying DNS records for DKIM, SPF, and DMARC. Confirm that the “From” address matches the authenticated domain and check Postmark or WordPress logs. This process will help identify whether the issue is with sending, authentication, or recipient-side filtering.