top of page

Ensuring ChilliDB can send emails on your behalf

operations16

Updated: 12 minutes ago

This article is intended for system administrators. Follow the instructions below to ensure that emails sent from ChilliDB are successfully received by recipients.


Configuring Your Email Address

ChilliDB can send emails to your clients. To enable this, you need to create an email address for your contact record, typically in the format myname@mydomain.com.au. When your clients' mail servers receive an email from ChilliDB, they may verify whether ChilliDB is authorised to send emails on your behalf. If this verification fails, your emails may be rejected, resulting in bounced email replies.


Setting Up SPF Records

To prevent email rejection and authorise ChilliDB to send emails on behalf of your domain, you must create an SPF (Sender Policy Framework) record in your domain’s DNS settings.

Your SPF record should include the following entry:

v=spf1 include:smtp.chillidb.com -all

This ensures that ChilliDB is recognised as a legitimate sender for your domain.


Allowing ChilliDB to Send Emails to Your Organisation

Additionally, verify that your organisation’s mail server allows ChilliDB to send emails to your staff. If you send an email through ChilliDB to yourself, your mail server may reject it due to security settings. You may need to configure your mail server to trust ChilliDB's mail server (smtp.chillidb.com).


Configuring DKIM Records

To further enhance email security and deliverability, you must create the following two CNAME records in your domain:

Hostname: chillidb1._domainkey
Points to: chillidb1._domainkey.chillidb.com

Hostname: chillidb2._domainkey
Points to: chillidb2._domainkey.chillidb.com

Once these changes are applied, notify us so that we can begin signing your emails using the DKIM key.


Need Further Assistance?

If you require additional information or support, please log a request in the ChilliDB Helpdesk.

88 views0 comments

Recent Posts

See All

Comments


bottom of page