On Fri, 2005-07-01 at 12:37 -0400, Matt Singerman wrote:
> Hi Mark,
>
> Thanks for posting this - I didn't even know this filed existed! I
> think I've located the problem - mailmanctl isn't running. However,
> when I try to start it (with "/usr/lib/mailman/bin/mailmanctl start"),
> nothing happ
Matt Singerman wrote:
> Argh. Still having problems. So I think there was a problem with the
> default mailman package, so I blew it away and reinstalled the RPM
> from scratch. This added a mailman home directory (good), but I still
> couldn't su (bad). Used vipw and changed mailman's shell fr
Argh. Still having problems. So I think there was a problem with the
default mailman package, so I blew it away and reinstalled the RPM
from scratch. This added a mailman home directory (good), but I still
couldn't su (bad). Used vipw and changed mailman's shell from
/sbin/nologin to /bin/bash.
Hi Mark,
Thanks for posting this - I didn't even know this filed existed! I
think I've located the problem - mailmanctl isn't running. However,
when I try to start it (with "/usr/lib/mailman/bin/mailmanctl start"),
nothing happens. I tried to su as user mailman to check the crontab
and try and
Matt Singerman wrote:
>but I don't even think it's getting that far. Any emails sent to the
>test list don't make it there at all. They're not being sent out to
>the members, and don't make it into the archives.
See the FAQ
>Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Article 3.14
-
Hello,
So our old list server died, and I opted to switch from OpenBSD to
Fedora for the new one. This is a brand-new system with nothing weird
or complex on it, yet. It is running Fedora Core 3 (I know, FC4 is
out, but I had this sitting around). I downloaded the latest Mailman
RPM after insta
