Deliverability, diagnostics and troubleshooting

Why emails land in spam

Receiving servers (Gmail, Outlook, Yahoo) check whether the server sending an email is allowed to send for its From domain. Three DNS records answer that question:

  • SPF lists the servers allowed to send mail for your domain.
  • DKIM adds a signature that proves the email wasn’t changed and came from your provider.
  • DMARC tells receivers what to do with mail that fails SPF or DKIM.

Your email provider gives you the exact records to add at your domain registrar or DNS host. Gmail and Yahoo now require SPF, DKIM and DMARC for most senders.

Diagnostics

Open Broodweb SMTP → Diagnostics and click Run Diagnostics. Each check shows OK, a warning or a failure, with an explanation.

DNS (MX records) Your From domain has mail servers.
SPF An SPF record exists for your From domain.
DKIM A DKIM record exists on a common selector (default, google, selector1, selector2, k1, smtp, s1, mail). A warning here can be a false alarm if your provider uses its own selector name; check its DNS instructions.
DMARC A DMARC record exists at _dmarc.yourdomain.com.
PHP, OpenSSL, extensions PHP version, OpenSSL for encrypted connections, and the curl, mbstring and json extensions.
REST API The plugin dashboard can talk to your site.
WP-Cron The queue worker is scheduled, and whether DISABLE_WP_CRON is set.
Server time, memory, database, file permissions, WordPress General health of the environment.

System Status shows the full server, PHP, database and WordPress details. Include it when you contact support.

Common problems

Connection test fails at DNS lookup

The host name is misspelled or doesn’t exist. Copy it again from your provider’s instructions.

Connection test fails at TCP connection or times out

Your host is blocking the port. Many shared hosts block 25, and some block 465 and 587 too. Try another port and encryption pair (587/STARTTLS, 465/SSL, or 2525 if your provider supports it). If every port is blocked, ask your host to open one, or switch to an API mailer (SendGrid, Mailgun, Postmark, Brevo), which uses normal HTTPS.

TLS verification or certificate errors

Check that the encryption matches the port: SSL with 465, STARTTLS with 587. Use the host name from your provider’s instructions, not an IP address, because the certificate is issued for the name.

Authentication fails (535, “Username and Password not accepted”)

  • Gmail / Google Workspace: your normal password won’t work. Turn on 2-step verification and create an App Password.
  • Office 365: SMTP AUTH must be enabled for the mailbox in the Microsoft 365 admin centre. Security defaults can block it.
  • Zoho, Yahoo: use an app password.
  • The username is usually the full email address.
  • If you changed your WordPress security keys, enter the password again (see Keeping credentials in wp-config.php).

The test email is “sent” but never arrives

  1. Check the spam folder.
  2. Make sure the From Email is on a domain you own and is allowed to send through your provider (a verified sender or domain for API services).
  3. Run Diagnostics and fix SPF, DKIM and DMARC.
  4. Check your provider’s activity log for bounces or blocks.

“Sender address rejected” or “not owned by user”

Your mail account isn’t allowed to send from the From Email. Use the same address as the SMTP username, or one the provider has verified, and keep Force this From email ticked.

Emails are stuck in the queue

The queue only moves when WP-Cron runs. Check the WP-Cron line in Diagnostics, check that the queue isn’t paused, and click Run Now to send a batch by hand. On quiet sites, set up a real server cron job for wp-cron.php.

The dashboard keeps loading or shows errors

The plugin’s screens load their data through the WordPress REST API. If a security plugin or firewall blocks /wp-json/, allow the bw-smtp/v1 routes for logged-in administrators. The REST API line in Diagnostics shows whether it is reachable.

Settings don’t seem to apply

Another SMTP plugin may be active and overriding them. Deactivate it. Also check whether the field is locked by a wp-config.php constant.

Was this article helpful to you?

Newsletter

Stay in the loop

Get notified about new plugins, updates, and exclusive tutorials.

No spam ever. Unsubscribe anytime.