Cookbook Maintenance GoSMTP

Fix Emails That Come From “WordPress” with GoSMTP and AI

Find out why emails say WordPress instead of your name, and the two boxes in GoSMTP that fix it.

Difficulty Beginner

Time ~5 min

Prerequisites

A site connected to WPVibe running GoSMTP 1.2.1 or newer (tested on 1.2.4, free) on WordPress 6.9 or newer, with an administrator account, and Enable AI Abilities switched on under GoSMTP > AI Abilities.

The prompt

My WordPress site uses GoSMTP. My emails come from "WordPress" at wordpress@my domain instead of my own name and address. Find out why and tell me how to fix it. Don't change any settings yourself.

1. Run discover_abilities with category gosmtp-test. If gosmtp-test/send-mail is not there, run rest_api GET /wp/v2/plugins with search gosmtp. If GoSMTP is active and its version is 1.2.1 or newer, tell me its AI abilities are off until I tick Enable AI Abilities in the Enable Abilities box under GoSMTP > AI Abilities in wp-admin (the MCP Adapter and Application Password steps on that page are not needed for WPVibe; if it is already ticked, the site needs WordPress 6.9 or newer), and stop. If it is installed but not active, tell me to activate it (updating it first if it is older than 1.2.1) and then tick Enable AI Abilities under GoSMTP > AI Abilities, and stop. If it is not installed or is older than 1.2.1, tell me to install or update the free GoSMTP plugin (1.2.1 or newer, on WordPress 6.9 or newer), and stop. Never read the gosmtp_options option directly: it holds the mail passwords and API keys.
2. Run gosmtp-settings/get and gosmtp-mailer/list. If mailers is empty, tell me GoSMTP has no mailer saved yet, so it is not handling my email at all: set one up under GoSMTP > Settings first. Then stop. If the primary mailer is gmail, outlook, zoho, amazonses, elasticemail, smtp2go, resend or mailersend, run rest_api GET /wp/v2/plugins with search gosmtp. If GoSMTP Pro is not active, tell me that mailer needs GoSMTP Pro, so GoSMTP is not handling my email and its From settings have no effect: reactivate GoSMTP Pro or pick another mailer on GoSMTP > Settings. Then stop.
3. Explain what I have: GoSMTP uses its From Email and From Name only when Force From Email and Force From Name are on. With them off, WordPress's own emails (password resets, new accounts, admin notices) go out as WordPress, from wordpress@my domain, and a plugin that sets its own sender keeps it. With them on, every email the site sends uses GoSMTP's From Email and From Name, including emails from my store or form plugins.
4. Ask me which address to send a test to, then run gosmtp-test/send-mail once with to set to it and subject GoSMTP sender test. If the call itself fails instead of returning sent, quote its error. If it says a valid recipient is required, ask me for the address again; otherwise stop. If sent is false, tell me the error and that the sending itself needs fixing first (the GoSMTP test email recipe covers it), and stop. Otherwise ask me what the From line shows.
5. If force_from_email and force_from_name are already true and from_email and from_name are filled in, but the test still came from WordPress, tell me GoSMTP's settings are right and something else is setting the sender: run rest_api GET /wp/v2/plugins and name any other active mail or SMTP plugin, and stop. If they are already on and filled in and the test shows my name and address, tell me GoSMTP is set up right: emails that still say WordPress were sent before the change or by something that does not go through GoSMTP (run rest_api GET /wp/v2/plugins and name any other active mail or SMTP plugin), and stop. Otherwise tell me the fix on GoSMTP > Settings: if From Email or From Name is empty, fill it in, with an address my mail provider lets me send from, ideally at my own domain (for Gmail, the account's own address or an alias added in Gmail's settings); tick Force From Email and Force From Name; save. Tell me this changes the sender of every email the site sends, so a plugin that uses its own sender address will use this one instead.
6. When I say I have saved, run gosmtp-settings/get and confirm force_from_email and force_from_name are true, and that from_email and from_name are not empty (GoSMTP ignores Force when they are). Then run gosmtp-test/send-mail once more to the same address and ask me to check the From line. If the From line shows a different address than From Email, my provider replaced it: for Gmail, add it as an alias in Gmail first. If this test fails when the first one worked, tell me my mail provider is refusing the new From Email: use an address or domain verified with that provider, or untick Force From Email until it is, because forcing it affects every email the site sends.

Already connected?

Skip pasting the full prompt. Drop this into your AI on a site that already has WPVibe:

Run the “Fix Emails That Come From “WordPress” with GoSMTP and AI” recipe from the WPVibe cookbook on my connected site.

Your password reset and new account emails arrive from WordPress, wordpress@yourdomain, even though you typed your shop’s name and address into GoSMTP. Customers don’t recognize the sender, and some mail providers treat it as spam.

The AI reads GoSMTP’s From settings, sends you a test email so you can see the sender you actually get, and explains why: GoSMTP uses its From Email and From Name only when Force From Email and Force From Name are ticked. Without them, WordPress’s own emails go out as WordPress, and every plugin that sets its own sender keeps it. It tells you exactly what to tick, then sends a second test to confirm.

Forcing applies to every email the site sends, so a store or form plugin’s own sender is replaced too: in our test, an email sent as a different address and name went out as GoSMTP’s From Email and From Name once Force was on. Use an address your mail provider allows you to send from. If test emails don’t arrive at all, start with this recipe.

Outcome

Your emails come from your own name and address, confirmed by a test email.