Mailman 3 August 2000 - Mailman-Users

news gateway errors
by Alan Batie Aug. 31, 2000

Aug. 31, 2000

Every now and then, gate_news errors: Date: Wed, 30 Aug 2000 19:55:06 -0700 (PDT) From: mailman(a)pico.passedge.com (Cron Daemon) To: mailman(a)pico.passedge.com Subject: Cron <mailman@pico> /usr/local/bin/python /usr/local/mailman/cron/gate_news Traceback (innermost last): File "/usr/local/mailman/cron/gate_news", line 119, in ? main() File "/usr/local/mailman/cron/gate_news", line 101, in main lock.unlock() File "/usr/local/mailman/Mailman/LockFile.py", line 263, in unlock raise NotLockedError Mailman.LockFile.NotLockedError This *looks* like perhaps the previous gate_news hadn't finished and the locking mechanism isn't working right, but I'm only gating about a dozen very low volume internal newsgroups. I find it hard to believe that it takes five minutes to process that... -- Alan Batie ______ www.rdrop.com/users/alan Me alan(a)batie.org \ / www.qrd.org The Triangle PGPFP DE 3C 29 17 C0 49 7A \ / www.pgpi.com The Weird Numbers 27 40 A5 3C 37 4A DA 52 B9 \/ www.anti-spam.net NO SPAM!

1 0

Re: [Mailman-Users] listmembers being "(ignored)", lockfile problems, 2.0b5
by J C Lawrence Aug. 31, 2000

Aug. 31, 2000

On Wed, 30 Aug 2000 16:44:05 -0400 Brett Dikeman <brett(a)iclick.com> wrote: > Greetings. This is a edited version of a post I sent to the > developers this morning. No response, so I can only assume no one > cares to respond. At least have the good grace to wait a day or two. Not all of us read this list that quickly -- lately for instance I tend to read it only every couple days. I know others are in a similar circumstance and Barry has recently stated that he's buried in the Python 2.0 release and does not have much time to spend on the Mailman lists until that's done. > in logs/smtp-failure: What do your MTA's logs say? -- J C Lawrence Home: claw(a)kanga.nu ---------(*) Work: claw(a)nuron.com http://www.kanga.nu/~claw/ Keys etc: finger claw(a)kanga.nu --=| A man is as sane as he is dangerous to his environment |=--

2 1

hard links
by Dan Mick Aug. 30, 2000

Aug. 30, 2000

Gerhard points out that the issue in question may be the "Openwall kernel patches", which are documented at http://www.openwall.com/linux/README If this is the root of "some Linuxes have problems with hardlinks", then according to that, it's because the patch prevents users from making hardlinks to files they don't own. If that's so, then the solution would be "make mailman own all the files in ~mailman", which seems to me to be a better solution in general anyway; given that chown takes a "recursive" parameter, it's easy. Anyone having mysterious permission problems with links should probably try this, after verifying that bin/check_perms doesn't report problems.

1 0

Re: [Mailman-Users] Archival failure (HyperArch?)
by Dan Mick Aug. 30, 2000

Aug. 30, 2000

> I've just set up a 2.0b5 server. I have all the list functionality > working right, as far as I know, but there are no HTML archives. The > mbox file is being updated -- I can see the messages in there -- but > it's not being converted to HTML. > > "arch" is being run, though. When I run it manually, I get: > Pickling archive state into /var/mailman/archives/private/list/pipermail.pck > > And the web stuff says (no matter whether I run arch directly, or let > Mailman do it): > Currently, there are no archives. 'arch' is not normally run to archive mail; it's merely a "rebuild" convenience command. Mails are normally archived internally by invoking methods in Archiver.py, specifically (usually) ArchiveMail(). However, diagnosing 'arch' would be a good thing to do. > I know I have a weird installation, but I don't know where to begin > debugging this -- not enough sense of HyperArch and pipermail's guts. > Any pointers? My standard recommendation: can you run arch under some sort of system-call-trace utility, and watch what files it opens (or tries) and what it tries to write? Solaris: truss Linux: strace

2 1

Re: [Mailman-Users] error during admin auth
by Dan Mick Aug. 30, 2000

Aug. 30, 2000

Does someone who knows the story about Mandrake and restricted hardlinks want to stand up and explain it? I spent an hour searching the web yesterday and came up empty. (I don't run Mandrake but I'd like to understand what the issue is.) > Date: Thu, 31 Aug 2000 00:29:59 -0700 > From: Gerhard Mourani <gmourani(a)openna.com> > X-Accept-Language: en > To: mailman-users(a)python.org > Subject: [Mailman-Users] error during admin auth > X-Beenthere: mailman-users(a)python.org > X-Mailman-Version: 2.0beta5 > List-Id: Mailman mailing list management users <mailman-users.python.org> > > Hi, > > I'm trying to configure my mailling list through the administrative > authentication web page and receive the following error: > > Traceback (innermost last): > File "/usr/share/mailman/scripts/driver", line 96, in run_main > main() > File "/usr/share/mailman/Mailman/Cgi/admin.py", line 136, in main > mlist.Save() > File "/usr/share/mailman/Mailman/MailList.py", line 847, in Save > self.__save(dict) > File "/usr/share/mailman/Mailman/MailList.py", line 822, in __save > os.link(fname, fname_last) > OSError: [Errno 1] Operation not permitted > > The problem is "Operation not permitted" why?? > > The directory under where mailman is installed is as follow: > > drwxrwsr-x 16 root mailman 4096 Aug 30 17:53 . > drwxr-xr-x 13 root root 4096 Aug 30 17:53 .. > drwxrwsr-x 8 root mailman 4096 Aug 30 17:55 Mailman > drwxrwsr-x 4 root mailman 4096 Aug 30 17:53 archives > drwxrwsr-x 2 root mailman 4096 Aug 30 17:53 bin > drwxrwsr-x 2 root mailman 4096 Aug 30 17:53 cgi-bin > drwxrwsr-x 2 root mailman 4096 Aug 30 17:54 cron > drwxrwsr-x 2 root mailman 4096 Aug 30 17:54 data > drwxrwsr-x 2 root mailman 4096 Aug 30 17:53 filters > drwxrwsr-x 3 root mailman 4096 Aug 30 17:57 lists > drwxrwsr-x 2 root mailman 4096 Aug 31 00:38 locks > drwxrwsr-x 2 root mailman 4096 Aug 30 17:58 logs > drwxrwsr-x 2 root mailman 4096 Aug 30 17:53 mail > drwxrwsr-x 2 root mailman 4096 Aug 30 16:48 qfiles > drwxrwsr-x 2 root mailman 4096 Aug 30 18:00 scripts > drwxrwsr-x 2 root mailman 4096 Aug 30 17:53 templates > > Thanks, > > / / Gerhard Mourani > > > ------------------------------------------------------ > Mailman-Users maillist - Mailman-Users(a)python.org > http://www.python.org/mailman/listinfo/mailman-users

1 0

Archival failure (HyperArch?)
by David Champion Aug. 30, 2000

Aug. 30, 2000

I've just set up a 2.0b5 server. I have all the list functionality working right, as far as I know, but there are no HTML archives. The mbox file is being updated -- I can see the messages in there -- but it's not being converted to HTML. "arch" is being run, though. When I run it manually, I get: Pickling archive state into /var/mailman/archives/private/list/pipermail.pck And the web stuff says (no matter whether I run arch directly, or let Mailman do it): Currently, there are no archives. I know I have a weird installation, but I don't know where to begin debugging this -- not enough sense of HyperArch and pipermail's guts. Any pointers? -- -D. dgc(a)uchicago.edu NSIT University of Chicago

1 0

Re: [Mailman-Users] create new list problem
by Dan Mick Aug. 30, 2000

Aug. 30, 2000

sha is supposed to be a python builtin; your Python must have problems. Try getting a better one. > File "/home/mailman/Mailman/Message.py", line 30, in ? > import sha > ImportError: No module named sha

1 0

Re: [Mailman-Users] some suggestions for mailman 2
by J C Lawrence Aug. 30, 2000

Aug. 30, 2000

On Thu, 31 Aug 2000 10:57:17 +1100 Anand Kumria <wildfire(a)progsoc.uts.edu.au> wrote: > On Wed, Aug 30, 2000 at 11:23:39AM -0700, J C Lawrence wrote: >> http://www.kanga.nu/lists/listinfo/ > http://slug.org.au/lists/ Good show. >> This has required no patching to any of the Mailman sources, >> other than the normal Defaults.py/mm_cfg.py business. >> >> (Yes, I know I'm running v1.1, but the same was true when testing >> out moving to one of the v2 betas (I'm not ready to roll it into >> production there)) > Strange, I'm using 1.1 as well and in SecurityManager.py, I traced > my administration authentication problem down to: ...patch deletia... > Otherwise things were working correctly. All I can say is that I don't have a matching edit to my file and it works perfectly (I'm a little tight for time to fully research it). FWIW I'm using the Debian slink package on a woody system (not ready to upgrade to the woody v2 mailman yet). It is also possible that this is due to the fact that I only moderate under Mozilla. I haven't used other browsers. >> This is what the umbrella options are for. > Yes but it is currently an all or nothing affair (afaict). Either > all your list members are people or they are all sublists and > never the two shall mix. <checking quickly as I've never used the Umbrella feature directly) True, it does look that way. > I've unfortunately inhereted a list with mixed subscribers. But > even if I hadn't I can see great uses with having `sublist' be a > per subscriber option - for large lists you could have domain > based feeders, etc. BTW: You might want to take a look at my archiving setup for your lists. See: http://www.kanga.nu/archives/ with the (currently undocumented and slightly out of date) sources available under: ftp://ftp.kanga.nu/pub/Kanga.Nu/WebArchives/ Its a combo of MHonArc to do the actual archiving, some bash scripts to handle the directory business, and then various PHP and PHPLib-based bits to support the final rendering of the pages to the user/browser. The main thing it adds is format and look'n'feel control, and MIME support to the archives (all compliments of MHonArc), the ability to reply to archived messages right from the web (compliments PHP), and the ability to entirely redefine the presentation/look'n'feel of the archives without having to regen them (compliments of PHPLib's templating supports). -- J C Lawrence Home: claw(a)kanga.nu ---------(*) Work: claw(a)nuron.com http://www.kanga.nu/~claw/ Keys etc: finger claw(a)kanga.nu --=| A man is as sane as he is dangerous to his environment |=--

2 1

listmembers being "(ignored)", lockfile problems, 2.0b5
by Brett Dikeman Aug. 30, 2000

Aug. 30, 2000

Greetings. This is a edited version of a post I sent to the developers this morning. No response, so I can only assume no one cares to respond. I searched through my archives. I couldn't search through the list archives because the search engine on python.org appears to be broken(and yes, I followed the instructions, choosing only SIG archives.) I found a bunch of posts related or similar to my problems, but not much in the way of resolutions or anthing that seemed to help me. The setup we're running is Solaris, python 1.5.2, which I compiled myself. The list was working great, until people started loosing mail delivery. I thought the auto-bounce handler was removing people, but they're still listed as subscribed, and I never received a message from the bounce handler saying they would be removed. Now, what I'm seeing in the logs: in logs/smtp-failure: smtp-failure:Aug 30 11:16:15 2000 (122) -1 <email addr> (ignore) (many, many times) This user is in fact not getting email from either of the two lists he belongs to. The number in ()'s changes, though not with every entry in the logs. and, in logs/post, I see constant entries about: Aug 30 04:53:08 2000 (23571) post to <listname> from <listname>-request@<hostname>, size=28501, 177 failures (always the same number of failures and size; seems to be some sort of unrelated mail loop of some kind.) and there are posts that go through: Aug 30 04:44:42 2000 (23411) post to <listname> from <some subscriber's email address>, size=528, success Qrunner seems to be working: Aug 30 02:55:04 2000 (22304) qrunner begining Aug 30 02:55:09 2000 (22304) qrunner ended (this is repeated every time qrunner is launched, which is wasteful in terms of space since it runs once a minute; I've got 56k of text for less than 12 hours of running) Now, this mystery "177 failures" message shows up again: Aug 30 06:50:10 2000 (25068) All recipients refused: please run connect() first Aug 30 06:50:10 2000 (25068) smtp for 177 recips, completed in 2.620 seconds In logs/bounce, I'm not sure I understand the meanings: Aug 29 23:13:31 2000 (18077) <listname>: <someuser> - 27 more allowed over 426977 secs then there will be: Aug 29 23:13:33 2000 (18077) <listname>: <differentuser> - 0 more allowed over 395006 secs The non-delivery problem affects digest and non-digest users. Archives are working fine. One list is 1,500 people; 500 normal, 1000 digest users; the other is about 100 people, mostly non-digest. We're using sendmail, and I have the threaded delivery turned on due to the large number of slow/bad mail servers(and experience has shown that splitting them up into chunks results in a dramatic improvement in delivery times.) Some mail is getting by, and some users report that after re-subscribing, their problems have gone away, although I made some changes(like clearing out qfiles/ and also removing stale lockfiles) around the same time, so it's hard to tell.) However, several users are still not getting any mail no matter what I do(they do get the list welcome message when I re-subscribe them, however.) Thanks all for any help/tips. I wouldn't mind applying some patches that have been introduced since 2.0b5 that will fix this stuff, if they're available. Brett

3 2

Re: [Mailman-Users] some suggestions for mailman 2
by J C Lawrence Aug. 30, 2000

Aug. 30, 2000

On Wed, 30 Aug 2000 12:04:07 +1100 Anand Kumria <wildfire(a)progsoc.uts.edu.au> wrote: > I've now been using Mailman (note no studly caps) for a while so, > here are some comments: > - I've placed my lists at /lists/ instead of /mailman/ so > that required a patch to SecurityManager.py to send cookies with > the right path I do the same, as you can see here: http://www.kanga.nu/lists/listinfo/ This has required no patching to any of the Mailman sources, other than the normal Defaults.py/mm_cfg.py business. (Yes, I know I'm running v1.1, but the same was true when testing out moving to one of the v2 betas (I'm not ready to roll it into production there)) > - I'd be *most useful* to have a another subscriber option > which indicated that the subscriber wasn't really a person but > was, in reality, a sublist. For those subscribers monthly notices > (which should also be a per-subscriber thing IMO) and other > administrativia would be sent to owner-<subscriber> (or > <subscriber>-owner, or <subscriber>-admin). This is what the umbrella options are for. > - I'd love to be able to edit messages that get held for > approval. So that I can remove HTML from some email, reset the > reply-to to somewhere more appropriate or simply trim things down > and insert a "modified by whomever" message. On v2 you can. -- J C Lawrence Home: claw(a)kanga.nu ---------(*) Work: claw(a)nuron.com http://www.kanga.nu/~claw/ Keys etc: finger claw(a)kanga.nu --=| A man is as sane as he is dangerous to his environment |=--

2 1