Dan Liston wrote:
>
> I really do not understand what is to test for archiving. Either the
> file is created, and appended to with each message, or it isn't.
But that's the point. After you "fiddle" with the config and aliases settings--and make sure the right directories/files AS FAR AS
YOU UNDERSTAND THEM are set up--you need to be able to dry run to see if the archives are created.
FWIW, the archives ARE created for the digested lists, but not for undigested. Can't figure that one out.
> As for
> digests, you can send the "mkdigest listname-digest
> listname-digest-outgoing password" message to majordomo any time you
> want to force a digest to be created, regardless of size, lines, or age
> of work files.
Yeah, I forgot about that.
> If your aliases, listname(-digest).config files, and majordomo
> ownerships and permissions on files and directories are correct, you
> only need to look in the directories defined for $listdir,
> $digest_work_dir, $filedir, and $filedir_suffix in your majordomo.cf for
> the existance of properly named files after a message has been
> received/distributed for the list in question.
> ... Just check to
> see if the file has content matching the distributed message. The
> filename is indicated by volume number and issue number of the digest.
> Since the file is in a directory named for the list's digest, you know
> what is digested before even seeing the volume and issue numbered files.
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.
Here is what I have in my DIGEST configuration file:
---------------------
admin_passwd = xxxxxxx
administrivia = yes
advertise << END
END
announcements = yes
approve_passwd = xxxxxxx
archive_dir =
comments << END
END
date_info = yes
date_intro = yes
debug = no
description = DESCRIPTION OF DIGESTED LIST GOES HERE
digest_archive =
digest_issue = 15
digest_maxdays =
digest_maxlines =
digest_name = my-list-digest
digest_rm_footer = my-list
digest_rm_fronter =
digest_volume = 3
digest_work_dir =
get_access = list
index_access = open
info_access = open
intro_access = list
maxlength = 40000
message_footer << END
MESSAGE FOOTER FOR DIGESTED LIST GOES HERE
END
message_fronter << END
_SUBJECTS_
END
message_headers << END
END
moderate = no
moderator =
mungedomain = yes
noadvertise << END
END
precedence = bulk
purge_received = no
reply_to = my-list@mydomain
resend_host = mydomain
restrict_post = my-list:my-list-digest
sender = owner-my-list-digest
strip = yes
subject_prefix = [MY-LIST DIGEST]
subscribe_policy = open+confirm
taboo_body << END
END
taboo_headers << END
END
unsubscribe_policy = open
welcome = yes
which_access = list
who_access = closed
---------------------
HERE is the aliases file:
---------------------
#####################################
# Majordomo Aliases
#####################################
owner-majordomo: me@localhost
majordom: owner-majordomo
Majordomo-Owner: owner-majordomo
majordomo: "|/home/majordomo/runtime/wrapper majordomo"
#####################################
# MY-LIST
#####################################
owner-my-list: bpolhem@swbell.net,nobody
my-list: "|/home/majordomo/runtime/wrapper resend @/home/majordomo/lists/my-list.resend"
my-list-approval: owner-my-list
my-list-doit: :include:/home/majordomo/lists/my-list,"|/home/majordomo/runtime/wrapper digest -R -C -l my-list-digest
my-list-digest-outgoing"
owner-my-list-doit: owner-my-list
my-list-request: "|/home/majordomo/runtime/wrapper majordomo -l my-list"
owner-my-list-request: owner-my-list
#####################################
# MY-LIST DIGEST
#####################################
owner-my-list-digest: owner-my-list
my-list-digest: my-list
my-list-digest-doit: :include:/home/majordomo/lists/my-list-digest
my-list-digest-approval: owner-my-list
owner-my-list-digest-doit: owner-my-list
my-list-digest-request: /home/majordomo/runtime/wrapper majordomo -l my-list-digest
owner-my-list-digest-request: owner-my-list
[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?]
---------------------
Finally, here are the lines from MAJORDOMO.CF
---------------------
$listdir = "/home/majordomo/lists"
$digest_work_dir = "/home/majordomo/digests"
$filedir = "/home/majordomo/archives";
$filedir_suffix = "";
---------------------
The list stuff for my-list is located in /home/majordomo/lists as required. The directory for my-list-digest is located in
/home/majordomo/digests, as required.
There are directories for both my-list and my-list-digest located in /home/majordomo/archives. They don't have "suffixes".
Follow-Ups:
References:
|
|
