The Integrations page has an Email card for the mail server SIEMLite sends email through. (It was on the System page in v0.10; the settings carried over.) Fill in the server, choose the connection security, add a login if the server needs one, and say what address mail is sent from. Send test sends a message with the settings as they are in the form, before you save them, and shows the server's own error if it fails (a wrong password, a port that isn't listening, a certificate that doesn't verify).
| Security | Usual port | Use it for |
|---|---|---|
| STARTTLS | 587 | Most mail providers and relays: starts plain, then upgrades to an encrypted connection. |
| TLS | 465 | Servers that expect an encrypted connection from the first byte. |
| None | 25 | A relay on a network you trust. The login and every message cross the network in plain text. |
- Logins use PLAIN or LOGIN, whichever the server offers.
- Accept any certificate is for a server with a self-signed certificate. The connection is still encrypted, but SIEMLite can't tell whether it is talking to the right server.
- The password is encrypted with a key in
siemlite-secret.key, next to the database (/datawith Docker). It is never shown again, and the page only says whether one is saved. A backup contains the encrypted password but not the key, so after a backup is restored onto a different server the page says the password can't be read there; enter it again. Keepsiemlite-secret.keyprivate, likesiemlite.key. - The saved password is only ever used with the server and login it was saved for. If you change the server, port, security or username, and for Send test against a different server, type the password again, so nothing can make SIEMLite log in somewhere else with the saved one.
- Saving and testing are recorded in the audit log (without the password).
- This sets up the connection only; nothing sends email by itself yet.