Subj : Squish Areafix To : Joe Davis From : Bob Jones Date : Thu Jul 31 2003 09:16 am JD>> Somehow, Squish magically tosses to the right JD>> area... not sure how... thats another story. :) I'd have to look up how I'm doing it. JD>> But, having more than one netmail area, and using SqaFix, JD>> requires one to use something like FTrack or NetMgr, to scan JD>> for, locate and move netmails for SqaFix to the one msgarea JD>> that it can scan. ml> wouldn't that be covered by having different configs for each ml> network? JD> Not sure of your meaning yet. JD> Do you mean a different Squish.cfg for each network? JD> ...hmmmm.... I don't think so. I don't believe that's what he ment. If I was going to do it, it would be with multiple sqafix.cfg files, with each sqafix configuration in their own subdirectory. And running sqafix once for each of the different subdirectories. JD> I found what was in the back of my mind, when I used JD> the term magically. :) JD> This is from an original Squish.cfg: JD> ; Every system must have at least one NetArea. You can declare JD> ; more NetAreas if you like (and Squish will scan all of them when JD> ; packing mail). All inbound NetMail will be placed into JD> ; this area. JD> If you have it handy, have a look at it, so it is not out of context. JD> I read it that the "all inbound netmail will be placed JD> into this area" is referring to the one netarea that JD> this portion of Squish.cfg comments is leading one to JD> create. JD> I don't recall ever finding in Squish.doc, an JD> explanation of how to tell Squish to seperate and toss JD> to different netmail areas, according to the Zone. It's been a long time since I've read the docs, but I think you will find the info in the area related to multi-zone stuff. Squish is 3d or 4d aware, but not 5-d aware. From memory, if you set up a netmail address with an alternate primary address that is a *different* zone number, then squish will toss stuff to that different zone number in the first netmail area that has that zone number for the (alternate) primary address... JD> Venturing a guess, Squish does it based on some sort of JD> Zone matching, based on if it finds a -p . JD> Like this: JD> NetArea FN_Net e:\mypathhere -$ -p1:261/1380 JD> NetArea STN_Net e:\mypathhere -$ -p111:4025/105 Without looking at my configs, I believe you got it. And as a result, SqaFix can not be run as a single configuration for Fidonet and for STNnet in your example..... Which can cause "fun" when you have a downlink that is in both nets.... The down link would also have to make sure that they link to sqafix using their correct zone based FTN address, or the request wouldn't work.... JD> What do you think? possible? probable... ? I think you got it. ml> seems to me that sqafix is based kinda like FD and ml> others... i have a ml> main netmail area that is for the mailer and tools... all netmail ml> passes thru it... however, on the bbs, there are seperate netmail ml> areas for each of the networks... what i do is to run the areafix ml> stuff before tossing the messages into the other netmail areas... ml> rather than running something to bring them back out... Actually, I think SqaFix was designed just for a single network... The way SqaFix is designed, it prevents a user in zone 1 from adding echos distributed in zone 111 (using Joe's example above)... Which is a *good* thing.... Moderators in fidonet would complain if someone had an out-of-fidonet address in their origin line on a fidonet echo.... It would also screw up the seen-by information, possibly causing some systems to not see the message. [Echomail routing is *still* 2d for handling mesh routing within a zone. And zone 1 operates on a mesh basis....] So, adding additional netmail areas to SqaFix also means SqaFix needs to be beefed up to keep track of zone number vs echo area and handle requests accordingly.... Hmmmmm...... Take care..... Bob Jones, 1:343/41 --- Maximus/2 3.01 * Origin: Top Hat 2 BBS (1:343/41) .