Subj : IREX & LoraBBS To : Russell Tiedt From : Peter Knapper Date : Tue Dec 26 2000 02:26 am Hi Russell, PK> I don't know Lora BBS at all sorry, however using a Binkley style PK> outbound (BSO), if your PRIMARY zone is defined as Zone 5, then - PK> Outbound is Zone 5 PK> Outbound.001 is Zone 1 PK> Outbound.002 is Zone 2 PK> etc RT> Outbound FamilyNet - POTS RT> Outbound.001 Zone1 - IREX - e-mail RT> Outbound.002 CCCNet - POTS RT> Outbound.005 Zone2, 3, 4, 5, 6 - IREX - FTP RT> Outbound.0DC ???????? Ah yes, of course (ZONK, sound of hand hitting head......;-)), now I remember, your PRIMARY zone is Familynet (Zone 8), which will have traffic ending up in Outbound. However the above list still does not seem quite right because you have 2 x Zone 2's in the SAME Outbound structure, even though they are in different networks!!! Remember that FIDONET work using BSO is going to find OUTBOUND.002 and that COULD be VERY confusing. Now I dont know how CCCNET fits into this, if it truly uses Zone 2, then you have a SERIOUS clash between Fidonet and CCCNet Zone numbering there, and the only way I can see to work around this is to move ALL CCCNET mail and traffic into a completely different OUTBOUND directory structure from everything else in TOTAL! You may also need to move CCNET INBOUND traffic into a different structure, and THEN use unique Inbound & Outbound mail processing to keep Fidonet and CCCNET apart. IE: You should probably have something like this to get true BSO working properly without having the Zone clash. Note: All Zones are defined, however they may not ALL be required if your Routing forces mail via a comon path. I ALWAYS define all Fidonet Zone directories regardless of actual use, because this makes things VERY clear and allows CRASh mail to those Zones to still work normally - \Fido\Outbound Familynet Zone 8 \Outbound.001 Fido Zone 1 .002 Fido Zone 2 .003 Fido Zone 3 .004 Fido Zone 4 .005 Fido Zone 5 .006 Fido Zone 6 .0DC Whatever Zone 220 is!!! \CCCNet\Outbound CCCNet Zone 2 (Note no Extn.) Note that if your mail PROCESSOR has NEVER directly (IE not ROUTED mail) packed mail for a Zone, or your mailer has never CONNECTED with a Zone (IE you ROUTE mail via other Zones), then you may not have an OUTBOUND.nnn directory created for that Zone. I take your Fidonet config to suggest that you connect directly with Zone 1 (via IP) but route all other Fido Zones via your Zone 5 connection(s). The issue that I see above is that CCCNet is going to have the potential of confusing your mail handling tasks as far as distinguishing between the 2 x Zone 2's is concerned. Fortunately Familynet and Fidonet do not clash zone numbers, so the one Outbound structure can be used, but not for your SECOND Zone 2! For true BSO operation, the OUTBOUND directory .EXT should match the HEXADECIMAL version of the DECIMAL ZONE numbers you are connecting with EXACTLY (except that your DEFAULT zone has no .EXT). BSO works fine for all FTN's that do NOT clash in Zone numbers. When they do clash, you have to build a totally unique inbound/outbound/handling structure. Ok, going back to your original question, you say the compressed mail files (.MOx, .TUx, etc) just sit there, and don't move. Well in themselves they do nothing to drive the Mailer (POTS or IP) operation anyway, its the .FLO (.HLO, ..NLO, .CLO, etc) files that actually drive the Mailer(s). Find these for each set of compressed mail files tjhat are nt moving and you should have your answer. Also remember that if your BBS and Mail processing happens using Zone 8 as your PRIMARY Zone, then ALL your MAILER (IS POTS & IP) operations MUST ALSO use Zone 8 as their PRIMARY zone, otherwise it wont look in the right place for the important files (the FLO files). Things can also get a bit complicated when using Internet and POTS mailers sharing a common Outbound structure because you don't (normally) want IP traffic to be moved by your POTS mailer and vice versa, so setting IP mail to ..CLO is not normally desired, however I dont know IREX at all so I am not sure exactly how it handles this. I use BinkD and force BinkD to send to whichever IP node I wish to process by passing it commandline parameters. That way if my IP connection ever fails I can fall back to POTS transfers by simply renaming the .HLO file as required. If you BSO config is fine for ALL your S/W, then you should also be able to do the same. We took a while to get back to the original question but I think we made it eventually.........;-) Cheers...........pk. --- Maximus/2 3.01 * Origin: Another Good Point About OS/2 (3:772/1.10) .