Below Bulk Sender

You sent the first newsletter. A few people replied. A few did not see it. One customer found it in spam.

Then you searched for email deliverability advice and found the same checklist everywhere, SPF, DKIM, DMARC, unsubscribe links, spam rate, 5,000 messages a day.

That checklist is not wrong. It is just written for someone else.

The common deliverability literature assumes a sender close to bulk volume. A technical founder with 40 subscribers, a three-week-old domain, and a mostly B2B list is in a different category. You may pass every bulk-sender requirement and still have poor newsletter deliverability, because the real risk is not formal noncompliance. It is weak trust, thin history, mixed domain reputation, and no useful diagnostic surface.

This is the content gap. Bulk-sender checklists explain how to satisfy rules at scale. They do not explain what decides email deliverability for startups before scale exists.

What Is Deliverability?

Email delivery means the receiving system accepted the message. Email deliverability means the message reached a useful place, usually the inbox, not spam, quarantine, or silent suppression.

That distinction matters. A platform can report that an email was delivered while the buyer never saw it. For a small B2B newsletter, that is the practical failure. The system did not reject you, but the relationship did not happen.

Deliverability is not one setting. It is an accumulated judgment. Mailbox providers look at authentication, sending behavior, domain history, recipient engagement, complaints, bounces, and the local policies of the receiving organization.

The founder mistake is treating deliverability as a launch checklist. It is closer to credit history. You can set up the paperwork in a day. You cannot manufacture trust at the same speed.

Bulk Sender Defined

Google defines a bulk sender as a sender that sends close to 5,000 or more messages to personal Gmail accounts in a 24-hour period. The details matter. Google says the count is across mail from the same primary domain, including subdomains, and gives an example where 2,500 messages from solarmora.com and 2,500 from promotions.solarmora.com make the sender bulk. See the Gmail sender FAQ.

Two points are often missed.

• The rule applies to personal Gmail accounts, not every mailbox that happens to be hosted by Google.
• Once a sender meets the bulk-sender criteria, Google says the classification is permanent. Changing practices later does not remove it.

This is why the standard advice can mislead a founder. If you send 40 emails to a list of work addresses, you are not experiencing the same operating environment as a sender pushing thousands of messages into personal Gmail every day.

Outside the threshold does not mean outside risk. It means outside the dashboard, outside most written guidance, and often outside escalation paths.

Shared Domains Hurt

The most expensive early setup is also the most common, one primary domain for the website, newsletter, product notifications, and cold outreach.

Because Google aggregates volume across a primary domain and its subdomains, the newsletter and the outreach machine are not cleanly separate in the way founders often assume. A subdomain can help with routing and operational separation, but it does not make the primary-domain relationship disappear for Gmail classification.

If the same root domain is used for cold outreach and a newsletter, the reputations can be linked. A complaint pattern from outreach can weaken confidence in the newsletter. Newsletter sends can contribute to volume. If the combined activity crosses Google’s bulk-sender criteria, that status does not expire, according to the Gmail sender FAQ.

There are three practical options.

• Use the primary company domain only for human correspondence and critical product mail.
• Use a subdomain for newsletter sending, accepting that it still sits under the same primary domain for some Google calculations.
• Use a separate sending domain for outreach, especially if outreach volume or targeting quality is uncertain.

None is free. Separate domains add DNS work, monitoring, and brand judgment. Subdomains are easier, but less isolated. What neither option can do is retroactively clean up a pattern that has already trained mailbox providers to distrust you.

If you are still below 1,000 subscribers, the cheapest time to separate risky motion from trusted motion is now.

B2B Is Different

Google states that its sender guidelines do not apply to messages sent to Google Workspace accounts, and that enforcement described in the FAQ applies to personal Gmail accounts. That line matters for B2B founders.

Your newsletter list is likely dominated by company addresses. Many of those companies may use Google Workspace, Microsoft 365, Proofpoint, Mimecast, or internal filtering rules. The public Gmail bulk-sender checklist is not the governing rulebook for those recipients. Their organization’s filtering policy is.

This does not mean authentication is optional. It means compliance with Gmail’s public bulk-sender requirements is only one layer. A work mailbox may apply stricter controls, custom quarantine rules, attachment policies, link reputation checks, impersonation detection, or vendor-specific scoring.

That is why one subscriber can receive the newsletter, another at the same company can miss it, and a third can find it quarantined. The sender did not necessarily change. The receiving environment did.

The practical response is narrower than founders want. You cannot optimize every company filter. You can authenticate correctly, use a stable From: identity, avoid sudden volume jumps, reduce link and tracking noise, ask early subscribers to reply, and read bounce messages carefully.

New Domains Struggle

Google’s FAQ defines a new domain in a way that captures many early-stage companies, a domain that has not previously sent more than 5,000 messages per day to personal Gmail accounts since January 1, 2024. Google also says enforcement progression for new domains is accelerated.

That does not mean a young domain is doomed. It means the system has little positive history and less patience for bad signals.

Warm-up is often discussed badly. It is not a ritual where sending more email magically creates safety. It is a controlled way to let a domain build ordinary, consistent, wanted mail patterns. The important words are controlled, consistent, and wanted.

Google also notes that the top-of-message unsubscribe link appears only for messages that pass automated eligibility checks, including gradual increases in sending volume. A visible unsubscribe control is not just a compliance feature. It can reduce spam complaints by giving recipients a less damaging way to leave.

If you are choosing between platforms, sending domain control and unsubscribe header support are not minor features. They determine how much of the trust layer you own. We cover the platform decision separately in beehiiv vs Substack for Software Founders.

One Complaint Matters

Google’s guidance is to keep the user-reported spam rate below 0.1 percent and avoid ever reaching 0.3 percent. The FAQ says spam rate is calculated daily.

That arithmetic looks different at small list size.

• One complaint from 40 recipients is 2.5 percent.
• One complaint from 200 recipients is 0.5 percent.
• One complaint from 1,000 recipients is 0.1 percent.

This does not mean one angry reader will destroy your domain. The published thresholds and mitigation processes are written for bulk senders, and low-volume senders may not see the number represented in a dashboard.

But the complaint is still a signal. At small scale, every negative signal is noisy, but it is not meaningless. The best response is not panic. It is list quality.

Do not import every contact you have ever met. Do not add sales prospects to a newsletter because they were in a CRM. Do not hide the unsubscribe path. The safest early list is small, explicit, and expecting the email.

No Dashboard Exists

Low-volume senders often want a diagnostic panel that explains what happened. Usually, they will not get one.

Google Postmaster Tools is useful when there is enough eligible volume to show patterns, but Google does not publish a single universal minimum in the FAQ. At 40 subscribers, you should assume the dashboard may be empty, delayed, or not useful.

Mitigation is also not designed for the smallest sender. Google’s FAQ describes escalation in the context of bulk senders meeting all requirements. If you are below the threshold, you should not build an operating plan around getting a human review.

Use humbler instruments.

• Send seed emails to personal Gmail, Outlook, Yahoo, and company accounts you control.
• Ask five trusted recipients where the message landed.
• Read bounce codes instead of relying only on platform dashboards.
• Watch replies, not opens, because open tracking is increasingly distorted.
• Keep a simple send log, date, list size, subject, platform, domain, and anomalies.

This is not sophisticated. It is proportionate. At early volume, judgment beats false precision.

Bounce Codes Translated

If Gmail rejects or temporarily defers mail, the error code is often more useful than a generic platform status. Google lists these codes in the Gmail sender FAQ.

• 4.7.23, temporary issue with missing or mismatched PTR. Check reverse DNS with the sending provider.
• 4.7.27, SPF did not pass. Confirm the sending service is included in the SPF record.
• 4.7.29, TLS is missing. Confirm the sender supports encrypted transport.
• 4.7.30, DKIM did not pass. Recheck the DKIM selector and DNS value.
• 4.7.31, DMARC is missing or not acceptable. Publish a DMARC record, often starting with p=none.
• 4.7.32, From: alignment failed. Align the visible From: domain with authenticated SPF or DKIM identity.
• 5.7.25, permanent PTR failure. Fix reverse DNS through the sending infrastructure provider.
• 5.7.27, permanent SPF failure. Correct SPF before sending again.
• 5.7.29, permanent TLS failure. Use a sending service with proper TLS.
• 5.7.30, permanent DKIM failure. Correct DKIM signing and DNS publication.

Temporary codes mean the message may be retried. Permanent codes mean you should stop and fix the configuration. Re-sending bad mail is not persistence. It is negative training data.

How Deliverability Works

A mailbox provider receives a message and asks a series of questions.

• Is this sender authenticated?
• Does the visible sender align with the technical sender?
• Has this domain sent wanted mail before?
• Are recipients opening, replying, deleting, ignoring, or reporting?
• Does the message resemble abuse seen elsewhere?
• Does this recipient organization have stricter local policy?

No single answer decides every outcome. A well-authenticated email from a new domain can still be filtered. A familiar sender can survive minor imperfections. A new sender has less margin.

For founders, this means the first ten sends matter. The list should be tighter than your ambition. The content should match the promise that caused people to subscribe. The sender identity should stay stable.

If you need the strategic publishing layer before the plumbing layer, start with How to Start a Newsletter That Wins Your First Customers.

How To Test

Testing deliverability at 40 subscribers is imperfect. Still, you can learn enough to avoid obvious failure.

1. Send to your own personal Gmail, Outlook, Yahoo, and business accounts.
2. Check inbox, promotions, spam, quarantine, and message headers.
3. Confirm SPF, DKIM, and DMARC pass in the received message.
4. Send to five real subscribers and ask where it landed.
5. Compare outcomes by provider and company domain.
6. Review bounces within 24 hours.

Avoid overreading seed tests. They are indicators, not verdicts. The goal is to catch broken authentication, obvious spam placement, and company-filter issues before you send to the whole list.

Calculating Deliverability Rate

There is no single deliverability rate that tells the truth. Most platforms show delivery rate, accepted messages divided by sent messages. That is not inbox placement.

For a small newsletter, track four numbers separately.

• Acceptance rate, delivered by the receiving server.
• Bounce rate, split between temporary and permanent failures.
• Observed inbox placement, based on seed and subscriber checks.
• Reply rate, the best early proxy for wanted mail.

If 40 messages are accepted, the platform may report 100 percent delivery. If 10 landed in spam, the business outcome is 75 percent useful placement. The second number is harder to measure, but closer to what matters.

Why Deliverability Matters

For an early-stage company, the newsletter is not a media asset first. It is a trust surface.

If the email does not arrive, the content strategy fails before it begins. If it arrives in spam, the brand is trained into the wrong context. If subscribers report it, mailbox providers receive a machine-readable vote against future contact.

This is why authentication is not plumbing in the narrow sense. It is trust expressed in DNS records, headers, and behavior.

The work is not to trick filters. The work is to make wanted mail legible to machines.

How To Improve

For a forty-subscriber setup, do the following in order.

1. Choose the sending domain deliberately. Keep cold outreach away from the domain you need people to trust.
2. Publish SPF for the actual sending service.
3. Enable DKIM and verify that it passes on received mail.
4. Publish DMARC, start with p=none, then plan a move toward stricter policy when reporting is clean.
5. Align the visible From: domain with authenticated SPF or DKIM identity.
6. Add RFC 8058 one-click List-Unsubscribe headers where your platform supports them. Google says a mailto link or body link alone does not satisfy the one-click requirement for bulk senders.
7. Honor unsubscribes within 48 hours, matching Google’s stated expectation for bulk senders.
8. Increase volume gradually, especially on a new domain.
9. Send only to people who knowingly subscribed or clearly expect the message.
10. Review bounce codes after every early send.

Some of these items are formal requirements only once you become a bulk sender. Do them early anyway. They are cheaper before the list grows, before multiple tools depend on the domain, and before a bad reputation becomes expensive to unwind.

Takeaway

The standard email deliverability checklist is built around Google bulk sender requirements. It is necessary reading, but incomplete for founders below the threshold.

At 40 subscribers, your risk is different. You have little domain history, no reliable dashboard, no practical escalation path, and a list governed mostly by company filters rather than public Gmail rules. One complaint is arithmetically large. One shared domain can connect your best relationship channel to your riskiest acquisition motion.

The fix is not complicated. Separate risky sending, authenticate correctly, align the From: domain, make unsubscribing easy, grow volume gradually, and watch real replies more closely than vanity metrics.

Email deliverability for startups is not about looking like a bulk sender. It is about becoming a trustworthy sender before scale makes the mistakes permanent.

If you want the infrastructure and editorial system built together, Better helps technical teams design the publishing layer, the operating cadence, and the trust mechanics behind it. See our newsletter infrastructure work.