Route WordPress Email Through Authenticated SMTP—with Clear Setup and Diagnostics
Aegisify Core SMTP Settings gives WordPress administrators one shared place to configure authenticated email delivery for password resets, WooCommerce order messages, form notifications, security alerts, backup notices, and other mail sent through WordPress. Instead of depending only on the hosting server’s default mail function, administrators can select Aegisify SMTP when available or connect a supported SMTP provider using the required host, port, encryption, authentication, sender identity, and reply-to settings.
The goal is not to promise inbox placement. It is to make WordPress email routing more controlled, provider-authenticated, testable, and easier to troubleshoot before important messages are placed into production workflows.
What the Aegisify SMTP Settings Page Does
Aegisify Core acts as the shared administrative control plane for WordPress email routing. The SMTP page brings the transport, sender identity, credential, and diagnostic settings into one controlled workflow.
Send WordPress Mail Through SMTP
When SMTP and global routing are enabled, mail generated through the WordPress mail workflow can use the configured SMTP transport instead of relying only on the server’s default mail mechanism.
Use an Authorized Sender
Define the From Email, From Name, and Reply-To address so transactional messages use a consistent identity aligned with the domain and provider you control.
Test Before Depending on Delivery
Use Test Connection to validate the SMTP session, then Send Test Email to confirm the complete path from WordPress to the configured administrative recipient.
Choose the Delivery Option That Fits Your Environment
The current Aegisify Core interface supports a suite relay option when available and licensed, common provider labels, and manual SMTP configuration. Always verify the exact endpoint and credential requirements in your provider’s current documentation.
Prepare the Provider and Sender Before Configuration
Collect the provider-issued connection details first. This reduces trial-and-error and helps distinguish WordPress configuration problems from provider, DNS, or hosting restrictions.
Configuration Checklist
- SMTP hostname for the correct provider and region
- Required port and matching encryption method
- Provider-issued SMTP username and password or token
- A From Email address authorized by the provider
- A monitored Reply-To address
- SPF, DKIM, and DMARC records where applicable
- Outbound firewall access from the WordPress host
- Access to the WordPress Admin Email inbox for testing
Common Port and Encryption Pairings
| Port | Typical Transport | Operational Guidance |
|---|---|---|
| 587 | TLS / STARTTLS | Common submission configuration for authenticated SMTP. Use it when your provider documents this pairing. |
| 465 | Implicit SSL/TLS | Used by providers that require encryption from the beginning of the SMTP connection. |
| 25 | Provider-specific | Frequently blocked or restricted by hosting providers. Use only when both the provider and host permit it. |
Recommended Aegisify Core SMTP Configuration Workflow
Complete the configuration in this order so each test has a clear purpose and failed delivery can be isolated more quickly.
Open Aegisify SMTP Settings
Sign in to WordPress as an Administrator and go to Aegisify → SMTP Settings. Access to shared Core settings should remain limited to trusted administrators.
Enable SMTP Deliberately
Turn on Enable SMTP. Enable Send all WordPress emails via SMTP when the goal is to route the site’s WordPress mail consistently through this transport.
Select Aegisify SMTP or a Provider Preset
Choose Aegisify SMTP when the licensed relay integration is available, select a listed provider, or use Custom SMTP or Other for manual configuration. Presets are configuration aids; verify all populated values.
Enter the Host, Port, and Encryption
Use the exact SMTP hostname supplied by the provider. Match the port to the required TLS, STARTTLS, or SSL/TLS method. A mismatched port and encryption setting is a common connection failure.
Configure Authentication
Enable SMTP authentication when required and enter the provider-issued SMTP username and secret. For Amazon SES, use generated SES SMTP credentials rather than an AWS console login.
Set the Sender and Reply Path
Enter a verified From Email, a clear From Name, and a monitored Reply-To address. A strong default is an address on a domain your organization controls and has authorized with the provider.
Save and Confirm the Effective Configuration
Save the settings and review the values again. Existing saved options or supported configuration-file overrides may affect which values are actually used.
Run Both Diagnostic Tests
Run Test Connection first, then Send Test Email. Confirm receipt at the WordPress Admin Email and review spam, quarantine, or provider logs when the message does not appear.
Protect SMTP Credentials and Sending Reputation
SMTP configuration affects a business-critical communication path. Treat the password or token as a production secret and treat the sending domain as part of your organization’s reputation.
Keep Secrets Out of Screenshots and Exports
Use provider-scoped credentials, restrict WordPress Administrator access, and never expose SMTP passwords in screenshots, public tickets, documentation examples, database exports, or copied support messages.
Use the Configuration Override Workflow Where Appropriate
Aegisify Core can present a configuration-file snippet for supported SMTP overrides. This can keep secrets out of normal WordPress options and make development, staging, and production values easier to separate. Store secrets using protected configuration or environment-management practices.
Understand What Each Diagnostic Proves
A successful connection is necessary, but it is not the same as verified message delivery. Run both tests and evaluate the results separately.
Test Connection
Checks whether WordPress can reach the SMTP host using the selected port, encryption, and authentication settings. Failure commonly points to the endpoint, credentials, TLS pairing, DNS, or outbound firewall access.
Send Test Email
Sends an actual message to the WordPress Admin Email to verify more of the end-to-end route. For Amazon SES accounts operating in Sandbox, the recipient may also need to be verified with SES.
When the SMTP Test Fails
Work through the failure in a controlled order rather than changing several settings at once.
Confirm the hostname, port, encryption, provider region, DNS resolution, and outbound firewall policy on the WordPress host.
Recheck the SMTP-specific username, password, API token, account status, and whether the credential is authorized for SMTP submission.
Verify the From Email or domain with the provider and review SPF, DKIM, DMARC, sandbox, and regional sender requirements.
Check the WordPress Admin Email, spam and quarantine folders, provider activity logs, suppression lists, and recipient-side filtering.
Confirm that Aegisify Core has an active eligible license and that the relay integration is available for the site and plan.
Review the sending plugin, From address overrides, message size, attachment behavior, recipient policy, and application-specific mail hooks.
Aegisify Core SMTP FAQ
What happens when Aegisify SMTP is disabled?
Aegisify Core does not apply its SMTP routing configuration. WordPress continues using the mail behavior otherwise available to the site and hosting environment.
Does SMTP guarantee that messages reach the inbox?
No. SMTP provides an authenticated delivery path to the provider. Final acceptance and inbox placement can still depend on sender authorization, DNS alignment, provider reputation, message content, recipient filtering, suppression lists, and account limits.
Can I use a provider that is not listed?
Yes, when the service supports standard SMTP and supplies the required hostname, port, encryption, authentication, and sender details. Use Custom SMTP or Other and follow that provider’s current instructions.
Why should I run Test Connection and Send Test Email?
Test Connection evaluates the SMTP session and authentication. Send Test Email evaluates more of the real delivery path. Passing one test does not automatically prove the other.
How can Aegisify AI help?
Ask about Aegisify or WordPress: errors, plugins, security, SEO, compatibility, troubleshooting, comparisons, or launch a free website scan.
Understand Every WordPress SMTP Setting Before You Route Production Email
This Aegisify Core SMTP field reference explains every control involved in WordPress SMTP routing: the master enablement switch, global mail routing, provider selection, host, port, encryption, authentication, credentials, sender identity, diagnostics, and supported wp-config.php overrides.
Use it when configuring a new provider, reviewing an existing installation, troubleshooting delivery, preparing a migration, or documenting how password resets, WooCommerce messages, form notifications, security alerts, and other WordPress email leave the site.
Routing and Scope
These controls determine whether Aegisify Core participates in WordPress mail delivery and how broadly the configured transport is applied.
Enable SMTP
Master SwitchEnable SMTP is the top-level control for Aegisify Core’s outbound mail routing. When enabled, supported WordPress mail operations can use the SMTP configuration saved on the page or supplied through supported configuration overrides. When disabled, Aegisify Core does not apply those SMTP settings and WordPress continues using the site’s otherwise available mail behavior.
The documented default is disabled, which avoids changing production mail until an administrator deliberately configures, saves, and tests the transport.
Send All WordPress Emails via SMTP
Global ScopeThis option applies the configured SMTP route broadly to mail generated through the WordPress mail workflow, including core notifications, password resets, WooCommerce transactional messages, form notifications, plugin alerts, and supported custom application messages.
Enable it when the objective is a consistent transport across the site. Before depending on global routing, test the workflows that matter most because plugins or custom code may alter headers, sender identities, attachments, or delivery behavior.
Provider, Host, Port, and Encryption
These fields define which SMTP relay WordPress contacts and how the connection is established and encrypted.
Provider
Configuration AidThe Provider selector helps administrators begin with an appropriate configuration pattern for a known SMTP service. A preset can suggest or populate transport values, but it does not remove the need to verify the provider’s current hostname, region, port, encryption, credential, sender, and account requirements.
The public interface example uses Amazon SES (SMTP). Treat that as an example configuration rather than a required provider or universal default. Administrators can use a listed provider or enter compatible SMTP settings manually.
SMTP Host
Relay EndpointThe SMTP Host is the fully qualified hostname of the server that accepts outbound mail from WordPress. Enter the exact endpoint documented by the provider. Some services use regional or account-specific hosts, so copying an endpoint from another environment can produce connection or authentication failures.
The Aegisify guide shows email-smtp.us-east-1.amazonaws.com, the Amazon SES SMTP endpoint for the US East (N. Virginia) region. A production site must use the endpoint that matches its provider and credential region.
SMTP Port
Network PathThe SMTP Port determines where WordPress opens the network connection to the relay. The port must match the provider’s documented encryption method and must be allowed by the WordPress hosting environment.
Port 587 with STARTTLS is common. Port 465 is often used for implicit SSL/TLS. Port 25 may be blocked or restricted by hosting providers and should be used only when both the provider and host explicitly support it.
Encryption
Transport SecurityThe Encryption field controls how the SMTP connection is protected in transit. With TLS/STARTTLS, the connection begins and is upgraded to an encrypted session. With implicit SSL/TLS, encryption is established when the connection opens.
Select the exact method required by the provider and pair it with the correct port. An incorrect pairing can prevent connection negotiation. Encryption protects the transport between WordPress and the SMTP relay; it does not by itself guarantee final delivery or inbox placement.
Authentication, Username, and Password
These settings prove to the relay that the WordPress site is authorized to submit mail through the selected account.
Use SMTP Authentication
AuthorizationWhen authentication is enabled, Aegisify Core supplies the configured SMTP username and password or token during the SMTP session. Most commercial SMTP services require authenticated submission to prevent unauthorized relay and associate messages with an approved account.
Disable authentication only when an administrator understands the relay architecture and the provider explicitly supports a trusted internal or otherwise controlled unauthenticated path.
Username
SMTP IdentityThe Username field stores the provider-issued SMTP authentication identity. It may not be the same as the administrator’s normal account login. Enter the exact SMTP username generated or documented by the provider.
For Amazon SES, use the SES-generated SMTP username. Do not use an AWS console password or assume that a general IAM credential is interchangeable with the SES SMTP credential.
Password
Sensitive SecretThe Password field contains the SMTP secret, password, or token paired with the username. Treat it as a production credential. Do not expose it in screenshots, public support messages, page source, documentation examples, database exports, migration packages, or shared backups.
Where supported by the installed Aegisify Core version, prefer the generated wp-config.php override workflow for sensitive values. In managed environments, use protected configuration, environment variables, deployment secrets, or a server-side secrets manager rather than hard-coding real credentials into public or version-controlled files.
From Email, From Name, and Reply-To
These settings determine the sender identity shown to recipients and where responses are directed.
From Email
Sender AddressThe From Email appears in outgoing message headers and should be an address or domain the SMTP provider has authorized. A provider may reject or rewrite messages when the address is unverified or conflicts with account and domain policies.
Use a domain your organization controls and align the sending setup with provider-supported SPF, DKIM, and DMARC records where applicable. These controls support authentication and reputation management, but they do not guarantee inbox placement.
From Name
Display IdentityThe From Name is the human-readable sender displayed in the recipient’s mailbox. Use a name that clearly identifies the organization, product, store, support team, or operational function responsible for the message.
Consistency matters more than promotional wording. A stable sender name can help recipients understand why they received the email and distinguish transactional communication from unrelated marketing.
Reply-To
Response PathThe Reply-To address tells the recipient’s email client where responses should go. It can match the From Email or direct replies to a monitored support mailbox, shared inbox, ticketing system, or operational team.
A Reply-To field does not replace sender verification. Keep the From Email aligned with the authenticated sending policy and use Reply-To to preserve a practical response workflow. Avoid directing users to an unmonitored address when the message reasonably invites a reply.
Diagnostics: Test the Connection and the Delivery Path
The two diagnostic actions answer different questions. Run both after initial setup and after any provider, credential, DNS, hosting, firewall, port, encryption, or sender change.
Test Connection
Purpose: Checks whether WordPress can reach the SMTP host and complete the configured connection and authentication sequence.
- Use after changing the provider, hostname, port, encryption, username, or password.
- A failure often points to the endpoint, TLS pairing, credential, DNS, or outbound firewall policy.
- A successful connection does not prove that the recipient received the message.
Send Test Email
Purpose: Sends a real message to the WordPress Admin Email and validates more of the end-to-end route.
- Confirm the WordPress Admin Email before testing.
- Review the inbox, spam, quarantine, suppression, and provider activity logs.
- For Amazon SES in Sandbox, the recipient may also need to be verified in SES.
Secure wp-config.php Overrides
Aegisify can provide a ready-to-copy configuration snippet so supported SMTP values can be managed outside ordinary WordPress database settings.
Why Administrators Use Overrides
- Keep sensitive SMTP secrets out of ordinary WordPress options.
- Separate development, staging, and production mail configuration.
- Reduce accidental secret exposure during database exports and migrations.
- Make deployment-managed configuration easier to review and rotate.
- Preserve controlled settings when the WordPress database is cloned.
Implementation: Copy the exact snippet generated by the installed Aegisify Core version and place it above the standard “stop editing” line in wp-config.php. Do not copy real credentials into public documentation or source control.
AEGISIFY_SMTP_ENABLED
AEGISIFY_SMTP_HOST
AEGISIFY_SMTP_PORT
AEGISIFY_SMTP_ENCRYPTION
AEGISIFY_SMTP_AUTH
AEGISIFY_SMTP_USERNAME
// The public guide also references a password
// override such as:
AEGISIFY_SMTP_PASSWORDOperational Best Practices for Administrators and Integrators
Treat SMTP as a production dependency. A successful one-time test is useful, but ongoing reliability also depends on provider status, credentials, DNS, sending limits, hosting policy, and recipient filtering.
Use the correct regional hostname, port, encryption, SMTP credential type, verified identity, and account state documented by the provider.
Use scoped SMTP credentials, restrict Administrator access, rotate exposed secrets, and keep production values out of screenshots and repositories.
Configure provider-supported SPF, DKIM, and DMARC records and review alignment when messages are rejected, quarantined, or classified as spam.
Repeat both diagnostics after migrations, DNS edits, provider changes, credential rotation, firewall changes, or WordPress hosting moves.
Review provider quotas, rate limits, suppression lists, verified-recipient rules, account restrictions, and regional service status.
Test password resets, WooCommerce messages, forms, alerts, and other critical workflows—not only the built-in test message.
SMTP Field Reference FAQ
Does enabling SMTP guarantee better deliverability?
No. Authenticated SMTP can provide a more controlled and diagnosable transport than an unconfigured server mail path, but delivery still depends on the provider, sender authorization, DNS alignment, reputation, message content, account limits, and recipient filtering.
Is Amazon SES the required Aegisify SMTP provider?
No. Amazon SES appears in the public guide as an example configuration. Use the provider and endpoint appropriate to your environment and verify every preset value before saving.
What is the difference between From Email and Reply-To?
From Email identifies the sender in the message headers and should align with the provider’s authorized sending policy. Reply-To tells the recipient’s mail client where a response should be directed.
Why can Test Connection pass while the message is missing?
The connection test validates access to the SMTP service. The message can still be filtered, suppressed, rejected by sender policy, affected by account restrictions, or delivered to spam or quarantine.
Should SMTP secrets be stored in wp-config.php?
Use the supported configuration method that best fits your security and deployment model. A protected override can keep secrets out of ordinary database options, but the file and secret source must still be secured and excluded from public repositories, logs, screenshots, and exposed backups.
