Odhiambo Washington writes: > When I enter the admin page of my list, all links point to > HTTPS://my.dom.ain, except the one that points to the list archives which > points to HTTP. > How is this possible?
It's *possible* because list archives are frequently hosted at a different URL, so the base URLs for archive URLs have a separate variable from the base for Mailman admin (including user configuration) pages. There are several ways they might have become different in your case so I'm not going to try to enumerate them, but check in mm_cfg.py: # The url template for the public archives. This will be used in several # places, including the List-Archive: header, links to the archive on the # list's listinfo page, and on the list's admin page. # # This should be a string with "%(listname)s" somewhere in it. Mailman will # interpolate the name of the list into this. You can also include a # "%(hostname)s" in the string, into which Mailman will interpolate # the host name (usually DEFAULT_URL_HOST). PUBLIC_ARCHIVE_URL = 'http://%(hostname)s/pipermail/%(listname)s/' and compare with: # Mailman needs to know about (at least) two fully-qualified domain names # (fqdn); 1) the hostname used in your urls, and 2) the hostname used in email # addresses for your domain. For example, if people visit your Mailman system # with "http://www.dom.ain/mailman"; then your url fqdn is "www.dom.ain", and # if people send mail to your system via "yourl...@dom.ain" then your email # fqdn is "dom.ain". DEFAULT_URL_HOST controls the former, and # DEFAULT_EMAIL_HOST controls the latter. Mailman also needs to know how to # map from one to the other (this is especially important if you're running # with virtual domains). You use "add_virtualhost(urlfqdn, emailfqdn)" to add # new mappings. # # If you don't need to change DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST in your # mm_cfg.py, then you're done; the default mapping is added automatically. If # however you change either variable in your mm_cfg.py, then be sure to also # include the following: # # add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) # # because otherwise the default mappings won't be correct. DEFAULT_EMAIL_HOST = 'localhost' DEFAULT_URL_HOST = 'localhost' DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/' # DEFAULT_HOST_NAME has been replaced with DEFAULT_EMAIL_HOST, however some # sites may have the former in their mm_cfg.py files. If so, we'll believe # that, otherwise we'll believe DEFAULT_EMAIL_HOST. Same for DEFAULT_URL. DEFAULT_HOST_NAME = None DEFAULT_URL = None I've included the docs from Defaults.py. Note that PUBLIC_ARCHIVE_URL is separated from the other URLs by a lot of text in Defaults.py. Of course they can be in any order in mm_cfg.py. As you can see from the defaults the URLs for all of these variables default to the http scheme. I suspect that when you (re)configured your lists for HTTPS, you didn't fixup PUBLIC_ARCHIVE_URL, and it seemed to Just Work (except for the URL scheme) because you have a single-domain setup. Let me know if that wasn't it. Steve ------------------------------------------------------ Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
