Looking at your directory listing and your aliases, you should have a
lists directory with a vaclist file and a vaclist.archive subdirectory.
The vaclist.archive subdirectory should have a FILE called vaclist.YYMM
where YY is a 2 digit year (we didn't learn from Y2k?) and a 2 digit
month for MM, not another vaclist.archive subdirectory.
Your alias for archiving should look like this (all one line);
vaclist-outgoing: :include:/usr/local/majordomo/lists/vaclist,"|/usr/local/maj
ordomo/wrapper archive2.pl -f /usr/local/majordomo/lists/vaclist.archive/vacli
st -a -M","|/usr/local/majordomo/wrapper digest -r -C -l vaclist-digest vaclis
t-digest-outgoing"
Notice that I put white space between the alias: and what it expands to.
Second, I removed the incorrect .archive from the end of the command, and
Third, I moved the -a -m from in front of the file definition to the end of
the command but changed the m to M. Your life would be much easier if you
just create additional aliases to reference the archiving and digest tools,
rather than having one alias that is over 256 characters long. Reference
my previously posted example aliases.
The bottom line is, make the changes to your alias for the list. Delete
the /usr/local/majordomo/lists/vaclist.archive/vaclist.archive directory.
Try sending another message to your list and look for error messages.
Dan Liston
VACList Admin wrote:
> Hi Dan & Co.
>
> I use archive2.pl too, so changes the alias, and now receive one of these
> with each post:
>
>
> ----- The following addresses had permanent fatal errors -----
> "|/usr/local/majordomo/wrapper archive.2pl -a -m -f
> /usr/local/majordomo/lists/vaclist.archive/vaclist.archive"
> (reason: system error (e.g., can't fork))
> (expanded from: vaclist-outgoing)
> ----- Transcript of session follows -----
> wrapper: Trying to exec /usr/local/majordomo/archive failed: No such file or
> directory
> Did you define PERL correctly in the Makefile?
> HOME is HOME=/usr/local/majordomo,
> PATH is PATH=/bin:/usr/bin,
> SHELL is SHELL=/bin/sh,
> MAJORDOMO_CF is MAJORDOMO_CF=/usr/local/majordomo/majordomo.cf
> 451 4.0.0 "|/usr/local/majordomo/wrapper archive -a -m -f
> /usr/local/majordomo/lists/vaclist.archive/vaclist.archive"... Operating
> system error
> Message could not be delivered for 5 days
> Message will be deleted from queue
>
>
>
> On 11/16/02 8:15 PM, "Daniel Liston" <dliston@sonny.org> wrote:
>
>
>>Let me make a correction to my previous post of just tightening the
>>permissions on your directory. I should have asked for these
>>majordomo.cf lines;
>>
>>$homedir = "/usr/lib/majordomo";
>>$datadir = "/var/lib/majordomo";
>>$listdir = "$datadir/lists";
>>$digest_work_dir = "$datadir/digests";
>>$log = "$datadir/Log";
>>$sendmail_command = "/usr/sbin/sendmail";
>>$mailer = "$sendmail_command -oi -oee -f\$sender";
>>$bounce_mailer = "$sendmail_command -oi -oee -f\$sender -t";
>>$filedir = "$datadir/archives";
>>$filedir_suffix = "";
>>$config_umask = 007;
>>$TMPDIR = "/var/lib/majordomo/tmp";
>
>
>
> $homedir = "/usr/local/majordomo";
> (no datadir)
> $listdir = "$homedir/lists";
> $digest_work_dir = "/usr/local/majordomo/digests";
> $log = "$homedir/Log";
> $sendmail_command = "/usr/sbin/sendmail";
> $mailer = "$sendmail_command -oi -oee -f\$sender";
> $bounce_mailer = "$sendmail_command -oi -oee -f\$sender -t";
> $filedir = "$listdir";
> $filedir_suffix = ".archive";
> $config_umask = 007;
> $TMPDIR = '/usr/local/majordomo/tmp';
>
>
>>and to validate those settings, showed example directory/file
>>ownership and permissions of my $datadir;
>>
>>-rw-r--r-- 1 majordomo majordomo 9648 Sep 3 03:11 aliases
>>drwxr-x--- 8 majordomo majordomo 4096 Sep 2 23:27 archives
>>drwxr-x--- 5 majordomo majordomo 4096 Sep 2 23:27 digests
>>drwxr-x--- 2 majordomo majordomo 4096 Nov 14 02:45 lists
>>-rw-r----- 1 majordomo majordomo 0 Nov 10 08:31 Log
>>drwxr-xr-x 2 majordomo majordomo 4096 Oct 22 20:16 recipes
>>drwxr-x--- 2 majordomo majordomo 4096 Oct 16 13:51 tmp
>
>
> $homedir looks like this:
> -rw-rw-r-- 1 majordom majordom 62616 Nov 20 17:49 Log
> drwxr-xr-x 2 majordom majordom 512 Aug 29 18:02 Tools
> -rw-r--r-- 1 majordom majordom 5284 Nov 15 14:12 archive2.pl
> drwxrwxr-x 3 majordom majordom 512 Oct 30 17:41 archives
> drwxr-xr-x 4 majordom majordom 512 Oct 30 15:53 digests
> drwxr-xr-x 5 majordom majordom 1024 Nov 20 17:49 lists
> -rw-r--r-- 1 majordom majordom 10491 Oct 30 17:42 majordomo.cf
> drwxr-xr-x 2 majordom majordom 1024 Nov 20 15:55 tmp
>
> lists looks like this:
> -rw-r--r-- 1 majordom majordom 3350 Nov 20 15:25 vaclist
> drwxr-xr-x 3 majordom majordom 512 Nov 11 17:45 vaclist.archive
>
> vaclist.archive looks like this:
> drwxr-xr-x 2 majordom majordom 512 Nov 11 17:45 vaclist.archive
> (and is empty...)
>
>
>
>>In my case, I stray from the default majordomo.cf setting of
>>$filedir = "$listdir";
>>$filedir_suffix = ".archive";
>>so my aliases and directory structure are a bit different as well.
>
>
>>My "test" aliases look like this;
>>test: "|/usr/lib/majordomo/wrapper resend -l test test-outgoing,nobody"
>>#test: "|/usr/bin/procmail -f- /var/lib/majordomo/recipe/test"
>>owner-test: test-owner,
>>#owner-test: test-approval,"|/usr/lib/majordomo/wrapper autobounce -l test"
>>test-owner: dliston
>>#test-approval: dliston,bouncefilter
>>test-approval: test-owner
>>test-outgoing:
>>:include:/var/lib/majordomo/lists/test,test-archiver,test-digestify
>>test-archiver: "|/usr/lib/majordomo/wrapper archive2.pl -f
>>/var/lib/majordomo/archives/test/test -a -M"
>>test-digestify: "|/usr/lib/majordomo/wrapper digest -r -C -l test-digest
>>test-digest-outgoing",
>>test-request: "|/usr/lib/majordomo/wrapper request-answer test"
>>#test-request: "|/usr/lib/majordomo/wrapper majordomo -l test"
>>test-digest: test
>>owner-test-digest: owner-test
>>test-digest-outgoing: "|/usr/bin/bulk_mailer owner-test@sonny.org
>>/var/lib/majordomo/lists/test-digest"
>
>
> owner-vaclist:admin@airstream.net
> owner-vaclist-digest:owner-vaclist
> owner-vaclist-outgoing:owner-vaclist
> owner-vaclist-digest-outgoing:owner-vaclist
> vaclist-approval:owner-vaclist
> vaclist-digest-approval:owner-vaclist
> vaclist: "|/usr/local/majordomo/wrapper resend -l vaclist
> vaclist-outgoing,nobody"
> vaclist-digest:vaclist
> vaclist-outgoing::include:/usr/local/majordomo/lists/vaclist,
> "|/usr/local/majordomo/wrapper archive2.pl -a -m -f
> /usr/local/majordomo/lists/vaclist.archive/vaclist.archive",
> "|/usr/local/majordomo/wrapper digest -r -C -l vaclist-digest
> vaclist-digest-outgoing"
> vaclist-digest-outgoing::include:/usr/local/majordomo/lists/vaclist-digest,n
> obody
> vaclist-request: "|/usr/local/majordomo/wrapper majordomo -l vaclist"
> vaclist-digest-request: "|/usr/local/majordomo/wrapper majordomo -l
> vaclist-digest"
>
>
>
>>If you notice, I use separate aliases to define my archive and digest
>>processes, and refer to them as test-archiver and test-digestify. My
>>test-archiver utilizes archive2.pl rather than the "archive" you are
>>using, and the fully qualified archive file matches
>>"$filedir/$list$filedir_suffix". If I were following the defaults in
>>original majordomo.cf, my test-archiver would expand to;
>>"|/usr/lib/majordomo/wrapper archive2.pl -f
>>/var/lib/majordomo/lists/test.archive/test -a -M"
>>This would imply, that I have a test.archive directory that is owned
>>by majordomo in my lists directory, and that directory would contain
>>a file called test.200211 for all messages received this month.
>>
>>I would be willing to be that your -f parameter to archive has
>>vaclist.archive/vaclist.archive instead of vaclist.archive/vaclist.
>
>
> That's correct, but in my case shouldn't it? Or should I delete the sub
> vaclist.archive directory and change:
>
> "|/usr/local/majordomo/wrapper archive2.pl -a -m -f
> /usr/local/majordomo/lists/vaclist.archive/vaclist.archive",
> to
> "|/usr/local/majordomo/wrapper archive2.pl -a -m -f
> /usr/local/majordomo/lists/vaclist.archive/vaclist", ??
>
> What about the the args? Why are they yours different from the default?
>
> Thanks again,
> RJ Dial
> Airstream.org
>
>
>>Dan Liston
>>
>
>
>
>
>>VACList Admin wrote:
>>
>>>Also having archiving problems. Each post results in the following error:
>>>(at 50 post a day, the queue is full!!)
>>>the: /usr/local/majordomo/lists/vaclist.archive/vaclist.archive
>>>directories do exist with correct owner & group, and permissions set at 775
>>>Any ideas?
>>>RJ
>>>---------------------------
>>>The original message was received at Sun, 10 Nov 2002 12:44:20 -0800 (PST)
>>>from majordom@localhost
>>>
>>> ----- The following addresses had permanent fatal errors -----
>>>"|/usr/local/majordomo/wrapper archive -a -m -f
>>>/usr/local/majordomo/lists/vaclist.archive/vaclist.archive"
>>> (reason: system error (e.g., can't fork))
>>> (expanded from: vaclist-outgoing)
>>>
>>> ----- Transcript of session follows -----
>>>wrapper: Trying to exec /usr/local/majordomo/archive failed: No such file or
>>>directory
>>> Did you define PERL correctly in the Makefile?
>>> HOME is HOME=/usr/local/majordomo,
>>> PATH is PATH=/bin:/usr/bin,
>>> SHELL is SHELL=/bin/sh,
>>> MAJORDOMO_CF is MAJORDOMO_CF=/usr/local/majordomo/majordomo.cf
>>>451 4.0.0 "|/usr/local/majordomo/wrapper archive -a -m -f
>>>/usr/local/majordomo/lists/vaclist.archive/vaclist.archive"... Operating
>>>system error
>>>Message could not be delivered for 5 days
>>>Message will be deleted from queue
>>
>>
>>
References:
|
|
