From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] REJECT: Too many recipients to the message
Date: Mon, 01 Jun 2009 17:27:14 -0500 [thread overview]
Message-ID: <4A2455C2.1020306@freescale.com> (raw)
In-Reply-To: <20090601220021.3F722832E416@gemini.denx.de>
Wolfgang Denk wrote:
> Dear T Ziomek,
>
> In message <20090601210846.GJ8553@email.mot.com> you wrote:
>>>>>> How about reconfiguring the list software instead?
>>>>> I see no reason for that yet.
>> I see no reason, at least none articulated as of yet, for the current
>> configuration.
>
> The current configurations is (1) the default one, and (2) pretty
> useful to detect list abuse that has not been cought yet by other
> means.
I don't understand what CC lists have to do with abuse of the mailing
list -- any mail generated by a CC is done at the sender's mail server.
CC lists do not cause additional mail to be sent by lists.denx.de.
At worst, long-running threads can accumulate CCs that are no longer
relevant to where the thread has gone (and I'm fine with encouraging
those to be trimmed), but that's got nothing to do with the mailing list
itself. The only thing that having the list reject such mails will
accomplish is that people *not* on the CC list won't see the mail, which
is sort of the opposite of the intended effect.
>>> We neever before had any such problems. Currently these are caused
>>> because some messages have 5 (or more) samsung.com addresses listed
>>> on Cc:; for example, "[PATCH] The omap3 L2 cache enable/disable
>>> function to omap3 dependent code" has 6 such addresses on Cc:
>> And what problem does that cause?
>
> Such messages need manual moderation which (1) delays the messages and
> (2) causes additional work to the list moderator (me).
That problem is not caused by the CC lists, but rather the configuration
of the list server. What problem do the CC lists cause *by themselves*?
>>> In this specific case, a
>>> company-internal distribution list would probably be more
>>> appropriate.
>> I don't understand what you envision here, or what it would accomplish.
>
> They could Cc: u-boot-addicts at foo.com (i. e. just one address) and
> distribute this internally to anybody who might be interested.
What would that accomplish (keeping in mind that the CCs are often not
for expanding the distribution list but calling specific people's
attention to the mail)? If those "addicts" were uniformly interested in
all u-boot mail, why wouldn't they just subscribe to the list? If
they're only interested in some threads, what makes you think it will be
the same set of "5 (or more)" people each time?
How should I know that someone wants to be CCed by some address other
than what they post with?
-Scott
next prev parent reply other threads:[~2009-06-01 22:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 17:58 [U-Boot] REJECT: Too many recipients to the message Wolfgang Denk
2009-06-01 18:39 ` Scott Wood
2009-06-01 18:47 ` Jerry Van Baren
2009-06-01 18:50 ` Scott Wood
2009-06-01 20:01 ` Wolfgang Denk
2009-06-01 20:00 ` Wolfgang Denk
2009-06-01 20:32 ` T Ziomek
2009-06-01 20:51 ` Wolfgang Denk
2009-06-01 21:08 ` T Ziomek
2009-06-01 22:00 ` Wolfgang Denk
2009-06-01 22:27 ` Scott Wood [this message]
2009-06-02 0:09 ` T Ziomek
2009-06-02 6:53 ` Stefan Roese
-- strict thread matches above, loose matches on Subject: below --
2009-06-02 2:52 HeungJun, Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A2455C2.1020306@freescale.com \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox