This text file, will contain questions like those I have received in Email or a public conference about JamMail. Primarily, these questions are going to related directly to JamMail or JamScan. If you have suggestions of how to integrate some of this into the manual let me know. Q) How do I contact you? A) The following Network addresses are all valid: FidoNet#1:163/139, ZyXELNET#18:18/0, AmigaNet#40:553/139 ab207@freenet.carleton.ca Snail: James McOrmond 264 2nd Avenue. Ottawa, On K1S 2H9 Canada Voice: 613-230-8720 ZyXEL: 613-230-2172 VFC: 613-230-1136 Q) How to I start a JamMail Mailer? A) Execute the S:Setup script. Since JamMail sets the execute bit, you only need to type "setup" from any CLI where the s: directory is in your search path. Q) How do I shutdown JamMail? A) Various different ways. 1) press Ctrl-C in the scheduler window. If configured, it will close the rest of the system down. 2) If configured (in the scheduler menu), pressing Ctrl-C in a modem window will close the scheduler down, and then the scheduler will close everything else down (if configured). 3) Send an Abort message to the scheduler: rx "Address JAMMAIL Abort" 4) If the scheduler is not configured to abort all other lines, abort messages will need to be sent to each active line as well as the scheduler. ************************************************* NB: All abort commands will wait untill the current session (if there is one) is finished. Pressing Ctrl-D in a modem/scheduler window typically will timeout any waiting/delay that is being done by that window. ************************************************* Q) How do I shutdown a single JamMail line/modem? A) if you are really sure you want to do this: rx "Address JAMMAIL1 Abort" Aborts line 1 rx "Address JAMMAIL2 Abort" Aborts line 2, etc... Q) After shutting down a single line, how can I get it to operate again? A) assuming the line was shut down as explained in the previous question: launch JAMMAIL1 jammail!startup-1 1 25000 would launch line 1 launch JAMMAIL2 jammail!startup-2 1 25000 would launch line 2, etc... Q) How about starting/stopping the scheduler? A) JamMail currently is not designed to operate without a scheduler. Previously there was an option to operate without the scheduler but it has been removed. In future versions, there will be two different schedulers built in. The first one will be an expanded version of the current scheduler. The second one, will be a very simple one that a "point" type system would use to poll only their boss, and they'd likely close down after a good session. Q) Can I setup xxxxx File server designed for TrapDoor? A) Yes. All file request servers designed for TD (or any other mailer, as long as its external) should be launchable from JamMail. Q) How? A) It is going to vary between different freq servers. Typically, its going to require the editing of both the XferqSH command line (configured in Menu A), and the contents of the Freq.cfg file (as named in menu 9). XferqSH is currently being used to handle Freq servers. It has a small built in Freq server, but most people are not going to use it. NB: If you are going to support UserFreqs, you may want to copy what you put in the Freqcfgs variable/command line, into the userfreq equivalents. The only difference may be a switch (if the server supports it), to return a textual response to the user, instead of a fidonet message packet. That would be set in the UserFreqcfg file if necessary/possible. There are two methods of launching a Freq server, Synchronously (like TrapDoor, or an MS-Dos system), or Asynchronously (multi- tasking!). Most freq servers designed for TD, will still run Asynchronously, and if it works, you should definately attempt to setup your server like that. In a recent message to Brendan Pratt about launching FFRS, this was part of my response (sort of edited). JM> > My Freq command under TrapDoor is :- JM> > JM> > FREQUEST "Xeno:FFRS Mail:FFRS.cfg %i %o %B %n %S" JM> For synchronous execution edit the freqcfg file to have this line: JM> #?.req xeno:ffrs mail:ffrs.cfg %R %O %S JM> For Asynchronous execution: JM> #?.req run xeno:ffrs mail:ffrs.cfg %R %o %S JM> ^^^ ^^ (small %o) JM> In the "Freq Server" xferq menu, the last "field" should be: JM> \"$(baud) $(remote.zone):$(remote.net)/$(remote.node).$(remote.point) Sysop\" JM> this would replace the "received at $(baud) on line.date $