On Monday, August 11, 2003, at 10:31 am, Tony wrote:
Hi Tokio,
I checked out Rob's bug report and he says that he tried fix_url, but it only
worked for private archives, not for the public ones.... :(
Rob's bug report, as with yours, lack precision in specifying exactly which Mailman generated pages have links on them which contain (in the HTML text), absolute URLs referring to the wrong hostname. See my comments below on the broadfer questions that need to be answered in order to attack the perceived problem.
Thanks for the suggestion though.
Tony Quoting Tokio Kikuchi <[EMAIL PROTECTED]>:
Hi,func=detail&aid=784888&group_id=103&atid=100103
You should state your urlhost/emailhost pairs in mm_cfg.py like;
add_virtualhost('www.virtual.dom', 'mail.virtual.dom')
then use fix_url.py.
Rob Brandt wrote:
I recently submitted a bug report on that:https://sourceforge.net/tracker/?
No response yet.
Rob
Quoting [EMAIL PROTECTED]:
Hi,
I hope someone can help me with this:
I am a web space reseller on a shared server.
One of the features we get is mailman, which we offer to our clients.
One thing I have noticed about it is that if a mailing list has a has a
private archive, the address is
http://clientdomain.com/mailman/private/listname, which is fine, but if
the archive is public, then the address is
http://myhostingprovidersservername.com/pipermail/listname - which is
not fine :(
The cause of this is likely to be in the configuration of the Apache server servicing the virtual hosts concerned rather than it being a Mailman problem per se.
I'm assuming that named virtual hosting is being used by the Apache server concerned so that clientdomain.com and myhostingprovidersservername.com resolve to the same IP number.
Unless the Apache server has some special provisions made in its configuration/operation the pipermail archives, which are served as regular web pages by Apache without the intervention of Mailman specific CGI programs, will be equally visible through any of the hostnames that resolve to the same IP that myhostingprovidersservername.com resolves to. If this is the case then any of the public lists is potentially visible through any of the named virtual hosts supported by Apache on the same IP number.
I do not work with it myself, but I believe that the CPanel virtual hosting support software, which your hosting provider may be using, does perform some trickery to help avoid conflicts between list names on different virtual hosts. If your hosting provider is using that and something related to it is misconfigured then this may be contributing to the problem.
When you say "if the archive is public, then the address is http://myhostingprovidersservername.com/pipermail/listname"; what precisely do you mean?
Do the links to list archives for a given virtual host on the /mailman/listinfo and /mailman/admin and other /mailman/<somtehing> CGI generated pages for that host have URL's that refer to the myhostingprovidersservername.com rather than clientdomain.com host?
Or are there links on other pages on the server that have the 'defective' domain in their URLs?
If you look at the source of MM's pipermail archive pages you will find that for the most part the generated links on those pages are server relative, the main exception being (with MM2.1.2) to extracted attachment files. So once started on a link specifying the 'wrong' hostname, links on pages then reached also appear to be 'wrong'.
To get much further with diagnosing the problem will need a bit more input from you.
40arielbusiness.comThis means that my clients can see the domain name of the underlying
provider I am buying space off, and potentially they might jump ship.
Is this something that can be fixed by me/the hosting provider, and if
so, how?
Many thanks,
Tony
-- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
------------------------------------------------------
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
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/tony-mm%
------------------------------------------------------
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
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/ r.barrett%40openinfo.co.uk
------------------------------------------------------ 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
