I have fiddled and diddled with this and I can't seem to get
it resolved.
Here is the message I get from the CRON program:
----------------
SUBJECT: Cron <root@MyDomainHost> run-parts /etc/cron.daily
producing My-List-digest V3 #1
processing /home/majordomo/digests/My-List-digest/001
processing /home/majordomo/digests/My-List-digest/002
processing /home/majordomo/digests/My-List-digest/003
*
*
*
processing /home/majordomo/digests/My-List-digest/018
mj_digest: ABORT
open(DIGEST,
">/home/majordomo/archives/My-List-digest/v03.n001"): No
such file or directory
----------------
In a separate message I get:
----------------
SUBJECT: MAJORDOMO ABORT (mj_digest)
--
MAJORDOMO ABORT (mj_digest)!!
open(DIGEST,
">/home/majordomo/archives/My-List-digest/v03.n001"): No
such file or directory
----------------
Now, the funny thing is that in MAJORDOMO.CF, I have set
$listdir = /home/majordomo/lists
and $archivedir = "".
So I can't figure out why it keeps trying to go to the
nonexistant ../archives/My-List-digest/v03.n001 to place the
archives.
Now, another thing: Why is it that, although there is PLENTY
of activity on the mailing list, it keeps building exactly
18 numbers of the digest, before aborting? It has done this
consistently for about three weeks. FYI, as of this evening
there are actually 180 separate DIGEST numbers sitting in
/home/majordomo/digests/My-List-digest. NONE of these
digests have gone out to subscribers (although there are
subscribers).
I guess I don't quite understand the relationship between
the digest and the archives.
FWIW, I have not yet set up archiving because of the
aforementioned failure to get archive2.pl to work (still
working on that one).
Any advice or observations are welcome.
Follow-Ups:
References:
|
|
