Documentation
The mail system integrated into the workspace
Every VIGIL-MESH workspace comes with a mail system: mailboxes organized into folders, outbound email, aliases that redirect one address to another, and webhooks that notify your applications when a message arrives. This page describes what Mail can do today and how it fits with the rest of the platform. It stays factual: the functions described are the ones that exist, with no promise of perfect deliverability or turnkey compliance.
Mailboxes and folders
A mailbox is the arrival point for an address's messages. Inside it, folders organize the mail: the usual system folders (inbox, sent, drafts, trash, junk) are present out of the box, and you can create others to file by project, by client or by incoming stream.
One mailbox per address
Each workspace address receives into its own mailbox. Aliases, on the other hand, do not create a mailbox: they deliver into an existing one (see the Aliases section).
System folders and free folders
Inbox, sent, drafts, trash and junk are provided; the folders you create serve your own filing and can be nested.
Moving and reading
A message can be moved from one folder to another, marked read or unread, and deleted to the trash before permanent removal.
Sending
Sending goes from a workspace address to one or more recipients, with a subject, a body and carbon-copy recipients. A draft can be prepared and sent later; once it has gone out, the message is kept in the sent folder of the originating mailbox.
- 1Choose the sending addressThe sender is a workspace address. It is the one that carries the sending reputation and appears in the message headers.
- 2Compose the messageSubject, body, primary and carbon-copy recipients. A saved draft remains editable until it is sent.
- 3Send and keep the traceThe outgoing message is placed in the sent folder. If the remote server rejects it, the failure is surfaced to you rather than silently ignored.
Aliases
An alias is an address that has no mailbox of its own: it redirects incoming mail to one or more real workspace addresses. It is the simple way to expose service addresses (contact, billing, support) without multiplying mailboxes or accounts.
| Notion | What it is | Behavior |
|---|---|---|
| Mailbox | Address with its own storage | Receives and keeps messages in its folders |
| Alias | Address without storage | Redirects incoming messages to one or more mailboxes |
| Service address | Alias meant to be shared (e.g. contact@) | Delivers into the mailbox(es) of the people concerned |
An alias can point to several mailboxes to share an address within a team. Since it stores nothing, deleting an alias erases no mail: it only cuts off the redirection going forward.
Webhooks (mail events)
Webhooks connect Mail to your applications: when an event occurs — typically the arrival of a message — the platform calls a URL you provide, with the event's data. You thus automate the processing of incoming mail without polling the mailbox in a loop.
- 1Declare the receiving URLYou register your service's HTTP address. It is the one the platform will call for each subscribed event.
- 2Choose the eventsThe main event is the reception of a message. Subscribe only to what interests you to avoid noise.
- 3Handle the incoming callYour service receives the event's data and triggers its logic: creating a ticket, updating a no-code database, sending an internal notification.