Hi, * Derrick 'dman' Hudson [02-07-14 03:11:36 +0200] wrote:
> Problem : > Sometimes a message received via a mailing list, but doesn't > mention the list in any of the recipient headers. (eg a member > bounced an off-list reply back to the list) Mutt's list-reply > function doesn't recognize any lists in that case. These are BCCs to lists which is really bad. If someone BCCs a mail to a list he/she should write a few words why the original receipent doesn't need to know why it's going to a list, too. Anyway, how often does that happen and is it worth to spent time on working around this? > Solution (my idea) : > For MLMs that include a List-Post: header, I think it would be > useful if mutt would (or could) use that to derive the address of > the list. See Cedric's answer. There's an RfC specifying those headers and I've only seen Mailman adding them. It could be difficult to parse them. > I can think of several ways of handling this -- > 1) use List-Post: by default. Doesn't require setting 'lists'. > 2) use List-Post: if no 'lists'/'subscribe' addresses are found > using current methods > 3) use List-Post: in addition to current method > 4) a configuration option to choose from the above. In which form of reply do you want the address to be used? Normal reply, group reply or list reply? This is really important since I don't believe anybody does a BCC to a list without purpose. What do you do if the Reply-To: and Mail-Followup-To: headers don't mention the list, too? If the sender doesn't want answers to go to the list, too, a user may run into trouble by accidently sending a reply to the list. > Do people think this is a good idea? Generally, yes since there's an RfC for those headers. But on the other hand, there're already 5 headers it has to take care of with the different reply methods: From:, To:, Cc:, Reply-To: and Mail-Followup-To:. The current reply behaviour has to be adjusted by giving more details than your 3 methods, I think. > Can it be added to the wishlist? If you want to do, just use flea(1) to report a bug with a severity of 'whishlist'. bye, Rocco
