Question
How do I customise the outgoing email address using AWS (Amazon Web Services)?
Answer
Amazon Simple Email Service (Amazon SES) is a cloud-based email sending service, which allows you to add an existing email address that will appear when sending correspondence from NowInfinity.
Note:
- We strongly recommend your IT specialist assists with setting up AWS. Alternatively, reach out to your Domain Name System (DNS) hosting provider (e.g. CrazyDomains, GoDaddy, etc.) to request assistance with setting up your SPF and DKIM records.
- Only one email address is available per account. We recommend using your general email address, e.g. info@youremail.com.au.
-
NowInfinity allows you to customise the outgoing email address for all correspondence to your clients. This article relates to the use of AWS (Amazon Web Services), however there are 2 other options:
- Navigate to Menu > Portal > Portal Settings > Email Settings.
- Select AWS Simple Email Service from the drop down box.
- Ensure SPF and the DKIM keys updates have been made within your DNS hosting provider.
- Within "Send Mail From" enter the email address that will be shown as a "Sender's email" for outgoing correspondence.
Note: personal email domains (e.g. those ending in @gmail.com) cannot be used for AWS, as SPF and DKIM Keys cannot be configured for these. Other examples include AOL, Outlook, Zoho, Mail.com and Yahoo. - Click on "Verify"
- A verification email will be sent to the email address. Open this email and click the URL link to verify:
- Once the verification process is complete, click "Verify" again from the Portal Settings page to activate this setting.
Note: Once ticked, the "Verify" button will update to "Verified" with a tick box: - Enter the name you wish to appear as the sender into "Send mail from name"
- (Optional) To have a copy of all outbound emails sent to a specific email address, enter the email address into "Send a copy of all emails to". While optional, this is recommended.
- Select "Save Sender Data", then "Set AWS"
Note: If you receive the following warning, the DKIM details are not detected. You will need to ensure they have been added correctly. If they have only just been added correctly, there may be a delay in the DKIM records publishing.
SPF
Sender Policy Framework (SPF) is an email validation standard that is designed to prevent email spoofing. Domain owners use SPF to tell email providers which servers are allowed to send email from their domains.
Instructions to set up SPF:
If your domain does not have an existing SPF record, publish a TXT record with the following value: "v=spf1 include:amazonses.com ~all"
SPF records can contain multiple statements. Therefore, if your domain already has an SPF record, you can add an ‘include’ statement for Amazon SES.
For example, if there is already a record for outlook, you can edit the record and publish the following: "v=spf1 include:amazonses.com include:spf.protection.outlook.com ~all"
DKIM Keys
Domain Keys Identified Mail (DKIM) is a standard that allows senders to sign their email messages with a cryptographic key. Email providers then use these signatures to verify that the messages weren't modified by a third party while in transit.
Click here to learn how to use DKIM with Microsoft 365.
- To generate DKIM keys, navigate to Menu > Portal > Portal settings > Email settings, when AWS is selected as the email type.
- Select "Generate DKIM Keys" in the "DOMAINKEYS IDENTIFIED MAIL (DKIM) RECORD" sub-section.
Generated keys will be available in the read-only mode in the text box below:
Note: When DKIM keys are note detected as set up, selecting the "Remind me to set DKIM keys every 3 days" checkbox will send a reminder email every 3 days.
The received tokens should be added in DNS in the following CNAME format. (Note: the format needs to be CNAME, rather than TXT):
token1._domainkey.example.com CNAME token1.dkim.amazonses.com
token2._domainkey.example.com CNAME token2.dkim.amazonses.com
token3._domainkey.example.com CNAME token3.dkim.amazonses.com
example.com - is your domain name
For example, applying this template to the tokens shown in the preceding example produces the following records:
hirjd4exampled5477y22yd23ettobi._domainkey.example.com CNAME hirjd4exampled5477y22yd23ettobi.dkim.amazonses.com
v3rnz522czcl46quexamplek3efo5o6x._domainkey.example.com CNAME v3rnz522czcl46quexamplek3efo5o6x.dkim.amazonses.com
y4examplexbhyhnsjcmtvzotfvqjmdqoj._domainkey.example.com CNAME y4examplexbhyhnsjcmtvzotfvqjmdqoj.dkim.amazonses.com