Skip to main content
Every client needs the same four values. Set them once and existing mail code sends through MailBreeze unchanged.

Verifying your setup

Before wiring an application, confirm the credentials work by sending yourself a message:
A working configuration ends with:

Frameworks and applications

For WooCommerce and form plugins, the MailBreeze WordPress plugin also syncs contacts and orders into MailBreeze. It is separate from SMTP and the two work together.

Postfix relay

To route an entire server’s outbound mail through MailBreeze, add to /etc/postfix/main.cf:
Create /etc/postfix/sasl_passwd:
Then secure and load it:
sasl_passwd holds your API key in plain text. Restrict it to root and remember it exists when rotating keys — a revoked key causes Postfix to defer mail quietly rather than raise a visible error.

Choosing a port

587

The standard submission port. Use this unless it is blocked.

465

Implicit TLS. For clients that expect TLS from the first byte.

2525

Fallback for networks and hosts that block 587.
Port 25 is not offered for submission.

Migrating from another provider

Change the host, username, and password. Everything else in your existing configuration stays as it is. If you are moving from a provider whose SMTP host you reached on port 2525, MailBreeze accepts 2525 too, so the port does not need to change either. Your sending domain must be verified with MailBreeze first — DNS records from your previous provider do not carry over.