docs: mark MX-exclusion plan Fix 1 + Fix 3 shipped
Fix 1 (consumer mx: exclusion) and Fix 3 (pw-mx-tag cron) live as of 9eeed47.
Verified: warmup pool 353,909 after fix (not starved), mx:yahoodns.net cap=0
during warmup, cron tags idempotently. Fix 2 (NULL bucket cap) deferred.
This commit is contained in:
parent
9eeed47c4b
commit
b7cce370d7
1 changed files with 14 additions and 1 deletions
|
|
@ -1,11 +1,24 @@
|
|||
# Plan: close the MX-exclusion gaps in the trucking warmup
|
||||
|
||||
**Status:** PROPOSED (2026-06-20). Analysis + design only; no code shipped yet.
|
||||
**Status:** Fix 1 + Fix 3 SHIPPED 2026-06-20 (commit `9eeed47`); Fix 2 deferred.
|
||||
**Owner context:** warmup day 17; big operators (Google/Microsoft/Proofpoint/
|
||||
Mimecast/Barracuda/Cisco/Broadcom) are EXCLUDED until day 30, then re-introduced
|
||||
via `mx_daily_caps()`. This plan fixes three holes that let throttling/consumer
|
||||
MX operators through during that window.
|
||||
|
||||
## What shipped (2026-06-20, commit `9eeed47`)
|
||||
- **Fix 1 (DONE):** `CONSUMER_MX_OPERATORS` (mx:yahoodns.net, mx:icloud.com,
|
||||
comcast/charter/centurylink/windstream/tds/earthlink) folded into
|
||||
`WARMUP_EXCLUDE_OPERATORS`, used by both the `fetch_carriers()` exclusion SQL
|
||||
and `mx_daily_caps()` (same day-30 ramp). Verified live: warmup-eligible pool
|
||||
= 353,909 carriers after the fix (not starved), and `mx_daily_caps()` returns
|
||||
cap 0 for mx:yahoodns.net during warmup.
|
||||
- **Fix 3 (DONE):** `infra/cron/pw-mx-tag` installed to `/etc/cron.d/` (05:45 UTC
|
||||
daily, `--only-unsent --limit-domains 20000`). Verified: a 200-domain test run
|
||||
tagged 216 domains; idempotent/bounded.
|
||||
- **Fix 2 (DEFERRED):** bounding the NULL bucket cap — the cron will drain the
|
||||
backlog, revisit if NULL stays large.
|
||||
|
||||
---
|
||||
|
||||
## Background: how the two MX layers work today
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue