Nesta página: [ocultar]
WordPress nunca enviou um email em sua vida. Ele entrega sua mensagem ao e-mail do PHP() função, recebe de volta um verdadeiro ou um falso, e trata isso como um relatório de entrega. Nothing in that exchange checks whether the message left the server. Nothing checks whether the receiving domain accepted it, or whether it dropped into a junk folder. That gap is why your contact form shows “Message sent” while your inbox stays empty. Most guides on this topic stop at “install an SMTP plugin”. This one also covers the two 2026 deadlines that will break setups working fine today. And it covers the mailer plugin flaw that exposed stored API keys, which attackers were still hunting ten weeks after the patch shipped.
Última revisão: agosto 2026. Versões de plug-ins, host sending limits, mailer pricing and authentication deadlines verified against primary sources.
Resposta rápida: Stop letting WordPress use PHP mail() and route it through an authenticated mailer instead. Install FluentSMTP (livre, sem nível pago) or WP Mail SMTP, then connect it to a sending service over an API rather than an SMTP port. Publish SPF, DKIM and DMARC records for your sending domain. Debaixo 300 e-mails por dia, Brevo’s free tier covers it at sem custo. Antes de qualquer coisa, trigger a password reset from your login page: if that fails too, the problem is your server, not your form.
Two Tests That Split the Problem in Half
Nine causes is a lot to work through blind. These two tests take about four minutes and tell you which half of the list to read.
- Teste 1. Trigger a password reset. Go to your login page, clique “Perdeu sua senha?”, and enter the address of an admin account. This path calls core’s wp_mail() with no form plugin, no theme code and no queue in between. If the reset email arrives, WordPress can send and your problem is further down the stack. Se isso não acontecer, the failure is at the server or transport layer.
- Teste 2. Send a test email. Install FluentSMTP or WP Mail SMTP and use its email test tab. Send it to an address on a different domain and provider than the site. Isso importa mais do que parece. Mail sent to an address on the same domain often never leaves the server, so it arrives even when outbound delivery is completely broken.
Now read the result:
- Teste 1 throws a visible error, or the plugin test reports a connection failure: go to causes 1, 2, 4 e 5.
- Both tests report success but nothing arrives, or everything lands in spam: go to cause 3.
- The test email arrives but form or WooCommerce notifications don’t: go to cause 6.
- It worked last month and stopped without anyone touching the site: go to causes 5, 8 e 9.
- Some emails arrive and others never do, with no pattern by recipient: go to cause 7.
Check the spam folder before declaring a test failed. An email that reached the junk folder is an authentication problem, which has a different fix from an email that never left the building.
Where This Guide’s Facts Come From
Every limit, price and date below was read from a primary source in August 2026. Nothing was carried over from an older version of this page. Host sending caps come from the hosts’ own published policies: SiteGround’s acceptable-use article, Hostinger’s cPanel email limits page, and Kinsta’s transactional email documentation. Those three publish exact numbers. Most hosts stay vague, which is why these three get named and others don’t. Plugin figures (instalações ativas, current version, last-updated date, tested-up-to version) were read from the WordPress.org plugin directory on 27 agosto 2026. Authentication deadlines come from Microsoft Learn and Google’s own sender guidelines. Both have shifted at least once, so they’re worth re-reading rather than quoting from memory.
We excluded three things on purpose. Out went fixes that only work inside one host’s control panel, and plugins whose last update predates 2026. So did any mailer whose free tier we couldn’t confirm on a current pricing page. Dois limites honestos. We did not run deliverability tests, so nothing here claims measured inbox placement. And Brevo and Resend both block automated reads of their pricing pages. Those two figures are cross-checked between independent sources rather than quoted from the vendor. Amazon SES, Arma postal, Postmark and WP Mail SMTP figures came straight off the vendor pages.
Cause 1: WordPress Hands Your Mail to PHP and Stops Watching
O WordPress advanced administration handbook is blunt about what wp_mail() na verdade é. It calls the function “a wrapper for a language API library that handles the submission of a message to an MTA”. The library is PHPMailer, bundled with core. Unless something overrides it, PHPMailer calls PHP’s mail() função, which needs a sendmail-compatible binary on the server acting as the mail transfer agent. Miss that binary, or leave it unconfigured, and the handbook’s verdict is direct: “the outgoing mail won’t be sent.”
Here’s the part that wastes the most support time. PHP’s mail() returns true when the message is accepted for local queuing, not when it is delivered. A true means “the handoff worked”. It says nothing about whether a receiving server accepted the message an hour later, or bounced it, or filed it as spam. WordPress has no visibility past the handoff, so it reports success and moves on.
The fix is to replace the transport. Helpfully, wp_mail() is a pluggable function that exposes hooks (pre_wp_mail, phpmailer_init, wp_mail_failed) which every SMTP plugin uses to redirect mail through an authenticated connection. SMTP is Simple Mail Transfer Protocol, the rules servers follow when handing messages to each other. That single change resolves the largest share of these tickets. It swaps a fire-and-forget local handoff for a service that authenticates, retries and reports back.
One 2026-specific note if you have custom mail code. WordPress 7.0.1, lançado 9 Julho 2026, shipped fixes across 31 bugs including the mail component, and core moved to PHPMailer 7.0.0. That version is functionally identical to 6.11.1. The major version bump exists purely to flag a backward-compatibility break for child classes, where lang(), setLanguage() and $language became static. It only affects code that extends PHPMailer, so a normal site running a mailer plugin is unaffected. A developer who wrote a custom PHPMailer subclass three years ago should check it.
Cause 2: Your Host Caps Outbound Mail Lower Than You Think
400 e-mails por hora. That’s the ceiling on SiteGround’s StartUp, GrowBig, Ecommerce and Coderick plans, and even GoGeek and Cloud stop at 800 por hora. SiteGround also counts each recipient separately, so one message to 80 people costs you 80 against the quota, nenhum.
Hostinger publishes its cPanel numbers too: 2,400 messages per day and 200 per hour on cPanel Silver and Gold. There’s a warning attached that most people miss. Those limits “apply to the total number of messages sent via SMTP and PHP from all email accounts on your hosting plan”. Your marketing newsletter and your WooCommerce receipts draw from the same bucket.
Managed WordPress hosts are stricter still. Kinsta relays transactional mail through MailChannels and caps it at 150 emails per day on its entry plans (35k, 65k and WP 2). The middle tiers get 1,000 por dia, and the top tiers get 3,000. Those caps apply per plan across every site on it, not per site. Kinsta monitors outgoing volume. In the case of a serious policy violation, diz “email sending functionality may be temporarily disabled until the issue is resolved”.
Put those side by side and the gap is stark. Kinsta 150 a day on an entry plan is one sixteenth of Hostinger’s 2,400 daily cPanel allowance. A modest store shipping 40 pedidos por dia, with a customer receipt and an admin copy on each, is already at 80 mensagens. That’s before you count password resets, stock alerts or review requests. It doesn’t take much growth to hit a wall you didn’t know existed.
Ports are the other half of this cause. Porta 25 is blocked outbound by default at AWS, Nuvem do Google, Azure, DigitalOcean, Linode, Vultr and most shared hosts. An open port 25 on a compromised server turns it into a spam relay overnight. Porta 587 with STARTTLS and port 465 with implicit TLS are the usual survivors. The reliable move is to skip SMTP ports altogether and use a mailer’s HTTPS API on port 443. No host blocks it, because it’s the same port your site already serves on. If you’re weighing up a dedicated relay against what your host bundles, our comparison of SMTP hosting services and their sending limits covers both camps.
Cause 3: The From Address Doesn’t Belong to You
Picture a contact form set to send from the visitor’s own address, so you can hit reply without retyping anything. Sensible-looking, and it quietly breaks delivery. Gmail receives a message claiming to come from gmail.com, arriving from a server in your host’s IP range. Nothing authorises it to speak for gmail.com. That is the textbook signature of spoofing, and it gets binned or junked.
Three acronyms carry this section, so here’s the short version. SPF lists which servers may send for your domain. DKIM signs each message so tampering shows. DMARC tells receivers what to do when the first two disagree.
do Google sender guidelines have applied to everyone since 1 fevereiro 2024, not just to bulk senders. You need SPF or DKIM on the sending domain, valid forward and reverse DNS, and TLS for transmission. Your spam rate in Postmaster Tools has to stay below 0.3%. Cross 5,000 messages a day to Gmail accounts and it tightens to SPF e DKIM e DMARC, plus one-click unsubscribe on marketing mail. Yahoo aligned with the same rules in February 2024, and Microsoft began enforcing its equivalent for high-volume senders from May 2025. The WordPress handbook now describes DMARC as “becoming almost mandatory”, which is unusually strong language for official documentation.
Three fixes, in order of impact. Primeiro, set the From address to something on your own domain and put the visitor’s address in Reply-To. You keep the one-click reply and stop failing alignment. Segundo, publish an SPF record that authorises whichever service actually sends your mail. Watch the ten-DNS-lookup limit in the SPF spec: an eleventh lookup fails the whole record, not just the last entry. Terceiro, enable DKIM signing at your mailer and add its public key to DNS. Then add a DMARC record starting at p=none, so you get aggregate reports before enforcing anything.
If your mailboxes and your website live on the same shared plan, splitting them is often the cleaner path. A dedicated provider handles SPF and DKIM setup for you. Nosso resumo de business email hosting providers covers what that costs per mailbox.
Cause 4: Gmail Rejects the Password You Just Typed
Start with the dead end, because it saves an hour. Your normal Gmail password will not work, and no amount of retyping changes that. Google removed Less Secure App access from personal Gmail accounts in May 2022 and switched it off for Google Workspace on 30 setembro 2024. Every tutorial that tells you to enter your email address and password into an SMTP form was written before those dates.
Two paths remain. Turn on 2-Step Verification and generate a 16-character App Password, which you paste in place of your real password, one per application. Or use your plugin’s dedicated Gmail or Google Workspace mailer, which runs OAuth and never touches a password at all. OAuth is the better option, because revoking one app’s access doesn’t disturb anything else. It takes longer to set up, so App Passwords remain the pragmatic choice on a single site.
Then there’s the quota nobody reads until it bites. Gmail counts recipients, not messages, adding up To, Cc and Bcc: 500 recipients per day on a personal account and 2,000 on Google Workspace. Sending over SMTP with those credentials draws from the same allowance as the web interface. Google Workspace’s SMTP relay service is a separate product with a higher ceiling, aproximadamente 130 times the number of users in the account per day. New accounts are throttled to 100 recipients a day for the first month. That last detail explains a specific and maddening scenario. A brand-new Workspace tenant looks broken on day one, then fixes itself weeks later without anyone changing a setting.
Compare that 2,000-a-day Workspace figure with Brevo’s free tier at 300 a day and Workspace looks generous, until you remember the counting method. One order confirmation to a customer with two staff addresses in Bcc costs you three, nenhum. A store sending 200 receipts a day with two internal copies each is at 600 recipients. The free Gmail account it started on gave up at 500.
Cause 5: Microsoft 365 Basic Auth Stops Working at the End of December 2026
If your site authenticates to a Microsoft 365 mailbox with a username and password, it stops working at the end of December 2026. Microsoft published an updated deprecation timeline on 27 janeiro 2026. At the end of December 2026, Microsoft disables SMTP AUTH basic authentication by default for existing Exchange Online tenants. Administrators can still re-enable it, but tenants created after December 2026 won’t have the option at all. Microsoft has said the final removal date will be announced in the second half of 2027.
This is the last protocol standing. Microsoft Learn states flatly that “Basic authentication is now disabled in all tenants”. That covers Exchange ActiveSync, POP, IMAP, Remote PowerShell, Exchange Web Services, the Offline Address Book, Autodiscover and Outlook for Windows and Mac. SMTP AUTH survived because so much machinery depends on it, and the original 1 marcha 2026 date slipped to give organisations room. It has not been cancelled.
One detail makes this harder than the Gmail situation. Microsoft Learn notes that “the deprecation of basic authentication also prevents the use of app passwords with apps that don’t support two-step verification”. Google left a fallback open in the form of App Passwords. Microsoft is not leaving one. OAuth, or a different sending path entirely. Those are the only two answers.
So pick one now rather than in December. Use your SMTP plugin’s Microsoft 365 or Outlook.com mailer if the mail must originate from that mailbox and appear in its Sent Items. It authenticates over OAuth through a registered app in your tenant. Otherwise move transactional mail off the mailbox entirely and onto a dedicated relay, leaving Microsoft 365 to handle mail written by humans. The second option is less work, survives every future authentication change Microsoft makes, and gives you delivery logs a mailbox will never provide.
Cause 6: WordPress Sent It. Your Form Plugin Never Asked.
Did the form actually call wp_mail()? Um verde “obrigado, your message has been sent” tells you nothing about it. That confirmation means the submission was processed and, usualmente, that the entry was saved. Delivery is a separate event the visitor’s browser never learns about.
Formulário de Contato 7 is the usual suspect, and not because the plugin is faulty. Its Mail tab has a From field that many people set to the submitter’s address, which trips exactly the alignment failure described in cause 3. Set From to an address on your own domain, move the submitter into Reply-To, and check that the To field points somewhere a human reads. Then look at whether a second mail template is enabled and misconfigured, because a broken autoresponder can fail the whole send.
WooCommerce hides its own trap. Each notification type under WooCommerce, Definições, Emails has its own enable toggle and its own recipient list. o “New order” recipient does not follow the site’s admin email. Change the admin address in WordPress general settings and the Woo recipient keeps pointing at the old one. Order confirmations to customers then work perfectly while you receive nothing, which reads like a total failure but is one stale field.
Is the store the reason email reliability matters to you? Nosso guia para WordPress hosting for ecommerce covers the sending headroom a growing store needs.
Two more worth ruling out. Conditional logic on a form notification can suppress the email for exactly the submissions you care about. And most managed hosts disable outbound mail on staging environments by design. A form tested on staging can look broken when it’s working as intended.
Cause 7: Loopbacks Fail and Queued Mail Never Leaves
Not all mail goes out the moment you trigger it. Plenty gets queued and sent later, e “mais tarde” in WordPress means WP-Cron. That scheduler isn’t a real cron daemon. It fires when someone loads a page, by making an HTTP request from your server back to your own site at wp-cron.php. That self-call is the loopback, and when it fails, queued mail sits in the queue indefinitely with no error anywhere a site owner would look.
Diagnosing it takes thirty seconds. Open Tools, then Site Health, then the Info tab, then Scheduled events. WordPress runs the loopback test there and prints the actual cURL error when it can’t reach itself.
The causes are almost always at the network layer rather than in WordPress. A firewall rule that blocks the server from calling its own public address. A load balancer that won’t route traffic back to origin. A DNS record for your own domain resolving to somewhere the server can’t reach, which is common right after a migration. HTTP basic authentication on a staging site, which the loopback request has no credentials for. Aggressive bot protection that rate-limits the server’s own requests as suspicious.
The durable fix is to stop relying on page loads. Definir DISABLE_WP_CRON to true in wp-config.php and register a real system cron job that hits wp-cron.php every five minutes. Every decent host supports this, and it also removes the small performance cost WP-Cron imposes on visitors. This cause only applies to mailer plugins with a queue or retry feature. A plugin that sends synchronously during the request never touches cron. That’s exactly why a plugin test email can succeed while queued notifications fail.
Cause 8: The Plugin You Installed to Fix Email Became the Bigger Problem
An SMTP plugin holds the credential to your sending service. Leak that key and an attacker can send mail from a domain you carefully authenticated with SPF, DKIM and DMARC. That’s a worse outcome than sending nothing at all. This stopped being hypothetical in 2026.
Gravity SMTP is the mailer plugin from Rocketgenius, the company behind Gravity Forms. It carried an unauthenticated REST API endpoint that returned a full system report to anyone who asked. The report included PHP and web server versions, loaded extensions, the document root path, the WordPress version and the active theme. It also returned the installed plugin list with version numbers, database platform and table details, and plugin configuration values including possible API keys or tokens.
Every release up to and including 2.1.4 was affected. Rocketgenius patched Gravity SMTP in version 2.1.5 em 17 marcha 2026, and the flaw was published as CVE-2026-4020 on 31 marcha 2026. Vulnerability trackers first observed in-the-wild exploitation on 27 Maio 2026, counting 412 distinct attacking IP addresses by 1 Junho 2026. Security reporting put the affected install base above 100,000 sites.
Run Gravity SMTP and haven’t updated since March? That’s your first job today. Rotate every API key the plugin stored immediately after.
A second incident that same month is worth knowing about before you choose a plugin. Em 12 Junho 2026, tampered JavaScript was served through Awesome Motive’s content delivery network for OptinMonster and TrustPulse between 22:17 e 22:42 UTC. PushEngage kept serving it until 19:02 UTC ativado 13 Junho. The code harvested administrator authentication tokens and nonces, created a rogue admin account and installed a backdoor plugin with a web shell.
Sansec identified it and an advisory followed on 15 Junho 2026. Root cause was a known UpdraftPlus flaw on Awesome Motive’s marketing server, which surrendered CDN API credentials. To be exact about this: WP Mail SMTP is an Awesome Motive product and it was not among the compromised plugins. But that incident is the vendor’s track record rather than a thought experiment. It’s a fair thing to weigh when the plugin will be holding your sending credentials.
Four habits reduce this whole class of risk. Scope your mailer API key to sending only, never to full account access, which every serious mailer supports. Rotate that key after any compromise anywhere in your plugin stack, not just in the mailer. Check a plugin’s last-updated date before installing, because an SMTP plugin untouched for a year is a credential store nobody is patching. And run a periodic check across the whole site rather than the mailer alone. Our walkthrough on testando a segurança do seu site WordPress covers what to look at.
Cause 9: You Hit a Ceiling That Moved
Twilio retired SendGrid’s free Email API and free Marketing Campaigns plans starting 27 Maio 2025, with a 60-day transition window. Any WordPress site still pointing at a free SendGrid key stopped sending in late July 2025. That single change broke sites whose owners had configured SMTP once, years earlier, and never looked at it again. New SendGrid accounts now get a 60-day trial at 100 e-mails por dia, after which Email API plans start at USD 19.95 por mês.
Here’s what the free tiers look like now, all confirmed in August 2026. Brevo remains the most generous at 300 emails per day (aproximadamente 9,000 um mês) with unlimited contacts and no expiry. Resend allows 3,000 a month but caps you at 100 um dia, so it suits steady trickles and not bursts. Mailgun offers 100 a day with no expiry. Postmark’s free plan is 100 emails per mês, which is a development sandbox rather than a production allowance.
Those numbers diverge more than they look. Resend’s 3,000 a month is thirty times Postmark’s free 100, and both stop dead when you hit the line.
Pago, the ranking inverts. Em 10,000 e-mails por mês, Amazon SES custa USD 1.00 on its a la carte rate of USD 0.10 por 1,000. Postmark’s cheapest paid plan covers the same 10,000 por USD 15.00, and Mailgun’s Basic plan asks exactly the same. That’s a 15x difference for identical volume, and it buys you Postmark’s managed sending reputation versus SES handing you the reputation to manage yourself. SES also sells plan-based pricing, with Essentials running USD 0.16 por 1,000 até 10 million a month. New AWS customers receive up to USD 200 in free-tier credits, válido para 12 meses.
Ceilings aren’t the only thing that moves. An expired API key, a rotated password nobody updated in the plugin, a failed card, or a lapsed domain verification will all stop sending. Nothing changes on the WordPress side to warn you. If email died on a specific date and nothing on the site changed, log in to the mailer first. Read its dashboard before you touch WordPress at all.
Pick a Mailer: Four Scenarios With Real Numbers
Generic advice (“choose a reliable provider”) helps nobody. Find the line below that matches your situation.
Volume: debaixo 300 um dia. Budget zero. Brevo’s free tier plus FluentSMTP. It covers a brochure site, a small blog and most membership sites outright. Skip Mailgun’s free plan here. Em 100 a day it’s a third of Brevo’s allowance, and a membership site running a password-reset wave clears 100 before lunch. Don’t plan around SendGrid at this budget either, because Twilio retired its free plan starting 27 Maio 2025.
Carga de trabalho: a WooCommerce store. Entre 40 e 200 pedidos por dia, on managed hosting. Amazon SES over its API. Em 200 orders with a customer copy and an admin copy each, you’re at roughly 12,000 messages a month. That costs USD 1.20 on SES a la carte against USD 15.00 on Postmark’s entry plan. Skip your host’s bundled relay here. Até 80 order emails a day, plus stock alerts and password resets, sits uncomfortably close to Kinsta’s 150-per-day entry cap. Kinsta can disable sending on a serious overage.
Público: inside Microsoft 365. Move transactional mail off the staff mailbox before December 2026, and route it through Brevo or SES instead. If the mail genuinely must appear in that mailbox’s Sent Items, use your plugin’s Microsoft 365 OAuth mailer rather than a password. What you cannot do is fall back on an app password the way Gmail users can. Microsoft’s basic auth deprecation removed app passwords for apps without two-step verification.
Prioridade: placement over price. For receipts and invoices, Postmark at USD 15.00 um mês para 10,000 e-mails. sim, that’s fifteen times SES’s a la carte cost for the same volume. It’s the right trade when nobody on your team will watch bounce rates or warm an IP. Choose SES over it only if someone owns deliverability as an actual job. SES gives you the price and hands you the reputation management along with it.
WP Mail SMTP, FluentSMTP or Post SMTP?
All three do the same core job: redirect wp_mail() through an authenticated connection. Where they part company is price, and what you get without paying.
WP Mail SMTP is the giant: 4+ milhões de instalações ativas, versão 4.9.0, last updated 25 Junho 2026, tested to WordPress 7.0.4. The free version connects to the mailers most sites need. Pro costs USD 49 for the first year against a list price of USD 99. Year two costs 2.02x year one para um único site. Elite is USD 99 primeiro ano (listar USD 149) and adds white-glove setup, meaning their team configures DNS and the mailer for you. Developer covers 20 sites em USD 199, Agency covers 100 em dólares americanos 399, and there’s a 14-day refund window.
FluentSMTP from WPManageNinja has 600,000+ installations and sits at version 2.3.1. Its directory page commits to something unusual: “FluentSMTP is 100% gratuito e de código aberto, and it always will be”. No pro version, no locked features. That’s the comparison that matters. FluentSMTP has roughly one seventh of WP Mail SMTP’s install base. It gives away the email logging and multiple-connection routing that WP Mail SMTP puts behind a licence renewing at USD 99 um ano.
Post SMTP from WPExperts.io is the smallest of the three at 300,000+ instalações, and the most recently maintained, shipping version 4.0.1 em 25 agosto 2026. It rates 4.7 fora de 5 através 525 reviews and needs PHP 7.6 ou mais recente.
Now the recommendations. Install FluentSMTP if you run your own site and want logging plus backup connections without ever seeing an invoice. No feature ransom, no renewal to forget.
Buy WP Mail SMTP Pro if you’re billing a client for the setup and need a vendor with a support desk to escalate to. The Elite tier’s done-for-you DNS configuration can save you a billable afternoon. Just budget the USD 99 renovação, não o dólar 49 título.
Take Post SMTP if you’re already running it and it works. A plugin updated two days ago is not one to migrate away from on principle. Choosing fresh with no other constraint, FluentSMTP’s larger install base and no-paid-tier promise make it the default. WP Mail SMTP is the pick the moment paid support enters the requirements.
How to Stop It Coming Back
Fixing the send is the easy half. Knowing when it breaks again is the half people skip. Email fails silently by nature: nobody complains about an order confirmation they never knew existed.
Turn on email logging in whichever plugin you chose. It costs nothing in FluentSMTP. And it converts “I think the form is broken” into a timestamped record of what was attempted and what the mailer said back. Then enable failure alerts so a delivery error reaches you rather than a log nobody opens. Configure a backup connection if your plugin supports one, so a mailer outage rolls over to a second service instead of dropping mail.
Put three dates in a calendar. A Microsoft 365 basic auth cutoff at the end of December 2026, if any part of your stack still authenticates that way. Your mailer’s API key rotation, on whatever schedule you set. And a quarterly reminder to send one test email. It takes a minute, and it catches the expired-credential failures from cause 9 before a customer does.
Finalmente, read your DMARC aggregate reports rather than just publishing the record. Começando às p=none and never looking at the reports gives you the paperwork without the benefit. The reports tell you which services are sending as your domain. That’s how you catch both a forgotten legacy sender and an attacker, and it’s what lets you move to p=quarantine with confidence instead of hope.
perguntas frequentes
Why does my contact form say the message was sent when nothing arrives?
The success message confirms the form processed the submission, not that any email was delivered. PHP’s mail() function returns true when the server accepts the message for local queuing, so WordPress reports success and never learns what happened next. Trigger a password reset from your login page to test core’s mail path with the form plugin removed from the equation. If the reset arrives and the form notification doesn’t, the fault is in the form’s own notification settings.
Do I need to pay for WP Mail SMTP Pro?
Para a maioria dos sites, não. The free version connects WordPress to the major mailers, which is the fix for the underlying problem. Pro adds email logging, monitorando, backup connections and failure alerts. Custa USD 49 for the first year and USD 99 todos os anos depois, so budget the renewal figure. FluentSMTP includes logging and multiple connections at no cost. The honest case for paying is a support desk you can escalate to, or the Elite tier’s white-glove setup.
Can I use my Gmail account to send WordPress emails?
sim, but not with your normal password. Google ended Less Secure App access for personal Gmail in May 2022 and for Google Workspace on 30 setembro 2024. Enable 2-Step Verification and generate a 16-character App Password, or use your plugin’s Gmail mailer, which connects over OAuth. Watch the ceiling. Gmail counts recipients rather than messages: 500 a day on a personal account, 2,000 on Workspace. A To plus two Bcc addresses costs three.
Why do my WordPress emails go to spam instead of the inbox?
Almost always because the From address isn’t authenticated for the domain it claims. Desde a 1 fevereiro 2024, Google has required SPF or DKIM, valid forward and reverse DNS, and a spam rate under 0.3% from every sender. Yahoo and Microsoft enforce equivalents. Set the From address to your own domain and put the visitor’s address in Reply-To. Then publish SPF, DKIM and DMARC records for the service that actually sends your mail.
Is FluentSMTP better than WP Mail SMTP for a WooCommerce store?
For a store owner managing their own site, sim, on cost. FluentSMTP includes email logging and multiple sending connections for free. Both features matter for a store where a missing order receipt turns into a support ticket. WP Mail SMTP charges USD 99 a year at renewal for the same capability. Choose WP Mail SMTP Pro instead if an agency runs the store and needs vendor support with an invoice behind it. Elite’s white-glove DNS setup is the other reason to pay.
How many emails can my WordPress site send per day on shared hosting?
Fewer than you’d guess, and the numbers vary widely. SiteGround allows 400 an hour on StartUp, GrowBig, Ecommerce and Coderick, subindo para 800 on GoGeek and Cloud. Hostinger’s cPanel Silver and Gold plans allow 2,400 a day and 200 uma hora, counting SMTP and PHP mail against the same quota. Kinsta caps entry plans at 150 transactional emails a day across the whole plan. Routing through an external mailer sidesteps all three limits.
Why did my WordPress emails suddenly stop when nothing on the site changed?
Something changed outside WordPress. The most common culprits are a withdrawn free tier, an expired API key, a failed payment on the mailer account, or a lapsed domain verification. Twilio’s retirement of the SendGrid free plan starting 27 Maio 2025 broke sites this exact way. Microsoft 365 users have a scheduled version of this coming. SMTP AUTH basic authentication is disabled by default for existing tenants at the end of December 2026. Check your mailer’s dashboard before troubleshooting WordPress.
Conclusão
The root cause is nearly always the same. WordPress is handing mail to PHP’s mail() função, which reports success on the handoff and knows nothing about delivery. Your host is either capping that path, blocking its ports or leaving it unauthenticated. Route WordPress through an authenticated mailer and most of this list stops applying at once.
Concretely: instalar FluentSMTP unless you need paid support. Connect it to Brevo if you send under 300 e-mails por dia, or to Amazon SES if you send more and someone will watch deliverability. Connect over the API rather than an SMTP port, and publish SPF, DKIM and DMARC for the sending domain. Escolher WP Mail SMTP Pro instead when a client is paying and a support contract matters, and price it at the USD 99 renovação. Then do the two things almost nobody does. Turn on logging. And put the end of December 2026 in your calendar if any part of your stack still signs in to Microsoft 365 with a password.
Maybe this hunt has convinced you the real problem is the plan underneath the site, not the plugin on top of it. Nosso guia para choosing hosting for a WordPress website covers what sending headroom to look for before you migrate. De lá, the natural next reads are our comparisons of dedicated SMTP relay services and business email hosting. A site that has outgrown its host’s mail quota has usually outgrown its mailbox setup too.