Updates

The SMTP Step Most Send Mail As Tutorials Skip

Most guides to setting up a Gmail email alias stop at the moment you click “Next” in Settings. They show you how to add a name, type an address, and hit save, then declare victory. What they gloss over is the fork in the road that appears right after: Gmail asks whether you want to send through Gmail itself or through your own SMTP server. That single choice determines whether your alias works in five minutes or fails silently for a week, and it is the step where most broken configurations begin.

Here is the short version of why it matters. If you pick “Send through Gmail,” Google routes your outbound mail and the setup is nearly automatic, but the From address is limited to what Google will vouch for. If you pick “Send through your own SMTP server,” you are telling Gmail to hand your message to a third party, and that third party wants a host name, a port number, and credentials that are almost never your normal account password. Tutorials skip this because it requires knowledge that lives outside Gmail: the SMTP settings of your mail provider, an app password generated after enabling 2-Step Verification, and a clear idea of which port your provider actually accepts. Without those three pieces, the alias sits in an unverified state and every message you try to send bounces back with a generic error.

What follows is the practical sequence for the Send mail as setup, written for people who have already tried once and got stuck, or who want to get it right the first time. We will cover what the feature actually does, what to have on hand before you open Gmail settings Accounts and Import, how to add the alias address, how to choose between Gmail’s relay and your provider’s SMTP server, how Google’s confirmation email and verification code work, and how to test the From header once the alias is live. Keep in mind that Google has announced it will discontinue Send as for third-party addresses starting January 2027, so the setup you build now is worth understanding rather than copying blindly. The SMTP step is the one that decides whether your second Gmail address behaves like a real mailbox or like a decoration in a dropdown menu.

What “Send mail as” Actually Does and When You Need It

Send mail as is the Gmail setting that lets you put a different address in the From line while still sending through Google’s infrastructure. You type a message in the normal compose window, pick the alias from the From drop-down, and the recipient sees you@yourdomain.com instead of your gmail.com address. Replies come back to whichever address you choose in the same settings panel, so nothing has to be forwarded manually.

The confusion starts with the word “alias,” because Gmail uses it for two different things. A Gmail email alias is not a separate mailbox. Gmail offers plus aliases: append +anything to your username and mail still lands in the same inbox. So jane+newsletters@gmail.com and jane+shopping@gmail.com both deliver mail to jane@gmail.com. Dot aliases work the same way, since Gmail ignores periods in the local part. These are filters in disguise, useful for tracking who sold your address, but they never give you a new login or a new inbox.

A second Gmail address is a genuinely separate account with its own password, storage, and settings. That is the right tool when you want isolation, not relabeling. A second Google account provides a separate inbox, which matters if you are separating work from personal mail or handing a role-based address to a colleague. The trade-off is administrative overhead: two sign-ins, two sets of filters, two recovery paths.

Send mail as sits between those poles. It gives you a professional From address without a second inbox, and it is the mechanism behind most custom-domain setups. The common scenarios:

  • Custom domain on a personal account. You own example.com, your mail is hosted elsewhere or forwarded into Gmail, and you want outbound mail to carry the domain address.
  • Gmail plus aliases used as sender identities. Less common, but some people register jane+support@gmail.com as a send-as address so replies can be filtered into a dedicated label.
  • Shared or role inboxes. Addresses like orders@ or info@ that several people answer. Send mail as lets each person reply from the shared address while the underlying mail stays in one place.
  • Google Workspace alias addresses. Workspace allows 30 aliases per user, and admins can route a catch-all email domain into a single mailbox. Send mail as makes those addresses usable on the way out, not just the way in.

One deadline is worth knowing before you invest time here. Gmail will discontinue Send as for third-party addresses starting January 2027, so if your alias points at a non-Google mailbox, plan a migration path rather than building years of workflow on it. Google documents alias limits on its help pages, and AllMail publishes Gmail alias guides that track these changes as they land.

Before You Start: Prerequisites for Adding an Alias

Most failed Send mail as setups are not really Gmail failures. They are missing prerequisites: an inbox you cannot open, an admin who never granted the permission, or a Google account without 2-Step Verification. Five minutes of preparation saves an hour of debugging later.

Start with access to the destination mailbox. Gmail sends a verification email to the address you are adding, and someone has to open it and click the link. If the alias is a Gmail plus alias such as yourname+shop@gmail.com, the message lands in your own inbox, so you are already set. If it is a custom domain address like orders@yourdomain.com, you need either the mailbox password or control of the catch-all email forwarding rule that routes that address somewhere you can read. Confirm this before you touch Settings, because the verification email has a finite shelf life and a stalled setup leaves a half-configured alias behind.

Next, know which account type you are working in. A free Gmail account lets you add up to 99 Send mail as addresses, and you manage all of them yourself. A Google Workspace account is different: Google documents alias limits on its help pages, and Workspace allows 30 aliases per user, with some of them provisioned by the admin console rather than by you. If your organization restricts external address configuration, you will not see the option at all until an administrator enables it. Ask first. A two-line message to IT beats staring at a greyed-out button.

Then handle 2-Step Verification. If you plan to send through your own SMTP server, most providers no longer accept your regular account password. They require an app password, and Google only generates one after 2-Step Verification is active on the account. Turn it on under Security, create an app password labeled something recognizable like “Gmail send as,” and store it somewhere safe. You will paste it once during SMTP setup and rarely see it again. If your provider has moved to OAuth instead of app passwords, check its documentation now rather than mid-wizard.

Collect the SMTP details while you are at it, because the setup screen will demand them without warning. You need the outgoing server hostname, the port and encryption type (usually 465 with SSL or 587 with TLS), and the exact username the provider expects, which is often the full email address. Keep this in a note.

  • Mailbox access or forwarding control for the alias address
  • Knowledge of whether the account is free Gmail or Google Workspace
  • 2-Step Verification enabled and an app password generated
  • SMTP host, port, encryption, and username from the provider
  • Admin approval if Workspace policy restricts alias creation

One more thing worth deciding early: whether this alias is a long-term identity or a test. Changing your gmail.com address is allowed once every 12 months, so if you are experimenting, a plus alias costs nothing and can be deleted without consequence. A custom domain alias tied to a business identity deserves the extra ten minutes of preparation described above.

Adding Your Alias in Gmail Settings, Step by Step

Open Gmail on the web. The mobile apps do not expose the full Accounts and Import panel, so this is desktop work even if you only ever read mail on your phone. Click the gear icon at the top right and choose “See all settings,” then pick the Accounts and Import tab. On a Google Workspace account the tab may sit under “Accounts” depending on rollout, but the contents are the same: a “Send mail as” block, a “Check mail from other accounts” block, and a “Grant access to your account” block. You want the first one.

From the Settings Tab to the Send Mail As Screen

  1. In the “Send mail as” row, click “Add another email address.” A small dialog opens over the settings page.
  2. Enter the display name exactly as you want it to appear in recipients’ inboxes. This is what shows next to the address in Outlook, Apple Mail, and Gmail itself, so use a real name or a team name, not the raw address.
  3. Enter the email address you are adding. This is your alias address: a custom-domain address like hello@yourdomain.com, a Gmail plus alias such as yourname+orders@gmail.com, or a shared desk address.
  4. Leave “Treat as an alias” checked in most cases. It tells Gmail to route replies and to skip the extra envelope handling that some mailing lists and CRM tools mishandle. Uncheck it only if a specific tool on the receiving end rejects messages sent from an alias.
  5. Click “Next Step.”

That click is the fork in the road, and it is where most walkthroughs wave their hands. Gmail now asks you to choose between two radio buttons: “Send through Gmail” and “Send through yourdomain.com SMTP servers.” The first option is a one-click finish. Gmail sends the message from its own infrastructure with your alias in the From header, and recipients may see “on behalf of” or a “sent via gmail.com” notice depending on their client. The second option is the one that produces clean, authenticated mail from your own domain, and it is the one that demands real configuration: SMTP server hostname, port, username, and password.

Pick the SMTP option and the dialog expands into the fields that matter. For a Google Workspace alias, the host is smtp.gmail.com and the port is 465 with SSL or 587 with TLS. For a third-party mailbox, pull the host and port from that provider’s documentation, not from a forum post. The username is usually the full alias address. The password field is where people stall: if the account has 2-Step Verification on, your normal password will be rejected and you need a 16-character app password generated from the provider’s security settings.

Click “Add Account” and Gmail fires off a verification message. Nothing is active yet. The alias sits in the Send mail as list marked “Pending verification” until you complete the confirmation step covered next. If you close the tab at this point, the entry stays pending indefinitely, and messages you try to send from it will bounce back with a “You no longer have access” style error. Google documents the full field list and the 99-address cap for Send mail as on its help pages, so keep that reference open while you fill in the SMTP block.

Send Through Gmail vs. Send Through Your Own SMTP Server

Halfway through the Send mail as wizard, Gmail presents two radio buttons: “Send through Gmail (easier to set up)” or “Send through your domain’s SMTP servers (for advanced configuration)”. Most walkthroughs glide past this screen in one sentence, and this guide is no exception. That is a mistake, because the choice determines whether your alias keeps working, what recipients see in the message headers, and how much setup work lands on your desk today.

The first option is the fast lane. Gmail sends on behalf of your alias through Google’s own infrastructure. You supply a display name and the alias address, complete verification, and you are done. The catch is that messages carry a “Sent by gmail.com” or “on behalf of” note in some clients, and services that check SPF alignment will see Google’s servers, not your domain’s. For a Gmail plus alias or a personal address you control anyway, that is fine. For a business address on a custom domain, it looks amateurish to anyone who inspects headers.

The second option routes outbound mail through your provider’s SMTP server, which means Gmail is only the composer and the sending reputation belongs to your domain. This is the path that actually requires homework, and it is where tutorials go quiet. You need four values from your email host: the SMTP hostname, the port, and your login credentials. Ports 465 (SSL) and 587 (TLS) are the usual suspects; 25 is blocked by most providers and by Google itself.

The credential part trips up the most people. Google will not accept your normal mailbox password in most cases, especially if the provider enforces modern authentication. You need an app password generated by that provider, or in the case of a Google Workspace alias, an app password created inside your own Google account after 2-Step Verification is switched on. Typing your everyday login here produces an authentication error that says nothing useful, which is why so many setups stall at this exact field.

One more wrinkle worth knowing before you commit. Gmail has announced it will discontinue Send as for third-party addresses starting January 2027, so if your alias points at an external provider’s SMTP server, plan for a migration rather than a permanent arrangement. Google Workspace accounts, which allow 30 aliases per user, are the safer long-term home. Either way, take the SMTP fork seriously: get the host, port, and app password from your provider’s help pages first, paste them carefully, and treat the next verification step as the real finish line.

Completing SMTP Verification With Google’s Confirmation Email

Clicking “Add Account” does not finish the job. Gmail now sends a verification message to the address you just configured, and until you answer it, the alias sits in your settings as an unverified entry that cannot send anything. The message arrives from send-as-noreply@google.com with a subject line about a verification request, and it contains both a confirmation link and a numeric code. Either path works; the code exists for people who read mail in a client that mangles links.

Click the Link or Paste the Code, Then Confirm the Toggle

Open the destination mailbox and find the Google message. If you click the link, Gmail opens a confirmation page tied to your signed-in session and the alias flips to verified automatically. If you prefer the code, copy the digits, return to Settings > Accounts and Import > Send mail as, click “Verify” next to the pending address, and paste the code into the field. The alias shows “Verified” once it goes through.

One detail the wizard handles quietly: when you finish verification, Gmail asks whether the alias should be treated as an alias of your account or as a separate address. Choose “Treat as an alias” if you want replies to land in the same inbox and filters to apply normally. This setting is what makes a custom-domain address behave like a Gmail email alias rather than a detached mailbox.

A few practical notes from doing this repeatedly:

  • The verification email can take a minute or two. Give it that long before resending.
  • Check spam and any quarantine on the destination side. Corporate filters are suspicious of automated senders, and a caught verification email is the single most common reason people think setup failed.
  • The code and link both expire. If you come back the next day, click “Resend” and start the step again.
  • You need to be signed in to the Gmail account that owns the alias when you click the link, or the confirmation page will not know which account to update.
  • If you chose “Send through Gmail” rather than your own SMTP server, the flow is identical. Verification is about proving you control the address, not about the transport.

There is a limit worth knowing before you repeat this process. Google’s help pages document that Send mail as supports up to 99 addresses per account, so verification for each alias is a one-time cost rather than a recurring chore. Google Workspace admins can also pre-approve domain aliases from the admin console, which skips the inbox round trip entirely for addresses inside your own domain. If you are adding an address on a domain you administer, ask whether that route is available first; it saves the wait and the spam-folder hunt.

Once the alias reads “Verified,” the setup is complete on paper. The next step is proving it actually sends, which means a test message and a look at the From header.

Testing the Alias and Troubleshooting Common Failures

The alias is live once the confirmation step clears, but live does not mean correct. Send a test message to an address you control on a different provider (an Outlook or Yahoo mailbox works well), open it, and inspect the From header. You want the display name and the alias address to appear exactly as configured, not “on behalf of” your gmail.com address. If you see the gmail.com address in the header, the alias was added but the Send mail as entry was never confirmed, or the SMTP credentials were rejected silently.

Also check the message in the sent folder of the external mailbox to confirm it actually passed through the external SMTP server rather than Gmail’s own relay. A quick way is to compare the Received headers: a message sent through your own SMTP server will show that provider’s host near the top of the chain.

Diagnosing the Failures You Will Actually Hit

Wrong port or encryption. Gmail accepts SMTP on port 465 with SSL or port 587 with TLS. Mixing them up is the single most common reason the setup screen throws a connection error. Port 25 is blocked and will never work. Check your provider’s documentation for the exact host name too, since smtp.yourdomain.com and mail.yourdomain.com are not interchangeable.

Rejected app password. If the external provider enforces 2-Step Verification, your normal account password will fail authentication. Generate an app password in that provider’s security settings and paste it into the SMTP password field. Remove any spaces the provider displays in the grouped password. If the provider has revoked older app passwords, issue a fresh one.

Missing 2-Step Verification. Some providers only expose app passwords after 2-Step Verification is enabled on the account. If the app password menu does not exist, that is the reason. Turn on 2-Step Verification, wait a few minutes for the option to appear, then create the password.

Verification email in spam. The message from send-as-noreply@google.com sometimes lands in the spam or promotions tab of the destination mailbox. Search for “Gmail Confirmation” across all folders, including trash. If it never arrived, return to Settings, open the alias under Accounts and Import, and resend the verification. The link expires, so request a new one rather than hunting for an old message.

Alias missing from the From dropdown. An unconfirmed alias stays invisible when composing. Confirm it first. For Google Workspace accounts, an admin may also need to whitelist the address in the admin console before it appears for users.

One last note on timing: Gmail has announced it will discontinue Send as for third-party addresses starting January 2027, so if your workflow depends on a custom-domain alias through an external SMTP server, plan a migration path to Google Workspace aliases or a separate account before that date.

Once the alias is live, do not leave it untested. Send one message to an address you control on a different provider, open it, and inspect the From header in the raw source. Gmail will show the alias in the From line while the Sender line may still reference your gmail.com address, and some strict mail gateways flag that mismatch. If recipients report the message landing in spam, check your domain’s SPF and DKIM records before you blame Gmail. A custom domain that sends through smtp.gmail.com but has no SPF entry authorizing Google will fail authentication on the receiving end, and no amount of retrying the Send mail as wizard fixes that.

The practical next step depends on what you actually need. If you only want to sort incoming mail, skip Send mail as entirely and use Gmail plus aliases: append +newsletter or +orders to your existing address, then build Gmail filters on those plus alias addresses so each stream lands in its own label. Plus aliases deliver mail to the same inbox, cost nothing, and take about two minutes to set up. If you need to reply from a branded address, finish the SMTP verification, then test with a real send and a raw-header check. If you need a genuinely separate mailbox rather than an alias address, a second Google account provides a separate inbox and avoids the whole forwarding chain. Keep the constraints in mind as you scale: Send mail as supports up to 99 addresses per account, Google Workspace allows 30 aliases per user, and changing your gmail.com username is allowed once every 12 months. Gmail will discontinue Send as for third-party addresses starting January 2027, so if your workflow depends on sending through an outside provider, plan the migration now rather than the week it stops working. Document the SMTP host, port, and app password somewhere your team can find them, and note which alias maps to which label. Guides such as the ones AllMail publishes on Gmail alias setups are worth bookmarking for the day a verification email goes missing or a password gets revoked.