# Fix email authentication for mail.ru

You are working on the DNS and mail configuration for mail.ru.
Measured by MailAuthWatch on 18 Oct 2026 from public DNS. Grade A (95/100).
Report: https://www.mailauthwatch.com/check/mail.ru

## What is published right now (do not assume anything else)
- SPF (TXT mail.ru): v=spf1 redirect=_spf.mail.ru   — valid, 1 of 10 lookups
- DMARC (TXT _dmarc.mail.ru): v=DMARC1;p=reject;rua=mailto:dmarc_rua@corp.mail.ru;
- DKIM: mail2._domainkey (1024-bit)
- MX: mxs.mail.ru  → Mail.ru
- Nameservers: ns2.mail.ru, ns1.mail.ru  → DNS host not recognised

## Tasks, in order of impact
### 1. One DKIM key is 1024-bit.
Why: Selector mail2._domainkey is under 2048 bits, which some receivers already downgrade. 
Rotate to a 2048-bit key at the sending service.

## Rules
- Publish exactly one SPF record; never add a second v=spf1 TXT.
- Do not remove any include: or ip4: you cannot account for; mail may depend on it.
- Do not set DMARC to p=reject in one step; stage through p=none → quarantine → reject.
- Show the planned DNS changes as a diff (record, old value, new value) before applying them.
- If you cannot access the DNS provider or Mail.ru, stop and say exactly what access you need.

## Verify
  dig +short TXT mail.ru
  dig +short TXT _dmarc.mail.ru
Then open https://www.mailauthwatch.com/check/mail.ru?fresh=1 and confirm:
  the grade is unchanged and no new issues appear. Target grade: A.

## Report back
List each record you changed (name, type, old value, new value), what you verified, and anything you could not do.