Subj : multiple ftn addresses and maximus 3.0 To : Mvan Le From : Richard Webb Date : Sat Jun 30 2007 03:02 pm Mvan Le wrote in a message to Richard Webb: ML> Squish has this feature: ML> areaname.SQO This file is used by the Squish tosser to ML> provide a custom origin line for the given ML> area. If an .SQO file is present for a ML> given message area, the first line in the ML> file will be used as the origin line for ML> messages in that area, overriding the ML> "Origin" setting in SQUISH.CFG. Squish will ML> automatically add the "* Origin" prefix and the ML> trailing "(zone:net/node)" text. Yes, but Maximus puts an origin line on a message already, so squish doesn't. THe custom origin line works, just do it once, mark my block after the first time and paste. Just hoping somebody knew of a global solution. Three extra keystrokes after the first area is defined . NO biggie. ML> Maybe ONE DAY the Origin keyword could be used with a ML> MsgDivisionBegin declaration to solve all such gating/multizone ML> origin line inconveniences. I reckon this feature could be ML> implemented in Maximus by 2030. There ya go! THat would be cool. . Just define it once for a given message division. That's one reason I haven't bothered with divisions yet. Btw, it's one feature I liked that was added since my days sysoping 2.01 wb. Just haven't seen the need for it yet. EVentually when we're telnet ready I'm going to implement some of the other features that are basically designed for tech support type boards etc. My objective: A user of the system who's handling an emergency situ IF he/she has to hand it off to somebody else it's easily enough done. That's for later on though . Regards, Richard .... Preparation, knowledge, and discipline can deal with any form of danger. --- timEd 1.10.y2k+ * Origin: Radio REscue net operations BBS (1:116/901) .