Hello mark   
      
      
    IS> sbbsecho.cfg file :-   
      
    ml> /there/ ya go :)   
      
    IS> -----------------------------------------------   
    IS> PKTPWD 1:14/400 XXXXXXXX   
    IS> PKTPWD 1:340/400 XXXXXXXX   
      
    ml> make sure you change your PKT passwords with those two systems unless   
    ml> the ones i X'd out were already faked by you for this posting... and   
    ml> your AREAFIX passwords!   
      
     ok, I have changed all password.   
      
      
      
    IS> DIRECT 1:14/400 1:229/426 3:770/1 1:340/400   
      
    ml> there's one of the lines i was after...   
      
    IS> ROUTE_TO   3:770/1 3:770/1   
    IS> ROUTE_TO   1:340/400 1:340/400   
      
    ml> and there's the other ones...   
      
    ml> ok, so you do not have any fallback "catch all" routes in place... you   
    ml> need something to tell sbbsecho where to send netmails that do not have   
    ml> any other directions... so we'll do that here... edit your sbbsecho.cfg   
    ml> and change the two lines above like this...   
      
    ml>  ROUTE_TO   3:770/1 3:ALL   
    ml>  ROUTE_TO   1:340/400 1:ALL 2:ALL 4:ALL   
      
     okay I have done this I edited sbbsecho.cfg in echocfg sbbsecho.cfg menu   
     it looked like this    
      
    1:340/400   
    3:770/1   
    1:ALL   
    3:ALL   
      
      
      
    ml> you don't need to route mail thru a system to itself... the above two   
    ml> changes will   
      
    ml>  * route all non-direct Z3 netmail to paul hayton's system   
    ml>  * route all non-direct Z1, Z2 and Z4 netmail to robert starr's system   
      
    ml> that should all netmails to any system to be sent routed... the four   
    ml> systems listed in your DIRECT line above are the only ones that will go   
    ml> DIRECT -=unless=- you have SCFG->Networks->FidoNet EchoMail and NetMail   
      
    ml>  - NetMail Defaults to Crash  Yes  AND/OR   
    ml>  - NetMail Defaults to Direct Yes  AND/OR   
    ml>  - NetMail Defaults to Hold   Yes   
      
   I have done this not sure why yes on hold though.   
      
      
      
      
    ml> those control netmail from within synchronet... we keep them all set to   
    ml> No so the routing laid out in sbbsecho.cfg takes over and controls   
    ml> where things go...   
      
    ml> the only other thing i can think of is your FIDOIN and FIDOOUT events   
    ml> in SCFG->External Programs->Timed Events...   
      
    ml>   FIDOIN        %!sbbsecho%. -belrsy!   
    ml>   FIDOOUT       %!sbbsecho%. -linf   
      
     done   
      
    ml> i /know/ that the FIDOIN command line is slightly different than the   
    ml> default that comes with synchronet... one change was the order of the   
    ml> options... the other change is more important in some respects in that   
    ml> it allows users on your bbs to write netmail to another user on your   
    ml> bbs... they shouldn't use netmail for this but they can... what happens   
    ml> is that the netmail is exported into the sbbs netmail directory and it   
    ml> would sit there and not go any further... the additional option in the   
    ml> above FIDOIN tells sbbsecho to import those local netmails back into   
    ml> the bbs since they are destined to a user on the bbs... in other words,   
    ml> local and foreign netmail written to users on your bbs will be imported   
    ml> to them...   
      
    ml> in any case, i think the above should take care of netmail from the bbs   
    ml> going routed... you can try using FM to send netmail if your FD netmail   
    ml> area is still pointing at the sbbs netmail directory... the key is that   
    ml> when you write netmail in FM, you'll also need to touch the   
    ml> sbbs\data\fidoout.now semaphore file or wait for someone to write a FTN   
    ml> network message on the bbs for that event to be triggered and the mail   
    ml> scanned out... you might need to touch the sbbs\data\fidoin.now   
    ml> semaphore in some cases to toss mail into the bbs... your mailer should   
    ml> be creating the fidoin.now one already so that mail is tossed when it   
    ml> arrives... unless you have a cron job doing that for you on a certain   
    ml> schedule ;)   
      
    ml> alright... i've been up over 24 hours again and i'm rambling...   
    ml> sorry... i'm off'a'here ;)   
      
      
   just to let you now whats happening it taurus outbound menu    
      
   post a netmail  and in taurus outbound menu    
   first line 3:770/330   
   open the + one netmail message   
   poll 1:340/400   
   it int as to trys to send it but just won't it is though it cannot fine the pkt   
      
   to send   
      
   Thank you for your help and sorry if I keep you up 24 hours working on this.   
      
   Ian Segers   
      
   ... http://www.1stchoicecore.co.nz...drop in same time   
   --- MultiMail/Win32 v0.49   
   --- SBBSecho 2.12-Win32   
    * Origin:  (3:770/330)