Screenshot shows Testcase 1 with duplicate headers in source. - inconsistent headers in message list vs message reader - inconsistent in msg reader: To/CC (wrongly showing both instances) vs. Bcc (showing first instance only) - Reply confusion: Attribution line uses second headers for XX wrote and the date - Reply wrongly includes 2nd instances of original From/To as reply recipients - Reply-all skips the CC recipients of the original message (should use first instance of original CC) For developers' convenience, here's the details... Only checkmarks `✔` and `n/a` are correct behaviour afasics. | Header | Message list | Message reader | Replies | Reply-All | | -------- | ------------- | ---------------------------- | ------------------------------------------------------- | ------------------------------------------------------------ | | From: | 1st From ✔ | 2nd From | Reply goes to 1st & 2nd From, vs. "2nd From wrote: ..." | Replies goes to 1st & 2nd From vs. "2nd From wrote ..." | | Subject: | 1st Subject ✔ | 1st Subject ✔ | 1st Subject ✔ | 1st Subject ✔ | | Date: | 1st Date | 2nd Date | 2nd Date | "... wrote on 2nd Date" | | To: | 1st & 2nd To | 1st & 2nd To | n/a | Reply recipients include: 1st & 2nd To | | Cc: | 1st & 2nd Cc | not shown in msg list (bugs) | n/a | missing (reply-all fails to include any one of the original Cc recipients) | | Bcc: | 1st Bcc | not shown in msg list (bugs) | n/a | n/a (by design no reply to original bcc, to prevent accidental exposure) | (Table done with [Typora](https://typora.io/), thanks to Ryan for recommending that!) (In reply to Thomas D. (:thomas8) from comment #4) > Confirming for 88.0a1 (2021-03-17) (64-bit). > We have inconsistent handling of malformed messages with multiple headers of same type (To, From, Date etc.) in spite of max-number=1. > Particularly, what we show in message header vs. message list is *different*, which is quite confusing.
Bug 705587 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Screenshot shows Testcase 1 with duplicate headers in source. - inconsistent headers in message list vs message reader - inconsistent in msg reader: To/CC (wrongly showing both instances) vs. Bcc (showing first instance only) - Reply confusion: Attribution line uses second headers for XX wrote and the date - Reply wrongly includes 2nd instances of original From/To as reply recipients - Reply-all skips the CC recipients of the original message (should use first instance of original CC) For developers' convenience, here's the details... Only checkmarks `✔` and `n/a` are correct behaviour afasics. | **Header** | **Message list** | **Message reader** | **Replies** | **Reply-All** | | -------- | ------------- | ---------------------------- | ------------------------------------------------------- | ------------------------------------------------------------ | | From: | 1st From ✔ | 2nd From | Reply goes to 1st & 2nd From, vs. "2nd From wrote: ..." | Replies goes to 1st & 2nd From vs. "2nd From wrote ..." | | Subject: | 1st Subject ✔ | 1st Subject ✔ | 1st Subject ✔ | 1st Subject ✔ | | Date: | 1st Date | 2nd Date | 2nd Date | "... wrote on 2nd Date" | | To: | 1st & 2nd To | 1st & 2nd To | n/a | Reply recipients include: 1st & 2nd To | | Cc: | 1st & 2nd Cc | not shown in msg list (bugs) | n/a | missing (reply-all fails to include any one of the original Cc recipients) | | Bcc: | 1st Bcc | not shown in msg list (bugs) | n/a | n/a (by design no reply to original bcc, to prevent accidental exposure) | (Table done with [Typora](https://typora.io/), thanks to Ryan for recommending that!) (In reply to Thomas D. (:thomas8) from comment #4) > Confirming for 88.0a1 (2021-03-17) (64-bit). > We have inconsistent handling of malformed messages with multiple headers of same type (To, From, Date etc.) in spite of max-number=1. > Particularly, what we show in message header vs. message list is *different*, which is quite confusing.
Screenshot shows Testcase 1 with duplicate headers in source (relevant message list columns shown are subject, correspondents, and date). - inconsistent headers in message list vs message reader - inconsistent in msg reader: To/CC (wrongly showing both instances) vs. Bcc (showing first instance only) - Reply confusion: Attribution line uses second headers for XX wrote and the date - Reply wrongly includes 2nd instances of original From/To as reply recipients - Reply-all skips the CC recipients of the original message (should use first instance of original CC) For developers' convenience, here's the details... Only checkmarks `✔` and `n/a` are correct behaviour afasics. | **Header** | **Message list** | **Message reader** | **Replies** | **Reply-All** | | -------- | ------------- | ---------------------------- | ------------------------------------------------------- | ------------------------------------------------------------ | | From: | 1st From ✔ | 2nd From | Reply goes to 1st & 2nd From, vs. "2nd From wrote: ..." | Replies goes to 1st & 2nd From vs. "2nd From wrote ..." | | Subject: | 1st Subject ✔ | 1st Subject ✔ | 1st Subject ✔ | 1st Subject ✔ | | Date: | 1st Date | 2nd Date | 2nd Date | "... wrote on 2nd Date" | | To: | 1st & 2nd To | 1st & 2nd To | n/a | Reply recipients include: 1st & 2nd To | | Cc: | 1st & 2nd Cc | not shown in msg list (bugs) | n/a | missing (reply-all fails to include any one of the original Cc recipients) | | Bcc: | 1st Bcc | not shown in msg list (bugs) | n/a | n/a (by design no reply to original bcc, to prevent accidental exposure) | (Table done with [Typora](https://typora.io/), thanks to Ryan for recommending that!) (In reply to Thomas D. (:thomas8) from comment #4) > Confirming for 88.0a1 (2021-03-17) (64-bit). > We have inconsistent handling of malformed messages with multiple headers of same type (To, From, Date etc.) in spite of max-number=1. > Particularly, what we show in message header vs. message list is *different*, which is quite confusing.