WordPress keeps the administration email change pending

Identify the request that remains pending

You entered a new address under Settings, then General. WordPress still displays a pending change, even after a successful test email from your mail tool. The priority is to follow that specific request: the currently active address, proposed destination, message generation and confirmation. A successful SMTP test does not automatically complete a request created before the transport was repaired.

You must also distinguish two independent settings. The site's administration email address receives messages about site operation. Your account's address is in your user profile and is used, among other things, for communications about that account. Changing the first does not replace the second. If you expect to log in using the new address, check the relevant profile instead of repeatedly changing Settings.

This guide covers the native change of a WordPress site's administration email address. Multisite network and hosting platform settings may have their own screens and recipients. A contact form may also use an address saved elsewhere. Do not consider the correction successful until you have identified the setting that actually needs to change.

Prepare access and useful information

You must be authorized to administer the site and use the new mailbox. To repair the native request, access to the new destination matters more than access to the old mailbox: confirmation is sent to the new address. This does not remove the need to verify site ownership and the agreement of the person responsible for its notifications.

If you work for an organization, check that the mailbox is monitored and another responsible person can access it when you leave. Avoid moving site notifications to a personal mailbox merely to clear the pending message.

1. Keep a valid administration session open and record your login identifier in your usual manager. Do not simultaneously start a password or profile change.
2. Privately record the active address displayed in Settings and the one named in the pending request. Check typing errors, spaces and the exact domain. A merely similar address is not an acceptable destination.
3. Record the time of a recent attempt and the mail tool already in use. Record its name and status without copying an SMTP password, API key or confirmation link into a public ticket.
4. Identify the rollback route: cancel the unconfirmed request or, after confirmation, request another change to an address still under control. Also retain the original transport configuration before changing it.

Separate the site address, profile and sender

Open Settings, then General, and inspect the administration email field and the notice below it. The field contains the active address; the notice shows a proposed address awaiting confirmation. Until the request completes, seeing the old address in the field may therefore be normal. Record both values separately instead of concluding that WordPress forgot your input.

Then open your profile in another tab, for viewing only. The profile address may legitimately differ. If this field has a pending request, you are in a different confirmation flow. Return to the correct screen and limit the correction to that request. Do not change every administrator account to make their addresses visually match the site's.

Finally, the sender configured in an SMTP tool is a third element. Its address must match the authorized transport; it is not automatically replaced by the administration address. Forcing a new sender without checking the sending domain can introduce another failure. Retain the configuration delivering messages when native confirmation is the only remaining problem.

A simple record suffices: target setting, active address, proposed address, sender and test destination. This private table prevents comparing a message received by your account with a confirmation sent to another mailbox.

Check receipt before restarting a request

The proposed mailbox must first receive a message sent from a source you control. This checks its existence and receiving rules; it does not yet check WordPress. Open its actual interface, then inspect spam, any quarantine and rules moving or forwarding messages. If a provider manages the mailbox, request a delivery record for a specific time.

A positive result from the sending function or plugin does not, by itself, prove delivery to the mailbox. A useful result connects sending with observed receipt. Keep useful tracking information without archiving personal message content.

1. Send a simple message to this mailbox from an authorized address, with a recognizable subject and no client data. Check actual receipt, not just the absence of an immediate bounce.
2. From the mail tool already configured in WordPress, send one test message to this same destination. Record the time, tool result and message's presence in the mailbox.
3. If the test succeeds only for another destination, compare the proposed mailbox's receiving rules. Do not yet replace the administration address with that other destination to bypass diagnosis.
4. If no WordPress tests arrive, address transport before recreating the request. An authentication error, provider rejection and acceptance without delivery are different observations.

Cancel the old request, then create a new confirmation

Once email reaches the correct mailbox, return to Settings, then General. Saving an already-pending value several times does not guarantee generation of a new message. The native flow lets you cancel the existing request and create a new one. It also avoids accumulating messages whose relationship to the current state is unclear.

If the link leads to an old site address or another installation, do not try to rewrite its confirmation parameter. Keep a redacted description of the discrepancy and correct the site context with its owner. An incomplete migration deserves a separate diagnosis.

1. Check again that the notice concerns the intended destination. Click Cancel beside that request. After returning to the screen, the notice should be gone and the active address unchanged.
2. Now enter the new address in the administration field and save once. Check that a new pending notice appears with exactly that destination.
3. Record the time and check the mailbox or authorized mail capture. Look for the message associated with the relevant site and this new attempt, rather than an old message found at random.
4. Before opening the link, check the site name and destination domain. The link contains confirmation information: do not publish it or send it to a URL analysis service.
5. Log into the administration area of the same installation with an account authorized to change its general settings. Open the link from the new message in that session, then return to Settings > General. The active address should now be the new one and the pending notice should be gone. Mailbox access alone does not allow confirmation of the change.

Run a controlled test on an authorized copy

On an isolated copy, a mail capture system lets you observe the flow without notifying a real person. First check that outgoing mail from this copy is actually captured and its commercial integrations are disabled. A mere “staging” label in hosting does not prove this isolation.

Prepare two test addresses recognized by the local capture, A and B, without reusing a client address. On this copy only, record A as the active address. Request a switch to B, then observe three elements: A remains active, the notice names B and the capture contains a confirmation addressed to B. This separates request creation from acceptance.

Then cancel the request in settings. Check that the notice disappears and A stays active. On this copy only, open the canceled test link from the authorized session and return to settings. A must still be active. Finally, create a new request to B and use the link from the new message. Check that B becomes active and the notice disappears. Return to A through a new confirmed request if the copy must regain its initial state.

This control validates neither the real provider's deliverability nor your domain's DNS configuration. It checks the local request, cancellation and confirmation cycle. To finish correcting the real site, you must still observe receipt in the authorized mailbox and the new value in that site's own settings.

Use WP Mail SMTP only if transport needs it

If the site lacks suitable transport, WP Mail SMTP can provide a way to configure it and send a control message. Its usefulness here is limited to email. The plugin does not replace validation of the new address or, on its own, explain why an old request remains pending. If another solution already handles delivery, start with its diagnostics.

If transport setup is refused or unknown, keep the documented state and pass the requirement to the mail administrator. Changing a provider, sender or DNS record affects other site emails; it must not become an improvised experiment for this one confirmation.

1. On the copy, record the current configuration and select one transport with the owner. Do not activate two competing plugins to try several providers at once.
2. Configure the authorized sending method using the provider's settings. Use a sender validated for this transport and protect credentials. Do not save production secrets in a shared copy without an appropriate policy.
3. Under WP Mail SMTP > Tools, open the Email Test tab. Explicitly enter the proposed mailbox, because the suggested destination may be your profile's address. On the copy, check that this destination belongs to the capture system. Run one test, then check actual receipt.
4. If this test works, return to cancellation and a new request in WordPress settings. Observe the confirmation message separately from the plugin test.

Locate the break when the test arrives but confirmation does not

After a new request, compare times and recipients. If the plugin test arrives but no confirmation message is visible in authorized tracking, first check that the new pending notice appears. Without it, the entry may not have been saved on the correct screen, or the destination may match the already-active address.

If the notice appears, use available traces to determine whether WordPress submitted the message to transport. Do not conclude that nothing was sent because optional logging is disabled. A provider may supply an identifier and delivery status without exposing the body. This is preferable to recording a full message containing a confirmation link.

Rejection after site acceptance points to the provider or receipt. No attempt in a correctly established tracking system points to the WordPress flow or a customization altering its messages. On a copy, the owner can compare behavior with a minimal configuration, making one change at a time while keeping test transport identical. They must restore each setting before attributing the result to a plugin.

If receipt works but confirmation does not change the value, check that you are using the latest message and correct site. Replaced or canceled requests are no longer valid evidence. Never pass their full parameters in a public support request.

Adapt the process when you lack some access

With settings access but no mailbox access, you can identify both values and cancel an incorrect request if responsible for it. You cannot demonstrate receipt. Involve the new mailbox's owner or agree with them on a destination that is actually accessible. Avoid repeated attempts to third-party addresses that have not agreed to receive these messages.

With mailbox access but no settings access, prepare the time and site name shown in the message. The site owner must check the active request and its destination before opening the confirmation flow. Do not ask them to hand over their administration account to complete this step.

With hosting access only, do not change several tables to force synchronization of the site's address and user addresses. The need is to restore a specific flow, not replace every occurrence of an address in the database. The owner can arrange a targeted technical intervention after backup and ownership checks; this exception must leave a record of the previous value, intended value and effect on notifications.

Validate the correction and plan its reversal

Confirmation is complete when the correct site's screen displays the new active address with no pending request. Check the user profile separately: it must not have changed if you handled only the site address. Also check that the transport sender remains as intended. This comparison avoids declaring success when a different setting was changed instead.

Before confirmation, rollback consists of canceling the request. After confirmation, request another change to the authorized return address and confirm it from that mailbox. Do not restore the entire database to undo this single setting: you could lose other recent operations. Emails already sent are not canceled by this rollback.

If you added a tool solely for a test, first check whether real sending now depends on it. Restore the documented original transport before removing it, or retain the chosen solution with its owner. Close unnecessary temporary logs and apply the planned retention period to test captures. Finally, retain a report without secrets: validated destination, confirmation time, receipt result and retained configuration.

Configure standard SMTP transport already included with your email service

This free workflow suits a provider that permits an SMTP connection with dedicated settings. The free plugin does not make the email service free or guarantee its quota. Under Plugins > Add New Plugin, search for WP Mail SMTP, check the publisher, then install and activate the plugin on the copy. Do not add this transport if another already works.

Under WP Mail SMTP > Settings > General, enter the authorized sender address and choose Other SMTP. Copy the host, encryption and port from your provider's documentation; do not choose a port through repeated guesses. Enable authentication if required by the provider and use dedicated credentials or the designated app password. Site administrators should be considered to have access to this configuration.

Save, then open Tools > Email Test and send to the controlled mailbox. After actual receipt, resume cancellation and creation of the WordPress request. If your provider requires OAuth or an API, use its documented integration instead of forcing this SMTP flow. Keep the initial configuration to restore transport if the test fails.