Check_perms fails to find it, and it's turning into a major problem. What (exactly) writes and rewrites the config.db file and what are the actual permissions it's supposed to have? From ealier reference it sounded as though it should be owned by nobody (since the webserver modifies/creates/backs-up/etc) and the group should be mailman. Ok - I can deal with this - but after manually setting the ownership to be just that - this is what I get after waiting a while and checking again: [root@unica mailman]# ls -lR lists/|grep config.db -rw-rw---- 1 nobody mailman 9759 May 9 14:14 config.db -rw-rw---- 1 nobody mailman 9759 May 9 14:14 config.db.last -rw-rw---- 1 nobody mailman 16876 May 9 15:27 config.db -rw-rw---- 1 nobody mailman 16876 May 9 15:26 config.db.last -rw-rw---- 1 nobody mailman 2865 May 3 04:03 config.db -rw-rw---- 1 nobody mailman 2865 May 3 04:03 config.db.last -rw-rw---- 1 nobody mailman 3775 May 9 12:00 config.db -rw-rw---- 1 nobody mailman 3775 May 8 17:00 config.db.last -rw-rw---- 1 nobody mailman 5123 May 9 14:08 config.db -rw-rw---- 1 nobody mailman 5123 May 9 14:08 config.db.last -rw-rw---- 1 nobody mailman 3149 May 9 12:00 config.db -rw-rw---- 1 nobody mailman 3149 May 8 17:00 config.db.last [root@unica mailman]# ls -lR lists/|grep config.db -rw-rw---- 1 mailman mail 9759 May 9 17:00 config.db -rw-rw---- 1 nobody mailman 9759 May 9 14:14 config.db.last -rw-rw---- 1 mailman mail 16876 May 9 17:00 config.db -rw-rw---- 1 nobody mailman 16876 May 9 15:27 config.db.last -rw-rw---- 1 nobody mailman 2865 May 3 04:03 config.db -rw-rw---- 1 nobody mailman 2865 May 3 04:03 config.db.last -rw-rw---- 1 mailman mail 3775 May 9 17:00 config.db -rw-rw---- 1 nobody mailman 3775 May 9 12:00 config.db.last -rw-rw---- 1 mailman mail 5123 May 9 17:00 config.db -rw-rw---- 1 nobody mailman 5123 May 9 14:08 config.db.last -rw-rw---- 1 mailman mail 3149 May 9 17:00 config.db -rw-rw---- 1 nobody mailman 3149 May 9 12:00 config.db.last As you can see - the ones that get modified have their permissions changed to 'mailman:mail' and I've seen further changes where it becomes 'nobody:mail' and then mailman starts spitting errors out right and left and the lists just queue up messages and don't do anything anymore. Could someone please explain in detail exactly how it's /supposed/ to happen in a good situation? <EOL> Tib ------------------------------------------------------ Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
