[Tickets #8719] IMP ignores additional list-* header-field tokens and chooses the less approriate one
bugs at horde.org
bugs at horde.org
Thu Nov 19 15:42:12 UTC 2009
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/8719
------------------------------------------------------------------------------
Ticket | 8719
Created By | peter.meier at immerda.ch
Summary | IMP ignores additional list-* header-field tokens and
| chooses the less approriate one
Queue | IMP
Version | 4.3.5
Type | Bug
State | Unconfirmed
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
peter.meier at immerda.ch (2009-11-19 10:42) wrote:
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 at googlegroups.com>
vs. the earlier one:
List-Post: <mailto:some-group at 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
More information about the bugs
mailing list