Subj : Re: sbbsecho.cfg To : Nicholas Boel From : Bill McGarrity Date : Mon Nov 06 2017 20:25:55 -=> On 01-09-15 16:04, Nicholas Boel wrote to Bill McGarrity <=- Hiya Nick... NB> On 09 Jan 15 14:38, Bill McGarrity wrote to Joe Delahaye: BM> domain fidonet c:\fd\outbound 1 binkd.net BM> I didn't have the binkd.net at the end of it. I checked the logs and BM> that gave me the answer. Now it uses it properly as I can now BM> direct/crash to any node listed. As soon as I get whispnet and BM> micronet compiled, I can remove all the ROUTE_TO's in the sbbsecho.cfg BM> file.... NB> Wait, what? I don't think you can remove your sbbsecho.cfg NB> configuration because you compile a nodelist for your mailer. All that NB> does is make your connections for you. sbbsecho still needs to know NB> where to direct netmail to, otherwise it will create wrong filenames NB> and binkd won't send it anywhere. I'm pretty sure the route_to is for netmail, not echomail. I've already told sbbsecho my uplink for echomail and when tossed it creates a PKT and a .CLO. If indeed I am right, then any nodelisted address I put in the netmail, a .MSG will be created, then fidoout will look at the To: address and create a .CUT using the hex address for the actual node it's going to. Binkd reads that cut and dials that node directly. Why route it if you can do it direct. Now with whispernet and micronet, being I haven't compiled a nodelist binkd can understand, I have to route through my hubs. That's the way I see it. Again, I maybe wrong but so far every netmail I have sent has gone direct and all my echomail is going to Janis and Björn properly. Bill Telnet: tequilamockingbirdonline.net Web: bbs.tequilamockingbirdonline.net FTP: ftp.tequilamockingbirdonline.net:2121 IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697 Radio: radio.tequilamockingbirdonline.net:8010/live .... Look Twice... Save a Life!! Motorcycles are Everywhere!!! --- MultiMail/Win32 v0.50 * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404) .