And I have now upgraded Mailman again to 2.1.13 and reapplied the
auto-approval patch, however I am not sure whether I need to do anything
with version numbers.
The short answer is you need to run config_list with the
"mlist.data_version = 96" input on only those lists which you created
with Ma
Hi,
I thought other listadmins might be having fun with gmail now being
available in the UK (rather than "googlemail", as it has been for a
while (despite 'gmail' originally being available, back in the days of
invitation only)), and thought I'd share my hackish way around this,
so listfolks can p
Adam Nielsen wrote:
>
>>> Also, rather than incrementing Version.DATA_FILE_VERSION further and
>>> setting yourself up for this kind of problem again, you could leave it
>>> at 97 and run the following (after applying the auto approval patch)
>>> to make sure all lists get updated
>>>
>>> #!/bin/sh
Tanstaafl wrote:
>
>Now, the path is correct, but there is no mailman directory in the
>htdocs folder, so the warning is correct - and, to make matters worse, I
>*do* have this path explicitly set in the
>/etc/apache2/vhosts.d/lists.example.com config file, although I'm not
>sure why now.
And thi
Hi all,
Late last year I upgraded Mailman and re-applied the auto-approval patch:
It has been implemented on the 2.2 branch which is not yet released, so
yes, you need to apply the patch to 2.1.12 if you need the
functionality.
Also, rather than incrementing Version.DATA_FILE_VERSION further a
-Original Message-
> Anyway, here's the warning/error:
> Warning: DocumentRoot [/var/www/localhost/htdocs/mailman] does not
exist
^
> apache2: Could not reliably determine the servers fully qualified
domain
> name, using ###.###.###.### for Serve
Hello again,
There's another annoying warning message I get that I'd like to resolve,
but I only get it at startup, so I keep forgetting about it. I had to
shutdown the server this morning to move it to a new UPS, and saw it
again when I started the server up, so now I'm asking. I know there's
som
