Tips on Alternative Mail Setup:

You run your regular export just as you always did as well as your
regular import so that you can bring in the routed mail you have
picked up.

You will be sending out mail to your regular hub, but receiving PUBLIC
mail via the alternative import.  In your postlink.cfg file, or an
additional .cfg file, whichever you prefer, you tell postlink which
channels you are bringing in mail via the alternative system and that
takes care of the public mail for you.

You do a regular import of mail for your routed mail. Your local site
runs as it always did.  Only the hub you call site is set up
differently.

After you get your routed mail from your hub you run postlink caller.cfg
/continue which will put the routed mail in the .prv files (if you are a
hub) and your board if you are a node or run import mode set to
automatic. Then whenever you wish, you will take the alternative packet
you got from the satellite and bring it in by running postlink
/altimport.

To back this up make the following changes in your setup in tmanage.

For your local site you keep the regular configuration.

for the hub you call you make the following changes:
turn off allowed public incoming - no channels
turn off active incoming - no channels (these come into your hub via
your alternative import packet)

Remember: you run your regular export, which you probably have set at
automatic - then you run postlink caller.cfg and it does its thing,
creating the preamble, making your Uxxx.zip to upload.  You call, go in
the door, upload that, take down your routed objects and go away.  Then
some other time, when you have the satellite packets, you bring in the
public mail.

Some further tips on how to set up for the satellite - henceforth called
alternative mail delivery:

You only run altimport and never the altexport. Only I should run
altexport!  You continue to call your hub, in order to upload all the
regular mail from your system and pick up your routed mail.  You get all
the public mail from the alternative mail site!

You run your regular export just as you always did as well as your
regular import so that you can bring in the routed mail you have
picked up from your hub.  You do your regular thing with the postdoor
to send in your new mail and pick up the routed objects.

You will be sending out mail to your regular hub but receiving PUBLIC
mail via the alternative import.

You can create an altimp.cfg file or add the necessary configuration
options to your postlink.cfg file.  Whichever you wish.

In either your altimp.cfg file or postlink.cfg file, you tell postlink
which channels you are bringing in public mail via the alternative
system and that takes care of the public mail for you.  So you do a
regular import of mail for your routed mail (objects as there may be
private files as well although in the future I will send out network
files via the alternative mail.) Here are the configuration options for
alternative mail importing:

ALT-IMP-CHANNELS=1-1300
LOG=ALTIMP.LOG
ALT-IMP-DIR=C:\POSTLINK\ALTIMP

(I like to keep the log separate as it is easier for me to look at as
my postlink.log is humongous)

Your local site runs as it always did.  Only the hub you call site is
different.  After you get your routed mail from your hub you run
postlink caller.cfg /continue which will put the routed mail in the
.prv files (if you are a hub) and your board (whether you are a hub or
a node) as long as you have your import mode set to automatic.

(If as a hub you have your import mode set to manual you of course
have to run postlink /import after the caller.cfg /continue option - as
usual) This is all usual here.  Nothing different.

The differences. You will take the alternative packet you got and bring
it in by running postlink /altimport.

The software is now written so that it assumes that any channel which
you export mail in, ie your allowed public outgoing and active public
outgoing, are channels that you are willing to accept private, routed
objects in as well.
