Hi!
I'm running a potato system with majordomo installed.
The mailing lists work ok, but when I try to unsubscribe
(by sending an appropriate e-mail), I get this in the
log file:
ABORT chown(0, 31, "/var/lib/majordomo/lists/risiko.new"): Operation not
permitted
feri.
G John Lapeyre writes:
>
> On Wed, 3 Dec 1997, Steve Mayer wrote:
> >
> > Have you checked out the sample configurations in the /usr/doc/majordomo
> > G John Lapeyre wrote:
> >
> > > I can't seem to get majordomo to work. I don't understand much
> > > about setting uid 's . The follow
On Wed, 3 Dec 1997, Steve Mayer wrote:
>
> Have you checked out the sample configurations in the /usr/doc/majordomo
> G John Lapeyre wrote:
>
> > I can't seem to get majordomo to work. I don't understand much
> > about setting uid 's . The following transcript is an example of what
> >
G John,
Have you checked out the sample configurations in the /usr/doc/majordomo
directory? These are pretty helpful in setting up your system alias file to
provide the proper syntax.
Steve Mayer
[EMAIL PROTECTED]
[EMAIL PROTECTED]
G John Lapeyre wrote:
> I can't seem to get majordom
I can't seem to get majordomo to work. I don't understand much
about setting uid 's . The following transcript is an example of what
happens when I try to use it. I tried looking at man pages on sendmail,
exim, and several docs on majordomo. I searched debian bug reports and
web and us
On Wed, 28 Aug 1996, Brian C. White wrote:
G'morning everybody,
> > This symptom with majordomo usually indicates a problem with access rights.
>
> Yup. All the directories were owned by admin.qmail or something similar.
> Removing and re-installing majordomo fixed all that.
Is qmail already d
Brian C. White writes:
>I'm trying to set up majordomo on our server, but have run into the
>following problem.
>
>Any mail sent to the "majordomo" alias and gets piped into the majordomo
>command via "wrapper" causes majordomo to just spin its wheels, chewing
>cpu cycles and allocating more and mo
> This symptom with majordomo usually indicates a problem with access rights.
Yup. All the directories were owned by admin.qmail or something similar.
Removing and re-installing majordomo fixed all that.
Thanks!
At 11:31 PM 8/27/96 -0400, Brian C. White wrote:
>
>Any mail sent to the "majordomo" alias and gets piped into the majordomo
>command via "wrapper" causes majordomo to just spin its wheels, chewing
>cpu cycles and allocating more and more memory. If I run the command
>manually ("wrapper majordomo
Brian C. White wrote:
>I'm trying to set up majordomo on our server, but have run into the
>following problem.
>
>Any mail sent to the "majordomo" alias and gets piped into the majordomo
>command via "wrapper" causes majordomo to just spin its wheels, chewing
>cpu cycles and allocating more and m
I'm trying to set up majordomo on our server, but have run into the
following problem.
Any mail sent to the "majordomo" alias and gets piped into the majordomo
command via "wrapper" causes majordomo to just spin its wheels, chewing
cpu cycles and allocating more and more memory. If I run the comm
11 matches
Mail list logo
