Subj : IREX & LoraBBS To : Peter Knapper From : Russell Tiedt Date : Tue Dec 26 2000 01:03 am PK> 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 ???????? PK> Ah yes, of course (ZONK, sound of hand hitting head......;-)), now I PK> remember, your PRIMARY zone is Familynet (Zone 8), which will have PK> traffic ending up in Outbound. However the above list still does not PK> seem quite right because you have 2 x Zone 2's in the SAME Outbound PK> structure, even though they are in different networks!!! Remember PK> that FIDONET work using BSO is going to find OUTBOUND.002 and that PK> COULD be VERY confusing. True, but it seems to work, also I can do nothing about it as LoraBBS is a all_in_one package. These are very nice, up to a point, that is. The documentation suggests that it is possible to to use independent mailer and tosser if LoraBBS is registered, which mine is. The problem is that it is not very clear on how to achieve this. PK> Now I dont know how CCCNET fits into this, if it truly uses Zone 2, PK> then you have a SERIOUS clash between Fidonet and CCCNet Zone PK> numbering there, and the only way I can see to work around this is to PK> move ALL CCCNET mail and traffic into a completely different OUTBOUND PK> directory structure from everything else in TOTAL! You may also need PK> to move CCNET INBOUND traffic into a different structure, and THEN PK> use unique Inbound & Outbound mail processing to keep Fidonet and PK> CCCNET apart. PK> \Fido\Outbound Familynet Zone 8 PK> \Outbound.001 Fido Zone 1 PK> .002 Fido Zone 2 PK> .003 Fido Zone 3 PK> .004 Fido Zone 4 PK> .005 Fido Zone 5 PK> .006 Fido Zone 6 PK> .0DC Whatever Zone 220 is!!! PK> \CCCNet\Outbound CCCNet Zone 2 (Note no Extn.) Cannot access the mailer setup - due to above reasons. Not that I would not like to. Maybe I must collect some packets for use in "testing" and see if I can get LoraBBS to stop useing it's internal mailer and tosser. PK> Note that if your mail PROCESSOR has NEVER directly (IE not ROUTED PK> mail) packed mail for a Zone, or your mailer has never CONNECTED with PK> a Zone (IE you ROUTE mail via other Zones), then you may not have an PK> OUTBOUND.nnn directory created for that Zone. I take your Fidonet PK> config to suggest that you connect directly with Zone 1 (via IP) but PK> route all other Fido Zones via your Zone 5 connection(s). True on both counts. PK> The issue that I see above is that CCCNet is going to have the PK> potential of confusing your mail handling tasks as far as PK> distinguishing between the 2 x Zone 2's is concerned. Has not so far. PK> Fortunately Familynet and Fidonet do not clash zone numbers, so the PK> one Outbound structure can be used, but not for your SECOND Zone 2! Yes PK> For true BSO operation, the OUTBOUND directory .EXT should match the PK> HEXADECIMAL version of the DECIMAL ZONE numbers you are connecting PK> with EXACTLY (except that your DEFAULT zone has no .EXT). BSO works PK> fine for all FTN's that do NOT clash in Zone numbers. When they do PK> clash, you have to build a totally unique inbound/outbound/handling PK> structure. Understood. PK> Ok, going back to your original question, you say the compressed mail PK> files (.MOx, .TUx, etc) just sit there, and don't move. Well in PK> themselves they do nothing to drive the Mailer (POTS or IP) operation PK> anyway, its the .FLO (.HLO, .NLO, .CLO, etc) files that actually PK> drive the Mailer(s). Find these for each set of compressed mail files PK> tjhat are nt moving and you should have your answer. They are placed in the Outbound directory with the *.MOx etc files. PK> Also remember that if your BBS and Mail processing happens using Zone PK> 8 as your PRIMARY Zone, then ALL your MAILER (IS POTS & IP) PK> operations MUST ALSO use Zone 8 as their PRIMARY zone, otherwise it PK> wont look in the right place for the important files (the FLO files). Ok, understood, but as above mailer is part of BBS for POTS, and IREX to move mail via Internet. PK> Things can also get a bit complicated when using Internet and POTS PK> mailers sharing a common Outbound structure because you don't PK> (normally) want IP traffic to be moved by your POTS mailer and vice PK> versa, so setting IP mail to .CLO is not normally desired, however I PK> dont know IREX at all so I am not sure exactly how it handles this. I PK> use BinkD and force BinkD to send to whichever IP node I wish to PK> process by passing it commandline parameters. That way if my IP PK> connection ever fails I can fall back to POTS transfers by simply PK> renaming the .HLO file as required. If you BSO config is fine for ALL PK> your S/W, then you should also be able to do the same. IREX can and does send mail which is on hold. PK> We took a while to get back to the original question but I think we PK> made it eventually.........;-) Yes, I hope I have now solved it, namely that my other AKA's where not set up in IREX, I have now changed this and entered them in the same order as they are entered in LoraBBS. Will test this a little later. --- Msged/LNX TE 06 (pre) * Origin: Rusty's BBS - Bloemfontein, Free State, South Africa (5:7105/1) .