[ mailman-Bugs-784888 ] Wrong domain in public archives

SourceForge.net noreply at sourceforge.net
Mon Dec 1 10:16:36 EST 2003

Bugs item #784888, was opened at 2003-08-07 13:03
Message generated for change (Comment added) made by bwarsaw
You can respond by visiting: 

Category: Pipermail
Group: 2.1 (stable)
>Status: Closed
Resolution: None
Priority: 5
Submitted By: Rob Brandt (robbrandt)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong domain in public archives

Initial Comment:
I *think* I've found a bug in 2.12.

I've had a longstanding issue with all of my mailing
lists pointing to the wrong domain for mail archives. 
When I originally set up the server, used an initial
"recreational" domain name not intended to be used
widely.  The intention was to switch to the real domain
names later once the server went live.  I did that, but
all of the URLs for archives (only archives) still
pointed to the stupid domain name.

I intended to fix this in 2.12 by using the fix_url
function while I was also fixing a bunch of other
stuff.  I've needed to move some of my lists to other
domains anyway, so this seemed like a good time.  So I
ran fix_url over almost all of my domains, and tested
them as I went.  Everything went as planned, except
some of them still had the archives pointing to the
recreational domain.
 Then it dawned on me that the ones that didn't get
fixed were all *public* archives; the ones that did get
fixed were all private.

I went to one of the public archives and switched it to
private, and the URL to the archives was then OK! 
Switched it back to public and it was wrong again.

So, it seems that this is a bug.  Or I've missed a
configuration setting somewhere.




>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-12-01 10:16

Logged In: YES 

Close as per the 2003-08-11 16:46 comments.


Comment By: Rob Brandt (robbrandt)
Date: 2003-08-11 16:46

Logged In: YES 

The problem is resolved, with great help from Richard
Barrett.  For the sake of posterity, let the bug archives show:

* Be sure you have proper virtual host mapping
(add_virtualhost()) in mm_cfg.py;
* Be sure that the list setting for "Host name this list
prefers for email" is in fact your mail exchange address,
not a base URL for browsing (which was my problem);
* Run fix_url.py


Comment By: Tokio Kikuchi (tkikuchi)
Date: 2003-08-11 08:15

Logged In: YES 

Have you defined your (url_host, mail_host) pair in your
mm_cfg.py ? You should state like:
add_virtualhost('www.virtual.dom', 'mail.virtual.dom')


You can respond by visiting: 

More information about the Mailman-coders mailing list