SMTP connection
Enter the host, port, security mode and credentials your email provider gives you, and connect any compatible account you control.
Built for agencies and B2B sales teams.Built for lead generation agencies and B2B sales teams. Manage contacts, automate email sequences, and handle replies in one workspace.
Start free →Link the SMTP and IMAP accounts your organization controls, and use them for campaign sending and reply handling. Enter the details your email provider gave you, test the connection and assign the account to a campaign.
SMTP sending
IMAP replies
The tools are built to work within the broader DevBoxy outreach platform, from the first connection to the replies that follow.
Enter the host, port, security mode and credentials your email provider gives you, and connect any compatible account you control.
Confirm that the configured account can connect before you assign it to a campaign, so a typo never delays a launch.
Apply account-level limits and pacing to connected sender accounts, so each one sends at a rate you choose.
Use compatible IMAP access so campaign replies are processed in the unified inbox, with their context attached.
Five steps take an existing mailbox from provider settings to a campaign-ready sender.
Find the SMTP host, port, security mode and credentials in your email provider’s settings.
Add them to DevBoxy for the account you control.
Confirm the account can connect before you use it.
Provide compatible IMAP access so replies can be processed.
Set limits and pacing, then use the account in your campaigns.
Your provider decides which port and security mode to use. The common combinations below are a guide, so always confirm against your provider’s documentation.
| Protocol | Port | Security mode | Used for |
|---|---|---|---|
| SMTP | 587 | STARTTLS | Sending campaign email |
| SMTP | 465 | SSL/TLS | Sending campaign email |
| IMAP | 993 | SSL/TLS | Processing replies |
SMTP accounts do not come with a campaign dashboard of their own. DevBoxy adds the controls, so each connected sender works within limits you set.
Most failures come from one of four settings. Check them in this order.
Confirm the exact SMTP host and port from your provider, and test that the port is reachable.
Match STARTTLS or SSL/TLS to the port. A mismatch is a common cause of failure.
Check the username and password, and whether your provider requires an app-specific password.
Some providers limit SMTP access by plan or setting. Check that SMTP is enabled for the account.
Once an account is connected and tested, build on it.
SMTP is the standard protocol for sending email. An SMTP account lets DevBoxy send your campaign emails through a mailbox or mail service that your organization controls.
You need the host, port, security mode and credentials that your email provider gives you. You can then test the connection before assigning the account to a campaign.
SMTP only sends mail. Compatible IMAP access lets DevBoxy process campaign replies so they appear in the unified inbox with their context attached.
Use the values your provider specifies. Port 587 with STARTTLS and port 465 with SSL/TLS are common for SMTP, and port 993 with SSL/TLS is common for IMAP, but providers differ.
Yes. Connection testing confirms that the configured account can connect before you assign it to a campaign.
Yes. You can apply account-level limits and pacing to each connected sender account, so every account sends at a rate you choose.
Check the host and port, make sure the security mode matches the port, confirm the username and password, and see whether your provider requires an app-specific password or restricts SMTP access.
No. DevBoxy connects to accounts your organization already controls. Your provider still hosts the mailbox, and DevBoxy adds campaign sending, limits, pacing and reply handling on top.
Start with the tools you need today, then connect more infrastructure, campaigns and conversations over time.