Installing TLB:

First read through the README file to verify that you have the necessary
version of perl and the associated modules.  Edit the first line of the tlb
script to indicate the location of the perl interpreter on your system.  If
you have the Time::HiRes module, also uncomment the line near the beginning
of the TLB script to get more accurate timings.

Then prepare a configuration file for your mailing lists.  A complete
description of a config file is in complete.tlb; this includes a listing of
all of the options and their documentation.  A very simple config file is
in simple.tlb which duplicates the batching behavior used by the
bulk_mailer program.  There is also a configuration for use at sites
running the Majordomo mailing list software; this configuration (mj.tlb)
allows TLB to be invoked by Majordomo as a mailer instead of Sendmail.
Look in mj.tlb and Majordomo's majordomo.cf for instructions on how to do
this.  The file TIPS has useful tips on some configuration options.

Next perform a test run.  This will ensure that TLB can talk to each of the
delivery hosts you have specified, and will send a message to you through
each of them.  Run the test by entering one of the lines below, replacing
the parenthesized text by any options which your config file requires:

tlb -t your@address (any options your config requires) your.config

or

tlb -t your@address -d56 (options) your.config

to turn on extra instrumentation.  No mail will be sent to your list
recipients; the address file will not even be read.  Then run a dry run
with:

cat test.message | tlb -d255 (options) your.config

which will show you the address lists before and after sorting, the
individual batches, the status of connections as they open and close, any
responses received from the other end of the connections, and the SMTP data
that will be sent.  No mail is actually transmitted, though.

Finally, place TLB in the aliases file.  The exact place to put it varies
depending on how it is to be used and what (if any) mailing list manager is
in place.  In general, if you have an alias with an :include: statement,
replace the include statement with a TLB invocation.  Here is an example
for the Majordomo mailing list manager:

Change

test-list-out: :include: /path/to/test-list

to

test-list-out: "|/path/to/tlb /path/to/test-list.tlb"

or

test-list-out: "|/path/to/tlb -l test-list /path/to/tlb.config"

if you have a single config file for many lists.

A more complicated setup may use the archiving program which comes with
Majordomo, and may also use the Majordomo wrapper program so that all files
can be owned by the Majordomo user:

test-list: "| /path/to/majordomo/wrapper resend -l test-list -h your.host
              test-list-out,nobody"

test-list-out: "| /path/to/majordomo/wrapper tlb -l test-list -a
                  /path/to/mj.tlb",


Note that in this configuration, tlb must be placed in the same directory
as the wrapper.

With a development version of Majordomo, tlb can be specified as the mailer
that resend will call to deliver the message; the aliases required are
simply:

test-list: "| /path/to/majordomo/wrapper resend -l test-list -h your.host
              nobody"

and in majordomo.cf, set:

$mailer = "/path/to/tlb -l $opt_l mj.tlb";

Note that at this time there is no public release of Majordomo that
supports this feature, though it is supported in version 1.94beta1 and up.
See majordomo.cf and mj.tlb for more information.

TLB should operate fine, logging information to syslog on the "mail"
service, with levels "info", "notice" and "warning".  Please report any
problems to Jason Tibbitts <tibbs@hpc.uh.edu>.

Thanks for using TLB!

