Start with the application you already have.
If your application already accepts an SMTP host, port, username and password, an authenticated SMTP connection is a natural starting point. You can often change the provider without changing the part of your application that composes messages.
Use HTTP when email is part of your code.
An email API fits applications that already make HTTP requests from their backend. WazobiaMail provides an endpoint for sending messages and a dashboard for managing sending keys. Keep the key on your server; a public website cannot keep an embedded secret private.
Your domain matters either way.
Whether you choose SMTP or HTTP, set up your sending domain and review its verification status. Follow the records shown in your dashboard rather than copying DNS values from another account. A working connection and an authenticated domain are separate parts of a good setup.
Make the first message a small one.
Send an example message to an address you control. Check the sender, content and delivery result before connecting a live workflow. Your active plan and provider determine the sending limits that apply.
By the WazobiaMail team at Bonifade Technologies.
← Back to the guides