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.
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).
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.
Messages get delayed, and they exceed my patience quota ;-)
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@foo.com (i. e. just one address) and distribute this internally to anybody who might be interested.
Best regards,
Wolfgang Denk