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 bin/unshunt ...
GREAT ! Thanks a lot !
I recovered all the backlog !
I suspect this may be due to the fact a while ago I created some soft
links from my own ~/.mail directory e.g. fitsconv.mbox ->
/var/lib/mailman/archives/private/fitsconv.mbox/fitsconv.mbox
(the links are owned by me and have lrwxrwxrwx)
Actually I had already reset the permissions for the archive folders (I
simply enabled archive for a test list to see the fresh permission, and
applied them to the old folders). This enabled archiving of new messages.
But I was missing the "shunt" piece.
Additional symlinks to the file are irrelevant unless you are writing to
it (you shouldn't be) and changing its group.
I cannot trace how they were (systematically for 3 lists) set to the wrong
way. Now my alpine mail client enters the folders and sees them in
READONLY mode (which is good), and refuses to delete messages (which is
also good). If I enter a message flagged new (unread), it will set its
flag to "read" ... maybe this is what mislead me ... but this is obviously
an internal memory flag of the client. If I exit and re-enter the folder,
I see the original status. Which for me is fine.
Going back to digest mode ...
------------------------------------------------------
Mailman-Users mailing list [email protected]
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org