Gmail Send As Alias allows you to send emails from a different email address while still using your primary Gmail account. This feature lets you appear to send from a personal, business, or alternate email without switching accounts.
When you enable a Send As alias, Gmail uses your primary account's SMTP server to deliver messages from the alias. The recipient sees the sender as the alias address, but replies go to your inbox. This is useful for managing multiple identities from one interface.
For example, if your primary email is [email protected], you can set up [email protected] as a Send As alias. You'll see outgoing messages labeled as sent from [email protected], but replies land in your [email protected] inbox.
Gmail sends emails through its secure SMTP servers. When you select a Send As alias, Gmail adds a special header to the message: From: shows the alias, but the actual sending server remains your primary account's domain.
The system verifies ownership of the alias address before allowing it. You must confirm the alias via a verification email sent to the address you're adding. This prevents spoofing and ensures only authorized users can send from a given email.
Once verified, the alias appears in the "From" dropdown when composing a new message. You can choose which alias to use per email, and Gmail remembers your preference across devices.
Send As aliases work with both personal and business email addresses. You can add any email address that belongs to you-even if it's hosted on a different provider-but the domain must allow incoming mail and have proper DNS records.
| Type | Domain Requirement | Verification Method | Use Case |
|---|---|---|---|
| Personal Gmail | None (same Google account) | Email confirmation | Using a nickname or secondary identity |
| Custom Domain (e.g., @yourcompany.com) | DNS MX, SPF, DKIM records | Email or manual DNS check | Business branding, team coordination |
| Third-party Email (e.g., Yahoo, Outlook) | IMAP access and POP enabled | Email confirmation | Legacy email reuse, temporary alias |
Google requires valid SPF and DKIM records for custom domains. Without them, emails may be marked as spam or rejected. According to Google's documentation, misconfigured DNS settings are the most common cause of failed delivery when using Send As aliases.
A non-obvious requirement: Gmail will not let you use an alias if the address has previously been used as a "Send From" address in another Google account. This prevents conflicts and maintains account integrity.
Users often report that Gmail won't send from an alias after setup. The most frequent cause is missing or incorrect SPF/DKIM records. For example, a company using @acme.com as an alias must publish a valid SPF record like v=spf1 include:_spf.google.com ~all.
If you see the error "The email address you entered is not valid," double-check spelling and ensure the domain accepts inbound mail. Try sending a test email to yourself from the alias to verify delivery.
Another issue: replies don't arrive in your inbox. This happens when the alias is not properly configured in the receiving email client. Ensure your default email app (like Apple Mail or Outlook) is set to check the correct inbox for replies.
I once set up a Send As alias for a nonprofit's newsletter using a custom domain. After confirming the SPF record, I still got bouncebacks. The fix was adding a DMARC policy. Google recommends setting p=quarantine or p=reject to prevent spoofing attempts.
Gmail Send As Alias is not the same as forwarding. Forwarding copies incoming messages to another address. Send As lets you send from a different address, but the original inbox remains the sender's.
It's also not the same as creating a new Gmail account. A new account has its own storage, settings, and login. An alias shares everything except the visible sender address.
Some users think they can send from a Gmail address they don't own. That's impossible. You must have access to the inbox and be able to receive a verification email. Google blocks unauthorized alias creation to prevent abuse.
To do this, your app must authenticate with OAuth 2.0 and request the https://www.googleapis.com/auth/gmail.send scope. When calling the messages.send endpoint, include the from field in the message headers.
For example, a Python script using the Google Client Library can send an email from [email protected] like this:
message = create_message('[email protected]', '[email protected]', 'Subject', 'Body')
send_message(service, 'me', message)
This method bypasses the web interface and is ideal for automated workflows like appointment reminders or status updates.
When using the API, ensure the alias is verified in the Gmail web interface first. The API won't accept unverified addresses, even if DNS records are correct.
Gmail Send As Alias enables you to send emails from different addresses while maintaining control from your primary account. It's useful for professionals managing multiple roles, nonprofits handling outreach, or teams coordinating under shared branding.
For automated systems, the Gmail API supports Send As aliases with proper authentication. Always test with a small group before deploying at scale.