Tickets :: Comment on [#8719] IMP ignores additional list-* header-field tokens and chooses the less approriate one

* Your Email Address
* Spam protection	Enter the letters below: . .. ..__. .. . \|__\|\| \|\| \| \|\ / \| \|\|/\\|\|__\\__\| \/
Comment	> Recently google-groups added an additional post mechanism to the > List-Post field in mails from their lists: > > List-Post: <http://groups.google.com/group/some-group/post?hl=>, > <mailto:some-group@googlegroups.com> > > vs. the earlier one: > > List-Post: <mailto:some-group@googlegroups.com> > > This is completely valid by RFC. > > However, IMP now displays only the first token (the url) when > choosing to display the List-Headers, as well if we choose to reply > to the the list (Reply -> To List) IMP chooses the url as recipient. > > Regarding RFC 2369 [1] this header is correct but it is up to the MUA > to choose the option he can use, which would be the mailto: option in > IMP's case. > > Hence IMP should: > > - Display all Tokens in the List Header Overview > - Prefer the mailto Token over any url token > > [1] http://www.ietf.org/rfc/rfc2369.txt
Attachment
Watch this ticket