The newsletter leaves the same server as WordPress: 8,000 recipients, PHP mail() script. The next day, all transactional mail — invoices, password resets — lands in spam. The shared IP is blacklisted. The host suspends sending, sometimes the whole account. The website and the mailing list are not the same business.
Web hosting serves pages and, sometimes, limited SMTP for transactional mail. Emailing — Brevo, Mailjet, Mailchimp, and equivalents — runs bulk send infrastructure with reputation, bounces, unsubscribe, and analytics. Confusing the two endangers what actually drives revenue: mail customers expect after a purchase.
Typical host SMTP limits
On shared hosting, daily quotas often sit between 200 and 500 messages — a serious newsletter exceeds that in minutes. A shared IP carries the reputation of hundreds of neighbor sites, some sending spam. Without structured feedback loops, bounces harden the list invisibly. Abuse policies are strict: one report can suspend the entire site, not just marketing sends.
For a low-volume contact form, authenticated SMTP or a light third-party service is enough. For a list, a dedicated ESP is the norm.
Choosing and configuring an ESP
Check region and DPA if your list is European — the logic in choosing a cloud region applies to subscriber data. Respect GDPR opt-in: proof of consent, unsubscribe link, processing register. Configure SPF, DKIM, and DMARC progressively with DNS records from the provider. Warm up volume gradually on a new domain. Clean the list: remove hard bounces and long inactive addresses.
WordPress plugins should call the provider API — not send thousands of messages via wp_mail. See also SPF, DKIM, DMARC for mail authentication.
Link to site hosting
The site stays with your host; sending goes through the ESP. Do not confuse MX for business mail @company.tld — sometimes at the host or Google Workspace — with campaigns sent via newsletter@ and provider DNS. If a send script is compromised, see handling abuse.
The climax: shared IP is not newsletter reputation
Compare SMTP limits and offers on the directory and comparator.
Decide and move forward without blind spots
From day one, separate the transactional channel — hosting or dedicated SMTP — from marketing via an ESP with its own reputation. Configure SPF, DKIM, and DMARC on the sending domain before the first bulk send. Document opt-in and GDPR-compliant unsubscribe. Never send more than a few hundred messages per day from shared hosting without written host approval. Finally, monitor transactional deliverability after each campaign — that is the most reliable alarm signal.
Frequently asked questions
Can I send my newsletter from shared hosting?
Technically sometimes yes, practically discouraged: low quotas (200–500/day), shared IP sometimes already tainted, no fine bounce handling. Blacklist and abuse suspension risk — see also hosting terms.
What is the difference between site SMTP and a mailing tool?
Site SMTP serves transactional mail — orders, password resets. A mailing tool brings dedicated reputation, bounce handling, unsubscribe, stats, and GDPR opt-in compliance.
SPF and DKIM — what to configure?
SPF authorizes sending servers; DKIM signs the message. The mailing tool provides DNS records — separate from web MX. Do not exceed ten DNS lookups for SPF.
Host business email on the same provider as the site?
Possible on shared IMAP for classic business mail. Mass lists stay on a dedicated ESP; do not mix newsletter reputation with support mail reputation.
If your newsletter leaves the same server as the blog, it is not a saving — it is a risk to all your email.