Mailman 3 April 1999 - Mailman-Users

Question about the template directory
by Soren Dayton 08 Apr '99

08 Apr '99

I see that Util.maketext() uses the template directory for things, but it seems to me that a much nicer idea might be to have a template path, using the first template in the path. This could handle upgrades very robustly, and allow an obvious kind of list administrator modification. Would this be a desirable feature? (I would submit code, but I don't actually know python... Sorry) Thanks Soren

2 1

Hypermail integration
by Tzeng, Nigel 07 Apr '99

07 Apr '99

We're testing mailman as our list software and so far we like it. However, we'd like to be able to search our archives for info...something that Pipermail doesn't offer. I've finished compiling Hypermail and I'm wondering if anyone has any pointers in replacing pipermail with Hypermail. Thanks! Nigel Tzeng Century Computing

2 1

Problems (still) MM-1.0b11 & Python 1.5.2b2 on BSD3.1
by George M. Ellenburg (Mailing List Account) 07 Apr '99

07 Apr '99

Fetched Python 1.5.2b2 from Python.org, install and tests went without a hitch. Sucked down MM 1.0b11 this morning as well. As user 'mailman' I ran `./configure --prefix=/u1/mailman --with-mail-gid=32766 --with-cgi-gid=32766` (32766 is user nogroup) followed next by `make install`. No problems here. In fact, I'm able to access the admin cgis. But, as before, if I try to rin /bin/newlist I get the following error: sundial:~/bin $ ./newlist Enter the name of the list: test Enter the email of the person running the list: gme(a)caffeine.sundial.net Initial test password: XxXxXxXx Traceback (innermost last): File "./newlist", line 141, in ? raise SystemExit(main(sys.argv)) File "./newlist", line 91, in main newlist.Create(list_name, owner_mail, pw) File "/u1/mailman/Mailman/MailList.py", line 718, in Create self.Lock() File "/u1/mailman/Mailman/MailList.py", line 1267, in Lock self._lock_file.lock('w|', 1) File "/usr/local/lib/python1.5/posixfile.py", line 190, in lock flock = fcntl.fcntl(self._file_.fileno(), cmd, flock) IOError: [Errno 22] Invalid argument sundial:~/bin $ Anyone have any clues or ideas? Many thanks. ----- George M. Ellenburg Tel: +1 407 438 6710 Systems Administrator, Fax: +1 407 438 6714 Sundial Internet Services, WWW: www.sundial.net a Division of Micro Mainframe Technology, Inc. "If users are made to understand that the Systems Administrator's job is to make computers run, and not to make them happy, they can, in fact, be made happy most of the time. If users are allowed to believe that the Systems Administrator's job is to make them happy, they can, in fact, never be made happy." -- Paul Evans (as quoted by Barb Dijker in "Managing Support Staff", LISA '97)

3 4

A couple of questions
by Richard Ellerbrock 07 Apr '99

07 Apr '99

Just a compliment to start off with. I think that mailman is the best thing since sliced bread! Now for the questions: Under the list admin web page, membership management page, mass subscribe section how does a person change the "Send Welcome message to this batch?" to default to no. If I change the DEFAULT_MAX_MESSAGE_SIZE = 2048 in the mm_cfg.py file, the web page only displays the first three characters (204). Bug! Under the list admin web page, Archival Options, how do I change Archive Options to default to No? If I change ARCHIVE_TO_MBOX = -1 in mm_cfg.py, strange things happen. The web page still says Yes and I can never get archiving turned on again. I now have to resort to manually changing this to No for each list that I create. Bummer! I would really like to see a generic interface for user subscriptions like Listserv has. All admin commands can be sent to an address like listserv(a)myhost.com with subscribe, view list etc. commands. Anybody willing to do this? It should be pretty simple writing a wrapper around mailman, but I do not know python and I do not have the time to figure it out. Richard Ellerbrock richarde(a)eskom.co.za

1 0

"No module named pythonlib"
by Tor Houghton 07 Apr '99

07 Apr '99

The Cron daemon reports the following for the mailman user: Traceback (innermost last): File "/home/mailman/cron/gate_news", line 27, in ? from Mailman import MailList File "/home/mailman/Mailman/MailList.py", line 33, in ? File "/home/mailman/Mailman/ListAdmin.py", line 28, in ? File "/home/mailman/Mailman/Message.py", line 31, in ? ImportError: No module named pythonlib (Had I noticed this earlier, I would have included it in my previous mail.) Cheerio, Tor Houghton.

2 2

RE: [Mailman-Users] Approved posters denied in 1.0b11
by Grace, Terry 07 Apr '99

07 Apr '99

I had the same problem. Barry suggested I add USE_ENVELOPE_SENDER = 0 to mm_cfg.py and it worked like a charm. -----Original Message----- From: mailman-users-admin(a)python.org [mailto:mailman-users-admin@python.org]On Behalf Of J.D. Falk Sent: Tuesday, April 06, 1999 1:13 PM To: mailman-users(a)python.org Subject: [Mailman-Users] Approved posters denied in 1.0b11 Just upgraded to 1.0b11 'cause I saw this problem in 1.0b10 and thought maybe 11 would fix it...people who're supposed to be allowed to post to lists (whether it's subscribers only or a subset thereof) are being blocked, as if the list now requires administrative approval for all messages. I'm guessing that this is something I missed in the spate of mail about b10 over the past few weeks.... ---------========== J.D. Falk <jdfalk(a)cybernothing.org> =========--------- | "Confusion is mightier than the sword." | | - Abbie Hoffman | ----========== http://www.cybernothing.org/jdfalk/home.html ==========---- ------------------------------------------------------ Mailman-Users maillist - Mailman-Users(a)python.org http://www.python.org/mailman/listinfo/mailman-users

3 2

Approved posters denied in 1.0b11
by J.D. Falk 06 Apr '99

06 Apr '99

Just upgraded to 1.0b11 'cause I saw this problem in 1.0b10 and thought maybe 11 would fix it...people who're supposed to be allowed to post to lists (whether it's subscribers only or a subset thereof) are being blocked, as if the list now requires administrative approval for all messages. I'm guessing that this is something I missed in the spate of mail about b10 over the past few weeks.... ---------========== J.D. Falk <jdfalk(a)cybernothing.org> =========--------- | "Confusion is mightier than the sword." | | - Abbie Hoffman | ----========== http://www.cybernothing.org/jdfalk/home.html ==========----

2 1

RE: Mailman-Users digest, Vol 1 #169 - 13 msgs
by Ken Manheimer 06 Apr '99

06 Apr '99

On monday, Ray Everett-Church <ray(a)everett.org> wrote: > I'm curious... are the anti-spam features (such as restricted posting) > for this list turned off? I've not had a spammer attack any of my lists > yet <wood knock="on">... If they aren't, could I suggest they be > turned on so we can see if the Kuppler crooks make it through again? As barry indicated, there's a lot of spam you haven't seen, because it was caught. Most is caught by a rule which prohibits holds postings which do not explicitly mention the name of the list among the destination addresses for the message. A smaller portion after that catches postings which do explicitly mention the list name, among too numerous other destinations. The kuppler garbage made it through because it used a labor-intensive sending process which explicitly targets every destination individually - you may have noticed "<mailman-users(a)python.org>" as the sole destination on the offending message. It may be that such efforts will have "Re: Ad:" or some such on them, but we can't tell on just one occurrance. When/if we see one or two more, we'll be able to infer a pattern, and then tailor one of the pinpoint filters (per-address prohibition, or subject-line match as you suggest, or whatever...) The not-so-nice thing is that restricting postings to list-members-only is a rather extreme measure, because it can entail some maintenance overhead. Ie, it restricts the list members to posting from one sending address, and even there the smart-matching is tricky, and can require maintenance of the posters option. The nice thing is, the explicit-destination constraint catches a _lot_ of the garbage, and we can handle the smallish remainder in a proportional way. It seems (he says, with some satisfaction) to be working.-) (I say this quietly because i don't want to "declare war on spammers" - declaring war is like asking for people to hit you, which doesn't seem like a smart thing to do.) ken klm(a)digicool.com

1 0

exim configure
by nbecker＠fred.net 06 Apr '99

06 Apr '99

Here is all I needed to do to use mailman with exim: After system_aliases: Add mailman_aliases: driver = aliasfile file = /etc/aliases.mailman search_type = lsearch user = mailman initgroups errors_to = mailman-owner This assumes you want the alias pipes run as user "mailman". You can cut and paste verbatim the aliases spit out by "newlist" into "/etc/aliases.mailman".

1 0

kudos and question
by nbecker＠fred.net 06 Apr '99

06 Apr '99

First let me say mailman is entirely too cool! Next a question. I have setup a list here. Attempting to followup to a message I posted to my list (using gnus) it goes to <list>@hns.com. Unfortunately I don't control hns.com, only nbeckerpc.hns.com. Where can I configure this? (My exim mailer is configured to accept hns.com as well as nbeckerpc.hns.com - but if someone else not using my machine tries to reply it will just bounce)

1 0