Dear Wolfgang & everyone,
It happened ”Too many recipients to the message”, and I'm very sorry that my messages's many CC cause this event.
Before that, I didn't find the recipients # limits on the u-boot mailinglist guidelines. So, I just send the messages like other my situation.
If It's hard to configure mailing list server, I think the warnning about“The limit of CC” is showed on the u-boot mailinglist guidlines or anywhere.
Thanks & Sorry.
Best Regards, Riverful
----- 원본 메시지 ----- 보낸 사람: T Ziomek ctz001@email.mot.com 보낸 날짜: 2009년 6월 2일 화요일 오전 9:09 받는 사람: Wolfgang Denk wd@denx.de 참조: Scott Wood scottwood@freescale.com; u-boot@lists.denx.de 제목: Re: [U-Boot] REJECT: Too many recipients to the message
On Tue, Jun 02, 2009 at 12:00:21AM +0200, 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,
Unless there's a good reason it's the default, I wouldn't defer to that in the presence of good arguments otherwise.
and (2) pretty useful to detect list abuse that has not been cought yet by other means.
What sort(s) of abuse has configuration this helped catch?
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).
But that's a problem caused by the list server's config, not inherently by the # of CCs.
I doubt that this is really necessary.
"Necessary" is in the eye of the beholder here. And IMHO the presump- tion should be that the sender of an email is addressing it properly. Absent either (a) clear, significant abuse of emails' recipients or (b) a measurable and significant impact on the list provider [1], let people CC who they consider appropriate and let the list server send emails to whomever it is asked to send emails to.
[1] E.g. exceeding bandwidth quotas, mail delivery being delayed for hours, etc.
I take this example back; as Scott reminds us the CCs don't affect the list server (except for a few more bytes in the headers of a message it relays). In which case I have even more trouble seeing the harm in re- moving the list server's [apparently arbitrary and unsubstantiated] CC limit. Or at least changing it to a much higher number.
Messages get delayed, and they exceed my patience quota ;-)
Again, not inherently because of having "too many" CCs.
Raise/remove the limit, and your immediate issue is resolved. What's not to like?
Tom