Having an alias for the archiver just simplifies doing the archiving.
If on your listname-outgoing alias you have the :include: file, and
an alias to the archiver, it is easier to follow and understand than
putting all the commands and arguments on the same line. For example,
this would be pretty difficult to follow;
listname-outgoing010110: :include:/var/lib/majordomo/lists/listname,"|/usr/lib/majordomo/wrapper archive2.pl -f /var/lib/majordomo/listname.archive/listname -a -M","|/usr/lib/majordomo/wrapper digest -r -C -l listname-digest listname-digest-outgoing010110,nobody"
By creating an alias for the archiver, and another for the digestifier,
you simplify each alias. Isn't this easier to follow?
listname-outgoing010110: :include:/var/lib/majordomo/lists/listname,listname-archiver,listname-digestify
listname-archiver: "|/usr/lib/majordomo/wrapper archive2.pl -f /var/lib/marjodomo/listname.archive/listname -a -M"
listname-digestify: "|/usr/lib/majordomo/wrapper digest -r -C -l listname-digest listname-digest-outgoing010110,nobody"
The outgoing alias (listname-outgoing010110) is what delivers the message
to the recipients, the archiver (which also gets the message into the
archive file), and in this case, the digested version of the same list.
In the above example of choices for aliases, mail is sent to the listname
alias. (I did not show that alias, but will now)
listname: "|/usr/lib/majordomo/wrapper resend -l listname listname-outgoing010110,nobody"
This alias calls the resend script which is how rules in listname.config are
enforced, and if all goes well, the messages is sent from resend to the
outgoing alias. Making your archives searchable from a web interface will
also require tools like MHonArc, Glimps, and/or Wilma.
Do a search of the archives on the word example. You should find tons of
aliases and config files examples.
Dan Liston
Robert Gahl wrote:
>
> I have this really bad feeling that this is a standard question that gets
> asked a lot, but I can't find the answer in the archives that I'm looking
> for. Basically, I need to create a list and create an archive of that list
> so that we can capture all information that is sent through the list so
> that it can be searched (similar to what I was able to do when looking for
> info from this list) from a web interface.
>
> I understand that I need to create an "alias" using archive.pl or
> archive2.pl (each having their own special set of features). My problem is
> how is that alias used. That is, is it:
>
> a) Creating an alias called mylist-archive will cause majordomo to
> automatically invoke this when a message comes through the standard
> majordomo alias.
>
> b) One must add mylist-archive as a user of the majordomo list so that
> email to the list is simply passed through the archiver.
>
> or
>
> c) People must send mail to mylist-archive, not mylist, and the archive
> "alias" does the archive magic AND does the majordomo list magic all at the
> same time.
>
> Finally, I'm looking for recommendations for a web-o-fied interface into
> that archive (similar, again, to what I used to search the majordomo-users
> alias).
>
> Thanks.
>
> ===
> Bob Gahl Bicycle (Ryan Vanguard) Mobile || @
> ARPA/Internet: bgahl@bawcsa.org || !_ \
> URL: http://www.bawcsa.org/bgahl/ || (*)-~--+--(*)
> "Sahn joong moe low ful how jee yah ching wong" - "When the
> mountain has no tigers, the monkey will also declare himself
> king." Chinese Proverb
Follow-Ups:
References:
|
|
