Email Basics

Email isn't just messages on the internet. It's a protocol driven system built for reliable, asynchronous communication between humans and machines.

When you send an email, it travels through servers (MTAs) using SMTP and is fetched later via IMAP or POP3. It's formal, universal, and traceable. Think of it as a vessel carrying a sealed message across digital waters, structured, logged, and accountable. That structure is what makes it dependable decades after its invention.

Over 4.3 billion people use email today, and that number keeps growing every year. Analysts expect it to reach nearly 4.8 billion users soon, more than half of the planet.

It's simple enough for anyone to use, yet complex enough to power global business. Email evolves constantly. What worked in 2004 doesn't work in 2025\. Filters, privacy rules, and inbox algorithms shift daily.

People keep saying email is dead, but it's the same story every year. Like a message in a bottle that keeps washing back to shore, email always finds its way back into the conversation.

When you hit send, your message leaves your email client, passes through your provider's SMTP server, looks up the recipient's domain via DNS, and lands in their server's inbox queue.

From there, the recipient's client retrieves it.

Behind the scenes, it's all server to server communication using standardized protocols. SMTP moves the mail; IMAP or POP3 fetch it. These rules let Gmail, Outlook, and any other provider communicate like ships following the same navigation charts.

An email client is your control center: the application you use to read, send, and manage mail.

Outlook, Apple Mail, and Thunderbird are common examples. They connect to your mail server using IMAP (for syncing) or POP3 (for downloading) and use SMTP to send.

The client is the interface you see; the server is the engine doing the heavy lifting.

Local clients give you power and integrations, while web interfaces focus on accessibility and speed.

Webmail is email you access through a browser. Think Gmail.com or Outlook.com.

The processing happens on the provider's servers; you interact through a graphical web interface.

The advantage is accessibility from any device with an internet connection. The trade off is dependence on that connection.

Modern webmail platforms are secure, constantly updated, and usually safer than unpatched local software.

Always use strong passwords and enable multi factor authentication.

Email transport refers to how messages move between servers using SMTP. Email storage refers to how messages are kept on the server and accessed by clients using IMAP or POP3.

Transport is the journey; storage is the destination.

Think of it as the difference between the voyage across the ocean (transport) and the warehouse where cargo rests until the captain retrieves it (storage). One moves the mail, the other holds it safely until needed.

The To field shows who the message is intended for. You might see something like firstmate@tidalmail.com or lighthousekeeper@harborpost.com. This field does not control delivery. Delivery happens through the invisible RCPT TO commands that are exchanged during the SMTP conversation.

For every recipient. Including CC and BCC. The sending server issues a separate RCPT TO command. The To line is only the human facing label that is written into the header once the server already knows where the message is going.

Think of it as the name written on the letter inside the envelope. The actual delivery address is on the envelope itself. The mail crew cares about the envelope. Not the decoration inside.

The From field shows who appears to have sent the message. The real technical sender is defined by the envelope MAIL FROM which is what SPF checks. So the visible From can be one thing and the envelope sender can be something else.

There are two parts here. The first part is the friendly from or display name such as Captain Kraken of the Inbox Odyssey. The second part is the actual address such as kraken@tidalmail.com. Phishing attacks often abuse this by keeping the display name familiar while hiding a suspicious domain in the real address.

It is the return address written on the letter. The Return Path which is added later is the harbor post office box where undeliverable mail is sent.

The Subject line is the first thing people see. Many studies show that about thirty five to forty five percent of recipients open an email based on the subject line alone. A strong subject earns the open. A weak one loses it.

Originally all headers were limited to plain ASCII. When we wanted to use other languages or even emojis we needed MIME encoding. That is why you sometimes see subjects that look like this \=?UTF-8?B?8J+MgA==?=. That is RFC 2047 in action. It wraps non ASCII text so mail systems can carry it.

Fun detail. Re does not truly mean reply. It comes from Latin res which means the matter. So Re Your invoice simply means about your invoice. That is why it showed up in old office memos and then email inherited it.

BCC means Blind Carbon Copy. In the pre digital office a secretary could create a copy for someone quietly. The official recipient never saw that another copy existed.

In email. BCC does the same thing. The hidden recipients receive the message. Their addresses do not appear in the copy that everyone else sees. It is the quiet listener in the captain's cabin.