"Lands in the inbox" — with the asterisk spelled out.
Every email provider claims great deliverability. Almost none explain what that means or
admit where their control ends. This page draws the line: what we do, what you do, and
what nobody on earth can promise.
The short version, before anything else
No provider can guarantee inbox placement. The receiving mail server makes
that decision, using signals it deliberately does not publish, and it weighs your content
and your recipients' behaviour alongside our infrastructure. What we can do — and do — is
make every controllable signal as strong as it can be. Anyone promising you more than that
is describing something that does not exist.
Division of labour
Who controls which half
Inbox placement is a score built from roughly two halves. Here is the split, without softening.
Ours: the infrastructure half
SPF — a tight sender policy listing only our own sending hosts.
DKIM — every outbound message cryptographically signed, keys rotated on schedule.
DMARC at p=reject — aligned, enforcing, with aggregate reports monitored.
Dedicated sending ranges — checked against major blocklists continuously.
Correct PTR and HELO — forward-confirmed reverse DNS on every sending host.
MTA-STS and TLS-RPT — enforced transport policy, published and reported.
An outbound abuse gate that suspends spammers rather than throttling them.
Yours: the behaviour half
Who you write to. Mail people expect gets opened; opens are the single strongest positive signal there is.
What it looks like. Wall-to-wall images, link shorteners and bulk-template markup all score against you.
How fast you ramp. A brand-new address sending 400 messages on day one looks exactly like a compromised account.
Whether people complain. One "mark as spam" outweighs a great deal of good behaviour.
Bounce hygiene. Repeatedly mailing dead addresses is one of the clearest bulk-sender tells.
Our part is fixed on day one. Yours compounds.
Authentication
What a receiving server checks first
Before any content is examined, the receiver runs three checks. Failing any one of them
is the most common reason ordinary, well-intentioned mail is filed as spam — and it is
entirely an infrastructure problem, which means it is ours.
SPF asks: is this IP allowed to send for this domain?
DKIM asks: does the signature prove the message was not altered in transit?
DMARC asks: do the domains in those two checks match the From: header — and if not, what does the domain owner want done about it?
inbox.my publishes p=reject, the strictest DMARC policy available. It means that
anyone forging mail from our domain gets it rejected outright rather than delivered to spam,
which protects both your recipients and the domain reputation you are buying into.
Why we ban bulk sending — and why that is the feature
The reason a shared domain can have good deliverability at all is that somebody is willing to say no.
01
Reputation is collective
Every inbox.my mailbox sends from the same domain and the same ranges. One customer running a cold-outreach campaign degrades placement for everybody else on the platform. There is no way to isolate the damage after the fact.
02
Suspension, not throttling
Rate-limiting a spammer just slows the damage. Our outbound gate scores every message leaving the platform and suspends the mailbox outright when it crosses the line. No refund, per the terms — and that is deliberate.
03
Listings get fixed, not dodged
If a sending IP is blocklisted, the account behind it is suspended and we file a delisting request. We do not rotate to a fresh IP and carry on — that is evasion, and it is how a domain's reputation dies permanently.
What counts as bulk
Newsletters, marketing campaigns, cold outreach, sales sequences, automated notification
blasts and any list you did not personally collect with explicit consent. inbox.my is a
personal mailbox — one human, writing to people who know them. If you need to send
campaigns, use a dedicated ESP built for it. Acceptable use policy →
Practical
Getting the best placement from your side
Five habits that matter more than any provider feature.
01
Warm up gently
Send normal, personal mail for the first couple of weeks. Do not migrate an address and immediately blast 200 contacts — that pattern is indistinguishable from a hijacked account.
02
Write like a person
Plain text or light HTML, real sentences, no link shorteners, no images-only messages, no all-caps subject lines. Bulk-template markup is a signal in itself.
03
Get replies early
Ask a few contacts to reply to your first messages. Two-way conversation from a new address is the strongest positive reputation signal available to you.
04
Tell people the address changed
Send the change-of-address note from the old mailbox, not the new one, and ask recipients to add you to their contacts. Contact-list membership overrides a great deal of filtering.
Questions
Deliverability questions, answered straight
Can you guarantee my email lands in the inbox?
No, and neither can anyone else. Placement is decided by the receiving mail server using signals it does not publish. We control sender authentication, IP reputation and abuse prevention — the largest controllable inputs. You control content, volume and whether people want your mail. Any provider promising guaranteed inbox placement is selling something that does not exist.
Why does email go to spam even when nothing is wrong with it?
Usually one of five things: failing SPF, DKIM or DMARC alignment; sending from an IP range with poor or absent reputation; content that pattern-matches bulk mail; a sudden volume jump from a cold address; or recipients marking similar mail as spam. The first two are infrastructure and ours to solve. The last three are behavioural and yours.
Does a dedicated sending IP actually help?
It gives you a reputation that reflects the mail genuinely sent through it, rather than one shared with millions of unrelated senders on a hyperscaler's pool. That only helps if the pool is kept clean — which is exactly why the no-bulk policy exists and why we suspend rather than throttle.
Can I use inbox.my for marketing or cold outreach?
No. Bulk sending is grounds for immediate suspension without refund. This is not squeamishness: one bulk sender degrades the reputation every other customer is paying for. The restriction is the product.
What if a recipient still cannot find my mail?
Ask them to check spam and mark it as "not spam", then add you to their contacts — that single action changes filtering for every future message. If a specific domain rejects our mail consistently, send us the bounce message: full SMTP responses are how we find and fix real routing problems.
Do you publish deliverability statistics?
Not yet, and we would rather admit that than quote a number we cannot substantiate. Placement rates are measured against seed lists that are themselves easy to game, so the industry's published figures are worth very little. What we will show you is our DNS configuration — which is public, verifiable, and the part that actually matters.
Good infrastructure, honestly described.
Every controllable signal, set correctly, on a domain kept clean by policy.