Guy wrote:
>
>On 5 February 2010 20:01, Mark Sapiro wrote:
>
>> Every directory in the /var/lib/mailman/archives/private/ path must be
>> searchable by the web server. Where people normally go wrong is
>> setting g-x on /var/lib/mailman/archives/private itself without making
>> it owned by the web
Hi Mark,
On 5 February 2010 20:01, Mark Sapiro wrote:
>>1) Invitation/subscription confirmation emails go out with a link in
>>this format:
>>http://lists.domain2.net/confirm/test/526cfbe0f5e7836315ee5f17444aaae885500318
>>
>>lists.domain2.net is a virtual host and listed in mm_cfg.py.
>>
>>Is t
Guy wrote:
>
>I've got just 2 more problems left (I hope).
>
>1) Invitation/subscription confirmation emails go out with a link in
>this format:
>http://lists.domain2.net/confirm/test/526cfbe0f5e7836315ee5f17444aaae885500318
>
>lists.domain2.net is a virtual host and listed in mm_cfg.py.
>
>Is thi
On 5 February 2010 18:27, Mark Sapiro wrote:
> With (name, 5,0,5) and the others (name, 5,3,5) and (name, 5,4,5), the
> queues are partitioned into 5 slices and only slices 0, 3 and 4 are
> being processed leaving 40% of the messages waiting in the in/ queue.
Changed to the suggested 3,0,3-3,2,3
Guy wrote:
>
>I've managed to set up Mailman now (thanks Igor and Mark for all the
>help) clustered and with the vhost patch. But I'm having an odd
>problem. I'm not seeing a pattern to this, but some messages go
>through Postfix and are delivered to mailman and then nothing. Nothing
>in the Mailma
Hi,
I've managed to set up Mailman now (thanks Igor and Mark for all the
help) clustered and with the vhost patch. But I'm having an odd
problem. I'm not seeing a pattern to this, but some messages go
through Postfix and are delivered to mailman and then nothing. Nothing
in the Mailman logs and th
