Subj : Re: Binkd nondinnding to certain networks
To : Wilfred van Velzen
From : Joacim Melin
Date : Thu Dec 07 2017 09:41 pm
WvV> Hi Joacim,
WvV> 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:
Thanks for your input! I noticed now that there are a folder named
/fido/AmigaNet.027. In there is the outgoing packet that was created earlier
tonight. But it's still not sent out properly. The content of the 009600c8.clo
is as follows:
Which, I guess, is all the outgoing packets that hasn't been sent yet. I wonder
if the ^ symbol in front of the path is what mess things up. I have no idea
where that symbol comes from though.