Brian Wilson wrote:
>>First off, thanks for you and Igor for putting together and doing the legwork on getting the vhost patch working on 2.1.13. I've been wanting to migrate my lists away from my hosting provider and roll my own mailman install again, but was waiting on 3.0. Glad this will keep me happy in the interim.
>>There are a few things I noticed on my install today (Debian w/ Postfix).
>>1) rmlist doesnt work properly:
>># rmlist -a test at lists.example.com>test at lists.example.com list info not found as /var/lib/mailman/lists/test at lists.example.com>test at lists.example.com private archives not found as /var/lib/mailman/archives/private/test at lists.example.com>test at lists.example.com private archives not found as /var/lib/mailman/archives/private/test at lists.example.com.mbox>test at lists.example.com public archives not found as /var/lib/mailman/archives/public/test at lists.example.com>test at lists.example.com public archives not found as /var/lib/mailman/archives/public/test at lists.example.com.mbox>># rmlist test at lists.example.com>Not removing archives. Reinvoke with -a to remove them.
>test at lists.example.com list info not found as /var/lib/mailman/lists/test at lists.example.com
This does not surprise me. There are reasons why these patches aren't
applied upstream. Everyone whose done this has only done the parts
they're interested in. No on has done a complete job.
My recent work on this was only to adress Igor's specific issues. I
have my own vhost branch, and I'll see about fixing this (if it's
easy) and publishing the branch on Launchpad. However, it was never my
intent to make this wart free, and I don't want to get sucked in to
fixing bugs in code that has been entirely superceded in Mailman 3.
>2) Web locations are off...
>>If i go to archives for a list: http://lists.example.com/pipermail/lists.example.com/test/, the html link that links to listinfo uses DEFAULT_URL_HOST instead of the urlhost for the list I'm on (link goes to http://DEFAULT_URL_HOST/mailman/listinfo/test). I tried adjusting the templates (in templates/en/emptyarchive.html) to remedy this, but couldn't tell that the pages were changing when I adjusted the templates as the info didn't change on the website.
I see that is a problem in my vhost test system too. I'll see about
this too.
>I'm using this as my Apache config which should handle all "lists.domain.tld" type domains. I don't think this is what is causing the web locations to be off, but I'm not sure.
>><VirtualHost *:80>
> ServerName lists.example.com
> ServerAlias lists.*
>> RedirectMatch permanent ^/$ /mailman/listinfo
>> RewriteCond %{REQUEST_URI} !^/pipermail/lists\.(.*)?$ [NC]
> RewriteRule ^/pipermail/(.*)$ /pipermail/%{SERVER_NAME}/$1 [R=301,L]
> RewriteCond %{REQUEST_URI} !^/private/(.*)@(.*)?$ [NC]
> RewriteRule ^/private/(.*)/$ /private/$1@%{server_name} [R=301,L]
>> RewriteEngine on
> RewriteRule ^/mailman(/.*)?$ /cgi-bin/mailman$1 [PT,L]
></VirtualHost>
I'm sure I fixed this so there is no need for rewrite rules for
pipermail or private archives.
Also, depending on what you're trying to accomplish, the
RewriteRule ^/mailman(/.*)?$ /cgi-bin/mailman$1 [PT,L]
should probably be eliminated by putting
DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/'
in mm_cfg.py or adjusting Mailman's ScriptAlias in Apache.
>I don't have any live lists on my system, so I'll be glad to test whatever suggestions you might have. I did confirm that delivery works as it should with postfix by only adding the aliases map, virtual-mailman map and adding each "lists.domain.tld" to virtual_alias_domains.
I'll see what I come up with.
--
Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan