Hi,
It seems that eas-dev is stripping people on cc in certain cases. When I receive copies of my own replies the topic is prefixed with "[Eas-dev]" and the cc list only contains eas-dev itself.
Is that a deliberate choice? IMHO it would be better to keep the cc list in case you want to reply to your own messages.
It also looks like people are removed from to/cc when others reply to messages received through the list (not in to/cc).
Thanks, Morten
Hi Morten,
On 10.04.15 14:55 +0100, Morten Rasmussen wrote:
It seems that eas-dev is stripping people on cc in certain cases. When I receive copies of my own replies the topic is prefixed with "[Eas-dev]" and the cc list only contains eas-dev itself.
Could you, please, be more specific about those cases? AFAIK, the only case when mailman is doing that is when a person, who is subscribed to a ML, was also CCd.
Is that a deliberate choice? IMHO it would be better to keep the cc list in case you want to reply to your own messages.
It also looks like people are removed from to/cc when others reply to messages received through the list (not in to/cc).
That also might be caused by MUAs. Is that happening for different people?
-- Best Regards, Serge Broslavsky serge.broslavsky@linaro.org
Core Development Project Manager, Linaro M: +37129426328 IRC: ototo Skype: serge.broslavsky http://linaro.org | Open source software for ARM SoCs
On 10 April 2015 at 15:36, Serge Broslavsky serge.broslavsky@linaro.org wrote:
Could you, please, be more specific about those cases? AFAIK, the only case when mailman is doing that is when a person, who is subscribed to a ML, was also CCd.
Which is a per user option.
On Fri, Apr 10, 2015 at 03:48:12PM +0100, Mark Brown wrote:
On 10 April 2015 at 15:36, Serge Broslavsky <serge.broslavsky@linaro.orgmailto:serge.broslavsky@linaro.org> wrote:
Could you, please, be more specific about those cases? AFAIK, the only case when mailman is doing that is when a person, who is subscribed to a ML, was also CCd.
Which is a per user option.
Yes, I saw that one.
One example is the recent thread started by Mike "sched-freq dependencies". The first mail was sent to Juri, myself, and eas-dev. I replied with Juri on cc, but the copy sent by mailman tagged with [Eas-dev] doesn't have Juri on cc.
I use that same setup as I do for LKML.
Thanks, Morten
On 10.04.15 15:58 +0100, Morten Rasmussen wrote:
On Fri, Apr 10, 2015 at 03:48:12PM +0100, Mark Brown wrote:
On 10 April 2015 at 15:36, Serge Broslavsky <serge.broslavsky@linaro.orgmailto:serge.broslavsky@linaro.org> wrote:
Could you, please, be more specific about those cases? AFAIK, the only case when mailman is doing that is when a person, who is subscribed to a ML, was also CCd.
Which is a per user option.
Yes, I saw that one.
One example is the recent thread started by Mike "sched-freq dependencies". The first mail was sent to Juri, myself, and eas-dev. I replied with Juri on cc, but the copy sent by mailman tagged with [Eas-dev] doesn't have Juri on cc.
I use that same setup as I do for LKML.
This might help understanding what is happening (that option is indeed set for Juri):
"""...this behavior is intentional by design. Cc: recipients who are list members with their 'avoid duplicates' option set are removed from the Cc: list to keep that list from growing excessively in long threads with many 'reply-all' replies."""
https://bugs.launchpad.net/mailman/+bug/1216960
-- Best Regards, Serge Broslavsky serge.broslavsky@linaro.org
Core Development Project Manager, Linaro M: +37129426328 IRC: ototo Skype: serge.broslavsky http://linaro.org | Open source software for ARM SoCs
On Fri, Apr 10, 2015 at 04:18:21PM +0100, Serge Broslavsky wrote:
On 10.04.15 15:58 +0100, Morten Rasmussen wrote:
On Fri, Apr 10, 2015 at 03:48:12PM +0100, Mark Brown wrote:
On 10 April 2015 at 15:36, Serge Broslavsky <serge.broslavsky@linaro.orgmailto:serge.broslavsky@linaro.org> wrote:
Could you, please, be more specific about those cases? AFAIK, the only case when mailman is doing that is when a person, who is subscribed to a ML, was also CCd.
Which is a per user option.
Yes, I saw that one.
One example is the recent thread started by Mike "sched-freq dependencies". The first mail was sent to Juri, myself, and eas-dev. I replied with Juri on cc, but the copy sent by mailman tagged with [Eas-dev] doesn't have Juri on cc.
I use that same setup as I do for LKML.
This might help understanding what is happening (that option is indeed set for Juri):
"""...this behavior is intentional by design. Cc: recipients who are list members with their 'avoid duplicates' option set are removed from the Cc: list to keep that list from growing excessively in long threads with many 'reply-all' replies.""" https://bugs.launchpad.net/mailman/+bug/1216960
So it is deliberate :-)
And the option is set by default.
However, I don't get why whether you want to receive a duplicate copy has to be linked with the choice of whether you get stripped from the cc list on mails sent by everybody else to the mailing list. So if you reply in a thread where you where not originally in to/cc you will never know who was originally on cc it seems.
The growing cc-list argument isn't going to be a problem for us any time soon I think :-)
Anyway, I was just wondering why it didn't work like LKML.
Thanks, Morten
-
Mark Brown -
Morten Rasmussen -
Serge Broslavsky