headers
Corbett Klempay | 4 Jun 1998 02:50

2 Quickies...Help!

Being the big newbie, I am having 2 snags so far in my Mailman 1.0b4
installation (Red Hat 5.1):

1)
Cron is giving me this every 5 minutes:

Date: Wed, 3 Jun 1998 19:20:01 -0400
From: Cron Daemon <root <at> chimera.acm.jhu.edu>
To: mailman <at> chimera.acm.jhu.edu
Subject: Cron <mailman <at> chimera> /usr/bin/python
/home/mailman/cron/gate_news

Traceback (innermost last):
  File "/home/mailman/cron/gate_news", line 41, in ?
    file = open(os.path.join(mm_cfg.DATA_DIR, "gate_watermarks.last"),
"w")
IOError: (13, 'Permission denied')

2)
And I'm getting a 403 Forbidden on the test list...I'm thinking this might
be related to the other admin installing cgi-wrap...I'm not too keen on
how it works.

Does is the user mailman supposed to belong to just the users group, or
users as well as the mailman group?

CK

Note: since I sent this message originally, I changed to add the mailman
user account to be a member of the mailman group, which seems to have
(Continue reading)

Permalink | Reply | 0 comments |
headers
John Viega | 4 Jun 1998 07:47

Re: [Mailman-Developers] 2 Quickies

Just to let everyone know how this one turned out:

On Wed, Jun 03, 1998 at 07:44:11PM -0400, Corbett Klempay wrote:

> 1)
> Cron is giving me this every 5 minutes:
[...]
> Traceback (innermost last):
>   File "/home/mailman/cron/gate_news", line 41, in ?
>     file = open(os.path.join(mm_cfg.DATA_DIR, "gate_watermarks.last"),
> "w")
> IOError: (13, 'Permission denied')

Mailman was installed w/ group user instead of group mailman.

> 2)
> And I'm getting a 403 Forbidden on the test list...I'm thinking this might
> be related to the other admin installing cgi-wrap...I'm not too keen on
> how it works.

The problem here was that /home/mailman needed to be "chmod a+rx"'d.
That one should be mentioned in the install document!

John
Permalink | Reply | 0 comments |
headers
Barry A. Warsaw | 4 Jun 1998 17:12
Picon
Picon

Re: [Mailman-Developers] 2 Quickies

>>>>> "JV" == John Viega <viega <at> list.org> writes:

    JV> Mailman was installed w/ group user instead of group mailman.

Do you mean that $prefix wasn't chgrp'd mailman and chmod'd g+s?

I'd really like to know if those instructions in the INSTALL are
incorrect or not.  If they just overlooked, then I can write a test to 
guarantee that's set up correctly.

    JV> The problem here was that /home/mailman needed to be "chmod
    JV> a+rx"'d.  That one should be mentioned in the install
    JV> document!

Okay, here's what the INSTALL doc will say about setting up $prefix:

      Make sure this directory is set to group `mailman' and has the
      group sticky bit set.  You probably also want to guarantee that
      this directory is read and executeable by everyone. For example,
      these shell commands will accomplish this:

          % cd $prefix
          % chgrp mailman .
          % chmod a+rx,g+s .

-Barry
Permalink | Reply | 0 comments |
headers
John Viega | 4 Jun 1998 17:15

Re: [Mailman-Developers] 2 Quickies

On Thu, Jun 04, 1998 at 11:12:34AM -0400, Barry A. Warsaw wrote:
> 
> >>>>> "JV" == John Viega <viega <at> list.org> writes:
> 
>     JV> Mailman was installed w/ group user instead of group mailman.
> 
> Do you mean that $prefix wasn't chgrp'd mailman and chmod'd g+s?

Yeah, I think that it may have been a case of skimming through the
install docs, which I'm sure we've all done before!

John
Permalink | Reply | 0 comments |
headers
Barry A. Warsaw | 4 Jun 1998 17:27
Picon
Picon

Re: [Mailman-Developers] 2 Quickies

>>>>> "JV" == John Viega <viega <at> list.org> writes:

    JV> Yeah, I think that it may have been a case of skimming through
    JV> the install docs, which I'm sure we've all done before!

Yeah, I've been guilty too!  Well, I'll add an explicit check
(someplace).  Much better for configure or make install to barf and
point you at the documentation, then to just let people screw
themselves.  ;-)

-Barry
Permalink | Reply | 0 comments |
headers
Corbett J. Klempay | 6 Jun 1998 02:11

mailman and qmail?

Does Mailman 1.0b4 play nicely with qmail 1.02?  I'm wondering about
installing 1.0b4 on a qmail machine, and didn't know if they got along...

-------------------------------------------------------------------------------
Corbett J. Klempay			         Quote of the Week:
http://www2.acm.jhu.edu/~cklempay  "There exists in India no politician
				    daring enough to attempt to explain
                                    to the masses that cows can be eaten."

PGP Fingerprint: 7DA2 DB6E 7F5E 8973 A8E7  347B 2429 7728 76C2 BEA1
-------------------------------------------------------------------------------
Permalink | Reply | 0 comments |
headers
John Viega | 6 Jun 1998 15:35

Re: mailman and qmail?

On Fri, Jun 05, 1998 at 08:11:43PM -0400, Corbett J. Klempay wrote:
> Does Mailman 1.0b4 play nicely with qmail 1.02?  I'm wondering about
> installing 1.0b4 on a qmail machine, and didn't know if they got along...

In terms of message delivery, Mailman will have no problems with
qmail, since it talks to port 25 instead of calling sendmail directly.
However, the aliases that get generated are for Sendmail and
compatibles,  which is essentially every MTA except Qmail.

I also suspect that a mail gid wouldn't be needed (it seems to me
qmail does a setuid and setgid to the user before calling any
programs).  Thus, the C wrapper wouldn't be necessary.  However, it
might be, in which case, we definitely wouldn't be detecting the right
GID.

However, I would like to support qmail, and perhaps make it generate
the right aliases, etc.  I'd like to see qmail users do: 

./configure --with-qmail

or something like that.

So if you're willing to tackle the alias and GID issue, qmail should
work.  We'd definitely like to hear what is necessary to get it
working, and I'd be willing to help out in any way I could on that
one.

Oh, now that I'm thinking about it, I was assuming that qmail would be
run kto use user aliases, which would mean all your mailing lists
would have to start with "mailman", I think.  I am sure it also has a
(Continue reading)

Permalink | Reply | 0 comments |
headers
Corbett J. Klempay | 6 Jun 1998 19:12

initial mail

Is there an easy way to disable the initial mailing that everyone gets
when they are put on a list?  We want to move all of our Majordomo stuff
to Mailman, but have the users be none the wiser until we tell them about
it...

-------------------------------------------------------------------------------
Corbett J. Klempay			         Quote of the Week:
http://www2.acm.jhu.edu/~cklempay  "There exists in India no politician
				    daring enough to attempt to explain
                                    to the masses that cows can be eaten."

PGP Fingerprint: 7DA2 DB6E 7F5E 8973 A8E7  347B 2429 7728 76C2 BEA1
-------------------------------------------------------------------------------
Permalink | Reply | 0 comments |
headers
Corbett J. Klempay | 7 Jun 1998 00:09

one more thing...

I wrote earlier about surpressing the initial email sent to users as they
are added to a list...one other question...is is possible to surpress the
monthly password reminder?

-------------------------------------------------------------------------------
Corbett J. Klempay			         Quote of the Week:
http://www2.acm.jhu.edu/~cklempay  "There exists in India no politician
				    daring enough to attempt to explain
                                    to the masses that cows can be eaten."

PGP Fingerprint: 7DA2 DB6E 7F5E 8973 A8E7  347B 2429 7728 76C2 BEA1
-------------------------------------------------------------------------------
Permalink | Reply | 0 comments |
headers
John Viega | 7 Jun 1998 11:40

Re: initial mail

On Sat, Jun 06, 1998 at 01:12:46PM -0400, Corbett J. Klempay wrote:
> Is there an easy way to disable the initial mailing that everyone gets
> when they are put on a list?  We want to move all of our Majordomo stuff
> to Mailman, but have the users be none the wiser until we tell them about
> it...

Well, I'd suggest using the convert_list script in the bin directory,
although I think that does send out a notification.  I'll work up a
patch in the next day or so to give an option for subscribing people
without notification.

However, if you don't send people the notification message, they don't
ever know what their password is, or that they even have one.  We
could do something like email confirmation for everything...

Also, to answer your other mail about suppressing password reminders,
I'll do that one too.  For now, I'd just recommend removing the right
line from the crontab.in file, and installing a new crontab.  That'll
keep reminders from being sent.  I'll work on a per-list solution
soon.
Permalink | Reply | 0 comments |

Gmane