Most guides make POP3 sound like a protocol nobody should touch, then leave out the one situation where I still use it. That advice works for ordinary mailboxes, but it fails Edmonton homes and small offices carrying several gigabytes of old email that they can't realistically delete. IMAP is my default, POP3 is a deliberate exception, and SMTP is the always-on outbound lane.
These aren't three competing versions of the same setting. SMTP sends mail, while IMAP and POP3 retrieve it. The decision is whether your incoming mail should remain on the server and synchronise across devices, or whether an intentionally local archive makes more sense. Canadian providers continue to publish all three protocols, although their exact server settings differ. Bell lists IMAP on port 993, POP3 on port 995, and SMTP on port 587, while Eastlink lists IMAP on 993, POP3 on 995, and SMTP on 465 or 587 (provider settings comparison).
Table of Contents
- Why IMAP, POP3, and SMTP Are Not the Same Thing
- What Each Protocol Actually Does in the Email Stack
- IMAP vs POP3 at a Glance
- Ports, TLS, and the Settings You Actually Type In
- Choosing the Right Setup for Home and Hybrid Workers
- When POP3 Is Still the Better Call
- Security Beyond the Protocol Choice
Why IMAP, POP3, and SMTP Are Not the Same Thing
The common assumption is that IMAP, POP3, and SMTP are interchangeable choices buried together in an email app's advanced menu. They aren't. Two protocols handle incoming mail in different ways, and one handles outgoing mail. Mixing up those roles is a common reason a new account can receive messages but can't send them, or can send messages while showing an empty inbox.
IMAP is the normal incoming choice. It leaves messages on the mail server and synchronises the mailbox between your phone, laptop, tablet, and webmail. Read a message on one device and the status can follow you to the others. Folder moves, flags, and deletions also belong to the shared server mailbox.
POP3 is the exception. It was designed around downloading messages to a client, often removing the server copy after retrieval. That model still suits a single trusted computer with a properly maintained local archive, but it creates serious continuity problems when a person expects the same inbox on several devices. POP3's formal standards milestone is RFC 1939, published in May 1996, which helps explain why its original single-device design remains visible in modern compatibility settings (RFC 1939).
SMTP handles sending. When you press Send, your email client authenticates to the outgoing server and submits the message. SMTP doesn't replace IMAP or POP3, and IMAP doesn't send mail. A typical account uses SMTP for outbound mail and one retrieval protocol for incoming mail.
My default rule: Set up IMAP for incoming mail and SMTP for outgoing mail unless the mailbox size and backup plan give you a specific reason to choose POP3.
The choice should follow three practical questions. How many devices need access? How much mail must remain available? Which device owns the local backup? The protocol label matters less than the behaviour it creates.
What Each Protocol Actually Does in the Email Stack
Think of email as two lanes. The outbound lane uses SMTP, and the inbound lane uses either IMAP or POP3. That distinction makes account setup much easier.
SMTP sends the message
Your email client connects to an authenticated SMTP submission server when you send a message. Modern submission commonly uses port 587 with STARTTLS, or port 465 with implicit TLS. The server accepts the message and relays it toward the recipient's mail system. SMTP is also the protocol websites, scanners, and business applications use when they need to send email.
SMTP doesn't provide your inbox view. It doesn't decide which folders you see, and it doesn't synchronise read status. If sending fails while incoming mail works, investigate the outgoing server, port, encryption, authentication method, and account credentials. For a practical diagnostic path, use this guide to troubleshoot email authentication failure.
IMAP reads and synchronises
IMAP connects your client to messages stored on the server. Secure IMAP commonly uses port 993, while port 143 can use STARTTLS. The client can view messages, download content, mark messages read, move them into folders, and synchronise those changes during later sessions.
That server-side model is why IMAP fits phones and laptops. The server remains the shared mailbox, while each client keeps whatever local cache it needs for speed and limited offline access.
POP3 downloads incoming mail
POP3 retrieves messages from the server and downloads them to the client. In the traditional workflow, the server copy is removed after successful download. The local computer then becomes the main place where the mail lives.
Secure POP3 commonly uses port 995, while port 110 can use STARTTLS. POP3 is simpler and can be lighter for one-device retrieval, but it doesn't provide the same server-side folder and read-state management as IMAP. The University of Waterloo protocol lecture describes SMTP as message transfer, POP3 as download-and-remove retrieval, and IMAP as the richer protocol for manipulating stored server messages.
IMAP vs POP3 at a Glance
IMAP and POP3 both retrieve incoming mail, but they create very different ownership models. With IMAP, the provider's server holds the working mailbox and connected clients reflect it. With POP3, the downloading computer usually holds the authoritative copy, especially when the server copy is removed.
That difference affects more than whether messages appear on a phone. It changes how folders behave, where searches run, how offline access works, and who carries the backup responsibility. A user who wants one consistent inbox should choose IMAP. A user who deliberately wants a local archive can choose POP3, but must accept the administrative work that follows.
IMAP vs POP3 behavioural comparison
| Feature | IMAP | POP3 |
|---|---|---|
| Synchronisation | Mirrors mailbox activity across connected devices | Built around a single-device workflow |
| Server copy | Keeps mail stored on the provider's server | Typically removes messages after download |
| Folder state | Syncs folders, read status, and flags | Folder state remains local to the client |
| Search behaviour | Can search the server mailbox | Searches mail already downloaded locally |
| Offline access | Uses cached local copies and resynchronises later | Works offline because messages are downloaded |
| Backup implications | Depends partly on provider retention and backup practices | Makes the local computer responsible for the archive |
Where the trade-off appears
IMAP is convenient because a phone, laptop, and browser can show the same mailbox. It also lets you organise mail centrally, so a folder created on one client can be available elsewhere. The cost is server storage, and the quality of your access depends on the provider's mailbox limits and retention practices.
POP3 gives you a complete local working copy after download. That can be useful when a client has a large legacy mailbox, never needs to browse it from a second device, and has a tested backup routine. It can also be dangerous if the only copy sits on a computer that fails.
The important question isn't whether POP3 is old. It's whether the local machine is protected well enough to become the mailbox.
For most Edmonton households and offices, the answer is no, which is why I recommend IMAP. If older mail is taking too much server space, I usually separate the archive from new correspondence. Keep the old messages local on a backed-up computer, then configure IMAP for newer mail going forward.
Ports, TLS, and the Settings You Actually Type In
Port numbers tell the email client which service to contact, but encryption settings determine how that connection is protected. For modern secure deployments, the practical mapping is IMAP on 993, POP3 on 995, and SMTP submission on 587 or 465. Port 993 and port 995 use implicit TLS, meaning the secure connection starts immediately. Port 587 normally starts with a regular connection and upgrades it through STARTTLS.
Canadian provider documentation reflects this pattern. Bell publishes IMAP 993 with SSL/TLS, POP3 995 with SSL/TLS, and SMTP 587, while Eastlink publishes IMAP 993, POP3 995, and SMTP 465 or 587 (Canadian provider examples). RFC 8314 guidance favours TLS-only ports for modern email access and submission, as summarised in this RFC 8314 secure email port guide.
A practical settings reference
| Protocol | Port | Encryption | Authentication | Notes |
|---|---|---|---|---|
| IMAP | 993 | Implicit TLS | Provider-approved secure authentication | Default incoming choice |
| IMAP | 143 | STARTTLS | Provider-approved secure authentication | Use only when the provider requires it |
| POP3 | 995 | Implicit TLS | Provider-approved secure authentication | Deliberate local-download workflow |
| POP3 | 110 | STARTTLS | Provider-approved secure authentication | Avoid unless specifically required |
| SMTP submission | 587 | STARTTLS | Authenticated submission | Standard outbound choice |
| SMTP submission | 465 | Implicit TLS | Authenticated submission | Supported by some providers and clients |
Use your full email address as the username unless the provider explicitly says to use an alias or short account name. Don't select unencrypted authentication just because a setup wizard offers it. The mail provider may also require OAuth-based sign-in or an app password instead of the normal account password, especially where two-factor authentication is enabled. The exact choice belongs to the provider's current documentation, not to a guess based on the port.
For iPhone setup, Nerds 2 You provides a dedicated email setup guide for iPhone. After entering the account, test both directions. Send a message out through SMTP, then confirm that incoming mail arrives through IMAP or POP3 and behaves as expected on every device.
Choosing the Right Setup for Home and Hybrid Workers
A single-device household doesn't automatically need POP3. In most cases, IMAP remains the safer and more convenient arrangement because people eventually replace a phone, add a tablet, open webmail, or need to recover access after a computer problem.
One phone in a home
For a person checking Rogers or Telus email primarily on one phone, I'd still use IMAP on port 993 and SMTP submission on port 587. Enable the mail app's normal background or push behaviour where the provider supports it. That keeps the phone's view aligned with webmail, which becomes a useful fallback if the device is lost or damaged.
The setup stays simple because SMTP sends and IMAP receives. There's no benefit in choosing POP3 merely because one device is currently in use.
A hybrid worker with two identities
A hybrid worker using a work laptop and personal phone needs one shared mailbox, not two disconnected downloads. Configure IMAP with a cached local copy, then use SMTP on port 587 for sending. If the worker sends from a second approved identity, configure that as a permitted send-as alias rather than creating an unrelated POP3 silo.
This arrangement keeps sent messages and folder decisions visible across the devices. It also makes troubleshooting more predictable because both clients use the same server-side mailbox.
A shared family mailbox
A shared family address on an iPad or kitchen computer should stay on IMAP. Give each person a folder convention, such as a named folder for messages they're handling, rather than relying on POP3 to make separate local copies.
That approach prevents one person from downloading and removing mail before another person sees it. It also preserves a common view when someone checks the address from webmail.
A small business using a hosted suite
Microsoft 365 and Google Workspace accounts often use their native Exchange or provider connectors instead of manually configuring basic IMAP. Where the service uses ActiveSync or a native Exchange or Graph connection, follow that provider-specific path. SMTP on port 587 remains the outbound relay for devices such as scanners and customer relationship management applications when the service permits authenticated submission.
For business email, I recommend IMAP-style central access or the provider's native synchronisation connector. POP3 should not be the standard for a small office.
When POP3 Is Still the Better Call
POP3 is mostly obsolete for ordinary daily email, but obsolete doesn't mean useless. I recommend it only when a client has several gigabytes of email that they absolutely cannot delete, and the provider's IMAP storage limit makes keeping the entire archive on the server impractical.
My usual approach is to inspect the mailbox first. If the client can delete redundant messages or archive older material safely, I reduce the mailbox and use IMAP. If the old collection must remain intact, I keep those older emails local on a computer that is being backed up, then configure IMAP for newer messages. The result separates the historical archive from the active multi-device mailbox.
Government of Canada email configuration standards specify a mailbox size of no larger than 100 GB and no smaller than 25 GB, with attachments no larger than 25 MB (Government of Canada email configuration reference). Those thresholds don't decide the configuration by themselves, but they show why mailbox capacity can become a genuine planning issue rather than a theoretical concern.
The right POP3 conditions
POP3 makes sense only when all of these conditions are understood:
- Local ownership: One trusted computer becomes the primary place where downloaded messages live.
- Verified backup: The local mail store is included in a working backup and can be restored.
- Limited device access: The client accepts that phones and webmail won't show the same complete archive.
- Clear retention plan: The client knows which messages remain online and which move into the local archive.
Use POP3 on port 995 with TLS and send through SMTP on port 587. I don't treat “leave a copy on the server” as a backup. It creates another copy, but it doesn't replace a tested local backup strategy.
For help protecting that local archive, use Nerds 2 You's guide to backing up Outlook emails. The trade-off remains direct: POP3 offers offline-first access, but it loses multi-device state, server-side search across the full archive, and the convenience of a shared mailbox.
Security Beyond the Protocol Choice
A secure port won't stop a convincing phishing message, a stolen password, or a spoofed business domain. Canadian cyber guidance focuses email risk on phishing, spoofing, impersonation, and business email compromise, with protection built around encrypted transport and domain controls rather than a simple IMAP-versus-POP3 decision (Canadian Centre for Cyber Security guidance).
TLS protects data moving between the client and server. It doesn't protect the inbox after an attacker authenticates with a stolen password or token. That's why I treat the protocol settings as one layer in a larger configuration.
The controls that matter
| Layer | What It Does | Where It Lives | 2026 Recommendation |
|---|---|---|---|
| TLS | Encrypts the connection between client and server | Email client and mail service | Use secure IMAP, POP3 only when deliberate, and authenticated SMTP |
| SPF | Lists authorised sending hosts for a domain | Domain DNS | Publish and maintain one accurate policy |
| DKIM | Adds a cryptographic signature that receivers can verify | Sending service and domain DNS | Enable signing for every legitimate sender |
| DMARC | Connects domain alignment, receiver policy, and reporting | Domain DNS and receiving mail systems | Deploy deliberately and review reports regularly |
| Two-factor authentication | Adds an additional account verification step | Mail account and identity provider | Enable it for every supported mailbox |
| Access controls and logs | Restrict and record administrative activity | Mail platform and business systems | Review RBAC and audit log details when evaluating broader access governance |
For a normal account, use IMAP on 993 with implicit TLS and SMTP submission on 587 with STARTTLS, subject to the provider's authentication requirements. Use OAuth-based sign-in where available, or an app password where the provider requires one for a two-factor account. After migration, revoke old app passwords and unused sessions instead of leaving them active indefinitely.
SPF, DKIM, and DMARC address a different problem from mailbox retrieval. SPF identifies authorised sending infrastructure, DKIM lets the receiver validate a signed message, and DMARC connects authentication alignment with policy and reporting. Together, they are far more relevant to spoofing and domain impersonation than choosing IMAP instead of POP3.
For an Edmonton office, the practical sequence is clear:
- Secure account access: Enable two-factor authentication and remove obsolete credentials.
- Harden the client: Use encrypted IMAP and authenticated SMTP submission.
- Protect the domain: Publish SPF, enable DKIM, and configure DMARC.
- Review activity: Check authentication and DMARC reports monthly, then investigate unfamiliar senders or sign-ins.
- Retire POP3: Keep it only where local archiving is intentional, backed up, and documented.
Nerds 2 You doesn't provide remote services or full MSP services, but it does provide ongoing support and network monitoring for small and medium businesses. The team also handles most major hardware repairs on site, while board-level repairs aren't provided. For a deeper setup review, see the business email setup service.
Nerds 2 You Edmonton can configure IMAP, POP3, and SMTP on supported computers and phones, organise local archives, and help verify backups and account security. Visit Nerds 2 You Edmonton to arrange on-site email setup, hardware support, or ongoing network monitoring for your Edmonton home or small business.
Contact Nerds 2 You for quality professional service
Experience the difference with our dedicated team of experts ready to assist you. Whether you need immediate support or have questions about our services, we are here to help. Reach out today and let us provide you with the reliable service you deserve. Your satisfaction is our priority and we guarantee a prompt response to all inquiries.