Setting the Sender Domain for Bulk Email

By setting the domain authentication setting (SPF authentication, DKIM authentication) for bulk email, you can show that emails are sent from a Sansan-managed server. This setting prevents the target recipient from seeing a message such as "sent via sansan.com". This reduces the chances of your mail going to the recipient's Spam folder.

 

Key Points

  • Use of this function requires administrator access.
  • Some records need to be registered in the DNS of the target domain you are using. Consult with your network administrator for specifics.
  • Please set DMARC authentication in your environment to reduce risk of emails being falsely detected as spam.

 

Procedure

Checking DNS records

  1. Click [Admin Settings] > [Domain Settings].
  2. Enter [Sender Domain].
  3. Register the displayed records in your domain in [DNS Settings].

 

Registering DNS records

Add the records indicated in the above step 3 to the DNS of your domain. It may take up to 48 hours for this to take effect.
Consult with your network administrator for specifics about registration.

 

Enabling DNS records

After confirming that the records are effective in the DNS, return to the domain authentication setup screen and click the "Verify" button. If the settings are correct, the status will be "Active".

 

Deleting the domain

Select the target domain and click "Delete".

 

Frequently asked questions

Q. Even after 48 hours, I'm still getting an error message on the Sansan screen.

A. There may be a problem with the DNS records you entered. Use a command that queries DNS, such as "Dig", to check if the DNS records are reflected. If the ANSWER is empty, it means the record doesn't exist or isn't being reflected. Please review and revise the settings.

Command (example) Type
dig mx sub.example.com MX
dig txt m1._domainkey.sub.example.com TXT
dig txt sub.domainkey.example.com TXT

 

Q. I checked with the "Dig" command and there's no problem, yet it's not working. What else might be wrong?

A. Please check the following.

  1. Domains in DNS records may be automatically converted
    Some registrars will automatically add the domain name to the end of the DNS record. For example, "mail.example.com" may be converted to "mail.example.com.example.com".
    In that case, if you register only a subdomain ("example"), it will be converted to the correct domain. When adding DNS records, follow the rules for existing records.
  2. TXT record is split
    "k=rsa; t=s; p=..." Check if enclosing the TXT VALUE in quotation marks like this solves the problem.
  3. There are duplicate DNS records.
    Make sure there are no duplicates of existing MX or TXT records.
  4. Underscores can't be used
    Some registrars don't accept underscores. Unfortunately, the domain setup cannot be completed correctly if this is the case with your registrar.
  5. Spaces
    Make sure there are no extra spaces in the domain name.
Was this article helpful?
34 out of 100 found this helpful