GivingTuesday is Dec 1: find the emails that will bounce before you send

GivingTuesday estimates US donors gave $4.0 billion on the day last year, up 13% from 2024. With numbers like that, any nonprofit would be tempted to email everyone on file: last year's donors, lapsed donors, the gala sign-up sheet, the list from the old CRM.

Mailbox providers don't like sudden jumps in volume, and sending platforms keep score on your bounces. Amazon says high bounce rates can send your email to the spam folder, which is a bad place for your biggest fundraising email of the year to land.

You have three weeks. That's enough time to find the bad addresses, save the donors worth saving, and warm up the older part of your list before December 1.

How many nonprofit emails bounce?

The best public number I've found on nonprofit email bounces comes from M+R Benchmarks. In 2025, 4% of nonprofit email subscribers at the start of the year became unreachable because of bounces, and another 12% unsubscribed. Disaster and international aid groups had it worse, at 6% and 21%.

On a list of 20,000, that 4% is 800 people a year you can no longer reach. M+R is counting list loss over a full year, though. The bounce rate on a single send is a different number, and it's the one platforms police.

The same study says the average subscriber got 50 emails in 2025, 31 of them fundraising appeals. That's good news for your active list, because it gets tested all the time. An address bounces, it gets suppressed (many sending platforms do this for you), and you move on.

The risk sits in the records that never got those 50 emails. Nobody has tested those addresses in a while, and on December 1 they'd all get tested at once.

Why is a GivingTuesday send riskier than a normal one?

In a normal week, you mail people who heard from you recently. GivingTuesday breaks that pattern, and the companies running the inboxes and sending platforms have been clear about what they'd rather see:

• Google tells senders to keep a steady rate, avoid bursts, and start with engaged people at low volume before building up. If messages start bouncing or getting deferred, it says to cut volume until the errors drop.
• Yahoo puts it this way: "Don't start sending daily emails to subscribers of your weekly or monthly mailing." That's a fair description of a lot of GivingTuesday countdowns.
• Amazon SES says that if you have to mail addresses you haven't contacted lately, keep them to a small part of your overall sending. It calls re-engagement campaigns risky because of bounces, complaints and spam traps.

Spam traps matter if your database goes back a long way. Amazon notes that some are old addresses that were once real and sat unused, and others are near-copies of real addresses with a typo in the domain. Even a few hits can hurt your reputation as a sender.

Aim for a hard bounce rate below 2%. HubSpot lists 5% as a reason to suspend an account, and the bounce rate guide covers what the other platforms say.

You can still email lapsed donors. Check them first, and send to them separately.

A three-week plan before December 1

Week of Nov 9: find out who's on the send

Pull the hard bounce rate for your last few campaigns, separate from soft bounces. If you send from Mailchimp, HubSpot or Marketing Cloud, the number lives there. Salesforce's own bounce fields only cover email sent through Salesforce with bounce management turned on.

If your donor data lives in Salesforce, our free 15-minute audit for nonprofits walks through the reports, including this year's donors with no address or a bounced email. Nothing gets installed in your org.

Then split the send in two: people who've opened or clicked recently, and everyone else. Pick a window that fits how often you mail. If you mail weekly, three months is a reasonable place to start.

While you're at it, ask whoever manages your DNS to confirm SPF, DKIM and DMARC. Gmail and Outlook both set stricter rules for senders above 5,000 messages a day, and your biggest day of the year may be the day you cross that line.

Week of Nov 16: check the segment you don't trust

Run "everyone else" through an email check. A proper one looks up the domain's mail servers, asks the receiving server whether the mailbox exists, and flags disposable addresses, role addresses and known spam traps. No message goes out, so your donors never see it.

Event sign-up sheets and paper forms are where a lot of bad addresses start. M3AAWG, the industry group that writes sender best practices, warns that without a confirmation step, typos and fake addresses get onto a list unchecked.

Then sort the results:

Look at role addresses by hand before you cut them, since info@ may be the only address you have for a family foundation or a congregation. Fix obvious typos like gmail.con, then check them again, and leave anything you'd have to guess at.

A bad email doesn't have to mean a lost donor. Export the mailing address and phone number alongside each failed record, and have someone contact the people who matter most, such as recent major donors and monthly givers, to ask for a current email. Your development team would much rather find this out in November.

Week of Nov 23: warm up with something that isn't an ask

Before Thanksgiving, send the checked segment a short email with no ask in it: a thank-you, a program update, what last year's gifts paid for. Send it in small batches over a couple of days. Yahoo also suggests asking inactive subscribers to reconfirm from time to time, and this is a good moment for it.

Remove hard bounces the same day, then look at the rate. If this segment comes back above 2%, keep it out of December 1. Leaving some lapsed donors out of one send costs you far less than dragging down the email to people who gave last month.

December 1: send in stages

Mail your engaged list first. Once you've looked at the bounces on that send, mail the older segment later in the day, in a smaller batch. If your countdown means more email than this list usually gets, save the extra sends for your engaged list. If errors climb, slow down, as Google advises.

From December 2: clean up before year-end

Remove hard bounces as soon as the day's sends finish. For soft bounces, M3AAWG's rule of thumb is to drop an address after two bounces in a row over two weeks or more.

Do this before the year-end appeals and receipts go out. A donor who gives $250 or more in a single gift needs a written acknowledgment to claim the deduction, and the IRS says email is an acceptable way to send it. A receipt that bounces in December is easy to miss, and it can turn into a confused phone call in April.

What email validation won't fix

Validation tells you a mailbox can receive mail. It can't tell you the person behind it still wants to hear from you.

A lapsed donor with a perfectly valid address can still hit the spam button, and Gmail wants your spam rate below 0.10%. Amazon's advice is not to buy, rent or share email addresses, and I'd count list swaps with partner organizations in that.

Validation also can't confirm every mailbox on a domain that accepts all mail, so those results belong in their own segment.

Where DQVerify fits

DQVerify email validation works on a CSV: upload your list, map the email column, and get a result code and risk score on every row. Files under 50,000 rows typically finish in under ten minutes. Download your results during your session, because batch files are deleted afterwards.

If you're on Salesforce, export a report with Contact IDs, check the file, and bring the results back with the Data Import Wizard or Data Loader. The native connector comes with Enterprise plans.

Each email check uses one credit. Packs start at $275 for 20,000 credits, about $0.014 per address, with no subscription. You can start with 100 free credits (1,000 if you sign up by November 30, 2026) for 14 days, no credit card, business email required. Try it on your oldest segment first, since that's where you'll see the most.

Email checks run on DQE Software SAS infrastructure in France, and we don't store your validation data.

So when did anyone last email the oldest segment on your GivingTuesday list? If nobody on your team can say, start there.