1. Start with permission
The strongest campaign begins before the message is written. Every recipient should have a legitimate relationship with the sender and a reasonable expectation of receiving the type of message being sent.
Good sources include direct customer signups, clearly described newsletter forms, membership enrollment, event registration with an email choice, or an existing customer relationship where the message is relevant and lawful. Keep enough source information to explain when and how the address entered the list.
Do not use purchased, rented, scraped, harvested, guessed, or appended email lists. A list can be technically valid and still be inappropriate to contact. Sending to people who did not ask for the message creates complaints, blocks, damaged domain reputation, and legal risk.
2. Build the SMTP rotation correctly
WHPSend organizes campaigns and hands messages to SMTP accounts you control. Customer accounts should not configure Web Host Pro-hosted mailboxes or SMTP hosts on Web Host Pro networks.
Connect third-party email accounts that explicitly support authenticated SMTP. For a small campaign, configure and test at least three separate SMTP-enabled email accounts. Larger campaigns need more accounts in the cycle so the work is distributed without forcing one mailbox beyond its normal limits.
- Confirm the SMTP hostname, port, encryption mode, username, and password with the provider.
- Use a From address that the SMTP provider authorizes.
- Set realistic hourly and daily limits below the provider's maximum.
- Test every account before adding it to an active rotation.
- Pause accounts that show authentication, reputation, or repeated delivery failures.
3. Authenticate the sending domain
SPF, DKIM, and DMARC help receiving systems understand which services may send for a domain and what to do when authentication fails. Configure them according to the third-party SMTP provider's instructions and verify them before a campaign.
The visible From domain should align with the authenticated sending identity whenever possible. Avoid changing domains or sender identities frequently; consistency gives recipients and providers a clearer history to evaluate.
4. Prepare a healthy list
Remove obvious errors, duplicates, invalid domains, previous hard bounces, complaints, suppressions, and unsubscribed recipients before sending. WHPSend's list-health tools can help identify records that need review, but automated checks do not replace permission.
Segment the audience by the reason for the message. A smaller, relevant list typically performs better than a broad list assembled only because the addresses are available.
5. Write an honest, useful message
Use a recognizable sender name, a subject that accurately describes the content, and a message that delivers the value promised when the recipient joined. Keep the primary purpose obvious. Avoid misleading urgency, false replies, imitation security notices, or subject lines that conceal a promotion.
Include a working unsubscribe link and any business identification required for your audience. Preview the campaign on both desktop and mobile, verify every link, and send a test to accounts at different mailbox providers before queueing the full audience.
6. Increase volume gradually
New mailboxes and domains do not have an established sending history. Begin with smaller groups of engaged recipients and increase volume gradually. Sudden bursts from new or previously quiet accounts can look abnormal even when the list is legitimate.
For larger campaigns, add more properly configured SMTP accounts instead of forcing the minimum three accounts to carry all volume. Keep each account inside its provider's limits and monitor the combined pace of the rotation.
7. Watch the response
Review delivery logs during and after every campaign. Repeated authentication failures, blocks, bounces, or complaint signals are reasons to pause and investigate, not reasons to immediately retry at a higher rate.
Honor unsubscribe requests promptly, preserve suppression records, and remove failed addresses where appropriate. Recipient behavior is feedback about list quality, expectations, frequency, and message relevance.
Common mistakes that damage delivery
Sending to a list you cannot explain
If you cannot describe where an address came from and why the recipient expects the message, do not send to it.
Using only one mailbox
A single account creates a fragile campaign and concentrates volume. WHPSend requires at least three third-party SMTP-enabled accounts for small campaigns and more for larger rotations.
Using Web Host Pro mail or IP addresses
Web Host Pro-hosted mailboxes and SMTP hosts on reserved Web Host Pro networks are unavailable to customer accounts. Use approved outside providers with SMTP access, and diversify the rotation across services when practical.
Ignoring authentication
A campaign should not begin until SPF, DKIM, DMARC, From identity, and SMTP authentication have been reviewed.
Sending too much too quickly
Provider limits are ceilings, not goals. Volume should match the history of each mailbox, the quality of the list, and the engagement of recipients.
Hiding the unsubscribe option
Making it difficult to opt out turns a manageable unsubscribe into a complaint. Keep the choice obvious and honor it.
Retrying failures without diagnosis
Repeatedly retrying blocked or invalid recipients can make the problem worse. Read the error, correct the cause, and suppress addresses that should not be retried.
Campaign preflight checklist
- The audience gave permission or has another lawful, relevant basis for contact.
- The list source is documented and suppressions have been preserved.
- At least three third-party SMTP-enabled accounts are active and tested.
- Larger campaigns have additional SMTP accounts and conservative limits.
- No Web Host Pro-hosted mailbox or SMTP host on a Web Host Pro network is being used for customer delivery.
- SPF, DKIM, DMARC, From identity, and reply handling are configured.
- The subject and content are accurate, useful, and free of deceptive elements.
- Links, mobile layout, unsubscribe handling, and test deliveries work.
- The team is ready to monitor logs and pause when warning signals appear.
Need help reviewing the setup?
Use the WHPSend contact form for general product questions. Existing customers should open an authenticated support ticket when the request involves account details, SMTP configuration, or private campaign information.