Session log update: jlohr forward confirmed, ntirety DNS context added (2026-05-12)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

clients/dataforth/session-logs/2026-05-12-session.md

@@ -134,3 +134,30 @@ POST https://outlook.office365.com/adminapi/beta/{tenant}/InvokeCommand
 | Customer | Dataforth Corp (id: 578095) |
 | Status | Customer Reply (unchanged this session) |
 | Comment added | ID 410543322, 2026-05-12 10:33 AM MST |
+| Comment added | ID 410550508, 2026-05-12 11:08 AM MST — forward delivery confirmed |
+
+---
+
+## Update: 11:08 MST
+
+### Forward Delivery Confirmed
+
+Third ntirety.com test email triggered after inbox rule was re-created and outbound spam exception was in place:
+
+- ntirety.com email arrived at jlohr@dataforth.com: 17:58:33 UTC
+- Inbox rule fired, forwarded as FW: to mike@azcomputerguru.com: 17:58:47 UTC (14 seconds)
+- Dataforth outbound trace status: **Delivered**
+
+Forward is fully operational. Ticket #32142 updated with confirmation comment (ID 410550508).
+
+### Infrastructure Context Documented
+
+Clarification from Mike: the jlohr forward was set up specifically to receive infrastructure notifications from ntirety.com, which hosts Dataforth's public DNS (dataforth.com zone). DNS changes go through the ntirety portal — not a registrar panel.
+
+Docs updated to capture this:
+- `clients/dataforth/docs/overview.md` — DNS Host: ntirety.com added to Environment Summary
+- `clients/dataforth/docs/active-directory.md` — jlohr row updated with ntirety DNS context
+
+### Defunct Transport Rule
+
+The transport rule "Forward ntirety.com to jlohr -> Mike Swanson" (BlindCopyTo) remains in place but is non-functional — blocked by INKY PhishFence StopProcessingRules action. Candidate for cleanup.