home *** CD-ROM | disk | FTP | other *** search
Text File | 1976-11-25 | 67.9 KB | 1,713 lines |
- Further Development, Inc. InterEcho Demo Manual - May 1 1996
- ======================================================================
- (c) Copyright 1993-1996 Further Development, Inc. All rights reserved.
-
- ^
- | Further Development, Inc.
- | Further P.O. Box 821864
- ____|____________ South Florida, FL 33082
- (____|____________) USA
- |
- | Development, Inc . Phone 1-954-436-2080 M-F 2pm-8pm EST
- ____|______________________ 1-500-675-0049 5pm-10pm PST
- (____|______________________) Fax 1-954-432-2223
- | BBS 1-954-436-1085
- | Fidonet 1:369/35
- InterMailnet 211:211/101
- E-Mail fdi@furtherdev.com
-
- See our Website at http://www.furtherdev.com
-
- This short manual is a quick guide to help you through the basic
- installation of the demo version of InterEcho. It will not however be
- sufficient for you to learn everything about InterEcho and make a
- perfect setup. To do that, you will need the 90 page manual which you
- will receive when you purchase InterEcho.
-
- This manual on file is also shipped with the registered version of
- InterEcho. It may come in handy.
-
- In the following text and in the setup program, we refer to our front
- end mailer InterMail and our sysop message editor InterEdit. They are
- other products made by us to be used with InterEcho, but they are not
- shipped with InterEcho or with this demo. Free demo versions of them
- are sometimes available on our BBS.
-
- Trademarks
- ----------
- All products by Further Development, Inc. are trademarks or registered
- trademarks of Further Development, Inc. Other brand and product names
- are trademarks or registered trademarks of their respective holders.
-
- Fable of Contents
- -----------------
- 1. System Requirements
- 2. Installation
- 3. Jump Start
- 4. Starting IESetup and InterEcho
- 5. Path and DOS variable
- 6. Mail Processing Status
- 7. Using IESetup
- 8. Message Folders
- 9. Areafix Commands
-
-
- System Requirements
- ===================
- * IBM AT (80286) or higher, or true compatible. An 80386 is recommended.
- * DOS version 3.1 or higher.
- * Hard drive with a minimum of 2 MB of free space. This is sufficient
- for InterEcho alone. Much more space will be needed for the message
- bases and for the inbound and the outbound echomail.
- * 640 KB minimum RAM, with at least 400 KB of DOS memory available
- for InterEcho.
-
-
- Installation
- ============
- * At the DOS prompt, create a temporary directory:
-
- md \temp
-
- * Decompress the InterEcho archive:
-
- pkunzip ie*.zip \temp
-
- * Change directory and start the install program:
-
- cd \temp
- install
-
- * Follow the instructions on the screen. The install program will
- first create the directories, install the files, and then the setup
- program will take you on a guided tour. Remove the temporary
- directory \temp when you are done.
-
- InterEcho shares setup files with our front end mailer InterMail. We
- strongly recommend that you install both in the same directory, that
- is c:\im.
-
-
- Jump Start
- ==========
- * Install on hd
- * Move AREAFIX.HLP from \im to \im\system
- * Verify paths in IESetup, specially the netmail folder
- * Enter links
- * Enter echomail areas in your BBS (makewild, pcbsetup, scfg)
- * Select your BBS in Message Folder Template
- * Import echomail folder setup from your BBS, FIDONET.NA or AREAS.BBS
- * Connect links to echomail areas
- * Run INTRECHO /TAG
- * Check the log file
- * Enter a few test messages on your BBS
- * Test scan by runing INTRECHO
- * Check the log file
- * Test toss a small echomail packet from \im\secure
- * Check the log file
- * Enter netmail folders on your BBS
- * Import netmail folder setup in IESetup
- * Enter a few test netmail messages on your BBS
- * Test scan netmail with INTRECHO
- * Check the log file
- * Back up inbound mail BEFORE you toss them the first few days
- * If something goes wrong, check the log, check folder and link setup,
- read the manual, correct the error, delete the dupe database
- IEDUPFIL.IDX and re-toss the backup.
- * Automate the start of InterEcho from batch file AFTER you have
- verified that everything works ok.
-
-
- Starting IESetup
- ================
- If you are already using InterMail or an earlier version of
- InterEcho, you will need to verify the configuration in the IESetup
- program before you run this version of InterEcho for the first time.
-
- * At the DOS prompt, change to your InterEcho main directory:
-
- cd \im
-
- * To start the setup program, type
-
- iesetup
-
- There is only one command line option for IESetup:
-
- iesetup /install
-
- It will take you one the same guided tour as the install program did.
-
-
- The first time you start InterEcho
- ----------------------------------
- InterEcho tags exported messages in your message base. This stops
- InterEcho from exporting the same messages the next time. No such tags
- exist the first time you run InterEcho. To stop InterEcho from
- exporting all of your messages, you need to run InterEcho in the
- tag mode, but only if you have defined folders that already exist and
- contain messages. If your folders are new or empty, you do not need
- to run InterEcho in the tag mode, since there are no messages to
- mark.
-
- If you do export all your messages by mistake, InterEcho will create
- fairly huge outbound echomail packets in the directory for outbound
- echomail \IM\OUTECHO. You should just delete them. If you do not
- delete them, and your mailer sends the files to your links, they may
- or may not classify your messages as dupes and delete them
- accordingly. If they do not delete them, your dupe messages may
- travel farther along the echomail paths and you may receive
- embarrassing comments, complaints or threaths on decapitation.
-
- * At the DOS prompt, change to your InterEcho main directory:
-
- cd \im
-
- * The first time you start InterEcho (note the spelling,
- the missing "e"), type:
-
- intrecho /tag
-
-
- Start InterEcho manually
- ------------------------
- At any time you may start InterEcho manually from the DOS prompt:
-
- * Change to your InterEcho main directory:
-
- cd \im
-
- * Start the InterEcho program:
-
- intrecho
-
-
- Command line options for InterEcho
- ----------------------------------
- You may combine the options as you wish on the same line.
-
- intrecho
- Contrary to some other echomail processors, InterEcho will
- give you full performance when you start it without any options.
- This includes tossing, scanning and areafix. As a result, you
- don't need to worry about cryptic command line options just to
- get the job done.
-
- intrecho /areafix
- Process messages to Areafix in the InterMail netmail folder.
- (If the %RESCAN option is used, the message base will also be
- scanned for mail.)
- This is also done if you start InterEcho without any command
- lines options at all. Use this switch only when you don't want
- InterEcho to do the full job.
-
- intrecho /mem
- Gives extra memory debug information on the bottom line. Does
- not affect the operation. Shows number of file handles in
- use, free (unused) memory and the lowest level of free memory
- during the run.
-
- intrecho /noareafix
- Do not process messages to Areafix in the InterMail netmail
- folder. Use this switch only when you want other programs to
- see messages to Areafix.
-
- intrecho /notify
- Create netmail status reports to links that have the "Send
- notify list" checkbox selected in IESetup -> Links -> Edit ->
- Areafix.
-
- intrecho /scan
- Scan the message base and export newly locally entered mail to
- your up and downlinks. This is also done if you start InterEcho
- without any command lines options at all. Use this switch only
- when you don't want InterEcho to do the full job, for example
- when a caller logs of the BBS.
-
- intrecho /tag
- Use the first time you scan messages in a non-empty message
- folder. InterEcho marks all messages as exported, but does not
- export anything.
-
- intrecho /toss
- Toss inbound echomail to up and downlinks, and import to the
- local message base. This is also done if you start InterEcho
- without any command lines options at all. Use this switch only
- when you don't want InterEcho to do the full job.
-
- intrecho /unknown
- Re-toss mail from the folder for Unknown areas. Make sure you
- have added the missing areas (or correct spelling errors) before
- you re-toss.
-
- intrecho /unsecure
- Re-toss mail from the folder for Unsecure mail. Make sure you
- have added the correct packet password before you re-toss, or
- that you have selected Unsecure mode under Application ->
- InterEcho -> Options.
-
-
- If you do scan out mail after every caller logs off the BBS, you
- don't need to scan out again when you toss inbound mail. You will
- save a few seconds by letting InterEcho do only the tossing and
- areafix processing:
-
- intrecho /toss /areafix
-
-
- Exit from InterMail 2.2
- -----------------------
- If you are running InterMail and a BBS, you probably want to automate
- the processing of echomail. You will get the best performance by starting
- InterEcho from the same batch file that you use to start InterMail,
- that is IMRUN.BAT. By letting InterMail exit with an errorlevel, for
- example 50, you may use the errorlevel in the IMRUN.BAT to start
- InterEcho. For more information about errorlevels, see your DOS
- manual. You may only run one copy of InterEcho at a time, and only
- one of your mailer tasks may start InterEcho. The following describes
- three methods.
-
-
- Exit InterMail on received echomail file
- ----------------------------------------
- You may set InterMail to exit and run InterEcho a few seconds after a
- compressed echomail file is received. InterMail will check the file
- name, and does not exit when other types of files are received. This
- method works well if you receive only a few echomail files per day.
-
- * Start IMSetup, the InterMail 2.2x setup program
- * Go to Manager -> Events.
- * Select an event and go to the Behavior sub menu.
- * Set Exit when mail is received = Yes.
- * Go to Mailer -> Errorlevels.
- * Set Received mail = 50.
- * Change your IMRUN.BAT according to one of the methods described below.
-
-
- Exit InterMail on timed event
- -----------------------------
- By setting up one or more timed events per day, you may do the mail
- processing during off-peak hours, when not so many users are calling.
- This method works well if you receive many files per day and it is
- this method we recommend for multi-line setup of InterMail.
-
- * Start IMSetup, the InterMail 2.2x setup program.
- * Go to Manager -> Events.
- * Create a new event with the Ins key.
- * Make it an external event, by setting the event Tag to X.
- * Set the Errorlevel = 50.
- * Change your IMRUN.BAT according to one of the methods described below.
-
-
- Exit InterMail by pressing a function key
- -----------------------------------------
- The function keys in InterMail "waiting for a call" screen may be
- defined to run external programs. This feature is nice to combine
- with other methods of starting InterEcho, since it allows you to
- process the mail with just one single keystroke.
-
- * Start IMSetup, the InterMail 2.2x setup program.
- * Go to Mailer -> Function keys.
- * Press the key you want to assign, for example F2.
- * Enter the title to appear in listing, for example InterEcho
- * To exit with an errorlevel, enter in the Action field:
-
- ?50
-
- * Set the Pause = No and Check = No.
- * Change your IMRUN.BAT according to one of the methods described below.
-
-
- Start InterEcho from a batch file
- ---------------------------------
- The following text describes several similar methods of using
- errorlevel 50 to start InterEcho from IMRUN.BAT.
-
-
- Direct from the if-errorlevel line
- ----------------------------------
- The syntax of the DOS batch command "if errorlevel" lets you enter
- any DOS command after the errorlevel, to be executed when this
- particular errorlevel is set. A program name is a valid DOS command,
- and therefore you may simply enter "intrecho" after the errorlevel.
-
- :loop
- c:
- cd \im
- im
- if errorlevel 100 dobbs
- if errorlevel 50 intrecho
- goto loop
-
- Starting InterEcho cannot be easier than this and, in most cases,
- does not have to be more complicated.
-
-
- Jump to another section with GOTO
- ---------------------------------
- If you would like to run other programs in the same event as you
- process mail, you may want to jump to another section in IMRUN.BAT:
-
- :loop
- c:
- cd \im
- im
- if errorlevel 100 dobbs
- if errorlevel 50 goto procmail
- goto loop
-
- :procmail
- rem enter_whatever_commands_you_like_here
- intrecho
- rem enter_whatever_commands_you_like_here
- goto loop
-
-
- Start other batch file
- ----------------------
- If you plan to do so many things that you feel the need of running
- InterEcho from a separate batch file, DOS allows you two methods of
- starting the other batch file. The first one starts the ANOTHER.BAT
- but will not make DOS automatically continue in IMRUN.BAT after
- ANOTHER.BAT ends. It is therefore very important that the last
- command in your ANOTHER.BAT starts IMRUN.BAT again:
-
- :loop
- c:
- cd \im
- im
- if errorlevel 100 dobbs
- if errorlevel 50 another.bat
- goto loop
-
- This is a sample of your ANOTHER.BAT:
-
- :start
- rem enter_whatever_commands_you_like_here
- intrecho
- rem enter_whatever_commands_you_like_here
- c:\im\imrun.bat
-
- Use CALL to start other batch file
- ----------------------------------
- The second method uses the CALL statement that makes the IMRUN.BAT
- continue on the line after the CALL when the other batch file ends:
-
- :loop
- c:
- cd \im
- im.exe
- if errorlevel 100 dobbs
- if errorlevel 50 call another.bat
- goto loop
-
- This is a sample of your ANOTHER.BAT, started with the CALL statement:
-
- rem enter_whatever_commands_you_like_here
- intrecho
- rem enter_whatever_commands_you_like_here
-
- Note that the last command does not start IMRUN.BAT. If you manually
- test this ANOTHER.BAT by starting it direct from the DOS prompt, it
- should return to DOS when it ends. It should not return to IMRUN.BAT.
-
-
- Run InterEcho after a BBS caller logs off
- -----------------------------------------
- If you want to export messages entered by your BBS callers
- immediately after they log off, you may start InterEcho from your
- POSTCALL.BAT or whatever batch file name you use for similar tasks:
-
- :start
- rem enter_whatever_commands_you_like_here
- intrecho /scan
- rem enter_whatever_commands_you_like_here
- :end
-
- Another method is to start InterEcho direct from the EXEBBS.BAT. This
- is a sample for Wildcat! 4.0, that works with most modems:
-
- @echo off
- set MNP=
- if %4 == /Arq set MNP=MNP
- if %4 == /Arq/Hst set MNP=MNP
- if %4 == /Arq/V32 set MNP=MNP
- if %4 == /Arq/Mnp set MNP=MNP
- if %4 == /Arq/Mnp/Mnp5 set MNP=MNP
- if %4 == /Arq/Lapm set MNP=MNP
- if %4 == /Arq/Lapm/V42bis set MNP=MNP
- if %4 == /Arq/Hst/Hst set MNP=MNP
- if %4 == /Arq/Hst/Hst/Mnp5 set MNP=MNP
- if %4 == /Arq/Hst/Hst/V42bis set MNP=MNP
- if %4 == /Arq/V32/Mnp set MNP=MNP
- if %4 == /Arq/V32/Lapm set MNP=MNP
- if %4 == /Arq/V32/Lapm/V42bis set MNP=MNP
- if %4 == /Arq/V32/Lapm/Mnp/Mnp5 set MNP=MNP
- cd \wildcat
- wildcat /b %1%MNP% %3
- cd \im
- intrecho /scan
- imrun.bat
-
- You may save some processing time by just doing the scanning and no
- tossing.
-
-
-
- Path and DOS variable
- =====================
- Both InterEcho and IESetup read the IM environment variable, if it is
- available, to determine the location of the setup file FD.SYS. This
- means you do not have to change directories to \im before starting
- InterEcho. We recommend you add this line to your AUTOEXEC.BAT file:
-
- set IM=C:\IM
-
- The program files do not have to be present in the directory from
- which you start them. DOS will find them if you add the \im directory
- to your PATH statement in your AUTOEXEC.BAT. Sample:
-
- path c:\;c:\dos;c:\im
-
-
-
- Mail Processing Status
- ======================
- InterEcho gives you a full real-time status report during the mail
- processing. This information is useful for fine tuning your system.
-
- ┌─ Inbound ──────────────────────────┬─ Outbound ────────────────────────┐
- │ Processed (tossed) mail: 0 │ Scanned message base: 0 │
- │ Echomail imported: 0 │ Echomail exported: 0 │
- │ BBS netmail: 0 │ BBS netmail exported: 0 │
- │ InterMail netmail: 0 │ InterMail netmail packed: 0 │
- │ Msgs in unlisted areas: 0 │ Echomail for links: 0 │
- │ Unsecure mail (no psw): 0 │ │
- │ Dupes: 0 │ │
- └────────────────────────────────────┴───────────────────────────────────┘
-
- - Processed (tossed) mail
- Number of processed inbound messages, both echomail and netmail.
-
- - Echomail imported
- Number of inbound echomail messages imported to your message folders.
- Passthru echomail is not included.
-
- - BBS netmail
- Number of incoming netmail messages saved to the BBS netmail folder.
-
- - InterMail netmail
- Number of incoming netmail messages saved to the InterMail netmail
- folder.
-
- - Msgs in unlisted areas
- Number of incoming echomail messages with an Area tag not listed
- in the Message Folder manager.
-
- - Unsecure mail (no psw)
- Number of incoming echomail and netmail messages with a bad packet
- password or received by InterMail from a link with no session password.
-
- - Dupes
- Number of duplicate messages received.
-
- - Scanned message base
- Number of scanned messages, both echomail and netmail. Messages in
- folders that has no new mail may not be counted.
-
- - Echomail exported
- Number of echomail messages exported from your message base or BBS.
-
- - BBS netmail exported
- Number of netmail messages exported from your BBS. This value will
- be zero if you don't offer netmail for your BBS callers.
-
- - InterMail netmail packed
- Number of netmail messages moved from the InterMail netmail folder
- and compressed along with the outbound echomail.
-
- - Echomail for links
- Number of echomail messages forwarded to your links, both uplinks
- and downlinks.
-
-
-
- Using IESetup
- =============
- This program lets you configure the operation of InterEcho. You may
- define your echomail areas, your links, paths, netmail behavior,
- colors etc. After starting IESetup, you will see the desktop and
- the main menu.
-
- Global
- ------
- The Global menu contains the most frequently used menus and all the
- settings that are shared with InterMail, InterEcho and InterEdit (the
- InterMail message editor).
-
- Global -> Message Folders
- -------------------------
- Described further down.
-
- Global -> Links
- ---------------
- A network link is a connection between a node and a hub. Your links
- are the nodes and hubs you connect with to send and receive echomail
- and netmail. The link (hub) you call to get the majority of the mail,
- is called an Uplink. If you forward echomail to other nodes, you may
- call them Downlinks. The Link manager lets you define the settings
- for all your links, both up and downlinks. InterEcho and IESetup will
- support more than a thousand links.
-
- The Link manager lists all your links. The field at the bottom
- displays some extra information about the highlighted link.
-
- - Press the New button when you want to add a new link.
-
- - Edit a link by double clicking with a mouse, or move to it with
- up/down arrows and press Enter or Alt-E.
-
- Edit and add New links
- ----------------------
- The Link dialog box lets you add and change the settings for a link.
-
- - Network Address
- The network address is a node number that may consist of four parts;
- the zone, the net, the node and the point number, separated with a
- colon, a forward slash and a point. You should use the point number
- only when the address is a point node. InterEcho uses the address as
- the destination of netmail with attached echomail files. If the
- address is a regular node, you only need to enter the first three
- parts. Example:
-
- 1:249/1
-
- If the link is a point, include the point number:
-
- 1:369/102.17
-
- - Sysop name
- InterEcho will place the Sysop name in the header of outbound
- netmail. Enter the real name of the person, for example:
-
- John Doe
-
- - Access to Groups
- The Area Group letter provides a means for you to set (and block out)
- groups of echomail areas for your links. You must select one or more Area
- Group letters for each link. The Area Group letter must be a capital
- letter from A to Z. For example:
-
- ABC
-
- - AKA to use on mail
- Select one of your AKAs (Node Addresses) to use as sender address
- for mail to this link.
-
- - Netmail msg status
- These settings cover the status of netmail messages to your link.
-
- + None
- No flag at all gives you the chance to fully control the treatment of
- netmail through the InterMail routing file, for example in a nightly
- event.
-
- + Hold
- Use the Hold flag when you want to be sure no mail gets sent on your
- dime. Note that the routing command Unhold in InterMail doesn't
- affect the Hold flag in a message.
-
- + Crash
- Use the Crash flag when you want InterMail to send the mail at once,
- for example on toll free local calls.
-
- + Direct
- The Direct flag in netmail overrides your routing rules in InterMail,
- which is proper for echomail. Avoid routing of echomail. We suggest
- you select the direct flag for all your links.
-
- + Hold Direct
- Combines the Hold flag and the Direct flag features as listed above.
-
- + Crash Direct
- Combines the Crash flag and the Direct flag features as listed above.
-
- - Comment
- Here you may enter extra information about the link, for example phone
- number and street address. Does not affect the operation.
-
- - Options
- + Accept unsecure mail
- When selected, InterEcho will process mail from this link, even if
- the expected packet password is wrong/missing or if the mail was
- found in the directory for inbound unsecure files (usually \im\files),
- that is if your mailer has no session password defined for this link.
- When not selected (default), InterEcho will toss unsafe mail from this
- link to the folder for unsecure mail.
- This option can not be set if you have selected to run InterEcho in
- the Unsecure Mode. See Application -> InterEcho -> Options.
-
- MsgAreas button
- The screen shows a list of all echomail folders, both locally stored
- areas and Passthru areas. You may connect areas by clicking with the
- mouse or pressing the space bar. Press and hold the space bar to
- connect many areas in an easy way.
-
- Areafix button
- If you are feeding mail to others, you may want to let them change
- their settings from remote, without your intervention. The Areafix
- area manager lets them do it. This feature is disabled if you leave
- the Areafix password field blank.
-
- - Allow link to use
- You may disable or enable each and every Areafix command for this
- link. A selected checkbox lets the link use the command. An empty
- checkbox will block the link from using the command. For more
- info on the following commands, see the Areafix section below.
-
- [X] %NOTIFY
- [X] %PAUSE
- [X] %RESUME
- [X] %RESCAN
- [X] %HELP
- [X] %AREAFIXPSW
- [X] %LIST
- [X] %QUERY
- [X] %UNLINKED
- [X] %STATUS
- [X] %NOTE
-
- + Forward Areafix
- Select if you want Areafix to connect this link to unlisted areas
- found in one of the Echolists (see below). If not selected, Areafix
- will not honor requests of areas that are not listed locally (in your
- Message Folder manager, see below).
-
- - Current options
-
- + Send notify list
- If selected, InterEcho will create a netmail status report to this
- link, when started with the /NOTIFY option. This setting may be
- changed from remote by the link, if you have enabled the use of the
- %NOTIFY command.
-
- + Paused
- If selected, InterEcho will not prepare mail for this link. Useful
- for vacations. The link may temporarily turn off the mail flow,
- without disconnecting from areas. This setting may be changed from
- remote by the link, if you have enabled the use of the %PAUSE and
- %RESUME commands.
-
- - Areafix password
- Enter a password to enable areafix. If you leave this field blank,
- InterEcho will not honor areafix requests from this link. The link
- needs to place this password on the subject (Re:) line in messages
- to areafix.
-
-
-
- MsgPacket button
- When feeding mail to others, it's useful to be able to adjust the
- look of your outbound mail. Your links may prefer a specific
- compression program, they may not be able to process certain file
- names or they may want to limit the size of the archives.
-
-
- - Allow Areafix
- You may disable or enable each and every Areafix command for this
- link. The list of checkboxes works like the list under the Areafix
- button. A selected checkbox lets the link use the command. An empty
- checkbox will block the link from using the command.
-
- [X] %COMPRESS
- [X] %ARCNAME
- [X] %ARCAGE
- [X] %ARCSIZE
- [X] %PKTSIZEKB
- [X] %PKTSIZEMSG
- [X] %PKTPSW
-
- - Compression
- All common archive formats are supported. Some are built-in and does
- not require additional compression programs. Others do and we assume
- they are placed in a PATH listed directory. The internal PKZIP 1.10
- compatible method is faster than the others, and is recommended.
- InterEcho appends new outbound *.PKT files to existing archives if
- possible, that is, if the archive has not been transfered by InterMail.
-
- InterEcho will automatically select the proper de-compression method
- for inbound mail.
-
- ARC (internal)
- ARJ
- LZH
- PAK (internal)
- PKT (no compression)
- RAR
- ZIP1 (1.10 internal)
- ZIP (2.0+ external)
- ZOO
-
- - Archive name
- There are six options to name the outbound archives. You don't have
- to worry about the names of inbound archives, because InterEcho will
- look for them all, no matter what you have defined for the outbound
- names.
-
- + MO1 - always the same
- No matter what day of the week or the size of the file, InterEcho
- will keep adding new PKT files to this single archive. Useful for
- links with low volume or links that transfers the mail less than
- once a week.
-
- + SU1 - 1 per day
- InterEcho creates one archive file per day, and keep adding
- PKT files no matter the size of the archive. The file name
- extensions will be MO1, TU1, WE1, TH1, FR1, SA1 and SU1.
-
- + SU9 - 10 per day
- InterEcho creates up to ten archive files per day. For example,
- the file name extension for a Monday will be MO1, MO2, MO3, MO4,
- MO5, MO6, MO7, MO8, MO9 and MO0. Note that we use one through nine
- and end with a zero. The size of the first nine is determined by the
- Archive max size. The last archive has no max limit. It will grow as
- much as needed. This naming convention is the most common one and
- should work with most other mail tossers.
-
- + SUF - 16 per day
- Works just like the "10 per day" option, but in addition, the last
- character for a Monday can be MOA, MOB, MOC, MOD, MOE and MOF. This
- naming convention is also common.
-
- + SUZ - 36 per day
- Works just like the "16 per day" option, but in addition, we use the
- rest of the alphabet for the file name extension, for example MOG,
- MOH and MOZ. This naming model is useful for links with high volume
- mail flow, but may not be supported by other mail tossers.
-
- + SZZ - 1296 per day
- Works just like the "36 per day" option, but in addition we use the
- middle character of the file name extension, for example M11 and TAQ.
- This gives a whopping 36*36=1296 combinations per day, but may not be
- supported by other mail tossers. Use with caution!
-
- - Del old archive
- NOT IN USE YET - WILL BE ADDED LATER.
- Set number of days you like to keep mail archives. Older archives
- will be deleted. If set to zero (default), no archives will be deleted.
- This feature is useful if you want to keep some control over the
- volume of untransmitted mail, for example if the link suddenly stops
- polling for mail and the mail starts to pile up on your hard drive.
- Use with caution!
-
- - Archive size
- You may set the max size for the compressed archives, but it's only
- approximate, because InterEcho estimates the compressed size before
- the compression is done.
-
- - Max PKT size
- You may set the max size of outbound PKT files in kilobytes.
-
- - Messages per PKT
- You may set the max size of outbound PKT files in number of messages.
-
- - Packet password
- Enter a password for higher security against bogus echomail. The
- password will be written to all outbound echomail packets to this
- link, and the password will be expected in all inbound echomail
- packets from this link. It is necessary that the link enter the same
- packet password in his/her mail tosser setup. Note that the packet
- password has nothing to do with the areafix password or the session
- password. If you receive a mail packet without packet password, from
- a link for which you have defined a packet password, InterEcho will
- toss the content to the folder for Unsecure messages. If you leave
- this field blank, no packet password will be used for this link. By
- default no packet passwords are used and will not be used until you
- manually enter them.
-
- Note: You may override the demand for correct packet password by
- NOT selecting to run in SECURE mode, enforce passwords, etc. in the
- Option dialog under Application -> InterEcho.
-
-
-
- Global -> Address
- -----------------
- When you join networks, you will receive node numbers to identify who
- you are. The node number may consist of four parts, the zone, the
- net, the node and the point number. They are separated with a colon,
- a forward slash and a period. You may use the point number only when
- the address is a point node. If the address is a regular node, you
- only need to enter the first three parts. The list of addresses is
- used in other sections of IESetup.
-
-
- Global -> Paths and files -> System
- -----------------------------------
- The install program creates all needed subdirectories and files. You
- may change all directory names, but we strongly recommend against it.
- Technical support and future upgrades will be easier if you follow
- our recommendations. If you need to place some of the files on
- separate hard drives, then please use the same directory names.
-
- - Config file dir
- This directory contains configuration files. We recommend:
-
- c:\im\system\
-
- - Rcvd Files (no pwd)
- Files received by InterMail from nodes with whom you have no session
- password will be stored here. We recommend:
-
- c:\im\files\
-
- - Secure Files (pwd)
- Files received by InterMail from nodes with whom you do have a
- session password will be stored here. We recommend:
-
- c:\im\secure\
-
- - Nodelist
- Not used by InterEcho. InterMail and InterEdit looks here for the
- nodelist. We recommend:
-
- c:\im\nodelist\
-
- - Swapping
- This directory is used for swapfiles, for example when InterEcho
- is swapping out to run external programs for file compression. Place
- this directory on a ramdrive for faster performance. We recommend:
-
- c:\im\
-
- - Semaphore
- InterEcho, InterMail and InterEdit use this directory for mutual
- semaphore files. It is important that they share the same directory.
- Place this directory on a ramdrive for faster performance. We
- recommend:
-
- c:\im\sema\
-
-
- Global -> Paths and files -> Msg base Paths
- -------------------------------------------
- - Hudson message base directory
- If you plan to use the Hudson or Goldbase file format for local
- storage of messages, you need to enter the path where it is
- located. Example:
-
- c:\hudson\
-
- - Wildcat! main directory
- If you use Wildcat! BBS, enter the path to the Wildcat! BBS home
- directory. For Wildcat! 3.5 - 3.91 we recommend: c:\wc30\
- and for Wildcat! 4.0 we recommend: c:\wildcat\
-
- - Synchronet main directory
- If you use Synchronet BBS, enter the path to the Synchronet BBS home
- directory. Example: c:\sbbs\
-
-
- Global -> Local Users
- ---------------------
- You may enter up to ten persons as local users. A local user in this
- context, is a person like you that has access to your keyboard. It
- may be your spouse, employee or similar. A local user is not a caller
- to your BBS, even if the caller connects through a LAN. To avoid
- confusion, we simply call them "BBS callers".
-
- InterEcho does not use the security levels (they are reserved for
- InterEdit), but if you define passwords, IESetup will ask you for a
- password when started.
-
-
- Global -> General -> Options
- ----------------------------
- - Your Country code
- Not used by InterEcho. InterMail use the direct dial code for your
- country when compiling the nodelist, for example 1 for USA and
- Canada; and 46 for Sweden.
-
- - Fast kbd repeat rate
- If you want to use the built in "keyboard accelerator" function,
- but use it only if you are NOT loading Fastkey or a similar program.
-
- - 101/102 key Enhanced keyboard
- InterEcho always uses 101/102 keyboard.
-
- - Screen flickers
- If you are using a CGA screen you may select this option to avoid
- screen flicker.
-
- - Force 24 hour format
- Not used by InterEcho. All time information will use 24-hour
- military format.
-
-
- Global -> General -> Origin Lines
- ----------------------------
- An origin line is a type of signature at the bottom of an echomail
- message, usually giving the system name and location. Both InterEcho
- and InterEdit may use them. You should not enter your node address
- here, because the AKA you have defined in your Message Folders will
- automatically be added at the end of the line, by either InterEcho or
- InterEdit. You may enter up to 20 origin lines, and later pick one
- of them in the Message Folder manager. Feel free to be creative.
- Origin lines that are too long will be truncated to the correct
- length, with a warning message in the log.
-
-
- Application -> InterEcho
- -----------------------
- This group of menus covers all settings that are unique for InterEcho.
-
-
- Application -> InterEcho -> Preferences -> Colors
- -------------------------------------------------
- The two lists show all colored items used by the application. Scroll
- to the one you want to change and select background and foreground
- colors. The square in the lower right corner shows a sample of the
- color combination.
-
-
- Application -> InterEcho -> Preferences -> Display
- --------------------------------------------------
- You can change the screen mode. Not all video adapter cards support
- these modes.
-
-
- Application -> InterEcho -> Preferences -> Memory & Swapping
- ------------------------------------------------------------
- You can set the application to swap to EMS instead of to the hard
- drive.
-
-
- Application -> InterEcho -> Preferences -> Options
- --------------------------------------------------
- - Import BBS netmail for local users, i.e. those listed in IESetup.
- NOT IN USE YET - WILL BE ADDED LATER.
-
- - Only import netmail for listed users
- NOT IN USE YET - WILL BE ADDED LATER.
-
- Note: InterEcho imports all netmail to the BBS netmail folders, if
- such folders exist, with exception of netmail to sysop, or more
- exact, to one of the ten names listed under Global -> Local Users. In
- a future release, when the two options above are implemented, you
- will be able to import netmail for sysop to the BBS netmail folders,
- and you will be able to make a list of BBS callers for whom you wish
- to import the netmail.
-
-
- - Use AREAS.BBS instead of internal database
- Select this option in case you insist on using an external Areafix
- utility. It will force IESetup and InterEcho to use AREAS.BBS and to
- not use the IEAREAS.CFG, just like InterEcho 1.02. In addition if you
- set this option, InterEcho will ignore any received Areafix requests,
- even if you use the /AREAFIX command line option.
-
- - Run in SECURE mode, enforce passwords, etc.
- If not selected (default), InterEcho will not use packet passwords or
- secure mail, leaving you wide open for attacks. If selected,
- InterEcho will ensure that you don't receive or pass on bogus mail.
- We strongly recommend that you select this option and use all the
- built in security features.
-
- - Days to keep dupe data
- Enter the number of days you want to keep information about messages
- for dupe checking. The more days you enter, the bigger the dupe
- database and the better dupe checking.
-
-
- Application -> InterEcho -> Preferences -> Log
- ----------------------------------------------
- You have the option to save all the information written to the screen
- when InterEcho runs, to a log file for your perusal. This log file
- may be very useful if you run into problems. Use this file, or
- excerpts from it, whenever you contact us or others for technical
- support.
-
- - Automatic daily renaming
- You have the option to automatically start a new log file with a new
- name every day after midnight. The file name will be of the style
- IEYYMMDD.LOG, where YY = year, MM = month and DD = day. For example
- the log file for August 17, 1994, will be named IE940817.LOG. This is
- useful when you want to keep the current log file small. This file
- name convention also makes it much easier to find the log file for a
- particular day.
-
- - Log path + filename
- You may define the name and path for the file in several different ways.
-
- + If you want your log files named in the IEYYMMDD.LOG format, select
- Automatic daily renaming, enter the path, trail with a backslash,
- but skip the file name. This is the method we recommend. Example:
-
- c:\im\
-
- + If you want a single log file named IE.LOG (and keep the same file
- name every day), do not select Automatic daily renaming, enter the
- path, trail with a backslash, but skip the file name. Example: c:\im\
-
- + If you want to define your own path and filename (and keep the same
- file name every day), just type the path and filename you prefer,
- but do not select Automatic daily renaming. Example: c:\log\tosser.log
-
- + If you select Automatic daily renaming and then type your own path
- plus filename, the name you entered will be used the first day, but
- the second and following days, your log files will be named in the
- IEYYMMDD.LOG format, in the directory you specified.
-
- + If you do not want a log file, leave the path field empty and do not
- select Automatic daily renaming.
-
- - Log message types
- Select what type of messages you want InterEcho to save to the log
- file. We recommend that you select the last option DEBUG: All of the
- above. It will make your log file larger, but the extra debug
- information is very useful if you run into problems.
-
-
- Application -> InterEcho -> Preferences -> Paths
- ------------------------------------------------
- - Outbound echomail
- InterEcho saves the outbound echomail files here. It's important that
- you do not combine this directory with the directory InterMail uses
- for outbound netmail packets. We recommend: c:\im\outecho\
-
- - Work dir unsecure
- Used for unsecure temporary files. It is very important that no other
- program uses this directory. We recommend: c:\im\echowork\
-
- - Work dir secure
- Used for secure temporary files. It is very important that no other
- program uses this directory. We recommend: c:\im\worksafe\
-
-
- Application -> InterEcho -> Preferences -> Echo lists
- -----------------------------------------------------
- The Echo list manager lets you define lists of echomail areas. This
- information is needed for the Areafix Forward feature. When a
- downlink requests a new area via Areafix, and that particular area is
- not listed in the ordinary Message Folder manager, InterEcho may turn
- around and request this area from your uplink, and at the same time
- create the area in the Message Folder manager and connect the
- requesting link. The autoadded area will be of the Passthru type (not
- available on your BBS) and will get Group letter 'A'. InterEcho will
- search the Echolists (for area tags) in file name alphabetical order.
-
- The Forward Areafix feature is powerful, but can sometimes be
- misused, therefore is it protected with several layers of security:
-
- * The field for the downlink Areafix password must not be empty.
- * The link must know his/hers Areafix password.
- * The "Allow link to use Forward Areafix" option must be selected.
- * One or more Echolists must be defined, with correct settings such
- as path and uplink Areafix password.
- * The link must have at least one of the same Group letters as the Echolist.
- * The requested areatag must be listed in the qualified Echolist.
-
- Only if all the above is set and used correctly, will areas be auto-added.
-
-
- - Echolist file
- Enter a file name, for example FIDONET.NA
-
- - Echolist path
- Enter the path where the Echolist file is located, for example:
- E:\BBS\FIDO\
-
- - Comments
- Here you may enter extra information about the echolist. Does not
- affect the operation.
-
- - Link
- Select the uplink from one of your links. This is the link from where you
- get the major part of your mail.
-
- - Groups
- Select one or more Groups. Only links with minimum one matching Group
- letter, will be able to connect a new area via Areafix Forward. If
- you want to block some links out from auto-adding new areas, simply
- make sure they don't have any of the Group letters that you enter here.
-
- - Forward Areafix program
- Enter the name of the Areafix program that your uplink uses,
- for example: areafix
-
- - Forward Areafix password
- Enter the Areafix password that your uplink assigned for you.
-
-
-
- Application -> InterEcho -> Areafix synonyms
- --------------------------------------------
- Here you may enter up to 16 different names for Areafix. These
- synonym names may be used by your links when sending area manager
- requests. The list gives them a chance to continue to use whatever
- name they have grown used to, for example RAID.
-
-
-
- Application -> InterEcho -> Preferences -> Area Group names
- -----------------------------------------------------------
- The Area Group letters provides a means for you to set (and block out)
- groups of echomail areas for your links. You must select one Area
- Group letter for each message folder and you must select one or more
- Area Groups for each link. In this menu you may add some extra
- information about the group. You may, for example, enter networks
- names. It will make it easier to identify the group. Area Group names
- are optional and will not affect the operation of InterEcho.
-
-
- Application -> IESetup -> Preferences -> Options
- ------------------------------------------------
- - Create backup (*.BAK) files
- IESetup lets you save backups of the config files. We recommend you
- select this option. The backup may be useful, if a config file
- becomes damaged.
-
- - Auto save desktop on exit
- NOT IN USE YET - WILL BE ADDED LATER.
- IESetup lets you save the desktop when you exit. The desktop is the
- place where you work with ASCII files.
-
-
- File, Edit and Window (on the top menu line)
- --------------------------------------------
- A good ASCII file editor comes with IESetup. It may be useful
- whenever you need to do a quick change to an ASCII setup file. You
- may open several windows to edit ASCII files and you may arrange them
- on the desktop. This menu lets you tile, cascade, move, zoom and
- close all windows.
-
-
- Global -> Message Folders
- -------------------------
- The most frequently used part of IESetup is the manager for your
- message folders. Here you may add, delete, rename and change their
- settings. This is not a message editor, however. To read and reply to
- messages, you need a message editor like InterEdit. If you are not
- familiar with the word "folder", think of it as a conference
- (Wildcat!), an area (PCBoard), a board (Hudson & Goldbase), a
- sub-board (Synchronet) or a directory (*.msg). A folder is a place
- for messages. The messages may be of certain type or of a specific
- topic. You may have just a few folders or you may have thousands and
- they may each contain thousands of messages. Your hard drive space,
- your RAM memory and/or your BBS software set the limits.
-
- InterEcho does not use all of the options in IESetup. We included
- them so users of InterMail and InterEcho should not have to switch
- between two setup programs to do almost the same job. The Message
- Folder manager in IESetup completely replaces the folder manager in
- InterMail IMSetup 2.2x.
-
- If you are running a BBS, we suggest that you first enter your
- folders in the BBS software setup program (Makewild, PCBSetup, Scfg,
- etc.). That way you may later use the built-in quick-import function
- in IESetup, thus saving a lot of typing. You may also import from
- FIDONET.NA and AREAS.BBS type of files.
-
- If you for some reason cannot import your folders, you will have to
- type them in manually. Some hints may come in handy:
-
- - Make a list on paper of message areas available on your BBS. The
- list should include name, area tag and location in your BBS (either
- board #, conference #, path or filename).
-
- - An alternative is to download (or areafix query) a list of
- available areas from your uplink, print it out and write the location
- of the folders in your BBS. With the list beside you, the typing will
- be much simpler. Be especialy careful with the spelling of area tag
- names.
-
- The dialog box for Message Folders works in much the same fashion as
- the dialog box for Links. You will see a list of all your message
- folders. The leftmost character in the list marks the folder type.
- N means BBS Netmail, E means Echomail and L means Local messages.
- Folders without a letter in the leftmost column are of a special
- type, see below for more information. The field at the bottom
- displays some extra information about the highlighted folder.
-
-
- Template
- --------
- The folder template is used when you create new folders, either by
- pressing the New button or by importing folder setup from file. All
- the settings in the template will be copied to the new folder. This
- makes it very fast and convenient to add many folders. The Folder
- Template dialog box works in the same fashion as the Message Folder
- dialog box described below.
-
- Import
- ------
- This feature lets you quickly import folder configurations from other
- programs and from common echomail area lists such as FIDONET.NA and
- AREAS.BBS, thus saving you hours of typing. IESetup creates new
- folders with information from the folder template and the areas you
- have selected to import. Before you start to import, take your time
- and fine tune the settings in the folder template, specially the
- folder type and the message format.
-
- - Import file type
- Select the list or program you want to import from.
-
- + AREAS.BBS
- This file is used by many programs for storage and transfer of
- area and link information. IESetup imports both the location of
- the folders, area tags and the node numbers of the links. Make sure
- you have entered the links in the Link manager before you import the
- areas. Passthru areas area marked with a "P" in AREAS.BBS and
- IESetup will set the message format to the Passthru type, even if
- your folder template is set to another format.
-
- + FIDONET.NA
- This is a list of all echomail areas available on the FidoNet North
- America backbone. The list is updated every week and can be
- downloaded from most FidoNet nodes. Some Fido style networks
- maintain similar lists in the same format. If you type a filename
- in the import file field, instead of selecting one of the pre-
- defined types, IESetup will assume that the file uses the same
- format as FIDONET.NA.
-
- + PCBoard 15.0+
- IESetup lists all the areas you have defined in PCBSetup. IESetup
- honors the echomail flag in PCBSetup by setting those folders to the
- echomail type and the others to Local. Netmail folders must be
- changed manually to Netmail type.
-
- + Synchronet
- IESetup lists all the sub-boards you have defined in SCFG. IESetup
- honors the three methods of storage: Self-packing, Fast Allocation
- and Hyper Allocation, but you will not be able to see or change
- the storage method in IESetup. Whatever method you have selected in
- SCFG will be used. Please make sure that the file name is valid in
- the "Internal Code" field in SCFG for each sub-board.
-
- + Wildcat! 3.5-3.91 and Wildcat! 4.0
- IESetup lists all the conferences you have defined in Makewild. The
- conference type (echomail, local) is determined by the settings in
- your template, except for conferences that are defined as FidoNet
- netmail in Makewild.
-
- - Path and filename
- The path and filename for the program or list should be filled out
- automatically in most cases. Change if necesary.
-
- IESetup reads the config file or area list you selected and matches
- the list against the list of folders you already have defined in
- IESetup. Existing area tags are not listed. The remaining list is
- presented to you as a picklist to the left. The right side lists all
- the areas/conferences that you want to import. You select an area by
- moving the area name from the left side to the right side. There are
- several ways to do this:
-
- * Double click on the area name in the left list.
- * Select the area in the left list and press Alt-A or click on the
- right-pointing button.
- * Select the area in the left list and use the Tab key to move to
- the right-pointing button and press Enter. (Our testing has shown
- that this is not a very popular method...)
-
- IESetup starts to create new folders and fill them with information
- from the folder template and the list you import from. Some
- information may have to be entered manually depending on what program
- or file you import from. If that is the case, IESetup will ask you
- for the additional information in a pop-up window, one for each area.
-
-
- Export
- ------
- This feature lets you quickly export folder configurations to an
- AREAS.BBS file.
-
-
- Edit folder - Add new folder
- ----------------------------
- The Message Folder dialog box (under the Edit button and New button)
- lets you add and change the settings for a folder.
-
- - Folder type
- There are different types of folders. The first three types are
- available when you add and edit folders. The other four types are
- "hardcoded" and you cannot remove or rename them.
-
- + Echomail
- Define one folder of this type for each echomail area you use.
-
- + Local
- InterEcho does not scan or toss to a Local folder. Use this folder
- type with InterEdit to access local folders on your BBS, or to better
- organize your private messages.
-
- + BBS Netmail
- If you run a BBS you may want to let your callers exchange netmail
- with callers on other BBSs. Make sure your BBS supports netmail,
- and a method for the caller to enter the destination node address.
-
- Hints for netmail in PCBoard 15.x: The "ROUTE" extended header line
- can be used to specify the destination address for outbound netmail
- or enter it on the first line of the message, in one of the
- following two methods:
-
- To: 1:369/102
- @>1:369/102
-
- + InterMail Netmail
- This is the most important folder of them all. You will not be able
- to move, remove, rename or inactivate this folder. InterEcho will
- create empty-body messages here, which attach outbound echomail
- files. InterEcho will also move some incoming netmail to this
- folder. If you are not using our front end mailer InterMail, change
- the path for this folder to where your mailer stores netmail.
-
- + Unlisted areas
- InterEcho moves inbound echomail messages with unknown area tags to
- this folder. This happens if you misspelled an area tag. It will also
- happen if you receive a new echo from your uplink before you had time
- to create a new folder. Use InterEdit to view them. You will not be
- able to remove or rename this folder, but you may set it inactive in
- the option menu. InterEcho automatically deletes all messages with
- unknown area tag, if the folder is inactive.
-
- + Unsecure messages
- InterEcho moves mail received in the directory for inbound unsecure
- files \IM\FILES to this folder. It also moves messages without packet
- password to this folder, if a packet password is defined in the Link
- manager. To avoid this, simply set up a session password and/or a
- packet password with your link. You cannot remove or rename this
- folder, but you may set it inactive. InterEcho deletes all unsecure
- messages if the folder is inactive. We suggest you keep this folder
- active.
-
- + Dupes
- You may receive echomail messages that you have already received
- before. They are duplicate messages, or "dupes". They are created by
- an incorrectly configured mail tosser somewhere else, or by echomail
- links going in circles. InterEcho keeps a database of information
- about all echomail messages you have received and sent. InterEcho
- compares incoming echomail with information in the dupe database and
- moves dupes into this folder. View them with InterEdit and delete
- them. You will not be able to remove or rename this folder, but you
- may set it inactive in the option menu. InterEcho deletes dupes
- automatically, if the Dupe folder is inactive. We suggest you keep
- it active.
-
- If you (for test purpose) let InterEcho process the same inbound
- echomail file a second time, all the new messages are considered
- duplicates. You may override this by manually deleting the dupe
- database (c:\im\system\iedupfil.idx) before you toss the second
- time.
-
- - Message format
- InterEcho supports several different files formats for local storage
- of messages. This makes it possible to use InterEcho with many of
- the available BBS programs on the market. You may switch from one BBS
- to another without much more effort than changing a couple of options
- per message folder. InterEcho also allows you to freely mix different
- message formats. If you plan to use InterEcho with InterEdit, but
- without a BBS, *.msg is your best choice. They are described below.
-
- - Board #, Conference #, Filename, Path, Sub-board
- The name and location of message folders are described somewhat
- differently in each message format and each BBS software. Common
- names are Conference, Board, Sub-board, Path and Area. This field
- will change the label and type of input field depending on which
- message format you have chosen in the previous field.
-
- + *.msg
- Hundreds of software programs support the *.msg
- ("star-dot-emm-ess-gee") message format well. It is slow, however,
- because each message is stored in a separate file. The file name is
- the number of the message and the extension is always MSG. You must
- create a separate directory for each folder. Use, for example, the
- first eight characters in the area tag as a directory name:
-
- c:\im\mail\scuba\
-
- + Goldbase
- Similar to Hudson, but with room for many more messages. Select
- from the pick list the same Board number as your BBS uses, for
- example :
-
- 27
-
- + Hudson
- Supported by several BBS programs and a lot faster than *.msg. The
- only real drawback is the relatively limited space for messages.
- Around 15500 messages will fit before you need to purge. Select
- from the pick list the same Board number as your BBS uses, for
- example :
-
- 37
-
- + JAM
- This format is used by BBS software like ProBoard, RemoteAccess
- and others. Enter the same drive, path and filename as you did in
- the BBS software. Do not trail with a backslash and do not enter a
- file name extension. For example:
-
- c:\pcb\fido\scuba
-
- + PCBoard 15.0+
- This format is used by the PCBoard BBS software version 15.0 and
- higher.
-
- * You may place several conferences in the same directory. Enter
- the same drive, path and filename as you see in PCBSetup. Do not
- trail with a backslash and do not enter a file name extension:
-
- c:\pcb\fido\scuba
-
- * Or, if you wish to place each conference in a separate directory:
-
- c:\pcb\fido\scuba\scuba
-
- Hints for echomail in PCBoard: On page 2 of your conference setup
- in PCBSetup, you must set "Echomail in conference" to Yes. You may
- also want to set "Force echo on all messages" to Yes, "Disallow
- private messages" to Yes, "ORIGIN info in messages" to No and
- "Prompt for ROUTE info" to No. Set "Level to save file attachment"
- and "Level to request return receipt" high enough to disable their
- use, since most echomail areas don't allow them.
-
- + Synchronet
- This format is used by Synchronet BBS software version 2.11. Enter
- the same path+filename as you see in Scfg. Note that the filename
- extension MUST NOT be entered, and that the there MUST NOT be a
- trailing backslash after the filename.
- Hints for netmail: Enter C:\SBBS\DATA\MAIL in the Filename field.
-
- + Wildcat! 3.5-3.91
- This format is used by Wildcat! BBS software from version 3.5 up
- to 3.91. Enter the same conference number as you see in Makewild,
- for example:
-
- 85
-
- + Wildcat! 4.x
- This format is used by the Wildcat! version 4.0 and higher, including
- version 4.11. Enter the same conference number as you see in Makewild,
- for example:
-
- 62
-
- + Passthru
- If you plan to forward echomail to downlinks, but have no interest
- in keeping the messages available on your BBS or in InterEdit, you
- may define the folder as a Passthru. This makes InterEcho send the
- echomail in the same manner as with the other message formats, but
- not waste any space by saving them locally. If you later change your
- mind and would like to view the messages, you can just switch the
- format type and keep links and other settings. You cannot enter a
- path or board #, simply because none of these messages are stored
- locally on your hard drive.
-
- - AKA to use
- Select the sender address for messages entered in this folder. The
- address will be added to the end of the origin line in echomail
- folders. The address will be used as sender address for BBS Netmail
- folders.
-
- - Title
- Enter the name you would like to see in the folder list. If you
- cannot come up with anything else, enter the area tag.
-
- - Area Tag
- Each incoming echomail message contains an area tag. The area tag is
- the actual conference name used by the network. InterEcho compares
- the area tag from the inbound echomail message with the list of area
- tags you have entered. If the area tag is found in one of your folder
- definitions, InterEcho will toss the message to this folder. The area
- tag is the only information InterEcho uses to determine where to toss
- the message. InterEcho will not be able to find the correct folder if
- you spell the area tag wrong. These messages will then be tossed to
- the folder for Unlisted areas.
-
- - Comment
- The comment line is optional. It is not really needed for the
- operation of InterEcho, but it is a good place for a short comment
- about the folder.
-
- - Origin Line
- An origin line is a type of signature at the bottom of an echomail
- message, usually giving the system name and location, sometimes with
- quite a bit of personal flair.
-
- InterEcho adds the AKA you selected to the end of the Origin line.
- Make sure they are not too long to fit on one line in your message
- editor, otherwise they will be truncated. An origin line is not
- allowed to be wrapped.
-
- - Group
- Each folder must be assigned to an Area Group. There are 26 Area
- Groups available, and you may define them as you wish. We recommend
- that you define one group letter per echomail network. The group
- letter lets you more easily identify which network the area belongs
- to. In the Link manager you may select the groups to which each link
- is connected. This provides a method off blocking some areas.
-
- - Links button
- The screen shows a list of all links. You may connect links by
- clicking with the mouse or pressing the space bar. Press and hold the
- space bar for to easily connect many links. Note that you must
- connect both uplinks and downlinks. This dialog looks and works very
- similarly to the one under Global -> Links -> Edit/New -> MsgAreas.
-
- - Seen-By button
- Each exported echomail message has a list of addresses to which you
- have sent the message. The list will be used by your links to
- determine to whom they should toss the message. They will not toss
- messages with your address in the Seen-By list, back to you.
-
- Normally you only need to add your main address, but if you
- participate in several networks, you may want to add more of your
- AKAs to the list. This menu gives you the chance to pick the
- addresses you wish to use.
-
- - Password button
- This option is not used by InterEcho. A folder may be password
- protected in InterEdit. This means that even if the folder is visible
- to the local InterEdit user, he/she will have to enter the correct
- password in order to access it.
-
- - Options button
- This dialog box gives you the chance to fine tune the behavior of the
- folders. Some options are not available with some folder types. They are
- shown in gray and will not accept input, or they may not even be visible
- at all. Some options are not used by InterEcho, but by InterEdit.
-
- + Inactive
- Useful if you want to discontinue using the folder for a short
- period of time, but do not want to delete it. InterEcho will not
- toss to or export from an inactive folder.
-
- + Read-only
- This option is not used by InterEcho. InterEdit will not let you
- create a new message in a Read- only folder.
-
- + Restricted
- This option is not used by InterEcho. If the folder is restricted,
- messages with the Private status will not be accessible to the
- InterEdit user unless they are addressed to (or written by) him or
- her. Messages without the private status can be accessed by anyone,
- even in a restricted folder.
-
- + Allow local export
- This option is not used by InterEcho. InterEdit will only let you
- copy, move, print or export a message to file from a folder with this
- option selected.
-
- + Use Translation tables
- This option is not used by InterEcho. InterEdit uses character
- translation tables when reading and writing messages if this option
- is selected. Useful if you would like to see country specific
- characters in an echo that does not support them.
-
- + Tiny SEEN-BYs
- If selected, InterEcho strips unnecessary addresses from the SEEN-BY
- list on exported messages, in order to make them smaller. InterEcho
- will only place your links in the tiny list. Ask your uplink if you
- should use this option.
-
- + Allow Private status
- Some BBS software, like PCBoard, offers the option of Private status
- even for echomail messages. InterEcho does not export private
- messages if this option is not selected.
-
- + Allow high ASCII
- If not selected, InterEcho strips characters with an ASCII value
- above 127. Select this option in folders where you allow high ASCII
- graphics, ANSI or national characters like ñ, é, ç, ä etc.
-
- + Preserve formatting
- InterEcho does not adjust the format of the message body if this
- option is selected. This is useful for example in ANSI conferences
- supported by PCBoard and sometimes for gated Internet newsgroups.
-
- + Hidden
- Select this option if you never want to list this area in Areafix
- messages, even if some links may have access to it.
-
- + Visible
- Select this option if you always want to list this area in Areafix
- messages, even if some links may not have access to it.
-
- + Mandatory
- This option lets you prevent links from disconnecting this echo.
-
- + Default message status
- This option is not used by InterEcho. Sets default status flags for
- messages you create with InterEdit, in netmail folders only.
-
- + Default message priority
- This option is not used by InterEcho. Sets the default priority for
- messages you create with InterEdit. Only available in netmail folders.
-
- + Add Origin/Tear line
- Sets what program should create the Origin line and the Tear line.
- If you choose InterEcho, any existing Origin line and Tear line
- will be over written upon export. If you choose InterEdit, existing
- Origin lines and Tear lines will be kept, but if they do not exist,
- InterEcho will set them anyway. Only available in echomail folders.
-
-
- Areafix Commands
- ================
-
- <area> - Connect to a specified area.
- -<area> - Disconnect from a specified area.
- %HELP - Request Areafix help: this text.
- %LIST - List all areas available to you.
- %QUERY - List connected areas.
- %UNLINKED - List unconnected but available areas.
- %STATUS - Status report of your current settings.
- %RESCAN <area> - Scan out and send all mail in the specified area.
- %PAUSE - Temporarily stop sending mail in all areas.
- %RESUME - Resume from pause.
- %NOTIFY <ON|OFF> - Turn on/off periodical status reports.
- %COMPRESS <method> - Select archiver among: PKT, ARC, ARJ,
- LZH, PAK, RAR, ZIP1, ZIP and ZOO.
- %NOTE - Write message to sysop.
- %AREAFIXPSW - Change Areafix password.
- %ARCNAME <option> - Select name and number of archives per day.
- MO1 - always the same
- SU1 - 1 per day
- SU9 - 10 per day
- SUF - 16 per day
- SUZ - 36 per day
- SZZ - 1296 per day
- %ARCAGE - Set number of days to save mail.
- %ARCSIZE - Set max size of compressed archive in kb.
- %PKTSIZEKB - Set max size of PKT files in kb.
- %PKTSIZEMSG - Set max size of PKT files in number of messages.
- %PKTPSW - Change PKT password.
- --- - End of msg. Everything below is ignored.
-
- Please note that some of the options above may not be available.
- The sysop has the option to disconnect any and all of them.
-
-
-
- End of manual. When you purchase InterEcho, you will receive a
- comprehensive printed manual with an additional 60 pages, pictures,
- screen grabs, references, index, glossary, table of contents etc, etc.
-
- If you have any questions, please do not hesitate to contact us.
-
- ^
- | Further Development, Inc.
- | Further P.O. Box 821864
- ____|____________ South Florida, FL 33082
- (____|____________) USA
- |
- | Development, Inc . Phone 1-954-436-2080 M-F 2pm-8pm EST
- ____|______________________ 1-500-675-0049 5pm-10pm PST
- (____|______________________) Fax 1-954-432-2223
- | BBS 1-954-436-1085
- | Fidonet 1:369/35
- InterMailnet 211:211/101
- E-Mail fdi@furtherdev.com
-
- See our Website at http://www.furtherdev.com
-