Email — mailbox and what leaves the machine

Email — mailbox and what leaves the machineMailbox reading and sending, and the controls that stop data leaving. Email is the one feature that sends your data OUT, to people, sometimes with nobody watching, so it is worth being precise about what is protected and what is not. A mail profile is stored exactly like a database connection: the server address and the user name sit in a readable file, and the password goes into the same encrypted vault, under a name in its own namespace. There is deliberately no way to read a stored mail password back — no endpoint returns one, so a profile can be replaced but never revealed, and a bug in the interface cannot turn into a credential dump.

What this page covers

Email — what leaves the machine, and what stops it

Settings and controls documented

Name
Identifier
Port
Automatic
From address
EHLO name
Certificate authority file
Allow authentication without encryption
Default folder path
Start Outlook if it is not running
Mailbox address
Sign-in authority
Graph endpoint
Mark messages as bulk
Endpoint
Sender address
Turn off engagement tracking
Delivery checks after sending
API version
Password
API token
Access key
Allowed recipient domains
Test
Send a test message

Full page

The full page — procedures and the explanation of every setting — is available to signed-in users.

ATX Institute on LinkedIn

This site needs JavaScript for the full experience. Every page above is reachable without it.