Six emails I sent never arrived. Three of them were replies to actual clients. There was no bounce, no error, no warning of any kind — just a Sent folder that looked completely normal, with every message sitting in it where a sent message is supposed to sit. It took three days to find out, and by then the damage was already done.
That is how I learned the one thing this whole post is really about: the Sent folder means "handed over," not "delivered." Everything else here is the setup that got me a professional address for free, and the single step that quietly ruins it if you skip it.
Here is the short version, and you can stop reading after it if you just want the answer. You can run you@yourbusiness.com for zero dollars a month, entirely inside the Gmail you already use. One free service catches incoming mail and forwards it to you; a second free service signs the mail you send so it doesn't land in spam. There is no mailbox anywhere. The only real cost is the domain, about $12 a year.
Photo by Jan van der Wolf via Pexels.
I'll be honest about why I bothered. I already run two studios' worth of small operational plumbing, and I have a low tolerance for paying a monthly fee for something that turns out to be four lines of configuration. I also wrote here already about rebuilding our studio website after a renewal price quietly climbed on me. Same instinct, smaller bill. The difference this time is that I got it wrong first, and the way it went wrong is more useful than the way it went right.
Table of Contents
Why there's no mailbox in this setup
A professional email address does not require a mailbox. Email forwarding is a service that catches mail sent to an address on your domain and drops it straight into an inbox you already own — no second account, no second password, nothing extra to check. Your domain becomes a label on mail rather than a place mail is stored.
That's the part people don't expect. When someone emails you at your business address, a forwarding service receives it and passes it into your normal Gmail. When you reply, Gmail hands the message to a sending service, which stamps it as genuinely yours and puts it on the wire. Two free services stand in for one paid mailbox, and Gmail is the only thing you ever open.
The second half of that is the half everyone underestimates. Receiving mail is easy. Sending mail that actually gets accepted is the hard problem, because every receiving mail server on earth now assumes a stranger claiming to be your domain is a spammer until proven otherwise. Domain authentication is the proof: a short set of records in your domain settings that lets the sending service sign your mail so the far end can verify it really came from you. Skip it and your mail goes to spam, or nowhere at all.
The setup, in four steps
The whole thing takes about thirty minutes, most of which is waiting for domain settings to take effect. You need two things before you start: a domain you own, and the login for wherever you bought it, because you'll be pasting a few records into its DNS settings. If you have those, the rest is typing.
One: catch the incoming mail. I used ImprovMX, which is free for one domain forwarding to one address. You enter your domain and the Gmail address you want mail sent to, and it hands you three records to add to your DNS. Two of them tell the world where your mail should go; the third is an SPF record, which is a public note from your domain saying who's allowed to send on its behalf.
| Type | Name | Value | Priority |
|---|---|---|---|
| MX | @ | mx1.improvmx.com | 10 |
| MX | @ | mx2.improvmx.com | 20 |
| TXT | @ | v=spf1 include:spf.improvmx.com ~all | — |
Wait fifteen to thirty minutes, then email your new address from your phone. If it lands in Gmail, incoming is finished and you never have to think about it again.
Two: set up sending. This is the step that goes wrong, so give it the attention the first step didn't need. I used Brevo, also free. Make an account, go to the domains section, add your domain, and it gives you one TXT record and two CNAME records to paste into DNS. The CNAMEs are your DKIM keys, which is the signing mechanism that proves the mail is yours. Then click Authenticate, and refresh until the domain is actually marked Authenticated. Not pending. Not "records detected." Authenticated.
Three: connect it to Gmail. In Gmail, go to Settings, then Accounts and Import, then "Send mail as," then "Add another email address." Enter your name and your new address, then the SMTP details from Brevo: server smtp-relay.brevo.com, port 587, your Brevo login and SMTP key, secured with TLS. Gmail sends a confirmation code to your new address, which the forwarding service you set up in step one delivers straight to your inbox. Paste it in. If you want to send from the new address by default, there's a "make default" link on that same screen.
Four: prove it works. Send a test from the new address to an inbox that is not your own Gmail, and then go look at Brevo's delivery logs and confirm that specific message says Delivered. Better still, text a friend and ask them to tell you it arrived. If you want a second opinion on whether you'll land in spam, send one message to the address at mail-tester.com and aim for 8 out of 10 or better.
Do not connect Gmail until Brevo says Authenticated. If you wire up the Gmail side first, every message you send will look completely successful on your end and get rejected on the way out. That's not a hypothetical — it's step two of this post, and it's the whole reason I wrote it.
The step that fails silently
My domain hadn't finished authenticating in Brevo when I connected Gmail, and nothing in the chain was designed to tell me. Gmail accepted every message and filed it neatly in Sent. Brevo then refused all of them at the door. Six emails vanished into the gap between those two facts, three of them real replies to real clients.
Photo by Jan van der Wolf via Pexels.
What makes this failure mode nasty is that it looks exactly like success. A bounce message is a gift; it's the system doing you the courtesy of admitting it failed. Here there was no bounce, because from Gmail's point of view nothing failed — it handed the message off, which is all Gmail ever promises to do. The rejection happened one hop later, in a log I hadn't thought to open.
So the habit worth keeping is small and permanent. Trust the sending service's logs, not your Sent folder. Never send anything real until the domain shows as authenticated. And re-run that delivery test after any change to your domain or DNS, including changes you're sure are unrelated, because "unrelated" is doing a lot of work in that sentence.
Keeping it alive, and when to quit it
Three things keep this setup healthy, and none of them take ongoing effort. Turn on auto-renew at your registrar, because if the domain expires your email stops the same day, in both directions, with no warning. Know your ceiling: Brevo's free tier sends 300 emails a day, which is generous for client correspondence and not intended for marketing blasts or cold outreach. And remember that nothing is stored at your domain — every message you own lives in Gmail, so backing up Gmail is backing up your business mail.
The honest limitation is that this is a one-person arrangement. It's tied to a single Gmail account, which means no shared inbox, no second person answering the same address, and no clean handoff if someone else needs to cover your mail. The moment any of those becomes real, stop being clever and buy a mailbox. Zoho Mail runs about a dollar per person per month and Google Workspace about seven, and either one solves the exact problem this setup can't.
I'd also draw a hard line between operational mail and outreach. This is the plumbing for replying to clients, sending quotes, and answering the address on your website. It is not a cold-email rig, and using it as one is a good way to poison the reputation of a domain you actually need for real correspondence.
What this has to do with your event
Fair question, since we shoot conferences rather than configure mail servers. The connection is that the failure in this story is the failure I spend most of my working life trying to prevent: something that looks finished, reports itself as finished, and isn't. A Sent folder full of mail nobody got is the same shape of problem as footage that exists on exactly one card, or a gallery that's technically delivered but sitting behind a link nobody can open.
When we cover an event, the confirmation that matters isn't "we shot it." It's cards offloaded and verified before the gear goes in the case, files in two places before anyone goes home, and a delivery you've actually opened. That's the same instinct as opening the delivery log instead of trusting the Sent folder. Verify at the point where the failure would be invisible, not at the point where it's convenient.
It's also why we price in fixed packages and hand over files you own outright. Nobody should have to check whether the thing they paid for quietly didn't happen. And the address in the footer of this page? It runs on exactly the setup above. It's authenticated now.
Planning an event or a content push?
No sales pitch, no mystery pricing. Tell me what you're working on and I'll send back honest options — fixed packages, fast delivery, content you actually own.
Tell Me What You NeedFrequently Asked Questions
Can you really get a professional email address for free?
Yes, if you already own a domain and already use Gmail. A free forwarding service catches mail sent to your domain and drops it into Gmail, and a free sending service signs your outgoing mail so it passes authentication. The only real cost is the domain itself, roughly twelve dollars a year.
Do I need to buy a mailbox or a Google Workspace account?
Not for a one-person business. There is no mailbox in this setup at all. Incoming mail is forwarded into the Gmail account you already have, and outgoing mail is sent from that same Gmail using your domain address. You buy a real mailbox when you need a second person on the domain.
Why do my emails show up in Sent but never arrive?
Because Gmail's Sent folder records that Gmail handed the message to your sending service, not that anyone received it. If the sending service hasn't finished authenticating your domain, it accepts the handoff and then rejects the message. Nothing bounces back, so the failure is invisible until someone tells you.
How many emails can you send on a free plan like this?
Brevo's free tier allows 300 emails per day, which is far more than normal client correspondence uses. It isn't built for marketing blasts or newsletters, and it shouldn't be used for cold outreach. For replying to clients, sending quotes, and everyday business mail, the limit never comes up.
When should you stop using a free forwarding setup?
The moment you need a shared inbox, a second person on the domain, or mail that isn't tied to one personal Gmail account. At that point buy a real mailbox. Zoho Mail runs about a dollar per person per month and Google Workspace about seven, and both remove the ceiling this setup has.
How do you check that the setup is actually working?
Send a test message from the new address to an inbox that isn't your own Gmail, then open your sending service's delivery logs and confirm that specific message is marked Delivered. Better still, text someone and ask them to confirm it arrived. Your own Sent folder is not evidence of delivery.