Question #249403 on mailman in Ubuntu changed:
https://answers.launchpad.net/ubuntu/+source/mailman/+question/249403

Mark Sapiro proposed the following answer:
Yes, check Mailman's error log, and run Mailman's bin/check_perms.

Also, the actual archive is always in Mailman's
archives/private/LISTNAME/ directory and archives/public/LISTNAME should
be a symlink to archives/private/LISTNAME/. if archives/public/LISTNAME
is an actual directory with and index.html file and possibly others, it
can cause this. If you go to the archive via a URL like
http://example.com/mailman/private/LISTNAME, and log in and see the
archived messages, this is the problem. If this is the issue, you can
fix it by removing the archives/public/LISTNAME directory and letting
Mailman recreate the symlink. If you don't have access to do that, you
could try switching the archive to private and then back to public which
may or may not help. If not, you'll have to work with the server admins.

-- 
You received this question notification because you are a member of
Mailman Coders, which is an answer contact for mailman in Ubuntu.
_______________________________________________
Mailman-coders mailing list
[email protected]
https://mail.python.org/mailman/listinfo/mailman-coders

Reply via email to