Jeffrey Goldberg wrote:
>
>To my knowledge, the one place that a list administrator could by-
>pass the confirmation process for members is on the mass subscription
>page. Are there other locations as well?
The only other way I can think of offhand is to set subscribe_policy to
'Require appro
Brad Knowles wrote:
>
>However, even if the users are directly subscribed and without
>confirmation, they'll still be issued passwords and those passwords
>will be sent out to them on a monthly basis, so that they have the
>ability to log into a web site on your server and manage their
>subscri
On 8/22/07, Nicoll, Alan wrote:
> 1. We don't want any 'list owners' or 'moderators'. Just we lucky few
> admins will run the lists.
Then use a single central alias or mailing list as the list owner for
each of those lists, and have that be directed to your admins. For
one site I help admi
Hello,
I'm a site administrator running mailman 2.1.9 and am beginning to
delegate some responsibility to list administrators. While I trust
(the integrity of) these people, I am not fully confident that they
completely grasp the importance of the confirmation process
(particularly since
Nicoll, Alan wrote:
>
>We are migrating about 300 lists from majordomo to mailman and would like
>some help finding how to setup a few properties. We've worked at this a
>while and been unable to find where/how to set these. (See below for
>background.)
>
>
>
>1. We don't want any 'list owners'
We are migrating about 300 lists from majordomo to mailman and would like
some help finding how to setup a few properties. We've worked at this a
while and been unable to find where/how to set these. (See below for
background.)
1. We don't want any 'list owners' or 'moderators'. Just we luc
Mark Sapiro wrote:
>
>bin/arch --wipe -e 9 list1
Ooops! That should be
bin/arch --wipe -e list1
>bin/arch -s 1 -e 1 list1
>bin/arch -s 2 -e 2 list1
>...
>bin/arch -s 6 list1
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay A
Bob wrote:
>
>Everything was going along fine, with daily updates being added to the
>archive. I then wanted to refresh the entire archive and ran bin/arch
>--wipe list1
>
>it failed.
>
>Archive articles go from to 66990
>
>list1.mbox is: 526313754 Aug 21 20:19 list1.mbox
>
>The server NetBS
Barry Finkel ha scritto:
>> [...]
>
>> The patches were, for the most part,
>>> undocumented, so I had no idea exactly what they did. Nor did I know
>>> if they would fit into the 2.1.9 source, as some of the patches were
>>> based on pre-2.1.5 code.
>>
>> Manlio Perillo replied:
>>> This was une
Hi:
I am having a problem regenerating my archive.
Everything was going along fine, with daily updates being added to the
archive. I then wanted to refresh the entire archive and ran bin/arch
--wipe list1
it failed.
Archive articles go from to 66990
list1.mbox is: 526313754 Aug 21 20:1
10 matches
Mail list logo
