Never mind, I just adjusted apache to only do port 82, and everything works now..
However, that brings up a potentially interesting option - to ignore all virtual hosts/ips and just answer all requests as if they were for one server. Not all of us are running 1000+ lists or members, even... -----Original Message----- From: Chris Wiegand [mailto:[EMAIL PROTECTED]] Sent: Friday, May 24, 2002 11:45 AM To: Mailman-Users (E-mail) Subject: [Mailman-Users] Lists not showing up on alternate port... I was using mailing on a machine where apache served both port 80 and 81 (81 was the port we had to use for extenal access). If I go to the mailman site on either port, it sees the name as mail.signalbhn.org, no problem, and lists the list. However, I just added port 82, as we have to move to that port now, and when I go to it on port 82, it sees the name as mail.signalbhn.org:82, and so no lists show up... I can't seem to figure out why it doesn't do that on port 81, or why it does do it on port 82... Any way I can reset the lists so they're on the new port? ------------------------------------------------------ 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 ------------------------------------------------------ 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