Mail and invitations

Everything the product sends leaves through one mail connection. There is no second channel and no bypass path.

What goes out	When
Two calendar invitations per event	On creation, and again on every edit or cancellation
Messages to system owners and contacts	According to the update type and its template
The checklist summary	When every required question on the form has been answered
Scheduled reports and alert deliveries	On the schedule, or when the rule fires

"Send to the system owner" on the export screens is the exception, and it is deliberately not a send: it returns a file that opens as a mail draft on your own machine, so that you read it and send it yourself. The product does not send it.

Configuration

The mail connection is configured as a connection row in settings, not in a file that requires a restart.

Field	Note
SMTP server	An internal relay, or a hosted service
Port	25 for an internal relay · 587 with STARTTLS · 465 with implicit SSL/TLS
STARTTLS	Encrypting the connection after it opens — the usual choice on port 587
Implicit SSL/TLS	For servers that require encryption from the moment the connection opens
Username and password	Left empty when the server accepts unauthenticated submission
Sender address and sender name	These appear on every invitation that goes out
Sender address policy	See below

The sender address policy

Some messages in the product deliberately come from a different mailbox — the checklist summary from the operations center mailbox, an invitation on behalf of the event's creator. An internal relay will usually carry those; a hosted service accepts only the address it authenticated and rejects a stranger's.

The choice	The behavior
A dedicated address where possible	The default. The dedicated address is kept when the connection does not authenticate, or when it is on the same domain
Always the configured sender address	All mail leaves from the configured address. The display name survives, so the message still reads as coming from the operations center

The rejection in this direction is silent: the message simply stops arriving. For a hosted service, choose the second option.

Two tests, and only one of them proves anything

Action	What it does
Test	Connects to the server using the saved configuration — and sends nothing
Send a test mail	Sends a real message to an address you type, and reports stage by stage what happened

The test also reports which values it took from the deployment's own configuration where the row left them blank, otherwise you would be reading a verdict about a server you never typed. The password is never returned at any stage. One limit: five test mails per minute per user — a mail test costs nothing and lands in somebody's inbox.

When a send fails

A mail failure does not cancel the action the user already confirmed. The event is saved, the summary screen shows "not sent" with the reason, and editing the event in the calendar sends the invitation again.

Deleting the mail connection returns the product to the deployment's own mail settings — and if there are none, it is left with no mail channel. The delete dialog states both possibilities before it deletes.