Subj : I thing I give up
To   : Joacim Melin
From : Javier Sturman
Date : Tue Oct 14 2025 11:39 pm


   Hello Joacim!

14 Oct 25 13:16, you wrote to all:

Have you tried killing binkd process manually? It happened to me many times when I'm/was trying to test binkd I ran into weird behaviours.
I was restarting the service -FreeBSD- sudo service binkd restart but somehow not everytime took the config changes, then one time I k9ed every binkd pid.


 JM> I used to have all this stuff working for years but for some goddamn
 JM> reason it's not anymore.

 JM> Fidonet (in and outgoing) works fine. Netmail to other networks (in
 JM> and outgoing) works fine but regular packets (echomail) to other
 JM> networks does not.

 JM> this is from Binkd:

 JM> domain fidonet /fido/outbound 2
 JM> domain fido alias-for fidonet
 JM> domain fidonet.org alias-for fidonet
 JM> domain amiganet /fido/amiganet 2
 JM> domain fsxnet /fido/fsxnet 2
 JM> domain micronet /fido/micronet 2

 JM> This is from crashmail.prefs:

 JM> INBOUND /fido/inbound/
 JM> OUTBOUND /fido/outbound/
 JM> STATSFILE /etc/binkd/CrashMail.stats
 JM> TEMPDIR /fido/tmp/
 JM> CREATEPKTDIR /fido/tmp/
 JM> PACKETDIR /fido/packets/


 JM> Now, this is not an static error. For some reason, Binkd would send a
 JM> number of packets to Amiganet and then when I write some more messages
 JM> it will not touch it.

 JM> This file tells Binkd what to send (I think):

 JM> ftn@bbsutils:/fido/amiganet.027$ ls
 JM> 009600c8.try

 JM> In the packets directory lies the package itself:

 JM> ftn@bbsutils:/fido/packets$ ls
 JM> ee2fef00.pkt


 JM> I've checked: file permissions, network, DNS. It's all correct.  And
 JM> as I said: it all works with Fidonet.

 JM> I have no idea what to try next.  Any ideas are welcome.


 JM> --- NiKom v2.6.0
 JM>  * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:221/242.0)

Javier


--- GoldED+/BSD 1.1.5-b20170303-b20170303 + HPT 1.9.0 + Binkd 1.1a-115
 * Origin: FIDONODO DE JAS | ¯\_(O,O)_/¯ (4:900/733)

.