Email headers are not safely modeled as a dictionary with one value per field name.
A message can contain multiple Received fields, and their order is essential to reconstructing the route.
Other fields have cardinality and placement rules defined by message-format specifications.
When writing parsers, preserve repeated fields and original ordering unless the relevant standard explicitly says otherwise.