This guide explains how to email the people who have registered on your WordPress site, whether you call them members, subscribers, customers or simply users, and how to make sure those messages actually reach the inbox rather than the spam folder. It draws a clear line between three different things that often get muddled: the automatic emails WordPress already sends on your behalf, the deliberate messages and newsletters you compose yourself, and the point at which you should stop sending through your web server and switch to a proper email service. It is written for Noiz clients running a self-hosted WordPress site and assumes no prior knowledge of how email delivery works.
Last reviewed: 27 July 2026, against WordPress 7.0.2 (latest stable). This guide is written for Noiz hosting and is kept current against WordPress. It complements, and does not replace, the official WordPress documentation linked below.
Official Documentation Reference
- Users screen (WordPress Documentation): how the list of your registered users works, including the columns and the bulk actions that are actually available in WordPress core.
- Roles and Capabilities (WordPress Documentation): the user roles you can target when you want to email only a segment of your users, such as customers or members.
- wp_mail() function reference (WordPress Developer Resources): the single core function that WordPress itself, and every email plugin, uses to send a message; useful for understanding what happens behind the scenes.
- Email sender guidelines (Google): the authentication, unsubscribe and spam-rate rules that now apply to anyone sending email to Gmail addresses, and a good proxy for what every mailbox provider expects.
- POPIA Section 69: Direct marketing by unsolicited electronic communications: the South African law that governs when you may email your users a marketing message.
Prerequisites
- You can log in to your WordPress admin dashboard as an administrator. Installing plugins and changing how the site sends email both require the administrator role.
- A real From address on your own domain, for example
[email protected](replace this with your own address). It should be a mailbox you can actually receive replies and bounce messages at, not an address that only exists in a settings field. - Access to your domain's DNS if you plan to send to more than a handful of people, so that the authentication records described later can be added.
- A clear idea of who you are emailing and why, because that decides which of the approaches below is the right one.
The Emails WordPress Already Sends
Before installing anything, it helps to know that a plain WordPress site already emails your users automatically. These are triggered by events, sent one message at a time, and you never compose them by hand. They include:
- New user registration: when someone registers, WordPress emails them their username and a link to set a password, and notifies the site administrator that a new account exists.
- Password resets: the "lost your password" link sends a reset email to the account holder.
- Comment notifications: WordPress can email you when a comment is posted or is held for moderation.
- Account and admin notices: confirmation when someone changes the site or account email address, and automatic notices about updates or a critical site error.
All of these are transactional emails: they are a direct response to something a specific person did. WordPress generates them through a single internal function, wp_mail(), and by default that function hands each message straight to your web server's own mail system. This matters later, because that default path is also the reason so many WordPress emails end up in spam.
What WordPress does not include is any way to sit down, write a message, and send it to all of your registered users at once. There is no "email your users" screen anywhere in the standard dashboard. That deliberate, one-to-many kind of email is the part you have to add.
Where Your Registered Users Live
Every registered account appears under Users then All Users in the dashboard. The table lists each person's username, name, email address and role, and you can filter it by role, sort it, or search it.
It is tempting to assume that because you can see everyone's email address here, you can select them and send a message. You cannot. If you open the Bulk Actions drop-down at the top of the list, the only choices WordPress core offers are Delete and Change role to. There is no send-email action.
This screen is still useful, though: the Role column is how you decide who to email. A membership or shop plugin usually gives members and customers their own roles, so "email all customers" really means "email everyone with the customer role". Keeping that in mind makes the tools below far more precise than blasting every account on the site.
Sending a Message to Your Users
Because WordPress has no built-in broadcast feature, you choose one of three broad approaches. They are not competitors so much as answers to different needs, and larger sites often use more than one at the same time.
Option 1: An email-to-users plugin (occasional, low volume)
Several free plugins add a simple compose screen to the dashboard and let you send a message to every user, or to a chosen role. Plugins such as Send Users Email, Email Users and Mass Email To Users are examples of this category; naming them is not an endorsement. This is the quickest way to send an occasional announcement to a modest number of people.
Understand the important limitation before you rely on one: by default these plugins still send through your web server's mail system, the same unauthenticated path WordPress uses for its own emails. The plugin controls who receives the message and what it says, but it does nothing on its own to help the message reach the inbox. For a dozen recipients that is usually fine. For hundreds, it is not, which is what the next two options and the deliverability section address.
Because a plugin like this can read every registered user's email address and send email in your domain's name, treat it as a powerful, sensitive tool. Check a plugin's reviews, active-install count, last-updated date and how it handles data before installing it, and keep it updated afterwards. The WordPress Security Checklist explains how to vet and maintain plugins safely.
Option 2: A newsletter or marketing platform (regular campaigns, growing list)
If you plan to send newsletters, product updates or promotions on a regular basis, use a dedicated email marketing service instead. These platforms handle the things a simple plugin does not: reusable templates, audience segmentation, scheduling, open and click tracking, automatic unsubscribe links, bounce handling and consent records. Many connect to WordPress through their own plugin that keeps your users or subscribers in sync. Services such as Mailchimp, Brevo, MailerLite and MailPoet are examples, again offered only as illustrations rather than recommendations.
The crucial difference is where the sending happens. With a marketing platform, your messages go out over the provider's own authenticated mail infrastructure, not your web server, so deliverability and list management are largely taken care of for you. This is the right home for anything that looks like a mailing list.
Option 3: Authenticated SMTP for the emails you already send
Sometimes the real problem is not that you want to broadcast anything, but that the transactional emails WordPress and your plugins already generate, order receipts, membership notices, password resets, are not arriving. The fix here is an SMTP plugin. It does not add a compose feature; instead it reroutes wp_mail() so that every email WordPress sends goes out through an authenticated mail service rather than the raw web-server path. Plugins such as WP Mail SMTP, FluentSMTP and Post SMTP are examples of this category.
An SMTP plugin is often worth installing regardless of which other option you choose, because it also lets you set a proper From name and address for the whole site and makes your existing automatic emails much more reliable.
When to Move Off Your Web Server's Mail
The single most useful thing to understand is why the default path fails as you grow. When WordPress sends through your web server, the message leaves from the server's shared IP address with no proof that you are allowed to send as your domain. Receiving mail systems see an unsigned message from an address they cannot verify and, quite reasonably, treat it with suspicion. The specific weaknesses are:
- No authentication: the message is not signed with your domain's DKIM key, and the sending server is usually not listed in your domain's SPF record, so receivers cannot confirm it is genuine.
- Shared reputation: the server's IP address is shared with other sites, and you do not control how it is regarded by mailbox providers.
- Volume limits: web servers are built to serve pages, not to push out large batches of email. Sending hundreds or thousands of messages can hit limits, back up in a queue, or get the server flagged.
- No list hygiene: bounces, spam complaints and unsubscribes are not tracked, so problems build up invisibly and damage your reputation further.
A simple rule of thumb: if you send a few transactional emails a day, an authenticated SMTP setup (Option 3) is plenty. The moment you are sending a genuine mailing list, whether that is tens, hundreds or thousands of people at once, move that sending to a dedicated email or marketing service (Option 2) that is designed for it. Trying to run a newsletter through your web server's mail is the most common cause of the deliverability problems below.
Deliverability: Getting Into the Inbox
Deliverability is the umbrella term for whether your emails actually arrive. It rests on three DNS records that together prove your messages are legitimate:
- SPF lists which servers are allowed to send email for your domain.
- DKIM adds a cryptographic signature so receivers can confirm a message really came from you and was not altered.
- DMARC ties the two together and tells receivers what to do with mail that fails the checks, while giving you reports on what is being sent in your name.
These are no longer optional. Since the major mailbox providers tightened their rules in 2024, and Microsoft extended similar enforcement in 2025, SPF, DKIM and DMARC, together with a working one-click unsubscribe link and a spam-complaint rate kept well below one in three hundred messages, are effectively required for anyone sending in any volume. The strictest thresholds apply above roughly five thousand messages a day, but the same practices are what keep even a small site out of spam.
Setting up SPF, DKIM and DMARC for your Noiz-hosted domain, and connecting an authenticated mail service, is covered in the email deliverability documentation in the Email section of this knowledgebase. This guide deliberately does not repeat those steps, so that there is one authoritative place to keep them current. Beyond the DNS records, a few habits keep your delivery healthy:
- Always send from a real mailbox on your own domain, so replies and bounce messages reach you and so DMARC alignment works.
- Keep the unsubscribe link working and honour opt-outs promptly; a rising complaint rate is the fastest way to land in spam.
- Grow your sending gradually rather than mailing a large list from a cold start.
- Remove addresses that bounce, and only email people who genuinely expect to hear from you.
Consent and the Law (POPIA)
Being able to email your users is not the same as being allowed to. This is a point worth taking seriously precisely because a plugin makes it so easy to email everyone at once.
Under South Africa's Protection of Personal Information Act (POPIA), section 69, direct marketing by electronic means, which includes email, is only permitted when the recipient has given consent, or is an existing customer whose contact details you collected during a sale, where you are marketing your own similar products or services and you gave them a fair chance to opt out. In practice this means someone registering an account, or buying from you, does not automatically agree to receive your newsletter.
Service and transactional emails, such as password resets, order confirmations and account notices, are not marketing and are unaffected. But promotional messages and newsletters need either consent or the existing-customer basis, every marketing email must offer an easy way to unsubscribe, and you should keep a record of how and when each person opted in. A good marketing platform (Option 2) records consent and manages unsubscribes for you, which is another reason to use one rather than a bare plugin once you are marketing rather than simply notifying. This is general guidance and not legal advice; if you are unsure, read the Act or speak to a professional.
Troubleshooting
- Users say the email never arrived, or found it in spam: the message almost certainly went out through the unauthenticated web-server path. Route your mail through an authenticated service using an SMTP plugin or a marketing platform, and confirm SPF, DKIM and DMARC are in place for your domain. A mail-testing tool that scores a sample message will pinpoint what is missing.
- Small messages send, but large batches do not: you are hitting your web server's sending limits. Move bulk sending to a dedicated email service with its own sending queue rather than pushing the whole list through WordPress.
- The From address shows something like
[email protected]or a server hostname: no proper sender has been set. In your SMTP or marketing plugin, set a From name and a real From address on your own domain, so replies and bounces reach you and so the message passes DMARC alignment. - Password resets and other automatic emails do not arrive: this is the same deliverability problem affecting transactional mail. Fix it with an authenticated SMTP setup. It is not a reason to install a bulk-email plugin, which would not help.
- Bounces and complaints are climbing: your list contains stale or non-consenting addresses. Remove addresses that bounce, honour every unsubscribe, and only email people who opted in. Ignoring this steadily wrecks your inbox placement for everyone else on the list.
If you are on a Noiz managed hosting plan, the support team can help you set up authenticated sending and the SPF, DKIM and DMARC records your domain needs, so your WordPress emails reach the inbox. If you are self-managed and get stuck, open a support ticket and include your domain, what you are trying to send, roughly how many recipients are involved, and what your recipients see happening, so the team can point you to the right approach.
