Subj : Binkd nondinnding to certain networks
To   : Joacim Melin
From : Nicholas Boel
Date : Thu Dec 07 2017 04:33 pm

Hello Joacim,

On Thu Dec 07 2017 21:41:16, Joacim Melin wrote to Wilfred van Velzen:

 WvV>> domain fidonet  /fido/outbound 2
 WvV>> domain AmigaNet /fido/outbound 2

 JM> Thanks for your input!  I noticed now that there are a folder named
 JM> /fido/AmigaNet.027. In there is the outgoing packet that was created
 JM> earlier tonight. But it's still not sent out properly.  The content of
 JM> the 009600c8.clo is as follows:

 JM> ^/fido/outbound/be9ed600.pkt
 JM> ^/fido/outbound/be9f1e00.pkt
 JM> ^/fido/outbound/bea52300.pkt
 JM> ^/fido/outbound/59bea5c4.su0
 JM> ^/fido/outbound/59bea5c4.su1
 JM> ^/fido/outbound/59bea5c4.tu0
 JM> ^/fido/outbound/59bea5c4.tu1
 JM> ^/fido/outbound/59bea5c4.tu2
 JM> ^/fido/outbound/59bea5c4.tu3
 JM> ^/fido/outbound/59bea5c4.we0
 JM> ^/fido/outbound/59bea5c4.th0
 JM> ^/fido/outbound/2994e600.pkt
 JM> ^/fido/outbound/29974200.pkt

 JM> Which, I guess, is all the outgoing packets that hasn't been sent yet.
 JM> I wonder if the ^ symbol in front of the path is what mess things up.
 JM> I have no idea where that symbol comes from though.

Yes, it is. By the way it seems, binkd isn't setup correctly. Wilfred's domain 
lines for binkd are what yours should read. If that is the case, paste us the 
top portion of your binkd.conf so we can see what you do have.

You've most likely setup binkd to use 5D BSO with a line like "domain amiganet 
/fido/outbound 39", and Crashmail II doesn't support that. Make sure to use 
your Fidonet domain for any and all othernets you setup in binkd, and binkd 
will use the proper directories.

AmigaNet.027 is not a valid directory in 4D BSO, but outbound.027 is.

Regards,
Nick

.... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
 * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

.