1097820 - [email] Normalize addressparser output for groups

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::E-Mail, defect)

Description

[James Burke [:jrburke]]

This came up in bug 1087184 comment 25, the main issue:

"We found an edge case that causes breakage relating to the "group" syntax used in the "undisclosed-recipients:;" idiom when there are no listed recipients of a message."

The best fix, to prevent issues long term:

addressparser (at least the one we use for 2.1/2.2) returns { name, group: [ {name, address}... ]}  instead of just { name, address } when it sees a group.

On trunk we probably want to:
- Create a flatAddressParser that has normalized output so that all entries in the array are of the form { name, address } with name optionally being null.
- Have the invariant that all addresses always look like that prior to contact normalization.

Note that the specific issue called out in bug 1087184 is fixed, by guarding for `undefined` in the group case, as it is the only case we have hit so far that ran into this issue. However, for long term sanity and to prevent future problems, the normalization should be done.

Comment 1

[BMO Automation]

Firefox OS is not being worked on