{"id":1146,"date":"2026-03-13T15:25:13","date_gmt":"2026-03-13T12:25:13","guid":{"rendered":"https:\/\/allinonewpsettings.com\/blog\/?p=1146"},"modified":"2026-09-12T17:14:03","modified_gmt":"2026-09-12T14:14:03","slug":"configure-smtp-wordpress","status":"publish","type":"post","link":"https:\/\/allinonewpsettings.com\/blog\/configure-smtp-wordpress\/","title":{"rendered":"WordPress SMTP Settings: Host, Port and Setup Guide"},"content":{"rendered":"

WordPress cannot send email out of the box. It tries, but on most servers the attempt either fails silently or the message lands in spam. WordPress SMTP settings<\/strong> change the last link in that chain: the message now leaves through an authenticated mail server rather than the server’s local delivery agent.<\/p>\n

This guide covers where the problem comes from, the real host and port values by provider, and a verification that proves the settings are actually in use.<\/p>\n

\nTable of contents<\/strong><\/p>\n
    \n
  1. Why WordPress mail does not arrive<\/a><\/li>\n
  2. WordPress SMTP settings by provider<\/a><\/li>\n
  3. Before you enter your WordPress SMTP settings<\/a><\/li>\n
  4. WordPress SMTP settings step by step<\/a><\/li>\n
  5. Verification: is it really working<\/a><\/li>\n
  6. If it still does not work<\/a><\/li>\n
  7. AIOWS SMTP Manager<\/a><\/li>\n
  8. FAQ<\/a><\/li>\n
  9. Sources<\/a><\/li>\n<\/ol>\n<\/div>\n

    Why WordPress mail does not arrive<\/h2>\n

    When WordPress sends email it calls wp_mail()<\/code>. That function uses the PHPMailer library, and PHPMailer hands the message to PHP’s mail()<\/code> function by default. mail()<\/code> passes it to the local delivery agent on the server.<\/p>\n

    There are two break points in that chain.<\/p>\n

    The first:<\/strong> most shared hosting providers disable mail()<\/code> or block outbound port 25. The restriction exists to stop spam, and it stops legitimate site mail along with it. WordPress reports success and nothing leaves.<\/p>\n

    The second, and the more insidious one:<\/strong> even when mail()<\/code> works, the message goes out without authentication. The receiving server cannot verify that it was authorised to send on behalf of your domain. SPF and DKIM do not align, the Return-Path does not match, and the message either lands in spam or is rejected outright.<\/p>\n

    WordPress SMTP settings replace that last step. PHPMailer no longer hands the message to a local agent; it connects to a real mail server with credentials and sends from there. The message now leaves an authenticated source.<\/p>\n

    WordPress SMTP settings by provider<\/h2>\n

    WordPress SMTP settings need four values: host, port, encryption type and authentication method. They are connected \u2014 pairing the port with the wrong encryption is the single most common mistake.<\/p>\n

    \n\n\n\n\n\n\n\n\n\n\n\n
    Provider<\/th>\nHost<\/th>\nPort<\/th>\nEncryption<\/th>\nAuthentication<\/th>\n<\/tr>\n<\/thead>\n
    Gmail (personal)<\/td>\nsmtp.gmail.com<\/code><\/td>\n587<\/td>\nSTARTTLS<\/td>\nApp password<\/td>\n<\/tr>\n
    Gmail (personal)<\/td>\nsmtp.gmail.com<\/code><\/td>\n465<\/td>\nSSL\/TLS<\/td>\nApp password<\/td>\n<\/tr>\n
    Google Workspace<\/td>\nsmtp.gmail.com<\/code><\/td>\n587<\/td>\nSTARTTLS<\/td>\nApp password or OAuth<\/td>\n<\/tr>\n
    Microsoft 365<\/td>\nsmtp.office365.com<\/code><\/td>\n587<\/td>\nSTARTTLS<\/td>\nOAuth 2.0 recommended, SMTP AUTH must be on<\/td>\n<\/tr>\n
    Yandex<\/td>\nsmtp.yandex.com<\/code><\/td>\n465<\/td>\nSSL\/TLS<\/td>\nApp password (mandatory), username is the part before @<\/td>\n<\/tr>\n
    Shared hosting<\/td>\nmail.yourdomain.com<\/code><\/td>\n465<\/td>\nSSL\/TLS<\/td>\nMailbox credentials<\/td>\n<\/tr>\n
    Shared hosting<\/td>\nmail.yourdomain.com<\/code><\/td>\n587<\/td>\nSTARTTLS<\/td>\nMailbox credentials<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    About the shared hosting rows:<\/strong> on cPanel-based providers the mail.yourdomain.com<\/code> pattern applies. The exact values are in cPanel under Email Accounts \u2192 Connect Devices \u2192 Mail Client Manual Settings<\/strong>; whatever that screen shows is correct for your server.<\/p>\n

    Why port 25 is not in the table:<\/strong> port 25 is for server-to-server delivery and most hosting providers block outbound traffic on it. Site mail goes out over 587 or 465.<\/p>\n

    Microsoft 365 does not offer 465.<\/strong> Microsoft accepts only 587 with STARTTLS for client submission. A device trying to connect on 465 will not connect at all.<\/p>\n

    Microsoft 365 is changing its authentication.<\/strong> Microsoft is retiring connection by app password for SMTP submission in favour of OAuth 2.0. When it is switched off, the error reads:<\/p>\n

    550 5.7.30 Basic authentication is not supported for Client Submission<\/code><\/pre>\n
    If you see that, your password is not wrong \u2014 the method is no longer accepted. Check Microsoft’s own announcement for the current timetable; the date has been postponed more than once.<\/p>\n
    Yandex uses a different username.<\/strong> Other providers take the full email address; Yandex takes only the part before the @. For example@yandex.com<\/code> the username is example<\/code>.<\/p>\n
    Yandex also has two prerequisites: in the mail settings, under Email clients<\/strong>, turn on IMAP access and “App passwords and OAuth tokens” before creating an app password at id.yandex.com\/security<\/code>. The password is shown once and can take a few hours to become active.<\/p>\n
    Connecting from outside Russia, smtp.ya.ru<\/code> is the more reliable host.<\/p>\n
    587 or 465:<\/strong> both are correct; the difference is when encryption starts. 587 opens plain and upgrades with the STARTTLS command. 465 is encrypted from the first byte. Use whichever your provider documents; where both are supported, 587 is the more common choice.<\/p>\n
    \n\"Pairing
    A crossed pairing breaks the connection \u2014 this is the most common mistake.<\/figcaption><\/figure>\n
    Before you enter your WordPress SMTP settings<\/h2>\n
    Note what is there now.<\/strong> If an SMTP plugin is already installed, screenshot the host, port and sender address fields. If the new settings do not work you can go back.<\/p>\n
    Create an app password.<\/strong> Gmail, Microsoft 365 and Yandex will not accept your account password over SMTP. You need a separate app password, and that requires two-step verification on the account.<\/p>\n
    In Gmail: Google Account \u2192 Security \u2192 2-Step Verification \u2192 App passwords.<\/p>\n
    \n\"Creating
    The password is shown once \u2014 do not close the dialog before saving it.<\/figcaption><\/figure>\n
    Decide the sender address.<\/strong> It has to be on the same domain as the mailbox you authenticate with. Connecting as info@yourdomain.com<\/code> and sending as noreply@anotherdomain.com<\/code> is a reason to be rejected.<\/p>\n
    WordPress SMTP settings step by step<\/h2>\n
    Whichever SMTP plugin you use, the fields are the same.<\/p>\n
    Host:<\/strong> the value from the table, for example smtp.gmail.com<\/code>.<\/p>\n
    Port:<\/strong> 587 or 465.<\/p>\n
    Encryption:<\/strong> STARTTLS for 587, SSL\/TLS for 465. Getting this pairing wrong comes back as a connection timeout or a certificate error.<\/p>\n
    Authentication:<\/strong> on.<\/p>\n
    Username:<\/strong> usually your full email address. Some hosting providers use a different pattern; the configuration screen in cPanel shows the right one.<\/p>\n
    Password:<\/strong> the app password. Not the account password.<\/p>\n
    From address:<\/strong> the address of the mailbox you authenticate with.<\/p>\n
    From name:<\/strong> your site name. This is what the recipient sees in their inbox.<\/p>\n
    Save, then go to verification. Saving is not the same as working.<\/p>\n
    Verification: is it really working<\/h2>\n
    Sending a test email is not enough. All four checks have to pass.<\/p>\n
    \n\n\n\n\n\n\n\n\n
    Check<\/th>\nHow<\/th>\nExpected<\/th>\n<\/tr>\n<\/thead>\n
    Does the test send<\/td>\nUse the plugin’s test tool, to yourself<\/td>\nNo error<\/td>\n<\/tr>\n
    Does it reach the inbox<\/td>\nCheck the spam folder too<\/td>\nInbox<\/td>\n<\/tr>\n
    Is it really leaving via SMTP<\/td>\nView the message source, read the Received:<\/code> lines<\/td>\nYour server name appears<\/td>\n<\/tr>\n
    Is a wrong password rejected<\/strong><\/td>\nEnter a deliberately wrong password and test again<\/td>\nThe test must FAIL<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
    The fourth is the most important and the most often skipped. If a test with the wrong password still reports success, your WordPress SMTP settings are not in use \u2014 the plugin has quietly fallen back to mail()<\/code>. Restore the correct password afterwards.<\/p>\n
    Do not rely on the test tool alone. Try a real event as well: submit a contact form or request a password reset. A test that works while form emails do not<\/a> is a separate and common problem, usually caused by the form putting the visitor’s address in the sender field.<\/p>\n
    If it still does not work<\/h2>\n
    If the WordPress SMTP settings are saved and nothing has changed, work through these.<\/p>\n
    Connection timed out or refused.<\/strong> Your hosting provider may be blocking the outbound port. If 587 does not work, try 465. If neither does, ask your provider whether outbound SMTP is open. For a fuller diagnosis see the SMTP connect() failed guide<\/a>.<\/p>\n
    535 authentication error.<\/strong> The password is wrong, or an account password was used. Create an app password. On Microsoft 365 the SMTP AUTH setting also has to be enabled for the mailbox; in corporate tenants it is off by default.<\/p>\n
    Certificate error.<\/strong> The port and encryption do not match. You may have paired 465 with STARTTLS or 587 with SSL\/TLS. Do not use the option that disables verification; it hides the problem rather than solving it.<\/p>\n
    Mail sends but lands in spam.<\/strong> SMTP alone is not enough. Your domain also needs SPF and DKIM records<\/a>.<\/p>\n
    \n
    How AIOWS helps:<\/p>\n
    AIOWS SMTP Manager<\/h2>\n
    Entering the values above by hand is not hard, but it grows when you want OAuth on Gmail or Microsoft 365. That means creating a project in the Google Cloud Console, configuring the consent screen, generating credentials, defining a redirect URI and completing the authorisation flow. Fifteen steps, and again from scratch for every client.<\/p>\n
    EasyConnect in AIOWS SMTP Manager reduces it to one link: you pick your Google or Microsoft account, grant permission, and the connection is made. No console configuration, no copying keys, no redirect URI.<\/p>\n
    \n\"WordPress
    Each card shows host, port and encryption together; selecting one fills the fields.<\/figcaption><\/figure>\n
    The module carries thirteen provider presets: Gmail, Outlook and Office 365, Yahoo, Zoho, SendGrid, Mailgun, Amazon SES, Brevo, SparkPost, Postmark, Yandex, shared hosting, and a custom SMTP server for anything else. Selecting a card brings host, port and encryption together, so the pairing mistake in this article never occurs.<\/p>\n
    The shared hosting preset derives the host from your own site \u2014 it arrives as mail.yourdomain.com<\/code>. The Yandex card carries its two prerequisites on its face: the username is the part before the @, and an app password is mandatory.<\/p>\n
    The test tool checks each part of the configuration separately, and when a send fails it names the stage it failed at \u2014 DNS resolution, connection, TLS handshake or authentication. The server’s own reply line is shown too; credentials never are.<\/p>\n
    Its limits, stated plainly:<\/strong> the module cannot open a port your hosting provider has blocked, it cannot write your domain’s SPF or DKIM records into DNS for you, and it cannot change an SMTP AUTH setting that is off in your Microsoft 365 tenant. Those three need you or your provider.<\/p>\n
    Explore AIOWS SMTP Manager<\/a>Compare AIOWS plans<\/a><\/p>\n<\/section>\n
    FAQ<\/h2>\n
    Do I have to configure WordPress SMTP settings at all?<\/strong><\/p>\n
    WordPress’s own delivery path does not authenticate, so your messages either do not arrive or land in spam. SMTP is the standard way to get email delivered reliably.<\/p>\n
    Can I use my account password?<\/strong><\/p>\n
    Gmail, Microsoft 365 and Yandex will not accept it. You need an app password, and that requires two-step verification on the account.<\/p>\n
    Should I choose 587 or 465?<\/strong><\/p>\n
    Whichever your provider documents. Where both are supported, 587 is more common. What matters is pairing the port with the right encryption type.<\/p>\n
    How many emails can I send through Gmail?<\/strong><\/p>\n
    Personal Gmail accounts have a daily sending limit. Sites with high volume are better served by a transactional email provider.<\/p>\n
    I configured SMTP and it still lands in spam.<\/strong><\/p>\n
    SMTP gets the message delivered; it does not build reputation. Your domain needs SPF and DKIM records.<\/p>\n
    The test email arrives but form emails do not.<\/strong><\/p>\n
    The form plugin is putting the visitor’s address in the sender field, which conflicts with authentication. Fix the sender to an address on your own domain and put the visitor’s address in Reply-To.<\/p>\n
    Sources<\/h2>\n