> Before you commit too heavily to this, I suggest you look at the first
> 570+ lines at
> <http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/annotate/head%3A/NEWS>
> and see if you really want to be installing a 4 year old release.
The only reason i chose 2.1.7 is because the patch applied cleanly, but i guess
you are right.
I just sat down and applied the patch to the 2.1.13 source. There few few
rejects, but I went through
all of them and it looks like that code that already made it upstream and
included in 2.1.13.
Compiled and installed it, but for the life of me i cant create a new list for
a virtual domain.
bin/newlist -u lists.domain1.net [email protected]
and end up with
Illegal list name: [email protected]
This is very strange, because the domain already exists in mm_cfg.py and the
patch applied cleanly to bin/newlist too.
Any idea what may be wrong?
>> put these in mm_cfg.py:
>> DEFAULT_EMAIL_HOST = 'lists.dept.university.edu'
>> DEFAULT_URL_HOST = 'lists.dept.university.edu'
>> add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>> add_virtualhost('lists.domain1.net', 'lists.domain1.net')
>> add_virtualhost('lists.domain2.net', 'lists.domain2.net')
>> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.domain1.net', 'lists.domain2.net']
>>
>>
>> RewriteCond %{REQUEST_URI} !^/pipermail/([a-z]+)\.(.*)?$ [NC]
>> RewriteRule ^/pipermail/(.*)$ /pipermail/%{SERVER_NAME}/$1 [R=301,L]
>>
>> Basically all it does is insert "lists.domainX.net" between /pipermail/ and
>> /test-list/. Public archives are now working with
>> http://lists.domain1.net/pipermail/lists.domain1.net/test-list/
>
>
> So you can't have lists with names beginning with letters and a dot.
>
> I think a better method would be a separate Alias /pipermail/ directive
> in each VirtualHost block.
>
Right. That was a quick rule and i already realized that couple of my lists are
not gonna work with this.
There is, however, a common name convention, so i will make a better match
later.
As far as virtual hosts go, I'd like to keep configuration to a minimum. As i
mentioned on IRC, I am looking at approximately 20 separate domains and
maintaining 20 separate installations and configs is a management nightmare.
>
>> Next I tried to test Private archives and this is where I hit the wall and
>> need some help with.
>>
>> The listinfo page for my test-list showed that the URL for the private
>> archives was http://lists.domain1.net/private/test-list, so i figured i
>> would be able to fix it with the same rewrite rule that i used for the
>> Public archives.
>
>
> As I said, because I'm compulsive I will look at this in more detail
> and follow up, but probably not for a few days.
>
Thanks, Mark! I really appreciate the help.
------------------------------------------------------
Mailman-Users mailing list [email protected]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
