SECURITY
What this build does not pretend to enforce
The browser can reject a private hostname in the sample SMTP form. That check is guidance. It is not the production control, and a determined client can bypass any check that lives only in the interface.
An optional account can be created from Get Started. The password is stored as a scrypt hash, and the sign-in cookie is HttpOnly and separate from the workspace cookie. The sample workspace does not require that account. A new account stays pending until a 6-digit code is confirmed. That code is sent by the platform mail service when it is configured, not through a customer SMTP connection. Authenticator codes are not enabled.
SMTP and OAuth secrets are sealed with AES-256-GCM when CONNECTIONS_ENCRYPTION_KEY is configured. API responses do not return them. Private, loopback, and metadata addresses are rejected after DNS resolution, and TLS certificates are not bypassed. A message the server accepts is not described as delivered.
