- Order confirmations must always arrive; newsletters can tolerate losses.
- Treating both as ordinary email from one mailbox drags critical messages down to marketing-grade delivery.
- Here is how to separate the streams.
Every business sends two fundamentally different kinds of email. Transactional messages — order confirmations, password resets, invoices, booking tickets — are triggered by a user action and must arrive, every time, instantly. Bulk messages — newsletters, offers, announcements — go to many people at once and can tolerate imperfect delivery. Mixing the two on one mailbox or one server is one of the most common and damaging email mistakes we see in Nepal.
Why the Distinction Matters to Filters
Inbox providers score senders. Bulk mail inevitably accumulates some spam complaints and dead-address bounces — that is the nature of lists. When bulk mail shares infrastructure with transactional mail, its complaints damage the shared reputation, and suddenly password resets and eSewa payment confirmations start landing in spam. Users blame your business, not the filter.
The Rules for Each Stream
| Aspect | Transactional | Bulk / marketing |
|---|---|---|
| Consent | Implied by the transaction | Explicit opt-in required |
| Unsubscribe link | Not required | Mandatory, one-click |
| Infrastructure | SMTP/API service or app server | Newsletter platform |
| Sending domain | mail.yourdomain or main domain | news.yourdomain subdomain |
The Recommended Architecture
- Staff correspondence: normal business email hosting — Zoho, Google Workspace or cPanel mailboxes.
- Transactional: your website or app sends through a transactional email API or authenticated SMTP relay, from an address like noreply@ or billing@ on your main domain, fully covered by SPF and DKIM.
- Bulk: a newsletter platform sending from a subdomain such as news.yourdomain.com.np with its own DKIM. If the subdomain reputation ever suffers, your main domain and transactional mail stay clean.
Signs You Have a Mixing Problem
- Marketing blasts go out from info@ through the office mail server.
- Password resets started hitting spam after a big campaign.
- Your one shared IP shows on a blocklist after every newsletter.
- Staff mail slows to a crawl on the first of the month when statements go out.
Any of these means the streams need separating — usually a one-day project with immediate results.
Why the Subdomain Isolation Trick Works
Sending reputation is tracked separately for a subdomain and its parent domain in most modern filtering systems — this is precisely why routing bulk mail through news.yourdomain.com.np rather than yourdomain.com.np directly isolates the risk. If the newsletter subdomain accumulates spam complaints from an aggressive campaign or a stale list, filters degrade trust in that specific subdomain without automatically extending the same penalty to the root domain handling staff correspondence and transactional mail. This is a deliberate architectural choice, not an accident of DNS structure, and it is the single highest-leverage change available to a business currently sending everything from one identity.
Frequently Asked Questions
Is an invoice with a promotional footer still transactional?
Mostly yes if the primary purpose is the invoice, but heavy promotion inside transactional mail invites reclassification by filters — keep it minimal.
Can small businesses skip the separation?
Under a few hundred marketing messages a month the risk is modest, but the subdomain habit costs nothing and scales safely.
What volume counts as bulk to Gmail?
Google applies bulk-sender rules from roughly 5,000 messages a day to Gmail addresses, but authentication and unsubscribe rules are best treated as universal.
We architect all three streams for clients — start with business email, add hosting with SMTP support, or ask for a sending architecture review.
