Can I send email from my own domain using my existing Gmail?

Why sending is a separate step

Receiving mail on your domain is a change to your domain: records say where mail is delivered, and everything that writes to you follows them. It applies to the whole world at once and needs nothing from your mail app.

Sending is different. When you write a message, the app you are writing in decides which server carries it and which address it claims to be from. Your domain has no say in that — it can only publish which servers are permitted to send on its behalf, which is what SPF and DKIM do. So the sending identity has to be configured inside each app you write from.

Your domain controls where mail arrives. Your mail app controls what your outgoing mail claims to be. That is why the two halves are configured in two different places.

Adding your domain as a sending address

The wording differs between apps — “Send mail as”, “Add another address”, “Aliases”, “Add account” — but the sequence is the same everywhere, and so are the details you need.

1. 1

   Collect the outgoing server details first

   The server hostname, the port, your full address as the username, and the password issued for it. Have them in front of you — the dialogue times out and restarts if you go looking mid-way.

2. 2

   Add the address in your mail app's accounts settings

   Enter [email protected] and the display name recipients should see. The display name is what appears in their inbox list, so write it the way you want to be read.

3. 3

   Enter the outgoing server, not “alias of this account”

   This is the step that decides everything. Choosing the alias option skips the server details and sends through your existing provider, which is what produces the via note recipients can see.

4. 4

   Confirm the address

   The app sends a confirmation to the address you just added. Because that address routes to the inbox you are already in, it usually arrives in the same place seconds later.

5. 5

   Make it the default for replies

   Set replies to go out from the address the message was sent to. This is what makes the whole thing automatic — you never have to remember to switch sender.

6. 6

   Send one message to a different provider and read it there

   Not to yourself at the same provider. Open it in another account and look at the sender exactly as a customer would.

The “via” note, and how to remove it

The most common complaint after setting this up is that recipients see something like “from [email protected] via gmail.com”. It is a small piece of text, and it undoes most of the point of the exercise: it announces that the address is a front for another account.

It appears when the message claims to be from your domain but was actually handed to the internet by a different provider's servers. The receiving app notices the mismatch and discloses it — correctly, because that mismatch is also what a forgery looks like.

The fix is the step above: configure the outgoing server rather than accepting the alias option. Once messages leave through a server your domain has authorised, there is no mismatch, nothing to disclose, and the note disappears.

When it will not connect

Setup failures here are few and they repeat. Work through them in this order.

• The username is not your local part. It is the full address, [email protected], not you. This is the most frequent single cause.
• The password was mistyped or has expired. Passwords for sending addresses are long and are shown once. If you no longer have it, issue a new one rather than guessing — rotating takes seconds and guessing can lock the address temporarily.
• The port or encryption setting is wrong. Use exactly the values you were given. Where an app offers a choice, choose the secure option rather than the one it defaults to.
• Your network blocks outgoing mail ports. Common on hotel, café and some corporate networks. Try the same setup on a phone using mobile data — if it works there, the network was the problem and nothing is wrong with your settings.
• The address is not verified for sending yet. If the domain's records were published in the last hour, give it time; sending is enabled after verification completes, not when the records are pasted.

How to check it is really right

1. 1

   Send to an account at a different provider

   Sending to yourself at the same provider proves almost nothing, because the message never leaves the building.

2. 2

   Look at the sender line as a recipient sees it

   The display name and address should be yours, with no “via” and no second address in brackets.

3. 3

   Reply to that message and check the reply goes to your domain

   If a reply lands anywhere other than your domain address, the reply-to setting is wrong and conversations will drift back to the personal address over time.

4. 4

   Check the authentication result

   Most mail apps can show the original message details, which report whether the checks passed. Passing here is the objective proof that the setup is complete.

A guided check that sends a real message from the app you configured and reports what the receiving side actually saw is worth using if your provider offers one — it is the difference between a screen saying the records look right and evidence that a real message passed every check.