Built for agencies and B2B sales teams.

Start free →

Connect your existing SMTP accounts.

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.

Host, port and security modeTest before you assignIMAP for reply processing
Connection successfulReady to assign to campaigns
Core capabilities

Everything you need to connect SMTP and IMAP accounts for cold email

The tools are built to work within the broader DevBoxy outreach platform, from the first connection to the replies that follow.

SMTP connection

Enter the host, port, security mode and credentials your email provider gives you, and connect any compatible account you control.

Connection testing

Confirm that the configured account can connect before you assign it to a campaign, so a typo never delays a launch.

Sender controls

Apply account-level limits and pacing to connected sender accounts, so each one sends at a rate you choose.

Reply context

Use compatible IMAP access so campaign replies are processed in the unified inbox, with their context attached.

How to connect

How to connect an SMTP account to DevBoxy

Five steps take an existing mailbox from provider settings to a campaign-ready sender.

  1. 01

    Gather your details

    Find the SMTP host, port, security mode and credentials in your email provider’s settings.

  2. 02

    Enter the SMTP settings

    Add them to DevBoxy for the account you control.

  3. 03

    Test the connection

    Confirm the account can connect before you use it.

  4. 04

    Add IMAP for replies

    Provide compatible IMAP access so replies can be processed.

  5. 05

    Assign to campaigns

    Set limits and pacing, then use the account in your campaigns.

Ports and security modes

SMTP ports and security modes explained

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.

  • STARTTLS. The connection starts in plain text and upgrades to an encrypted one. It is commonly used with port 587.
  • SSL/TLS. The connection is encrypted from the first byte. It is commonly used with port 465 for SMTP and port 993 for IMAP.
  • Use what your provider gives you. Enter the exact host, port and mode from your provider, then run the connection test.
Check a port
Sender controls

Account-level limits and pacing for every SMTP sender

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.

  • Limits per account. Decide how much each sender may send, based on its provider and reputation.
  • Pacing for every sender. Control how quickly an account sends, so campaigns run at a steady rate.
  • Use accounts across campaigns. Assign a tested SMTP account to the campaigns that need it.
Explore campaigns and sequences
Reply context

IMAP access brings campaign replies into the unified inbox

SMTP only sends mail. To process the replies, DevBoxy uses compatible IMAP access that you provide, and shows each response next to the campaign that earned it.

SMTP sends

Your campaign emails go out through the SMTP account you connected.

Prospect replies

The contact answers the message in their own mailbox.

IMAP processes it

Compatible IMAP access lets DevBoxy process the response.

Unified inbox

The reply appears with its campaign, contact and sender attached.

Explore the unified inbox

Troubleshooting

If the SMTP connection test fails

Most failures come from one of four settings. Check them in this order.

Host and port

Confirm the exact SMTP host and port from your provider, and test that the port is reachable.

Security mode

Match STARTTLS or SSL/TLS to the port. A mismatch is a common cause of failure.

Credentials

Check the username and password, and whether your provider requires an app-specific password.

Provider restrictions

Some providers limit SMTP access by plan or setting. Check that SMTP is enabled for the account.

FAQ

SMTP accounts FAQ

Still unsure? Read the DevBoxy blog or contact the team.

What is an SMTP account for cold email?

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.

What information do I need to connect an SMTP account?

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.

Why do I also need IMAP?

SMTP only sends mail. Compatible IMAP access lets DevBoxy process campaign replies so they appear in the unified inbox with their context attached.

Which port and security mode should I use?

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.

Can I test the connection before using the account?

Yes. Connection testing confirms that the configured account can connect before you assign it to a campaign.

Can I limit how much an SMTP account sends?

Yes. You can apply account-level limits and pacing to each connected sender account, so every account sends at a rate you choose.

Why did my SMTP connection test fail?

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.

Does DevBoxy replace my email provider?

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.

Build a stronger outreach workflow with DevBoxy.

Start with the tools you need today, then connect more infrastructure, campaigns and conversations over time.