Important Change to Email Sending from Incluziv Cloud
Incluziv Cloud is upgrading its email-sending infrastructure to improve email deliverability and help ensure important business emails reach your customers reliably.
From 15 November 2026, Gmail, Yahoo and similar common email accounts will no longer be supported as sending accounts.
Important Deadline
15 November 2026
Support for Gmail, Yahoo and similar common email accounts as sending accounts will be discontinued from:
15 November 2026
After this date, customers must use one of the following:
Incluziv-managed sending domain
or
Your own authenticated company domain
We are announcing this change well in advance so that customers who want to configure their own domain have sufficient time to complete the necessary technical setup.
Why Is Incluziv Making This Change?
Improving Email Deliverability
Email providers such as Gmail, Yahoo and Microsoft have strengthened their email authentication and anti-spam requirements.
When applications send business emails through regular mailbox accounts, receiving email providers may not recognise the application as an authorised sender.
This can result in important emails being:
-
Delivered to Spam or Junk
-
Delayed
-
Rejected
-
Blocked by recipient email servers
-
Incluziv Cloud is therefore moving to an authenticated email-delivery infrastructure designed for reliable system-generated business communications.
This applies to emails such as:
Invoices · Sales Orders · Purchase Orders · Payment Receipts · Statements · Quotations · Dispatch Notifications · Customer Alerts
What Is Changing?
From Common Mailbox Accounts to Authenticated Email Sending
Your Two Options
Option 1:
Incluziv-Managed Email Sending
For most customers, this will be the recommended and simplest option.
Incluziv Cloud will provide a common authenticated domain that will be used exclusively for sending system-generated notifications.
The email infrastructure behind this domain will be configured using modern sender-authentication and email-deliverability standards.
What happens to replies?
Your existing business email address can continue to be configured as the Reply-To address.
For example, an email may technically be sent through the Incluziv email-delivery domain, while replies from your customer can still be directed to:
or any other email address specified by you.
Advantages
-
No AWS setup required by you.
-
No DNS configuration required by you.
-
Better email authentication.
-
Reduced likelihood of emails being classified as spam.
-
Centralised email-delivery management by Incluziv Cloud.
-
Your regular email address can continue to receive customer replies.
Option 2:
Send Through Your Own Company Domain
Customers who want emails to originate from their own business domain can continue to do so.
For example:
or
However, the domain must be properly authenticated for application-based email sending.
What will be required?
You will need an Amazon Web Services (AWS) account and the required email service configuration.
Your domain administrator, IT team or domain provider will also need to configure the necessary DNS records.
These normally include:
SPF
SPF identifies which servers are authorised to send emails on behalf of your domain.
DKIM
DKIM digitally signs outgoing emails and allows receiving mail servers to confirm that an email genuinely originated from an authorised sender.
DMARC
DMARC defines how receiving email providers should handle emails that fail authentication checks and provides an additional layer of protection against domain spoofing.
Depending upon your existing email configuration, additional DNS entries may also be required.
The Incluziv Cloud team will provide the application-side configuration details required for connecting your authenticated email service with Incluziv Cloud.