mailmanlistinfo without slash
I haven't seen this mentioned - When I look at the Archives of a list, I get the CORRECT message below:
No messages have been posted to this list yet, so the archives are currently empty. You can get more information about this list. <----underlined link
The [albeit minor] problem is that the link above is missing a "/" in the linked URL like the following example: http://www.mydomain.com/cgi-bin/mailmanlistinfo/listname
Note - Should be mailman/listinfo instead of mailmanlistinfo
Can I correct that somewhere? Thanks! - John
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.7.6 - Release Date: 1/27/2005
John Fleming wrote:
I haven't seen this mentioned - When I look at the Archives of a list, I get the CORRECT message below:
No messages have been posted to this list yet, so the archives are currently empty. You can get more information about this list. <----underlined link
The [albeit minor] problem is that the link above is missing a "/" in the linked URL like the following example: http://www.mydomain.com/cgi-bin/mailmanlistinfo/listname
Note - Should be mailman/listinfo instead of mailmanlistinfo
Can I correct that somewhere? Thanks! - John
It looks like you may have changed DEFAULT_URL_PATTERN in mm_cfg.py. Does it have a trailing slash?
If this is the problem, after you fix DEFAULT_URL_PATTERN, you need to run bin/fix_url.py under bin/withlist to fix the list(s). Just run
bin/fix_url.py
for instructions.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
It looks like you may have changed DEFAULT_URL_PATTERN in mm_cfg.py. Does it have a trailing slash?
No, it doesn't - Should it? If so, others don't have it either, e.g. this is how I found things:
DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman' PRIVATE_ARCHIVE_URL = '/cgi-bin/mailman/private' IMAGE_LOGOS = '/images/mailman/'
Thus the first 2 don't and last one does. Should they all have the trailing slash? (Actually I don't need the cgi-bin part, but I'll fix that later after I get the basic problem corrected.)
If this is the problem, after you fix DEFAULT_URL_PATTERN, you need to run bin/fix_url.py under bin/withlist to fix the list(s).
OK, I've added the trailing slash, run fix_url.py using withlist and restarted Mailman, but everything is the same - The link still has "listinfomailman" without the needed slash. Any more ideas?
Hi,
I don't know if this was the right answer but ...
John Fleming wrote:
OK, I've added the trailing slash, run fix_url.py using withlist and restarted Mailman, but everything is the same - The link still has "listinfomailman" without the needed slash. Any more ideas?
The initial pipermail index page is generated when the list is created. So, you must test it by another new list or do rmlist/newlist again.
-- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/
John Fleming wrote:
OK, I've added the trailing slash, run fix_url.py using withlist and restarted Mailman, but everything is the same - The link still has "listinfomailman" without the needed slash. Any more ideas?
The initial pipermail index page is generated when the list is created. So, you must test it by another new list or do rmlist/newlist again.
Thanks, Tokio - I'll test it with a new "test" list. If it appears fixed, and I use rmlist/newlist to recreate each of my lists, will all other parameters (members, privacy settings etc) be retained? Or will I be starting from scratch with each list if I recreate it with newlist?
- John
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.7.6 - Release Date: 1/27/2005
Thanks, Tokio - I'll test it with a new "test" list. If it appears fixed, and I use rmlist/newlist to recreate each of my lists, will all other parameters (members, privacy settings etc) be retained? Or will I be starting from scratch with each list if I recreate it with newlist?
You need to. You can however save lists/<listname>/config.pck somewhere else and restore it later.
-- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/
John Fleming wrote:
It looks like you may have changed DEFAULT_URL_PATTERN in mm_cfg.py. Does it have a trailing slash?
No, it doesn't - Should it? If so, others don't have it either, e.g. this is how I found things:
DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman' PRIVATE_ARCHIVE_URL = '/cgi-bin/mailman/private' IMAGE_LOGOS = '/images/mailman/'
Thus the first 2 don't and last one does. Should they all have the trailing slash? (Actually I don't need the cgi-bin part, but I'll fix that later after I get the basic problem corrected.)
I think it is best if they all do have the trailing slash, but there are many places in Mailman's code where the trailing slash is checked for and added if absent, but clearly not everywhere.
If this is the problem, after you fix DEFAULT_URL_PATTERN, you need to run bin/fix_url.py under bin/withlist to fix the list(s).
OK, I've added the trailing slash, run fix_url.py using withlist and restarted Mailman, but everything is the same - The link still has "listinfomailman" without the needed slash. Any more ideas?
As Tokio mentioned in another reply, the archive was probably built with the bad value and now that the list is fixed (assuming that is the fix) the archive needs to be rebuilt.
As Tokio also suggested, since there isn't anything in the archive yet, you could remove the list and recreate it (and use config_list to save the settings before deleting and restore them later), but if you have members and they have various different options, etc. it is probably much simpler to just do
bin/arch --wipe <listname>
to recreate the archive.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
----- Original Message ----- From: "Mark Sapiro" <msapiro@value.net> To: "John Fleming" <john@wa9als.com>; <mailman-users@python.org> Sent: Thursday, January 27, 2005 9:22 PM Subject: Re: [Mailman-Users] mailmanlistinfo without slash
John Fleming wrote:
It looks like you may have changed DEFAULT_URL_PATTERN in mm_cfg.py. Does it have a trailing slash?
No, it doesn't - Should it? If so, others don't have it either, e.g. this is how I found things:
DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman' PRIVATE_ARCHIVE_URL = '/cgi-bin/mailman/private' IMAGE_LOGOS = '/images/mailman/'
Thus the first 2 don't and last one does. Should they all have the trailing slash? (Actually I don't need the cgi-bin part, but I'll fix that later after I get the basic problem corrected.)
I think it is best if they all do have the trailing slash, but there are many places in Mailman's code where the trailing slash is checked for and added if absent, but clearly not everywhere.
If this is the problem, after you fix DEFAULT_URL_PATTERN, you need to run bin/fix_url.py under bin/withlist to fix the list(s).
OK, I've added the trailing slash, run fix_url.py using withlist and restarted Mailman, but everything is the same - The link still has "listinfomailman" without the needed slash. Any more ideas?
As Tokio mentioned in another reply, the archive was probably built with the bad value and now that the list is fixed (assuming that is the fix) the archive needs to be rebuilt.
As Tokio also suggested, since there isn't anything in the archive yet, you could remove the list and recreate it (and use config_list to save the settings before deleting and restore them later), but if you have members and they have various different options, etc. it is probably much simpler to just do
bin/arch --wipe <listname>
to recreate the archive.
Well, it doesn't like bin/arch as above because the archive is empty:
Luke:/var/lib/mailman/bin# ./arch --wipe sked
<snip>
Cannot open mbox file /var/lib/mailman/archives/private/sked.mbox/sked.mbox: [Errno 2] No such file or directory: '/var/lib/mailman/archives/private/sked.mbox/sked.mbox' Luke:/var/lib/mailman/bin#
I also tried just ./arch without the --wipe and got the same error.
*** I did create a brand new test list, and the link is CORRECT for that list, so fix_url after adding the trailing slash did fix the problem. Now to get the existing lists fixed - maybe. I intend for these lists to NOT have archives, so it's academic for existing lists. I just would like fix it so that the incorrect link doesn't appear if someone goes there out of curiosity and then hits the listinfo link to get back. I guess I might have to save the config and recreate the lists if I really want the link fixed that badly. Thanks Mark and Tokio for your help - Future lists won't have this problem! - John
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.7.6 - Release Date: 1/27/2005
John Fleming wrote:
Well, it doesn't like bin/arch as above because the archive is empty:
Luke:/var/lib/mailman/bin# ./arch --wipe sked
<snip>
Cannot open mbox file /var/lib/mailman/archives/private/sked.mbox/sked.mbox: [Errno 2] No such file or directory: '/var/lib/mailman/archives/private/sked.mbox/sked.mbox' Luke:/var/lib/mailman/bin#
I also tried just ./arch without the --wipe and got the same error.
*** I did create a brand new test list, and the link is CORRECT for that list, so fix_url after adding the trailing slash did fix the problem. Now to get the existing lists fixed - maybe. I intend for these lists to NOT have archives, so it's academic for existing lists. I just would like fix it so that the incorrect link doesn't appear if someone goes there out of curiosity and then hits the listinfo link to get back. I guess I might have to save the config and recreate the lists if I really want the link fixed that badly. Thanks Mark and Tokio for your help - Future lists won't have this problem! - John
Tokio's suggestion to move (or copy) lists/<listname>/config.pck aside and then remove and recreate the list and then move the config.pck back is a good one, but a simpler idea is if there is no archives/private/<listname>.mbox/<listname>.mbox file, just do
bin/arch --wipe sked /dev/null
or whatever your other list names might be.
I tested that this time and it works :-)
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
----- Original Message ----- From: "Mark Sapiro" <msapiro@value.net> To: "John Fleming" <john@wa9als.com>; <mailman-users@python.org> Sent: Thursday, January 27, 2005 11:08 PM Subject: Re: [Mailman-Users] mailmanlistinfo without slash
John Fleming wrote:
Well, it doesn't like bin/arch as above because the archive is empty:
Luke:/var/lib/mailman/bin# ./arch --wipe sked
<snip>
Cannot open mbox file /var/lib/mailman/archives/private/sked.mbox/sked.mbox: [Errno 2] No such file or directory: '/var/lib/mailman/archives/private/sked.mbox/sked.mbox' Luke:/var/lib/mailman/bin#
I also tried just ./arch without the --wipe and got the same error.
*** I did create a brand new test list, and the link is CORRECT for that list, so fix_url after adding the trailing slash did fix the problem. Now to get the existing lists fixed - maybe. I intend for these lists to NOT have archives, so it's academic for existing lists. I just would like fix it so that the incorrect link doesn't appear if someone goes there out of curiosity and then hits the listinfo link to get back. I guess I might have to save the config and recreate the lists if I really want the link fixed that badly. Thanks Mark and Tokio for your help - Future lists won't have this problem! - John
Tokio's suggestion to move (or copy) lists/<listname>/config.pck aside and then remove and recreate the list and then move the config.pck back is a good one, but a simpler idea is if there is no archives/private/<listname>.mbox/<listname>.mbox file, just do
bin/arch --wipe sked /dev/null
or whatever your other list names might be.
I tested that this time and it works :-)
The above seemed to work. I restarted Mailman, and then when clicking the Archives link on the Listinfo page, I was taken to Forbidden You don't have permission to access /pipermail/sked/ on this server.
I thought maybe I just needed to rebuild the archive, so I did that, but same error. I looked at the permissions of /var/lib/mailman/archives/private/sked.mbox and it is the same as my other lists that don't give the FORBIDDEN error - group-list, owner www-data, 2775 (set GID). Which page exactly has incorrect permissions?
Here's the bin/arch run:
Luke:/var/lib/mailman/bin# ./arch --wipe sked /dev/null Traceback (most recent call last): File "./arch", line 187, in ? main() File "./arch", line 166, in main shutil.rmtree(mlist.archive_dir()) File "/usr/lib/python2.3/shutil.py", line 142, in rmtree raise exc[0], (exc[1][0], exc[1][1] + ' removing '+arg) OSError: [Errno 2] No such file or directory removing /var/lib/mailman/archives/private/sked Luke:/var/lib/mailman/bin#
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.1 - Release Date: 1/27/2005
John Fleming wrote:
----- Original Message ----- From: "Mark Sapiro" <msapiro@value.net>
<snip>
bin/arch --wipe sked /dev/null
or whatever your other list names might be.
I tested that this time and it works :-)
The above seemed to work. I restarted Mailman, and then when clicking the Archives link on the Listinfo page, I was taken to Forbidden You don't have permission to access /pipermail/sked/ on this server.
I thought maybe I just needed to rebuild the archive, so I did that, but same error. I looked at the permissions of /var/lib/mailman/archives/private/sked.mbox and it is the same as my other lists that don't give the FORBIDDEN error - group-list, owner www-data, 2775 (set GID). Which page exactly has incorrect permissions?
/var/lib/mailman/archives/private/sked/index.html
The web accessable archive is in the sked/ directory. The sked.mbox/ directory only contains the sked.mbox file which is the archive in mbox format.
Here's the bin/arch run:
Luke:/var/lib/mailman/bin# ./arch --wipe sked /dev/null Traceback (most recent call last): File "./arch", line 187, in ? main() File "./arch", line 166, in main shutil.rmtree(mlist.archive_dir()) File "/usr/lib/python2.3/shutil.py", line 142, in rmtree raise exc[0], (exc[1][0], exc[1][1] + ' removing '+arg) OSError: [Errno 2] No such file or directory removing /var/lib/mailman/archives/private/sked Luke:/var/lib/mailman/bin#
It looks like there was no existing archive when you ran
bin/arch --wipe sked /dev/null
so the command failed and didn't build a new archive. The archive is gone because the previous
bin/arch --wipe sked
which failed on the lack of the sked.mbox file had removed the archive before failing.
So now try
bin/arch sked /dev/null
i.e. without the --wipe. This should build a new, empty archive.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
----- Original Message ----- From: "Mark Sapiro" <msapiro@value.net> To: "John Fleming" <john@wa9als.com>; "Mark Sapiro" <msapiro@value.net>; <mailman-users@python.org> Sent: Friday, January 28, 2005 3:00 PM Subject: Re: [Mailman-Users] mailmanlistinfo without slash
John Fleming wrote:
----- Original Message ----- From: "Mark Sapiro" <msapiro@value.net>
<snip>
bin/arch --wipe sked /dev/null
or whatever your other list names might be.
I tested that this time and it works :-)
The above seemed to work. I restarted Mailman, and then when clicking the Archives link on the Listinfo page, I was taken to Forbidden You don't have permission to access /pipermail/sked/ on this server.
I thought maybe I just needed to rebuild the archive, so I did that, but same error. I looked at the permissions of /var/lib/mailman/archives/private/sked.mbox and it is the same as my other lists that don't give the FORBIDDEN error - group-list, owner www-data, 2775 (set GID). Which page exactly has incorrect permissions?
/var/lib/mailman/archives/private/sked/index.html
The web accessable archive is in the sked/ directory. The sked.mbox/ directory only contains the sked.mbox file which is the archive in mbox format.
Here's the bin/arch run:
Luke:/var/lib/mailman/bin# ./arch --wipe sked /dev/null Traceback (most recent call last): File "./arch", line 187, in ? main() File "./arch", line 166, in main shutil.rmtree(mlist.archive_dir()) File "/usr/lib/python2.3/shutil.py", line 142, in rmtree raise exc[0], (exc[1][0], exc[1][1] + ' removing '+arg) OSError: [Errno 2] No such file or directory removing /var/lib/mailman/archives/private/sked Luke:/var/lib/mailman/bin#
It looks like there was no existing archive when you ran
bin/arch --wipe sked /dev/null
so the command failed and didn't build a new archive. The archive is gone because the previous
bin/arch --wipe sked
which failed on the lack of the sked.mbox file had removed the archive before failing.
So now try
bin/arch sked /dev/null
i.e. without the --wipe. This should build a new, empty archive.
I think that's right. I've done several things since my last post, and now everything's working great and life is good! I'd like to summarize for my own record and in case there's anyone as inept as me lurking here:
- The original problem was that on a list's archive page, there was an incorrect link to "More Information". That link was missing a slash, i.e. /mailmanlistinfo/listname. Several ways to handle that were mentioned, but I ended up saving the lists' .pck files and then deleting the lists and recreating and substituting the old .pck files. That fixed the original problem, and the missing slash appeared. However, there were now some virtual domain/weird link problems.
When I went to list A's archive page, the More Information link was to another domain, the main domain of the site. If I clicked this link, I actually went to the correct page for list A, even with the correct domain (although technically incorrect in the link). When I started looking around and messing with other lists, things got really confusing!
First I was told I should use fix_url.py. Then we decided I would also need to rebuild the archive after running fix_url.py to get the link corrected on the Archives page.
After some learning of how to use withlist, fix_url, and arch, I methodically went through each of my lists (I only have 4), running first fix_url and then rebuilding the archive. This got confusing to this newbie because when I rebuilt the archive, the ownership of the archive directory changed to the user I was running as rather than www-data. The owner of the archive has to be www-data or apache wouldn't let me surf that page later.
So for each list, I ran:
bin/withlist -r -l fix_url listname --urlhost=desireddomain
bin/arch --wipe listname /dev/null
Then I changed the ownership of /archives/listname (and maybe /archives/listname.mbox) to www-data. These were both group list and didn't need to be changed.
Then I restarted mailman (unnecessary?)
Now when I click on the Archives link on a listinfo page, the link contains the proper slashes, and I am taken to a page that says there are no archives. The link for More Information on that archive page uses the correct domain! YAY! Life is good!
I'm sure most of you knew all of this, but I've learned a lot. FAQ or no, when someone tells a newbie to run fix_url.py, you'd be surprised how difficult it can turn out to be. ;-) Thanks especially to Mark and Tokio and to everyone for your patience and bandwidth. - John
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.1 - Release Date: 1/27/2005
----- Original Message ----- From: "Mark Sapiro" <msapiro@value.net> To: "John Fleming" <john@wa9als.com>; <mailman-users@python.org> Sent: Thursday, January 27, 2005 10:57 AM Subject: Re: [Mailman-Users] mailmanlistinfo without slash
John Fleming wrote:
I haven't seen this mentioned - When I look at the Archives of a list, I get the CORRECT message below:
No messages have been posted to this list yet, so the archives are currently empty. You can get more information about this list. <----underlined link
The [albeit minor] problem is that the link above is missing a "/" in the linked URL like the following example: http://www.mydomain.com/cgi-bin/mailmanlistinfo/listname
Note - Should be mailman/listinfo instead of mailmanlistinfo
Can I correct that somewhere? Thanks! - John
It looks like you may have changed DEFAULT_URL_PATTERN in mm_cfg.py. Does it have a trailing slash?
If this is the problem, after you fix DEFAULT_URL_PATTERN, you need to run bin/fix_url.py under bin/withlist to fix the list(s). Just run
bin/fix_url.py
for instructions.
- and here's my ScriptAlias in my apache httpd.conf:
ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/ ScriptAlias /mailman/ /var/lib/mailman/cgi-bin/
participants (3)
-
John Fleming -
Mark Sapiro -
Tokio Kikuchi