Make WordPress transactional email a boring part of running your site.
Route the messages WordPress sends through authenticated Parcel Wing SMTP instead of depending on your web server's default mail setup. You can start with an existing SMTP plugin today; no Parcel Wing-specific WordPress plugin is required.
WooCommerce order and customer emails
WordPress password resets and account notices
Contact-form notifications that use wp_mail()
Plugin and membership notifications that use WordPress mail
The setup path
WordPress already has a common mail surface: most transactional messages flow through wp_mail(). A compatible SMTP plugin can redirect that mail to Parcel Wing without changing WooCommerce templates or rewriting your site.
Add and verify your sending domain
Parcel Wing shows the DNS records your domain needs and checks the observed configuration before you send production mail.
Create SMTP credentials
Use Parcel Wing's SMTP credentials with a WordPress SMTP plugin that supports a custom or other-SMTP connection.
Route WordPress mail through Parcel Wing
Enter the host, port, encryption, username, and password from the Parcel Wing SMTP setup in your WordPress mail plugin.
Send a real test
Test the SMTP connection, then trigger the WordPress or WooCommerce message you actually care about so you verify the full application path.
Keep your existing WordPress stack
Use a plugin that supports custom SMTP. Parcel Wing is the sending service, not a replacement for WooCommerce or your form plugin.
Verify before production traffic
Domain readiness and test sending give you a clearer boundary between a WordPress configuration problem and a sender-domain problem.
Start with the mail your store depends on
Test order confirmations, password resets, and other operational messages instead of stopping after a generic SMTP test succeeds.
Already using WP Mail SMTP?
You can keep your current WordPress mail plugin. Choose Other SMTP, use Parcel Wing's verified-domain sending credentials, and send a test before changing production email.
Connect WP Mail SMTP to Parcel WingAlready using FluentSMTP?
Keep FluentSMTP installed. In its settings, add a connection, choose Other SMTP, and use the same Parcel Wing sending credentials as other SMTP clients. There is no native FluentSMTP integration or vendor partnership.
- Add the sender domain to Parcel Wing, publish its requested DNS records, and wait for sending readiness.
- Create an active Parcel Wing API key. In FluentSMTP, choose Other SMTP.
- Set the SMTP host to
smtp.parcelwing.com, port587, encryption to TLS (STARTTLS), and authentication to On. Useparcelwingas the username and the active API key as the password. - Set From Email to an address on your verified domain. Save the connection, run FluentSMTP's email test to an inbox you control, then trigger a real WordPress or WooCommerce notification before switching production traffic.
Keep your prior SMTP settings for rollback. If the connection times out, check whether your host permits outbound port 587; if authentication fails, check the username and API key. Store the API key carefully: FluentSMTP documents options for storing connection secrets, including its WordPress configuration path. A successful test handoff does not guarantee inbox placement.
For the plugin's current screens and secret-storage options, consult FluentSMTP's official Other SMTP instructions.
Password reset email missing?
Separate an account or reset-flow error from a WordPress mail failure first. If the reset request reaches wp_mail(), then test the shared SMTP path and move outward to provider acceptance and mailbox placement.
Contact Form 7 notification missing?
Start with the form result and Contact Form 7 Mail settings before changing SMTP or DNS. Then test the shared WordPress mail path and move outward only if the form itself is configured correctly.
Troubleshoot Contact Form 7 emailMail sends, but lands in spam?
First separate a message that was rejected or bounced from one the recipient accepted and placed in spam. Then check the shared SMTP path, sender identity, domain authentication, and the real WordPress message that is being filtered.
Running WooCommerce?
See the store-specific setup path when you are connecting order and customer email, or use the troubleshooting checklist if messages are already failing.
