Console email
An email connector that writes messages to the application log rather than sending them.
| Category | |
| Authentication | None |
| Reaches | Nothing |
| Needs an agent | No |
Capabilities
Section titled “Capabilities”email.send
What it is for
Section titled “What it is for”Development. Work on wording or on a flow that sends email without a mail server, and without accidentally emailing a real parent from a test database.
A first look. Configure it on a fresh install and lodge a test repair. The message that would have been sent appears in the log, so you can see exactly what the product sends before deciding on wording or on a real email connector.
Training environments. People can work freely in an instance that cannot email anybody.
Configuring it
Section titled “Configuring it”Admin, Connectors, Console Email (dev), Configure.
| Field | Value |
|---|---|
from |
A From address. Display only, since nothing is sent |
The test connection always succeeds.
Where the output goes
Section titled “Where the output goes”The same place as the rest of the application log:
| Install | Where |
|---|---|
| systemd | journalctl -u plugboard -f |
| Validated reference bundle on Windows or macOS | logs/ inside the install directory |
| From source | The terminal you started it in |
The Windows/macOS row is conditional launcher guidance. Current native release packaging targets Linux x64; check actual assets.
Each entry carries the recipient, the subject and the body, so you can read the message exactly as it would have arrived.
Never in production
Section titled “Never in production”Obvious, but the failure is silent. With this connector enabled, everything appears to work. Repairs are lodged, statuses change, receipts are generated. Nothing reaches anybody.
The symptom, weeks later, is families saying they were never told their child’s device was ready.
If you use this to explore, replace it with SMTP or Google Workspace before anyone real depends on it.