Messaging · SMTP / IMAP · v1.0.0 · manifest schema 1.0
The lowest-common-denominator messaging transport. It serves the same `message.send` capability Slack and Discord do, which means a module that needs to tell a human something always has somewhere to send it even when no chat platform is installed. Inbound mail is triaged into the Communication Hub rather than into a separate inbox.
- Last sync
- 1h ago
- Health
- 62/100
- Rate ceiling
- 60/min
- Webhooks
- not supported
Add to the estate and begin the authentication handshake. Every operation is a state transition inside AI-EOS — no external service is contacted.
Health
62/10062/100 — 8% of calls failing, against a 2% degraded threshold. 1 further penalty applied.
- −30Error rate8% of calls failing, against a 2% degraded threshold.
- −8Rate ceilingPeak consumption reached 98% of the 60/min ceiling.
Authentication
Authenticated- Method
- Service Account
- Credential
svc_····862a- Last verified
- 4h ago
- Principal
- aeos-platform@email.svc
- Expires
- 721h
- Scopes held
- 2/2
mail.sendmail.read
- 1.InitiateThe Hub prepares a Service Account request for SMTP / IMAP.
- 2.Supply account emailEntered once. Held by reference — the Hub stores no credential material.
- 3.Supply private key referenceEntered once. Held by reference — the Hub stores no credential material.
- 4.Supply domain delegationEntered once. Held by reference — the Hub stores no credential material.
- 5.VerifyThe Hub performs one authenticated read to confirm the grant, then records the reference.
Nothing is contacted. The Hub stores no credential material — only a masked reference, the granted scopes and an expiry. There is no field on the auth record a secret could go in, which is a stronger guarantee than a policy of not putting one there.
Capabilities2
- Send mail
message.sendDeliver a notification to an external address.
- Receive mail
message.receiveTriage inbound mail into the Communication Hub.
Modules request capabilities, never connectors. A capability offered by two connectors gives the requesting module a fallback it does not have to know about.
Usage · 24h
Event Subscriptions3
- Approval Requested
approval.requestedA gate opened and is waiting on an executive seat.
Raised by workflows · see the fan-out chain
- Critical Recommendation
decision.criticalThe advisory layer raised something at critical priority.
Raised by decision-engine · see the fan-out chain
- Report Generated
report.generatedThe analytics layer produced a consolidated read.
Raised by intelligence · see the fan-out chain
Publisher
First party- Name
- AI-EOS
- Publisher ID
- aeos
- Platform vendor
- SMTP / IMAP
- Support
- operations@ai-eos.internal
Published by the platform itself. These manifests ship with the build rather than being fetched.
SMTP / IMAP owns the platform this plugin reaches. AI-EOS authored the manifest.
Version and changelog
Up to date- Installed
- 1.0.0
- Published
- 1.0.0
- Minimum platform
- 1.0.0
- Compatibility
- Compatible
- Manifest schema
- 1.0
- First published
- 16 months ago
Requires platform 1.0.0 or newer. This build is 1.0.0.
- 1.0.0major · 9 months ago
- First stable release. SMTP send and IMAP read against a service account.
- Subscribed to approval.requested so a gate reaches an inbox when a channel is not enough.
Permissions and scopes
viewer+AI-EOS permissions are what this plugin may do insidethe platform, resolved against the API Gateway’s own table. Scopes are what the external platform is asked to allow. They are different systems and neither substitutes for the other.
- company:read4 roles
Companies, departments, executives and the knowledge graph projection.
- workflow:read4 roles
Workflows, stages, tasks and approval gates.
- analytics:read4 roles
Enterprise Intelligence read models and the Decision Engine's outputs.
- mail.send
- mail.read
Dependencies0
Declares no dependencies. It can be installed against an empty estate.
Whether each is satisfied is resolved against the live estate at install time, not here.
Security
- Authentication
- Service Account
- Credential storage
- Never stored
- External scopes
- 2
- AI-EOS permissions
- 3
- Minimum role
- viewer
- Inbound deliveries
- Not accepted
- Tenant isolation
- Installation state is tenant-scoped
A plugin is a data literal. Nothing in the marketplace executes plugin code, and a plugin cannot bypass the Authentication Manager, the Integration Hub, the API Gateway or a permission check, because it has no code path — the host performs every transition.
The credential is referenced by a masked hint (svc_····862a) and nothing else. The auth state type has no field a credential fits in, so the guarantee is enforced by the type checker rather than by convention.
Privacy
- Data leaving AI-EOS
- 1 capabilities
- Data entering AI-EOS
- 1 capabilities
- Modules served
- 3
- Event topics received
- 3
Direction is declared per capability, so what this plugin can send and what it can receive are both enumerable rather than a matter of trust. It reaches only the modules listed above, and only through capabilities the Integration Hub resolves.
Documentation2
Logs4
- Gateway3h agoError rate at 8% over the trailing window. The gateway is applying backoff.
- Sync21m agoSynchronisation completed — 93,312 records reconciled in 24h.
- Gateway59m ago23,328 gateway calls in 24h at 306ms mean latency.
- Registry4d agoConnector v1.0.0 installed against manifest schema 1.0.
Roadmap
- Threading inbound replies onto the originating conversation
- DKIM and SPF posture surfaced on the connector health panel
What this connector would gain next. Mirrors the Future Integrations list every module carries in the Navigator registry.