[Bug 265965] Re: url parse (probably) cannot handle port number
mark at msapiro.net
Thu Jan 7 04:11:06 CET 2010
The original bug is invalid. If the site is properly configured with the
appropriate port in DEFAULT_URL_PATTERN and PUBLIC_ARCHIVE_URL in
mm_cfg.py the web interface works fine. E.g.
DEFAULT_URL_PATTERN = 'http://%s:8080/mailman
PUBLIC_ARCHIVE_URL = 'http://%(hostname)s:8080/pipermail/%(listname)s'
After making such a change in mm_cfg.py, you need to run fix_url to
update existing lists. See the FAQs at <http://wiki.list.org/x/gIA9> and
The issue in the comment from Raphael Mankin is probably because the
list's host_name attribute has a port. It should not. This in turn
probably results from having a port appended to DEFAULT_EMAIL_HOST or
the host in an add_virtualhost() directive. This is a misconfiguration.
Note that the list's host_name is exposed and can be changed on the
list's General Options admin page.
** Changed in: mailman
Status: New => Invalid
url parse (probably) cannot handle port number
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
More information about the Mailman-coders