On 09/18/2014 07:19 AM, James Nightly wrote:
>
> I created new lists on the new server, copy/pasted member emails and
> list settings (using config_list).
It would have been much easier and more complete to just have copied the
lists/LISTNAME/config.pck files
> There is only one set of lists,
> Since you moved servers, I suspect there are two lists and some things
> are going to/coming from the old list(s) and some are going to/coming
> from the new list(s).
> And how did you add the members to the new list(s)? config_list doesn't
> do anything with members or their passwords or options
On 09/17/2014 07:57 AM, James Nightly wrote:
>> I'm not sure why you did config_list. If you were upgrading an existing
>> install, this was unnecessary.
>
> I had to move to a different server. Sorry, I should have explained
> that a little better.
And did you notice the part in my reply to you
> I'm not sure why you did config_list. If you were upgrading an existing
> install, this was unnecessary.
I had to move to a different server. Sorry, I should have explained
that a little better.
> What is the reason (from the admindb interface or the held message
> notice or Mailman's vette lo
On 09/16/2014 03:23 PM, James Nightly wrote:
> Can MM generate some type of statistics for all the lists, e.g. number of
> messages per week, month, most frequent posters, which list has most
> traffic etc.?
It's all in Mailman's 'post' log, but beyond what's in the contrib/mmdsr
script report (i
Can MM generate some type of statistics for all the lists, e.g. number of
messages per week, month, most frequent posters, which list has most
traffic etc.?
All of our lists are setup where members can post, other (non-members) are
moderated. After updating to 2.1.18-1 and config_list -i all of t
