Mailman 3 October 1998 - Mailman-Developers

SMTPHOST can come in very handy
by Scott Oct. 31, 1998

Oct. 31, 1998

I've got about 30 sizable lists running on mailman, all of which are majordomo converts <grin>. Though most of the listowners miss the old majordomo feature of notifying the administrator when subscribes or unsubscribes occur, they like alot of the other features alot, like automatic bounce processing, web archiving, etc. Some of the features they dont even know they like, like the fact that the site admin can define SMTPHOST. little story, that might come in handy for others one day. … [View More]

1 0

Re: [Mailman-Developers] observation from a bystander :) [long and boring]
by Tomas Fasth Oct. 30, 1998

Oct. 30, 1998

Peter, as a bystander myself I can certainly understand your frustration and have sometimes found myself in similar situations. But I also think you might have to lower your expectations on other people's urge to please you. Here's some basic guidelines when dealing with free software: * Don't expect someone else to do more than yourself. * Improvements are done through working code, not fancy suggestions. * Be humble to the fact that active developers are sacrificing their free time. * Your … [View More]

3 2

call_scrips: wrong dir..?
by Peter Gervai Oct. 29, 1998

Oct. 29, 1998

Hello, I'm fighting (with no luck, let me comment) with Oct 29 01:36:05 1998 admin: [----- Traceback ------] admin: Traceback (innermost last): admin: File "/var/lib/mailman/scripts/driver", line 97, in run_main admin: main() admin: File "../Mailman/Cgi/subscribe.py", line 96, in main admin: call_script('options', [list._internal_name, member]) admin: File "../Mailman/Cgi/subscribe.py", line 66, in call_script admin: list.Unlock() admin: AttributeError: Unlock and reached … [View More]

1 0

Re: [Mailman-Users] Bug Message
by Ken Manheimer Oct. 29, 1998

Oct. 29, 1998

On Wed, 28 Oct 1998, Alvin Gunkel wrote: > I have installed mailman and Python 1.5.1 per instructions. When > trying to access the subscribe program I get the following: > > We're sorry, we hit a bug! > [...] > Traceback (innermost last): > File "/u1/mailman/scripts/driver", line 97, in run_main > main() > File "../Mailman/Cgi/subscribe.py", line 30, in main > path = os.environ['PATH_INFO'] > File "/usr/local/lib/python1.5/UserDict.py", line 12,… [View More]

2 1

New release of my patches
by Balazs Nagy Oct. 28, 1998

Oct. 28, 1998

Hiyas, It seems I have to repatch new versions day-to-day waiting for someone who apply 'em. I would be glad if someone applies my patches - at least cmdhandler and cgiext patches. FYI cmdhandler enables administrator commands by email and cgiext handles the extensions of CGI programs (as you can read it in README but doesn't work). The third one (MTA patch) is experimental, it works for me - at home, but I didn't try it out at kva.hu. Please apply'em. -- Linux Supporting Center -- Red … [View More]

3 3

observation from a bystander :) [long and boring]
by Peter Gervai Oct. 28, 1998

Oct. 28, 1998

Hello, As half of this day was spent exclusively with mailman I thought I finally enter this list and submit some comments. I am really disappointed that nobody reads the mailman-user list who is able to answer so complex questions that "what this and that error means". (The volume isn't THAT high there.) Since I do not know Python, don't work with it, I had almost no chance to find bugs. Since nobody helped (as later turned out: very basic!) my problems I had to waste almost a day learning … [View More]Python basics, realising that I have to change code, figure out syntax, etc etc You know the story. Then inserting debug points into the program (it's hard to debug when you don't know how, remember?), and to find the problems (most of them), and realizing that it was almost the same as the one was mentioned as 'duplicate mails' at the beginning this month (apart from lots of permission problems). This could be solved in 2 minutes by someone who at least had the idea what Python is... khm. Anyway, this got solved, so excuse me my rants. However my mail on mailman-user list contained maybe some hints or ideas would have been nice to be read by at least one developer to decide whether it worths mentioning... I still hope SOMEONE will take that 2 minutes. So I realized that Scott fixed that race problem around processQueue (see? I'm a mailman pro in less than 8 hours :-)), but I don't really see why anyone would use sticky (or any special) bits for locking. Why don't use lockfiles? A simple queue.LOCKED would do fine. And this reminds me to mention that I hope that other files are locked as well, including list and subscription databases. Locking is easy. And if anyone needs ideas I could advice to see Exim mailer's locking which is rock stable even when deliveries were aborted by system freeze... Worths an inspection, if anyone needs multiple-record-locking. Oh, and for those who won't read that mail of mine out there I mention that I asked about which files and directories should be writable by cgi uid, mailman uid or both. I welcome the idea of a script checking directory and file ownership, permissions (and setting them, actually). The whole problem of mine started as I want to use mailman with Exim, and more-or-less I solved the problem, and even put a little howto on users mailing list (though nobody seem to care). This means I don't use wrappers but I'm very picky about permissions and ownerships, and things tend to die horribly when I don't figure out which dir and file should be owned who and with what permissions (unless of course I let 0666 files and 0777 dirs all over the place - which I don't). Especially rude to create a mailman.root owned rw-rw-r-- file which needs to be modified/deleted by the cgi.cgi user. I loved the permissions of the logs or the lists directory, for example. :-) Oh, and why didn't I want to write the mail here? Because I ain't no developer (um, I wasn't so far), and because I don't know Python (didn't know so far). Um, that's all. Sorry if it was too long. And I even kept it short. :) bests, grin ps: constructive criticism welcome, and flames as well by PERSONAL email. I fear that the effect will be the same as on mailman-users: silence. [View Less]

1 0

confusing post requirements policy
by Scott Oct. 23, 1998

Oct. 23, 1998

Recently i added an option to mailman to make it so that the list of posters that are allowed to post sans approval would or would not include the list members automatically. I have several lists using this option, and just discovered that a good deal of confusion was created over the fact that there are 3 interrelated questions on the admin cgi (and corresponding variables) that could be summed up in 2: 1) variable member_posting_only. 2) variable posters 3) posters_includes_members … [View More]

2 3

Re: [Mailman-checkins] CVS: mailman/Mailman MailList.py
by Balazs Nagy Oct. 23, 1998

Oct. 23, 1998

On Tue, 20 Oct 1998, Ken Manheimer wrote: > First of all, yesterday i was confused about what the "norcv" option > is - it sounds too much like what the "nomail" option is for, and i > forgot about the "receive one's own postings" option - had to scramble > around to figure it out. I suggest something like "rcvmine" Maybe 'metoo' -- Linux Supporting Center -- Red Hat Qmail packages -- http://lsc.kva.hu PGP 0x1DE3631D / A8 B4 92 EE 1F 55 27 C8 86 64 9C 42 41 A4 BD B8

3 2

mm_cfg.py overwrite when upgrading intentional?
by Harald Meland Oct. 21, 1998

Oct. 21, 1998

>From Mailman/Makefile.in: 44 MODULES= *.py [...] 64 install: 65 for f in $(MODULES); \ 66 do \ 67 $(INSTALL) -m $(FILEMODE) $$f $(PACKAGEDIR); \ 68 done This means that Mailman/mm_cfg.py is copied over the existing mm_cfg.py when upgrading. I don't think this is intentional, as the next lines in Makefile.in are: 69 $(INSTALL) -m $(FILEMODE) mm_cfg.py $(PACKAGEDIR)/mm_cfg.py.dist 70 if … [View More]

1 0

Re: CVS: mailman/Mailman MailList.py Archiver.py
by Harald Meland Oct. 21, 1998

Oct. 21, 1998

[scott(a)chronis.pobox.com] > Update of /export/public/cvsroot/mailman/Mailman > In directory anthem:/tmp/cvs-serv5888/Mailman > > Modified Files: > MailList.py Archiver.py > Log Message: > code cleanup: > moved the archivery directory checking code to > Archiver.Archiver.CheckHTMLArchiveDir() and call that from > MailList.Save(). As I'm not very familiar with python yet (and thus probably shouldn't be running bleeding edge CVS versions of Mailman :), I'm not … [View More]

1 0