justin/new-site
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

warmup: IP rehab for .91-.93 so they can be reallocated

Browse source 
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.
This commit is contained in:
justin 2026-06-09 20:27:47 -05:00
parent 6f361d307d
commit 25f4a7503b
2 changed files with 207 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

8
infra/cron/pw-ip-rehab Normal file
View file

@ -0,0 +1,8 @@
# IP reputation rehab for .91-.93 (mta02-04), retired after the May 30-31
# over-volume blast so they can be reallocated. Sends a small daily-ramping
# trickle (10/IP day0 -> +10/day -> cap 60/IP) of genuine compliance check-in
# mail to clean business/ISP-domain, never-bounced recipients via the heavily-
# throttled rehab02/03/04 postfix transports (30s/msg, bound to each IP). This
# rebuilds provider-internal reputation. Logs to /opt/performancewest/logs
# (deploy-owned -- a /var/log redirect would make cron silently fail).
30 8 * * 1-5 deploy cd /opt/performancewest && python3 scripts/ip_rehab.py >> /opt/performancewest/logs/pw-ip-rehab.log 2>&1