Re: Mail-followup-to oddity
* Mon Nov 14 2005 Rado S <rado@xxxxxxxxxxxxxxxxxxx>
> recently I learned that list-reply replies to a subscribed ML
> _in addition_ to MFT. Intuitively I expect that replies are _only_
> sent to MFT (much like Reply-To:).
Is this what you meant:
| Muttrc has "set honor_followup_to" and
| "subscribe mutt-dev".
|
| When a message has MFT:<bugs-any> and TO:<mutt-dev>,
| a <list-reply> to the message will be addressed
| TO:<mutt-dev> and CC:<bugs-any>.
Although I don't know whether this is intended,
this COULD be right, because
0) bugs-any is not (declared as) a list, and
1) you can use group-reply instead.
But the next case is certainly a bug:
| Muttrc has "set honor_followup_to",
| "subscribe mutt-dev" and "lists bugs-any".
| ^^^^^^^^^^^^^^^^^^^^
| When a message has MFT:<bugs-any> and TO:<mutt-dev>,
| a <list-reply> to the message will be addressed
| TO:<mutt-dev> and CC:<bugs-any>.
The reply should be TO:<bugs-any>.
> Can we change list-reply to send only to MFT if that exists?
Sounds good. Which do you expect?:
| If a MFT header has a list's address and a non-list address,
| <list-reply> should be sent to:
|
| 0) both <list> and <non-list> or
| 1) only <list>
Wait.
Before changing the code, we should read the manual:
| list-reply (default: L)
|
| Reply to the current or tagged message(s) by extracting any
| addresses which match the regular expressions given by the
| lists or subscribe commands, but also honor any Mail-Followup-
| To header(s) if the $honor_followup_to configuration variable
| is set. Using this when replying to messages posted to
| mailing lists helps avoid duplicate copies being sent to the
| author of the message you are replying to.
"honor any Mail-Followup-To headers" - What does it mean?
No matter whether MFT's addresses are lists or not,
a <list-reply> should be sent to all addresses in MFT?
Wow, that's very easy to code! ;)
P.S.
Modify mutt_fetch_recips() in send.c if you're going to fix it.
--
tamo