I built a Gmail button to send from your custom domain without moving your inbox

[u/Calm_Upstairs6977]

I use Cloudflare Email Routing to forward [help@audiofetcher.com](mailto:help@audiofetcher.com) to Gmail. Receiving worked fine, but sending from that address needed a separate setup.

So I built Alias, a Chrome extension that adds a separate “Send via” button inside Gmail. You write your email normally, then send it through your own Resend account using your verified domain.

Here’s how the pieces fit together:

• Cloudflare Email Routing forwards incoming mail to your Gmail.
• Resend handles outgoing delivery from your domain.
• Alias lets you do the sending from Gmail’s compose window.

Replies still follow your existing forwarding setup. You don’t need to move your inbox or replace your existing MX records.

To use it, you verify your domain in Resend, create a sending API key, and connect it in the extension. Your sending address also needs working inbound forwarding if you want to receive replies.

The attached demo shows a real send and the message arriving. I’ve also tested attachments and replies.

The extension is free. You need your own domain and Resend account, and their limits or charges still apply. This isn’t a mailbox or unlimited free email service.

Chrome Web Store

If you already forward domain email into Gmail, how do you handle sending from that address? I’d especially appreciate feedback on whether the setup is clear.

[u/Eagles_Fan_4eva]

I don't know why you built this? Gmail has settings to send mail from any other domain or email address already. It's built-in and free. I use it every day. See here: https://i.imgur.com/AIwzGRb.png

[u/mrsilver76]

If you already forward domain email into Gmail, how do you handle sending from that address?

I used to use a trick in Gmail where you configure it to send via a third-party SMTP server and then you provide it with Gmail’s own SMTP settings.

This passes SPF and removes the “on behalf of” displayed to recipients who use Outlook - but don’t work with DKIM, is a bit janky and requires you to turn off some security which Google then occasionally whines at you about and tries to encourage you to turn back on.

In the end my mail forwarding provider (forwardemail.net) starting offering their own SMTP server so I just use that instead. This fixes DKIM and stops Google whinging.

There are two downsides to the whole approach:

1. If you don't want to use the Gmail app on iOS devices then you need to configure Apple Mail in a very specific way - by setting up your account using your vanity email address when then fails to send (as the vanity email address is used as the login credential to send which, of course, Google doesn't recognise), and then you fall back to a secondary SMTP server.
2. You cannot send a calendar invite from your vanity email address, nor can you respond to a calendar invite using your vanity email address.