= Сообщение: 2923 из 7125 ====================================== FTSC_PUBLIC = От : Bill McGarrity 1:266/404 02 Jun 17 16:09:00 Кому : Joe Bruchis 02 Jun 17 16:09:00 Тема : Binkp and Binkd not reading outbound FGHI : area://FTSC_PUBLIC?msgid=6913.2ftscpubl@1:266/404+1d9719a9 На : area://FTSC_PUBLIC?msgid=1:3828/12.0+9317a650 = Кодировка сообщения определена как: ASCII ================================== ============================================================================== -=> Joe Bruchis wrote to All on 06-02-17 10:30 <=-
JB> Hello All!
JB> I have ECHOCFG setup with a Binkley style front end. I have Internet JB> Rex (binkp) and BINKDWIN (binkd) also set up as Binkley flo mailers. I
You only need one of those mailers. I'd can Irex and use binkd.
JB> belong to 2 nets, fidonet 1:3828/12 and Dixienet 901:1/11. Echo and JB> netmails in SBBS are properly scanned and packed by SBBSECHO as noted JB> on the screen during processeing and in the sbbsecho.log. SBBSECHO JB> places outbound messages for 901:1/1 in an outbound called JB> \outbound.385. I have tried sending packets to my uplink using both JB> binkp and binkd. In both I have the path to my outbound as JB> c:\sbbs\fido\outbound. In SBBS I have the same path to my outbound. Why JB> is SBBSECHO placing the mail in \outbound.385? I tried manually moving JB> the packets from \outbound.385 to \outbound and still, neither bink JB> recognizes mail after a rescan.
binkd works on hex addressing. The conversion for decimal 901 is hex 385. Sbbsecho puts it in that folder automatically which it should.
I would first look at your binkd.cfg and make sure the following are set:
Make sure you also have a binkd style nodelist to tell what the INA of each node is.
I would also like to look at your sbbsecho.ini file to make sure you have zone-blind set correctly. Also, sbbsecho should create a *.*LO and/or *.*UT file. Let us know what those are as well...
