There is one unresolved List however.
One particular List has a public archive. All attempts to access the archive via the web gives me "403 Forbidden. You don't have permission to access this resource"
When I flip the archiving to "private", it works fine ... they become accessible via admin interface. Going back to the original setting (Public) makes the archives inaccessible again.
What could be wrong?
Regards Onyeibo
On Fri, 30 Oct 2020 13:22:37 +0100 "Onyeibo Oku" <onyeibo@schemefusion.com> wrote:
Hi Mark,
On Thu Oct 29, 2020 at 5:14 PM WAT, Mark Sapiro wrote:
On 10/29/20 3:00 AM, Onyeibo Oku wrote:
check_perms should make them right. The important thing is group permissions on files should be
rwand directoriesrwsand the group should be Mailman's group. If check_perms says things are OK and there are still permission errors, it is probably a SELinux or apparmor issue.Basically, the first step is to install Mailman and get it working on the new server. Once you have a working Mailman installation on the new server, for each list you want to move, create the /var/lib/mailman/LISTNAME directory on the new server and move the /var/lib/mailman/LISTNAME/config.pck file to it. That should be all you need to move the list. For archives, create the /var/lib/mailman/archives/private/LISTNAME.mbox directory and move the /var/lib/mailman/archives/private/LISTNAME.mbox/LISTNAME.mbox file. Then run
bin/arch --wipe LISTNAMEas the mailman user to rebuild the pipermail archive.It worked! It worked! Thank you so very much.
Regards Onyeibo
Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-leave@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/