You may have seen the following banner appear at the top of your account:

This relates to recent changes with how Google and Yahoo, as well as other providers, handle inbound communication communication from senders with particular emphasis on bulk senders.

You can see which channels are affected and what changes need to be made.

To see channels that may be affected navigate to this link:

https://dashboard.edesk.com/channel-domain

In this article we will go over what changes you will need to make to channels that use the option “Send from own email address via eDesk.”

A little background on the recent changes

During October of 2023 Gmail and Yahoo announced that there would be a requirement for DMARC to be present in a bulk senders DNS record.

A DMARC record is a text entry within the DNS record that tells the world your email domain’s policy after checking SPF and DKIM status. DMARC authenticates if either SPF, DKIM, or both pass. This is referred to as DMARC alignment or identifier alignment.

The reasons for this change is that Google and Yahoo wish to take steps to help make email communication much safer and secure. By enforcing validation they can help prevent unwanted spam and curtail nuisance communication. By validating your DMARC records you can help improve inbox placement and help providers identify you as a legitimate sender.

How does this affect eDesk?

We have already gone ahead and made sure our records are all up to date so all messages from our domain addresses are compliant with the required changes.

If your channel is set to use “Send directly from the channel’s eDesk email address” we will have you covered and no further action will be required.

Where you will need to make a few changes will be if you use the option:

A few additional changes will need to be made to allow us to send emails via your domain on your behalf.

We will cover these changes in the next section

Send from own email address via eDesk

Originally when this setting was selected all you were required to do is add an SPF record to your DNS records. With the change to DMARC a few additional records will need to be applied.

When you navigate to your channel now you will see the following Notification on screen:

When you click Start Verification you will be taken to a screen where you will see the current status of authorisation.
 

If you click on Download .csv DNS record set you will see what records need to be added to your domains DNS records.

These will come in the form of:

• 1 SPF Record (If not already Set)
• 1 MX record
  • Be aware that some DNS Services may require you make a slight change to this record. Please check with your provider how they accept this record.
    • Some DNS services will accept the full record in one line.
    • Other DNS services may require the numeric value, the "Priority Value", to be placed in a separate field.
      • The "10" value will go in Priority field or equivilently named field.
      • The "feedback-smtp.us-east-1.amazonses.com" will go into the Value field or equivilently named field.
• 3 CName records

Once these have been inserted into your DNS records eDesk will be able to send fully compliant messages using your domain address.
 

The screen will show you when verification was last checked and the status of DKIM status, Mail from Status etc.

One thing to note: if multiple channels use the same domain address, in our example edesk.com you will only need to update the DNS record once.

For example, say on our hypothetical eDesk account we have the channels:

• hello@edesk.com

• deliveries@edesk.com

• orders@edesk.com

Your DNS record would only need to be updated the once and the change would be applied to all channels as they share the same domain address.

However, if you have multiple channels that use different domains:

• hello@edesk.com

• hello@repricer.com

• hello@feedbackexpress.com

The DNS records for each domain will need to be updated to be DMARC compliant.

You can also check the status of any other channels that need updated on the Channel Domains Screen: