| Document: FSC-0086 | Version: 001 | Date: 03 September 1995 | | Mirko Mucko, 2:2433/920 Information / Description of a new standard S tandard R equest I nformation F ile Copyright (c) 1994,95 by Gordian Schuermann & Mirko Mucko I Overview Introduction 0 Description in general 1 Required statements 1.1 Optional statements 1.2 Undefined options 1.3 Implementation 2.0 0. Introduction In common, more and more mailer are about to implement the ability to call external request processors. But very soon, we discovered a command line cannot handle all the information the mailer has and the ERP needs. To transfer the information in a proper and fast way, we designed and implemented the S R I F option in the mean it will be a standard soon. The structure and idea is protected by copyright law, except these circumstances: + you may distrubute, use and implement this structure for free + you have not to pay any value for usage of these methodes + you should note in your documentation the origin of SRIF 1. Descritption The SRIF name is the only parameter given from the Mailer to the External Request Processor. The file is designated as a so called "plain vanilla ASCII" file, filled with pre-defined, optional and not-yet defined statemets. We discussed the possibility of binary files, and of EMSI-like files, but a plain ASCII control file is more flexible and can be read faster by various program languages (C, Pascal, Basic, Cobol ect). In the SRIF, one command plus parameter is allowed per line, the file is unlimited in length, comments are not allowed. The SRIF is generated by the Mailer and after the ERP finished its work, the Mailer is responsible for erasing the SRIF. 1.1 Required statements The following statements are required for the ERP: Sysop This is the name of the remote sysop AKA This is the main aka of the remote system in 4D or 5D notation. A zero as point number may be ommited, the domain with "@" is optional Baud This is the effective baud rate, not the fixed DTE rate Time