Mailman 3 May 1999 - Mailman-Users

stalled / locks?
by Ricardo Kustner 24 May '99

24 May '99

Hi, When I approve a post in the admindb interface (mailman rc1), the connection "stalls" for several seconds after the new page has been brought up... the weird thing is that the full html output has been displayed on the browser, but apperantly, the http connection isn't closed immediately after this... could this be a lock-file problem? I know it doesnt really look like a huge problem, but since i'm running mailman our poor little p100/32mb server is barfing on *huge* loads sometimes, making it almost impossible to telnet and reset the server ... this often happens shortly after a moderator has approved several posts through the admin interface. Ricardo.

3 4

[Patch itself]
by Bernhard Reiter 22 May '99

22 May '99

Of course I forgot to attach the patch, to the last mail. Sorry. Bernhard

3 2

Re: [Mailman-Developers] found a bug? "ValueError: bad marshal data"
by Harald Meland 22 May '99

22 May '99

[Ricardo - Miss Janet. Fanclub] > Hi, > > like i mentioned earlier, when i approve a post with admindb, the webbrowser > stalls for several seconds before closing the connection... well i just found > out that it generates an error in my apache logs (See below) > is this a bug? or does this mean one of the databases is corrupted? Looks like one of your pipermail archive databases (located under ~mailman/archive/private/LISTNAME/database/) is corrupt. Sorry to say, I don't know very much about these database files -- but, if you have a plain mbox archive of the list as well (located in ~mailman/archives/private/LISTNAME.mbox/LISTNAME.mbox), I guess the entire pipermail web archive can be regenerated from there. To regenerate, do rm -r ~mailman/archives/LISTNAME/ ~mailman/bin/arch LISTNAME ~mailman/archives/private/LISTNAME.mbox/LISTNAME.mbox (but make sure you have all the needed articles in the mbox archive first). > ps: don't you all agree mailman needs more publicity? Well, if it's _good_ publicity, then yes, of course :) > did rc1 get posted on freshmeat and stuff? Just checked, and yes, it seems like Barry did so. -- Harald

1 0

[Patch] "(Details)" bug, minor
by Bernhard Reiter 22 May '99

22 May '99

Fixed two minor bugs regarding the (Details) buttons on the general options page for a mailinglist. * hitting them openend another browser, this is unwanted from a usability point of view. If the user wants another window, he will tell his browser so or open one right away. Even if not everybody considers this a bug, it should be at least configurable (and off per default of course. ;> ) * The detail page lacks the submit button for really submitting the changed data. The comment in the code told the story. I added another line to save the user from losing the typed in information or the overview about the operations here. BTW: A guide on how to seamlessly integrate hypermail would be greatly appreciated, IMO. Regards, Bernhard

1 0

Re: [Mailman-Users] Archiving
by J C Lawrence 21 May '99

21 May '99

On Fri, 21 May 1999 13:52:34 +1000 Bek Oberin <gossamer(a)tertius.net.au> wrote: > Why would somebody want to use a non-Pipermail archiving program? > What're the advantages? Format and presentation control, intelligent search supports, and various databasing advantages come to mind for moving away from Pipermail. -- J C Lawrence Home: claw(a)kanga.nu ---------(*) Linux/IA64 - Work: claw(a)varesearch.com ... Beware of cromagnons wearing chewing gum and palm pilots ...

1 0

only users on my domain are able to subscribe???
by jason 21 May '99

21 May '99

why is it that only users that are on my domain getting confirmations returned to them?? jason jason2(a)stjohnscc.com

1 0

Re: [Mailman-Users] Mailman and Postfix
by Rupa Schomaker (list) 21 May '99

21 May '99

First some suggestions: 1) is mailman running under it's own UID? If so, then that is the UID you want the mail-wrapper to use. What is UID 600? 2) use a seperate database for the mailman aliases. Make sure the database is owned by user mailman. 3) When postfix delivers, it'll deliver with the UID of the alias file that matched your user. Thus it'll deliver using the mailman uid. eg: my site has /home/mailman/aliases with listalias. listalias is owned by mailman. I use postalias to build listalias.db. postalias is run as the *user* mailman. (not sure if the .db will be made with root's ownership if you use newaliases as root). I left out the new alias from alias_database 'cause I don't want newaliases to rebuil it -- rather I do so manually (or as part of the list creation process). /etc/postfix/main.cf has: alias_maps = hash:/etc/aliases, hash:/home/mailman/aliases/listalias Hope this is of some help... Gerard Hickey <Gerard.Hickey(a)nsc.com> writes: > OK. I have a really stupid problem, but I could not really find any > answers in the mailing list archive. > > For quite some time I have wanted to move my majordomo lists to mailman. > I finally got around to getting python 1.5.2 compiled and mailman seemed > to be working fine. After creating a test list and trying to send mail > through it, I started to have problems with the wrapper complaining > about the gid not matching. After reading for a while it sounded like > postfix would fix these problems (and I wanted to get away from sendmail > anyways). > > Now that I am running postfix, I still get simular problems. When mail > is sent to the test mailing list from across the network, everything > seems to work fine. But when a message is sent from the local machine > where postfix and mailman are running, I get the wonderful errors about > gid conflicts. Below are the messages from syslog about the problem. > > May 21 11:51:27 thoreau Mailman mail-wrapper: Failure to exec script. > WANTED gid 65534, GOT gid 600. (Reconfigure to take 600?) > May 21 11:51:27 thoreau Mailman mail-wrapper: Failure to exec script. > WANTED gid 65534, GOT gid 1. (Reconfigure to take 1?) > > Does anyone have a solution for this situation? > > Thanks.... > -- > Gerard Hickey email: Gerard.Hickey(a)nsc.com > National Semiconductor Corporation phone: +1 207 541 6101 > Advance Development Center, MS 03-03 fax: +1 207 541 6108 > 5 Foden Road, South Portland, Maine 04106-1706 > > -- Rupa (rupa(a)rupa.com for normal email) Please don't email duplicate replies.

1 0

Mailman and Postfix
by Gerard Hickey 21 May '99

21 May '99

OK. I have a really stupid problem, but I could not really find any answers in the mailing list archive. For quite some time I have wanted to move my majordomo lists to mailman. I finally got around to getting python 1.5.2 compiled and mailman seemed to be working fine. After creating a test list and trying to send mail through it, I started to have problems with the wrapper complaining about the gid not matching. After reading for a while it sounded like postfix would fix these problems (and I wanted to get away from sendmail anyways). Now that I am running postfix, I still get simular problems. When mail is sent to the test mailing list from across the network, everything seems to work fine. But when a message is sent from the local machine where postfix and mailman are running, I get the wonderful errors about gid conflicts. Below are the messages from syslog about the problem. May 21 11:51:27 thoreau Mailman mail-wrapper: Failure to exec script. WANTED gid 65534, GOT gid 600. (Reconfigure to take 600?) May 21 11:51:27 thoreau Mailman mail-wrapper: Failure to exec script. WANTED gid 65534, GOT gid 1. (Reconfigure to take 1?) Does anyone have a solution for this situation? Thanks.... -- Gerard Hickey email: Gerard.Hickey(a)nsc.com National Semiconductor Corporation phone: +1 207 541 6101 Advance Development Center, MS 03-03 fax: +1 207 541 6108 5 Foden Road, South Portland, Maine 04106-1706

3 3

nesting lists
by dominic＠juniper.net 21 May '99

21 May '99

First of all let me say that I am very impressed with mailman. It does almost everything we need it to do. However, I ran into one major problem. I am in the process of trying to migrate a complicated sendmail alias scheme to mailman. Currently we have a hierarchy of aliases. For example, a top level alias will point to lower level ones. The problem that I have is that when I nest lists with mailman, if someone is on more than one of the bottom level lists, they will get duplicate messages. Is there anyway for mailman not to send out duplicates in this case? Also, it is not possible to not have people on more than one of the lower level lists, so making sure that there are not duplicates is not an option. Any help would be appreciated! Dominic dominic(a)juniper.net

2 1

cron errors from mailman
by jason 21 May '99

21 May '99

any ideas why i keep getting this?

1 0