That worked! Thanks a lot for the help.
Tokio Kikuchi uttered:
> Hi,
>
> I think this patch will work.
>
>https://sourceforge.net/tracker/index.php?func=detail&aid=685788&group_id=103&atid=300103
>
> Cc-ing mailman-developers.
>
> Erik S.E. Walu
Since our upgrade to MM2.1, the Cc: field of messages sent to the list,
if it has addresses in it, is altered to multiple cc: headers. For
example, Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] when expanded and
resent by mailman becomes, on seperate lines:
cc: [EMAIL PROTECTED]
cc:
We've recently upgraded to Mailman2.1 and have noticed that Mailman is
now changing our Cc: headers and doing some RFC 2822 non-compliant
business with them. The original header might be:
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
when the message comes through to the list, the h
Is there a way to limit the max limit on message size globally for all
lists? Were concerned about letting customers manage this veriable as it
can have extremely detrimentel effects when your installation becomes
quite large. Please respond to me personally as well as the list.
Thanks.
--
Erik
Is there a workaround for getting mailman to honor the case of a
listname upon creation, we've noticed that it always capitalizes the
first letter of a listname at creation time. Suggestions and comments
welcome.
thanks
-esew
--
Erik Walum <[EMAIL PROTECTED]>
Internet Systems Engineer
Verio I
We've been anticipating the fabled virtual domain support in mailman 2.0
for a long time, but alas, the only documentation on this appears to be
a hack (ref: README.EXIM). IS there any further documentation on mailman
2.0's added support for virtualdomains, or was it simply a rewrite of
the cronta
