home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 2 BBS
/
02-BBS.zip
/
au1_inf.zip
/
U1.INF
(
.txt
)
< prev
Wrap
OS/2 Help File
|
1995-07-03
|
56KB
|
1,704 lines
ΓòÉΓòÉΓòÉ 1. Title Page ΓòÉΓòÉΓòÉ
U 1
UUCP - FIDO gateway
Version 1.99
Operator's guide
Copyright (C) 1991-1995 by Dmitry Zavalishin.
ΓòÉΓòÉΓòÉ 2. Introduction ΓòÉΓòÉΓòÉ
That's Beta!
Overview
Reaching the author
Getting the last version
System Requirements
Registration
ΓòÉΓòÉΓòÉ 2.1. It is a beta version! ΓòÉΓòÉΓòÉ
Hi, dear user!
Well, this is another beta version of U1. It has bugs, it does all but the
things you need it to, it doesn't work at all... :-) Sure, I do my best to make
it better and better, but don't judge me too strictly, if something is wrong!
Note as well, that the documentation you're reading is in the beta testing too
:-). Part of it I wrote myself, and part was translated from Russian by Natasha
Razdaeva (Thanx!) some time ago. Hope I'll find some time later to rewrite
obsolete parts from scratch to be sure everything is in sync with current state
of code.
A word on version numbers. U1 version number has major part, minor part and
modification letter. For example, version 1.98t has major number 1, minor
number 98 and letter t. Each time I change code significantly or release alpha
version, modification letter is changed. Each time the beta version is released
or i'm out of letters :-), minor number is increased. Major number changes once
a final release is done.
ΓòÉΓòÉΓòÉ 2.2. Overview ΓòÉΓòÉΓòÉ
This product (hereinafter Gate) is the facility that enables you being the user
both of UUCP network (such as Relcom, UUNET, etc.) and FIDO (FidoNet, LifNet,
etc.) to integrate these networks. Gate is able to transfer messages from one
network to another as well as integrate electronic conferences (echoes,
newsgroups).
ΓòÉΓòÉΓòÉ 2.3. How to Get in Touch with the Author ΓòÉΓòÉΓòÉ
If you want to get in touch with the author of this thing with your comments,
questions, suggestions and swearing you may:
Subscribe to UU2 echo.
Send a letter via e-mail:
Internet dz@phantom.ru
UUCP funet.fi!kiae!phantom!dz
FIDO Dmitry Zavalishin, 2:5020/32
Call by telephone number: +7 (095) 110-6728
Send a snailmail letter to: Zavalishin D.K., Russia, Moscow,
Arteckovskaya 7-4, fl. 260
Hi there!
ΓòÉΓòÉΓòÉ 2.4. Downloading the latest version ΓòÉΓòÉΓòÉ
Here's how can you get this stuff:
Subscribe to UU2 fileecho and receive updates automatically.
Check ftp.kiae.su/pub/os2/fido.
Check ftp.cdrom.com and hobbes.nmsu.edu.
F'Req U1 from 2:5020/32.
Warning: FIDO node 2:5020/32 is my home node and shares phone line with
me. Please teach your mailer to call me from 21:00 to 3:00 GMT ONLY.
ΓòÉΓòÉΓòÉ 2.5. System Requirements ΓòÉΓòÉΓòÉ
Hardware
No special hardware required. Current version of U1 will run on any OS/2
compatible Intel x86 machine.
Software
OS/2 2.0, 2.1, 2.11, Warp 3.0 or later required. Rexx support must be
installed.
U1 was tested (by myself or betatesters) with: Novell Netware 3.11,
Lantastic, FrontDoor 2.01-2.10, BinkleyTerm 2.50-2.59 (and some sideway
betas, such as EE beta D and E), D'Bridge, Imail 1.10-1.21, Squish
1.00-1.11, UUPC/Extended 1.12k.
In addition I must mention that U1 was used in multichannel FIDO systems
in a situation when gate modules work in both channels simultaneously.
You
I hope you're familiar enough with FTN and UUCP concepts. :-)
ΓòÉΓòÉΓòÉ 2.6. Registration ΓòÉΓòÉΓòÉ
Current (1.98-1.99) alpha or beta versions are free for use as long, as version
2.0 is not released. I'm not sure how much will it cost in future, but it is
planned to be released as shareware, or, maybe, bookware :-),
magazine_subscription_ware :-), etc.
I'm open to your comments and suggestions!
ΓòÉΓòÉΓòÉ 3. Hilights ΓòÉΓòÉΓòÉ
Two address conversion schemes at once: Traditional (Z:N/F.P <-->
pP.fF.nN.zZ.domain) and userlist-based one.
Optional access restriction: You can define domains which are accessible
for non-registered FIDOnet-side user.
News/echo gating in viamail/viauux/viarsh modes or via user-defined
program. Compressed feeds supported.
Complete activity log, optionally with debugging info.
Statistics support: all the letters passing gateway are logged together
with their origin and destination address, direction (to or from fidonet)
and size. Just import this information to your DBMS and prepare any
reports you like.
Remote access module: broadcasts messages to all registered gate users,
sends help file on user request, etc.
Easy way to add specific headlines to your letters. Need
'Return-Receipt-To:' or 'Distribution:' headline? Just write it in the
first line of the message text - gate will move it into the header of
resulting uucp message.
Cc, Return-Receipt supported.
Automatic UUencode of (small) attached files.
Can be easily combined with nearly any UUCP clone.
Handy uucp address representation in Fido messages - in almost all the
cases you don't need to add that stupid 'To:' line to your message.
Advanced FIDO standards, such as FSC-0044, FSC-0035 are implemented.
Unlimited number of echo/newsgroups supported. There is no limit at all -
adding more and more group names to list just slows conversion down a
bit.
Optional Cyrillic code tables conversion. Additional code conversion
tables can be added to new versions of gate.
Large messages from UUCP to FIDO are PKZIPped and converted to
file-attaches on the fly.
Filtering of control messages in UseNet news (such as cancel,
newgroup...)
Selective headline elimination system: Define which headlines you want to
see in FIDO messages. Definitions for netmail and echomail are separate.
Unwanted headlines can be stripped or hidden under ^A.
Three log file formats - my own, BinkleyTerm and FrontDoor lookalike.
Powerfull log file filter: all the messages are divided into classes. You
can turn logging of each class of messages on or off separately.
Fidogate's 'Comment-To:' headline supported.
Ability to add 'Distribution' headline to all the messages in any
newsgroup.
Well, i'm tired to enumerate :-)... Just set it up and try yourself!
ΓòÉΓòÉΓòÉ 4. The way it works ΓòÉΓòÉΓòÉ
Following pages describe in general the way U1 works.
ΓòÉΓòÉΓòÉ 4.1. Mail transfer ΓòÉΓòÉΓòÉ
Programs UU2Fido.exe and Fido2UU.exe are e-mail (as opposed to news and echoes)
gateway parts.
ΓòÉΓòÉΓòÉ 4.1.1. Mail from FIDO to UUCP ΓòÉΓòÉΓòÉ
This is what FIDO2UU.EXE is needed for. Being executed, FIDO2UU.EXE performs
the following steps:
1. Searches NETMAIL folder of your FIDO system for messages, that should be
processed. Messages, that will be processed by FIDO2UU.EXE must have
destination address, that is equal to the address, given in any FTN
parameter of U1 setup, and destination user name that is equal to the
name given in the Magic parameter of U1 setup or contains character '@'.
2. Each of the messages found is converted to UUCP- style one as follows:
3. Origin address is searched in USERS.U1 and replaced with corresponding
UUCP one, if found. If more than one matching occurrence exists, first
one is used. If origin address is not found in USERS.U1, user is treated
as not registered and some restrictions are applied. (See below). In this
case address is converted to
FirstName_LastName@pPOINT.fNODE.nNET.zZONE.<U1_DOMAIN>
Where <U1_DOMAIN> is chosen from FTN setup parameter, that is most
closely matches FidoNet address of the letter's sender.
4. If FIDO destination username field contains '@', it's value is used as
UUCP destination address. Otherwise, message is searched for the line of
form 'To: <uucp_address>' and value of <uucp_address> is used as
destination.
5. Message is searched for FIDO-style CC lines, all of those lines are
converted to RFC-822 form and added to resulting message header to inform
recipient about addresses where copies of letter was sent to.
6. Message is searched for U1-specific XCC lines ('XCC: <uucp_address>').
Uucp-addresses, that are given in those lines are added to those listed
in CC headlines of resulting message, and copies of message are sent to
those addresses, as well, as to primary destination address.
7. Before sending message to destination or XCC address, validity of
addresses is checked, if user is not a registered one. Address assumed to
be valid if all of it's parts, except for local name (as defined in
RFC-822) are found among the contents of Free setup file parameter.
Example:
SETUP.U1 contains:
Free mycompany.com borland.com john.UUCP Frank
Valid addresses:
me@myhost.mycompany.com
john.UUCP!JohnHimSelf@borland.com
Hey@Frank%borland.com
Frank!root
Invalid addresses:
john!root
Somebody@borland.org
8. Message beginning is searched for all other lines of form 'Name: Value',
and all of them are converted to UUCP message headlines.
ΓòÉΓòÉΓòÉ 4.1.2. Mail from UUCP to FIDO ΓòÉΓòÉΓòÉ
UU2FIDO.EXE is responsible for it. Your UUCP package must run this program
instead of it's usual mail delivery program (rmail or sendmail). To achieve
that you need to rename UU2FIDO.EXE to RMAIL.EXE or SENDMAIL.EXE, according to
what name mail delivery program has in your package. Make sure you have not
deleted original delivery program - gate needs it to be able send mail to UUCP
side.
Another way to set up gate can be used if your UUCP is able to call external
delivery program to deliver mail to specified domains. In this case you don't
need to rename anything at all - just set up your UUCP package to call
UU2FIDO.EXE. (For detailed discussion on this method please see cooperation
with UUPC 1.12).
ΓòÉΓòÉΓòÉ 4.1.3. Viamail news entry point ΓòÉΓòÉΓòÉ
If one of the delivery addresses is 'newsmaster' (this name is configurable, of
course), the letter will be sent to the echo-mail too. For example, (if the
configuration is the same as it is in SETUP.U1 file of documentation) execution
of the command "uu2fido dz newsmaster < news_article" will lead to the sending
of file contents to the user dz and, what is more, to the conversion of file
contents into echo- packet in compliance with the contents of Newsgroups
headline. (In fact, UU2FIDO.EXE just stores the copy of message in the U1
inbound news spool. The conversion to echo-packet is performed by UNBATCH.EXE)
ΓòÉΓòÉΓòÉ 4.2. News transfer ΓòÉΓòÉΓòÉ
News/echo gateway is more complex than e-mail and has twice more parts:
RNews.exe and Unbatch.exe for news to echo conversion and SNews.exe and
Batch.exe - for echo to news.
ΓòÉΓòÉΓòÉ 4.2.1. Echo-Mail to News ΓòÉΓòÉΓòÉ
This is a quite sophisticated process. SNEWS and BATCH programs are responsible
for it. To have the echo being sent, your echo-processor has to make the packet
with echo- mail. The packet must be made for the first address placed in
ECHOADDRESS parameter of configuration file and it must not be compressed by
some compression program. In particular, there is a possibility to create
non-compressed packets in Imail 1.21 echo-processor. After starting with key
-s, SNEWS.EXE will search for the netmail letters which have been sent to
ECHOADDRESS with echo-packet attached to them and then snews program will try
to convert and delete the echo-packet. You may also attach snews to echo-
processor as an additional compression program. In such a mode the program
converts the packet and deletes it instead of compressing it. Nevertheless, it
does not surprise the echo-processor usually. The only trouble is that the
processor in this case generates the letter to which, as it seems to him, the
file is attached. You may clean these letters by running SNEWS.EXE -s, but what
is more likely, the echo-processor will delete them in its next pass.
The program SNEWS.EXE converts the letters of FIDO format into UseNet format
and places them in the special directory, from which they may be taken by the
program BATCH.EXE later on. As a result of BATCH.EXE operation the letters are
converted into the news packets. In turn, the packets are sent to the receiving
systems using method, specified in configuration file (FEEDS.U1) for that
system.
ΓòÉΓòÉΓòÉ 4.2.2. News to Echo ΓòÉΓòÉΓòÉ
The receiving of news also proceeds by two stages. On the first stage, uu2fido
(ViaMail) or rnews (ViaUux) program receives the news packet and places it into
inbound spool- directory. The program UU2FIDO.EXE considers as news everything,
that have been sent to the address, placed in the configuration file in the
parameter NEWSMASTER. The contents of the spool-directory is handled by
UNBATCH.EXE. This program converts news to echo-packets addressed to your node
and places them in the your FIDO software inbound files directory. Usually it
is enough for your echo-processor to find it there and to import.
ΓòÉΓòÉΓòÉ 5. Setting things up ΓòÉΓòÉΓòÉ
Ok, in general, installation of U1 is not too complex... for experienced
FIDOnet sysop... who understands UUCP technology as well :). Here's the common
case described step-by-step:
1. Find (or create) good lovely directory to put all the junk to.
2. Copy all the files there. You may like to put a .DLL file to one of your
LIBPATH directory.
3. Edit U1 setup file.
Here you will need to tell the gate which thing it must call to send uucp
mail (RmailEXE parameter). Usually it will be something like rmail.exe or
sendmail.exe - refer to your UUCP package to find this out and...
1st way: rename it! You'll have to replace original RMAIL.EXE (or
whatever you have) with UU2FIDO.EXE. So:
a. Rename RMAIL.EXE to (say) UURMAIL.EXE
b. Rename UU2FIDO.EXE to RMAIL.EXE
c. In SETUP.U1 set RmailEXE parameter to have value UURMAIL.EXE.
2nd way: Make sure your UUCP package's RMAIL.EXE will call uu2fido
to deliver letters to domain you're going to use for FIDO/FTN mail.
Don't rename anything, in SETUP.U1 set RmailEXE parameter to have
value RMAIL.EXE (or whatever it happens to be in your UUCP package).
4. Set U1 environment variable in your CONFIG.SYS file - it must contain the
name of directory you put U1 setup files to.
5. Go to your echo processor setup and tell echo processor that you've got a
new compression program called U1, and that it is known that to compress
mail packet with that program echo processor must execute 'SNEWS.EXE
name.pkt' or 'SNEWS.EXE -i anything name.pkt'. You will use this
'compression' program to export echoes to gate. Assign it to the node or
point which address you have in EchoAddress setup parameter of U1, than
add that address to export list of any echo you wand to gate out.
ΓòÉΓòÉΓòÉ 5.1. Setup.U1 reference ΓòÉΓòÉΓòÉ
U1 setup file is a plain text file called Setup.U1, which is placed in a
directory pointed by U1 environment variable.
For example, if your setup file is f:\Network\U1\Setup.U1 you must include SET
U1=f:\Network\U1 for gate to work properly.
Setup file can contain comments and parameters. Any text from semicolon
character to the end of line is a comment and is ignored by U1. Each parameter
is beginning with a keyword. Keywords can be written in any case (even mixed).
Warning: Maximal total line length is 200 characters.
Among all the parameters flags are those, that can have value 'Yes' or 'No'
only. Note that default is 'Yes', if flag keyword is used alone in a setup
file.
Example:
Announce Yes ; Turn option on
Announce No ; Turn option off
Announce ; Turn option on
Announce XYZ ; Turn option on, issue error message
ΓòÉΓòÉΓòÉ 5.1.1. Required parameters ΓòÉΓòÉΓòÉ
The following parameters must be defined.
FTN
Magic
NetMail
NetFile
InFiles
Domain
Postmaster
UserList
TZ
ΓòÉΓòÉΓòÉ 5.1.1.1. FTN ΓòÉΓòÉΓòÉ
FTN Address/Mapping definition(s)
This record describes FTN gate operates in, sets gate address in that network
and defines UUCP address mapping.
Format:
FTN Name AKA UUCP-Domain [z=FZ-TZ]
Name Short name of Fido Technology Network described
AKA Our address in that network, INCLUDING DOMAIN
UUCP-Domain domain to use for this FTN on UUCP side
FZ-TZ Lower and upper value of zone number - used for domain
guessing.
There may be two FTN records, which differ only in AKA part.
FTN fidonet 2:5020/32.256@fidonet.org fidonet.org z=1-6
FTN fidonet 2:5020/32.512@fidonet.org fidonet.org z=1-6
ΓòÉΓòÉΓòÉ 5.1.1.2. Magic ΓòÉΓòÉΓòÉ
Magic name of our gate. Usually - UUCP. Used to send mail to be gated to, if
uucp address is too long to fit in 36 characters.
Magic UUCP
ΓòÉΓòÉΓòÉ 5.1.1.3. Netmail ΓòÉΓòÉΓòÉ
Your FIDO mailer netmail directory. Netmail folder must be in *.MSG format for
gate to work properly.
NetMail n:\mail
ΓòÉΓòÉΓòÉ 5.1.1.4. NetFile ΓòÉΓòÉΓòÉ
Directory where your FIDO mailer stores received files and where your
echo-processor searches for inbound echo-packets.
NetFile n:\files\in
ΓòÉΓòÉΓòÉ 5.1.1.5. InFiles ΓòÉΓòÉΓòÉ
Additional directories to scan file attaches in
InFiles n:\files\in\insecure,n:\files\in\unlisted
ΓòÉΓòÉΓòÉ 5.1.1.6. Domain ΓòÉΓòÉΓòÉ
Your Internet domain. If you have no one, use machine-name.UUCP
Domain isoft.msk.su
ΓòÉΓòÉΓòÉ 5.1.1.7. PostMaster ΓòÉΓòÉΓòÉ
UUCP-name of postmaster - person, who is responsible for gate operation. Copies
of gate error report letters will be sent to him/her. Also he will receive all
the letters, which address was not understood by gate (If not in
PassUnknownBack mode).
PostMaster postmaster
Warning: There must be corresponding entry in userlist, for example:
postmaster 2:5020/32 Post_Master
ΓòÉΓòÉΓòÉ 5.1.1.8. UserList ΓòÉΓòÉΓòÉ
File with list of registered gate users. See userlist reference.
UserList u:\gate\users.u1
ΓòÉΓòÉΓòÉ 5.1.1.9. TZ ΓòÉΓòÉΓòÉ
Time zone in format +/-HHMM. Moscow is +0300/+0400.
TZ +0300
ΓòÉΓòÉΓòÉ 5.1.2. Optional parameters ΓòÉΓòÉΓòÉ
The following parameters are optional.
UUCP
PercentInFrom
LogStyle
Log
LogLevel
Mail headlines elimination
Debug
Announce
Free
PassUnknownBack
Code_FU
Code_UF
Code_UF_flag
RmailExe
RmailExitL
RmailExitR
UuxExe
ZipLimit
KickUUCPFlag
StoreFiles
FidoFromFieldSize
ΓòÉΓòÉΓòÉ 5.1.2.1. UUCP ΓòÉΓòÉΓòÉ
uucp package type. Valid types:
ache30 uupc/*, coop. Demos, vers. 3.0
uupc11r uupc/ext 1.11R or later
waffle waffle 1.64 or later
Uucp Ache30
ΓòÉΓòÉΓòÉ 5.1.2.2. PercentInFrom ΓòÉΓòÉΓòÉ
If set to Yes, From_ line will have '@' replaced with '%' in it. Some packages
require it, some - not. Default to yes.
PercentInFrom No
ΓòÉΓòÉΓòÉ 5.1.2.3. LogStyle ΓòÉΓòÉΓòÉ
Defines the format of log file. Possible values:
Default Selects own format of log
Binkley BinkleyTerm lookalike mode
FrontDoor you see...
Warning: This one must be placed BEFORE Log keyword.
LogStyle Binkley
ΓòÉΓòÉΓòÉ 5.1.2.4. Log ΓòÉΓòÉΓòÉ
Name of gate operation log file.
Log u:\gate\u1.log
ΓòÉΓòÉΓòÉ 5.1.2.5. LogLevel ΓòÉΓòÉΓòÉ
Used to select information you want to see in log file. Turn debug mode on to
get complete log, then look at it and select key-characters of records you like
to see.
Meaning of characters:
a Address conversions
e Echomail info
n News info
b batched news
c compression
f file attaches
u user info
x Rexx log operator output
# chitchat (nothing to do, all done, etc)
% Timings, metrics
$ Mail logging
LogLevel au%$
ΓòÉΓòÉΓòÉ 5.1.2.6. Mail headlines elimination ΓòÉΓòÉΓòÉ
Following parameters define which RFC headlines to eliminate when converting
messages from UUCP to FIDO.
Meaning of example below: first line enables all headlines, second one tells to
hide under ^A everything that starts with "Receiv" or "Resent-" (not
implemented yet), and last tells to eliminate "Message-Id" and "From_" anyway.
Note: To eliminate leading UUCP From line, use "From_" as shown below.
MailPassHL *
MailHideHL Receiv* Resent-*
MailKillHL Message-ID From_
ΓòÉΓòÉΓòÉ 5.1.2.7. Debug ΓòÉΓòÉΓòÉ
Use Debug flag to get detailed logging. Produces very large logs.
Debug
ΓòÉΓòÉΓòÉ 5.1.2.8. Announce ΓòÉΓòÉΓòÉ
With this flag most U1 modules will display it's names when started.
Announce Yes
ΓòÉΓòÉΓòÉ 5.1.2.9. Free ΓòÉΓòÉΓòÉ
This keyword enables use of gate by persons not registered in userlist. If used
alone, enables access to any uucp/internet address. To limit access list
permitted domains and/or uucp machine names after keyword.
Free su ua by ew msk kiae demos dialnet isoft
In this example the following addresses will be valid:
user@subdomain.msk.su
kiae!msk.su!user
user@smthng%msk.su@somewhere.kiae.su
@msk.su:user@hq.demos.su
Next ones will be bounced:
service%nic.ddn.mil@kiae.su
demos!fuug.fi!henry@ford.us
ΓòÉΓòÉΓòÉ 5.1.2.10. PassUnknownBack ΓòÉΓòÉΓòÉ
This flag can be used if you want to use gate together with usual uucp
environment. In PassUnknownBack mode gate passes letters it cannot deliver to
FIDO back to uucp.
PassUnknownBack
ΓòÉΓòÉΓòÉ 5.1.2.11. Code_FU ΓòÉΓòÉΓòÉ
(For cyrillic code table conversion) Code table name to use for fido/uucp
conversion. (Used by FIDO2UU)
Code_FU None
ΓòÉΓòÉΓòÉ 5.1.2.12. Code_UF ΓòÉΓòÉΓòÉ
Code table name to use for uucp/fido conversion. (Used by UU2FIDO & UNBATCH)
Code_UF KOI8-CP866
ΓòÉΓòÉΓòÉ 5.1.2.13. Code_UF_flag ΓòÉΓòÉΓòÉ
Without this keyword uucp-fido code table converter will be used every time
UU2Fido called. This keyword specifies mode, in which code conversion will only
take place if UU2Fido called with -u flag. You will need this mode if you
interested in cyrillic characters code translation and use U1 with UUPC/* in
PassUnknownBack mode.
Code_UF_flag
ΓòÉΓòÉΓòÉ 5.1.2.14. RmailExe ΓòÉΓòÉΓòÉ
Name of uucp mail delivery agent.
RmailExe u:\uupc\uusmail.exe
ΓòÉΓòÉΓòÉ 5.1.2.15. RmailExitL ΓòÉΓòÉΓòÉ
Rmail must return this exit code if letter delivered to local uucp mailbox.
(This is an error condition for gate. Use -1 to disable.)
RmailExitL 0 ; For UUPC/Ache
RmailExitL -1 ; For other UUCP packages
ΓòÉΓòÉΓòÉ 5.1.2.16. RmailExitR ΓòÉΓòÉΓòÉ
Exit code that rmail returns on successful delivery of the letter.
RmailExitR 48 ; For UUPC/Ache
RmailExitR 0 ; For other UUCP packages
ΓòÉΓòÉΓòÉ 5.1.2.17. UuxExe ΓòÉΓòÉΓòÉ
Name of uucp remote execution program
UuxExe u:\uupc\uux.exe
ΓòÉΓòÉΓòÉ 5.1.2.18. ZipLimit ΓòÉΓòÉΓòÉ
Maximal size of message to pass to FIDO netmail without conversion to
file-attach.
ZipLimit 16384
ΓòÉΓòÉΓòÉ 5.1.2.19. KickUUCPFlag ΓòÉΓòÉΓòÉ
Name of file to create when something new sent to UUCP side
KickUUCPFlag u:\net\bink\btexit77.01
KickUUCPFlag u:\net\bink\fdexit77.01
ΓòÉΓòÉΓòÉ 5.1.2.20. StoreFiles ΓòÉΓòÉΓòÉ
Directory where you hold your outbound files. Used to hold file-attaches
created by uu2fido.
Default value: %U1%\gate.out
Directory will be created automatically, if not exists.
StoreFiles u:\gate\gate.out
ΓòÉΓòÉΓòÉ 5.1.2.21. FidoFromFieldSize ΓòÉΓòÉΓòÉ
Sets maximal length of contents of FIDO message 'from name' field. If uucp
address to be placed in from field is longer than this parameter's value, uucp
address will be replaced with gate magic name.
Default value: 35.
FidoFromFieldSize 36
ΓòÉΓòÉΓòÉ 5.1.3. News/echo parameters ΓòÉΓòÉΓòÉ
The following parameters must be defined for news/echo gateing to work.
EchoAddress
NewsMaster
Origin
Organization
News headlines elimination
GateId
InNewsSpool
OutNewsSpool
NewsPath
EchoList
FeedList
CnewsFeed
EchoMsgSize
PktSize
NoCrossPost
NewsBadGroupMSG
NewsControlMSG
ΓòÉΓòÉΓòÉ 5.1.3.1. EchoAddress ΓòÉΓòÉΓòÉ
Address pair, used by news gate. Will be used for echo packet headers, FIDO
PATH/SEEN-BY lines. First address is an address of newsgate. It will be used in
'From' field of .PKT files, generated by gate. Second one is an address these
.PKTs will have in 'To' field.
EchoAddress 2:5020/128.0@fidonet.org 2:5020/32.256@fidonet.org
ΓòÉΓòÉΓòÉ 5.1.3.2. NewsMaster ΓòÉΓòÉΓòÉ
Uucp username of ViaMail receiver. Your newsfeed must send news to this address
in your domain in ViaMail mode. There must be corresponding entry in user
table.
NewsMaster newsmaster
ΓòÉΓòÉΓòÉ 5.1.3.3. Origin ΓòÉΓòÉΓòÉ
Origin line added to echo messages by gate. If not defined, origin line is
built from Usenet message Organization headline.
Origin Infinity Soft Labs
ΓòÉΓòÉΓòÉ 5.1.3.4. Organization ΓòÉΓòÉΓòÉ
Used to form Organization headline in outgoing news articles.
Organization Infinity Soft Labs
ΓòÉΓòÉΓòÉ 5.1.3.5. News headlines elimination ΓòÉΓòÉΓòÉ
Selective headlines elimination. See Mail{Pass/Hide/Kill}HL. Note that
NewsHideHl is implemented, unlike MailHideHL.
NewsPassHL *
NewsHideHL X-* Organization Resent-* Distribution
NewsKillHL Path Lines Newsgroups From Subject Message-Id Reply-To Date Sender
ΓòÉΓòÉΓòÉ 5.1.3.6. GateId ΓòÉΓòÉΓòÉ
Optional. Don't define if not sure that you need it.
This string is appended to Organization headline and used to check for dupes
from uucp side. (Yes, path headline is generated and checked too, but when U1
used with newsserver, this method doesn't work because newsservers strips path
headlines)
Default value for this parameter contains your domain name.
GateId (isoft_gate)
ΓòÉΓòÉΓòÉ 5.1.3.7. InNewsSpool ΓòÉΓòÉΓòÉ
Optional. Don't define if not sure that you need it.
Used to hold incoming news articles.
Default value: %U1%\news.in
Directory will be created automatically, if not exists.
InNewsSpool u:\gate\news.in
ΓòÉΓòÉΓòÉ 5.1.3.8. OutNewsSpool ΓòÉΓòÉΓòÉ
Optional. Don't define if not sure that you need it.
Used to hold outgoing news articles.
Default value: %U1%\news.out
Directory will be created automatically, if not exists.
OutNewsSpool u:\gate\news.out
ΓòÉΓòÉΓòÉ 5.1.3.9. NewsPath ΓòÉΓòÉΓòÉ
Thing gate will put in 'Path:' headline of outgoing news articles and check for
in incoming ones to find dupes. You can set complex things here like
'isoft!isoft.msk.su' - all the string will be put to 'Path:' headline of
outgoing messages, but incoming message's path will be checked only against
first component of this parameter's value (in our example - 'isoft'). Please
don't include 'newsgate' or something like username - U1 adds '!newsgate' to
path line automatically.
NewsPath isoft!isoft.msk.su
ΓòÉΓòÉΓòÉ 5.1.3.10. EchoList ΓòÉΓòÉΓòÉ
List of gated newsgroup/echo names: used for group name translation
EchoList u:\gate\echoes.u1
ΓòÉΓòÉΓòÉ 5.1.3.11. FeedList ΓòÉΓòÉΓòÉ
List of uucp nodes we send gated news to. See example.
FeedList u:\gate\feeds.u1
ΓòÉΓòÉΓòÉ 5.1.3.12. CnewsFeed ΓòÉΓòÉΓòÉ
Makes U1 to act as a simple Cnews-type system - feed received cnews articles
back to uucp.
CnewsFeed
ΓòÉΓòÉΓòÉ 5.1.3.13. EchoMsgSize ΓòÉΓòÉΓòÉ
Max. size of echomail message gate will create.
Default - 12 Kbytes.
EchoMsgSize 12000
ΓòÉΓòÉΓòÉ 5.1.3.14. PktSize ΓòÉΓòÉΓòÉ
Recommended size of .PKT files created by gate
PktSize 400000
ΓòÉΓòÉΓòÉ 5.1.3.15. NoCrossPost ΓòÉΓòÉΓòÉ
Turn off crossposting. Messages from usenet to FIDO will be posted only to the
first area found in Echoes.U1
NoCrossPost
ΓòÉΓòÉΓòÉ 5.1.3.16. NewsBadGroupMSG ΓòÉΓòÉΓòÉ
Defines the way of processing of messages, which have no known newsgroup tag in
their Newsgroups: headline
Possible values:
Separate Put message to special echo. (UU2.BAD_GROUP)
Kill Don't process (delete) it.
Pass Pass unchanged. (Use last group name from Newsgroups headline as
echo tag)
NewsBadGroupMSG Separate
ΓòÉΓòÉΓòÉ 5.1.3.17. NewsControlMSG ΓòÉΓòÉΓòÉ
Defines the way of processing of messages, which have Control: headline.
Possible values:
Separate Put message to special echo. (UU2.CONTROL)
Kill Don't process (delete) it.
Pass Pass unchanged.
NewsControlMSG Separate
ΓòÉΓòÉΓòÉ 5.1.4. Gremote parameters ΓòÉΓòÉΓòÉ
The following parameters must be defined for gremote to work.
HelpFile
PassWord
ΓòÉΓòÉΓòÉ 5.1.4.1. HelpFile ΓòÉΓòÉΓòÉ
Gremote sends this file in response to 'Help' command.
HelpFile u:\gate\gatehelp.txt
ΓòÉΓòÉΓòÉ 5.1.4.2. Password ΓòÉΓòÉΓòÉ
Password for privileged gremote commands.
PassWord Oh-John!-Oh-No!
ΓòÉΓòÉΓòÉ 5.2. Users.U1 reference ΓòÉΓòÉΓòÉ
Users.U1 file contains list of registered gate users. Name of this file must be
given in UserList setup file parameter.
Setup file can contain comments and user definitions. Any text from semicolon
character to the end of line is a comment and is ignored by U1.
User definition general form is:
uucp_name [parameters] fido_address fido_name
Parameters start with '-' or '/' and have form
-key=value
Currently these parameters are defined:
-from=domain used to define domain, used in uucp From: field
-filedir=path directory to put fileattaches for this user to
Note: uucp_name can have domain as well, but, currently, it will be ignored
by U1.
Examples:
; Entry for postmaster
postmaster 2:5020/32.0 Postmaster
; Forward mail to UUCP to postmaster too
uucp 2:5020/32.0 Postmaster
; dz@isoft.msk.su, default domain used
dz 2:5020/32.0 Dmitry_Zavalishin
; same as above
dz@ 2:5020/32.0 Dmitry_Zavalishin
; dz-1@dialnet.msk.su, explicit domain used
dz-1@dialnet.msk.su 2:5020/23.4 Dmitry_Zavalishin_1
; dz-2@pd.isoft.msk.su, partially defined domain - pasted to default
dz-2@pd. 2:5020/23.77 Dmitry_Zavalishin_2
; Entry for newsmaster
newsmaster 2:5020/32.0 NewsMaster
newsmaster 2:5020/23.55 NewsMaster
newsmaster 2:5020/23.4 NewsMaster
ΓòÉΓòÉΓòÉ 6. Cooperation with ΓòÉΓòÉΓòÉ
In the following subsections I'm describing 'interesting' details of U1
installation together with a different 3-rd party software packages.
ΓòÉΓòÉΓòÉ 6.1. Sendmail ΓòÉΓòÉΓòÉ
U1 can be used as sendmail-driven mailer. Sendmail version 1.3.2 or later
should be used. Note though that Warp IAK sendmail has been designed to work
with slip only and senses state of the slip driver. So avoid using it if slip
is not the only way you communicating with outer world. For use with LAN TCP/IP
or any UUCP connections get yourself a copy of sendmail.exe from the latest IBM
TCP/IP CSD. The following excerpt from sendmail.cf shows how U1 mailer can be
described to be called by sendmail.
Note: Flag -x is ignored by U1 and used just to overcome glitch in sendmail
program execution logic.
Muu2, P=C:\u1\uu2fido.exe, A=-x1 $u, Flags=upm, Sender=10, Recipient=12
To use sendmail instead of usual rmail, which is called by U1 to deliver uucp
mail, use rmail.c filter program.
ΓòÉΓòÉΓòÉ <hidden> Example of sendmail configuration ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Calling sendmail instead of rmail ΓòÉΓòÉΓòÉ
// Fake rmail, analyzes From_, calls sendmail
#include <stdio.h>
#include <string.h>
#include <process.h>
#define ALOT 16384
char cmd[ALOT];
char from_[ALOT];
int have_from_ = 0, have_host = 0, pos;
char dummy[100], path[ALOT], host[100], full_path[ALOT];
int c;
int
main( int ac, char **av )
{
FILE *pipe;
fgets( from_, 4096, stdin );
if( strncmpi( from_, "From", 4) == 0 & from_[4] != ':' )
{
char *p;
have_from_ = 1;
sscanf( from_, "%s %s%n", dummy, path, &pos );
p = from_+pos;
p = strstr( p, "remote from");
if( p == 0 )
strcpy( host, "" );
else
{
sscanf( p+11, "%s", host );
have_host = 1;
}
}
if( have_host )
sprintf( full_path, "%s!%s", host, path );
else if( have_from_ )
sprintf( full_path, "%s", path );
else
sprintf( full_path, "localhost!uucp" );
sprintf( cmd, "sendmail -f %s", full_path );
while( --ac )
{
strcat( cmd, " " );
strcat( cmd, *++av );
}
fprintf( stderr, "cmd: %s\n", cmd );
if((pipe = _popen(cmd, "wb")) == NULL)
{
fprintf( stderr, "Unable to create pipe\n" );
return 1;
}
if( !have_from_ )
fputs( from_, pipe );
while( (c = getchar()) != EOF )
putc( c, pipe );
if( ferror( pipe ) )
{
_pclose( pipe );
return 2;
}
return _pclose( pipe );
}
ΓòÉΓòÉΓòÉ <hidden> Waffle 1.65 ΓòÉΓòÉΓòÉ
As it was said before, there's two different ways of U1 installation exist -
one with replacing RMAIL.EXE with UU2FIDO.EXE, and one without such
replacement.
Replacing rmail.exe
Rename (Waffle's) RMAIL.EXE to UURMAIL.EXE, rename (U1's)
UU2FIDO.EXE to RMAIL.EXE and put it to the directory where RMAIL.EXE
was, in SETUP.U1 write:
RmailEXE <correct_drive_&_dir>\uurmail.exe
RmailExitL -1
RmailExitR 0
Cooperating with RMAIL.EXE
Don't rename anything. In SETUP.U1 write
RmailEXE <correct_drive_&_dir>\rmail.exe
RmailExitL -1
RmailExitR 0
In <waffle_dir>\uucp\paths write:
.fidonet.org | <U1_dir>\uu2fido.exe
<U1_domain> | <U1_dir>\uu2fido.exe
NB! Make sure you didn't set PassUnknownBack mode in U1 setup!
ΓòÉΓòÉΓòÉ 6.2. UUPC/1.12 Extended ΓòÉΓòÉΓòÉ
Replacing rmail.exe
Rename (uupc's) RMAIL.EXE to UURMAIL.EXE, rename (U1's) UU2FIDO.EXE
to RMAIL.EXE and put it to the directory where RMAIL.EXE was, in
SETUP.U1 write:
RmailEXE <correct_drive_&_dir>\uurmail.exe
RmailExitL -1
RmailExitR 0
Cooperating with RMAIL.EXE
NB! The following method was not tested, I'm not sure it works.
Don't rename anything. In SETUP.U1 write
RmailEXE <correct_drive_&_dir>\rmail.exe
RmailExitL -1
RmailExitR 0
In <uupc_dir>\conf\hostpath write:
*.fidonet.org | <U1_dir>\uupc2uu2.cmd
<U1_domain> | <U1_dir>\uupc2uu2.cmd
In <U1_dir>\uupc2uu2.cmd write:
<U1_dir>\uu2fido %3@%2
NB! Make sure you didn't set PassUnknownBack mode in U1 setup!
ΓòÉΓòÉΓòÉ <hidden> UUPC/* by Ache ΓòÉΓòÉΓòÉ
;p. Versions supported:
3.00 completely
4.07 no viauux news reception possible
5.00 PassUnknownBack will not work well.
Installation is nearly the same as for UUPC 1.12. The only difference is the
value of the following items in SETUP.U1:
RmailExitL 0
RmailExitR 48
ΓòÉΓòÉΓòÉ 6.3. Squish 1.01 ΓòÉΓòÉΓòÉ
The following is how to export echoes to gate:
SETUP.U1:
...
FTN FidoNet 2:5020/23.0@fidonet.org fidonet.org z=1-6
Magic uucp
EchoAddress 2:5020/23.1@fidonet.org 2:5020/23.0@fidonet.org
...
ECHOES.U1:
...
fido.bermudian.sysop Bermudian.Sysop
fido.bermudian.talks Bermudian.Talks
...
SQUISH.CFG:
...
Address 2:5020/23
...
Compress compress.cfg
Routing route.cfg
...
Pack U1 2:5020/23.1
...
; The following two groups are to be gated to news
;
EchoArea Bermudian.Sysop x:/Somewhere/bsys -$m200 2:5020/23.1
EchoArea Bermudian.Talks x:/Somewhere/btlk -$m200 2:5020/23.1
...
COMPRESS.CFG:
...
Archiver U1
Extension U1
Ident 0,NothingOfAGreatValue
Add x:\uu2\snews %f
End Archiver
...
ROUTE.CFG:
Send hold file 2:5020/23.1
ΓòÉΓòÉΓòÉ <hidden> GEcho 1.00 ΓòÉΓòÉΓòÉ
The following is how to export echoes to gate: System data/Compression
programs/8 menu:
ΓòÆΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòò
Γöé Γöé
ΓöéΓûáARC PKPAK -a ΓòÆΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉ 8 Γòò Γöé
Γöé ARJ ARJ a -e -m1 -sΓöé Γöé Γöé
Γöé LZH LHA a /mt Γöé Program SNEWS Γöé Γöé
Γöé PAK PAK A /L /ST Γöé Switches -i Γöé Γöé
Γöé ZIP PKZIP -ao Γöé Memory 640 Γöé Γöé
Γöé ZOO ZOO a: Γöé Γöé Γöé
Γöé SQZ SQZ a /q0 /z3 ΓòÿΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓò¢ Γöé
Γöé 8 Γöé
Γöé 9 Γöé
Γöé 10 Γöé
Γöé GUS {+} Γöé
Γöé Γöé
ΓòÿΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓò¢
Node manager menu:
ΓòÆ New entry ΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉ Node manager Γòò
Γöé Γöé
Γöé Node address 2:5020/23.1 Γöé
Γöé Sysop name Γöé
Γöé Route via 2:5020/23.1 Γöé
Γöé Packet password Γöé
Γöé AreaMgr password Γöé
Γöé Authorized groups Γöé
Γöé Remote maintenance No Γöé
Γöé Allow rescan No Γöé
Γöé Forward requests No Γöé
Γöé Send notify list No Γöé
Γöé Compression type SNEWS -i Γöé
Γöé Mail archive status Hold Γöé
Γöé Direct Yes Γöé
Γöé Γöé
ΓòÿΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓò¢
Add 2:5020/23.1 to the export list of all areas you want to gate to UseNet.
ΓòÉΓòÉΓòÉ <hidden> IMail 1.21 ΓòÉΓòÉΓòÉ
Compression Programs menu: Program 8 snews -i Node Export Manager
menu:
Address 2:5020/23.1
Password
Groups
Direct Y
Remote Maint N
Status Hold
Program snews -i
Capability Type 2+
CW Handling Force
In General configuration/Product codes menu add product code 'CC'.
Add node 2:5020/23.1 to the export list of all echoes you want to export to
UseNet.
ΓòÉΓòÉΓòÉ <hidden> FastEcho ΓòÉΓòÉΓòÉ
Edit/Compression Programs menu:
ΓòÆΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉCompression ProgramsΓòÉΓòò
Γöé Tag Command Γöé
ΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöé
Γöé A) UU2 snews -i Γöé
Γöé B) ΓûæΓûæΓûæ Γöé
Γöé C) Γöé
Γöé D) Γöé
Γöé E) Γöé
Γöé F) Γöé
Γöé G) Γöé
Γöé H) Γöé
ΓòÿΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓò¢
Edit/Node Configuration menu:
ΓòÆΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉNode-ManagerΓòÉΓòò
Γöé Γöé
Γöé Node: 2:5020/23.1 4D: Y Γöé
Γöé Tosscan: N Γöé
Γöé Your Aka: 2:5020/23.0 D'Bridge: N Γöé
Γöé ARCmail 0.60: N Γöé
Γöé Password: Direct: Y Γöé
Γöé Crash: N Γöé
Γöé Hold: Y Γöé
Γöé Packer: UU2 Umlaut: None Γöé
Γöé Γöé
ΓòÿΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓò¢
Add 2:5020/23.1 to the export list of echoes you want to gate to UseNet.
ΓòÉΓòÉΓòÉ 7. Remote control unit ΓòÉΓòÉΓòÉ
This utility (GREMOTE.EXE), being started without any parameters, searches the
letters which have been sent to the user with the name Gate and when found
them, the utility tries to find and execute the commands contained in letter.
It should be noted that the letters may come through Gate too - gremote ignores
the lines of the RFC822 letter header.
Gremote understands the following commands:
HELP Sends back a note concerning GREMOTE commands together
with the contents of special file (See HelpFile config.
file option).
USERS (Secure) Sends the list of registered gate users.
ECHOES Sends the list of gated echo-, news-groups.
NOTIFY (Secure) Sends the letters to the all the registered users
of gate with reminding, that they are gate users, what
their address is and how they may ask for help.
BROADCAST (Secure) Distributes text following the command (up to the
end of the message) to the all the registered users.
ΓòÉΓòÉΓòÉ 8. User's manual ΓòÉΓòÉΓòÉ
Sending letters via gate (FIDO side)
1. Address
Well, you going to send a letter to Internet. Recipient's address is
"jack@jpc.super.org", gate you will use is placed at 1:333/22 and
it's "magic name" is UUCP. (Gate's magic name can be set up in MAGIC
parameter of configuration file.) Two ways exist to prepare that
letter.
- First method:
FIDO destination address of letter must be "UUCP, 1:333/22",
the very first line of letter text must be "To:
jack@jpc.super.org".
- Second method:
FIDO destination address must be "jack@jpc.super.org,
1:333/22". This method is much more convenient, but can be used
only if Internet address is short enough to fit into the FIDO
username field.
2. Netmail reply
When replying to letter, which came from gate, you always have
correct FIDO destination address, because U1 makes FIDO letter
"from" field to contain best kind of address possible, filling
username subfield with Internet address if it is short enough, or
with gate's magic name otherwise. In the latter case you need to
type in "To: Internet_address" in the first line of your reply
manually (Unless your message editor supports FTS-0034/35
recommendations). Note that Internet address of the person you
replying to can be found in a special kludge line (REPLYTO) U1
inserts.
3. Receipt Request
Letters with RRQ flag are confirmed with a fragment of the gate log
file, which corresponds to the processing of the letter. In
addition, resulting uucp letter will carry Return-Receipt-Request
headline.
4. Additional headlines
In the very first lines of the letter you may insert the lines like
"name: value". They must be started from the first position and must
not have blanks between a keyword and a colon. It is desirable to
make the first letters of the key words capital. All the lines of
such a form (down to the first line not answering to this
description) are considered to be the lines of RFC822-header of the
letter and are placed there. Their width is limited by 75 symbols.
Example:
|
|To: myfriend@somewhere.us
|To: news@kiae.su
|Newsgroups: comp.lang.std.c++
|Distribution: su
|Return-Receipt-To: me@mydomain.su
|
|<- this is the left border of editor window :)
5. CC feature
To send a letter to the several addresses in uucp network you may
use the following way: place at the very beginning of the letter the
line 'xcc: address one_more_address ...'. Abbreviation 'xcc'
(instead of the usual 'cc') is chosen so that the line would not be
interpreted by FIDO software.
6. Text formatting
Gate will automatically reformat the lines with the width more than
80 characters. Formatting is executed without right border
indentation and hyphenation. Unfortunately, by now it is not
possible to disable the formating despite of the fact, that
sometimes I want to (to transfer wide table, for example). On the
other hand, not every network may transfer the letters with the
line's width more than 80 symbols, so gate in some sense provides
standartability to your letters.
7. UUENCODE
If you need to send a small file to Internet, you don't have to
encode it yourself and stuff into the letter. Just attach file to
the letter, and U1 will uuencode it for you and send along with the
text of letter. Please don't attach large files, 'cause U1 does not
split 'em up into the parts before encoding and resulting letter
will be too large to pass through.
Sending letters via gate (UUCP side)
1. Comment-To
When posting an article into the newsgroup which is gated to FIDO
with U1, you can force gate to set FIDO echomail message 'To' field
to anything you want using a special "Comment-To:" headline. Syntax
of that headline is "Comment-To: User Name <address>". User name
given will replace the usual "To: All" in resulting echo message,
and address is simply ignored.
ΓòÉΓòÉΓòÉ 9. Technical Notes ΓòÉΓòÉΓòÉ
See following pages.
ΓòÉΓòÉΓòÉ 9.1. General Technical Notes ΓòÉΓòÉΓòÉ
The FTSC assigned product code for U1 is CC hexadecimal.
U1 supports 3D/4D and partially 5D addresses.
U1 creates and is able to receive Type 2+ packets, provided they have
correct capability word as well as it's validation copy.
U1 batcher doesn't add '#! cunbatch' line at the beginning of compressed
UseNet batches. It is assumed that U1 will be used with Cnews as the
receiver of batches, which doesn't need '#! cunbatch' header.
Echo-News gateing: text, that follows origin line will be stripped.
U1 never gives up timeslices since there's no situations when U1 waits
for some event to happen.
I did my best to make sure U1 will not cause any problems on the network,
but nothing is guaranteed. But if you encounter some problem related to
file locking or something else related to multitasking environment,
please feel free to inform me.
ΓòÉΓòÉΓòÉ 9.2. Standards supported ΓòÉΓòÉΓòÉ
U1 supports FIDO standards
FTS-0001
FTS-0004
FTS-0009
FSC-0035
FSC-0044
FSC-0053
and Internet standards
RFC-822
RFC-1036
RFC-1123
ΓòÉΓòÉΓòÉ 9.3. FIDO kludge lines ΓòÉΓòÉΓòÉ
Kludge lines parsed:
FMPT
TOPT
INTL
FLAGS
DOMAIN
MSGID
REPLY
PID
Kludge lines created:
FMPT
TOPT
INTL
FLAGS
DOMAIN
MSGID
REPLY
PID
REPLYADDR
REPLYTO
Please note that U1 never attempts to find letter origin address in MSGID
field.
ΓòÉΓòÉΓòÉ 9.4. A word on errors handling ΓòÉΓòÉΓòÉ
In short, Gate registers errors in the log file and makes the following efforts
to secure your property if it failed to do something:
Delivery error to UUCP
The letter will be generated to the sender of the initial message
and to the postmaster. The letter contains the corresponded fragment
of the U1 log file and text of the original letter.
The recipient was not found during delivery to FIDO
The original letter will be sent to the postmaster. If he is also
not found in the users' list - so much the worse for you. The letter
is simply lost.
The news-group has not found in the list while converting of news into echo
The letter will be sent to the echo named bad_group.
The echo-group has not found while converting of echo into news
The letter will be ignored.
Among the all fatal errors the worst ones are those, that may occur during
delivery of the letter from UUCP. They, usually result in loss of the letter,
because some of UUCP packages, when delivering received messages, simply
ignore exit codes, returned by delivery program.
ΓòÉΓòÉΓòÉ 10. Thanx... ΓòÉΓòÉΓòÉ
People I'm really thankful to...
Alex Belyaev, Alex Popov, Alex Rudnev, Alex Selkov, Alex Sherbakov, Alex
Snigerev, Alex Young, Andew Bloschintsev, Andrew Chernov (Ache), Andrew
Kovalev, Andy Nickolayev, Boris Mostovoy, Boris Tyshkievitch, Dmitry Baronov,
Dmitry Khrustalev, Egons Bush, Eric Fletcher (Eugeny Chupriyanov), Eugene
Crosser, Eugene Peskin, Fyodor Evseev, Gena Rez, Gennady Zvonov, Grubina Olga
(Russian dox edition), Harry Bush, Igor Sviridov, Joseph Urban, Kira
Stratonnokova (my wife!), Kirill Lebedew, Mark Patterson, Max Mikheenkov,
Michael Bravo, Mike Skulkin, Natasha Razdaeva (partial dox translation to
english), Nikki Chumakov, Oleg Nesterov, Oleg Polovinkin, Peter Zeltins, Sergey
Ryzshkov (Initiation!), Sergic Dobridnuk, Vad Potapov, Vadim Getmanshchuck,
Valery Bardin and all the Relcom team (Relcom network!), Yuri PQ, Yuri Yashnev
(Financial support), Serge Terekhov
If you feel you must be mentioned in this list, but is not, I am sorry, sorry,
sorry... Please, forgive me - it is really hard to recall all the people I
discussed U1 with!
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
FTN Stands for FidoNet Technology Network.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
To get latest CSD, ftp to software.watson.ibm.com, change directory to
tcpip/os2 and download updates.
Note: Don't you get TCP/IP 1.2 updates mistakenly.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Secure (Privileged) GRemote commands: The privileged commands may be executed
only when a valid password is given. To use such commands you need to pass
password in the Subject field of the letter.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Registered Users: Registered users are the users, which are mentioned in the
USERS.U1 configuration file.