Understanding DKIM and Return-Path Records for Interpreter Intelligence Email Delivery

Julie Earnest
Julie Earnest

Interpreter Intelligence sends notification emails on behalf of your agency’s domain. For example, emails may be sent from an address using your domain, such as @1nsight.com, so that recipients recognize the communication is coming from your organization. These emails can be job offers, confirmations, cancellations or financial related.

To support secure and reliable email delivery, Interpreter Intelligence uses Postmark as part of the notification process. Postmark is an email delivery service that helps send system-generated emails.

As part of standard email security and sender validation, Postmark requires your domain to contain specific DNS validation records. These records are called DKIM and return-path records.

What are DKIM and return-path records?

DKIM

DKIM stands for DomainKeys Identified Mail. It is an email authentication method that helps prove that an email was authorized by the domain it claims to be from.

When Interpreter Intelligence sends an email on behalf of your domain, the DKIM record allows receiving email providers, such as Gmail, Outlook, and Yahoo, to verify that the email is legitimate and that Interpreter Intelligence has permission to send it on your behalf.

In short, DKIM helps confirm:

  • The email was authorized by your domain.
  • The email was not sent by someone pretending to be your organization.
  • The message is less likely to be treated as suspicious or spam.

Return-path

The return-path record is another DNS record used in email delivery. It helps manage bounced emails and sender verification.

When an email cannot be delivered, the receiving mail system sends the bounce information back through the return-path. Having a validated return-path helps Postmark and Interpreter Intelligence properly track delivery issues and maintain the reputation of emails sent on your behalf.

Why does Interpreter Intelligence use these records?

Interpreter Intelligence uses DKIM and return-path records to help ensure that emails sent on behalf of your agency’s domain are trusted by receiving email systems.

Because your organization controls your domain, only you or your domain administrator can add or update these DNS records. Adding the records proves that Interpreter Intelligence is authorized to send email using your domain.

This prevents Interpreter Intelligence emails from appearing as though they are being sent without your permission.

When are these records set up?

These records are typically configured when a customer first onboards with Interpreter Intelligence.

During setup, Postmark provides the required DKIM and return-path records. Your organization then adds these records to your domain’s DNS settings.

Once the records are added and verified, Interpreter Intelligence receives confirmation that the domain records are valid.

Why do these records need to be updated periodically?

Postmark may periodically expire or rotate domain validation records as part of its standard security and vetting process.

When this happens, Postmark provides new records and notifies Interpreter Intelligence that the existing records need to be updated. Interpreter Intelligence then sends the updated record information to your organization so your domain administrator can make the necessary DNS changes.

This is a normal maintenance task and does not mean anything is wrong with your domain or Interpreter Intelligence account.

What happens if the records expire?

Expired DKIM or return-path records do not necessarily mean that emails will stop sending from Interpreter Intelligence on your behalf.

However, expired or missing records can affect how receiving email providers evaluate those messages.

Without current validation records, emails may be viewed as higher risk. This can increase the likelihood that messages are:

  • Marked as spam.
  • Flagged as suspicious sender activity.
  • Delayed or rejected by some receiving email systems.

For example, if an email sent by Interpreter Intelligence to one of your recipients is marked as spam, email communication to that recipient may be stopped until Interpreter Intelligence manually marks the recipient email address as Not Spam in Postmark.

This is a standard email delivery and sender protection practice. It is not specific to Interpreter Intelligence or Postmark.

Why is it important to keep these records current?

Keeping DKIM and return-path records up to date is a best practice for email deliverability and domain security.

Current records help ensure that emails sent by Interpreter Intelligence on your behalf are recognized as valid by receiving email providers. This helps reduce the risk of messages being marked as spam and supports consistent delivery of important notifications.

What action is required?

If Interpreter Intelligence notifies you that your records need to be updated, your domain administrator should add or update the DNS records provided.

Once the records are updated in your domain, Interpreter Intelligence receives confirmation that the records are valid. No further action is required after the records are successfully verified.

Example DKIM record

Below is an example of a DKIM record that may be provided for your domain.

Hostname

11190419160128pm._domainkey

Type

TXT

Value

k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCiZEkX+r2fDgiL3ptO46auw/M7kNKTkbO0EZLllFcxoEbXDOg/NEXH0DgYy3gYySWqTbC7HxTkPkEVi+tgbr9ziFAGmpXb9cPUKupuYhG9detCa0HAxTslbvX4QMGE8/uL5lx7s5xX4x74Mp+aVl+ReizljLtCR5HIFIgT7nB3xQAABBCC

If you use one of the common DNS providers, check this help article for step by step instructions
Resources for adding DKIM and Return-Path records to DNS for common hosts and DNS providers

Your actual DKIM and return-path records will be different. Always use the specific records provided to you by Interpreter Intelligence.

Summary

Interpreter Intelligence uses DKIM and return-path records to securely send emails on behalf of your agency’s domain. These records prove that Interpreter Intelligence is authorized to send email from your domain and help receiving email providers recognize those messages as legitimate.

When Postmark issues updated records, your organization must update them in your domain’s DNS settings. Keeping these records current helps protect your domain reputation, improves email deliverability, and reduces the chance that important Interpreter Intelligence notifications are marked as spam.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request