Skip to content

Email and SMTP

App auth supports verification and password recovery. Each app can use its own SMTP provider and verified sender domain. A shared sender processes bounded mail work; apps do not run a separate mail process or hold SMTP credentials.

Platform account email and customer app email have separate configuration. General transactional email, marketing, custom arbitrary templates and a public mail-sending primitive are not current V1 promises.

Your platform agent key needs write scope:

Terminal window
bfast smtp set --app my-counter \
--host smtp.resend.com --port 587 \
--username resend --from noreply@your-verified-domain.example
bfast smtp status --app my-counter --json

Enter the provider’s SMTP password or sending key at the hidden prompt. There is no password command argument. Automation can pipe a secret manager’s output with --password-stdin. The dashboard Authentication page supplies the same settings.

The Resend example requires an account, a verified sender domain and a sending key. Other supported SMTP providers can use their own host, port and credentials. Use the provider’s TLS connection settings. The platform rejects unsafe internal destinations; app SMTP is not arbitrary outbound network access.

Setting replaces the whole profile. Status returns configuration presence and mail counters, never the secret. Saving settings does not send a test email.

Terminal window
bfast smtp clear --app my-counter

Clearing blocks new app email. Existing eligible users can still use password login and ordinary app requests during delivery failure.

Use a real inbox for public signup. Follow the verification link before login. For an owner-only test without email, use bfast users create --verified as described in the quickstart.

The development sender is restricted to an authorized test inbox. Do not rely on it for your customers. Configure your own app SMTP for real registration and reset. SMTP acceptance means the provider accepted a message; it does not prove inbox delivery.