Requested Feature:

Enable Breeze customers to publish DKIM CNAME records in their domain DNS (via SendGrid) so that outbound Breeze messages are DKIM-aligned with the customer’s domain.

Summary:

Breeze currently does not support publishing custom DKIM records for customer domains when sending via SendGrid. This creates alignment issues under DMARC policies set to p=reject.

Problem:

Our church enforces DMARC with p=reject to protect against spoofing.

While SPF passes (with include:sendgrid.net), DKIM fails alignment because Breeze does not provide custom DKIM records.

This forces customers to choose between:

1. Weakening DMARC (p=none or p=quarantine)

2. Sending from @breezechms.com instead of their own domain

3. Accepting delivery failures for legitimate messages

Impact:

- Weakening DMARC reduces email security, creating a false sense of protection.

- Sending from @breezechms.com reduces trust and trains recipients to accept mail from outside domains.

- Churches and nonprofits are frequent phishing targets; the lack of DKIM alignment makes us more vulnerable.

Why This Matters:

SendGrid natively supports custom DKIM records. The limitation appears to be in Breeze’s integration, not the underlying technology. Supporting DKIM for custom domains would:

- Improve deliverability for Breeze customers enforcing DMARC.

- Strengthen security for churches against spoofing and phishing.

- Provide Breeze with a strong marketing advantage as a platform that “takes email security seriously.”