BugWP logo BugWP
Back to Community
Home / Community / General

Why Your FluentSMTP From Name Isn't Working (And How to Fix It)

18 threads Sep 16, 2025

Content

Understanding the FluentSMTP "From Name" Issue

A common issue reported by users of the FluentSMTP plugin is that the configured "From Name" is not being used when emails are sent. Instead, emails might show a generic name like "SMTP_NAME," the name associated with the email account itself, or even the WordPress admin email name. This guide will explain why this happens and provide the most effective solutions based on community reports and resolutions.

Why Does This Happen?

The "From Name" not being respected is rarely a bug in the FluentSMTP plugin itself. Based on numerous support threads, the cause is almost always related to one of the following factors:

  • Email Provider Restrictions: Certain providers, especially Microsoft 365/Outlook, have strict rules about which "From Name" and "From Email" can be used, often tying them directly to the account used for authentication.
  • API Key Generation: For API-based connections (Gmail, Outlook), the "From Name" and "From Email" are often locked to the identity of the account that generated the API keys.
  • Alias Configuration: Attempting to send from an alias email address (e.g., [email protected] vs. [email protected]) often requires specific permissions granted by the email provider, not just configuration within WordPress.
  • Conflicting WordPress Settings: Other plugins or your site's admin email setting might be overriding the FluentSMTP configuration.

Common Solutions to Fix the From Name

1. For Gmail or Outlook API Connections

If you are using an API connection (Gmail or Microsoft 365/Outlook), the solution is specific:

The Fix: You must generate a new set of API keys (Client ID and Secret) using the exact email account you want to appear as the "From Email." The "From Name" will then typically be the display name associated with that specific email account in your Google Workspace or Microsoft 365 admin panel.

As noted in support threads, generating API keys with one email and trying to send from a different alias will not work due to permission structures inherent to these services.

2. For Microsoft 365/O365 Alias Issues

This is one of the most frequently reported scenarios. Users find that even after configuring an alias and checking "Force Sender Name," emails are sent from the primary account's details.

The Fix: This is primarily a restriction on Microsoft's side. The FluentSMTP team's consistent advice is to:

  • Create a separate connection in FluentSMTP for each alias you wish to use.
  • Contact Microsoft Support to request the necessary permissions or features be enabled on your tenant to allow sending from aliases via API or SMTP. This often involves specific settings in the Azure Portal that are not adjustable by default.

3. Clearing a Persistent "SMTP_NAME" or Other Generic Name

If your emails are stubbornly showing a name like "SMTP_NAME," the issue is likely that another plugin is overriding the FluentSMTP settings.

The Fix: You can add a small code snippet to your theme's functions.php file or a code snippets plugin to prevent this override:

add_filter('fluentsmtp_disable_from_name_email', '__return_true');

4. Check the "Default Connection" Setting

FluentSMTP will try to match the "From Email" address of an outgoing message with a configured connection. If no match is found, it uses the connection marked as "Default." If your admin email is overriding your intended "From Name," ensure the email address you are trying to send from is explicitly set up in its own connection or matches the default connection's email.

Conclusion

In most cases, a "From Name" not working is not a flaw in the FluentSMTP plugin but a result of how modern email providers handle authentication and identity. The solution almost always involves configuring your email service (be it Google, Microsoft, or another SMTP provider) correctly to grant the necessary permissions for the name and address you want to use. For complex provider-specific issues like Microsoft aliases, contacting your email host's support is often the most direct path to a resolution.

Related Support Threads Support