> This is a more theoretical question for you mj users. How exactly is it that
> the majordomo program associates a list with its digest? What I'm asking is
> how, once I recieve a message to list does the majordomo program suite make a
> copy in the list-digest working dir as "root-ly" defined in majrodomo.cf.
> Does it only match the text "list" to the supposed digest called
> "list-digest"? Or is there a way to specify what the digest is called? Also,
> what program does this matching? Is it resend that reads the list.config file
> to determine what the digest name is? I can't find a setting for it? Or is
> it not in resend, but in another program.
>
> In short:
> What program copies the "list" messages to the "list-digest" work dir, and how
> does it match them?
This is set up by your aliases, e.g.,
space-and-flight-outgoing: :include:/majordomo/lists/space-and-flight,
space-and-flight-archive, "|/majordomo/majordomo/wrapper digest -r -C -l
space-and-flight-digest space-and-flight-digest-outgoing"
Then you define your digest aliases and set a byte limit to trigger digesting
(or run mkdigest via cron), per the FAQ and other docs.
Now, what *I* want to know is how digest (in 1.93) knows what the original
list name is, for use in removing the message_footer. That's not in the aliases
file, nor in majordomo.cf (that I could find).
Bonnie Scott
> Erik
|
|
