Hi Joacim,

On 2017-12-07 21:41:17, you wrote to me:

 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
 JM>>> networks was sorted in different folders?

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

 WvV>> For instance:

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

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

 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.

That's not correct, binkd won't look in there. It should be /fido/outbound.027.
Did you configure that in the crashmail config? Or did crashmail come up with
that all by itself?

 JM> In there is the outgoing packet that was created earlier tonight. But
 JM> it's still not sent out properly.  The content of the 009600c8.clo is
 JM> as follows:

A .clo file is not a packet!

 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. I
 JM> wonder if the ^ symbol in front of the path is what mess things up. I have
 JM> no idea where that symbol comes from though.

No that has nothing to do with it. Torsten explained it...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815