Re: [Mutt] #2934: does not honor Reply-To when replying to message
#2934: does not honor Reply-To when replying to message from self
Comment (by Derek Martin):
{{{
On Thu, Jul 19, 2007 at 07:23:42PM -0000, Mutt wrote:
> When replying to a message sent by yourself, Mutt does not honor the
> Reply-To header, and sends the reply to the original recipients instead
> (as per $reply_self=no). This is coming from the assumption that the
> address found in te Reply-To header would be an alternate address of
> yourself, and hence should not receive the reply.
It seems obvious to me that if you've bothered to set a reply-to
header on your messages, you want all replies to go to that address,
including replies from yourself... But one or two people complained
about that idea when I raised it before.
> However, it may as well be the case that the address in the Reply-To
> header is some other address, or one's address plus some other address.
> While I'll agree that (r)eplying to Reply-To instead of recipient on
> self messages can be discussed (please make a decision nonetheless), I
> strongly believe that it should be included when (g)roup-replying.
I agree completely, and I think even the (r)eply case is an easy fix.
Just check whether the addresses in Reply-To: match alternates, and
remove the ones that match (assuming you've configured mutt not to reply
to yourself). If you're left with an empty list (Reply-To can contain
multiple e-mail addresses), then use the original recipients instead.
Alternately, if you find a match to alternates, you could just always
copy the original recipients, in addition to whatever addresses didn't
match alternates. I think this behavior is kind of stupid, but it may
be what some people want, and it eliminates a special case. I suppose
it's easier to remove addresses which Mutt added, than it would be to
add addresses it decided not to add (particularly if they are not
addresses you have in your address book).
}}}
--
Ticket URL: <http://dev.mutt.org/trac/ticket/2934#comment:>