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 > 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. Actually, the MUA will set a Status: header in the mbox to indicate the message has been read so that the 'read' status persists across sessions, but of course this requires the MUA to have permission to write the mailbox. 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. -- Mark Sapiro <[email protected]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ 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
