What makes email different from instant messaging?

Email doesn't need both people online at the same time. Instant messaging does.

So when When you hit send on an email, it doesn't disappear if the recipient is offline. The message gets stored on your mail server, forwarded to the next server in the chain, stored again, forwarded again, until it reaches the recipient's mailbox. If a server along the route is temporarily unavailable, the message waits in queue and retries later. This is called store-and-forward, and it's why email can take minutes (or hours) to arrive.

Instant messaging works differently. Both people need to be connected to the same service at the same time. If you send a message and the recipient isn't online, modern IM platforms store it for delivery later (basically copying email's trick), but the core protocol still requires an active session.

Think of email as a cargo ship moving containers between ports. Each port holds the cargo until the next ship arrives. Instant messaging is a phone call: you need both ends connected for the line to work.

Why this matters for email senders: store-and-forward means you can't control exactly when your email arrives. A marketing ESP might queue your campaign to spread sends over time. A recipient's mail server might greylist your message and delay it by 15 minutes. The internet between servers might be slow. You send at 9am, but the reader doesn't see it until 9:47am. That's normal.

This is also why bounces can take days to arrive. If the recipient's server is down, your server will retry for 24-72 hours before giving up and sending a bounce message back to you. Instant messaging would just fail immediately.

The store-and-forward model is why email scales so well. You can send to 100,000 people without all 100,000 being online. It's also why email authentication (SPF, DKIM, DMARC) exists: each server in the chain needs proof the message is legitimate, because there's no live handshake like in IM.