Two admin requests land in the same support queue and get the same answer: “I set up the alias and it still is not working.” In both cases the configuration was done in Gmail settings, and in both cases the part that actually creates an alias was never touched. The confusion is structural, not a knowledge gap. Forwarding lives in the user’s Gmail settings, under Forwarding and POP/IMAP, while aliases live in the Google Workspace Admin console. Different screens, different permissions, different behavior when mail arrives. Once you separate those two control planes in your head, the troubleshooting gets much faster.

Forwarding Is a User Setting With a Confirmation Handshake

Forwarding in Gmail is configured by the mailbox owner. Open Gmail, click the gear icon, choose See all settings, then the Forwarding and POP/IMAP tab. Add a forwarding address, and Google sends a verification email to that destination. The recipient has to click the confirmation link or paste the code before the forward activates. This is deliberate: it stops someone from silently routing your mail to an address you do not control.

The verification step trips people up because it looks like nothing happened. Until the destination confirms, Gmail shows the address as pending, and no mail moves. If the destination is a corporate mailbox with aggressive spam filtering, the verification email from Google can land in quarantine. Check the destination’s quarantine before you assume the setting failed.

Forwarding also has a scope choice that matters more than most admins realize. You can forward only new mail or also forward existing messages, and you can choose whether to keep a copy in the inbox. For a departing employee whose mail needs to reach a manager, keep the copy so the account stays auditable. For a role-based address that several people monitor, forward without a copy to avoid duplicate replies.

Where Forwarding Fits Alongside POP and IMAP

The Forwarding and POP/IMAP tab also controls POP and IMAP access, which is why it can feel like a grab bag. Those settings are about how mail leaves the mailbox through a client, not about where mail is delivered. Turning on IMAP does not affect forwarding, and disabling POP does not break an active forward. Treat them as three independent switches on one screen.

If you need every message from a domain to land somewhere specific, forwarding is the wrong tool. Forwarding is per-mailbox. A catch-all email pattern that catches anything addressed to a domain is configured in the Admin console under Gmail routing, and it behaves differently from a forward. Mixing the two up is the second most common source of “the forward is broken” tickets.

Aliases Live in the Admin Console, Not in Gmail Settings

An alias is an additional address that delivers mail to the same inbox as the primary account. In Google Workspace, you add aliases in the Admin console by opening the user’s profile and adding addresses under the alias section. Google Workspace allows 30 aliases per user. Those aliases receive mail into the user’s existing mailbox; there is no separate inbox, no separate login, and no separate password. The user signs in as the primary address and sees everything.

This is the control plane distinction that causes most confusion. An admin who wants john.smith@gmail.com to also receive mail sent to sales@ goes to Gmail settings looking for an alias field and finds forwarding instead. They set up a forward to the same address, which does nothing useful, and conclude the alias feature is broken. It was never configured, because the alias field is in the Admin console, not in Gmail.

Aliases also have a sending side. To reply from an alias, the user needs a Send mail as entry, which is configured under Gmail settings, Accounts and Import. Google supports up to 99 send-as addresses per account. That means a single mailbox can receive on 30 aliases and send as up to 99 addresses, which covers most departmental use cases without provisioning a second account.

Setting Up Send mail as for an Alias or External Address

Go to Gmail settings, Accounts and Import, then Send mail as, and click Add another email address. If you want to create email alias Gmail accounts for an internal Workspace alias, the address is already verified and the entry activates immediately. For an external address, such as a Yahoo or Outlook mailbox, Google sends a verification email with a code, and you also need the SMTP server details of that provider. That is where the send-as-noreply@google.com message originates: it is the verification handshake, not spam.

Google will discontinue Send as for third-party addresses starting January 2027, so plan external send-as migrations before then. Internal Workspace aliases are unaffected by that change. If your team relies on sending as a personal Yahoo address from inside Gmail, start moving that workflow to a proper Workspace alias or a delegated mailbox now rather than waiting for the cutoff.

Plus Aliases and Dot Tricks Work Without Any Admin Setup

Gmail plus aliases need no configuration at all. Any address of the form janedoe+newsletter@gmail.com delivers mail to the same inbox as janedoe@gmail.com. The plus sign and everything after it are ignored for routing but preserved in the To field, which makes them useful for filtering. Sign up for a vendor with a plus alias, and if that vendor leaks your address, you know exactly which alias was sold.

Gmail filters can be created on plus alias addresses, so mail to janedoe+shopping@gmail.com can skip the inbox and get a label automatically. The filter matches on the To field, which still contains the full plus address. This is the cheapest segmentation available in Gmail and it requires zero admin involvement. For consumer accounts and for Workspace users who just want inbox hygiene, it is the first tool to reach for.

Dot aliases work the same way on gmail.com addresses: john.smith@gmail.com and johnsmith@gmail.com are the same mailbox. Google ignores dots in the local part. This only applies to gmail.com, not to Workspace domains, where dots are significant. Do not build a filtering scheme on dots for a Workspace account; it will not behave the way you expect.

Changing your gmail.com address is allowed once every 12 months, which matters if a plus alias scheme has outgrown its usefulness. You cannot change a Workspace primary address the same way. For Workspace, you rename the user, and the old address becomes an alias automatically so mail keeps flowing. That automatic alias is worth knowing about because it explains why a renamed user still receives mail addressed to their old name.

Diagnosing an Alias That Appears Broken

When someone reports that an alias is not working, check three things in order. First, confirm the alias exists in the Admin console under the user’s profile. If it is not there, nothing else matters. Second, send a test message from an external account, not from another address on the same domain, because internal delivery can mask routing problems. Third, check whether the sender received a bounce or whether the message was silently accepted and filed somewhere unexpected by a filter.

If the alias exists and mail still does not arrive, look at Gmail routing rules in the Admin console. A routing rule that rewrites or rejects certain recipients will override an alias. Default routing settings can also send mail to a different destination before it reaches the user’s mailbox. These rules sit above the alias in the delivery chain, so an alias that looks fine can still fail because a routing rule intercepted the message.

The reverse mistake happens too. An admin sets up a second Google account thinking it will function as an alias. A second Google account provides a separate inbox, separate storage, and separate login credentials. It does not deliver to the first account. If the goal is one inbox receiving several addresses, a second account is the wrong answer, and it doubles the management overhead.

For consumer Gmail users who want a second Gmail address without a second login, the plus alias is the only option that behaves like an alias. There is no alias field in consumer Gmail settings. The features that exist are forwarding, send-as, and plus addressing, and each covers a different need. AllMail publishes Gmail alias guides that walk through these consumer cases if you need a reference to hand to a non-admin user.

Google documents alias limits on its help pages, including the 30-alias ceiling for Workspace and the 99 send-as ceiling. Those numbers are worth memorizing because they define when you need to provision a new user instead of stacking more aliases on an existing one. A user with 30 aliases receiving high-volume mail is a candidate for a shared mailbox or a dedicated account, not another alias.

A Practical Sequence for Setting Both Up Correctly

Start with the destination. If mail should land in an existing mailbox under a new address, create the alias in the Admin console first. If mail should leave the mailbox and arrive somewhere else, set up forwarding in Gmail settings and complete the verification from the destination. Do not substitute one for the other, and do not assume that setting one configures the other.

After the alias exists, add the send-as entry so replies come from the right address. For internal aliases this takes seconds. For external addresses, gather the SMTP server details before you start, and remember the January 2027 cutoff for third-party send-as. Then build filters on plus aliases for the mail that should be segmented, and test from an external sender to confirm the whole chain works.

Write down which control plane each piece lives in and keep that note with your onboarding checklist. Forwarding and POP/IMAP is the user’s screen. Aliases and routing are the admin’s screen. Send mail as is back on the user’s screen, under Accounts and Import. When a report comes in that something is broken, the note tells you which screen to open first, and that alone resolves most of these tickets before anyone starts changing settings.