Mark Sapiro writes:
> The safe thing is for 'you' to not have write permission on the mbox. If
> you did have in the past, this may be how the group was changed.
Quite likely.
Basically, there are two ways to change the content of a file on
Unix-like systems. One way is to write-lock (at leas
On 06/16/2015 09:38 AM, Lucio Chiappetti wrote:
> On Tue, 16 Jun 2015, Mark Sapiro wrote:
>> Just fix the permissions and run Mailman's bin/unshunt ...
>
> GREAT ! Thanks a lot !
> I recovered all the backlog !
Good!
> I cannot trace how they were (systematically for 3 lists) set to the
> wro
On Tue, 16 Jun 2015, Mark Sapiro wrote:
2) apparently since the wrong permission were setup, archiving stopped
to work. Is there a way to rebuild the archives from messages stored
in personal folders (I am not sure I have all of them though !)
Just fix the permissions and run Mailman's b
On 06/16/2015 02:17 AM, Lucio Chiappetti wrote:
> I am running a few mailing lists with private archive on my machine.
> I see that /var/lib/mailman/archives/private/ contains two directories
> per list one named "listname" and the other one "listname.mbox".
>
> Owned by wwwrun.mailman, permission
I am running a few mailing lists with private archive on my machine.
I see that /var/lib/mailman/archives/private/ contains two directories
per list one named "listname" and the other one "listname.mbox".
Owned by wwwrun.mailman, permissions drwxrwsr-x
The listname directory contains one index.h
