Dan: Many thanks for the followup. My majordomo is 1.94.3 and running
sendmail 8.9.3. You are right. I don't need the archive, just a daily
digest with the "white noise" headers stripped out. Digest will not work on
my "shared server" as configured, so I have done a woirkaround that does
the digest, but with all of the extra headers. The script in archive2.pl
would do fine if I could get it to work with my strange aliases. Here's
what the mainlist looks like for a vhost list only (running on my
"maindomain.com" server) and it works fine (also all aliases are defined
okay in the "virtmaps")... and the "a63134765" is the special designated
"outgoing" for each vhost:
# Entries for Majordomo Mailing List Manager on myvhost.com
majordomo-at-vhost.com: "|/usr/local/majordomo/wrapper majordomo -C
/usr/local/majordomo/myvhost.com.cf"
# "myvhostlist" list
myvhostlist-at-myvhost.com: "|/usr/local/majordomo/wrapper resend -l
myvhostlist -h maindomain.com a63134765"
a63134765::include:/usr/local/majordomo/Lists/myvhostlist
owner-myvhostlist-at-myvhost.com: myvhostlistmgr@myvhost.com
myvhostlist-request-at-myvhost.com: "|/usr/local/majordomo/wrapper
request-answer myvhostlist"
myvhostlist-approval-at-myvhost.com: myvhostlistmgr@myvhost.com
********************************************************
BUT, this setup for a list plus digest will not work:
********************************************************
# Replaces above plain list aliases in attempt to set up digest:
# "myvhostlist" list
myvhostlist-at-myvhost.com: "|/usr/local/majordomo/wrapper resend -l
myvhostlist -h maindomain.com a63134765"
a63134765::include:/usr/local/majordomo/Lists/myvhostlist,
myvhostlist-digestify
owner-myvhostlist-at-myvhost.com: myvhostlistmgr@myvhost.com
myvhostlist-request-at-myvhost.com: "|/usr/local/majordomo/wrapper
request-answer myvhostlist"
myvhostlist-approval-at-myvhost.com: myvhostlistmgr@myvhost.com
# "myvhostlist-digest" list
myvhostlist-digestify: myvhostlist-digest-at-myvhost.com:
"|/usr/local/majordomo/wrapper digest -r C -l myvhostlist-digest -h
maindomain.com a17242431"
myvhostlist-digest: myvhostlist
a17242431::include:/usr/local/majordomo/Lists/myvhostlist-digest
owner-myvhostlist-digest-at-myvhost.com: myvhostlistmgr@myvhost.com
myvhostlist-digest-request-at-myvhost.com: "|/usr/local/majordomo/wrapper
request-answer myvhostlist-digest"
myvhostlist-digest-approval-at-myvhost.com: myvhostlistmgr@myvhost.com
Sorry about the wrap mess and so much detail. My workaround for the digest
is to collect the day's messages in a user account and mail them out by
cron at midnight each day. Of course, it is full of the extra headers and
is what I'm trying to remove.... any more ideas appreciated.... or if you
see something above.
At 07:01 PM 6.9.2001 -0500, Dan Liston wrote:
>I did "assUme" that you are running majordomo-1.94.5 when I sent my previous
>response. I am still making that assumption, and that your sendmail is at
>least version 8.9.3 or higher.
>
>Did you look at the first paragraph of text in the archive2.pl script? It
>also allows you to do daily, monthly, or yearly archives. Archive2.pl is
>just a newer version of archive.pl.
># archive -f <archive> {-u|-a} [-d|-m|-y] [file ...]
># -f <archive> REQUIRED; specifies base file name for archive
># -u Input is a UNIX archive (separated by "From " lines) to split
># -a Input is a message to append to archive
># -d Archive file is <archive>.YYMMDD
># -D Archive file is <archive>.YYYYMMDD
># -m Archive file is <archive>.YYMM
># -M Archive file is <archive>.YYYYMM
># -y Archive file is <archive>.YY
># -Y Archive file is <archive>.YYYY
># Exactly one of "-u" or "-a" must be specified.
># At most one of "-d", "-D", "-m", "-M", "-y", or "-Y" may be specified;
># if none is specified, archive name is simply <archive>
>The key here, is that you are also allowed to use alternate majordomo.cf
>files. The -C /path/to/majordomo.cf is undocumented except in the perl
>code itself, and must be the very first argument to the command.
>
>Neither of the archive tools will "send" messages out, but only create
>the file with contents of that day's messages, and give the filename an
>extension that indicates the period of time in it's content.
>
>What it really sounds like your end goal is though, is to create a daily
>digest of messages and send those out rather than creating an archive.
>Setting up a -digest of your list requires additional aliases, and a
>listname-digest.config file (which purges received lines) for each list.
>A daily cron job can send a command to majordomo to "force" a digest to
>be compiled and sent out. Just be careful NOT to run this cron as root
>or majordomo.
>
>Dan Liston
>
>
>jacks@sage-american.com wrote:
>>
>> Dan: Thanks for the suggestion, but if my understanding of archive2.pl is
>> that it accumulates each incoming message into a monthly archive. My
>> workaround accumulates all of the messages for a single day into a holding
>> file. I was hoping to use the "archive.pl" tool rather than the archive2.pl
>> to next take the day's file containing all of the messages (in the order
>> received) and remove the "white noise" or all of the extra headers.
>> Archive.pl indicates that it will do the following:
>>
>> #Here is a perl program I wrote to keep mailing list archives.
>> #It is designed to produce list archive files similar to Revised
>> #Listserv. Each message is separated by a line of "==="s and
>> #most of the header "noise" is gone. Instead of being stored
>> #in one big file, they are split into one file per month with
>> #the name logYYMM where YY and MM are the numeric year and
>> #month.
>> #
>> #I call it from /usr/lib/aliases using:
>> #
>> # listname-archive: "|/usr/local/mail/majordomo/wrapper archive.pl \
>> # /usr/local/mail/lists/listname.archive"
>> #
>> #Where the last parameter is the directory name to put the
>> #log files into.
>>
>> I thought the script could be applied to a DAY'S list of messages and then
>> sent out stripped as described above. I would still need to deal with the
>> file name problem and change it to a day "logDDMMYY" instead of a month
>> "logYYMM"... then mail it out at midnight to the digest list....
>>
>> I don't have "root" permission, so I have some limits at the level of admin
>> for my dedicated server....
>>
>> Any more thoughts would be appreciated. I've seen many of your other
>> suggestions and you seem very willing and able on this stuff.... thanks!
>>
>> At 03:47 AM 6.6.2001 -0500, you wrote:
>> >try using "-C /path/to/xxvhst.cf" as the first argument to archive2.pl.
>> >
>> >Dan Liston
>> >
>> >jacks@sage-american.com wrote:
>> >>
>> >> My sendmail is modified to recognize different vhost aliases and
there is
>> >> a xxvhost.cf for each domain. The archive script seems to want the main
>> >> majordomo.cf.
>> >>
>> >
>> >
>>
>> Best regards,
>>
>> Jack L. Stone,
>> Administrator
>>
>> Sage-American
>> http://www.sage-american.com
>> jacks@sage-american.com
>
>
Best regards,
Jack L. Stone,
Administrator
Sage American
http://www.sage-american.com
jacks@sage-american.com
References:
|
|
