Sending email using the chain email domain is an enterprise offering that Loopon can provide to chains. It is not available for individual hotels. The service is available as one domain per chain.
Requirements
Our recommendation is to use a subdomain for the email. A subdomain could be:
anything@loopon.example.com or anything@feedback.example.com where example.com represents the domain used by your chain. There are several reasons for using a subdomain including:
- Separating the Loopon sendouts from business emails.
- Alowing Loopon to catch bounces and replies.
- Minimizing risk of configurations breaking during other IT updates within the chain.
Set up process
1. The client and Loopon will set up a direct technical contact representing both organizations for exchanging configuration, doing set up and common tests.
2. Loopon will provide an initial setup config. This information is available below.
Information provided:
| Information | Comment | Responsible |
| Domain and sub domain | To be used in send outs | Client |
| A-record (A) | To be set up in client DNS | Loopon provides, client sets up |
| MX-records (MX) | To be set up in client DNS | Loopon provides, client sets up |
| DMARC-record (TXT) | To be set up in client DNS | Loopon provides, client sets up |
| SPF-record (TXT) | To be set up in client DNS | Loopon provides, client sets up |
| DKIM-record (TXT) | To be set up in client DNS | Loopon provides, client sets up |
3. Once client has verified the setup Loopon will validate the set up which includes Google validating the domain.
| Information | Comment | Responsible |
| Google verification (TXT) | To be set up in client DNS | Loopon provides settings from Google, client sets up |
Testing
Mutual tests are done using mail-tester.com, a third party service that will verify the settings as well as other risks of being caught in spam filters, such as email subject and content.
Information provided by Loopon
| A | 46.21.109.106 |
| MXs | 10:aspmx.l.google.com 50:alt1.aspmx.l.google.com 50:alt2.aspmx.l.google.com 100:alt3.aspmx.l.google.com 100:alt4.aspmx.l.google.com |
| TXT (SPF) | Existing record add: include:_spf.loopon.com New record: "v=spf1 a mx include:_spf.loopon.com ~all" |
| TXT (DKIM) | Remove spaces i P attribute from: m1._domainkey.subdomain.example.com : "k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCuTpT95XgLT/R8 KwRC+tP7/acQ0dhVff9NXjwZJrS8qDwPX03hOyarWOJU05oYqLUdO5xjAoWzdSGc+A Vw91CdmMn9sjEwqV3urmainBQo/hfAKlEF3tZt7sMJK3FmtfRppKonHJL8MvKd/QHGe dIiE43uap9Fr758ng2qBfRC5wIDAQAB" |
| TXT (DMARC) | _dmarc.subdomain.example.com set value to v=DMARC1; p=none; pct=100; rua=mailto:dmarc@loopon.com; ruf=mailto:dmarc@loopon.com |
| TXT (Google) | google-site-verification=***** |
| CNAME | *****.subdomain.example.com points to sendgrid.net |
| CNAME | url*****.subdomain.example.com points to sendgrid.net |
| TXT |
em*****.subdomain.example.com "v=spf1 include:_spf.loopon.com ~all" |
| CNAME | em*****.subdomain.example.com points to mx.sendgrid.net |
***** = These are values unique to each chain and will be provided during the second part of the set up process.