BugWP logo BugWP
Back to Community
Home / Community / General

How to Configure Post SMTP for WordPress Multisite: Global vs. Individual Settings

18 threads Sep 17, 2025

Content

Configuring the Post SMTP plugin on a WordPress Multisite network can be a source of confusion. A common challenge users face is understanding how to manage settings across multiple subsites—whether to enforce a single, global SMTP configuration or allow for individual, per-site setups. This guide explains the two primary methods and provides steps to implement them.

The Core Issue: Global vs. Individual Control

By default, when you network-activate the Post SMTP plugin, it may not be immediately clear how settings are managed. Users often expect to find a configuration panel in the Network Admin dashboard, but this is not currently the primary method for centralized control. The confusion arises from two different operational modes:

  1. Global Settings Mode: A single SMTP configuration defined on the main site is applied to all subsites in the network.
  2. Individual Settings Mode: Each subsite can have its own unique SMTP configuration and "From" email address.

Solution 1: Enabling Global Settings for a Unified Configuration

This is the recommended approach if you want all subsites to use the same SMTP connection (e.g., the same Mailgun, Gmail, or Office 365 account).

  1. Network Activate: In your WordPress Network Admin dashboard, navigate to Plugins > Installed Plugins. Find "Post SMTP" and choose Network Activate.
  2. Configure the Main Site: Go to the main site's WordPress dashboard (often labeled "Main Site" or with ID 1). Navigate to Post SMTP > Settings and complete the SMTP setup wizard. Test the connection to ensure it works.
  3. Enable the Global Flag: While still on the main site, go to Post SMTP > Settings. Look for a checkbox or setting labeled "Enable global settings" or "Global Settings" and check it. Save your changes.

Once this is done, all subsites should inherit this main configuration. Their individual Post SMTP settings pages will likely be hidden or display a message indicating they are using the network's global settings.

Troubleshooting Global Settings

If you've followed the steps but subsites are not using the global configuration (as mentioned in Thread 14), try these steps:

  • Ensure the plugin is network-activated, not just activated on the main site.
  • Clear any caching on your site or server after enabling the global setting.
  • Deactivate and reactivate the plugin network-wide. Sometimes, a reactivation can resolve inheritance issues.

Solution 2: Allowing Individual Site Configuration

If you need each subsite to send from its own email address (e.g., [email protected] and [email protected]), you must disable the global settings mode.

  1. On the main site, go to Post SMTP > Settings.
  2. Uncheck the "Enable global settings" option and save your changes.
  3. You can now navigate to the dashboard of any subsite. You will find the Post SMTP menu available, allowing you to run the setup wizard and configure a unique SMTP connection for that specific site.

Important Considerations for Multisite

  • Email Logs: Email logs are typically kept separate for each subsite and are viewed within each site's own dashboard.
  • API Keys & Webhooks: For services like Google OAuth or Slack notifications, you generally need to generate a unique client ID and secret or webhook URL for each individual subsite where you configure a separate connection (Thread 5, 18).
  • Plugin Updates: After a major plugin update, you may be required to complete a brief migration or authorization step on each subsite (Thread 7). For networks with many sites, this process can be cumbersome and may require developer assistance to automate.

Conclusion

Effectively managing Post SMTP in a Multisite environment hinges on correctly using the "Enable global settings" option. Use it to enforce a uniform mailing solution across your network, or disable it to grant subsites autonomy over their email configurations. If you continue to experience issues, providing a detailed diagnostic report from the plugin can be the key to getting further assistance from the community.

Related Support Threads Support