| Summary | IMP ignores additional list-* header-field tokens and chooses the less approriate one |
| Queue | IMP |
| Queue Version | 4.3.5 |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | slusarz (at) horde (dot) org |
| Requester | peter.meier (at) immerda (dot) ch |
| Created | 11/19/2009 (5698 days ago) |
| Due | |
| Updated | 01/13/2010 (5643 days ago) |
| Assigned | 11/19/2009 (5698 days ago) |
| Resolved | 11/19/2009 (5698 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Bug #8719: Fix List-Post parsinghttp://git.horde.org/diff.php/imp/docs/CHANGES?rt=horde-git&r1=7f52cfe330ff812639803818a34d074546ec3f5e&r2=4b2f4623ae225c6bb2fb0b514ba039e24d114098
http://git.horde.org/diff.php/imp/lib/UI/Message.php?rt=horde-git&r1=e5d9fe667683cc55d02274431d66da299a5af8eb&r2=4b2f4623ae225c6bb2fb0b514ba039e24d114098
Web-Application, hence Web-Access preferred, or a MUA which prefers
the mail way. But you are the people deciding that.
address. So this part needs to be fixed.
State ⇒ Resolved
Bug: 8719Merge from git:horde-hatchery 4b2f4623ae225c6bb2fb0b514ba039e24d114098
http://cvs.horde.org/diff.php/imp/docs/CHANGES?rt=horde&r1=1.699.2.412&r2=1.699.2.413&ty=u
http://cvs.horde.org/diff.php/imp/lib/MIME/Headers.php?rt=horde&r1=1.92.2.40&r2=1.92.2.41&ty=u
Bug #8719: Fix List-Post parsinghttp://git.horde.org/diff.php/imp/docs/CHANGES?rt=horde-hatchery&r1=7f52cfe330ff812639803818a34d074546ec3f5e&r2=4b2f4623ae225c6bb2fb0b514ba039e24d114098
http://git.horde.org/diff.php/imp/lib/UI/Message.php?rt=horde-hatchery&r1=e5d9fe667683cc55d02274431d66da299a5af8eb&r2=4b2f4623ae225c6bb2fb0b514ba039e24d114098
State ⇒ Assigned
Assigned to Michael Slusarz
A list of multiple, alternate, URLs MAY be specified by a comma-
separated list of angle-bracket enclosed URLs. **The URLs have order of
preference from left to right.** The client application should use the
left most protocol that it supports, or knows how to access by a
separate application.
We are viewing on a web browser. Thus, by definition, a HTTP URL is
supported. So we show ONLY the first element we support when reading
left-to-right. Google is telling us that it prefers we post to groups
via the web (for obvious reasons) than via e-mail so we need to honor
that preference.
However, when replying, we obviously need to grab the e-mail address.
So this part needs to be fixed.
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ IMP ignores additional list-* header-field tokens and chooses the less approriate one
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
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