E-mail Configuration: Setting Up and Managing Electronic Mail

Every business email you send today rests on plumbing that is more than fifty years old. The interface has changed, but the underlying rules for sending, storing, and fetching messages have barely moved. For a B.Com student who will eventually manage official communication, vendor correspondence, or a company inbox, understanding how email actually works, not just how to click “send”, is genuinely useful knowledge. This post walks through what email is, the protocols that keep it running, and how to configure it correctly and securely.

Where email actually came from 🔗

Email did not arrive with the internet as we know it. It began in 1971, when engineer Ray Tomlinson was working on ARPANET, the U.S. government-funded network that eventually evolved into the modern internet. Tomlinson built the first system that let one person send a message to a specific person at a specific address, something earlier messaging tools on shared computers could not do. He is also credited with picking the “@” symbol to separate a username from its destination machine, a convention every email address in the world still follows. The very first test message he sent to himself was, by his own admission, something forgettable, but the addressing structure he created has outlasted almost every other piece of 1970s computing.

The three protocols that make email work 🔗

When you hit “send” or open your inbox, you are not really talking to a single system. Three separate protocols handle sending, storing, and retrieving mail, and each has a distinct job. Knowing which does what makes troubleshooting a broken email account far less confusing.

SMTP: the protocol that sends mail 🔗

SMTP, or Simple Mail Transfer Protocol, is responsible for pushing a message from your device to your provider’s server, and then relaying it onward to the recipient’s mail server. It is a one-directional, “push” protocol. SMTP has no interest in how your inbox is organised or how many folders you have; its only job is delivery. Every outgoing email, regardless of which app you use, passes through an SMTP server at some point in its journey.

IMAP: reading mail without moving it 🔗

IMAP, or Internet Message Access Protocol, retrieves mail but leaves it sitting on the server. When you open an email on your phone and later check the same inbox on a laptop, both devices show identical read/unread status and folder structure because the messages themselves never actually left the server. This is what makes IMAP the default choice for anyone who checks mail from more than one device.

POP3: download and disconnect 🔗

POP3, or Post Office Protocol version 3, works differently. It connects to the server, pulls the messages down to your device, and in its default configuration, deletes the copy on the server afterward. This made sense in an era of expensive, limited server storage and slow dial-up connections, when people checked mail from a single desktop computer. Today it is used far less often, mainly by people who want a permanent local archive and do not need multi-device syncing.

IMAP or POP3: which one should you actually use 🔗

For almost every modern user, especially anyone managing business correspondence, IMAP is the practical default. If you check mail on your phone during a commute and again on your laptop at office, IMAP ensures both stay in sync. Choose POP3 only in narrow situations, such as extremely limited internet access, a strict need to keep permanent local copies for compliance, or very tight server storage quotas. Most business email providers, including corporate Google Workspace and Microsoft 365 accounts, are configured for IMAP by default for exactly this reason.

Setting up an email account step by step 🔗

Configuring an email client, whether Outlook, Thunderbird, or a phone’s built-in mail app, always asks for the same core details: incoming server address (IMAP or POP3), outgoing server address (SMTP), the correct port number, and an encryption method.

Server addresses and port numbers 🔗

A typical configuration screen asks for an IMAP server on port 993, a POP3 server on port 995, and an SMTP server on port 465 or 587, with SSL or TLS encryption enabled for each. These specific numbers are standardised across providers precisely so that any email client can talk to any mail server without custom code.

Encryption: why SSL and TLS matter 🔗

Plain, unencrypted ports send your username, password, and message content across the network as readable text, which anyone intercepting that traffic could read. Enabling SSL or TLS wraps the entire conversation between your device and the mail server in encryption, so even if the data is intercepted, it is unreadable. Most ISPs and workplace networks now block the old unencrypted SMTP port 25 for outgoing mail specifically to reduce spam and interception risk, which is why 587 (with TLS) has become the standard for sending mail from client applications.

Authentication is moving beyond plain passwords 🔗

For years, configuring email meant simply typing in an email address and password. That is changing quickly. Google, for instance, has phased out plain password-based logins for IMAP, SMTP, and POP entirely, requiring OAuth-based authentication instead, which grants an app a revocable digital token rather than the actual account password. If you have ever had an old email app suddenly stop working and demand you “sign in again,” this is usually why. It is a meaningful shift for anyone configuring business email accounts, since older mail clients that only support username-and-password logins will simply fail to connect to modern providers.

Configuring email securely for business use 🔗

For organisations, email configuration is not just a personal convenience setting, it is a security decision. The Indian Computer Emergency Response Team (CERT-In) has issued formal information security guidelines covering areas such as network security, identity and access management, and security hardening for government and affiliated entities, and similar principles apply well to any business handling sensitive correspondence. In practice, this translates into a few habits worth building early in a professional career:

Enable encryption by default: always use the SSL/TLS ports rather than unencrypted ones, even if a provider technically allows plain connections.

Use strong, unique authentication: prefer app-specific passwords or OAuth over reused passwords across multiple services.

Verify server details before trusting them: only enter server addresses and ports supplied directly by your official IT department or provider’s documentation, never from an unsolicited email or third-party link.

Keep client software updated: outdated mail apps are more likely to rely on deprecated, less secure authentication methods.

Common configuration problems and quick fixes 🔗

Most email setup failures trace back to a handful of repeat issues. A mismatch between the port number and the encryption type selected is the most frequent one; port 587 needs STARTTLS, while port 465 needs implicit SSL, and mixing the two causes an immediate connection failure. Certificate errors usually mean the client is pointed at the wrong server address. And a message that fails to send but arrives fine when received often points to an ISP blocking outbound port 25, which is resolved by switching to port 587. When in doubt, checking a provider’s official help page for the exact current server settings is far more reliable than reusing settings found on a random forum, since providers occasionally update these values.

What do you think? Given how much of Indian business communication now runs through mobile devices, does it still make sense for any organisation to configure new accounts on POP3 rather than IMAP? And as providers phase out simple password logins in favour of OAuth, how prepared do you think most small businesses are for that shift?

References

1. https://www.npr.org/2016/03/06/469428062/ray-tomlinson-inventor-of-modern-email-has-died
2. https://www.guinnessworldrecords.com/news/2015/8/60/1971-first-ever-email-392973
3. https://www.geeksforgeeks.org/computer-networks/imap-vs-pop3-vs-smtp/
4. https://seas.harvard.edu/office-computing/email/gharvardedu-client-configuration
5. https://knowledge.workspace.google.com/admin/sync/transition-from-less-secure-apps-to-oauth
6. https://www.pib.gov.in/PressReleasePage.aspx?PRID=1936470