Keep your workflow.
Connect your sender.
Put utobo’s settings into an application that already supports SMTP. Keep creating your email there, then use utobo to send it and review the available activity.
Choose the matching port and encryption mode for your application.
- Host
- smtp.mail.utobo.com
- Port
- 587465
- Encryption
- STARTTLSImplicit TLS
- Username
- apikey
- Password
- av_live_...
Use the literal word apikey as the username and your utobo API key (av_live_…) as the password. Store it in the application’s secure settings.
Start with the mail settings you have.
These are SMTP configuration examples. Your application or plugin needs to support a custom encrypted SMTP connection.
Compatibility depends on the application’s settings. These examples are not native connector or partnership claims.
Your application keeps the message.
Use the content and templates your application already creates. Connect its outbound mail configuration to utobo and check the result of a controlled test.
Create the email.
Your existing workflow supplies the recipient, subject, and message.
Pass it to utobo.
Use the verified sender, API-key credential, and matching port/TLS pair.
Check the result.
Review the application response and available activity when a message needs attention.
Keep the port and encryption together.
Your application may call this setting Security, Encryption, or Connection type. Select the supported pair that matches its configuration.
The host and credential roles stay the same. The username is always the literal word apikey; the password is your API key. Your from-address still needs to be on a verified domain.
STARTTLS
Use when the application supports upgrading the SMTP connection to TLS.
Implicit TLS
Use when the application expects TLS from the start of the connection.
Make your first test easy to investigate.
Start with a verified sender and an address you control. Keep the application response handy while you review the message.
- 01
Verify the sender.
Complete sending-domain setup in utobo before configuring the application’s from address.
- 02
Enter the settings.
Add the host, the matching port and encryption mode, the username
apikey, and your API key as the password. - 03
Send a controlled test.
Use your application’s test action or a small, familiar workflow. Read its response.
- 04
Review the result.
Check available utobo activity and the receiving address. Investigate any error before broadening the send.
Start with the part that failed.
A connection problem, a rejected sender, and an authentication problem need different checks. Use the application’s response and the setup guide to narrow the next step.
Open email docs ↗Authentication
Check the username is the literal word
apikeyand the password is a valid API key.Sender rejected
Confirm the sending domain’s verification and review the from address configured in your application.
Connection
Check the hostname and port/TLS pair, then review your application’s connection requirements.
Outbound mail and your team’s inbox are separate decisions.
Configuring outbound SMTP alone does not require moving your incoming-mail MX records. If you also want customer replies in utobo’s Receiving inbox, treat that as a separate receiving setup and check the effect on existing mailbox routing.
A few things you might be wondering.
Find the detail you need before your first send.
Talk to the team ↗Do I need to rewrite my email templates?
If your existing application already produces the email and supports configurable SMTP, you can usually keep those templates there. The integration work depends on the application and how its mail settings are managed.
What do I use as the username and password?
Use the literal word apikey as the username, and your utobo API key (av_live_…) as the password, stored securely in the sending application. Your from-address must still be on a verified sending domain.
Can I use WordPress?
A compatible SMTP plugin can configure WordPress to use a custom SMTP sender. Follow the settings for your particular plugin; this is SMTP configuration rather than a native utobo connector.
Will SMTP move my existing inbox?
Outbound SMTP configuration alone does not move incoming mail. Changing MX records for inbound receiving is a separate action that can affect existing mailbox routing.
Does a successful test guarantee inbox placement?
No. Review the application response and available sending activity, then check the receiving address. Recipient systems make their own decisions about placement.
Give your existing email workflow a clear sending path.
Get the connection details, send a controlled test, and know where to look next.