Emails in WordPress often feel invisible until something breaks, lands in spam, or comes from an unexpected address. Subscriptions, comments, password resets, and contact forms may look similar to users, but they are not sent by the same system.
Understanding the difference between Jetpack-driven emails and Core WordPress transactional emails clarifies what’s handled for you, what comes from your own domain, and when SMTP or additional configuration actually matters; especially on WordPress.com or when using Jetpack on a self-hosted site.
Jetpack / WordPress.com (Subscriptions)
When you use Jetpack Subscriptions, the emails are sent by Automattic’s servers (WordPress.com), not your own. This is why they come from donotreply@wordpress.com.
Jetpack handles:
- Subscribing: Confirmation emails.
- New Posts: Automatic notifications to your list.
- Comment Subscriptions: “Notify me of follow-up comments” and “Notify me of new posts” checkboxes on the comment form.
Jetpack takes care of the mechanics of subscriptions, but wording and placement play a big role in whether readers actually sign up. I explored that side recently in: Stay in Touch.
The Core WordPress (Transactional Emails)
This is where emails are sent directly from your site. By default, WordPress does not use SMTP; it relies on the wp_mail() function, which triggers your server’s internal mailer (PHP Mail). In this setup, emails are sent from wordpress@yourdomain.com using your hosting provider’s resources.
I covered the custom domain email side in more detail in Custom Email With Your Domain.
SMTP is an optional configuration; usually added via plugins like MailPoet or WP Mail SMTP. It replaces PHP Mail to improve reliability and deliverability.
Core WordPress handles:
- Moderation: “A comment is held for moderation” (sent to Admin/Author).
- Engagement: “New comment on your post” (sent to Author).
- Pings: Trackbacks and Pingbacks.
- Contact Forms: To send you the submission.
- System Alerts: Password resets and new user registrations.
Summary Table
| Feature | Sent Via | Sender Address |
| Blog Subscriptions | Jetpack (Automattic Servers) | donotreply@wordpress.com |
| Comment Following | Jetpack (Automattic Servers) | donotreply@wordpress.com |
| New Post Alerts | Jetpack (Automattic Servers) | donotreply@wordpress.com |
| Admin Moderation | WordPress Core (PHP Mail / SMTP) | wordpress@yourdomain.com |
| Contact Forms | WordPress Core (PHP Mail / SMTP) | wordpress@yourdomain.com |
| Password Resets | WordPress Core (PHP Mail / SMTP) | wordpress@yourdomain.com |
Final Thoughts
WordPress uses two separate email paths when Jetpack is in use. Jetpack handles subscriber notifications through WordPress.com’s infrastructure, while Core WordPress sends transactional emails from your own domain.
If you are self-hosting WordPress, this is why MailPoet or an SMTP plugin is often recommended. Many email providers (Gmail, Outlook,…) limit or flag PHP Mail, which can cause moderation or contact form emails to be missed or end in the spam folder. Routing these transactional emails through a dedicated delivery service improves reliability, professionalism, and inbox delivery.
Leave a Reply