I'm afraid it doesn't - here's an example: [root@unica mailman]# ls -lR lists/|grep config.db -rw-rw---- 1 nobody mail 9759 May 9 14:14 config.db -rw-rw---- 1 nobody mail 9759 May 9 14:14 config.db.last -rw-rw---- 1 mailman mail 16876 May 9 15:27 config.db -rw-rw---- 1 mailman mail 16876 May 9 15:26 config.db.last -rw-rw---- 1 mailman mail 2865 May 3 04:03 config.db -rw-rw---- 1 mailman mail 2865 May 3 04:03 config.db.last -rw-rw---- 1 mailman mail 3775 May 9 12:00 config.db -rw-rw---- 1 mailman mail 3775 May 8 17:00 config.db.last -rw-rw---- 1 mailman mail 5123 May 9 14:08 config.db -rw-rw---- 1 mailman mail 5123 May 9 14:08 config.db.last -rw-rw---- 1 mailman mail 3149 May 9 12:00 config.db -rw-rw---- 1 mailman mail 3149 May 8 17:00 config.db.last [root@unica mailman]# ./bin/check_perms /home/mailman/archives/private/notopic/index.html bad gid (has: mailman, expected mail) /home/mailman/archives/private/distrib/index.html bad gid (has: mailman, expected mail) Problems found: 2 It sounds as though the check_perms script would have found all of these in error.. ? <EOL> Tib On Wed, 9 May 2001, Dan Mick wrote: > Apparently you didn't read what I said. > > > -rw-rw---- 1 nobody mail 16875 May 8 18:16 > > /home/mailman/lists/thelist/config.db > > is not group mailman. That would be the problem, and I have to believe > that check_perms would find it, too. > > > > The web server writes it. This is not a problem, because it's owned > > > by group mailman, and write permissions are granted to group mailman. > > > ------------------------------------------------------ > Mailman-Users maillist - [EMAIL PROTECTED] > http://mail.python.org/mailman/listinfo/mailman-users > ------------------------------------------------------ Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users