David Newman wrote:
>
>Thanks, Mark. Adding '-u hostname' did the trick.
>
>I'd suggest adding this to the FAQ, which currently does not mention the
>-u switch:
>
>http://wiki.list.org/display/DOC/4.27+Securing+Mailman%27s+web+GUI+by+using+Secure+HTTP-SSL
I have updated the FAQ. Thank you.
--
M
On 2/19/11 6:57 AM, Mark Sapiro wrote:
> David Newman wrote:
>>
>> With the mm.cfg config pasted below, clicking the archives link on a
>> list page for lists.domain2.tld redirects to
>>
>> https://mail.domain1.tld/pipermail/listname
>>
>> which fails because the list name is associated with doma
David Newman wrote:
>
>With the mm.cfg config pasted below, clicking the archives link on a
>list page for lists.domain2.tld redirects to
>
>https://mail.domain1.tld/pipermail/listname
>
>which fails because the list name is associated with domain2.tld and not
>domain1.tld.
Do you mean the link p
How to configure Mailman to handle https redirects to public archives
for virtual domains?
This is for a server with a canonical name of mail.domain1.tld, and
virtual names of lists.domain2.tld, lists.domain3.tld, etc.
With the mm.cfg config pasted below, clicking the archives link on a
list page
