Roy Vinner
>
>So, after I've set the -with-cgi-gid=apache and
>--with-mail-gid=mailman and rerun configure, will I need also to
>re-run make and make install? That will be a job for tomorrow...
Yes.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, C
Mark Sapiro wrote:
> roy vinner wrote:
>
>>I created a group www -- which included apache, mailman, and myself --
>>and set -cgi-gid=www.
>>The apache would not run the mailman/create, as it was complaining that
>>it could not run as www (even though apache was included in ). So I
>>set -cg
roy vinner wrote:
>
>I created a group www -- which included apache, mailman, and myself --
>and set -cgi-gid=www.
>The apache would not run the mailman/create, as it was complaining that
>it could not run as www (even though apache was included in ). So I
>set -cgi-gid=mailman and set user
Mark Sapiro wrote:
> roy vinner
>
>
>>Mark Sapiro wrote:
>>
>>
>>>Running this from the command line is not necessarily a valid test. The
>>>wrapper (/usr/local/mailman/mail/mailman) exects to be run by the MTA
>>>with the group that was configured by ./configure. This is almost
>>>always not t
On 7/28/05 4:13 PM, "Mark Sapiro" <[EMAIL PROTECTED]> wrote:
> Does this setting change whether or
>> not postfix runs chrooted or not?
Well, the option probably doesn't change, but the locations of lots of
things do change. For starters, if chrooted, Postfix couldn't find the
wrapped CGI unless
roy vinner
>Mark Sapiro wrote:
>
>> Running this from the command line is not necessarily a valid test. The
>> wrapper (/usr/local/mailman/mail/mailman) exects to be run by the MTA
>> with the group that was configured by ./configure. This is almost
>> always not the 'mailman' group. See
>> http:
Mark Sapiro wrote:
<...>
>>[EMAIL PROTECTED] mailman-2.1.6]$ /usr/local/mailman/mail/mailman request try
>>Failure to find group name mailman. Try adding this group
>>to your system, or re-run configure, providing an
>>existing group name with the command line option --with-mail-gid.
>
>
>
> R
roy vinner wrote:
>
>I've also discovered that if I run an alias expansion from the command line
>
>aliases:
>..
># STANZA START: try
># CREATED: Mon Jul 25 17:19:03 2005
>try: "|/usr/local/mailman/mail/mailman post try"
>try-admin: "|/u
Hi Jan,
Jan Kohnert wrote:
<...>
>>[EMAIL PROTECTED] mailman-2.1.6]$ /usr/local/mailman/mail/mailman request try
>>Failure to find group name mailman. Try adding this group
>>to your system, or re-run configure, providing an
>>existing group name with the command line option --with-mail-gid.
>
Hi John,
I appreciate your quick response!
John Dennis wrote:
> On Thu, 2005-07-28 at 16:28 -0500, roy vinner wrote:
>
>>Greetings!
>>
>>I have a problem that any address which is supposed to be resolved with
>>the path-to-mailman/data/aliases produces a "message undeliverable" error.
>>
>>I've
roy vinner schrieb:
> Greetings!
Hello,
> [EMAIL PROTECTED] mailman-2.1.6]$ /usr/local/mailman/mail/mailman request try
> Failure to find group name mailman. Try adding this group
> to your system, or re-run configure, providing an
> existing group name with the command line option --with-mail-g
On Thu, 2005-07-28 at 16:28 -0500, roy vinner wrote:
> Greetings!
>
> I have a problem that any address which is supposed to be resolved with
> the path-to-mailman/data/aliases produces a "message undeliverable" error.
>
> I've also discovered that if I run an alias expansion from the command lin
Greetings!
I have a problem that any address which is supposed to be resolved with
the path-to-mailman/data/aliases produces a "message undeliverable" error.
I've also discovered that if I run an alias expansion from the command line
aliases:
..
# STAN
13 matches
Mail list logo