Gmail, DKIM, and DMARC

Some good-to-know details about email deliverability and Jelly when using Gmail.

Why am I seeing a warning about my Gmail address not matching my Jelly email address?

If you’ve connected your Gmail account to Jelly for sending emails, but your Jelly email address doesn’t match the domain of your Gmail address, you might encounter some email deliverability issues.

What’s causing this?

Gmail uses a security standard called DKIM (DomainKeys Identified Mail) to sign outgoing messages. When Gmail signs emails, it always uses the domain associated with your primary Gmail account — not the domain in your custom Jelly “From” address — even if you’ve configured Gmail to send emails from that custom address.

For example:

Your Jelly team address: me@mycompany.com
Your connected Gmail account address: support@myothercompany.com

In this scenario, Gmail will sign outgoing messages using the myothercompany.com domain, rather than mycompany.com.

Why is this a problem?

Many email services use DMARC (Domain-based Message Authentication, Reporting & Conformance) to verify that the sending domain (in your “From” address) matches the DKIM signature. When there’s a mismatch, DMARC can flag your email as suspicious, causing it to land in spam folders or be quarantined.

What can I do?

To avoid issues:

Ideally, your Jelly team address should match the domain of the connected Gmail account.
If you prefer to use a different domain, consider not using Gmail to send your messages, and instead send via Jelly’s default provider instead. Jelly can sign your messages using the correct domain for each address you add.

If you need help, we’re always here — just reach out!