Emails Bouncing or Being Sent to Spam

Before you dig in

Experiencing multiple emails bouncing or going to spam? Look for the Alternate Sending suggestion further down in this article — it's our fastest fix.

Viewing your Email History

Permissions: You must be the Account Owner or have role-based access to History to view Church Management Settings > User Activity within your Breeze account.
  1. Click on Church Management Settings (the gear icon), select User Activity from the dropdown menu, and then click the Email tab on the left-hand side.
  2. View your metrics. Click into any sent or failed email record to view detailed performance metrics. You can easily see if a message was Delivered, Opened, or Dropped. (Note: you can view these metrics by clicking directly on the record or by clicking the edit icon.)

Tip: use the search bar to filter history down to a specific person if you're chasing one recipient's issue. Your email history also includes automated system emails, like form confirmations and volunteer schedules, in addition to messages you sent yourself.


What your status means

Find the status shown for your message in the table below.

Status What it means What to do
Delivered Reached the recipient's mail provider. If someone says they aren't receiving emails even though it shows Delivered, we've confirmed it sent — it likely landed in a spam or promotions folder. Have them mark it as safe or add the sender to their important/safe senders list.
Scheduled Queued to send — either scheduled by you or sent via "Send Now" and briefly waiting in the queue. No action needed. If it's well past the scheduled time, check Optimizing Email Delivery Times for expected queue delays during high-volume periods.
Invalid Address The account doesn't exist. Double-check the spelling.
Unsubscribed The recipient is on our provider's Global Suppression List — added by an unsubscribe click or a block from their own inbox. Have them resubscribe themselves at krm.tithely.com/resubscribe, or enter their email there for them to start the resubscribe process.
Bounced Usually the account doesn't exist. Occasionally the provider flagged it as spam ("Dropped" in the metrics detail means it was actively rejected). Verify the address is correct. If it is, see Alternate Sending below.
Processing This is in our queue to send. Please don't resend or redeliver the message if you see it in Processing — it's already on its way.
Landing in spam specifically? Suggest that your recipient find this message in their spam folder and mark it as safe. Another way to do this is to create a filter for *@mail.breezechms.com and set it to never send to spam. This is decided entirely by the recipient's inbox provider, so it's the one lever they control directly. For a universal setting change that improves email deliverability, see Alternate Sending below.

Fastest fix

Finding multiple emails bouncing or going to spam? Our fastest fix is Alternate Sending.

What it does: Alternate Sending routes your outgoing mail through a Breeze-owned domain (e.g., john.doe_rt+gmail@mail.breezechms.com) instead of sending it as if it came directly from your own address. Replies still land in your normal inbox — we handle the reply-to address, so nothing changes for the recipient. This resolves the large majority of bounce and failure cases, especially for anyone sending from a private domain.

Who needs to contact us: An admin or account owner of your organization should message us in the chat widget in the bottom right-hand corner of their screen when logged in, and ask us to enable Alternate Sending. It takes our team a couple of minutes, and it can be turned off just as easily if needed.


How to use the unsubscribe portal

If a recipient was unsubscribed and wants to start receiving emails again, send them to krm.tithely.com/resubscribe.

  1. Start receiving emails again. On the page, they'll enter their email address and we'll send a link to confirm they want to resubscribe.
  2. They enter their email address, then click Send me a confirmation link.
  3. They follow the prompts in the email they receive. If they weren't actually unsubscribed, the confirmation will tell them their email is already active.

This only re-enables email delivery to that address — it doesn't change which churches or organizations email them.

Suggested practices for resubscribe requests

We recommend putting the resubscribe link on your website or app so members can opt themselves back in whenever they realize they've stopped receiving your emails. It's also worth adding to your email templates — footers are a good spot — so anyone reaching out from an old or previously unsubscribed address can find it and resubscribe on their own.

It's best for a member to start the resubscribe process themselves. That said, an admin can kick it off on a member's behalf by entering their email address in the portal. Per CAN-SPAM requirements, only the member can actually complete the resubscribe — but once you've submitted their email, they'll receive a helpful email walking them through the next step.


More detail, if you want it

The fix above works the same way no matter where you send from. The sections below go deeper on domain setup, DMARC alignment, and timing questions, for anyone who wants the fuller picture.

Public vs. private domains: what changes

Sending from a public email account (Gmail, Yahoo, AOL, Comcast, etc.)

When Breeze sends on behalf of a public address, the recipient's mail server can tell the message didn't actually originate from Gmail's (or Yahoo's, etc.) own servers — even though it says it's from you. That mismatch is what triggers a lot of the bounce and spam-flagging behavior in the first place.

Recommended Enable Alternate Sending (see above). No technical setup, no domain changes.
Alternative — bigger lift Move your email account to a private domain (e.g., from john@gmail.com to john@yourchurch.org). This lets you authorize Breeze to send on your domain's behalf directly through DNS settings, but it's a heavier change than most people need — Alternate Sending solves the same core problem without it.

Sending from a private domain (you@yourchurch.org)

Private domains give you more control since you manage your own DNS — but that control doesn't automatically mean better deliverability, and it isn't required to fix bouncing.

Recommended Alternate Sending still helps here too, and it requires nothing from your technical admin.
Optional Your technical admin can add an SPF record authorizing our mail servers (see the SPF section below). Keep in mind that if DMARC or DKIM enforcement is already active on your domain, those settings override SPF, so this step alone often won't move the needle.
A quick note on SPF records

An SPF record tells other mail servers which systems are allowed to send email on your domain's behalf. If your technical admin wants to add ours, the value to include is:

include:sendgrid.net

If you already have an SPF record, add this to your existing one rather than creating a second record.

SPF is only one piece of email authentication, and it's commonly overridden by DMARC/DKIM settings if your domain has those enforced — which is increasingly common. If emails are still having trouble after adding this, that's usually why.

If you're dealing with a DMARC alignment failure specifically, see the section below — SPF won't resolve that one.

Why does my email security tool (DMARC) flag Breeze emails?

If your organization uses an email security monitoring tool (Valimail, Dmarcian, or similar), you may see Breeze emails flagged as failing an "alignment" check. This is expected behavior, not a misconfiguration on your part.

Why it happens: DMARC alignment checks that emails claiming to be "from" your domain were actually authorized by your domain. Breeze sends on your behalf through a shared sending system (SendGrid), so the underlying authentication belongs to Breeze's domain, not your church's. Your monitoring tool sees that mismatch and flags it.

Can we add custom DNS records per church? Not currently. Per-account DKIM/CNAME configuration isn't something our platform supports today.

Does adding the SPF record fix it? No — if DMARC alignment is specifically what you're trying to resolve, adding sendgrid.net to your SPF record won't fix it, and can push you toward your domain's maximum allowed DNS lookups with no benefit. Skip that step if alignment is your concern.

What we recommend:Alternate Sending. Once emails come from Breeze's own domain instead of appearing to come from yours, the alignment mismatch goes away entirely from your security reports. No DNS changes or IT work required — just ask us in chat.

More questions about email status and timing

Why is my email stuck in "Processing"?

This is normal during high-traffic periods. It means your email is safely queued and will send once the system reaches your place in line. Avoid clicking "Send" a second time — that can cause duplicate messages to go out.

Why is my email delayed?

Breeze processes email in a controlled queue to protect deliverability across thousands of churches sending at once. Volume is heaviest on Thursdays (the default day for volunteer reminders and weekend announcements), though delays haven't peaked above 30 minutes as we've been working to improve queue times.

How can I avoid delays?

  • Schedule emails for Tuesday or Wednesday instead of Thursday when possible.
  • If you need an email delivered by a specific time on a Thursday, schedule it about 30 minutes early to account for queue time.
  • Use "Send Later" rather than sending the instant content is ready.

Why don't you just send every email at once?

Sending a large volume of email in the same instant is a red flag to ISPs and can hurt sender reputation. Throttling the queue during peak times helps ensure email lands in the inbox instead of spam.

Why am I seeing volunteer schedules or form confirmations in my email history?

Email History captures all automated emails Breeze generates on your behalf, in addition to messages you send directly — this includes form sign-up confirmations and volunteer schedules, giving you a complete picture of your church's communications.

My email only has an image in it — will that cause a problem?

Yes. An email with only an image and no text can fail to send. Add at least a line of text alongside any graphic before sending.