I have a big issue with Crashmail II (v0.88) and possibly Binkd (Binkd 1.1a-92 (Mar 6 2016 22:36:59/Linux)). I really can't anywhere else to turn with this issue so if this is totally the wrong place, I apologize, and if anyone want to help me via netmail or email instead, I'd appreciate it.

I have several AKA:s in crashmail.prefs:

AKA 2:203/242.0
DOMAIN "FidoNet"

AKA 111:7046/42.0
DOMAIN "STN"

AKA 80:774/5.0
DOMAIN "Retronet"

AKA 46:2/106.0
DOMAIN "Agoranet"

AKA 21:1/116.0
DOMAIN "Fsxnet"

As long as Fidonet is on top, Crashmail will happily create the pointer file that tells Binkd what packages to send. If I move down one notch to the top of
the list, STN works but Fidonet or Retronet or whatever will not work.

The outgoing packages is still created but the "pointer" file is not created by
Crashmail.

Anyone have any ideas?

Thanks,

Joacim

--- NiKom v2.1.2
* Origin: Delta City BBS (deltacity.se, +46-8-6058800) (2:203/242.0)

Hello Joacim!

I cannot help you, although I do have a point system runn ing Binkd and
Crashmail. I is far simpler in setup as it has only one address.

I do have a few questions, that may lead you in the proper direction.

As Binkd is a BSO system, it expects separate outboud directories for each
zone. With the higher zone numbers some systems expect the suffix of the
outbound to be in octal notation, other expect hex notation.

Have you looked at your logfiles, there may be some clues about missing
directories.

Your RC Bjorn Felten claims to be a longtime user of Crashmail, his
experience may include the use of AKA's in several domains.

Crashmail was developed by a Swedish sysop, some may know how to contact him.
Johan Billing is no longer in Fidonet. Others who have worked on Crashmail
are RJ Clay and Lars Lars Kellog-Stedman.

Have you considered using different PREFS files for the different domains you
whish to cover?


15 Aug 16 18:42, you wrote to All:

I have a big issue with Crashmail II (v0.88) and possibly Binkd (Binkd 1.1a-92 (Mar 6 2016 22:36:59/Linux)). I really can't anywhere else to turn with this issue so if this is totally the wrong place, I apologize, and if anyone want to help me via netmail or email instead, I'd appreciate it.

I have several AKA:s in crashmail.prefs:

AKA 2:203/242.0
DOMAIN "FidoNet"

AKA 111:7046/42.0
DOMAIN "STN"

AKA 80:774/5.0
DOMAIN "Retronet"

AKA 46:2/106.0
DOMAIN "Agoranet"

AKA 21:1/116.0
DOMAIN "Fsxnet"

As long as Fidonet is on top, Crashmail will happily create the pointer file that tells Binkd what packages to send. If I move down one notch to the top of the list, STN works but Fidonet or Retronet or whatever will not work.

The outgoing packages is still created but the "pointer" file is not created by Crashmail.

Anyone have any ideas?

Thanks,

Joacim

--- NiKom v2.1.2
* Origin: Delta City BBS (deltacity.se, +46-8-6058800) (2:203/242.0)

Kees

--- GoldED+/LNX 1.1.5
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

15 Aug 16 19:39, Kees van Eeten wrote to you:

I cannot help you, although I do have a point system runn ing Binkd
and Crashmail. I is far simpler in setup as it has only one address.

i can't help very much, either...

I do have a few questions, that may lead you in the proper direction.

kinda same here as well...

As Binkd is a BSO system, it expects separate outboud directories for
each zone. With the higher zone numbers some systems expect the suffix
of the outbound to be in octal notation, other expect hex notation.

in BSO systems, you need to have the addresses in the same order in both tosser
as well as mailer... this is because the default outbound is for whatever zone you have listed first and all the others get the hex extensions added to them... at least the first (aka default) zone must be the same in all BSO tools...

)\/(ark

Always Mount a Scratch Monkey

... Remember that the customs of your tribe are not laws of nature!
---
* Origin: (1:3634/12.73)

Hi Kees,

After thinking long and quite hard about this, I went with separate configurations for each domain. I asked Bj÷rn about it and even he knows almost everything worth knowing, he could not answer my questions. The developer of Crashmail, Johan Billing, seems to have disappeared and his email address does not work. The last maintainer of the Crashmail source code is on Twitter and said something to the effect of "You can ask me but I haven't touched the code for years" and then went on not answering any of my questions.


Anyway, it works now. Happy, happy.

Regards,

Joacim

--- NiKom v2.1.2
* Origin: Delta City BBS (deltacity.se, +46-8-6058800) (2:203/242.0)

15 Aug 16 19:39, Kees van Eeten wrote to you:

I cannot help you, although I do have a point system runn ing Binkd
and Crashmail. I is far simpler in setup as it has only one address.

i can't help very much, either...

I do have a few questions, that may lead you in the proper direction.

kinda same here as well...

As Binkd is a BSO system, it expects separate outboud directories for
each zone. With the higher zone numbers some systems expect the suffix
of the outbound to be in octal notation, other expect hex notation.

in BSO systems, you need to have the addresses in the same order in
both tosser as well as mailer... this is because the default outbound
is for whatever zone you have listed first and all the others get the
hex extensions added to them... at least the first (aka default) zone
must be the same in all BSO tools...

Very interesting. I was not aware of this at all. They are probably not in the same order, except for Fidonet which is the first address/AKA in both configurations.

I will examine this further.

Thanks,

Joacim

--- NiKom v2.1.2
* Origin: Delta City BBS (deltacity.se, +46-8-6058800) (2:203/242.0)

16 Aug 16 22:28, you wrote to me:

in BSO systems, you need to have the addresses in the same order in
both tosser as well as mailer... this is because the default outbound
is for whatever zone you have listed first and all the others get the
hex extensions added to them... at least the first (aka default) zone
must be the same in all BSO tools...

Very interesting. I was not aware of this at all. They are probably
not in the same order, except for Fidonet which is the first
address/AKA in both configurations.

the main point i was making, which i think you did get but want to reenforce, is that the first one needs to be the same in all BSO tools... the AKAs (those after the default) should be able to be in any order since they are the ones which get the hex code zone extensions... i've found it best and easiest to just keep them all in the same order ;)

)\/(ark

Always Mount a Scratch Monkey

... Don't listen to her though. She's a troublemaker. Everybody knows it.
---
* Origin: (1:3634/12.73)