justin 25f4a7503b warmup: IP rehab for .91-.93 so they can be reallocated ... The 3 IPs (mta02-04 / .91-.93) retired after the May 30-31 over-volume blast are NOT on any DNSBL (Spamhaus/Barracuda/SpamCop/SORBS all clean) and have clean PTRs + SPF/DKIM/DMARC -- the damage was provider-internal reputation, which recovers with slow clean sending. scripts/ip_rehab.py sends a tiny ramping trickle (10/IP/day -> cap 60) of genuine CAN-SPAM-compliant compliance check-in mail to clean business-domain, never-bounced recipients via dedicated heavily-throttled postfix transports rehab02/03/04 (30s/msg, bound to .91/.92/.93). Routing uses an X-PW-Rehab-IP header + header_checks FILTER to override the transport_maps randmap warmup rotation (verified: mail routes via rehab transports, status=sent). Daily cron pw-ip-rehab. After ~2-3 weeks of clean sending the IPs can be reallocated.		2026-06-09 20:27:47 -05:00
..
pw-hc-campaign	fix(warmup): HC cron logged to /var/log (deploy can't write) -> cron silently died	2026-06-09 16:06:28 -05:00
pw-hc-refresh	fix(warmup): HC cron logged to /var/log (deploy can't write) -> cron silently died	2026-06-09 16:06:28 -05:00
pw-ip-rehab	warmup: IP rehab for .91-.93 so they can be reallocated	2026-06-09 20:27:47 -05:00
pw-warmup-tg-alert	monitoring: daily warmup IP-reputation Telegram alert	2026-06-08 21:06:41 -05:00