Hi Joacim,

On 2017-12-07 20:27:03, you wrote to All:

 JM> quick question: I got a setup with Crashmail II tossing and scanning
 JM> FTN style mail for my BBS. It all works fine with Fidonet but if I add
 JM> a second network to my BBS, to Crashmail II and to Binkd it goes
 JM> south. Binkd will not touch any outgoing mail to any other network
 JM> than Fidonet. In my case, I'm also a member of Aminet and any mail
 JM> created for Aminet is found and put in the outgoing folder by
 JM> Crashmail II.  Once there, Binkp will not even send it if my Aminet
 JM> HUB will connect to me and send me mail.

 JM> Here's Crashmail II's output:

 JM> Exporting message #8 from "Joacim Melin" to "All" in SYSOP_AMY 1
 JM> message exported Scanning for orphan files Scanning for old packets
 JM> Scanning for new files to pack Sending 29974200.pkt unpacked to
 JM> 39:150/200.0 Updating hwm for area SYSOP_AMY, old = 7, new = 8
 JM> CrashMail end

 JM> Binkp does... nothing at this point. Just sits there.

 JM> I see two possible issues:

 JM> 1. Crashmail II only has one (1) setting for outgoing mail:

 JM> INBOUND /fido/inbound/
 JM> OUTBOUND /fido/outbound/

 JM> Maybe Binkp would like it better if outgoing mail for different networks
 JM> was sorted in different folders?

Outbound pkt files for other zones should be put in seperate automatically
created directories.

For instance:

FidoNet Zone 1 -> /fido/outbound.001
AmigaNet Zone 39 -> /fido/outbound.027

You don't specify these either in your binkd.conf! This would look like:

domain fidonet  /fido/outbound 2
domain AmigaNet /fido/outbound 2



Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815