<?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>Interface misleads users into losing messages</title> 
  <pubDate>Fri, 10 Apr 2026 04:00:02 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/7783</link> 
  <atom:link rel="self" type="application/rss+xml" title="Interface misleads users into losing messages" href="https://bugs.horde.org/ticket/7783/rss" /> 
  <description>Interface misleads users into losing messages</description> 
 
   
   
  <item> 
   <title>Hi, I reported earlier today about how the &#039;Reply&#039; option mi</title> 
   <description>Hi, I reported earlier today about how the &#039;Reply&#039; option misleads users into addressing their list messages to the wrong address, which results in the mail list missing messages without anyone noticing.

My report, numbered 7782, was answered in a quickly way which I do appreciate.  I&#039;ve been told the usability bug I reported of is actually a deliberate choice related to some ancient discussion about &quot;Reply-To&quot; munging which I just think is way off its time.  But then, IMP is Open Source, and released under a license that allows me to use it for free, and I should be just happy about people making it.  So all right, I can accept IMP has got to have different options, one for replying to the sender and another to replying to the mail list.

Still, messages are getting lost, and that is a fault I cannot oversee.  The &#039;Blame the people for not learning to do things our way&#039; approach I think is out of any serious usability conception.

Usability is about to make things work the way people expects them to.  We are in 2008, and today when people clicks on a &#039;Reply&#039; option expects to send the reply *to the same place it came from*, and that includes mail lists.

So, all right, keep the separated options for replying to the sender and to the mail list.  But then, I you do so, if you&#039;re smart enough to detect the messages that need a &#039;Reply to list&#039; option, then don&#039;t allow the option for replying to the sender to be named &#039;Reply&#039;.  This is only misleading - you&#039;re fooling people into getting their messages lost.  Rename that option into &#039;Reply to sender&#039;, and that will be just fine.



Thank you for your attention.</description> 
   <pubDate>Tue, 16 Dec 2008 12:52:38 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7783#t51287</link> 
  </item> 
   
  <item> 
   <title>&gt; Still, messages are getting lost, and that is a fault I ca</title> 
   <description>&gt; Still, messages are getting lost, and that is a fault I cannot 

&gt; oversee.  The &#039;Blame the people for not learning to do things our 

&gt; way&#039; approach I think is out of any serious usability conception.



You still don&#039;t get it, do you? Again, this is not a bug, but behavior that is mandated by RFC-2822:



&quot;The originator fields also provide the information required when replying to a message.  When the &quot;Reply-To:&quot; field is present, it indicates the mailbox(es) to which the author of the message suggests that replies be sent.  In the absence of the &quot;Reply-To:&quot; field, replies SHOULD by default be sent to the mailbox(es) specified in the &quot;From:&quot; field unless otherwise specified by the person composing the reply.&quot;



In this case, the operator of the mailing list (the originator of mailing list messages) has decided not to munge the reply field. If you don&#039;t like that, your should complain to the people operating the mailing list.</description> 
   <pubDate>Tue, 16 Dec 2008 13:07:40 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7783#t51288</link> 
  </item> 
   
  <item> 
   <title>And please stop creating duplicate tickets.</title> 
   <description>And please stop creating duplicate tickets.</description> 
   <pubDate>Tue, 16 Dec 2008 13:14:36 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7783#t51290</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
