Lucio Chiappetti wrote:
The other question is that if I send a message to a list, the member receive it, but the message is NOT archived.
I see that a file appears in qfiles/shunt/
Have you run Mailman's bin/check_perms?
yes I did. As a result of the first run, as instructed in manual, I did
cd /var/lib/mailman/archives/ chown wwwrun private chmod o-x privateand re-run it again. (wwwrun is the suse user under which apache runs)
While the above changes result in the most secure configuration, they are only necessary (as opposed to o+x) if you have a multi-user system and you are concerned about local users being able to access private archives.
I see now that the default configuration of the list is archive=yes archive_private=public.
I see there are directories archive/private/listname, archive/private/listname.mbox and public/listname. The latter is a softlink to private. Is this normal ?
Yes, this is exactly as it should be. archives/private/listname.mbox contains a single file archives/private/listname.mbox/listname.mbox which is a unix mbox containing all archived posts to the list and which can be used as input to bin/arch to rebuild the pipermail archive which is in archives/private/listname/.
The symlinks in archives/public/ exist only for lists with public archives and are used by the web server to serve public archive pages without authentication. These are maintained automatically by Mailman as the list archives are changed from public to private or vice versa.
The actual archive is always in archives/private.
All of them are setgid directories owned by wwwrun.mailman except for those of list mailman which are owned by root.mailman, but I guess such list is special, and will have no traffic to be archived.
The owner doesn't matter. Only the group. The 'mailman' list is not special in this case and can have archives. The ownership difference is because the mailman list was created with bin/newlist (by root) whereas the others were created by the web CGI.
As a result of posting the first message to the list, a file listname.mbox is created in archive/private/listname.mbox (why private ?) and it contain the messages. But the index.html is not updated. A message is shunted, and the attached errors are generated.
The HTML is not updated because the exception occurs after the listname.mbox file is (created and) written, but before the HTML archive is updated.
The underlying problem is the same Mailman 2.1.11/Python2.6.5 incompatibility I mentioned in the 'bug adding user, and archiving gets "shunted"' thread.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan