IMAP & SMTP
The connection for a mailbox nobody hosts for you. You type the hosts, the ports and the password, and we sign in for real before agreeing to keep them, so a typo is caught while somebody is still sitting at the form.
Wiring a mailbox up by hand
savedProduct figures from the platform’s own defaults - not customer averages
How it works.
Where you point it is checked before anything connects
Both addresses you typed are looked up and refused if they land on loopback, a private range, the link-local block or anything reserved. A settings form is not a port scanner for the network we run in.
It signs in before it saves anything
A real login and logout runs against your incoming server first. A rejection comes back naming which thing is wrong, whether that is the password, the address, the port or the encryption setting, instead of a bare failure somebody has to guess at.
Sent is a place here, not a property
There is no marker on a message saying it was sent, so a message counts as outbound because of which mailbox it turned up in. That is why the sent mailbox is walked rather than inferred.
Your own copy has to be filed by hand, so we file it
Handing a message to an outgoing server leaves the sender's own sent mailbox empty, so the raw message is put there afterward and marked as read, the way any desktop client does it.
Two moments in every message.
Every message passes through the same seven. IMAP & SMTP is the lit ones, and everything either side of it is a different page in this category.
- 01Connect
the account it syncs with
- 02Compose
writing it, and from what
- 03Send
leaving now, or on a schedule
- 04Arrive
landing, and what it lands as
- 05Attach
pinning it to the right record
- 06Book
the meeting that comes of it
- 07Govern
who may use what, and see what
The specifics.
8 facts- Setup
- A form rather than a consent screen: address, password, both hosts and both ports, seven fields in all. Encryption is not one of them
- Defaults
- 993 with TLS inbound and 587 outbound, both fixed by the form. Port 465 is read as implicit TLS where a server asks for it
- Host guard
- Loopback, private, link-local, carrier-grade and reserved addresses are all turned away
- Cadence
- Polled every five minutes. This is the one connection with no push at all
- Window
- Since the previous run, or ninety days on the first, keeping the newest two thousand per mailbox, and two thousand is a floor on that cap rather than a ceiling. Five mailboxes are walked, so one pass can take a good deal more than two thousand in total
- Threading
- None. A message arrives here without a conversation identifier of any kind
- Write-back
- Read and starred are pushed outward, probing the message's own mailbox first and a list of common names after
- Bad password
- The connection is switched off rather than retried, so nothing keeps hammering your mail server
What this sits beside.
Mail and diary are one surface with several parts. These are the ones a person passes through in the same minute.
More in Email & Calendar
12 capabilitiesWebmail, four mailbox connections, tracking, calendar and meetings.
Book a slot while the customer is still on the line and the invitation is in their inbox before you say goodbye. What they change comes back when you sync.
The mailbox stays connected, and a message somebody moved is not sitting here twice. Outlook and Microsoft 365 over Graph, picking up only what changed.
A Microsoft mailbox brings its diary and address book with it, and whether it sits in Microsoft 365 or on a server in your building is worked out for you.
Templates with merge variables, organized into groups and granted per team, so the answer your best rep writes becomes the answer everybody sends.
Regulated copy stays with the people allowed to send it. Filing a template into a group is what shares it, so there is no second step for anybody to forget.
What does not count is the useful part: a rep opening their own message, a crawler, the same person twice in five minutes. A figure a supervisor can act on.
Park a thread and it comes back at the hour you named, unread, so nobody walks past it. Hold a send and it leaves at the hour you named, once, never twice.
A meeting agreed on a call is never lost because somebody else's service was slow. The booking is saved here first, then the room and the calendar entry.
Move the meeting an hour and the Zoom room moves with it, on the link guests already have. Delete the booking and the room goes too, with nobody chasing it.
The join link is made by the calendar itself, on the same save that books the meeting, so nobody hunts for it later. One Google account is the whole setup.
Pick Teams on a booking and the join link is written into the invitation guests receive, so nobody chases it in a follow-up. A room you own travels too.
Mail files itself against the lead, on a rule short enough to print: the addresses on the lead, matched exactly. No domain guessing, and nothing to dispute.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Email & Calendar
See imap & smtp on your own floor.
Thirty minutes, your numbers and your data. We will set imap & smtp up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included