[Mailman-Users] Mailman 2.1b2 installed and working (almost).

[Rob Brandt]

More insight to this problem:

It's permissions in aliases.db, as the httpd error log tells me. 
I've proved that to be true by setting the permissions for aliases.db 
to be read/write for all users, and it now works.  I'm certain that's 
*not* really what I want, but I'm not sure what the permissions 
*should* be' i.e., which user and group.  They are currently 
u=mailman, g=mailman.  I did try changing user to root just to see 
what would happen, but it didn't help the list creation and it 
prevented mail from being sent through the lists because of a script 
error.

Another problem.  The domain used to access the archives seems to 
always use the value found in DEFAULT_URL_HOST in mm_cfg.py.  It 
should use the same domain as is on the link page, or at least in the 
preferred host field.  It looks funny to start at one domain and end 
up at another.  Or do I not have something set right?

Rob

At 11:06 AM -0400 5/24/2002, Jon Parise wrote:
>On Thu, May 23, 2002 at 11:29:18PM -0700, Rob Brandt wrote:
>
>>  I've gotten Mailman 2.1b2 installed on my new linux server.  It's using
>>  Postfix as an MTA.  I can create lists, but an error is generated.  The
>>  list does exists, and I can edit it and everything.  But it seems that
>>  there's a problem with creating aliases for it.  See the error page pasted
>>  in below.
>>
>>  I suspect that it's a permissions problem, but at this late time of night,
>>  I can no longer see the forest for the trees.  Initially I did get in the
>>  infamous 'wanted uid 99, got 48' error.  Miraculously, I remember getting
>>  that when I installed v2.05 last summer, and the solution to run apache as
>>  uid/gid nobody.  Here's the error page:
>
>[snip]
>
>>  RuntimeError: command failed: /usr/sbin/postalias
>>  /usr/local/mailman/data/aliases (status: 1, Operation not permitted)
>
>Is /usr/sbin/postalias the correct path to postalias?  How are the
>permissions set for /usr/local/mailman/data/aliases?
>
>I have virtually the same setup working fine here, so it's probably
>just a permissions mismatch, as you say.
>
>--
>Jon Parise (jon at csh.rit.edu)  .  Information Technology (2001)
>http://www.csh.rit.edu/~jon/  :  Computer Science House Member


--