-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Gour wrote:
> dumpdb shows that everything is clean.
Hmmmm.
> 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 mailman config, either in
mm_cfg.py or Defaults.py, I would think.
The function that returns the archive URL is GetBaseArchiveURL() in
$prefix/Mailman/Archiver/Archiver.py. It consults VIRTUAL_HOSTS, so
what sort of things have you defined for VIRTUAL_HOSTS (most likely
using the add_virtualhost() call)?
Here's a quick little python script that will print out the keys from
VIRTUAL_HOSTS:
#! /usr/bin/python2
import paths
from Mailman import mm_cfg
for k, v in mm_cfg.VIRTUAL_HOSTS.items():
print k
I saved this in $prefix/bin/vhosts.py and ran it to get a list of
what's on my test system.
> Anything can be done?
Another WAG, but are there any apache directives that might be
affecting the URL's here? If you don't find anything in the Mailman
config that's inserting the old URL, that's the next place I'd look,
though it seems unlikely.
- --
Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp
======================================================================
If the world didn't suck, we'd all fall off.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl.
iD8DBQE/4KjOuv+09NZUB1oRApjKAJ4gamk+iyefn7gySaShrxqdpy20aQCff6Qu
y5COk56Xqin9W7rPu8f+CQY=
=fnv2
-----END PGP SIGNATURE-----
------------------------------------------------------
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
