Mailman-Users March 1999

mailman-users@python.org

102 participants
175 discussions

Re: [Mailman-Users] Mailman 1.0b9, password requirement.

by Roger Pe?a Escobio

-----Original Message----- From: Clark Evans <clark.evans(a)manhattanproject.com> To: bruce(a)perens.com <bruce(a)perens.com> Cc: sbolduc(a)uni-global.com <sbolduc(a)uni-global.com>; mailman-users(a)python.org <mailman-users(a)python.org> Date: Wednesday, March 24, 1999 7:49 PM Subject: Re: [Mailman-Users] Mailman 1.0b9, password requirement. >bruce(a)perens.com wrote: >> Rather than remove it, provide a check box to enable/disable it per list >> in the admin forms, or per user in the user's options. Then everybody will >> be happy. > >Great. > i think that the passwd option are very important when you set your user/subscriber option, if you dont have a passwd anybody can change your option :-( . i am sure that noone want this >> I won't give up subscription confirmation for anything, though. Too many times >> my lists have been used to maliciously mail-bomb someone. > >Now, confirmation I completely agree with. > me too Thanks

22 years, 9 months

Re: [Mailman-Users] Mailman questions (moderation capabilities, mostly)

by Greg Stein

RDB wrote: > > Thank you so much for your helpful answers. I have two short follow-up > questions: > > At 02:29 PM 3/30/99 -0800, you wrote: > > >MailMan has a "preapproved" list, but you need to add names to it > >manually. > > How could this be done? Could it be done through e-mail messages sent by > the moderators, or would they have to log into the server and edit the file > with PICO? The list is adjusted via the administrative web interface. You never need people to log into your machine simply to admin a list. The server admin needs to log in to create new lists and configure the MTA, but once a list is built... it's all web. This does imply that your moderators would have the ability to reconfigure the list parameters, so there is a bit more consideration than simply "are they prudent enough to moderate message content". Usually not a problem, IMO, because if they are moderating, then they're probably quite responabile and dedicated to a successful mailing list. > Also, I have a question about how moderation is done via the web-based > interface... Specifically, can the web interface that the moderators use > be shielded from the general public, so people who send messages to the > list can't have their messages viewed by anyone looking at the moderator's > page? The moderators (list admins) require a special password to get to the admin interface. So yes... it is shielded from the public. Cheers, -g -- Greg Stein, http://www.lyra.org/

22 years, 9 months

"No module named pythonlib"

by Tor Houghton

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.

22 years, 9 months

changing defaults

by Alan Neiman

I have found the "defaults.py" and the "mm_cfg.py" files, and I've been able to change almost all the defaults we want to. I do have a problem with the archives. We would like it turned off, and can't get that part working. I have added/changed the following line in both files, but the lists are still being created with archives turned on. ARCHIVE_TO_MBOX = -1 Any idea? thanks alan

22 years, 10 months

Re: [Mailman-Users] Mailman questions (moderation capabilities, m ostly)

by Ken Manheimer

Greg Stein was on the mark on most of the items, but i think he may have been mistaken on one of them. He wrote: > RDB wrote: > > 8. It would be great if the list software didn't fail to recognize a user > > just because the machine name directly following the @ in their e-mail > > address was added, deleted, or changed. Does MailMan handle this gracefully? > > I don't think it handles this. If i understand the question, i think it does. Mailman does something it calls "smart matching" for addresses comparisons when checking for membership and metoo matches, etc. This involves accepting as matches addresses that agree in the account name and all but the most qualified component of the host name part - the "machine name directly following the @". Actually, if i recall correctly, the rules are a bit more elaborate than that, but not much... Ken Manheimer klm(a)digicool.com

22 years, 10 months

Re: [Mailman-Users] changing defaults

by Alan Neiman

I understand that. The other 10 changes I made work, it's just this one that doesn't. Alan > Date: Wed, 31 Mar 1999 13:39:08 -0800 > From: Greg Stein <gstein(a)lyra.org> > MIME-Version: 1.0 > To: Alan Neiman <alann(a)ihs.com> > CC: mailman-users(a)python.org > Subject: Re: [Mailman-Users] changing defaults > Content-Transfer-Encoding: 7bit > > Alan Neiman wrote: > > > > I have found the "defaults.py" and the "mm_cfg.py" files, and I've been able to > > change almost all the defaults we want to. I do have a problem with the > > archives. We would like it turned off, and can't get that part working. I have > > added/changed the following line in both files, but the lists are still being > > created with archives turned on. > > the defaults are used at list creation time to populate the new lists' > configuration. The system doesn't defer back to the original defaults, > so you'll need to adjust each of your current lists to turn off > archiving. > > Cheers, > -g > > -- > Greg Stein, http://www.lyra.org/ Alan Neiman alan.neiman(a)ihs.com Unix System Administrator Information Handling Services -------------------------------------------------------------- ** 1997 & 1998 World Champions ** 17 & 2 -- Simply The Best -- The Broncos -- The Denver Broncos ** 1997 & 1998 World Champions ** --------------------------------------------------------------

22 years, 10 months

List config.db

by B. Friday

Got a question/bug report I don't know if this has been previously posted, but looking through my files for my mailing lists, I've noticed that each users password is located in the config.db file in plain text. While this isn't a termendous problem right now for me, I can see where this would be a problem for others. Is this on the list of things to do/change? Sincerly Brian Friday Systems Administrator La Sierra University Riverside, CA 92515 (909) 785-2554 x2

22 years, 10 months

Re: [Mailman-Users] Just installed 1.0b10 and have problem with call to non-function

by Rupa Schomaker (list)

"Rupa Schomaker (list)" <rupa-list(a)rupa.com> writes: > 1) I had to rename $prefix/scripts/dumb_deliver to > $prefix/scripts/deliver -- is this ok? Should I have been doing > something else? I use postfix as a mailer, but it provides a > sendmail compatible interface. But even that should matter, since > mailman uses smtp. This was obviously wrong. (and the root for some of my other problems). I've found the reason why I didn't have deliver. The first thing I do when getting sources is import the sources into CVS. Turns out that mail/.cvsignore has an entry for "deliver" which means that deliver will never be imported to CVS. I assume this was NOT intended. I've added deliver to my own CVS tree and hopefully won't continue having problems, but someone should change the distributed .cvsignore files... -- Rupa (rupa(a)rupa.com for normal email) Please don't email duplicate replies.

22 years, 10 months

Problems accessing /admin on the web interface

by Thomas Niedermeier

Hi everybody, I installed mailman a few days ago and got everything working all right, except for the access to the <hostname>/admin/<list> web-interface. If I append an '/' to the end of the url, I can access the first admin page *only*, others don't work and subpages won't either. I get back to the login screen and then back to the first admin page. BTW: the script appends another /mailman/admin/<list> to my url, and more often than not I end with an URL like <hostname>/mailman/admin/<list>/mailman/admin/<list> and the page stating that the list "mailman" is unknown.... Plus: the admin page doesn't accept any changes I enter and submit. Is this a known bug or are there any known workarounds? Thanks, Thomas

22 years, 10 months

Re: [Mailman-Users] Just installed 1.0b10 and have problem with call to non-function

by Rupa Schomaker (list)

"Rupa Schomaker (list)" <rupa-list(a)rupa.com> writes: > I'm not very familiar with python, so I'm not sure if I have enough > info here, but... I just installed mailman (attempting to move from > SmartList) and from what I've seen it is quite impresive. However, I > see the following error when subscribing or unsubscribing (though not > 100% consistant). Ok, I figured out the problem with this one. I ignored the advice in INSTALL and did the "make install" step as root. It was a permission problem and has been fixed. I think I'd still have the problem if one of the other modules attempted to log but if we never ask to log python doesn't complain about missing the LogMsg function. Now on to other things. 1) I had to rename $prefix/scripts/dumb_deliver to $prefix/scripts/deliver -- is this ok? Should I have been doing something else? I use postfix as a mailer, but it provides a sendmail compatible interface. But even that should matter, since mailman uses smtp. 2) If I've turned off montly reminders about passwords, the welcome message still says they'll go out. I assume this is a "its still beta, don't worry about it" problem, but maybe not... 3) The big one, moderation. (and the whole reason I'm switching from SmartList to Mailman. I setup the list to send immediate notices when new requests come in. I also said yes to whether to send mail to the poster if the posting is held for approval. When I send an email to the list, the email is put into the list's database and I can (from the web) administratively approve/reject the submission. However, neither the person submitting the message nor the admin get any email notification. If I manually run checkdbs (like it is in the cron) I don't receive an email. Manually running I notice that something *is* sent to the -admin address of the list. [mailman@gw cron]$ /usr/bin/python /home/mailman/cron/checkdbs -v test 3 test-admin(a)rupa.com But nothing bounces back around for me. If I add my email address to the test-admin alias I get a copy. So it looks like wrapper mailowner test doesn't forward the email to myself. <ponder> actually, Aha, I think I know what this one is. Postfix uses a header to look for mail loops. If mailman doesn't strip this header (Delivered-To:) then when it tries to deliver to itself again postfix treats it as a duplicate. Is there a way to tell mailman to strip a header before forwarding the message to itself (or outside)? 4) Related to moderation. How do I go about editing a message? I want to reformat and/or add comments to messages I approve. With smartlist, I make the changes to the message and then resend in the message with the Approved: header. How would I do the equivalent with Mailman? I guess thats it, more to come in the future, I'm sure. -- Rupa (rupa(a)rupa.com for normal email) Please don't email duplicate replies.

22 years, 10 months

Jump to page: