We have released an update that allows you to send out your Gecko emails through a new and improved processor. 

The new email processor should allow us to send emails faster and more securely, but it also gives users more options to verify their domains as a whole and improve the deliverability of the messages sent through Gecko. You will need to reverify your email senders in Gecko, which should only take a few minutes, after which you can enable the new processor with a flick of a toggle. Simple.  

Here's the announcement video:

Verifying domains

Whilst you can still verify individual emails senders in Gecko, we strongly recommend configuring a verified domain. Doing so will reduce the chance of emails being blocked or highlighted as spam by recipients' inboxes. The process of verifying a domain will require you to ask your IT team to add 6 records to your domain's DNS records.

To verify a domain go to Settings > Verified Senders & Domains > Domains and add a new domain: 

If your institution has emails ending @geckouni.ac.uk, your domain would be geckouni.ac.uk (i.e. the suffix of your email address without the @ sign). 

Once you enter your domain address, you will be taken to a page the will list some configuration details that will have to be added to your domain's DNS settings. 

Simply copy the 'Configuration Details' from the text box and send them to your IT team, asking them to add the provided records into their DNS settings for your domain. 

....and that's all you need to do for now. Once your domain has been verified, simply toggle to enable new processor. We've a short guide on this further down this page.  

The below screenshots are points of reference for the IT team or individuals tasked with updating the information in your DNS records:

When adding new DNS records, they will need to select a type, which is the first item shown on our records list. After a type is chosen, simply copy and paste the remaining values into the for configuration form: 

Notice that in some instances you may have to modify the values slightly when configuring them within your domain management service. In the example above, GoDaddy prompted an error when the exact host value ("gecko.adriantusk.com") was copied and pasted, whilst this was not an issue on AWS. Each provider will work slightly differently so you may be required to shift some of the details to fit their form. We also had to place the priority into a specific input field on GoDaddy as opposed to including it before the value.  

Verifying Senders

Another option would be to verify individual senders as opposed to a domain. Whilst we don't recommend this as crucial parts of the verification will be missing if this approach is followed (i.e. DKIM masking and Mail From Verification, both of which play a big part in helping stop your sent emails ending up in Junk/Spam folders) it is a fast alternative to get up and running in seconds. 

 Navigate to Settings > Verified Senders & Domains and use the options drop-down at the right of each sender record to 'send verification email'. 

You would need to check the respective inbox for an email from us and click on the link in the body of the email. You will be taken to the same area in settings and a success message will be shown at the top right to confirm the successful verification.

Enabling the new processor

Once you've verified your senders or domains, you'll be ready to switch over to the new processor. Simply switch on the toggle in Settings > Verified Senders & Domains and all your emails will be now processed via the same AWS infrastructure that hosts and processes your main data. 

Frequently Asked Questions:

What will happen to emails that we sent in the past?

All emails sent previously are still stored in the same place they always were, which means they will be accessible in reports, exports and messages just as they used to be.

Will we still be able to use the 'Send from the captured user' feature on form workflows?

This functionality will only be available and visible to users that have verified their domain. 

What happens if the sender is not verified and a workflow attempts to send an email using it?

The system will fall back on the default email sender configured in Settings > Account Settings. If the default email sender is not verified, the system will not be able to send the email and such records will be shown in the Messages section in gecko with the status of "Sender not verified"

Please share your feedback on this update by using the emojis below, contacting us through the live chat, logging a feature request through the 'Suggest a Feature' option in Gecko, or by emailing us on adrian@geckoengage.com 

Did this answer your question?