url parse (probably) cannot handle port number

[Mcocke]

If you use a port number on the url (example
www2.catherders.com:3800, such as dyndns webhob
requires) the web interface breaks/fails to function in
many places.

[http://sourceforge.net/tracker/index.php?func=detail&aid=811343&group_id=103&atid=100103]

[Raphael Mankin (raph+mailman)]

In particular, all mails sent from mailman have the port number on the end of the reply address. This causes certain mail servers to reject the messagges.

A workaround is to have two web listeners, one on port 80 and one on the real port e.g. 8080. One then redirects all mailman requests on port 80 to the other port. I do this because I have to have my main web server and my mailman web server running as different users.

The problem is current in 2.1.12

[Mark Sapiro (msapiro)]

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 <http://wiki.list.org/x/mIA9>.

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.