OK, it looks like your next digest will be issue number 15, and the rest
of the -digest.config file looks good to me.
Your list is not archiving because you do not have your archive tool set
on your my-list-doit alias. Which by the way is "your" equivalent of
the
-outgoing alias. Change -outgoing in my-list-digest-outgoing to -doit,
and add this to the line to enable regular archiving of your list.
,"|/home/majordomo/runtime/wrapper archive2.pl -f
/home/majordomo/archives/my-list/my-list -a -M"
The final argument of my-list-digest-outgoing did not exist on the LHS
of
your aliases file. That is why your digest was created, but never
delivered
anywhere. The messages were being sent to the internet black-hole. The
following is the alias that needs correction, as it is now, and what it
should
look like after being fixed.
> my-list-doit: :include:/home/majordomo/lists/my-list,"|/home/majordomo/runtime/wrapper digest -R -C -l my-list-digest
> my-list-digest-outgoing"
my-list-doit:
:include:/home/majordomo/lists/my-list,"|/home/majordomo/runtime/wrapper
digest -R -C -l my-list-digest
my-list-digest-doit","|/home/majordomo/runtime/wrapper archive2.pl -f
/home/majordomo/archives/my-list/my-list -a -M"
The -R tells digest to accept (recieve) the message, but do not send a
digest
if it makes the lines, age, or bytes exceed the setting in .config.
This is
where your cron command becomes mandatory. I would be interested to see
what
that looks like, and your @...my-list.resend contents too. You must be
using
examples from "Managing Mailing Lists" (which was written prior to
1.90). I
have said this before and I will say it again; "The only arguments that
should
be used for the resend command are -l listname and it's delivery
address."
All the other parameters are either redundant or overridden by the
.config
file. This makes the use of @filename a waste too, as it's intent was
to
create a shorter RHS for the alias. The exception to this statement is
the
-C (alternate configuration) parameter which can only be used in the
alias
file or the @filename.
Dan Liston
Bill Polhemus wrote:
>
> Dan, this morning, without explanation, the Digests for those lists that I have active were created automatically for the first time
> in about a week.
>
> HOWEVER, as usual the digests were NOT sent out.
>
[snip]
> [BY THE WAY: I can't figure out what the heck "my-list-digest-outgoing" is. I thought that it was the list of addresses subscribed
> to my-list-digest, but that is already set up as simply my-list-digest. Then I thought maybe it was the file that was built until it
> was ready to send, but I can't find it anywhere. What is it?]
d
References:
|
|
