Skip to main content
WP Postman records every email your WordPress site attempts to send, whether it succeeds or fails. The Email Logs screen gives you a timestamped, searchable history of all outbound messages — complete with the recipient address, subject line, delivery status, and the full message body. When something goes wrong with email delivery, the logs are the fastest way to identify whether the problem is with your SMTP credentials, your server connection, or the recipient’s mail server.

Accessing Email Logs

1

Open the WordPress admin dashboard

Log in to your site’s WordPress admin area at /wp-admin.
2

Navigate to WP Postman

Click WP Postman in the left-hand sidebar menu.
3

Click Email Logs

Select Email Logs from the WP Postman submenu. The full log table loads immediately, sorted by most recent first.

Understanding the Log Table

Each row in the log table represents a single outbound email attempt. The columns are:

Viewing a Log Entry

1

Locate the entry you want to inspect

Find the message in the log table by scanning the Recipient or Subject columns, or use your browser’s find-in-page to search for a specific address.
2

Click the View button

Click the View button in the Action column for that row. A detail panel opens.
3

Review the message details

The detail panel shows the complete email headers (From, To, CC, Reply-To), the full HTML or plain-text message body, and — for failed messages — the error response returned by the SMTP server. Copy this error text when contacting your SMTP provider’s support team.

Diagnosing Failed Emails

When a log entry shows a Failed status, the error message in the detail panel points to the root cause. Use the accordion below to match the error to a fix.
The SMTP server rejected your username or password. Double-check both fields in WP Postman → SMTP Settings. If you are using Gmail, remember that your regular Google account password does not work here — you must generate and use a dedicated App Password with 2FA enabled on your Google account. For other providers, verify that the credential you are using has not been rotated or revoked in your provider’s dashboard.
WP Postman could not establish a TCP connection to the SMTP host. Confirm the hostname is spelled correctly and that the port number matches the encryption setting you have chosen (587 for TLS, 465 for SSL). On some network configurations a firewall rule on the server blocks outbound SMTP connections — if you suspect this, contact WP Stratos support to confirm whether outbound connections on your chosen port are permitted.
The server connected but failed to negotiate a secure channel. This usually means there is a mismatch between the encryption setting in WP Postman and what the remote server expects. Try switching the Encryption setting between TLS and SSL, or temporarily set it to None to isolate whether the issue is with the encryption negotiation itself. Re-enable encryption once the connection is confirmed working.
Your SMTP server accepted the message and attempted delivery, but the recipient’s mail server refused it. This is outside WP Postman’s control and is typically caused by the recipient’s domain having strict spam filters, a full mailbox, or a policy that blocks messages from your sending domain. Check that your From Email address is on a domain with valid SPF, DKIM, and DMARC records published in DNS. Your SMTP provider’s dashboard may show additional bounce details.
Email logs are retained for 30 days and then automatically deleted. If you need to keep a longer-term record of email activity, export or copy relevant log entries before they age out.
Any time you update your SMTP settings, send a test email immediately and then open the Email Logs to confirm the new settings produced a Sent status. This habit catches misconfigured credentials before your users run into a broken password-reset or order-confirmation flow.