Rekhesh Mohan | 1 Aug 2011 16:21
Picon
Favicon

Re: mailman on freeBSD 8.2: getgrgid error


On 01/08/2011 Odhiambo Washington wrote
> What is the output of this command on your system:
> 
> grep www /etc/group

Here is the output:

[root <at> foo ~]# grep www /etc/group
www:*:80:www
[root <at> foo ~]# 

Thanks! 

--R

> 
> On Sun, Jul 31, 2011 at 23:27, Rekhesh Mohan <reks <at> iiap.res.in> wrote:
> > Hi folks,
> > I've been fiddling with mailman 2.1.14 (from freebsd ports) on free
> > BSD 8.2. Everything seems to be fine so far except for the web
> > based stuff. I get the following error when I try to access the
> > page:
> > 
> > http://this.great.site/mailman/listinfo
> > 
> > -------<error>--------
> > Mailman CGI error!!!
> > 
> > The Mailman CGI wrapper encountered a fatal error. This entry is
(Continue reading)

Mark Sapiro | 1 Aug 2011 17:01
Favicon

Re: mailman on freeBSD 8.2: getgrgid error

Rekhesh Mohan wrote:
>
>AFAIK, src/common.c is checking the GID with getgid() followed by 
>getgrgid(). Now, my machine uses blowfish instead of md5 for passwd. 
>getgid() is returning 80 - which is fine since i have gid(www) = 80 on my 
>system. However, getgrgid(gid) returns null :-|  I gave up my fight at 
>that point and decided to ask for help :)

This appears to be a C library/OS issue that has nothing to do with
Mailman. getgrgid(gid) should return a struct group for the group
whose ID is gid. This structure should contain the information which
is a representation of the fields in the /etc/groups record for that
gid. If gid is valid, the return from getgrgid(gid) should not be null.

>I tried to figure out the behaviour of these functions with a small test 
>code: getgrgid() returns gr_passwd = * for blowfish, and gr_passwd = x 
>for md5. Is that an issue with mailman or am I making mistakes somewhere 
>else in the installation?

Mailman only cares about getgrgid()->gr_name.

--

-- 
Mark Sapiro <mark <at> msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

Lorenzo Coronati | 1 Aug 2011 20:30

Re: mailman problem with exim

On 30/07/2011 15:57, Mark Sapiro wrote:
> Note that if you installed Mailman from a RedHat/CentOS rpm, most
> examples on the web won't work because the mail wrapper mail/mailman
> and the lists/ directory are not in the same MM_HOME directory. I.e.
> the wrapper is /usr/lib/mailman/mail/mailman and the list directory is
> /var/lib/mailman/lists/.
>
You got it Mark!
I didn't think to check those paths, and in fact they were wrong.
The error in the log was misleading me, nothing to do with virtual users 
and mysql...
I should have started with the simplest things...
Thanks a lot, I hope this thread can be useful to CentOS users.
Lorenzo

Ulf Dunkel | 1 Aug 2011 23:48
Favicon

Can I use /usr/sbin/postmap myself to update virtual-mailman.db?

Hi Mark,

I have moved my domains to a new server and have copied many mailing 
lists from the old server to the new one instead of creating them on the 
new server one by one.

Now I see that the virtual-mailman file isn't updated for these simply 
copied mailing lists, but only for newly created ones. The file warns me 
to edit it myself, but rather have it auto-updated from the 
virtual-mailman.db file.

If I have understood the process correctly, every time when I create a 
new mailing list, Mailman will add the relevant data to the 
virtual-mailman.db and run /usr/sbin/postmap to have the virtual-mailman 
file updated for Postfix.

Can I do this myself on the Server console? I would really like to avoid 
having to create all these mailing lists again ...

And - yes, they are all properly shown by list_lists and can be used in 
either way, but still not via the email interface.

Any help is appreciated, as always.

---Ulf Dunkel

Mark Sapiro | 2 Aug 2011 01:03
Favicon

Re: Can I use /usr/sbin/postmap myself to updatevirtual-mailman.db?

Ulf Dunkel wrote:
>
>Now I see that the virtual-mailman file isn't updated for these simply 
>copied mailing lists, but only for newly created ones. The file warns me 
>to edit it myself, but rather have it auto-updated from the 
>virtual-mailman.db file.

Actually, that's not what the warning means. See below.

>If I have understood the process correctly, every time when I create a 
>new mailing list, Mailman will add the relevant data to the 
>virtual-mailman.db and run /usr/sbin/postmap to have the virtual-mailman 
>file updated for Postfix.

That's backwards. Mailman adds the relevant data to the virtual-mailman
file and then runs /usr/sbin/postmap to update the virtual-mailman.db
file from virtual-mailman. When you put something like
hash:/path/to/data/virtual-mailman in your Postfix config, that tells
Postfix to consult the corresponding /path/to/data/virtual-mailman.db
database and to generate warnings in its log if the
/path/to/data/virtual-mailman.db is not at least as new as
/path/to/data/virtual-mailman

>Can I do this myself on the Server console? I would really like to avoid 
>having to create all these mailing lists again ...

What you want to run is Mailman's bin/genaliases which will completely
rebuild data/aliases and data/virtual-mailman based on the lists in
the installation including those you added by copying and run the
relevant postalias and postmap commands to update the .db files.
(Continue reading)

Tom Browder | 2 Aug 2011 13:31
Picon

Re: Mailman error: Forbidden: You don't have permission to access /pipermail/grads/ on this server [SOLVED]

On Sun, Jul 31, 2011 at 13:08, Mark Sapiro <mark <at> msapiro.net> wrote:
> Tom Browder wrote:
...
>>However, I, as a list user, cannot get access to the archives for a
>>list.  When I try to look at the archives through the link on the
>>Welcome message I get the following:
>>
>>  Forbidden
>>
>>  You don't have permission to access /pipermail/grads/ on this server.
>>
>>I tried changing the example line in the mailman.conf  file from:
>>
>>  Alias /pipermail/ /var/lib/mailman/archives/public/
...
>>I have searched this list for "pipermail" but see no similar problem.
>>
>>I'm sure I've missed a note somewhere but I'm not sure how to proceed.
>> The mailman docs talk about permissions and the mailman user but
>>Ubuntu installs all mailman files with root:list ownership which seems
>>to work for all else.  All the directories under /var/lib/mailman have
>>these permissions:
>>
>>  drwxrwsr-x  4 root list
>
> If that includes /var/lib/mailman/archives/private, then that's OK.
> Otherwise note that /var/lib/mailman/archives/private must be o+x or
> must have user:group xxx:list where xxx is the user that the web
> server uses to access files.

(Continue reading)

Rekhesh Mohan | 2 Aug 2011 14:42
Picon
Favicon

Re: mailman on freeBSD 8.2: getgrgid error


On 01/08/2011 Mark wrote
> Rekhesh Mohan wrote:
> >AFAIK, src/common.c is checking the GID with getgid() followed by
> >getgrgid(). Now, my machine uses blowfish instead of md5 for passwd.
> >getgid() is returning 80 - which is fine since i have gid(www) = 80
> >on my system. However, getgrgid(gid) returns null :-|  I gave up my
> >fight at that point and decided to ask for help :)
> 
> This appears to be a C library/OS issue that has nothing to do with
> Mailman. getgrgid(gid) should return a struct group for the group
> whose ID is gid. This structure should contain the information which
> is a representation of the fields in the /etc/groups record for that
> gid. If gid is valid, the return from getgrgid(gid) should not be
> null.

You are probably right. It may be an issue in C library/OS. I will try 
and discuss this in freeBSD lists. 

 
> >I tried to figure out the behaviour of these functions with a small
> >test code: getgrgid() returns gr_passwd = * for blowfish, and
> >gr_passwd = x for md5. Is that an issue with mailman or am I making
> >mistakes somewhere else in the installation?
> 
> Mailman only cares about getgrgid()->gr_name.

Now here is something that spoiled my sleep: I wrote a small test 
program to call getgrgid(), and it prints getgrgid()->gr_name = www. 
When I added a print statement inside common.c, I get 
(Continue reading)

Tom Browder | 2 Aug 2011 16:00
Picon

Re: Mailman error: Forbidden: You don't have permission to access /pipermail/grads/ on this server [SOLVED]

On Tue, Aug 2, 2011 at 06:31, Tom Browder <tom.browder <at> gmail.com> wrote:
> On Sun, Jul 31, 2011 at 13:08, Mark Sapiro <mark <at> msapiro.net> wrote:
>> Tom Browder wrote:
> ...
>>>However, I, as a list user, cannot get access to the archives for a
>>>list.  When I try to look at the archives through the link on the
>>>Welcome message I get the following:
>>>
>>>  Forbidden
>>>
>>>  You don't have permission to access /pipermail/grads/ on this server.
>>>
>>>I tried changing the example line in the mailman.conf  file from:
>>>
>>>  Alias /pipermail/ /var/lib/mailman/archives/public/
> ...
>>>I have searched this list for "pipermail" but see no similar problem.
>>>
>>>I'm sure I've missed a note somewhere but I'm not sure how to proceed.
>>> The mailman docs talk about permissions and the mailman user but
>>>Ubuntu installs all mailman files with root:list ownership which seems
>>>to work for all else.  All the directories under /var/lib/mailman have
>>>these permissions:
>>>
>>>  drwxrwsr-x  4 root list
>>
>> If that includes /var/lib/mailman/archives/private, then that's OK.
>> Otherwise note that /var/lib/mailman/archives/private must be o+x or
>> must have user:group xxx:list where xxx is the user that the web
>> server uses to access files.
(Continue reading)

Ulf Dunkel | 2 Aug 2011 16:37
Favicon

Re: Can I use /usr/sbin/postmap myself to updatevirtual-mailman.db?

Hi Mark.

> What you want to run is Mailman's bin/genaliases which will completely
> rebuild data/aliases and data/virtual-mailman based on the lists in
> the installation including those you added by copying and run the
> relevant postalias and postmap commands to update the .db files.

Excellent! That worked for me. :-)

Thank you so much,
---Ulf Dunkel

Tom Browder | 2 Aug 2011 17:30
Picon

Two questions ref virtual hosts and mailman

Question 1:
=========

Current situation:
------------------------

I have now pretty much a working solution for this situation (postfix
and mailman installed with Ubuntu packages on 64-bit 10.04 LTS (Lucid
Lynx) :

  1 server
  1 "real" domain: realdomain.com
  2 virtual domains: virtual-1.org
                            virtual-2.org

All are accessed successfully through SSL/TLS (https).

Desired situation:
------------------------

I can get new lists at the virtual domains okay, but here's what I
would like to do: change the mailing list virtual domains to:

  2 virtual domains: lists.virtual-1.org # this is my default domain for mailman
                            lists.virtual-2.org

BUT present the lists to the users as, say, info <at> virtual-1.org

I had some mixed success early on, but other problems intervened.  Now
that the other problems have been solved, I want to blow everything
(Continue reading)


Gmane