

                               -==* JamFlow *==-

                               By James McOrmond

                                January 15, 1996





JamFlow really does not really need documentation in its current form
as it requires no seperate config file, but I figured a quick note at
least, should be done.

JamFlow currently only receives information from the s:JamMail.cfg
file, so it is limited to JamMail systems.

It reads two things out of the jammail.cfg file.  Your outbound
directory (where to search for those .FLO files), and your list of
default domains.

Currently, only one domain can be configured per zone, so if you
have multiple networks using the same zones, JamFlow will likely not
work for you.

This is an example of what JamFlow looks like when its operating on
some outbound files.


-------------------------------------------------------------------------

JamMail_Xferq_ReFlow 0.12 by James McOrmond
Reading Config...
Default Domains: 21
Host AKA's: 1

Scanning "out:" for 4d.?LO files!

out:1.163.139.4.flo for FidoNet#1:163/139.4 -> Reading... (f=0)
out:1.163.139.4.tu0 -> Dots 4, Extension: .TU0 Sending as 00000000.TU0 (0)

out:1.163.329.0.flo for FidoNet#1:163/329.0 -> Reading... (f=0)
out:1.163.329.0.tu0 -> Dots 4, Extension: .TU0 Sending as 000000be.TU0 (0)

out:1.163.411.0.flo for FidoNet#1:163/411.0 -> Reading... (f=0)
out:1.163.411.0.tu0 -> Dots 4, Extension: .TU0 Sending as 00000110.TU0 (0)

out:1.163.578.0.flo for FidoNet#1:163/578.0 -> Reading... (f=0)
out:1.163.578.0.tu0 -> Dots 4, Extension: .TU0 Sending as 000001b7.TU0 (0)

Scanning "out:" for 4d.?UT files!
out:1.163.335.0.cut for FidoNet#1:163/335.0 -> Sending as 16013721.pkt (50)

-------------------------------------------------------------------------

As you can see, there were 4 .FLO files, and one .CUT file in the outbound
directory.

As it goes through each .FLO file, it lists each file in the .FLO file, as
well as the new name for the file if its a mail bundle, and the priority
of the file in brackets.

The .CUT file, is an uncompressed Netmail packet, with a crashmail priority.
Its temporary name is shown, as well as its priority.


The priorities used in JamFlow, are identical to the priorities used in
JamMail itself.  50 = Crash Mail, 30 = Direct Mail, 0 = Normal Mail, and
-50 is Hold.

This is what JamScan looks like when there is no work to do.

-------------------------------------------------------------------------

JamMail_Xferq_ReFlow 0.12 by James McOrmond
Reading Config...
Default Domains: 21
Host AKA's: 1

Scanning "out:" for 4d.?LO files!
None found!

Scanning "out:" for 4d.?UT files!
None Found or Nothing New!

-------------------------------------------------------------------------

Please send me a message if you have any problems with JamFlow.

James McOrmond
jam@jammys.net
1:163/139



ChangeLog:

0.10 - Initial version - only does .?UT files
0.11 - Now doing .?LO files as well.
0.12 - deleting .FLO file, cleaned up priorities - local testing
0.13 - stuff
0.14 - Now truncates bundles marked to be truncated instead of deleting them.

