This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
own-domain-sending [2014/07/09 08:16] ian [Use a domain that's already used for email] |
own-domain-sending [2017/08/02 10:54] (current) benc [Use a domain already used for email (Recommended)] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Own domain sending ===== | ===== Own domain sending ===== | ||
| - | By default, your Sentori account's From Address -- where emails are sent from and is sometimes shown in recipients' inboxes -- will use a non-branded Sentori domain (e.g. @snt1.net, @snt2.net, etc). Any emails sent back to these addresses will be discarded. | + | If you wish, you can use a From Address at your own domain so that your emails look as though they've come directly from you, rather than from one of Sentori's unbranded domains (@snt1.net, @snt2.net, etc). |
| - | The Reply Address -- where emails go if someone clicks the Reply button when reading one of your emails -- is set to an email address of your own on each Email and Template in your Sentori account. | + | To do this, you must make some changes to the Domain Name System (DNS) records of your domain and then [[help@sentori.co.uk|let us know]] so we can complete the setup within Sentori. |
| - | If you wish, you can use a From Address at your own domain so that your emails look as though they've come directly from you, rather than from Sentori. | + | === Warning === |
| - | + | ||
| - | To do this, you must make some changes to the Domain Name System (DNS) records of your domain and then let us know so we can complete the setup within Sentori. | + | |
| //Failing to make these changes correctly will result in email delivery problems from Sentori and possibly your domain as a whole - so be careful!// | //Failing to make these changes correctly will result in email delivery problems from Sentori and possibly your domain as a whole - so be careful!// | ||
| - | ==== Use a domain that's already used for email ==== | + | ==== Use a domain already used for email (Recommended Solution) ==== |
| If you want to use a domain that is already being used for email, these are the DNS records you need (using an example of "mydomain.com"). | If you want to use a domain that is already being used for email, these are the DNS records you need (using an example of "mydomain.com"). | ||
| - | This enables all emails sent to the From Address of the Emails you send from Sentori to go back to you. | + | This also allows emails sent to the From Address of your Sentori Emails to come back to you, unlike the setup below ([[#spf-recommendations|Use a domain without a mail server]]) which discards them. |
| - | //If you're unsure about any of these records or your domain already includes some of them, check with the appropriate technical person in your organisatin about how to proceed - modifying existing records may cause delivery issues throughout your domain!// | + | //If you're unsure about any of these records or your domain already includes some of them, check with the appropriate technical person within your organisation about how to proceed - modifying existing records may cause delivery issues throughout your domain!// |
| - | * Create a TXT SPF record for "mydomain.com." with the value "v=spf1 a mx include:snt0.net ~all". | + | === DNS settings === |
| - | * Create a TXT record for "_domainkey.mydomain.com." used for DKIM, with the value "o=~". | + | |
| - | * Create a TXT record for "sentori1._domainkey.mydomain.com.", also used for DKIM, with the following value (ensure it contains no spaces or carriage returns): \\ <code style="word-wrap: break-word;">"k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDJxNWiVwlBsvl765rGCFifo2BqqdNH83oxxFZ5b/XEdJFSFYZXahK7a3neD8QCzm5xVNV9KmDJbcKx6niExGHIVPA0d9C69hSZvPT40rZuJsxn62andncuKwlEzPJfgSvlyXSneA9pQKgb99WDTUpOwVY5A3vjdR9VpGRxXIyB7wIDAQAB;"</code> | + | All of these records should be created. |
| - | * Create a TXT record for "_dmarc.mydomain.com." used for DMARC with the value "v=DMARC1; p=none; rua=mailto:dmarc@mydomain.com" setting "dmarc@mydomain.com" to the email address of someone technical that should be sent daily DMARC reports by ISPs. | + | |
| + | - Create a **TXT** SPF record for "**mydomain.com.**" with the value "**v=spf1 a mx include:mail.snt0.net ~all**" or, if you already have an SPF record, add "**include:mail.snt0.net**" at the end before the existing "all" mechanism. (see [[#spf-recommendations|SPF Recommendations]] for checking tools and advice) | ||
| + | - Create a **TXT** record for "**_domainkey.mydomain.com.**" used for DKIM, with the value "**o=~**". | ||
| + | - Create a **TXT** record for "**sentori1._domainkey.mydomain.com.**", also used for DKIM, with the following value (ensure it contains no spaces or carriage returns): <code>"k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCS8aWsnuXoQ2RV7Yl6W/CirDtkDe5a9HVVXH47yaBjaENi11hBchEUykOzfaLNU7DsoL8c20XMz9su/AW4ooW2J8nYKk4T1bRKZYvyADCJ4Oddvxv0cjhoXvTkyjPPUjc5vrfXDVitx2oFr3a9LurJKmd/QZCssYU/rmGYb7+EBQIDAQAB;"</code> | ||
| + | - Create a **TXT** record for "**_dmarc.mydomain.com.**" used for DMARC with the value "**v=DMARC1; p=none; rua=mailto:dmarc@mydomain.com**" setting "**dmarc@mydomain.com**" to the email address of someone technical that should be sent daily DMARC reports by ISPs. | ||
| ==== Use a domain without a mail server ==== | ==== Use a domain without a mail server ==== | ||
| If email isn't set up on the domain and won't be (you have a domain, but don't have a mail server), then you can use the DNS instructions above and just add an MX record to point back at Sentori. | If email isn't set up on the domain and won't be (you have a domain, but don't have a mail server), then you can use the DNS instructions above and just add an MX record to point back at Sentori. | ||
| - | * Create an MX record for "mydomain.com." with the value "mail.snt0.net". | + | * Create an **MX record** for "**mydomain.com.**" with the value "**mail.snt0.net**". |
| - | Any emails sent back to your From Address will be discarded. | + | Any emails sent back to your From Address will be discarded so this option is not recommended. |
| ==== Let us know about the changes ==== | ==== Let us know about the changes ==== | ||
| - | Once you've created the appropriate DNS records, drop us a support ticket letting us know the following and we'll check your domain before updating Sentori to make it usable: | + | Once you've created the appropriate DNS records, [[help@sentori.co.uk|drop us a support ticket]] letting us know the following and we'll check your domain before updating Sentori to make it usable: |
| * The name of your Sentori Account | * The name of your Sentori Account | ||
| Line 40: | Line 42: | ||
| + | |||
| + | \\ | ||
| + | \\ | ||
| + | \\ | ||
| + | \\ | ||
| + | \\ | ||
| + | |||
| + | ==== SPF Recommendations ==== | ||
| + | * Tools such as [[https://mxtoolbox.com|MXToolBox.com]] and [[https://dmarcian.com/spf-survey/|dmarcian's SPF Surveyor]] can be used to check your SPF record is correct and highlight any problems. | ||
| + | * Multiple SPF records are not advised. According to Google this "may cause delivery and spam classification issues" (https://support.google.com/a/answer/4568483). If you have more than one SPF record then they should combined into a single one. | ||
| + | * You should avoid having more than 10 "lookups" to fully resolve your SPF record. [[https://mxtoolbox.com|MXToolBox.com]] and [[https://dmarcian.com/spf-survey/|dmarcian's SPF Surveyor]] can check this for you. If you're near or over that limit , remove any that are no longer needed and if you're still over the limit go on and convert "include" entries into their "ip4" equivalents where possible. For Sentori's "**include:mail.snt0.net**", this would be: | ||
| + | <code>ip4:83.222.233.164/30 ip4:83.222.233.168/30 ip4:83.222.235.232/29 ip4:134.213.146.5 | ||
| + | ip4:173.203.67.79</code> | ||
| + | |||
| + | Please note that while we have no plans to change Sentori's sending infrastructure, it's possible these values may be changed in the future. If you encounter delivery issues, confirm these values still match your SPF record and update if necessary. | ||