Domain verification is required for Quotilio.

Modified on Sun, 21 Jan 2024 at 10:01 AM

Hi User,


We have an important update for you regarding the DKIM settings verification for your domain. Starting from 10th February 2024, you will not be able to send quotes to your customers unless you verify your quote sender email and it's domain with us.


The DKIM verification ensures better deliverability and security for your customers' email clients (such as Gmail, Yahoo, etc.). It also prevents your emails from being reported as SPAM or COMPLAINT.


Gmail and Yahoo Mail have announced a new set of requirements for senders effective from February 2024, in order to safeguard user inboxes.


As our server uses AWS (Amazon Web Services)'s email messaging system, we are also enabling stricter email validation by DKIM/SPF/DMARC policy for all our customers, as mentioned in the AWS document here.


Please send us the following information to our support email (support@skylitech.com) by 10th February to get the DKIM settings for your domain:


- Domain Name: Your registered domain name from which your sender email is registered. For example, if you have set the quote sender email as john@example.com, then the domain name should be example.com. We need the domain name (example.com).

- Your store URL

- Your sender email (Registered in the Quotilio App).


After you send us the above information, we will send you the DKIM settings for your domain.


You need to add these DKIM settings to your Domain's DNS settings.


This way, your customers' email clients (i.e. Gmail, Yahoo, etc.) will verify that the incoming email (Quote email that you have sent) is actually from you (from your domain) and will not mark the email as SPAM or REJECTED.


  1. How the DKIM will help you? See the documentation here.

  2. How to add DKIM in your domain's DNS settings? See the documentation here


If you have any questions, please feel free to contact us at our Support email.








Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article