new-site/infra/network/interfaces
justin 5d9306b75c mail: dedicate fresh IP .90 (mta01) to filings subdomain for clean reputation
Added a fresh sending IP (.90/mta01) bound to the filings cold-outreach stream,
isolated from the reputation-damaged .94 trucking IP:
- .90 bound on ens18, persisted 3 ways (interfaces up/down hooks + pw-mail-ips
  service + watchdog cron, all updated for the Jun-24-outage safety pattern)
- postfix 'outfilings' transport binds .90 / HELO mta01
- sender_dependent_default_transport_maps routes @filings.* -> outfilings; moved
  the randmap:{out05:} catch-all to default_transport=out05 so the sender map
  can win (recipient transport_maps outranks it otherwise)
- filings SPF updated to include .90

TEST RESULT: fresh IP fixed the reputation signal (Gmail error changed from
'low domain reputation' on .94 to 'likely unsolicited' cold-start on .90).
Non-Google (GMX/Microsoft) deliver fine; Gmail cold-start remains a slow wall.
Plan: CT campaign to non-Google first, warm .90, trickle Gmail over weeks.
2026-07-01 00:11:07 -05:00

40 lines
1.8 KiB
Text

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug ens18
iface ens18 inet static
address 207.174.124.71/23
address 207.174.124.72/23
# Mail sending IPs (consolidated 2026-06-23 to remove snowshoe footprint):
# .94 = mta05 -> trucking stream (out05)
# .107 = hcmta01 -> healthcare HOT stream (hcout1)
# The dormant rotation pool (.90-.93, .95-.106, .108-.109 / mta01-20,
# hcmta02-03) was removed: a 20-IP footprint reads as snowshoe spam and
# hurt domain reputation. To re-expand later, re-add the address lines
# here + the postfix transports (master.cf) + BOTH SPF records, SLOWLY
# (one IP at a time, days apart, only after Postmaster Tools shows green).
address 207.174.124.94/23
address 207.174.124.107/23
address 207.174.124.90/23 # filings subdomain (mta01) - fresh-reputation cold stream
# Secondary IPs: classic ifupdown only applies the FIRST address line, so
# bring these up explicitly (survives reboot; the bare address lines above
# are kept as documentation + for ifupdown2 compatibility).
up ip addr add 207.174.124.72/23 dev $IFACE || true
up ip addr add 207.174.124.94/23 dev $IFACE || true
up ip addr add 207.174.124.107/23 dev $IFACE || true
up ip addr add 207.174.124.90/23 dev $IFACE || true
down ip addr del 207.174.124.72/23 dev $IFACE || true
down ip addr del 207.174.124.94/23 dev $IFACE || true
down ip addr del 207.174.124.107/23 dev $IFACE || true
down ip addr del 207.174.124.90/23 dev $IFACE || true
gateway 207.174.124.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 8.8.8.8 8.8.4.4
dns-search performancewest.net