Licensed to be used in conjunction with basebox, only.
// integration
SMTP
Applies to
Product: Cloud · Server · Audience: Administrator · Platform Operator
Outgoing mail for invitations and notifications: which settings are needed, how to test the configuration before saving, and what happens without SMTP.
What basebox sends mail for
- Invitations of new users (valid for 14 days) and their re-sending
- Password reset
- Further notifications of the application
Without working mail delivery, invitations do not arrive. basebox therefore warns when users are invited although no SMTP is configured. As a stopgap you can copy the invitation link in the Invitations tab and deliver it another way.
Settings
| Setting | Meaning | Typical value |
|---|---|---|
| SMTP host | Your mail server | smtp.company.com |
| Port | Connection port | 587 (STARTTLS) or 465 (TLS) |
| Username / password | Credentials of a sending account | dedicated service account |
| Connection type | starttls or tls |
starttls with 587, tls with 465 |
| Sender address | From address of the mails | noreply@company.com |
Use a dedicated service account with send permission for the sender address, not a person's mailbox. Make sure your domain's SPF/DKIM allow sending via this server so invitations do not land in spam.
Configuring in the interface
The mail configuration is part of the organisation settings. You can test it before saving: basebox establishes the connection and reports whether it succeeds. Only then save.
- Open Administration → Organisation or Settings and the mail configuration section.
- Enter host, port, credentials, connection type and sender address.
- Click Test connection.
- On success: Save. On failure: read the message – usually port/connection type mixed up or credentials wrong.
- Test with an invitation to yourself.
See Settings.
On basebox Server via configuration
Alternatively, the Platform Operator can set the mail parameters in the application server's Helm values – credentials as a Kubernetes secret, not in clear text:
aisrv:
env:
AISRV_SMTP_HOST: "smtp.company.com"
AISRV_SMTP_PORT: "587"
AISRV_SMTP_TLS_TYPE: "starttls"
AISRV_SENDER_EMAIL: "noreply@company.com"
AISRV_SMTP_USERNAME:
valueFrom:
secretKeyRef:
name: smtp-credentials
key: username
AISRV_SMTP_PASSWORD:
valueFrom:
secretKeyRef:
name: smtp-credentials
key: password
Reference: AISRV → SMTP configuration.
Network
The application server must reach your mail server on the chosen port (outbound TCP 587 or 465). On basebox Server that is a firewall rule in your network. In basebox Cloud, your mail server must be reachable from the Noris data center – or you use an internet-facing relay service of your organisation.
In fully air-gapped operation there is no path outwards; use an internal mail server or distribute invitation links manually.
Troubleshooting
| Symptom | Cause | Solution |
|---|---|---|
| Connection test fails immediately | Host/port wrong, firewall | Check DNS and port; telnet smtp.company.com 587 from the server |
| TLS error | Connection type does not match the port; private certificate | starttls↔587, tls↔465; check CA trust |
| Authentication rejected | Credentials, missing send permission | Check service account; app password instead of normal password with some providers |
| Mails do not arrive | Spam filter, SPF/DKIM | Authorise the sender domain; check the spam folder |
| Invitation expired | 14 days exceeded | Renew in the Invitations tab |
Next: Users · VPN / networking