Manual for FidoExport 1.42 and FidoImport 1.42 """""""""""""""""""""""""""""""""""""""""""""" Overview ======== To run a fido point with UMS you need FidoImport, FidoExport, TrapDoor and naturally UMS itself and a UMS newsreader. FidoImport is used to import fido messages to the ums messagebase which were transmitted by TrapDoor. FidoExport is used to export new messages from the messagebase into a format which will be transmitted by TrapDoor. The format of those file can be found in fido literature (FTC files). TrapDoor's manual explains the naming sheme of the files. Installation - The Variables ============================ FidoImport and FidoExport are configured by using variables in the global ums.config. Aa asterix ("*") marks variables which may be omitted. fido.netname name of the network using "Fido Technology". This will be used as identification for groups ("netname.group") and messages ("z:n/f.p@netmane") of this net. When usings fidonet itself use "fidonet". fido.pointaddress fido.fakeaddress (*) fido.stoneage (*) These variables describe you own fido address. "pointaddress" is the full 4D address of your system. "fakeaddress" is necessary if the software of your boss doesn't create 4D packets. If your boss can't handle incoming 4D packets you must set "stoneage" to "y" and only 3D packets will be created. Don't forget an AKA for you address. fido.bossaddress This is the address of you boss. fido.mausgate (*) fido.rfcgate (*) These are the addresses of gateways to "Maus" and RFC nets. You must supply them if FidoExport should export messages to this nets. fido.defaultorigin This is the origin which will be used if a message dosn't have an origin. fido.inbound fido.outbound fido.tmpdir (*) These are the paths (including tailing "/" or ":") of the directories for outgoing and incoming packets. fido.arccmd fido.dearccmd fido.junkcmd These AmigaDOS commands are used for bundling and unbundling packets. For malformed packets "junkcmd" is called. Using "%s" in the command string (up to 4 times) the name of the packet may be inserted. fido.charset.xy (*) FidoImport knows about ALL charsets defined in FSC 54. There are however many fido programs, that use different (undefined, illegal) names for the same charsets. In order to make these work anyways, you can redirect them to known charset. Known charsets (FSC 54) are: Level 2: "LATIN-1", "IBMPC", "MAC" Level 1: "GERMAN", "FRENCH", "DUTCH", "FINNISH", "CANADIAN", "ITALIAN", "NORWEG", "PORTU", "SPANISH", "SWEDISH", "SWISS", "UK" Example: "fido.charset.ISO-8859-1 = LATIN-1" redirects "ISO-8859-1" to "LATIN-1". fido.ascii (*) this pattern marks areas which don't allow other characters than pure ASCII. FidoExport converts all special characters (like umlauts) for these areas. All other groups get special characters with a proper charset kludge. fido.security (*) This string contains flags that enable certain security methods: PKTADR - only import a packet if its destination matches the local address. PKTPWD - use packets password for login. Default login will be used if this failes or a password does't exist. If not specified, "" will be tried as a password, too. SESSIONPWD - use TrapDoor's filenote (password "") for logins only if session was password protected. With PKTPWD and SESSIONPWD make it possible to guarantee that only authentic users (fido nodes) gain access to higer privileged UMS accounts. This is, of course, only usefull for nodes. Points won't use it. fido.debuglevel (*) fido.loglevel (*) fido.reportlevel (*) fido.reportuser (*) FidoImport and FidoExport create 3 different kinds of debug-/log information: - debug (stdout) - log (ums logfile, managed by umsserver) - report (a mail, that is sent to the 'reportuser') Levels are organized similiar to umsserver: the bigger the value, the more output is created. The outputs with lower values represent the more important information or the more serious errors. <5 means error, >=5 means log-/debug information. Installation - Hints / Example ============================== It's very important that certain variables can be local to the user entry of your boss. as an example all important lines of my ums.config: -- cut -------------------------------------------------------------------- aka 2:2407/106.3@fidonet fido.inbound = "UMS:Inbound/" fido.outbound = "UMS:Outbound/" fido.junkcmd = "Copy %s UMS:Bad/ *n Delete %s" fido.mausgate = "2:242/2.6" fido.rfcgate = "2:242/6.1" fido.debuglevel = 8 fido.loglevel = 6 fido.reportlevel = 5 fido.reportuser = SYSOP fido.charset.ISO-8859-1 = LATIN-1 fido.ascii = ~(fidonet.(AMIGA.GER|IBASE.POINTS|AMIPROG.GER|UMS.GER)) fido.defaultorigin = "Amiga Modula & Oberon Klub (AMOK) Stuttgart" user name = Intuition-Base alias = fido.2.2407.106.0 alias = fido.default readaccess = "fidonet.#?" writeaccess = "fidonet.#?" netaccess = #? import = #? export = "(#?@fidonet|#?.maus)" distribution = #? fido.netname = "fidonet" fido.pointaddress = "2:2407/106.3" fido.bossaddress = "2:2407/106.0" fido.arccmd = "LhA -u -m -U2048 m %s %s" fido.dearccmd = "LhA -m -f -x0 -U8192 x %s %s" enduser -- cut -------------------------------------------------------------------- each user entry of a fido system must have an alias in the form "fido.z.n.f.p". FidoImport uses this to log in. The user entry of your default node gets the line . and must respect . , and should be "#?" for now. You shold think abount the pattern. If you are only running a fido point an do not paticipate in other nets a simple "#?" is enough. Otherwise you must choose a pattern which doesn't overlap the patterns of other nets. Polling more than one fido systems ================================== Just add additional user entries for the other nodes. Using and you must specify which echos and which mail is exported the which node. Paticipating in other nets with "Fido Technology" ================================================= Just add additional user entries and choose a proper . Addressig of Mails ================== All addresses must be in a special format. You must use "2:123/4.5@fidonet" instead of simply "2:123/4.5". "@fidonet" is just an example. Use the proper instead. Mails without proper adresses will not be exported! Special features ================= In order to send file attaches you must add "file-attach" to the attribute field of a mail. The subject of the mail specifies the full path of the file. (e.g. "Mail:Uploads/AttachMe.LHA"). You can create crash mail by adding "crash" to the attributes. These messages will be directly exported to the boss of the receiver. Use TrapDoor to call the proper node. Usage of FidoImport =================== The template of FidoImport is: NAME,PASSWORD,SERVER/K,INBOUND/K,PRESERVE/S If no default login is given, "fido.default" will be used. FidoExport tries to get a proper login from TradDoor's filenates and/or 4D packet headers. Usage of FidoExport =================== The template of FidoExport is: USER,PASSWORD,SERVER/K USER and PASSWORD specify the user entry of the fido node you want to export to. If they are omitted FidoExport uses "fido.default". Epilogue ======== Please send bug reports and suggestion to Kai Bolay EMail: UUCP: kai@amokle.stgt.sub.org Hoffmannstraße 168 FIDO: 2:2407/106.3@fidonet D-7250 (71229) Leonberg Germany Martin Horneffer EMail: UUCP: mh@umshq.adsp.sub.org Warmweiherstraße 18 FIDO: 2:242/7.9@fidonet D-5100 Aachen MAUS: AC.maus, AC2.maus Germany