Due to heightened restrictions imposed by mail providers on email senders, we now require the setup of SPF and DKIM for utilizing custom "from" addresses in both the Revize Online Forms application and the Revize Public Service Request Application. These adjustments are aimed at enhancing email deliverability and will be enabled and enforced starting Wednesday, Feb 14th, 2024.
Currently, these systems use a turbosmtp sender address that doesn't match the 'from' header in the emails (Sender: noreply=revize.com@turbo-smtp.info). While this setup worked for many in the past, it is now more likely to cause emails to get quarantined for spoofing. To address this, the sender address will now be required to match the address used as the 'from' on the email. To support these changes, sender authentication must be implemented. Authentication will already be implemented for those using revize domain 'FROM' addresses. Others will need to implement these changes in their DNS or change to a revize 'FROM' address.
To implement these changes, you must add two DNS records for all the domains you use. Failure to make these adjustments could potentially impact your email deliverability. If you exclusively use the default noreply@revize.com sender, these changes are not necessary.
Important: For each of your sender email address domains, both SPF and DKIM records should be added.
SPF record:
Add the following TXT record to the domain of the envelope address (example.com), adhering to one of two cases:
If the SPF record is already in your domain, edit the record by appending `include:turbo-smtp.com` after the string `v=spf1`. Note: Remember to include a space before and after the additions. The resulting record will look something like `v=spf1 include:myotherdomain.example.com include:turbo-smtp.com ?all`.
If there is no existing SPF record, simply create one and enter the details as a TXT DNS record: `v=spf1 include:turbo-smtp.com ?all`.
DKIM record:
A DKIM record can be added as a TXT record by inserting the following:
Domain:
turbo-smtp._domainkey
Value (with no line breaks):
k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDT3MWLni6so1q9eQggRYBCLHFjohZkCnYHH8gZNDBm6zRrodRVpWpJQW7x3cWWiuBhS1X0IfBB80l5tqFa+yc+mVgnk8tkUzOHFbPQPp4fi7egTpMtsQW/ZMrxw73SItNvPr72qvJTYZNPxarMx+ULjEWybcfEdXHPY8jslGcpCwIDAQAB
These modifications may take some time to propagate, but you can confirm their correctness after waiting by using the following tools:
SPF: SPF Survey Tool
DKIM: DKIM Inspector Tool
For the DKIM inspector, enter your domain in the domain field and "turbo-smtp" in the selector field.
Should you require further assistance or have additional questions concerning these changes, feel free to submit a support ticket