GNOME Bugzilla – Bug 274382
Multiple CC headers are not processed properly
Last modified: 2013-09-10 13:50:00 UTC
My collegue sends email using Emacs with something like the following in the header: ---- To: xxx1@blah.com Cc: xx2@blah.com, xx3@blah.com Cc: xxx4@blah.com, xxx5@blah.com, xxx6@blah.com, xxx7@blah.com Bcc: --- In the Evolution email source view I see: --- To: xxx1@blah.com Cc: xxx4@blah.com, xxx5@blah.com, xxx6@blah.com, xxx7@blah.com Bcc: --- Note that the xx2 and xx3 values from the first CC header are missing! I cannot filter on these either. For all intensive purposes, they are lost and ignored by Evolution.
Just to be clear on why I marked this as 'Major' severity... If I 'Reply to All', any addresses in the first CC will not receieve that or subsequent information in the email thread. There is no no work around to see who I missed, or for me to even tell when this has happened in the past. When the email is moved from my IMAP server to the local mbox file, this information is irretrievably lost (I tried loading the file directly). Needless to say, this is unacceptable in my work environment.
RFC 2822 mandates exactly one CC header - so evolution is NOT broken, but emacs is. :-) minoring majority, i'd also like to close this one because it's just a broken mailer - if evolution e.g. would take care of all those outlook bugs there wouldn't be time to do sth different... ;-)
I am sorry Andre, but you are incorrect, Evolution is broken... From: http://www.faqs.org/rfcs/rfc2822.html 1.3. Structure of this document Section 4 of this document specifies an "obsolete" syntax. There are references in section 3 to these obsolete syntactic elements. The rules of the obsolete syntax are elements that have appeared in earlier revisions of this standard or have previously been widely used in Internet messages. As such, these elements MUST be interpreted by parsers of messages in order to be conformant to this standard. 4.5. Obsolete header fields Except for destination address fields (described in section 4.5.3), the interpretation of multiple occurrences of fields is unspecified. 4.5.3. Obsolete destination address fields obs-to = "To" *WSP ":" address-list CRLF obs-cc = "Cc" *WSP ":" address-list CRLF obs-bcc = "Bcc" *WSP ":" (address-list / [CFWS]) CRLF When multiple occurrences of destination address fields occur in a message, they SHOULD be treated as if the address-list in the first occurrence of the field is combined with the address lists of the subsequent occurrences by adding a comma and concatenating.
chris: ok, i should read it more carefully, thanks... :-)
Created attachment 50167 [details] [review] should fix
committed, will go into 2.2.x too.
Just wanted to send a big THANKS for your work on this! :)