Had a bit of spare time yesterday evening, and now qmail support in
majordomo2 is starting to come together, I thought I'd bite the bullet and
go for it. I used the downloaded the full version from cvs, and set about
installation. This is on Red Hat 5.1.
This is just a few observations from an "end user". I hope to get into
hacking some source when I have some more spare time (ha!)
1. I had to use h2ph to compile all the headers. In fact, it's lucky I had
the gcc source because a couple of the needed headers (stdarg.h/ph and one
other I forget) were only in that.
2. I had to download modules from CPAN. This was painless though, and
worked as advertised by the installation.
3. I use qmail. The installation didn't make the .qmail-default files as
advertised (I couldn't find any source to do this, so I assume it's not
4. I set the server up as 'mj2' since I'm also running majordomo 1.
However, even when I made the .qmail-default it didn't pick up mail, so I
had to make an alias for .qmail-mj2. From looking at the source it seems
hardcoded to 'majordomo'.
5. The crontab entries seem hard-coded to use 'majordomo' as well, as
they're talking to my majordomo 1 server. Haven't investigated yet, just
Apart from that, I've been playing around, and it looks great! Lack of
documentation made it a bit hard for me to "get into" it and understand what
I was doing, but I quickly overcame that. Does anyone have any opinion
whether it's stable enough to move some full-time lists to it?
I have two that I'd like to move over if I can - one has ~300 members, the
other ~250. So not exactly big beer, but I don't want to compromise them.
One other question -- under qmail does majordomo2 use qmail's VERP, or does
it do it's own magic? I don't care either way, but would like mj2 to handle
my bounces as best it can :-)
Adastra Software Ltd, Edmonton House, Park Farm Close, Folkestone, Kent
Tel: 01303 222700 Fax: 01303 222701 24-hr support: 0701 0702 016
Call handling for GP Co-ops & Deputising services www.adastra.co.uk