EmailElement Docs

Sender Domains

A Sender Domain is the domain your email goes out from, and the From and Reply-To addresses your recipients see. It proves it is yours through DNS — SPF is required, DKIM and DMARC are strongly recommended — and the same page carries its reputation score and its feedback loop settings.

Instructions

  1. Navigate to Sender Domains > Create Sender Domain. Pick how the domain sends before anything else: Other for a provider you connect yourself, Gmail for a Google Workspace account, or EmailElement for our own sending. EmailElement shows only when the account has it.

    • The choice is saved on the domain and decides which sections the form shows, now and every time it is opened again. It cannot be changed afterwards.

  2. Enter the domain name and select a Brand to associate with this domain. Sender Domain # is blank while creating and shows the number once saved.

  3. Fill in From Name and From Email (these are visible to recipients in their inbox). Optionally set ReplyTo Name and ReplyTo Email if replies should go to a different address.

  4. Click Validate DNS Records, which sits under the logo on the card at the top right. EmailElement checks three record types: SPF (required), DKIM (recommended), and DMARC (recommended). Green status = valid.

  5. If any record shows as not valid, guide the user to add or update DNS records at their domain provider. SPF authorizes sending servers, DKIM provides cryptographic signing, DMARC sets policy for authentication failures.

  6. Optionally configure the MX Record for EmailElement to handle reply-to email. If using MX, leave the ReplyTo Email field blank on the sender domain form.

  7. To set the name recipients see on the To header, expand the Advanced section and use To Name under Recipient Name:

    • Leave it blank and every send from this domain uses {{#if {First Name}}}{First Name} {Last Name}{{else}}{Email}{{/if}}. A contact with a first name gets their name; everyone else gets their email address.
    • Type replacement tags to change it, for example {First Name} {Last Name}. Right-click the box to insert a tag rather than typing it.
    • Conditional logic works here, using the same {{#if}} and {{else}} form as the default.
    • Up to 255 characters. One value per sender domain, with no per-brand or per-email override.
    • If the format resolves to nothing for a contact, that contact falls back to their email address rather than sending a blank name.
    • This is why a recipient sees "jane@example.com" <jane@example.com> instead of their name: the contact has no first name stored.

  8. To collect Yahoo spam complaints for the domain, expand the Advanced section and enter a Feedback Loop Domain - a subdomain the user owns and uses only for feedback loop reports, for example fbl.your-domain.com. Copy the read-only Mail Server value shown under the field, then Save the sender domain before going any further: Validate DNS Records is disabled until the domain is saved, and EmailElement only accepts mail for a feedback loop domain that is already stored. Then:

    • Add an MX record on the feedback loop domain pointing at that mail server. The user does not need a mailbox there - EmailElement receives the mail.
    • Enroll the sender domain in Yahoo Sender Hub, then publish the yahoo-verification-key TXT record Sender Hub issues for it on the sender domain, not on the feedback loop domain.
    • In Sender Hub, set the reporting email address to an address at the feedback loop domain and ask Sender Hub to send the verification code. On the sender domain page, click Get Verification Code to read the code, then enter it in Sender Hub. EmailElement holds each code for 5 minutes after it arrives.
    • Reopen the sender domain and click Validate DNS Records. Yahoo Verification Token and the feedback loop MX report Success once both records resolve.
    • From then on a Yahoo spam complaint is recorded as a Complained delivery event and the contact is added to the account suppression list automatically.

  9. Click Save to finalize the sender domain. The domain is now available for use in Send Integrations and Email Content.

  10. The Reputation Scoring tab on a saved sender domain shows how the domain is performing. It carries a Composite Reputation Score out of 100, rolled up from five weighted groups. Four of them have a card: Mailbox Provider Signals from Google Postmaster, Engagement & Delivery, External Reputation from blacklist listings, and Domain Profile. The fifth group, Deliverability, carries the largest weight and has no card, so bounces and complaints can pull the composite below every card on the page. A card with nothing collected yet reads No data, which is not the same as a score of zero.

What Each Option Changes

The card at the top right carries Ability to send, the logo for the option picked, and Validate DNS Records. Ability to send reports the Tracking record's state, and reads Unverified until the DNS has been checked. On a saved domain the card also holds the Active toggle, which saves on its own rather than waiting for Save; turning off a domain a live send integration is using lists that integration and will not let you confirm.

  • Other keeps every section: Webhook, Bounce Processing, Reply-To, Recipient Name and the Yahoo feedback loop.
  • Gmail drops Webhook and Bounce Processing, because Google reports those itself. The DKIM Selector can still be set, since Gmail publishes its own key.
  • EmailElement drops Webhook, Bounce Processing and the Yahoo feedback loop, and keeps Reply-To. Instead of a DKIM Selector it publishes the DKIM Record and the DMARC Record for you to add, each with its own state and Copy buttons.

There is no ESP Integration dropdown on the form any more. The selection page is the only place the answer is given.

Something went wrong. Reloading the page usually fixes it. Reload ×

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.