1. Creating the addresses        2

1. Main address: gps@yourdomain.com        2

2. System address: bounces-gps@yourdomain.com        2

B) Changing DNS Zone File Record        3

  1. SPF Record        4

Create a new SPF Record        5

Adding to an existing SPF Record        6

2.   DKIM Record        7

Recommendation: Clear out any email related errors        8

Recommendation: Add a DMARC Record        9

C) Testing your DNS Changes        11

Testing SPF Record Entry        12

Testing DKIM Record Entry        14

D) Contact Support        15

Setting the Main Email Account

A Pegasus site ships with the default address Pegasus@digitalcomtech.com as the system’s email address used for every email sent.  A user may specify their own email account, hosted under their own domain.  Let us follow an example for a site hosted under the URL: yourdomain.com.
A normal approach for the site owner is to want every message sent from the system, sent by an email address set as:

gps@yourdomain.com

It could be whatever the client wants, i.e: system@yourdomain.com or support@yourdomain.com etc.

Let us work this document with the example gps@yourdomain.com

Creating the addresses

Two email addresses are needed for Pegasus.

1. Main address: gps@yourdomain.com

This email address must exist under the mail system used by the domain yourdomain.com.  That means, the administrator of the mail server of this domain has to create this new address or recipient (an alias/nickname is also a valid setup).

After creating the email account, test if you can send messages from other email address to it. The client has to be able to consult this address’ inbox and check for the testing message.

2. System address: bounces-gps@yourdomain.com

Also, this address must exist, must be tested for incoming emails. Inbox’s accessibility has to be checked.  The prefix “bounces-” is always the same for any choice of main address. For example, if the client chooses gps@yourdomain.com as main system’s address he/she must create the following two addresses on its mail system:  1. gps@yourdomain.com, 2. bounces-gps@yourdomain.com

The “bounces-” prefixed address is not going to be visible to end-users. It’s just an address used by Pegasus system to audit mail-sending failures.

Important! Make sure that once you create the email addresses you set up the mailbox, by setting a default email client. Usually by visiting this email addresses inbox you should be good to go.

Changing DNS Zone File Record

Nowadays mail servers take several steps to reduce SPAM and prevent “Identity impersonation”.

In order for Pegasus to be able to use correctly an email account whose address is not under its domains, a couple of settings must set on the DNS Zone File configuration on the client’s domain.

In our example, the manager of the domain yourdomain.com

needs to be able to change the DNS Zone file of this domain.

Access to the DNS Zone File is a common operation that can not be denied to the owner of the domain. If the client can’t access the DNS Zone File of a domain owned by he/she, he/she has the right to ask for it to the Domain Registrant holding the user’s domain.

Domain Registrants normally put the DNS Zone FIle configuration

 under an “Advanced DNS Feature” option.

The DNS Zone file is a list of row-like entries.

Each entry has 4 fields:

[name]    [ttl]    [type]    [value, or data]

You will find entries with several types: “A”, “AAAA”, “TXT”, etc.

We are interested only in the ones with type “TXT”

  1. SPF Record

First, check if you already have an SPF entry set.  Todo so, check for a TXT-type entry whose value field starts with v=spf1.

If you find one, go to this section:

Adding to an existing SPF record

On the contrary, if you don’t have one keep reading: 

Important: For SPF records, only search for TXT entries set for the main domain.  That is, search for TXT entries whose name value indicate the name of your domain (yourdomain.com) and not a subdomain, like server.yourdomain.com or 123.yourdomain.com

Create a new SPF Record

Warning: Only create a record for SPF if you are sure you don’t already have one set!

Create a new record, set the HOST field for the main domain yourdomain.com : (not the subdomain)

Set the record type to TXT.

Set the ttl to the default value.

Set its value to: v=spf1 a mx include:_spf.pegasusgateway.com ~all

Make sure you end up with something like:

name                 ttl      type    value

yourdomain.com   43200   TXT   v=spf1 a mx include:_spf.pegasusgateway.com ~all

Save the zone file, review it after saving.

Adding to an existing SPF record.

Assuming you found a TXT record  whose value starts with v=spf and its subdomain value is empty!

The value field is composed of word-like subentries separated by an space.

Search any sub-entry that starts with “include:”.

You can add the value needed for Pegasus before or after this sub-entry, just make sure a space is placed between this new value and its neighbors.

The value needed for Pegasus is: include:_spf.pegasusgateway.com

For example:

You found a TXT record whose value is:

name                 ttl       type   value

yourdomain.com   43200   TXT   v=spf1 a mx include:spf.mtasv.net ~all

Note - TXT value may end in '~all' or '?all' this value should remain the same

when you add the value needed for Pegasus

You have to edit it so it looks like:

name             ttl     type  value

yourdomain.com   43200   TXT   v=spf1 a mx include:spf.mtasv.net include:_spf.pegasusgateway.com ~all

Save the zone file, review it after saving

2. DKIM Record

Regardless if you already find an existing DKIM TXT entry, you have to add a new TXT entry for Pegasus.

This time  you are going to add a record not for the main domain yourdomain.com but for the subdomain pt._domainkey, like this:

pt._domainkey.yourdomain.com

All you have to do is update yourdomain.com for your MAIN domain.

Add a new record:

*Updated Oct 2017*

v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPrVz1KtEpY174atknThiy7RT64o9zBoGn3

r92RcVQz8xe9Dtphvepg+9KF0/tr2gyaSpOOQeYPb+Z8HZC8x60CNN9IZAphvJDpQDC6Iotfrc2

DI0DRmZT/DTyw2jRnuufM7OZCeINsadEPQItmp6bAB3p2baWvUi7UFSuxKUqLwIDAQAB

*Please note this is one long string*

You have to end with an entry set like this:

MAKE SURE THERE ARE NO SPACES AFTER THE p=

name                           ttl     type   value

pt._domainkey.yourdomain.com   43200   TXT    v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBg...

Save the zone file, review it after saving.

Note that although you saved the DKIM entry as: v=DKIM1; k=rsa; …

Once you review it on the DNS zone file, you may see the ; being escaped differently,

this is completely normal.

Clear out any email related errors

For this step you may use the following page to find any email related errors with your domain, simply replace yourdomain.com with the your domain name

https://mxtoolbox.com/domain/yourdomain.com/

When encountered with a Problem, just click more information and try to resolve it.

Tips

If you are using multiple DNS servers, it is important that they are all synchronized, for more information please check the following link, simply replace yourdomain.com with your domain name

 http://dnscheck.pingdom.com/?domain=yourdomain.com

Add a DMARC Record

Yet another helpful tip in preventing your email from going into SPAM is to add a DMARC record, here’s a great guide from Google on how to do this:

Add a DMARC Record


Testing your DNS Changes

Note that changes in the DNS Zone FIle may take hours to propagate.

As they propagate you will find that sometimes changes are set,sometimes not,  this is due to different servers being consulted while the changes propagate.

For Mac and Linux users the best testing tool is the command line program “DIG”:

Open a terminal: Mac users, go to the spotlight (search icon) write terminal, and look for a preinstalled program called “terminal”.

For Windows users, there is no DIG utility, you can use an online dig tool. Search google for “online DIG”. For example: http://www.kloth.net/services/dig.php or https://toolbox.googleapps.com/apps/dig/#A


Testing SPF Record Entry

On the Google Apps toolbox checkout the TXT entry for your domain

You should see something similar to this on the TXT entry:

Testing DKIM Record Entry

On the Google Apps toolbox checkout the TXT entry for the domain

pt._domainkey.yourdomain.com

Please note that this is for the root domain, not a subdomain like gps, or iot, so if your pegasus site is gps.yourdomain.com the pt._domainkey will replace gps, making the full url pt._domainkey.yourdomain.com

Finally

If the toolbox results are satisfactory fill out the form on the next section below.

For tips & recommendations on how to prevent your mail from reaching SPAM, please follow this link:

        Custom Mail Procedure & Improvement

END OF DOCUMENT