Mailman 3 April 1998 - Mailman-Developers

Pre-release of new mailman version
by Ken Manheimer 10 Apr '98

10 Apr '98

I've packaged an a prerelease of my new version of mailman - the one currently running on python.org. I plan to do a real (beta) release by the end of the weekend, but would like to have people do some poking and prodding before then, to shake out any overt problems in my packaging methods... (Also, some people are doing their own work on particular pieces, and need to work w.r.t. the current version instead of the substantially different prior one.) Since there are some substantial changes, particularly in the way default site values are configured and in the maillist data structures, you should not overwrite anything you're using for production. (In particular, i haven't implemented the routine that migrates the datastructures from older list versions to the current one, so things *will* break) This relase is more for reference - yours and mine. Please let me know if you do play with it and have anything interesting to report. Thanks! ken manheimer klm(a)python.org

2 1

Re: [Mailman-developers] wrappers: legal_caller()
by John Viega 09 Apr '98

09 Apr '98

> On Thu, Apr 09, 1998 at 11:47:45AM -0400, Ken Manheimer wrote: > | On Thu, 9 Apr 1998, Scott wrote: > | > | > i have installed mailman as part of pilot project to test out new > | > mailing list managers for work. > | > > | > i had to change the ./mailman/mail/wrapper program to check for > | > multiple uids and gids to get the cron jobs to work properly (uid and > | > gid were that of mailman when sending out results). > | > > | > has this been incoporated into mailmanv1.0b1.2 yet? if not, here's a > | > patch to ./src/mail-wrapper.c (the same change can be applied to the > | > other legal_caller() functions in the wrappers): > | > | This sounds fine. Note that the next release will have a somewhat > | simpler wrapper situation - john has consolidated all the cgi wrappers > | into a single source file, so there now is a total of three wrappers - > | the generic cgi wrapper (which is parameterized to create an executable > | for each of the cgi scripts), the mail-wrapper, and the aliases wrapper. > > One more thing that may make the installation easier would be to have > a single header file that is #included in each c source file with > something like > > /* legal parent uid's of the wrapper ./mailman/mail/wrapper */ > const int LEGAL_MAIL_PUIDS[] = > { > 0, /* root */ > 1, /* bin */ > 537, /*mailman */ > -1, /* Sentinel, do not remove */ > } > > or if there's a worry of defining unused variables: > > #ifdef MAIL_WRAPPER > > [declaration] > > #endif > > along with a '#define MAIL_WRAPPER 1' in mail-wrapper.c > > this way, while whoever is installing the program, they would only > have to edit one file to play with the calling uid and gid. > > Scott Cotton > IC Group, Inc. > > > ------------------------------------------------------ > Mailman-developers maillist - Mailman-developers(a)python.org > http://www.python.org/mailman/listinfo/mailman-developers Actually, the ultimate goal is to have as much configuraiton as possible picked out automatically, and the rest of it maintained by a single file, or perhaps a web page. For example, most of the uids we could do a good job of guessing based on the passwd file, and then keep it open for people to change if they have special considerations. John

1 0

wrappers: legal_caller()
by Scott 09 Apr '98

09 Apr '98

i have installed mailman as part of pilot project to test out new mailing list managers for work. i had to change the ./mailman/mail/wrapper program to check for multiple uids and gids to get the cron jobs to work properly (uid and gid were that of mailman when sending out results). has this been incoporated into mailmanv1.0b1.2 yet? if not, here's a patch to ./src/mail-wrapper.c (the same change can be applied to the other legal_caller() functions in the wrappers): --- src/mail-wrapper.c Tue Jun 10 12:31:16 1997 +++ src/mail-wrappernew.c Thu Apr 9 03:41:32 1998 @@ -37,9 +37,18 @@ NULL /* Sentinal, don't remove */ }; -/* Should make these arrays too... */ -const int LEGAL_PARENT_UID = 8; /* mail's UID */ -const int LEGAL_PARENT_GID = 12; /* mail's GID */ + +const int LEGAL_PARENT_UIDS[] = { + 1, /* mail's uid */ + 537, /* mailman's uid */ + -1 /* Sentinel, don't remove */ +}; + +const int LEGAL_PARENT_GIDS[] = { + 1, /* mail's gid */ + 100, /* mailman's gid */ + -1 /* Sentinel, don't remove */ +}; /* @@ -77,20 +86,45 @@ ** is the parent process allowed to call us? */ int legal_caller() { - /* compare to our parent's uid */ - if(LEGAL_PARENT_UID != getuid()) + int uid, gid, isok, idi; + isok = 0; + idi = 0; + uid = getuid(); + while (LEGAL_PARENT_UIDS[idi] != -1) + { + if(LEGAL_PARENT_UIDS[idi] == uid) + { + isok = 1; + break; + } + idi++; + } + if ( isok == 0) { - fprintf(f,"GOT UID %d.\n", getuid()); - return 0; + fprintf(f,"GOT UID %d.\n", uid); + return 0; } - if(LEGAL_PARENT_GID != getgid()) + isok = 0; + idi = 0; + gid = getgid(); + while (LEGAL_PARENT_GIDS[idi] != -1) { - fprintf(f,"GOT GID %d.\n", getgid()); - return 0; + if(LEGAL_PARENT_GIDS[idi] == gid) + { + isok = 1; + break; + } + idi++; + } + if ( isok == 0) + { + fprintf(f,"GOT GID %d.\n", gid); + return 0; } return 1; } + int valid_command(char *command){ int i = 0; @@ -119,7 +153,7 @@ i = strlen(argv[1]) + strlen(COMMAND_LOCATION) + 2; command = (char *)malloc(sizeof(char) * i); sprintf(command, "%s/%s", COMMAND_LOCATION, argv[1]); - + fprintf(f, "command is %s\n", command); if(!valid_command(argv[1])){ fprintf(f,"Illegal command.\n"); } Scott Cotton IC Group, Inc

2 2

suggestion
by Scott 09 Apr '98

09 Apr '98

i would like to suggest two things about the confirmation step in subscriptions. first, that it be an option for email based subscriptions, and second, that just hitting reply and copying in the confirmation message (with or without regular email quotations) be made to work. if there's a consensus on this, i'd be willing to make the necessary changes. Scott Cotton IC Group, Inc.

2 1

BTW
by Scott 09 Apr '98

09 Apr '98

nice work on the upcoming release, if that is indeed what's running at python.org. is there any work in progress on a mail interface to the adminstrative functions? Scott Cotton IC Group, Inc.

2 1

Pipermail issue...
by Stu Ekins 08 Apr '98

08 Apr '98

Hi, Does anybody know of any issues with the pipermail module? It hasn't worked for me since I upped my python version to 1.5 (on Linux 2.x). I'm still learning the language and am not yet competent enough to debug it fully myself! Here's a traceback... Traceback (innermost last): File "./archive", line 31, in ? list.UpdateArchive() File "/home/mailman/mailman/modules/mm_archive.py", line 72, in UpdateArchive import pipermail File "/home/mailman/mailman/modules/pipermail.py", line 424, in ? words = string.split(datestr) TypeError: argument 1: expected read-only buffer, None found Cheers, Stu.

3 2