Fix PrestaShop Deliverability with Mailpro SMTP (Step-by-Step)

Introduction

PrestaShop handles catalog, carts, and checkout well—but many stores still rely on default PHP mail for transactional emails. That’s a deliverability trap. Without authenticated SMTP and domain alignment, mailbox providers are more likely to route your messages to spam. The fast fix is to route PrestaShop through Mailpro’s Swiss-hosted SMTP, then add SPF, DKIM, and DMARC to your sending domain. This guide shows the exact steps, the recommended ports (465/587), where to find the settings in PrestaShop 8/1.7, and a practical troubleshooting checklist.

Why PrestaShop Emails Land in Spam

PHP mail vs. authenticated SMTP

PHP mail sends without strong authentication by default. Authenticated SMTP verifies your identity and establishes a trusted channel using encryption (TLS/SSL), username, and password. Mailboxes prefer authenticated, aligned sends and will reward you with better inbox placement.

Missing domain authentication

If your domain lacks SPF, DKIM, and DMARC, providers can’t confidently verify that your messages are legitimate, which increases spam filtering and spoofing risk.

Sender/domain mismatch

Using a From address that doesn’t match the authenticated domain (or switching domains frequently) can look suspicious to mailbox filters.

Why Use Mailpro’s Swiss-Hosted SMTP

• Swiss-hosted privacy: Data residency you can point to, with compliance in mind.
• Deliverability fundamentals: Clear guidance for setup and authentication, plus transparent stats.
• Real-time visibility: Monitor sends, track engagement, and investigate issues quickly.
• Human support: Get help when you’re under deadline.

Learn more on the Mailpro SMTP/API page and SMTP/API FAQs.

PrestaShop 8 vs 1.7: Where to Find SMTP Settings

• PrestaShop 8: Advanced Parameters → Email → Email → “Set my own SMTP parameters”.
• PrestaShop 1.7: Advanced Parameters → Email → Email → “Set my own SMTP parameters”.

The labels are nearly identical; if you use a theme or admin enhancer, the path can appear under “Shop Parameters → Advanced,” but the fields are the same.

PrestaShop SMTP Setup with Mailpro (5 Minutes)

Works for PrestaShop 8 and 1.7. Exact labels may vary slightly by version, but the flow is the same.

1) Open the email settings

In PrestaShop, go to Advanced Parameters → Email and choose “Set my own SMTP parameters (for advanced users ONLY)”.

2) Enter your Mailpro SMTP credentials

• SMTP server: Use the value provided in your Mailpro account.
• Encryption: TLS/SSL (see notes below).
• Port: 465 (SSL) or 587 (TLS).
• Authentication: Yes (username & password).
• Username/Password: Your Mailpro SMTP credentials.

For the current, exact hostnames and port/encryption recommendations, consult: SMTP/API overview and SMTP/API FAQs.

3) Use an aligned From address

Set the From email to an address on the same domain you authenticate in Mailpro (e.g., [email protected]). Alignment helps DMARC pass and improves reputation.

4) Send a test email

In the same PrestaShop screen, use Send a test email. Confirm it arrives in the inbox (not spam). If it fails, jump to Troubleshooting.

5) Save your settings

Once the test works, save. Your store notifications will now send through Mailpro SMTP.

Exact Field Mapping (Cheat Sheet)

Ports & Encryption Matrix (465 vs 587)

• SSL + 465: Encrypted tunnel on connect; conservative firewalls often allow it.
• TLS + 587: Starts plain, upgrades to encryption; widely supported by hosts and ISPs.

If one path is blocked by hosting/firewall, try the other with the matching encryption.

Authenticate Your Domain: SPF, DKIM, DMARC

Domain authentication is essential. Add the DNS records Mailpro provides for your sending domain, then verify and retest.

• SPF: Authorizes Mailpro’s servers to send for your domain.
• DKIM: Cryptographically signs messages to prove authenticity.
• DMARC: Tells receivers how to handle failures and helps protect against spoofing.

Follow the guides here: SMTP/API FAQs. After propagation, resend your PrestaShop test email.

DMARC Policy Progression (Safe Rollout)

1. p=none (monitor): gather reports, fix alignment issues.
2. p=quarantine (soft enforcement): catch stragglers without hurting legitimate flow.
3. p=reject (full enforcement): once SPF/DKIM alignment is solid.

Keep all PrestaShop senders on the same authenticated domain to avoid alignment failures.

Which PrestaShop Emails Should Use SMTP?

• Order confirmations, invoices, shipping updates
• Account creation, password reset, two-factor prompts
• Refund notices, status changes, support tickets

All of the above benefit from authentication + Mailpro logging for audits and customer support.

Test, Monitor, and Improve

After switching to SMTP and authenticating your domain, monitor performance in Mailpro: Statistics.

• Watch delivery, opens, and clicks to confirm improvements.
• Track trends against context like what is a good email open rate.
• Investigate any spikes in bounces or complaints immediately.

Troubleshooting: Common Errors & Quick Fixes

Best Practices for Long-Term Deliverability

• Use dedicated, aligned senders: e.g., [email protected], [email protected].
• Consistent branding: Same From name/domain across notifications to build recognition.
• Keep templates lean: Clean HTML, clear text, and distinct links. Avoid excessive images or heavy code.
• Monitor signals: Keep an eye on Mailpro statistics to catch issues early.
• Secure your domain: Maintain SPF/DKIM/DMARC; rotate keys as needed; avoid forwarding chains that break authentication.
• Consider API for scale: If you outgrow SMTP, Mailpro’s API offers programmatic sending with robust logging.

Preflight Checklist (Copy/Paste)

• ✅ SMTP credentials saved and test email delivered
• ✅ From domain authenticated in Mailpro (SPF, DKIM, DMARC)
• ✅ Templates use your authenticated sender and consistent branding
• ✅ Statistics monitored in Mailpro
• ✅ Fallback port tested (465↔587) in case of host/firewall quirks

FAQs

Which port should I use, 465 or 587?

Both are supported. Use 465 with SSL or 587 with TLS, consistent with the settings provided in your Mailpro account. See SMTP/API FAQs.

Do I need SPF, DKIM, and DMARC?

Yes—these records help mailbox providers verify your identity and reduce spam placement. Configure them from the SMTP/API FAQs and retest.

Can I use Mailpro’s API instead of SMTP?

Yes. If you need more control or higher throughput, consider the Mailpro API.

Our PrestaShop emails still don’t send—what next?

Recheck your credentials, switch ports, confirm DNS, and test a default template. If problems persist, contact us: Mailpro support.

Will this affect our marketing newsletters?

No. This setup is for transactional notifications (orders, shipping, invoices, password resets). You can continue to run newsletters and promotions in Mailpro separately using your SMTP/API or the campaign sender.

Wrap-Up

Routing PrestaShop through Mailpro’s Swiss-hosted SMTP plus authenticating your domain (SPF, DKIM, DMARC) removes the biggest reasons transactional emails hit spam. Configure SMTP, send a test, monitor results in Mailpro statistics, and keep templates clean and consistent. That’s the path to steady inbox placement.

Ready to switch? Review the SMTP/API overview, compare pricing, or contact us for help with your setup.