ml>  On 2017 Sep 17 10:56:10, you wrote to All:

 JM>> Any netmail sent to AmigaNet is picked up by Crashmail:

 JM>> 1 message exported
 JM>> Scanning for orphan files
 JM>> Scanning for old packets
 JM>> Scanning for new files to pack
 JM>> Sending unpacked netmail to 39:150/200.0 (Normal)
 JM>> Updating hwm for area NETMAIL, old = 17, new = 18
 JM>> CrashMail end

 JM>> But it is never sent by Binkd.

 ml> assuming that crashmail does netmail in the traditional BSO way using
 ml> ?UT files, where did crashmail put the ?UT file? which of your BSO
 ml> outbound directories and what name did it use??

Here's the thing: Crashmail can only use one (1) directory for it's
outbound mail. Which is fine. 

When I create a netmail for a Fidonet recipient, Crashmail finds it: 

1 message exported
Scanning for orphan files
Scanning for old packets
Scanning for new files to pack
Sending unpacked netmail to 2:201/0.0 (Normal)
Updating hwm for area NETMAIL, old = 19, new = 20


I can verify this in the logs: 

Exporting message #20 from "Joacim Melin" to "joacim
melin" at 2:201/420 Uses this route statement: ROUTE
"2:*/*.*" "2:201/0.0" "2:201/120" Routing
message to 2:201/420.0 via 2:201/0.0

A token file to trigger a crash send is created in the outbound directory:


drwxrwxrwx  2 nobody 4294967294 4096 Sep 17 16:16 . drwxrwxrwx 28 nobody
4294967294 4096 Sep 17 14:30 .. -rw-r--r--  1 nobody 4294967294  356 Sep 17
16:16 00c90000.out

So far, so good. 

When I create a netmail to a recipient in AmigaNet, here is what happens: 

Exporting message #19 from "Joacim Melin" to "areafix"
at 39:150/200 Uses this route statement: ROUTE "39:*/*.*"
"39:150/200.0" "39:160/242" Routing message to
39:150/200.0 via 39:150/200.0


Again, looks good. But, and a big but: the token file to crash it to
39:150/200 is never created in the outbound directory. This, I guess, is
simply because Crashmail only can handle one Netmail area for one network,
in my case Fidonet. 

I will do some more experimenting. Maybe I need to use separate config
files for each network.  

I'll report back later. 


--- NiKom v2.3.1