claudetools/.claude/memory/project_dataforth_email.md at 449b7b51d5233bcf91f48f274ee0a0b4bdeea7a0

Files

Mike Swanson f8ed03c75a sync: auto-sync from GURU-5070 at 2026-06-02 07:25:49

Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-02 07:25:49

2026-06-02 07:25:55 -07:00

1.2 KiB

Raw Blame History

name, description, type, originSessionId

name	description	type	originSessionId
Dataforth email infrastructure	Dataforth uses M365 for email; the Exchange server on 172.16.x.x / neptune.acghosting.com is NOT Dataforth's — it belongs to ACG's own infrastructure	project	7034be43-1464-4085-b765-dc1226b1f8e0

Dataforth's email runs on Microsoft 365 (sysadmin@dataforth.com, tenant in vault at clients/dataforth/m365.sops.yaml).

The Exchange server at neptune.acghosting.com / 67.206.163.124 listed in the vault under clients/dataforth/neptune-exchange.sops.yaml is not part of Dataforth's infrastructure — do not use it for Dataforth email workflows.

Why: Mike corrected this during pipeline notification work (2026-04-22). The Exchange entry is an ACG-side server, not Dataforth's.

How to apply: For any Dataforth email sending, SMTP basic auth is disabled on the tenant. Must use OAuth2 — either XOAUTH2 over SMTP or (preferred) Microsoft Graph API POST /v1.0/users/sysadmin@dataforth.com/sendMail with a client_credentials token. Entra app is in vault at clients/dataforth/m365.sops.yaml under credentials.entra-app. Verify Mail.Send application permission is granted before use.

1.2 KiB Raw Blame History

1.2 KiB

Raw Blame History