How to Warm Up Titan Email: IMAP, SMTP, DNS and Ramp

To warm up Titan Email, connect IMAP imap.titan.email:993 with SSL and SMTP smtp.titan.email:465 with SSL, then ramp from 3 to 29 emails per day over 14 days. Skip DNS or access checks and Titan can reject the login, or mailbox reputation can stay weak. This guide gives the settings, checks, ramp and fixes.

If you only need the tool, start with the free warm-up tool. If you want to verify the setup first, use the tables below before adding the mailbox.

Titan Email often appears behind reseller or hosting dashboards. Do not guess the server names. Hostinger Email, Namecheap Private Email and Titan Email use different hosts. Use the Titan row only when your mailbox is actually served by Titan.

Which Titan settings should you use?

Connect Titan Email in BobWork with the Other IMAP + SMTP preset. Titan needs IMAP for receiving warm-up mail and SMTP for sending it.

Use your full email address as the username unless your provider panel says otherwise. If two-factor authentication is enabled, use an app password. Titan also requires third-party app access before an external mail client can connect.

Match the host, port and security type exactly. Port 993 uses SSL for IMAP. Port 465 uses SSL for SMTP. Do not set port 465 to STARTTLS, and do not set port 993 to plain or automatic if your client lets you choose the exact mode.

If your Titan account is in the EU cluster, use the EU hosts from the table. A correct password can still fail when the mailbox connects to the wrong regional host.

What does Titan check first?

Titan first checks whether the mailbox allows mail-client access. That means third-party app access, the right password type, the right host and the right encryption mode.

After the message leaves Titan, receiving providers judge the message and domain. They look at authentication, alignment, past engagement, sending pattern and user complaints. Warm-up is not only a login test.

Keep the first two weeks steady. Use plain-text messages, normal office-style replies and a gradual daily ramp. Sudden volume jumps look different from normal mailbox use, especially on a new domain.

Keep complaints low. For Gmail-bound bulk mail, Google publishes a spam complaint target under 0.1% and says never to reach 0.3%. Yahoo’s sender rules also use a 0.3% spam-rate limit for bulk senders. Treat those as upper bounds, not goals.

BobWork’s warm-up engine uses short plain-text office messages, spreads sends across the mailbox time zone and keeps threads short. The shared warm-up network does this automatically, or you can switch to a private pool per account if you prefer.

How do you warm up Titan Email?

Open BobWork Email Warm-up and add a mailbox using Other IMAP + SMTP. Titan is a standard IMAP and SMTP setup, so you do not need OAuth.

Use this connection path:

1. Sign in to BobWork with your email code.
2. Choose to add a mailbox.
3. Select Other IMAP + SMTP.
4. Enter the Titan email address as the mailbox name and username.
5. Add the IMAP host, port and SSL mode from the table.
6. Add the SMTP host, port and SSL mode from the table.
7. Paste the mailbox password, or the app password if 2FA is enabled.
8. Save the mailbox and let BobWork test the connection.

If you want the default pool, one Titan mailbox is enough to start. It warms with other active mailboxes in the shared warm-up network.

If you prefer your mailboxes to warm only each other, go to Mailbox pool → Pool mode and switch to a private pool. A private pool needs at least two mailboxes in the account.

BobWork does not read or answer your real mail. Warm-up mail is identified by the engine’s own hidden header. Warm-up mail found in spam is moved to the inbox, marked read, labelled Warm-up and archived after 24 hours.

If you are deciding between doing this by hand and using automation, read manual email warm-up vs automation. Manual warm-up can work, but it is easy to stop replying, skip weekends or forget to check spam.

Which DNS records matter?

Do the DNS work before you rely on warm-up. Warm-up can build mailbox behaviour, but it cannot fix missing authentication.

For Titan Email, check Titan or your reseller’s current DNS help for exact SPF and DKIM values. Do not copy a value from another provider. DNS values change, and resellers may use different records.

SPF tells receivers which servers can send for your domain. The SPF standard is defined in RFC 7208. Use one SPF TXT record per sending domain or subdomain. If SPF already exists, merge Titan’s mechanism into the existing record instead of creating a second SPF record.

DKIM signs mail with a private key and lets receivers verify it with a public DNS record. The DKIM standard is defined in RFC 6376. Enable DKIM wherever Titan or the reseller exposes it, then publish the selector and value they show.

DMARC tells receivers what to do when SPF or DKIM fails alignment. The DMARC specification is RFC 7489. Start with monitoring if you are unsure. A common starting record is v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com, but use a mailbox you can receive.

BobWork checks SPF, DKIM and DMARC daily and shows them per domain. For a deeper walkthrough, use SPF, DKIM and DMARC for cold email.

What 14-day ramp works?

The default BobWork ramp starts at 3 emails per day, adds 2 per day and caps at 30 per day. The cap is editable per mailbox up to 100, but do not raise it early on a new Titan mailbox.

The first 14 days take you from 3 to 29 warm-up emails per day. Day 15 reaches the default 30-per-day cap. Weekends run at 30% of the normal daily volume.

You can also build a custom plan with the email warm-up schedule generator. Keep the same principle: small daily increases, no sudden jumps and no cold campaigns before the mailbox has enough positive activity.

For a new domain, run warm-up for 2–3 weeks before serious outbound. For an existing domain with clean DNS and prior normal use, 7 days can be enough before a small test.

How do you fix errors?

Most Titan failures are setup errors. Fix the connection before changing the warm-up volume.

If spam landings rise, do not push through it. Our published practice is to pause a mailbox for a few days above a 5% spam rate. Add mailboxes rather than forcing more volume through one mailbox.

If Gmail is the main destination and you are seeing spam placement, use why emails go to spam to separate DNS, content, volume and reputation problems.

What should you verify now?

Use this checklist before you start sending real outreach from Titan Email.

This checklist is useful when a client says they use Titan through a host. The brand on the invoice matters less than the IMAP and SMTP hosts on the mailbox.

When is Titan ready?

A Titan mailbox is ready for outbound when it has warmed for at least 7 days, has a 7-day warm-up spam rate at or below 3%, and has received at least 30 warm-up emails. New domains should usually wait 2–3 weeks.

When you start cold email, keep real outreach to a typical range of 30–50 emails per day per mailbox. Add more mailboxes instead of forcing one Titan mailbox higher.

Keep warm-up running during campaigns at 10–15 emails per day. That keeps normal mailbox activity present while your real sends increase. If replies and bounces are managed across multiple mailboxes, a unified inbox for cold email can make follow-up easier.

BobWork Email Warm-up is free for up to 10 mailboxes per account, with no credit card and no time limit. Add Titan with Other IMAP + SMTP, check SPF, DKIM and DMARC, then let the ramp run before you send cold email.

Frequently asked questions