[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mutt-dev
Subject:    Re: [Mutt] #2304: reply / group reply behavior broken WRT $reply_to
From:       Mutt <fleas () mutt ! org>
Date:       2009-02-20 16:24:02
Message-ID: 060.d93e6b3cc2e3afbddf62e76b4fdbdc9c () mutt ! org
[Download RAW message or body]

#2304: reply / group reply behavior broken WRT $reply_to and $reply_self
----------------------------------+-----------------------------------------
  Reporter:  code@pizzashack.org  |       Owner:  mutt-dev                                      
      Type:  defect               |      Status:  new                                           
  Priority:  minor                |   Milestone:                                                
 Component:  mutt                 |     Version:  1.5.11 (and all others, including current CVS)
Resolution:                       |    Keywords:  patch                                         
----------------------------------+-----------------------------------------
Changes (by pdmef):

  * keywords:  => patch


Old description:

> {{{
> There seems to be a problem with how mutt handles $reply_to and
> $reply_self.  In particular, it seems to behave badly replying to
> some combinations of e-mails which are sent by oneself, and contain a
> Reply-to header.
>
> This is a bit complicated, as the interactions of these two variables
> forms a 3-dimensional decision matrix.  I apologize for the complexity
> of this bug report, but there's no way around it; it's a complex
> issue.
>
> The essential problem is that when $reply_to is set (and there is a
> Reply-to header), but $reply_self is unset, Mutt does the wrong thing.
> It ignores the Reply-to header completely, whether the user is
> REPLYing or GROUPREPLYing.  This apparently is true of all versions of
> Mutt including and prior to the current CVS.
> >How-To-Repeat:
> >Fix:
> Unknown
> }}}

New description:

 {{{
 There seems to be a problem with how mutt handles $reply_to and
 $reply_self.  In particular, it seems to behave badly replying to
 some combinations of e-mails which are sent by oneself, and contain a
 Reply-to header.

 This is a bit complicated, as the interactions of these two variables
 forms a 3-dimensional decision matrix.  I apologize for the complexity
 of this bug report, but there's no way around it; it's a complex
 issue.

 The essential problem is that when $reply_to is set (and there is a
 Reply-to header), but $reply_self is unset, Mutt does the wrong thing.
 It ignores the Reply-to header completely, whether the user is
 REPLYing or GROUPREPLYing.  This apparently is true of all versions of
 Mutt including and prior to the current CVS.
 >How-To-Repeat:
 >Fix:
 Unknown
 }}}

--

Comment:

 Any objections why this shouldn't be applied?

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/2304#comment:15>
Mutt <http://www.mutt.org/>
The Mutt mail user agent


[prev in list] [next in list] [prev in thread] [next in thread]