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
I'm running Mailman 2.1.1 on Mac OS X Server. My lists are primarily
English, but a few of them are also in French and even the English ones
sometimes have French accented characters. As a result, I would like
Mailman to encode all messages as ISO-8859-1.
Here's my problem:
A few users
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
Hi,
Any help with the following would be greatly appreciated:
I'm trying to install Mailman 2.1.1
My python executable is in /usr/local/bin/python
I have configured with parameters: ./configure --prefix=/sw/mailman/2.1.1
--with-mail-gid=mail --with-cgi-gid=www
I am using solaris
Hi,
I've recently put mailman on-line, after a week or so of testing.
I like the product alot.
This is now my first day of administering the environment from a remote
location, and I realised SSL isn't being used when entering my list admin
password.
How can I force SSL (https) connectivity
On Fri, 2003-04-04 at 22:00, Leonardo Sá wrote:
I've checked the apache configuration and it seems to be ok (otherwise, the
other lists would not be working). Rebuilding the list from scratch also
didn't work, and i do have 401mb ram that i think is enough for this kind of
job. Only
A follow-up to my earlier post re: Text encoding issue
I forgot to mention that I have content-filtering configured to strip
text/html to text/plain. However, on most lists other attachments types
(i.e. .doc, .pdf, etc.) are not prohibited.
I did an impromptu test with a small developer list
