Yandex publishes a short list of mandatory rules for mailing lists: sign every message with DKIM, publish SPF, send from a permanent IP with reverse DNS, and make unsubscribing immediate. It sets no volume threshold, and it has no postmaster tool: the old Yandex Postoffice pages no longer exist.
| Applies to | Mailing lists sent to Yandex Mail users |
| Bulk threshold | None; the rules are for any mailing list |
| Authentication | DKIM on every message, and SPF; DMARC recommended |
| Unsubscribe | A List-Unsubscribe header that acts immediately |
| Postmaster tool | None today |
Check your domain against Yandex Mail’s rules
Enter the domain in your From address. What its DNS shows is tested here; for the rest, send one message to our email test.
What mailing lists need
Yandex writes its rules for mailing lists and marks these ones required; it sets no volume threshold. It says it may treat mail that breaks them as spam, or reject it.
- Every message signed with DKIM, and an SPF record published.
- The From address matching the user the server authenticated: a real mailbox, which — if a robot sends from it — replies with how to reach support.
- A permanent IP address with properly configured reverse DNS, and valid, public WHOIS for the domain.
- Explicit consent, with the address confirmed by its owner.
- Clear unsubscribe instructions in every message that work without logging in or registering, and take no more than 10 minutes.
- A List-Unsubscribe header (RFC 2369) that unsubscribes immediately.
- A bulk header such as Precedence: bulk.
- Addresses the server reports as non-existent removed.
What happens to mail that does not comply
Yandex reserves the right to treat mail that breaks the mandatory rules as spam or to reject it. When nothing but spam comes from a sender, Yandex blocks it for 24 hours.
| The rejection | What it means |
|---|---|
Message rejected under suspicion of SPAM | Yandex’s filters judged the message to be spam. |
Client host [IP] blocked using spamsource.mail.yandex.net | The sending IP is on Yandex’s own list of spam sources. |
Blocked by spam statistics | Only spam has come from this sender recently; it is blocked for 24 hours. |
Yandex Mail’s tools for senders
- Rules for mailing lists — Yandex’s requirements, each marked required or optional
- Yandex bounce messages — what each rejection means
Recommended, not required
- A DMARC record.
- An informative host name for the sending server, not an auto-generated one like dsl-4-3-2-1.provider.net.
- A separate server, or a subdomain such as news.example.com, for bulk mail.
- Messages formatted to RFC 5322 and MIME, with a valid Date and Message-ID; no JavaScript, no links written as IP addresses, and no link shorteners.
Common mistakes
- Looking for Yandex Postoffice: its pages no longer exist, and Yandex documents no postmaster tool or feedback loop in its place.
- An unsubscribe that asks for a login or password — Yandex requires one that works without.
- Sending from a dynamic IP, or one without reverse DNS.
Setting up the records? The exact SPF include and DKIM records for each service are in our email setup guides, and what each part of a record does is in SPF, DKIM and DMARC explained.
Questions
Does Yandex require DMARC?
No — it recommends it. Its mandatory rules are DKIM on every message and a published SPF record.
Is there a Yandex feedback loop?
Not one Yandex documents today. The Postoffice tool that used to offer sender statistics no longer exists.
Sources
Checked against Yandex Mail’s own documentation on 25 September 2026:
- Sending a large number of messages — yandex.com
- Report on non-delivery to Yandex — yandex.com
- Yandex Mail mailbox security — yandex.com