> "TN" == Tom Neff <[EMAIL PROTECTED]> writes:
TN> Look, I completely agree with you about this major gotcha with
TN> Mailman, that its otherwise terrifically brilliant coders
TN> happen to have some ideological hobbyhorses they ride - there
TN> is no use arguing with them ab
Sorry, I missed this when it first appeared.
John W Baxter <[EMAIL PROTECTED]> wrote:
> One can patch the installation, if one manages the Mailman installation
> and has or develops the skills.
>
> One can't, if one uses the Mailman installation managed as a service by
> someone else. Suitable b
At 20:51 -0700 4/8/2002, Chuq Von Rospach wrote:
>On 4/8/02 6:19 PM, "John W Baxter" <[EMAIL PROTECTED]> wrote:
>
>
>> One can't, if one uses the Mailman installation managed as a service by
>> someone else. Suitable bribes to that person might help, though. I think
>> I remember the OP saying t
On 4/8/02 6:19 PM, "John W Baxter" <[EMAIL PROTECTED]> wrote:
> One can't, if one uses the Mailman installation managed as a service by
> someone else. Suitable bribes to that person might help, though. I think
> I remember the OP saying that he was in the using-a-service camp.
Of course, may
At 18:12 -0400 4/8/2002, Tom Neff wrote:
>The good news is it's open source, so you can patch your installation as
>needed. I was concerned to read you were unable to patch out the List-*:
>behavior. What happened when you tried?
One can patch the installation, if one manages the Mailman instal
David <[EMAIL PROTECTED]> wrote:
> Actually itis the only product that my host offers for mailing lists.
> It is a damn good program in all respects other than the programmers
> decision to force this on us and wrongfully cite it as following the
> standards. The standards make it optional not fo
