Skip to Content
Browse documentation

UAPP Email

Manage hosting-account mailboxes, autoresponders, filters, forwarding, distribution, routing, delivery tracking and SMTP relays in Eenos UAPP.

Open Hosting → Email. The sidebar requires the Email feature and detected Exim availability. Mailing Lists additionally requires the Mailman feature and component; Delivery Tracking and SMTP Smart Host have their own visibility switches and backend availability checks.

MenuGuide
Email AccountsManage mailboxes
Create Email AccountCreate a mailbox
AutorespondersSchedule automatic replies
ForwardersRoute an address elsewhere
Email FiltersMailbox-level rules
Domain FiltersDomain-level rules
Email PipesDeliver to a program
Distribution ListsMaintain simple recipient groups
Email Delivery TrackingInspect delivery events
SMTP Smart HostConfigure an outbound domain relay
Mail Exchange ServerChoose local or remote routing
Mailing ListsManage Mailman lists

Scope and requirements

Manage only domains and mail resources belonging to the signed-in hosting account. Mailbox and mailing-list creation check their plan allowances and reject address collisions. Available domain selections exclude wildcard entries where a concrete mailbox domain is needed.

Hosting a domain does not establish correct public MX, SPF, DKIM, DMARC or client settings. Verify DNS and actual inbound/outbound delivery separately. Mail Exchange Server controls local/remote routing; SMTP Smart Host controls outbound relay policy.

Demo and operational behavior

Demo restrictions vary. Autoresponders, filters and smart-host mutations are explicitly blocked. Mailbox creation and password changes substitute a generated password and can still submit. Mailbox delete/quota/status changes, forwarder/pipe creation, distribution creation/member addition, exchange changes and some Mailman actions lack an explicit demo guard in their views. Several delete actions do block demo requests. Read each guide and treat submissions as live operations rather than previews.

Preserve mail and routing before destructive changes

Record the intended address, domain and effect. Back up required mailbox content before deletion, avoid forwarding/filter loops and verify the result after saving. A successful configuration message is not proof of delivery or recipient inbox placement.

Do not expose passwords, relay credentials, private message subjects or recipient details in shared screenshots and reports.