Why Your Store Email Should Come From Your Own Domain

The email your customer sees is part of your brand

A shopper just paid you. The next thing they experience isn't your storefront — it's the order confirmation in their inbox. If that email arrives from a generic platform address, two things happen, and neither helps you.

First, it looks borrowed. A confirmation from [email protected] for a purchase at your shop reads as slightly off, the way a receipt on the wrong letterhead does. Second, and more expensively, it's more likely to land in spam. Receiving mail servers trust messages that are cryptographically tied to the domain they claim to come from. A generic sender for your store's mail is a weaker signal — and weak signals get filtered.

Sending from [email protected] fixes both. The email matches the shop, and — when it's signed by your domain — it clears the checks that inbox providers run before deciding where to put it.

What "signed by your domain" actually means

Three DNS records do the heavy lifting for deliverability. You don't have to be an email engineer to publish them, but it helps to know what each one tells a receiving server.

• SPF says "these servers are allowed to send mail for my domain." It authorizes the sending mail server so a receiver knows the message isn't spoofed.
• DKIM attaches a cryptographic signature to every message, tied to a key published in your domain's DNS. The receiver re-checks the signature; if it validates, the message provably came from your domain and wasn't tampered with in transit.
• DMARC states your policy — what a receiver should do with mail from your domain that fails those checks.

Together they answer the question every spam filter asks: is this really from who it says it's from? When the answer is a confident yes, your confirmations, password resets, and shipping updates go to the inbox.

How it comes together on BestWebby

You don't set up a mail server. When you connect and verify a custom domain, email hosting for that domain is provisioned for you: a signing key is generated, a [email protected] mailbox is created, and the exact DNS records to publish are shown in Settings → Email.

Your part is to publish four records at your DNS provider:

• An MX record, so mail addressed to your domain reaches the server.
• SPF, DKIM, and DMARC records, so outbound mail is authorized and signed.

Until you've published them, your store email keeps sending from the platform address — so nothing breaks while you finish the DNS side. Once the records are live, your store's notifications send from [email protected], signed by your domain. The switch is that clean: no downtime, no risk of a broken confirmation email during setup.

Beyond confirmations: your own mailboxes

The support@ address that carries your store's automated mail is set up automatically. You can also create additional mailboxes — info@, sales@, or whatever fits how you work — on any domain whose email hosting is active. Each one is a real mailbox you can put in a business card or a contact page.

A few practical notes worth knowing up front, so nothing surprises you:

• Save the password when you create a mailbox. It's shown once and isn't stored, so it can't be recovered. If you lose it, delete the mailbox and recreate it.
• These mailboxes use POP3, not IMAP. Point your mail client at mail.bestwebby.com — incoming on port 995 (SSL), outgoing on port 587 (STARTTLS) — using the full address as the username.
• Mail is kept on the server for 48 hours, then removed. The server relays your mail; it isn't long-term storage. Connect a POP3 client, keep it running so it pulls new mail down, and leave "delete from server after download" on so your own client becomes the permanent home for your messages. Check it at least every couple of days and nothing gets lost.

That last point matters most: the 48-hour window is deliberate, and the fix is simply to have a client downloading your mail. Set it up once and it takes care of itself.

The trust dividend

Branded email isn't a cosmetic touch. It's the difference between a confirmation that reassures a customer and one that makes them second-guess whether the order went through — and the difference between a shipping update in the inbox and one buried in spam that triggers a "where's my order?" support ticket a week later.

The setup is a one-time afternoon: connect your domain, publish the records, and point a mail client at any extra mailboxes you create. After that, every message your store sends is wearing your name, signed by your domain, and headed for the inbox.

Where to start

Connect your domain in Settings → Domains, wait for email hosting to go active, then open Settings → Email to copy your MX, SPF, DKIM, and DMARC records. Publish them at your DNS provider, give DNS a little time, and check that your next order confirmation arrives from [email protected]. From there, add any extra mailboxes you need and wire them into a POP3 client — with retention in mind — and you're done.