Skip to main content

Set Up Your Email Sender, Verify Your Domain, and Add BIMI

Written by Harneet Kaur

Overview

Your email sender is the address AfterShip uses to send your notification emails to shoppers. Learn how to set up your email sender, verify your domain, and add BIMI using AfterShip. This guide walks you through adding a sender address, choosing a default sender, adding DNS records, verifying your domain, and showing your logo in the inbox. Once your domain is verified, your notifications are far more likely to reach the inbox instead of spam.

Before You Begin

Requirements

  • An email address on a domain you own, such as [email protected]

  • Access to that mailbox, so you can retrieve a confirmation code

  • Access to your domain's DNS settings, or contact with the person who manages them

Limitations

  • You can't add addresses at Yahoo or AOL, because these providers reject mail that a third party sends from their domains

  • You can't verify addresses at free providers such as Gmail, Hotmail, Yahoo, and AOL, because AfterShip blocks them to prevent email scams

  • You can't set up BIMI in AfterShip; you publish it in your own DNS and host the logo on your own web server

Step 1: Add a Sender Address

Add the address AfterShip sends your notifications from, then confirm you own it. Ownership confirmation proves the mailbox is yours, and you complete it in the admin.

  1. Go to Settings > Email.

  2. Click Add email.

  3. Enter the address you want to send notifications from.

  4. (Optional) Enter a Sender name, such as your brand name.

  5. Enter the confirmation code that AfterShip sends to that address.

The sender name is the name shoppers see in their inbox. If you leave it blank, shoppers see only the email address. You can edit or clear the sender name at any time, and changing it doesn't affect verification.

AfterShip then adds the sender. If you already verified its domain, the sender is ready to use right away. Otherwise, the sender waits for domain verification in Step 4.

Use your own domain

Use an address on a domain you own, such as [email protected]. AfterShip handles public mailbox providers in one of two ways:

Provider type

Examples

What happens

Not permitted

Yahoo, AOL

These providers reject mail that a third party sends from their domains. You can't add the address.

Permitted with a warning

Gmail, Outlook, iCloud, and similar

You can add the address, but deliverability and brand trust suffer noticeably. AfterShip shows a warning.

Only business domains can be verified. AfterShip shows addresses at free providers, such as Gmail, Hotmail, Yahoo, and AOL, as Verification unsupported to prevent email scams.

Note: If you can only use a free provider address for now, move to your own domain as soon as you can.

Step 2: Choose a Default Sender

Set a default sender so you can change your sending address across every notification at once.

  1. Go to Settings > Email.

  2. Mark the sender you want to use as the default.

Any email template set to use default sender sends from whichever address currently holds the default marker. When you change the default, every template that follows it changes too. Templates locked to a specific address don't change.

The sender list on Settings > Email, showing the default marker and two different verification states.

Note: You can set an unverified sender as the default, but you carry the deliverability consequences.

Remove a sender

AfterShip disables the remove action in two situations. Hover over the action to see which situation applies.

Situation

Why

What to do first

It's the default sender

Removing it would leave no fallback address

Mark another sender as the default

It's in use

An email template or notification sends from it

Point those templates and notifications at another sender

Removing a sender email

Step 3: Add the DNS Records to Your Domain

Domain verification proves to receiving mail servers that AfterShip can send on your behalf. It requires DNS records, and it's what protects your deliverability. You verify each domain once, and every sender on that domain shares the result, so a second address on a verified domain needs no further DNS work.

  1. Go to Settings > Email. A sender whose domain isn't verified yet shows an Unverified tag.

  2. Click Verify domain on that sender. To send from a different address, click Add email first.

  3. In the pop-up, copy each record with its copy button.

  4. Add the records in your DNS provider exactly as shown.

The pop-up lists the following records, each with its own Status:

  • CNAME: Three records that let AfterShip send on your behalf and sign your mail. Required.

  • DMARC: One TXT record. Strongly recommended, because without it, mailbox providers may reject your emails or send them to spam.

Email domain verification pop-up

For a domain such as example.com, the records look like this. The values are unique to your account, so always copy them from the pop-up.

Type

Host

Value

CNAME

automizely

u12345678.wl000.sendgrid.net

CNAME

s1._domainkey

s1.domainkey.u12345678.wl000.sendgrid.net

CNAME

s2._domainkey

s2.domainkey.u12345678.wl000.sendgrid.net

TXT

_dmarc

v=DMARC1; p=none;

Important: A single character out of place prevents verification. Copy each value from the pop-up rather than typing it.

Where to add the records

You add the records in your DNS, not in AfterShip. If you don't manage DNS yourself, send the 4 records to whoever does. This is a short task for an IT team or your web agency, and guessing at it isn't worth the deliverability risk.

Most DNS providers document the exact steps for adding CNAME and TXT records:

For any other provider, search its help pages for "add a CNAME record".

What these records do

Three standards, SPF, DKIM, and DMARC, decide whether a receiving mail server trusts a message that claims to come from your domain. Together, they protect your brand from spoofing and phishing, and they let mailbox providers trust your mail, which improves deliverability. AfterShip handles two of them for you. You publish the third, DMARC, and it's the one most often skipped.

Standard

What it proves

Who sets it up

SPF

Which servers can send on behalf of your domain

AfterShip; nothing for you to do

DKIM

That no one altered the message in transit

AfterShip; nothing for you to do

DMARC

What receivers do when a message fails the two checks above

You, with your DNS provider

How each standard works:

  • SPF: Your domain publishes a DNS record that lists the servers allowed to send for it. The receiving server checks the sending server against that list. A mismatch suggests a spoofed message.

  • DKIM: Each message carries a digital signature made with a private key. The receiving server checks the signature against the public key in your DNS. A match proves no one altered the message in transit.

  • DMARC: Builds on SPF and DKIM. It tells receiving servers whether to deliver, quarantine, or reject mail that fails them.

AfterShip can't publish DMARC on your behalf, because it states your policy for your domain. Add it: without it, mailbox providers such as Gmail, Yahoo, and Outlook may reject your emails or send them to spam, even when the sender is otherwise correctly set up.

Choose a DMARC policy

You need access to your domain's DNS settings. Choose a policy that suits your brand with your IT team or a trusted third-party expert.

A DMARC record is a TXT record on your domain with two required tags: v=DMARC1, the version, and p, the policy.

Value

What receiving servers do with a failing message

none

Deliver it as normal

quarantine

Put it in the spam folder

reject

Refuse it outright, usually bouncing it back to the sender

Start with none. It changes nothing about delivery while you confirm that your legitimate mail passes, and it's the value in the record AfterShip generates. Tighten the policy to quarantine and then reject only once every system that sends as your domain authenticates correctly. This includes your notifications, your marketing tool, and your own mail server. If you move to reject too early, receiving servers silently block your own mail.

A minimal record looks like this:

Type:  TXT Host:  _dmarc Value: v=DMARC1; p=none

Two optional tags are worth knowing:

  • rua names an address to receive aggregate reports.

  • ruf names an address to receive failure reports.

Neither tag is required. Both produce a large volume of machine-readable mail, so add them only if someone will act on the reports.

Step 4: Verify Your Domain

Confirm that AfterShip can find your records. DNS usually propagates within a few hours, but it can take up to 48 hours.

  1. Wait for your DNS records to propagate.

  2. Go to Settings > Email and open the verification pop-up for your domain.

  3. Click Verify.

AfterShip marks the domain as Verified once it finds all 3 CNAME records, and every sender on that domain changes status at the same time. Verify domain then changes to View details, where you can check each record's status again. If the DMARC record is missing, the sender list reminds you to add one.

Warning: Don't remove these records later. Deleting the CNAME records after verification causes sending errors for every sender on that domain, and the sender list doesn't warn you.

Step 5: Confirm Your Records Work (Optional)

The verification pop-up shows a status for each record, including DMARC. To double-check from outside AfterShip:

  1. Enter your domain name in a DMARC checker, such as EasyDMARC's DMARC lookup, and check the status it reports.

  2. Read the headers of an email sent from your domain to see whether SPF, DKIM, and DMARC passed.

If the checker finds no record, the record hasn't propagated yet or you entered it against the wrong host.

Step 6: Show Your Logo With BIMI (Optional)

BIMI (Brand Indicators for Message Identification) is an email standard that shows your brand logo next to authenticated emails sent from your domain. It improves brand recognition and can lift open rates. A Verified Mark Certificate (VMC) confirms that the logo and its ownership are genuine, so recipients can trust it.

You publish the BIMI record in your own DNS, host the logo on your own web server, and get the certificate from a certificate authority. AfterShip's part is the SPF and DKIM that domain verification already gives you. Your logo appears only where the recipient's mailbox provider supports BIMI. See the BIMI Group's list of supporting providers.

How BIMI helps

  • Brand visibility: Your logo sits next to your email in the inbox, so shoppers recognize it instantly.

  • Trust: A logo signals that your identity is authenticated, which makes legitimate emails more trustworthy.

  • Less phishing and spoofing: Shoppers who expect your logo are harder to fool with an impersonation.

  • Consistent branding: The same logo appears in every supporting inbox.

  • More clicks: Shoppers are more likely to open and act on recognizable, trusted emails.

What you need first

  • A DMARC policy of p=quarantine or p=reject, because p=none isn't enough

  • SPF and DKIM, which domain verification already covers

  • A valid SSL certificate on your domain

  • A square SVG logo, centered, with a solid background, no larger than 32 KB (see the BIMI Group's logo requirements)

  • For Gmail, a VMC, which requires your logo to be a registered trademark

Publish the BIMI record

Once you meet every requirement above, publish the record at your DNS provider.

  1. Host your BIMI logo on your web server.

  2. Create a BIMI DNS record at your DNS provider that points to where you host the logo.

The BIMI Group implementation guide covers the record format and the process in detail.

Important: BIMI isn't set up in AfterShip. There's nothing to switch on in the admin.

What You and Your Shoppers Will Experience

After completing these steps:

  • You see your domain marked as Verified, and every sender on that domain shares that status

  • You change your sending address for every template that follows the default sender in one place

  • Shoppers receive your notifications from your own address, with your sender name in their inbox

  • Mailbox providers trust your mail more, so they deliver your notifications to the inbox instead of spam

  • Shoppers see your logo next to your emails in inboxes that support BIMI, once you publish a BIMI record

Troubleshooting

Problem

Cause

Solution

My domain stays unverified after I added the records

A stray space at the start or end of a value, the most common cause

Copy each value exactly from the verification pop-up

My domain won't verify on Cloudflare

Your DNS provider proxies traffic for these records

Set each record to DNS only

My DNS provider shows the host as automizely.example.com.example.com

Your provider adds your domain to the host automatically

Enter automizely as the host, not automizely.example.com

My records conflict with another email service

Another service already uses s1._domainkey or s2._domainkey on your domain

Contact support rather than overwriting the existing records

My domain still isn't verified after 48 hours

Another AfterShip organization may already have verified the same domain

Contact support

FAQs

1. Can I send from more than one address?

Yes. Add as many senders as you need, and choose which one each template uses.

2. Does changing the sender name require re-verification?

No. The sender name is a display name only.

3. How long does domain verification take?

Adding the records takes minutes. DNS usually propagates within a few hours, but it can take up to 48 hours. If the status hasn't changed after that, see Troubleshooting.

4. Do my notifications send before verification is complete?

Yes, but mailbox providers are far more likely to filter them as spam. Complete verification before you make your notifications active.

5. What is the DMARC record for?

DMARC tells receiving mail servers what to do with messages that fail authentication checks, and it improves how major inbox providers treat your domain. Without a DMARC record, mailbox providers may reject your emails or send them to spam.

Key Takeaways

  • Ownership confirmation proves the mailbox is yours; domain verification lets AfterShip send on your behalf

  • Publish DMARC at p=none first, and tighten it once every sending system authenticates correctly

  • Only business domains can be verified, and every sender on a verified domain shares the result

  • Shoppers see your logo in supporting inboxes once you publish BIMI with a quarantine or reject policy

  • Removing the CNAME records after verification causes sending errors for every sender on that domain

Did this answer your question?