Gmail, DKIM, and DMARC

Why am I seeing a warning?

If you’ve connected a Gmail account to Jelly for sending, but the domain of your Jelly team address doesn’t match the domain of the connected Gmail account, you’ll see a warning in Email Setup. This is because of how Gmail handles email authentication.

What’s causing this?

Gmail uses DKIM (DomainKeys Identified Mail) to cryptographically sign outgoing messages. When Gmail signs an email, it always uses the domain of the Gmail account — not the domain in the “From” address.

For example:

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

In this case, Gmail signs outgoing messages with myothercompany.com, even though the “From” address says mycompany.com.

Why is this a problem?

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

Whether this actually causes problems depends on the recipient’s email provider and your domain’s DMARC policy. Many emails will go through fine, but some recipients may have issues.

What can I do?

Two options:

1. Match the domains — Ideally, your Jelly team address domain should match the domain of the connected Gmail account. If your team address is support@mycompany.com, connect a Gmail account on mycompany.com.

2. Send via Jelly instead of Gmail — If you can’t match the domains, you can switch to sending via Jelly instead. When Jelly sends on your behalf (rather than routing through Gmail), it signs messages with the correct DKIM for each address using your domain’s DNS verification.