As I had begun to suspect, this had nothing to do with Mailman. I imported MySQL records from the old server for authenticating mail users and assigning virtual mailboxes. All of these contained numeric GID records appropriate for that installation, and the mail server indeed ran with that GID when communication with Mailman. A single MySQL command corrected this for 260 mailboxes and alias accounts and all is well!
My scripts which created _new_ records in this db set the proper GID out of the chute. .linuxmint.com/start/lisa/On Mon, 2012-08-27 at 10:32 -0500, Lindsay Haisley wrote: > I've looked into the pickled files for the problem list with dumpdb and > found no reference to the GID which might lock the "mail wrapper script" > onto the group ID of the server from which the list was exported. > Googling for "mail wrapper script" turns up lots of references, going > back many years, to the problem of an improperly set --with-mail-gid at > configure time, however this isn't the case here, since this was > properly set on the new server, and the problem occurs only with a list > imported from the old server where the numeric GID was different from > that of the "mail" group on the new server. > > check_perms returns "No problems found". > > What is the "mail wrapper script" to which the error message refers? -- Lindsay Haisley | "The only unchanging certainty FMP Computer Services | is the certainty of change" 512-259-1190 | http://www.fmp.com | - Ancient wisdom, all cultures ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
