Send Works, Receive Fails: Checking IMAP First

220-1201 By islever Editorial Last updated

Given a scenario, troubleshoot network issues Compare and contrast Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) ports, protocols, and their purposes

Short answer

C Check the laptop's incoming IMAP server name, port, and authentication/TLS settings, since outbound SMTP already works.

Question

An end user is able to send emails but not receive them. Which of the following settings should a technician check first on the user's laptop to troubleshoot the issue?
  1. DNS
  2. SMTP
  3. IMAP Correct Answer
  4. DMARC

Key Takeaways

The question tests whether you can map email send and receive operations to their protocols; the trap is blaming SMTP or DNS when the symptom already proves the outbound path works.

When an end user can send email but cannot receive it, the inbound IMAP configuration is the first thing to verify on the laptop. This 220-1201 question confirms that option C, IMAP, is the correct setting to check, while SMTP, DNS, and DMARC are not.

Common mistake: Choosing B (SMTP), because email troubleshooting instinctively points at the mail protocol — but SMTP handles sending, which is the one function that already works.

Expert Analysis

The governing principle: match the protocol to the direction of the flow. Email uses two distinct protocol families on the client. Outbound submission is handled by SMTP (Simple Mail Transfer Protocol), typically on TCP 25/587/465, while inbound retrieval and synchronization is handled by IMAP (TCP 143/993) or, less commonly today, POP3. Because the user can successfully send mail, the SMTP host, port, credentials, DNS resolution of the outgoing server, and general network connectivity are all demonstrably working. The failure is therefore isolated to the inbound leg.

Mapping the scenario to option C. The first thing to check on the laptop is the IMAP configuration: incoming server hostname, IMAP port (143 vs. implicit-TLS 993), authentication method, and SSL/TLS certificate validation, plus whether the account was accidentally set up as POP3 against a mailbox that only supports IMAP. A wrong incoming server name, a blocked port at the firewall, or a failed TLS handshake produces exactly this signature — send succeeds, receive never arrives.

Why the other options fail. Option B, SMTP, is the sending path and is already proven good by the symptom. Option A, DNS, is a poor first check: resolving the SMTP server is required for sending, and that resolution clearly succeeded, so DNS is not the discriminating variable — though it becomes relevant only if the incoming server name fails to resolve. Option D, DMARC, is a domain-level DNS policy published by the message sender's domain to instruct receiving mail servers how to handle authentication failures; it is not a laptop setting a technician edits and it does not block a local mailbox from syncing.

Verdict: option C.

Official Reference

https://www.comptia.org/training/resources/exam-objectives

This link opens the official vendor documentation in a new tab.

Exam Strategy

Read the symptom as a direction-of-traffic clue and split email into outbound (SMTP) versus inbound (IMAP/POP3) paths before looking at the options. Eliminate any option that governs the direction that already works, and eliminate anything that is a domain-level DNS policy rather than a client setting you can actually edit on the laptop. Apply the same move to any 'one direction works, the other does not' question involving ports, protocols, or firewall rules.

Frequently Asked Questions

Why isn't SMTP the first setting to check if email is broken?

SMTP is used only to send mail. Since the user can send successfully, the SMTP server, port, credentials, and connectivity are already proven good, so the fault must be on the receiving side.

Could DNS be the real cause of not receiving email?

Only if the incoming IMAP server hostname fails to resolve, but DNS is also needed to reach the SMTP server, and sending works. Check the IMAP server name, port, and TLS settings first, then verify DNS if the hostname does not resolve.

What is DMARC and why is it not the answer here?

DMARC is a DNS-based policy published by a domain's owners that tells receiving mail servers how to handle messages failing SPF or DKIM checks. It is configured at the domain level, not as a laptop client setting a technician edits.

More 220-1201 FAQ →

Community Votes

C
100%

100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 1 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 1

  1. Afie 👍 1 Answered C
    The user can send emails but cannot receive them. SMTP (Simple Mail Transfer Protocol) is used for sending email. IMAP (Internet Message Access Protocol) is used for receiving and synchronizing email messages from the mail server. Since sending works, the outgoing email settings are likely correct. The technician should first check the IMAP settings (server name, port, authentication, SSL/TLS settings).

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Practice All 220-1201 Questions

Access 105 questions with complete answers and detailed explanations.

View Full 220-1201 Practice Test →

← Back to 220-1201 Study Guide