Re: [Mailman-Users] Welcome to the "Mailman-Users" mailing list
In message mailman.1896.1119496649.10510.mailman-users@python.org, mailman-us ers-request@python.org writes:
Welcome to the Mailman-Users@python.org mailing list! Don't forget to check out the Mailman FAQ at:
Howdy, all!
I have a mysterious mailman migration muddle.
Platform: NetBSD 2.0.2, with Mailman 2.1.6. Lists: Several lists imported from an old Linux box.
Symptoms: Lists are Not Seen. Messages sent to mailman aliases (e.g., list-subscribe@) are delivered, according to sendmail. Nothing Happens. No log messages anywhere I can find. No errors. No bounce.
Admin.cgi doesn't see the lists.
I verify that, yes, I have a list named "mailman". "newlist mailman" says it already exists.
In desperation, I delete that list and rerun newlist mailman. Now that one list shows up. No others do.
Here's the neat part. I run dbdump on the config.pck files from the old and new copies of that directory.
*** /tmp/t Wed Jun 22 22:11:01 2005 --- /tmp/u Wed Jun 22 22:11:19 2005
*** 2,15 **** <----- start object 1 -----> { 'accept_these_nonmembers': [], 'acceptable_aliases': '\n', ! 'admin_immed_notify': True, 'admin_member_chunksize': 30, ! 'admin_notify_mchanges': False, 'admin_responses': {}, ! 'administrivia': True, ! 'advertised': True, ! 'anonymous_list': False, ! 'archive': True, 'archive_private': 0, 'archive_volume_frequency': 1, 'autorespond_admin': 0, --- 2,15 ---- <----- start object 1 -----> { 'accept_these_nonmembers': [], 'acceptable_aliases': '\n', ! 'admin_immed_notify': 1, 'admin_member_chunksize': 30, ! 'admin_notify_mchanges': 0, 'admin_responses': {}, ! 'administrivia': 1, ! 'advertised': 1, ! 'anonymous_list': 0, ! 'archive': 1, [...]
See anything suspicious here?
I am wondering whether the "True" vs. "1" distinction could be what is causing this to fail.
If it is... How do I fix it? I do not want to delete the lists and start over, because they have people on them.
I regret to admit that I have at most twenty milliclues about Python in general, and mailman in particular. (That said, I am already starting to think that, if I can figure out how mailman works, I may want to start migrating things to it from majordomo, because it's prettier.)
-s
Peter Seebach wrote:
In message mailman.1896.1119496649.10510.mailman-users@python.org, mailman-us ers-request@python.org writes:
Welcome to the Mailman-Users@python.org mailing list! Don't forget to check out the Mailman FAQ at:
And if you had, you might have come across http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.029.htp which would have helped with your problem.
You need to run fix_url against your old lists as explained in the 'Existing versus new lists' section of the above FAQ article.
-- Mark Sapiro msapiro@value.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
In message PC174020050627181552073442ec27d2@msapiro, Mark Sapiro writes:
Peter Seebach wrote:
In message mailman.1896.1119496649.10510.mailman-users@python.org, mailman-us ers-request@python.org writes:
Welcome to the Mailman-Users@python.org mailing list! Don't forget to check out the Mailman FAQ at:
And if you had, you might have come across http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.029.htp which would have helped with your problem.
You need to run fix_url against your old lists as explained in the 'Existing versus new lists' section of the above FAQ article.
Thanks! I actually did search the FAQ, but I apparently used the wrong search keywords. That looks helpful. I was looking for explanations of the behavior; I had no idea that the URLs were encoded in the list, or mattered, so I had no idea I needed to read the stuff about changing the URL. I assumed that since the Mailman list was showing up, the URL was set correctly...
-s
Peter Seebach wrote:
Thanks! I actually did search the FAQ, but I apparently used the wrong search keywords. That looks helpful. I was looking for explanations of the behavior; I had no idea that the URLs were encoded in the list, or mattered, so I had no idea I needed to read the stuff about changing the URL. I assumed that since the Mailman list was showing up, the URL was set correctly...
If you could let us know what searches you tried that didn't return the article or how we could better describe what the article addresses, we can try to update the FAQ to do better next time.
-- Mark Sapiro msapiro@value.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
In message PC1740200506281158130765eaa63bca@msapiro, Mark Sapiro writes:
If you could let us know what searches you tried that didn't return the article or how we could better describe what the article addresses, we can try to update the FAQ to do better next time.
Good point!
The issue here is that the FAQ describes what to do, and even mentions "old lists", but doesn't mention the symptoms. As a person whose mailman installation is failing, the only thing I have access to is symptoms. It would be good to have cross-references to this in the troubleshooting stuff; for instance, in the same place where you talk about database conversion (which I found) or the importance of creating an umbrella list (which I found).
I had no information that would have led me to suspect that "URLs" were part of my problem. I didn't know that a list had a URL encoded in it or anything like that. What I knew was that I had lists which looked correct, but which didn't show up on the admin.cgi page. And, also, where test messages to those lists produced no response at all, not even a mention in the log file.
Those are the kinds of symptoms I was looking at, and I knew enough to look around at the symptoms, but that FAQ entry, while describing what one needs to do, doesn't mention any symptoms... So there's no likelihood of a match.
I would think the right sort of thing would be a checklist of "things that can make a list not work", and have "wrong URL encoded in list (common when migrating lists)" on it. :)
-s
participants (2)
-
Mark Sapiro -
seebs＠plethora.net