I was looking today at /var/lib/mailman/lists and happened to notice
the owner seems to vary. It appears that some older lists are owner by
mailman:mailman and lists that I have recently created are owner by
root:mailman.
Here is what I see on my server:
drwxrwsr-x 2 rootmailman 4096 Jun 13
Carlos Williams wrote:
I was looking today at /var/lib/mailman/lists and happened to notice
the owner seems to vary. It appears that some older lists are owner by
mailman:mailman and lists that I have recently created are owner by
root:mailman.
snip
Now I know all the lists I create are done in
washakie wrote:
Then I have a rc file in /etc/procmailrc and the filter seems to work,
however, it isn't setting the correct 'privileges'. The rc file is owned by
the user=listname and here is the contents:
[EMAIL PROTECTED] ll /etc/procmailrcs/listname.procmailrc
-rw-r--r-- 1 listname root 468
Mark Sapiro-3 wrote:
Procmail doesn't like something about
/etc/procmailrcs/listname.procmailrc. I'm only guessing, but try
removing world read and making the group other than root.
Also see http://wiki.list.org/x/tYA9 because if listname's group is
not the --with-mail-gid group
Jens Meyer wrote:
Our postfix-mailserver hosts several domains (virtual mailhosting,
postfix/mysql) and mailman.
The primary domain myserver.de is a virtualized domain also. So this
domain is not listed in mydestination:
--
myhostname = mail.myserver.de
mydomain = myserver.de
myorigin =
washakie wrote:
Thanks. How do I determine what --with-mail-gid is set? I assume it's
mailman, as that is the default correct?
It appears from clues in your previous posts that your MTA is Postfix.
If this is the case, the 'mail group' is the group of the owner of
Mailman's data/aliases.db.
In
I am moving mailman from one server to another server (not changing
the domain) and noticed the instructions here:
http://mail.python.org/pipermail/mailman-users/2007-January/055208.html
The instructions show to make sure you copy both the contents of
/var/lib/mailman/lists to the new server and
Mark Sapiro-3 wrote:
In any case, if you ran configure, or if your packager was kind enough
to provide you with the package's config.log, you'll find the
configure options there. If all else fails, the expected group is in
the error message from the wrapper if you get it wrong (you can
Carlos Williams sent the message below at 11:53 6/13/2008:
I am moving mailman from one server to another server (not changing
the domain) and noticed the instructions here:
http://mail.python.org/pipermail/mailman-users/2007-January/055208.html
The instructions show to make sure you copy both
Hello, I've been trying to deal with a procmail/Mailman issue:
http://www.nabble.com/procmail-before-mailman-td17789754.html
But this is a separate question. I want to temporarily disable Mailman for
the list, to see if I can get procmail to work directly in the user home
directory, rather than
Carlos Williams wrote:
My question is when looking at /var/lib/mailman/archives/private/ I
notice that there are several old and deleted or no longer functioning
lists in this directory. Is there nothing that cleans up this path
when you create a test list and then remove it using the script
washakie wrote:
Thanks. It appears:
Group mismatch error. Mailman expected the mail wrapper script to be
executed as one of the following groups:
[mail, postfix, mailman, nobody, daemon],
but the system's mail server executed the mail script as group: users.
Try tweaking the mail server to run
washakie wrote:
Is there a way to 'shutdown' a list temporarily so that I can be assured
Mailman is not interefering at all with the mail delivery?
Mailman's 'bin/mailmanctl stop' or 'service mailman stop' will stop
Mailman's qrunners so Mailman will not process or send any mail, but
Mailman
13 matches
Mail list logo
