[Users] reply to list

[Ralf Mardorf]

On Wed, 21 Sep 2016 01:52:08 +0200, Michael Rasmussen wrote:
>On Wed, 21 Sep 2016 01:40:48 +0200
>Ralf Mardorf <silver.bullet at zoho.com> wrote:
>
>> On Wed, 21 Sep 2016 01:25:43 +0200, Michael Rasmussen wrote:  
>> >A special case is if the mail contains CC headers in which case
>> >these addresses remains as CC (all though very onusual for list
>> >replies).    
>> 
>> So at least invoking mailing list replies by "All" instead of "Reply"
>> doesn't offend RFC and could cause a different behaviour.
>> 
>> However, Claws not necessarily keeps Cc headers.
>>   
>I should have written 'CC might remain'. Corner cases cannot always
>with a 100% certainty be identified as list servers in which case
>behavior is undefined ;-)
>
>Eg. this mail you send to list: Message-ID:
><20160921005451.4e523c1a at utnubu>

Yes, this is the horror mail.

>Caused claws to have both TO and CC when hitting reply. 

Sometimes it's wanted to Cc, so it's good that Claws invokes mailing
list replies by "Reply" and not "All", because "All" ensures that
replies are send to "All", if explicitly is wanted, e.g. on developer
mailing lists. OTOH a lot of users expect that even a Reply-to header
is ignored, they often expect to automatically send replies only to the
mailing list, what ever headers are provided or _even are not provided_,
e.g. related to http://www.list.org/mailman-member/node21.html .

You quasi could say that there's a user-friendly approach that ignores
Reply-to, invokes  reply to list  by  reply to all  and perhaps even
detects the mailing list, if a list header is missing, the list only is
mentioned by To or Cc. And the other approach is user-centric, this
approach provided by Claws allows better communication with other
users, who don't need the quasi user-friendly approach, but the
features available by Claws' approach.

Regards,
Ralf