On Mon, 18 May 1998 17:09:48 -0700 Bill Houle
> At 04:00 PM 5/18/98 +0100, Richard Hopkins wrote:
> >MajorCool (version 1.3.0) seems to truncate long "restrict_post" values,
> >unexpectedly, when you use it to modify list configurations. (Only happens
> >if you actually modify restrict_post; no problems if you modify other
> >From a quick peek at the code, it looks to me like it should cater for
> >input of up to 128 characters, but it seems to truncate to something less
> >than 80 before writing out the config file. No warnings/errors are shown.
> Can you go back and do a bit more debugging for me/us? I understand what
> you are saying, except for one problem: MajorCool does not "write out" the
> config file -- that is handled by Majordomo. It still could be possible
> that MajorCool is handing a truncated version of the text to Majordomo, but
> it could be just as likely that you have found a problem with Majordomo
> itself rather than MajorCool...
Sorry for not making that clear, earlier....
I think the problem is with MajorCool truncating somewhere along the line,
as I don't get the problem when I use majordomo itself.
For example, here's a restrict_post I set up with majordomo (using
MajorCool to send me the config file, modifying the restrict_post value and
then submitting the new config to majordomo by mail)...
restrict_post = /users/majordomo/Lists/test-list cse-admin cse-cg cse-dsg cse-ig cse-mg cse-staff cse-syscomms
(the above is a single line. Mail readers may well wrap it.)
But here's what I get if I try to set the "long" restrict_post using
restrict_post = /users/majordomo/Lists/test-list cse-admin cse-cg cse-dsg cse-ig cse-mg c
(again, that's a single line)
Is there anything else you'd like me to check out, Bill?