Subj : RFC seriously
To   : Ian Segers
From : mark lewis
Date : Tue Dec 02 2014 21:30:53


 On Tue, 02 Dec 2014, Ian Segers wrote to mark lewis:

 IS> these directories, do I have to create them myself or does taurus
 IS> creates them itself.

your mail tosser should create them as needed and then only for the zones that 
mail is destined to... in some cases, a mailer may remove them when there is no 
more mail in them to be sent but i don't recall if the argus family does this 
or not... i have seen it in my taurus but only fleetingly and only once...

[trim]

 ml> taurus should not be looking in any special directory for 
 ml> netmail... sbbsecho has to do your netmail packing and routing... 
 ml> with that said, what does your sbbsecho.cfg contain for its DIRECT 
 ml> and ROUTE_TO lines?

 IS> Direct is yes

hunh? are you talking about in some of your node entries in echocfg? i was 
looking for the line from your sbbsecho.cfg file...

 IS> ROUTE_TO is set to my provider 1:340/400

can you post those lines, too, please? i'm looking to see what happens with 
netmail to nodes that you do not have specific routing for...

 IS> Netmail format is *.msg and front door I use to post a netmail
 IS> message 

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

)\/(ark

 
* Origin:  (1:3634/12)

SEEN-BY: 229/426 103/705 218/720 214/22 102/401 103/1 218/215 840 301/1
SEEN-BY: 218/860 880 601 870 930 124/5016 218/700 1 10/1 218/0 10/0

.