How SMEs Can Design Bulk Email Without Locking Themselves Into a Vendor

The short answer

For an SME sending bulk email to outside recipients, the realistic setup comes down to four points:

1. Send to each recipient individually - no big Bcc blast; one message per address
2. Own your subscriber state - keep active, unsubscribed, and bounced in your own DB
3. Accept unsubscribes automatically - put a link in the body and set the List-Unsubscribe header
4. Authenticate your sending domain - SPF / DKIM / DMARC / PTR / TLS, all in place

The point of “not depending on one specific service” is really about not handing the rules and state of your sending over to someone else.

Why a single Bcc blast isn’t enough

What you should keep in-house

State you own

• Subscriber data (email address, consent timestamp, source of consent, delivery category, unsubscribe state)
• Delivery rules (what goes to whom, at what rate, how bounces and unsubscribes feed back)
• Sender identity (sending domain, SPF/DKIM/DMARC, reply-to address, unsubscribe URL)

Things you can swap out

• The actual SMTP relay
• How the admin UI is built
• Where the send queue lives
• Where logs are stored

Minimum delivery stack (parts list)

1. Subscriber table - who you can send to
2. Suppression table - unsubscribes, hard bounces, complaints
3. Templates - subject, body (HTML/text), delivery category
4. Send queue - per-recipient state, send result, retry count
5. SMTP relay - your existing mail platform or your own server
6. Logs - who got what when, success/failure, suppression/bounce updates

Minimum fields for the subscriber table

Important: suppression always wins. Even if an address is still in your sales CRM, if the suppression table says unsubscribed, you don’t send. That rule needs to be hard-coded.

What to do at different volumes

Once a month, a few dozen recipients

• A merge-style template for outbound only
• Per-recipient sending
• Unsubscribe URL
• Send logs
• SPF / DKIM / DMARC in place

A few times a month, a few hundred recipients

• All of the above, plus a send queue, rate control, automatic bounce handling, and immediate unsubscribe processing
• A dedicated subdomain for sending
• Separate everyday human mail from promotional or announcement mail (e.g. billing@, notice@, news@)

Approaching a few thousand a day

At this scale, a dedicated service is often cheaper. Google now requires senders pushing more than 5,000 messages a day to Gmail to have SPF/DKIM/DMARC, one-click unsubscribe, and similar basics.

Legal and deliverability essentials you can’t skip

Consent

Promotional and marketing email generally requires prior consent. Keep evidence of:

• Consent timestamp
• Where it was collected
• What kind of mail it covers
• The wording shown to the recipient
• The screen or copy used to capture consent

Required disclosures

The footer needs:

• Sender’s name or company name
• Unsubscribe URL
• A statement that recipients can opt out
• Sender’s address
• A contact for complaints and inquiries

Authentication and deliverability

| Item | Minimum | |——|———| | Sending domain | SPF / DKIM / DMARC configured | | Sending server | A stable host with PTR records and TLS | | From / Reply-To | A real address that can receive replies | | Unsubscribe | Body link plus the List-Unsubscribe header | | List quality | Opt-in only; remove dead addresses | | Send rate | Ramp up steadily; don’t spike volume | | Monitoring | Watch bounces, spam rate, and complaints |

Common failures

• Sending normal human mail and promotional mail from the same address
• Tracking consent in a free-text memo field
• Handling unsubscribes manually by replying to email
• Dumping an old stack of business cards into the list
• Suddenly sending the largest batch you’ve ever sent
• Mixing promotional copy into transactional notifications
• Letting the customer CRM override the suppression table (suppression has to win)

Wrap-up

The real question isn’t “which button do I press?” It’s these five things:

• Per-recipient sending, not one big Bcc
• A subscriber table and a suppression table
• A flow that accepts unsubscribes automatically
• SPF / DKIM / DMARC / PTR / TLS
• Separating transactional mail from promotional mail

For a few dozen to a few hundred recipients per send, you can run this perfectly well without a dedicated service. The shortcut isn’t “blast it from a mail client” - it’s designing a small delivery system of your own.