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
Olivier Michel wrote:
>
>I keep receiving from a list called MYLIST a moderator request for a
>waiting message that should be considered (all traffic is moderated on
>that list) while actually there is no such message to be moderated. I
>looked through the FAQ of Mailman, through the pending queues
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
Hi,
I keep receiving from a list called MYLIST a moderator request for a
waiting message that should be considered (all traffic is moderated on
that list) while actually there is no such message to be moderated. I
looked through the FAQ of Mailman, through the pending queues and the
postfix sendin
