Knowledgebase
InboxSys.com > InboxSys Support > Knowledgebase

Search help:


Setting up "Domain settings"

Solution

"Domain settings" in InboxSys are used to:

  1. Configure the domainchecker
  2. Monitor IPs

Domain settings are found by clicking the cogwheels in the far right top, selecting "account settings" and "Domain settings". The form shown has 3 sections with the following options:

  1. Link domain template
    1. Cname
  2. Sender domain template
    1. MX record
    2. Default SPF /SenderID record
    3. Alternative SPF /SenderID record
    4. Default DKIM selector
    5. Default DKIM key
    6. Alternative DKIM selector
    7. Alternative DKIM key
  3. Formatting

Template system

The dropdown menus for linkdomains and senderdomains how all link- and senderdomains that can be found in the messages in your account. Picking an option from the linkdomain template automatically changes the CNAME field to show the setting from the selected domain. Picking an option from the senderdomain template automatically changes the MX, default SPF, alternative SPF, default DKIM Key and default DKIM selector fields to show the settings from the selected domain. The alternative DKIM key and the alternative DKIM selector remain unchanged.

The template system is the way to configure all fields at once, especially when you are unsure what to set. However, it is only possible to use the template system after you have received one or more campaigns to the seedlist trigger address.

Cname

Cname's are used for link redirection. All CNAME records that should be considered "correct" by the domainchecker can be entered in this field, separated by pipes.

Example: 2 domains are used for redirection across all messages: "link.example.com" and image.example.com. The following lookups apply:

$ host -t cname link.example.com
link.example.com is an alias for example.org.

$ host -t cname image.example.com
image.example.com is an alias for example.net.

In this constellation, the correct setting to put in this field is: "example.org|example.net"

MX record

All MX records that should be considered "correct" by the domainchecker can be entered in this field, separated by pipes.

SPF / SenderID (default and alternative)

All IP networks that should be considered "correct" by the domainchecker when checking for SPF or SenderID can be entered in this field, separated by pipes.

Example: Mail is primarilly sent from IPS A. Some streams go out via ISP B and rarely, Mails are being sent out from the local infrastructure. ESP A allows sending via the networks 127.0.0.0/24, 127.0.1.0/23 and 127.0.3.0/24. ESP B is allows sending via the networks127.1.0.0/24 and 127.1.1.0/24 and the IP for the local infrastructure is 127.5.5.123. We want to set IPs fom ESP A as default and all other IPs as alternative. The correct settings are:

Default SPF: 127.0.0.0/24|127.0.1.0/23|127.0.3.0/24

Alternative SPF: 127.1.0.0/24|127.1.1.0/24|127.5.5.123/32

DKIM selector (default and alternative)

Each DKIM selector field can hold one selector. This way, it is possible to add max. 2 selectors, for the domainchecker to consider "correct" on your domains.

DKIM key (default and alternative)

Each DKIM key field can hold one DKIM key. This way, it is possible to add max. 2 public keys, for the domainchecker to consider "correct" when checking DKIM settings on your domains.

Formatting

This dropdown menu shows all possible output formats for the copy/paste section in the domainchecker and other query outputs. This feature was designed to paste query results directly from InboxSys in a ticket, formatted according to the ticket system used.

In case you need any format which is not in the list, or you need any other help configuring the Domain Settings, please don't hesitate to create a support ticket.

 
Was this article helpful? yes / no
Related articles Monitoring IPs in "Network"
Read a campaign result - overview
Article details
Article ID: 11
Category: Knowledgebase
Rating (Votes): Article rated 3.4/5.0 (10)

 
« Go back

 
Powered by Help Desk Software HESK, in partnership with SysAid Technologies