Chris Haumesser writes:
> I was assuming the .keep folder had something to do with mailman
> internals.
That looks like a distro device to make sure that the data
directories don't get deleted if you delete the package.
Possibly what is happening is that the distro's version is patched to
ign
On 4/22/11 7:52 AM, Mark Sapiro wrote:
If there are or were any config.db* files, they were left after
migration from Mailman 2.0.x to 2.1.x and contained old data from
before the migration.
There are no config.db files in /var/lib/mailman, they are only
mentioned in the log.
The above seem
Chris Haumesser wrote:
>My filesystem recently crashed, breaking some aspects of my mailman
>installation.
>
>The email portion of the list itself is still functioning (for
>non-digest subscribers), and all the archives are intact. But I seem to
>be missing some config pickles that are preventi
My filesystem recently crashed, breaking some aspects of my mailman
installation.
The email portion of the list itself is still functioning (for
non-digest subscribers), and all the archives are intact. But I seem to
be missing some config pickles that are preventing digest delivery,
emergenc
On Thu, Apr 21, 2011 at 3:02 PM, Mark Sapiro wrote:
> Ognen Duzlevski wrote:
> >
> >I have not played much with mailman but I am curious about something. I
> >inherited a machine that runs mailman and one of the lists is setup
> through
> >postfix aliases to do the following:
> >
> >blah-subscrib
On Thu, 21 Apr 2011, Mark Sapiro wrote:
Ognen Duzlevski wrote:
How do I find out what "mailman join blah" resolves to? I guess my
question is ultimately - where do I look to find out who gets the join
and subscribe requests?
The MTA processes that ...
I guess the OP did not want to know h
