IMP ignores additional list-* header-field tokens and chooses the less approriate one

Recently google-groups added an additional post mechanism to

Thu, 19 Nov 2009 15:42:12 +0000

Recently google-groups added an additional post mechanism to the List-Post field in mails from their lists: List-Post: , vs. the earlier one: List-Post: 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

> - Display all Tokens in the List Header Overview No. Fr

Thu, 19 Nov 2009 18:53:37 +0000

> - Display all Tokens in the List Header Overview No. From RFC 2369[2]: 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. > - Prefer the mailto Token over any url token No. See above. However, when replying, we obviously need to grab the e-mail address. So this part needs to be fixed.

Changes have been made in Git for this ticket: Bug #8719: F

Thu, 19 Nov 2009 19:01:55 +0000

Changes have been made in Git for this ticket: Bug #8719: Fix List-Post parsing http://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

Changes have been made in CVS for this ticket: Bug: 8719 Me

Thu, 19 Nov 2009 19:04:37 +0000

Changes have been made in CVS for this ticket: Bug: 8719 Merge 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

Fixed in 4.3.6.

Thu, 19 Nov 2009 19:05:08 +0000

Fixed in 4.3.6.

> We are viewing on a web browser. Thus, by definition, a H

Thu, 19 Nov 2009 23:18:58 +0000

> 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. > >> - Prefer the mailto Token over any url token > > No. See above. ok, I agree. It's a point of view, if IMP is either more a Web-Application, hence Web-Access preferred, or a MUA which prefers the mail way. But you are the people deciding that. > However, when replying, we obviously need to grab the e-mail address. > So this part needs to be fixed. fine. Thank you!

Changes have been made in Git for this ticket: Bug #8719: F

Wed, 13 Jan 2010 00:15:49 +0000

Changes have been made in Git for this ticket: Bug #8719: Fix List-Post parsing http://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