<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Support multimessage view</title> 
  <pubDate>Mon, 06 Apr 2026 01:10:06 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/481</link> 
  <atom:link rel="self" type="application/rss+xml" title="Support multimessage view" href="https://bugs.horde.org/ticket/481/rss" /> 
  <description>Support multimessage view</description> 
 
   
   
  <item> 
   <title>ON low bandwidth links it&#039;s often a pain to view mesages one</title> 
   <description>ON low bandwidth links it&#039;s often a pain to view mesages one by one. It is easier to select the messages you want to read (usually all unread ones) and click one button to have a page presented which shows all the selected messages one after the other. I once patched aeromail locally to do this. An enormous benefit. 



When the link is slow, you do one page load and come back when its done then read your mails. It takes a little coding to ensure that all the links relevant to each message maintain that functionality, but otherwise you just repeat the standard message view over and over.</description> 
   <pubDate>Sat, 14 Aug 2004 00:36:24 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/481#t1706</link> 
  </item> 
   
  <item> 
   <title>If at all, this will be done in HEAD only.</title> 
   <description>If at all, this will be done in HEAD only.</description> 
   <pubDate>Sat, 14 Aug 2004 09:45:06 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/481#t1708</link> 
  </item> 
   
  <item> 
   <title>Had to do some reasearch on horde.org, but finally worked ou</title> 
   <description>Had to do some reasearch on horde.org, but finally worked out what HEAD means, and yes, of course that&#039;s the queue version I should have filed it on to begin with! Newbie moi. (may be advisable to put a little tip on http://bugs.horde.org/ticket/create.php about queue versions ...)</description> 
   <pubDate>Sat, 14 Aug 2004 12:09:02 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/481#t1710</link> 
  </item> 
   
  <item> 
   <title>Bounty added: http://www.horde.org/bounties/details.php#imp_</title> 
   <description>Bounty added: http://www.horde.org/bounties/details.php#imp_multimessage</description> 
   <pubDate>Sun, 20 Feb 2005 21:27:44 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/481#t5689</link> 
  </item> 
   
  <item> 
   <title>Initial implementation finished in HEAD.</title> 
   <description>Initial implementation finished in HEAD.</description> 
   <pubDate>Sat, 04 Jun 2005 07:46:25 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/481#t8848</link> 
  </item> 
   
  <item> 
   <title>Looks great! Is it by intention that there is now an empty s</title> 
   <description>Looks great! Is it by intention that there is now an empty space between all messages? IIRC these haven&#039;t been there before.</description> 
   <pubDate>Mon, 06 Jun 2005 11:29:19 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/481#t8896</link> 
  </item> 
   
  <item> 
   <title>Huh - that space has been around for 3+ months (since revisi</title> 
   <description>Huh - that space has been around for 3+ months (since revision 1.3):

http://cvs.horde.org/annotate.php/imp/templates/thread/thread.html?rev=1.7#46



I personally prefer the space between the messages because, to me, it helps me distinguish between the messages easier.  But whatever others think is better is fine by me.



I&#039;m going to go ahead and close this ticket as further usage over 5 or so days now indicates the code is working well - further bug/enhancement reports can be handled via dev@ or new tickets.</description> 
   <pubDate>Wed, 08 Jun 2005 03:56:57 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/481#t8965</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
