II0-001 · Question #162
Added "Received:" headers often include bogus information. All of the following items except one, is usually incomplete:
The correct answer is A. "To:" header. Option A is correct because the "To:" header is not part of "Received:" headers at all - it's a separate message header set by the sender, so it cannot be "usually incomplete" within Received: trace data. The question targets what Received: headers actually contain and how…
Question
Added "Received:" headers often include bogus information. All of the following items except one, is usually incomplete:
Options
- A"To:" header
- BIDs
- CPath
- DDates
How the community answered
(42 responses)- A79% (33)
- B5% (2)
- C14% (6)
- D2% (1)
Explanation
Option A is correct because the "To:" header is not part of "Received:" headers at all - it's a separate message header set by the sender, so it cannot be "usually incomplete" within Received: trace data. The question targets what Received: headers actually contain and how reliable that content is.
The distractors (B, C, D) are wrong because they are genuine components of Received: headers that are routinely falsified or incomplete: IDs (message/server identifiers can be forged or omitted), Path (the relay chain of hostnames/IPs is easily spoofed, especially by malicious senders), and Dates (timestamps depend on the sending server's clock and can be manipulated or simply wrong).
Memory tip: Think of Received: headers as a travel log stamped by each mail server - they record the journey (path, when/dates, who handled it/IDs). The "To:" field is the address on the envelope, written before the journey begins and managed separately - it never lives inside the travel log.
Community Discussion
No community discussion yet for this question.