Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-18 Thread Gour
Todd ([EMAIL PROTECTED]) wrote: > Cool. Not a problem. I learned a few things in the process. I'm glad there was some value in it. > I suppose if it really bugs you, you might be able to add a urlhost > value to the config.pck file and then modify the GetBaseArchiveURL() > call to look for it

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-17 Thread Todd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gour wrote: > Todd ([EMAIL PROTECTED]) wrote: [...] >> All right. I see now. When you look at the code for >> GetBaseArchiveURL(), you see that it inverts the VIRTUAL_HOST >> dictionary (or is it a list?) and uses emailhost as the key. So with >> th

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-17 Thread Gour
Todd ([EMAIL PROTECTED]) wrote: Hi Todd! Fortunately I did not bet on Apache :-) > All right. I see now. When you look at the code for > GetBaseArchiveURL(), you see that it inverts the VIRTUAL_HOST > dictionary (or is it a list?) and uses emailhost as the key. So with > the emailhost the sam

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-17 Thread Todd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gour wrote: > Todd ([EMAIL PROTECTED]) wrote: > >> Perhaps you could post all your add_virtualhost() calls from >> mm_cfg.py. That might help someone spot something useful. > > DEFAULT_EMAIL_HOST = 'lists.domain.com' > DEFAULT_URL_HOST = 'lists.domain

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-17 Thread Gour
Todd ([EMAIL PROTECTED]) wrote: > The private archive url uses a different method to create the URL, > bypassing the VIRTUAL_HOSTS list. You can take a look at the code in > Archiver.py where GetBaseArchiveURL() is defined to see the difference > in how the URL's are determined. OK. Clear. > Wh

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-17 Thread Todd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gour wrote: > Todd ([EMAIL PROTECTED]) wrote: > >> If you don't see the old URL in config.pck using dumpdb, then the >> URL has to be getting picked up from the general mailman config, >> either in mm_cfg.py or Defaults.py, I would think. > > There is

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-17 Thread Gour
Todd ([EMAIL PROTECTED]) wrote: > If you don't see the old URL in config.pck using dumpdb, then the URL > has to be getting picked up from the general mailman config, either in > mm_cfg.py or Defaults.py, I would think. There is nothing like that and why should private url work? > Here's a quick

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-17 Thread Todd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gour wrote: > dumpdb shows that everything is clean. H. > I'll check (again) with PUBLIC_ARCHIVE_URL, but what about > config.pck? If you don't see the old URL in config.pck using dumpdb, then the URL has to be getting picked up from the general

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-17 Thread Gour
Todd ([EMAIL PROTECTED]) wrote: > config_list doesn't output every list setting. Using dumpdb you might > find where the bad url is stored. Then you can add that to a > config_list output file, change the value to what you want and > re-import it with config_list. dumpdb shows that everything i

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-17 Thread Todd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gour wrote: > I have tried wiht config_list and there was nothing suspicious in > non-working list. config_list doesn't output every list setting. Using dumpdb you might find where the bad url is stored. Then you can add that to a config_list output

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-17 Thread Gour
Todd ([EMAIL PROTECTED]) wrote: > That's not too difficult. Basically, you can use the fix_url.py > script as an example of how to create a withlist script to change any > list values you need. You can also use config_list to export the list > config to a file and then add or edit the value you

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-16 Thread Todd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gour wrote: > Todd ([EMAIL PROTECTED]) wrote: > >> Here's a WAG, does it matter that PUBLIC_ARCHIVE_URL is set before >> DEFAULT_URL_HOST? I don't know how Python handles that. If order >> counts, then PUBLIC_ARCHIVE_URL would be picking up the host

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-16 Thread Gour
Todd ([EMAIL PROTECTED]) wrote: > Here's a WAG, does it matter that PUBLIC_ARCHIVE_URL is set before > DEFAULT_URL_HOST? I don't know how Python handles that. If order > counts, then PUBLIC_ARCHIVE_URL would be picking up the hostname from > what's defined in Defaults.py. If order is irrelevant

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-16 Thread Todd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gour wrote: > PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s' > DEFAULT_URL_HOST = 'lists.vediclists.net' > DEFAULT_URL_PATTERN = 'https://%s/mailman/' Here's a WAG, does it matter that PUBLIC_ARCHIVE_URL is set before DEFAULT_URL_H

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-16 Thread Gour
Todd ([EMAIL PROTECTED]) wrote: > Well, just so we'll all know, what are they set to? PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s' DEFAULT_URL_HOST = 'lists.vediclists.net' DEFAULT_URL_PATTERN = 'https://%s/mailman/' > Was mailman restarted after they were last changed, b

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-16 Thread Todd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gour wrote: > Todd ([EMAIL PROTECTED]) wrote: > >> Check what you have PUBLIC_ARCHIVE_URL and DEFAULT_URL_HOST set to in >> either Defaults.py or mm_cfg.py. Here's some text from Defaults.py >> regarding PUBLIC_ARCHIVE_URL: > > They're set (in mm_cfg.

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-16 Thread Gour
Todd ([EMAIL PROTECTED]) wrote: > Check what you have PUBLIC_ARCHIVE_URL and DEFAULT_URL_HOST set to in > either Defaults.py or mm_cfg.py. Here's some text from Defaults.py > regarding PUBLIC_ARCHIVE_URL: They're set (in mm_cfg.py) and the mystery is that for some lists everything is OK, while o

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-16 Thread Todd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gour wrote: > If the listinfo is on http://lists.domain.com/mailman/listinfo/listname and >admin on http://lists.domain.com/mailman/admin/listname why is the > lists' archive on http://www.virtualdomain.com/mailman/pipermail/.. ? Check what yo

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-16 Thread Gour
Simon White ([EMAIL PROTECTED]) wrote: > The archives are stored as full messages including headers; these > headers will not change if you change the parameters because they are > stored as the were before. > > You can use the mbox style archive store to change the headers, by using > sed on the

Re: [Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-16 Thread Simon White
16-Dec-03 at 09:40, Gour ([EMAIL PROTECTED]) wrote : > The problem is that I used fix_url script to transfer few lists from old > www.virtualdomain.com virtual domain to the new lists.domain.com, but although > new messages have correct List-* headers, I cannot change List-Archive header, > i.e. it

[Mailman-Users] re-creating list archive - old List-Archive problem

2003-12-16 Thread Gour
Hi! I transferred several mailing lists from oldserver (V2.0.x) to the new server with Mailman 2.1.x. The problem is that I used fix_url script to transfer few lists from old www.virtualdomain.com virtual domain to the new lists.domain.com, but although new messages have correct List-* headers, I