Open Email Server
In the EPAdmin administrator workspace, open Email Server or search the exact tool label. Server mail status differs from Customer owned-domain tools and configured notification SMTP. Read the detailed operational guide before making changes. The table lists every requested leaf in this group. A connected destination remains subject to current local permissions, resource ownership, installed capability, licence and fresh verification. It is not a production acceptance claim.
Complete tool reference
| Tool | Destination and behavior | Permission or limitation |
|---|---|---|
| Mail Server Configuration | Unavailable in this checkpoint | Typed global Postfix/Dovecot configuration is not implemented. Existing mail status and queue inspection remain available. |
| SMTP Settings | Unavailable in this checkpoint | Global hosting SMTP service tuning is not implemented. Notification SMTP is a separate existing setting. |
| IMAP / POP3 Services | Server → Builder; server services section | Any listed local Admin grant: server:read, server:manage |
| Mail Queue Manager | Server → Mail | Any listed local Admin grant: hosting:read, hosting:manage |
| Email Deliverability | Unavailable in this checkpoint | Administrator-scoped domain deliverability controls are not mounted in the server mail workspace. Customer owned-domain deliverability exists separately. |
| SPF / DKIM / DMARC | Unavailable in this checkpoint | Administrator-scoped SPF/DKIM/DMARC domain controls are not mounted. The server mail workspace provides service/queue evidence and sending limits only. |
| Spam Filtering | Unavailable in this checkpoint | Customer domain spam policies exist; global mail-server spam defaults and tuning are not implemented. |
| Mail Logs | ServerLogs → Services | Any listed local Admin grant: server:read, server:manage |
| Email Routing | Unavailable in this checkpoint | Customer local/external domain routing exists. Global mail-server routing configuration is not implemented. |
| Outgoing Mail Limits | Server → Mail | Any listed local Admin grant: hosting:read, hosting:manage |
Make and verify a change
Select the intended owned resource and load its current detail. Read impact, current revision, applicable preview and confirmation before an explicit submission. If the server requires fresh authentication, complete its password/MFA flow and submit the reviewed request again; no write is automatically replayed. Keep the durable operation ID and inspect the final resource/service state.
When a tool is missing or denied
Check the current role/grants, installed version and actual capability. A menu label marked unavailable has no supported action to force. Source updates can be newer than your installed kit; they do not automatically add hosting acceptance. Preserve the safe operation/correlation reference and inspect original state before retrying an interrupted change. Do not disable confinement, modify private journals or substitute another account to bypass denial.