sync: auto-sync from GURU-KALI at 2026-05-26 19:41:06

Author: Mike Swanson
Machine: GURU-KALI
Timestamp: 2026-05-26 19:41:06
This commit is contained in:
2026-05-26 19:41:06 -07:00
parent e0dd370934
commit 15de6a7cf2
15 changed files with 64 additions and 39 deletions

View File

@@ -4,6 +4,8 @@ description: How outbound email routing works on Neptune Exchange - SBR agent, M
type: project
---
[INFO] Treat outbound routing breakage as systemic, not per-client. Multiple clients (devcon, Sorensen/rieussetcorp) have hit the same "email not routing from Neptune" symptom — likely a shared config/platform problem rather than isolated incidents. When a fix is applied for one client, check whether it needs replicating for the others.
## Neptune Outbound Email Routing Chain
1. User sends mail from Exchange mailbox on Neptune (172.16.3.11)
@@ -37,6 +39,8 @@ Neptune physically moved from ACG office (72.194.62.7) to Dataforth (67.206.163.
## Known Issues (as of 2026-03-22)
[STALE 2026-05-26 — these overnight TODOs are ~2 months old and were never reconciled; re-verify before acting.]
- 67.206.163.122 has no PTR record and is blacklisted by some providers
- SNAT rule may not be active — outbound was going as .122 not .124 on 3/16. Need to check UDM (192.168.0.254) — couldn't auth via SSH tonight, check in morning
- MAIL transport server still exists in Exchange config but server is decommissioned