On Wed, 03 Dec 2014, Ian Segers wrote to mark lewis:

 ml> ahhh... yes, that complicates things a little more... right now i'm
 ml> thinking that sbbsecho will hopefully see those and pack them into
 ml> BSO/FLO style and set them where they need to be for delivery... i
 ml> think we're getting down to your route_to lines missing default (aka
 ml> catch all) routing... that's why i wanted to see the above two
 ml> mentioned sets of lines from your sbbsecho.cfg file ;)

 IS> Not sure if this will help you at all

 IS> sbbsecho.cfg file :-

/there/ ya go :)

 IS> -----------------------------------------------
 IS> PKTPWD 1:14/400 XXXXXXXX
 IS> PKTPWD 1:340/400 XXXXXXXX

make sure you change your PKT passwords with those two systems unless the ones
i X'd out were already faked by you for this posting... and your AREAFIX
passwords!

 IS> DIRECT 1:14/400 1:229/426 3:770/1 1:340/400

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

and there's the other ones...

ok, so you do not have any fallback "catch all" routes in place... you need
something to tell sbbsecho where to send netmails that do not have any other
directions... so we'll do that here... edit your sbbsecho.cfg and change the
two lines above like this...

 ROUTE_TO   3:770/1 3:ALL
 ROUTE_TO   1:340/400 1:ALL 2:ALL 4:ALL

you don't need to route mail thru a system to itself... the above two changes
will

 * route all non-direct Z3 netmail to paul hayton's system
 * route all non-direct Z1, Z2 and Z4 netmail to robert starr's system

that should all netmails to any system to be sent routed... the four systems
listed in your DIRECT line above are the only ones that will go DIRECT
-=unless=- you have SCFG->Networks->FidoNet EchoMail and NetMail

 - NetMail Defaults to Crash  Yes  AND/OR
 - NetMail Defaults to Direct Yes  AND/OR
 - NetMail Defaults to Hold   Yes

those control netmail from within synchronet... we keep them all set to No so
the routing laid out in sbbsecho.cfg takes over and controls where things go...

the only other thing i can think of is your FIDOIN and FIDOOUT events in
SCFG->External Programs->Timed Events...

  FIDOIN        %!sbbsecho%. -belrsy!
  FIDOOUT       %!sbbsecho%. -linf

i /know/ that the FIDOIN command line is slightly different than the default
that comes with synchronet... one change was the order of the options... the
other change is more important in some respects in that it allows users on
your bbs to write netmail to another user on your bbs... they shouldn't use
netmail for this but they can... what happens is that the netmail is exported
into the sbbs netmail directory and it would sit there and not go any
further... the additional option in the above FIDOIN tells sbbsecho to import
those local netmails back into the bbs since they are destined to a user on
the bbs... in other words, local and foreign netmail written to users on your
bbs will be imported to them...

in any case, i think the above should take care of netmail from the bbs going
routed... you can try using FM to send netmail if your FD netmail area is
still pointing at the sbbs netmail directory... the key is that when you write
netmail in FM, you'll also need to touch the sbbs\data\fidoout.now semaphore
file or wait for someone to write a FTN network message on the bbs for that
event to be triggered and the mail scanned out... you might need to touch the
sbbs\data\fidoin.now semaphore in some cases to toss mail into the bbs... your
mailer should be creating the fidoin.now one already so that mail is tossed
when it arrives... unless you have a cron job doing that for you on a certain
schedule ;)

alright... i've been up over 24 hours again and i'm rambling... sorry... i'm
off'a'here ;)

)\/(ark

If you think it's expensive to hire a professional to do the job, wait until
you hire an amateur.

--- FMail/Win32 1.60
 * Origin:  (1:3634/12.71)