Thanks, but that's all done. The problem is that the old lists want one
userid and group, any new lists want a different one. I can't figure out
why Postfix gets the error in the one case, but not the other.
That isn't a postfix problem, that's mailman complaining. Just use your
new id's and
On Sun, 2003-04-06 at 19:36, Todd Green wrote:
I do not believe this is the case. Postfix will execute commands via the
uid specified by postconf default_privs which is set to nobody if you
don't change it. However the mailman script is setgid, so it will run with
an effective group of
I recently moved a couple of lists to a new machine, also upgrading from a
2.1 beta to the final. I copied the entire Mailman directory structure from
the old to the new machine, then installed 2.1. I also switched from
Sendmail to Postfix. Now I seem to have a Catch-22 with regard to user ids.
My old lists are running okay. However, any new list I create has a user
id
problem with Postfix -- I get the Mailman expected the mail wrapper
script
to be executed as group... error when posting to a new list. If I
re-install, using the group name it expects for the new lists, then the
new
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf
...
Postfix should only need to access your mailman auto-generated
aliases. So
we have a userid and group dedicated for mailman (and the http
server), then
just add the userid for postfix to the mailman
