Mailman 3 November 2007 - Mailman-Users

Re: [Mailman-Users] Re Problems with "more info" Hyperlink from ListArchives Page
by Barry Finkel Nov. 7, 2007

Nov. 7, 2007

Barry Finkel wrote: >>I wrote, in part, >> >>>>... >>>>I have 13 lists. For each list I checked the URL chains from the >>>> >>>> https://lists.example.com/mailman/listinfo >>>> >>>>Mailman "home page", and for five of the lists I see URL problems. >>>> >>>>... >>>> >>>>Note that the Mailman list archives page lacks a "/" between "mailman" >>>>and … [View More]"listinfo". For each of these bad lists I ran >>>> >>>> /usr/lib/mailman/bin/withlist -l -r fix_url $list -u lists.example.com >>>> >>>>but there were no changes to the URLs. >>>>... >> >>and "Richard Rae" <Richard_Rae(a)xyratex.com> replied: >> >>>You might need to run the fix_url command >>> >>>~/bin/withlist -l -r fix_url listname >> >>Is this any different than the command I ran? I tried the >> >> fix_url >> >>command without the >> >> -u lists.example.com >> >>parameter, and the URLs did not change. and Mark Sapiro replied: >Yes, it is different, but that is not the current problem (or maybe it >was, but more on that in a paragraph). > >The -u option sets the url_host in case that list's url_host is >different from DEFAULT_URL_HOST, which I gather in your case it is not. > >Here's what I think the issue is. When you originally changed >DEFAULT_URL_PATTERN for the https scheme you left off the trailing >slash and added cgi-bin/as in > >DEFAULT_URL_PATTERN = 'https://%s/cgi-bin/mailman' >(when the 'mailman' list was created) > >also, apparently at some point you had other things like > >DEFAULT_URL_PATTERN = 'https://%s/cgi-bin/mailman/' >(bad3 through bad 6) >and > >DEFAULT_URL_PATTERN = 'https://%s/' >(bad2) > > >You later corrected that to > >DEFAULT_URL_PATTERN = 'https://%s/mailman/' > >and (perhaps later still) ran fix_url which fixed the hidden >web_page_url attribute on these six lists. > >However, the archive pages are static HTML pages. Current index and TOC >pages are constantly rebuilt as messages are added to the archives, >but pages that haven't been updated since before you ran fix_url will >have bad links as you observe. > >There are a few ways to fix this. The easiest is to run 'bin/arch >--wipe' on all the problem lists, but if these lists have archives >going back to older Mailman versions (I'm not sure how old is a >problem, but maybe 2.0.x, maybe pre 2.1.4), there are some potential >issues in that there may be unescaped "From " lines in message bodies >that are taken as mbox message separators by the archiver >(bin/cleanarch can help find/fix these). Also, there is a possibility >that messages may get renumbered in the archive which is not a problem >in itself, but it invalidates any saved URLs linking to individual >archive messages. > >If you don't want to run 'bin/arch --wipe' you can ignore the problem. >The main TOC page and the current period's index pages should get >fixed the next time a message is archived for the list, and new index >pages will be built correctly. If older index pages are a concern, >they can be edited with a script. Mark has a correct diagnosis. I went back through my records, and I did have different DEFAULT_URL_HOST values when I created these test lists. Each list was created with Mailman 2.1.9, so for most of the lists, sending another test posting to the list corrected the archive URL. I did not run bin/arch --wipe because I did not need to, and also I was unsure of the proper parameters. I also did not have time to look for the man page. I know that when I convert a Majordomo list to Mailman, I have to run /usr/lib/mailman/bin/arch --wipe $LISTNAME majordomolist.mbox after creating the majordomolist.mbox file from the Majordomo list archives. On my Ubuntu system man arch displays the man page for arch - print machine architecture One thing that fixurl did that I was not expecting was to change host_name back to the default in one test list where I had set it to another nodename for testing. But re-setting this parameter was easy to do via the admin web interface. ---------------------------------------------------------------------- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone: +1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: BSFinkel(a)anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994 [View Less]

2 1

Manipulating membership management flags (e.g., nomail) from the command-line?
by Chris Waltham Nov. 6, 2007

Nov. 6, 2007

I administer a Mailman 2.0.12 server that runs many (>870) mailing lists, the vast majority are used internally where I work. However, we have the odd external recipient; more problematically we have a bunch of internal recipients (e.g., username(a)bowdoin.edu) that forward their mail to an external provider like gmail. A couple of days ago I was troubleshooting an issue for a user and noticed that the "nomail" option was set for them in a particular list. Obviously, because of … [View More]

2 1

How does one back up the email address in a list...
by Mark Schlaudraff Nov. 6, 2007

Nov. 6, 2007

I'm sorry if this is posted some where however, I am unable to locate it... How do I export or backup the email address that are in a list? Thanks, Mark

2 1

Defaults.py file - pipeline changes
by Jewel Makda Nov. 6, 2007

Nov. 6, 2007

My list owners were getting hit pretty hard with spam, almost 4,000 just over a weekend. I did the following which has blocked most if not all of the spam going to listowners. What I did was the following: I edited the Defaults.py file to have the -owner messages go through the same pipeline as the normal messages delivered to list members. I know that one downside to this change is if someone wanted to subscribe to a list and sent an email to listname-owner(a)domain.com, the request it … [View More]

3 2

integrating mailman members list with another database
by David Beaumont Nov. 5, 2007

Nov. 5, 2007

We run a mailman list. Anyone can subscribe but we would prefer to restrict subscription to members of our not-for-profit organisation. We have those members on an online database. Has anyone ever linked the mailman list of subscribers to another database of email addresses and is there any way apart fom manually checking against our membership list and manually deleting subscribers to our mailman list? Apologies if it's in the FAQ I did look though. thanks David -- View this message in … [View More]

3 3

Rejection Message
by Martin Dennett Nov. 4, 2007

Nov. 4, 2007

When posting to a list, if I reply to a reply to a reply, I get a rejection from the server saying "The message's content type was not explicitly allowed" - but prior to this, the messages get accepted. Any ideas what may be causing this, and what the admin can do (no command line access) to prevent this from happening, please? Rgds MD

2 4

List archvie
by mattias Nov. 4, 2007

Nov. 4, 2007

I installed mailamn in debian with apt-get install But no listarchive A 404 page comes upp if i click on a mail archive link

2 1

Time change
by Mikael Hansen Nov. 4, 2007

Nov. 4, 2007

I was wondering if there are any issues in 2.1.9 or 2.1.8 with having the same hour twice, concerning archives and other sequence related matters such as moderating a message stamped later than the approval of it. Not that I plan on getting up at that time to check on things for a bit anyway, because if I do, I'll likely forget to turn off the alarm clock and then be woken up once again an hour later ;-) Mikael

3 2

[Fwd: Error: "Bad owner email address: mailman@(unused)" in SuSE 10.1]
by Jacques Dailey Nov. 4, 2007

Nov. 4, 2007

Hello, I set up Mailman as described in the README.SuSE documentation included in the install package. Everything seemed to be going fine until I got to step 4. ". . . call "/usr/lib/mailman/bin/newlist mailman" to create the master mailing list". Doing so resulted in the error "Bad owner email address: mailman@(unused). I am running OpenSuSE 10.1 x86_64. Upon checking /etc/aliases, I find the following entries: mailman: root mailman-owner: mailman What am I missing? Thanks, JD

2 2

Configuring Mailman account using URL-parameters.
by Jurgen Gaeremyn Nov. 2, 2007

Nov. 2, 2007

Hi, I've figured out it's possible to parse a lot of Mailman configuration directly through a URL (like the one below) http://mydomain.com/mailman/admin/mylist_mydomain.com/members/remove?send_u… This kind of coding is used in a Joomla-mailman bridge, and I'm looking into integrating this further into the website... I'd like users to allow to change their settings from inside the main website (without having to ask them for a second password or exposing the master password in a frame) So … [View More]

2 1