Start here

Set up your sender

Configure transport, inspect a received test and choose a pace your provider supports.

Free and Pro4 min readVersion 1.0.10
01

Connect your mail transport

The plugin submits messages through your configured WordPress mail transport. Set up a suitable SMTP or delivery plugin separately; NewsletterPlatform.com does not include a hosted sending allowance. Verify that your provider authorizes the sender address and use the exact domain-authentication records that provider supplies.

02

Save recognizable sender details

In Settings, enter the sender name, sender email, reply-to and owned test inbox. Add your business mailing address and privacy page, then save. In Delivery and site safety, inspect the current site identity and sending hold. Confirm production only for the site intended to send live mail.

The sender diagnostics check configured values and readiness. They do not verify SPF, DKIM, DMARC, domain ownership or inbox placement.

Save a recognizable sender, reply address and email footer. This local example does not demonstrate inbox delivery.
Free 1.0.10 · Actual WordPress interface. Save a recognizable sender, reply address and email footer. This local example does not demonstrate inbox delivery. Open full screenshot ↗
03

Test the complete path

Send an owned-address test of a saved draft. Check the received sender, reply address, authentication results, images, links and mobile rendering. Test representative recipient clients before a live campaign. An accepted WordPress call means the transport accepted the message; it is not proof of delivery.

If the test does not arrive, inspect your transport/provider logs. Do not repeatedly resend a whole campaign to diagnose an inbox problem.

04

Check limits and scheduling

The standard profile defaults to 30 attempts per hour and 5 per pass on a five-minute schedule. An administrator can separately acknowledge throughput mode and declare a provider allowance. Its upper configuration limits are 6,000 attempts per hour and 100 per pass; the lower of the configured cap and declared provider allowance applies.

These are ceilings, not guaranteed throughput. A worker stops starting new deliveries after a 20-second budget; an in-flight transport request can last longer. Host scheduling, provider throttling and transport speed still determine progress. Keep the limit conservative until you have measured your own setup.