![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to sbbsecho.src CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Synchronet] / sbbs / sbbs2 / echo / docs|
Return to sbbsecho.src CVS log | Up to [Synchronet] / sbbs / sbbs2 / echo / docs |
1.1 root 1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20: SBBSecho
21: Version 1.22
22: Updated 02/15/96
23:
24: FidoNet Packet Tosser for Synchronet BBS Version 2
25:
26: Copyright 1995 Digital Dynamics
27:
28: PO Box 501
29: Yorba Linda, CA 92686
30:
31: Voice: 714-529-6328 BBS: 714-529-9525 V.32/V.32bis
32: FAX: 714-529-9721 714-529-9547 V.FC
33: Fido: 1:103/705 ftp: netcom.com /pub/sb/sbbs
34:
35:
36: Table of Contents
37: =================
38: &&Contents
39:
40: Introduction....................................................@@INTRO___
41: Terminology.....................................................@@TERMS___
42: Installation....................................................@@INSTALL_
43: AREAS.BBS Format................................................@@AREASBBS
44: Configuration...................................................@@CONFIG__
45: Running SBBSecho................................................@@EXECUTE_
46: Command Line Switches...........................................@@SWITCHES
47: Area Manager Remote Commands....................................@@AREAFIX_
48:
49: Introduction
50: ============
51: &&Introduction
52: $$INTRO___
53:
54: SBBSecho is a full-blown FTN echomail program (tosser/scanner) for Synchronet
55: BBS version 2. SBBSecho is level III implementation of the SMB v2.00
56: specification including support for HyperAllocated and LZH compressed message
57: bases.
58:
59: It is intended to replace FTSC-1 (*.MSG) compatible echomail programs (GEcho,
60: Squish, FastEcho, Alexi/Mail, etc.) and SBBSFIDO with a single program
61: incorporating the standard features of echomail programs without the .MSG
62: phase (consuming disk space and time).
63:
64: You will not need to use SBBSFIDO (*.MSG import/export utility for Synchronet)
65: or any echomail programs after you have installed SBBSecho.
66:
67: Terminology
68: ============
69: &&Terminology
70: $$TERMS___
71:
72: FTN
73: ~~~
74: FidoNet Technology Network: Any network using FidoNet standards for addressing,
75: mail packets, mail sessions, node lists, etc.
76:
77: Zones, Nets, Nodes, and Points?
78: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
79: FTN node addresses are like phone numbers, they are made up of multiple
80: components (four to be exact). The components are: zone, net, node, and point.
81: Each component is specified by a decimal (base-10) number, separated by symbols
82: (no spaces):
83:
84: Zone:Net/Node.Point
85:
86: The zone represents the continent (if FidoNet) or the network number (if other
87: FTN network). All FidoNet nodes in North America have a zone 1 address. When
88: the zone is specified in an address, it is the first component and must be
89: followed by a colon. If the zone is not present in an address, the local
90: system's zone is assumed.
91:
92: The net represents the network number of the FTN node. Duplicate net numbers
93: may exist between zones. If the net number is not present, the local system's
94: net is assumed.
95:
96: The node number specifies an exact FTN node within a network. The node number
97: is the only required element of an FTN node address.
98:
99: The point is an optional component which specifies a sub-node that does not
100: directly receive mail and is also not listed in the main FTN node list, but
101: instead gets all its mail from its boss-node (zone:net/node.0). When the point
102: is not specified, 0 (zero) is assumed (i.e. 1:2/3 and 1:2/3.0 are identical)
103: which indicates the system is not a point node address.
104:
105: A 2D (2 dimensional) address refers to an FTN address containing just the
106: net and node numbers (i.e. 103/705).
107:
108: A 3D (3 dimensional) address refers to an FTN address containing the zone,
109: net, and node numbers (i.e. 1:103/705), specifically excluding the point number
110: if it exists.
111:
112: A 4D (4 dimensional) address refers to an FTN address containing the zone,
113: net, node, and optional point numbers (i.e. 1:103/705.1).
114:
115: A 5D (5 dimensional) address refers to an FTN address consisting of a standard
116: 3D or 4D address with an appended "@domain" (i.e. 1:103/[email protected]).
117:
118: Attach or FLO Mailer?
119: ~~~~~~~~~~~~~~~~~~~~~
120: If you are using FrontDoor, InterMail, D'bridge, SEAdog, Dutchie, or any other
121: ArcMail *.MSG attach-style mailer, you are using what we will refer to as an
122: "Attach Mailer".
123:
124: If you are using BinkleyTerm, Portal of Power, or any other FLO/CLO/HLO/DLO
125: style mailer, you are using what we will refer to as a "FLO Mailer".
126:
127: Both types are supported equally by SBBSecho.
128:
129: NetMail
130: ~~~~~~~
131: Point-to-point (usually person-to-person) direct or routed messages.
132:
133: EchoMail
134: ~~~~~~~~
135: Group or conference messages of a particular subject matter. Usually
136: distributed on a regional or continental (e.g. FidoNet Zone 1 backbone) scale.
137: FTN style echomail areas have a unique area tag (name) associated with them to
138: distinguish each area from the others.
139:
140: Packet
141: ~~~~~~
142: An FTN packet is a group of one or more messages contained in a single
143: uncompressed file. Packets may contain echomail and/or netmail messages.
144: Packets usually have a .PKT extension, although outbound NetMail packets for
145: FLO Mailers will have .?UT extensions (where ? is either O, C, D, or H). The
146: first eight characters of the filename may be anything, but are usually decimal
147: digits representing the date and time the packet was created. SBBSecho creates
148: temporary outbound packet files with a .PK_ extension and then renames them to
149: .PKT when they're completed. If you find any .PK_ files in your outbound
150: directory, don't worry. SBBSecho will find them the next time it is run and
151: continue packing them and sending them on their way.
152:
153: Bundle
154: ~~~~~~
155: An FTN bundle is a single file archive of one or more (usually compressed)
156: packets. Bundles will have file extensions where the first two characters
157: represent the day of the week the bundle was created (MO, TU, WE, TH, FR, SA,
158: and SU) and the third character of the extension is a number or letter. The
159: first eight characters of the filename may be anything, but are usually
160: hexadecimal digits representing the FTN node address (or relative address) of
161: the system that created the bundle. SBBSecho changes the file extension of bad
162: inbound bundles to .MO_, .MO-, or .MO.
163:
164: Areafix/Area Manager
165: ~~~~~~~~~~~~~~~~~~~~
166: Areafix is a synonym for area manager (the very first FTN area manager
167: program was called AreaFix). Area manager capabilities (remote adding/removing
168: of areas, changing compression type, etc) are built into SBBSecho, so therefore
169: no external area manager program is required. If you are not an FTN hub, then
170: the area manager portion of SBBSecho will probably not get any use on your
171: system.
172:
173: Installation
174: ============
175: &&Installing SBBSecho
176: $$INSTALL_
177:
178: To begin, copy the SBBSECHO.EXE, ECHOCFG.EXE, and AREAMGR.HLP files into your
179: Synchronet EXEC directory (usually C:\SBBS\EXEC), copy the SBBSECHO.CFG file
180: into your Synchronet CTRL directory (usually C:\SBBS\CTRL), and copy the
181: SBBSECHO.DOC file into your Synchronet DOCS directory (usually C:\SBBS\DOCS).
182:
183: If you plan on using the 32-bit DOS, OS/2, or Windows 95/NT version of
184: SBBSecho, you will need to put the appropriate SBBSECHO.EXE file into your
185: Synchronet EXEC directory (unzip OS2.ZIP for the OS/2 version, DOS4G.ZIP for
186: the 32-bit DOS version, or WIN32.ZIP for the Windows 95/NT version). If
187: you get memory allocation errors running the 16-bit DOS version or desire
188: improved performance, you will want to run one of the 32-bit versions.
189:
190: Add the SBBSCTRL and SBBSNODE environment variables to your AUTOEXEC.BAT.
191: Example:
192:
193: SET SBBSCTRL=C:\SBBS\CTRL
194: SET SBBSNODE=C:\SBBS\NODE1
195:
196: Note: The node number used for the SBBSNODE environment variable is not
197: important, use your NODE1 directory.
198:
199: These environment variables must be present for SBBSECHO and ECHOCFG to
200: function correctly. Type "SET" at the DOS prompt to be sure they are listed
201: correctly.
202:
203: You will also need to modify your existing MAILER.BAT (or FDRUN.BAT, IMRUN.BAT,
204: etc) file to accomodate the use of SBBSecho, or replace it with the MAILER.BAT
205: included with SBBSecho. If this is your first time setting up FidoNet, you will
206: not currently have a MAILER.BAT file set up, so use the one that is included
207: and modify it so that it reflects the proper drive letters and directories.
208:
209: Next, SBBSecho expects to find the file AREAS.BBS in your Synchronet DATA
210: directory (usually C:\SBBS\DATA) unless you have overridden the default name
211: and/or location using the ECHOCFG program. The format of this file is very
212: similar to the standard AREAS.BBS (which many echomail programs use, or can
213: at least export their native area file to this format - i.e. GEcho's GSETUP).
214:
215: SCFG can also export your sub-boards to AREAS.BBS, but you're probably better
216: off modifying the AREAS.BBS file you're already using (if you are) or
217: converting your current echomail program's area file to AREAS.BBS. This is
218: because SCFG assumes the sub-board short name will be the same as the area's
219: tag (as shown in your echo list), but this may not always be the case - unless
220: you imported an AREAS.BBS or FIDONET.NA file into SCFG to begin with).
221:
222: AREAS.BBS Format
223: ================
224: &&AREAS.BBS Format
225: $$AREASBBS
226:
227: Lines beginning with a semicolon (;) are considered comments, and are ignored.
228:
229: Each line is in the following format:
230:
231: CODE TAG UPLINKS
232:
233: Where:
234: CODE is the internal code of the sub-board. Any unrecognized internal
235: codes are considered "Passthru" (not imported to your BBS).
236:
237: TAG is the FidoNet tag as shown in your echo list (i.e. FIDONET.NA).
238: If this is '*', then it will be considered a "badecho" area
239: and will receive all messages for areas not otherwise specified
240: in this file.
241:
242: UPLINKS is a list of FidoNet addresses which you wish to export mail
243: to. At the very least, your hub's address should be listed
244: here. Your address should NOT be listed here. If multiple
245: addresses are specified, you should specify the full 3D address
246: for each.
247:
248: AREAS.BBS Example:
249:
250: SBBS SYNCHRONET 1:3615/50
251: SYNCDATA SYNCDATA 1:3615/50
252: SYNC_SYS SYNC_SYSOPS 1:3615/50
253:
254: The amount of spacing between each element in the line is not important. Each
255: line can be up to 1000 characters in length.
256:
257: So if your OLD AREAS.BBS file is in .MSG format (for example):
258:
259: C:\FD\ECHO\SBBS SYNCHRONET 1:3615/50
260:
261: It must be changed to match the example given above!
262:
263: Configuration
264: =============
265: &&Configuring SBBSecho
266: $$CONFIG__
267:
268: In order to set up SBBSecho for your system you must run the included ECHOCFG
269: program. It should already be located in your EXEC directory. You may want to
270: put your EXEC directory in your DOS search path so you can execute SBBSECHO and
271: ECHOCFG from any drive and directory on your system.
272:
273: Multiple configuration files can be used (but isn't usually required) for
274: multi-mailer systems. The default configuration filename is SBBSECHO.CFG
275: located in your Synchronet CTRL directory. You can override this by specifying
276: the name and location of the configuration file on the SBBSECHO and ECHOCFG
277: command lines. Example:
278:
279: ECHOCFG D:\ECHO1.CFG
280: SBBSECHO D:\ECHO1.CFG
281:
282: If you do not specify a configuration file, ECHOCFG and SBBSECHO will use
283: SBBSECHO.CFG located in your Synchronet CTRL directory.
284:
285: Upon running ECHOCFG you will be brought to the main menu of the configuration
286: program. The path and filename of the configuration file being modified will
287: appear at the top of the menu. Following are screen captures of available menus
288: within the configuration program and an explanation of the options contained on
289: each of them.
290:
291: �[�][?]�������������������������������������������ͻ
292: � C:\SBBS\CTRL\SBBSECHO.CFG �
293: ��������������������������������������������������
294: � �Mailer Type FrontDoor/Attach �
295: � �Maximum Packet Size 250K �
296: � �Maximum Bundle Size 250K �
297: � �Areafix Failure Notification User #1 �
298: � �Registration Number UNREGISTERED �
299: � �Nodes... �
300: � �Paths... �
301: � �Log Options... �
302: � �Toggle Options... �
303: � �Archive Programs... �
304: � �Additional Echo Lists... �
305: ��������������������������������������������������ͼ
306:
307: Mailer Type:
308: Selecting this option will toggle between the mailer types supported
309: by SBBSecho, either FrontDoor (message attach) type mailers or Binkley
310: (FLO file) type mailers. Choose the one that matches your front-end
311: mailer type.
312:
313: Maximum Packet Size:
314: This option allows you to set the maximum size of each outgoing
315: echomail packet.
316:
317: Maximum Bundle Size:
318: Mail packets are normally packed into what are called "bundles" (unless
319: a node is set up to receive uncompressed mail packets). This option
320: allows you to specify the maximum size of each outgoing mail bundle.
321:
322: Areafix Failure Notification:
323: This is the user number of the person where notification of Areafix
324: failures should be sent. Such failures include nodes which are not
325: configured for areafix, nodes using incorrect areafix passwords, and
326: the like. Setting this to 0 will disable this option.
327:
328: Registration Number:
329: Upon registering SBBSecho with Digital Dynamics, you will be given a
330: registration number. You should select this option and enter the
331: registration number you are given here. If you have not yet registered
332: the program, this should say "Unregistered".
333:
334: Nodes...
335: This option allows you to add, remove, and configure nodes that you
336: will be sending mail to. Selecting this option will bring you to
337: a sub-menu which will look similar to the following:
338:
339: �[�][?]�����ͻ
340: � Nodes �
341: ������������
342: � �ALL �
343: � �1:100/ALL �
344: � �1:200/300 �
345: � �2:ALL �
346: � � �
347: ������������ͼ
348:
349: At the Nodes... sub-menu, pressing the INSert key will allow you to
350: add a new node, pressing the DELete key will remove the currently
351: highlighted node number, and pressing ENTER on the currently
352: highlighted node will allow you to edit the options for that particular
353: node from a menu like the following (note that the node number you are
354: editing appears at the top of the window):
355:
356: �[�][?]�������������������������������ͻ
357: � 1:200/300 �
358: ��������������������������������������
359: � �Address 1:200/300 �
360: � �Archive Type ZIP �
361: � �Packet Type 2+ �
362: � �Packet Password �
363: � �Areafix Password �
364: � �Areafix Flags �
365: � �Status None �
366: � �Direct No �
367: � �Passive No �
368: � �Send Notify List No �
369: ��������������������������������������ͼ
370:
371: Address:
372: This is the address of the node you are editing, selecting it
373: will allow you to change this to a different address. Using
374: the "ALL" wildcard in place of one of the address components
375: will allow you to configure settings for all nodes that meet
376: that specication (e.g. all nodes in zone 1 can be specified
377: as 1:ALL or all nodes in zone 1, net 103 can be specified
378: as 1:103/ALL).
379:
380: Archive Type:
381: This is the compression type to be used when packing mail
382: bundles for this node. Selecting this option will allow you
383: to choose from a menu of currently configured archive types,
384: like the following:
385:
386: �[�][?]���������ͻ
387: � Archive Type �
388: ����������������
389: � �ZIP �
390: � �ARC �
391: � �LZH �
392: � �ARJ �
393: � �PAK �
394: � �SQZ �
395: � �ZOO �
396: � �None �
397: ����������������ͼ
398:
399: Selecting "None" will specify that this node is to receive
400: uncompressed packets (no bundles).
401:
402: Packet Type:
403: This is the packet type that will be used when creating mail
404: packets for this node. The default packet type used by SBBSecho
405: is 2+. If you are a "point" address (e.g. 1:100/100.1) you
406: should use either a type 2+ or 2.2 packet since type 2 packets
407: do not support point numbers. Selecting this option will allow
408: you to choose from a menu of currently supported packet types:
409:
410: �[�][?]��������ͻ
411: � Packet Type �
412: ���������������
413: � �2+ �
414: � �2.2 �
415: � �2 �
416: ���������������ͼ
417:
418: Packet Password:
419: This is a password that will be placed into each outgoing mail
420: packet for this node. Passwords are normally used for extra
421: security when sending and receiving mail packets. This node
422: must also have the same packet password defined for your
423: address and SBBSecho must be set up for secure operation (set
424: in the 'Toggle Options' sub-menu) in order for this feature to
425: function properly.
426:
427: Areafix Password:
428: This is the password that will be required by this node (in
429: the subject field) when it sends messages to the area manager
430: (AreaFix).
431:
432: Areafix Flags:
433: When additional echo lists have been defined (from the
434: 'Additional Echo Lists...' sub-menu) these flags determine
435: which echo lists can be used by this node when processing area
436: manager add requests.
437:
438: Status:
439: This option determines the netmail status that will be set
440: when SBBSecho sends out an areafix message or a file attach.
441: Selecting this option toggles between None, Crash, and Hold
442: status.
443:
444: Direct:
445: When set to 'Yes' this option will add a Direct kludge line
446: to messages that SBBSecho sends out (or create DLO/DUT files
447: for FLO mailers).
448:
449: Passive:
450: Setting this option to 'Yes' will prevent messages from being
451: sent to this node without the need for altering the AREAS.BBS
452: file. This is useful for temporarily shutting off the messages
453: to this node. This option can be toggled on and off remotely
454: via an area manager request.
455:
456: Send Notify List:
457: This determines whether or not this node is sent a Notify List
458: when using that command line option in SBBSecho.
459: A Notify List is a netmail sent to the system operator of the
460: node showing options set for the node as well as connected
461: areas.
462:
463: Paths...
464: This option allows you to configure the paths and filenames which are
465: used by SBBSecho. Selecting this option will bring you to the
466: following sub-menu:
467:
468: �[�][?]���������������������������������������������������ͻ
469: � Paths and Filenames �
470: ����������������������������������������������������������
471: � �Inbound Directory <Specified in SCFG> �
472: � �Secure Inbound (optional) None Specified �
473: � �Outbound Directory C:\IM\OUTBOUND\ �
474: � �Area File SCFG->DATA\AREAS.BBS �
475: � �Log File SCFG->DATA\SBBSECHO.LOG �
476: ����������������������������������������������������������ͼ
477:
478: Inbound Directory:
479: This is the directory where SBBSecho should look for inbound
480: mail packets. This is normally taken from whatever has been
481: set in the SCFG program.
482:
483: Secure Inbound (optional):
484: This is an optional directory where SBBSecho should look for
485: secure inbound mail packets.
486:
487: Outbound Directory:
488: This is the directory where SBBSecho will place outgoing mail
489: packets and bundles.
490:
491: Area File:
492: This is the path and filename of the file that SBBSecho will
493: use as it's AREAS.BBS file. By default SBBSecho looks for
494: the file AREAS.BBS in the data directory defined in SCFG.
495:
496: Log File:
497: This is the path and filename of the file that SBBSecho will
498: use when logging events. By default SBBSecho uses the file
499: SBBSECHO.LOG in the data directory defined in SCFG.
500:
501: Log Options...
502: This list allows you to toggle what events SBBSecho should place into
503: the logfile. Selecting this option will bring you to the following
504: sub-menu:
505:
506: �[�][?]����������������������������������ͻ
507: � Log Options �
508: �����������������������������������������
509: � �ALL �
510: � �NONE �
511: � �DEFAULT �
512: � �Ignored NetMail Messages No �
513: � �NetMail for Unknown Users No �
514: � �Areafix NetMail Messages Yes �
515: � �Imported NetMail Messages Yes �
516: � �Packing Out-bound NetMail Yes �
517: � �Routing Out-bound NetMail Yes �
518: � �In-bound Packet Information Yes �
519: � �In-bound Security Violations Yes �
520: � �In-bound Grunged Messages Yes �
521: � �Disallowed Private EchoMail Yes �
522: � �Circular EchoMail Messages No �
523: � �Duplicate EchoMail Messages No �
524: � �Area Totals Yes �
525: � �Over-All Totals Yes �
526: �����������������������������������������ͼ
527:
528: Selecting ALL, NONE, or DEFAULT will toggle all of the options to
529: 'Yes', 'No', or to their default states, respectively.
530:
531:
532: Toggle Options...
533: These options allow you to toggle various features in SBBSecho.
534: Selecting this option will bring you to the following sub-menu:
535:
536: �[�][?]�������������������������������������������������ͻ
537: � Toggle Options �
538: ��������������������������������������������������������
539: � �Secure Operation Yes �
540: � �Swap for Executables Yes �
541: � �Fuzzy Zone Operation No �
542: � �Store PATH Lines in Message Base Yes �
543: � �Store SEEN-BY Lines in Message Base Yes �
544: � �Store Unknown Kludge Lines in Message Base Yes �
545: � �Allow Nodes to Add Areas in the AREAS.BBS List Yes �
546: ��������������������������������������������������������ͼ
547:
548: Secure Operation:
549: When set to 'Yes', SBBSecho will compare the origin of any
550: incoming mail packets to the nodes in the AREAS.BBS file
551: as messages are imported. If a packet password has been
552: defined for that node, it will also be compared to the
553: password contained in the mail packet. Packets and messages
554: failing this security will not be imported.
555:
556: Swap for Executables:
557: SBBSecho relies on external executable programs for extracting
558: and compressing mail bundles. This option tells SBBSecho to
559: swap out of memory when running any of these executables,
560: giving the executable programs more free memory to run in.
561: This option is only used in the 16-bit DOS flavor of SBBSecho.
562:
563: Fuzzy Zone Operation:
564: Some mail programs do not create netmail messages with zone
565: information (INTL kludge line) or may only do so when sending
566: between zones. This is a problem for systems that receive
567: netmail for multiple addresses with different zones (AKAs with
568: different zone numbers). Setting this option to "Yes" allows
569: SBBSecho to guess what the correct originating and destination
570: zone is based on the net and node portions of the destination
571: address in netmail message.
572:
573: Store PATH Lines in Message Base:
574: When set to 'Yes', SBBSecho will store the PATH lines from
575: incoming echomail in the Synchronet message base headers (not
576: the body text). This option is useful for troubleshooting
577: routing/duplicate message problems.
578:
579: Store SEEN-BY Lines in Message Base:
580: When set to 'Yes', SBBSecho will store the SEEN-BY lines from
581: incoming echomail in the Synchronet message base headers (not
582: the body text). This option is useful for troubleshooting
583: routing/duplicate message problems.
584:
585: Store Unknown Kludge Lines in Message Base:
586: When set to 'Yes', SBBSecho will store any unknown kludge lines
587: from incoming echomail in the Synchronet message base headers.
588: This option is useful for troubleshooting problems.
589:
590: Allow Nodes to Add Areas in the AREAS.BBS List:
591: When set to 'Yes', SBBSecho will allow nodes to add areas
592: (via area manager) which are listed in the AREAS.BBS list.
593: When set to 'No', SBBSecho will only allow nodes to add areas
594: from any additionally configured echo lists which they have
595: access to.
596:
597: Archive Programs...
598: This option allows you to add or remove archive programs from SBBSecho.
599: Selecting this option will bring you to the following menu:
600:
601: �[�][?]�������������ͻ
602: � Archive Programs �
603: ��������������������
604: � �ZIP �
605: � �ARC �
606: � �LZH �
607: � �ARJ �
608: � �PAK �
609: � �SQZ �
610: � �ZOO �
611: � � �
612: ��������������������ͼ
613:
614: At the Archive Programs... sub-menu, pressing the INSert key will allow
615: you to add a new archive program. Pressing the DELete key will remove
616: the currently highlighted archive program. And pressing ENTER on the
617: currently highlighted archive program will allow you to edit the
618: options for that particular prgram from a menu like the following (note
619: that the name of the archive program you are editing appears at the top
620: of the window):
621:
622: �[�][?]���������������������������������������������������ͻ
623: � ZIP �
624: ����������������������������������������������������������
625: � �Packer Name ZIP �
626: � �Hexadecimal ID 504B �
627: � �Offset to Hex ID 0 �
628: � �Pack Command Line PKZIP %f %s �
629: � �Unpack Command Line PKUNZIP %f %s �
630: ����������������������������������������������������������ͼ
631:
632: Packer Name:
633: This is the name that will be used to reference this particular
634: archiving program. This is also the name that should be used
635: by nodes using areamanger to change their compression type
636: remotely.
637:
638: Hexadecimal ID:
639: This is a hexadecimal identifier that SBBSecho should look for
640: when determining the compression type used on incoming bundles.
641: In this example we are looking for the ID 'PK', '50' is the
642: hexadecimal value for the letter 'P' and '4B' is the
643: hexadecimal value for the letter 'K'.
644:
645: Offset to Hex ID:
646: This is the byte offset (from the beginning of the file) where
647: the hexadecimal ID for this archive program can be located.
648: In this example we are looking at an offset of 0 bytes from the
649: beginning of the file.
650:
651: Pack Command Line:
652: This is the command line used by this archiving program for
653: compressing files. The '%f' command line specifier will expand
654: to the name of the compressed file, the '%s' command line
655: specifier will expand to the name of the file being compressed.
656:
657: Unpack Command Line:
658: This is the command line used by the archiving program for
659: UNcompressing files. The '%f' command line specifier will
660: expand to the name of the compressed file, the '%s' command
661: line specifier will expand to the path where the file is
662: being extracted to.
663:
664: Additional Echo Lists...
665: This option allows you to add and remove additional echo lists which
666: can be used by SBBSecho for area manager add requests. Normally these
667: will be used in addition to your AREAS.BBS file. If you have the
668: toggle option 'Allow Nodes to Add Areas in the AREAS.BBS List' set to
669: 'No', you MUST create at least one additional echo list if you wish
670: to allow other nodes to add areas via area manager requests.
671:
672: Selecting this option will bring you to a sub-menu listing any
673: additional echo lists you currently have defined:
674:
675: �[�][?]������������������ͻ
676: � Additional Echo Lists �
677: �������������������������
678: � �C:\BACKBONE\FIDONET.NA �
679: � � �
680: �������������������������ͼ
681:
682: Pressing the INSert key will allow you to add a new echo list, pressing
683: the DELete key will remove the currently highlighted echo list, and
684: pressing ENTER on the currently highlighted echo list will allow you to
685: edit information about that list:
686:
687: �[�][?]���������������������������������������������������ͻ
688: � Echo List �
689: ����������������������������������������������������������
690: � �Echo List Path/Name C:\BACKBONE\FIDONET.NA �
691: � �Hub Address None �
692: � �Forward Password None �
693: � �Forward Requests No �
694: � �Echo List Flags BACK �
695: ����������������������������������������������������������ͼ
696:
697: Echo List Path/Name:
698: This is the full path and filename of the echo list you are
699: defining. This list should contain the areatag names of areas,
700: one per line, with any comments seperated from the areatag by
701: at least one space.
702:
703: Hub Address:
704: This is the address of the hub of the conferences contained
705: in this list. If an area is remotely added from this list
706: (using Areafix) this address is automatically added to the
707: AREAS.BBS file.
708:
709: Forward Password:
710: This is the area manager password to use when forwarding
711: requests.
712:
713: Forward Requests:
714: Setting this option to 'Yes' will cause SBBSecho to send a
715: request to the Hub Address specified to turn on an area from
716: this list. This happens when users remotely add areas using
717: Areafix and is not necessary if you are already receiving the
718: conferences in this list (ie: from Planet Connect).
719:
720:
721: Echo List Flags:
722: These are the flags required for a node to be able to gain
723: access to this particular echo list. These flags are defined
724: for each node from the 'Nodes...' sub-menu.
725:
726: Selecting this option will bring you to a sub-menu where you
727: may add and remove flags for this echo list.
728:
729: �[�][?]������������ͻ
730: � Echo List Flags �
731: �������������������
732: � �BACK �
733: � � �
734: �������������������ͼ
735:
736: Running SBBSecho
737: ================
738: &&Running SBBSecho
739: $$EXECUTE_
740:
741: The command line for executing SBBSECHO is very similar to SBBSFIDO, although
742: some command line switches have been eliminated.
743:
744: We suggest you use the following command lines:
745:
746: For importing:
747:
748: C:\SBBS\EXEC\SBBSECHO /LES!
749:
750: For exporting (Attach Mailer):
751:
752: C:\SBBS\EXEC\SBBSECHO /LIN
753:
754: For exporting (FLO Mailer):
755:
756: C:\SBBS\EXEC\SBBSECHO /LINF
757:
758: Remove all references to SBBSFIDO from your batch files (if you have any).
759: See the included MAILER.BAT as an example.
760:
761: Command Lines Switches
762: ======================
763: &&Command Lines Switches
764: $$SWITCHES
765:
766: usage: sbbsecho [cfg_file] [/switches] [sub_code]
767:
768: where: cfg_file is the filename of config file (default is ctrl\sbbsecho.cfg)
769: sub_code is the internal code for a sub-board (default is ALL subs)
770:
771: SBBSecho will execute normally (for Attach Mailer operation) with NO command
772: line switches required. Command lines switches are used to cause SBBSecho to
773: _do_ or _not_ do specific operations. When used, command line switches
774: are prepended by a slash (/) character. Multiple switches can be specified
775: in one grouping (multiple /switch sets are supported, but not required).
776: Switch letters are not case sensitive. The available switch letters and their
777: descriptions are:
778:
779: P: Do not import inbound packets or extract inbound bundles
780: X: Do not delete inbound packets (*.PKT) after they're imported
781: N: Do not import inbound netmail (packetized netmail and *.MSG)
782: D: Do not delete inbound netmail (*.MSG) after they're imported
783: I: Do not import inbound echomail
784: E: Do not export outbound echomail
785: M: Ignore echomail pointers (export all locally created echomail messages)
786: U: Update echomail pointers only (export no echomail messages)
787: T: Do not update echomail pointers (test export)
788: H: Export all echomail messages (including messages imported from FidoNet)
789: J: Ignore recieved bit on netmail (import even though flagged as received)
790: L: Create log file (data\sbbsecho.log)
791: R: Create report of import totals (text\sbbsecho.msg)
792: B: Import locally created netmail too (ignore the local flag)
793: A: Export ASCII characters only (override individual sub-board ex-ASCII strip)
794: F: Create packets for outbound netmail (necessary for FLO Mailer operation)
795: G: Generate notify lists
796: Y: Import netmail for unknown users to sysop (user #1)
797: O: Import all netmail regardless of destination address (unless flagged local)
798: S: Import private echomail override (strip private flag)
799: =: Change existing tear lines to === when exporting
800: !: Notify users via telegram of received echomail messages
801:
802: AREAFIX Commands
803: ================
804: &&Areafix Commands
805: $$AREAFIX_
806:
807: Remote area manager, or areafix, commands are used by uplinks to be able to
808: turn echo areas off and on, list currently connected areas, and more.
809:
810: The following text is from the file AREAMGR.HLP which, after installation of
811: SBBSecho, should be located in your Synchronet EXEC directory. It lists the
812: area manager commands available to the nodes which have been configured using
813: the ECHOCFG program:
814:
815: Address all requests to 'SBBSecho' or 'AreaFix' (without quotes).
816: Your Area Manager password goes on the subject line.
817:
818: In the body of the message to Area Manager:
819:
820: [+]<areaname> Connect an area
821: -<areaname> Disconnect an area
822: %HELP Request this message
823: %LIST Request a list of areas available to you
824: %QUERY Request a list of areas to which you are connected
825: %UNLINKED Request a list of areas to which you are not connected
826: %COMPRESSION <type> Change the compression type (ARC/ARJ/LZH/PAK/SQZ/ZIP/ZOO)
827: %PASSWORD <password> Change your AreaMgr password
828: %RESCAN Request a rescan of newly added areas
829: %ACTIVE Reconnect all temporarily disconnected areas
830: %PASSIVE Temporarily disconnect all connected areas
831: %FROM <address> Remote maintenance, must be the first command
832: %+ALL Connect all available areas
833: %-ALL Disconnect all areas
834: [---] Everything below the tear line is ignored
835:
836: NOTE: A compression type of NONE is also supported for uncompressed packets.
837:
838:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.