Why this matters now

In an attempt to counter the increasing number of spam emails, mailbox providers such as Microsoft, Google, Orange and Yahoo are applying progressively tighter rules to incoming mail. As part of our service, we send shipping notifications and track & trace emails on your behalf. We too want to ensure that these emails end up in your customer's inbox, not in the spam folder. This will require action on your part. Already done? Perfect. If not, please continue reading below.

What we ask you to do

Add these DNS records to your mail domains. They need to be in place by 1 January 2027:

• SPF — authorises nShift's relays to send on behalf of your domain.
• DKIM — adds a cryptographic signature proving each message genuinely came from your domain and was not altered in transit

Both are a one-time DNS change, normally completed by your IT team or hosting provider in a matter of minutes.

Our help centre article Maximize email deliverability by using SPF and DKIM explains exactly what to publish.

Other issues that damage deliverability

• Sender addresses that do not exist. Many customers send from a no-reply@ or noreply@ address that is not a real, working mailbox. This looks suspicious to receivers and breaks the return path for anything that cannot be delivered.
• Invalid recipient addresses. Misspelled domains such as gmail.con or hotmail.comm, truncated domains, and syntactically invalid addresses are guaranteed to bounce. Typo domains are also a known spam-trap vector, so they carry more reputational cost than an ordinary failed delivery. Validating email addresses at the point of capture in your own systems prevents this entirely.

What happens after 1 January 2027

Please arrange these changes before 1 January 2027. After that date, domains without valid SPF and DKIM configuration run two risks.
First, their mail is increasingly likely to be throttled, filtered into spam, or blocked outright by receiving providers, with the resulting loss of delivery notifications to their customers.
Second, because a single unauthenticated domain can damage the reputation of the infrastructure shared by everyone, we may have to stop sending mail on behalf of domains that remain unconfigured. We would much rather not take that step, which is why we are announcing this well in advance and are happy to help you get it arranged.

Need help?

If you are unsure of your current status, contact our support team. We will verify your domain and send you the exact records to publish.
 

Subscribe to Announcements

We recommend subscribing to Announcements in our Help Center so you’ll receive important updates about Transsmart by email. Go here: Announcements – nShift Transsmart Help Center and click the Follow button.