Hi Martin,

> I don't have any problems receiving netmail, but they aren't going out.

Ah, understood. Can you send netmail directly to another node via poll or pickup, or is the issue only with routed outbound netmail?

Is there anything I can do to help with troubleshooting?

Regards,
Jason

--- FMMS - OpenVMS AXP 8.4-2L1
* Origin: Shady Labs (1:218/910)

Martin Kazmaier wrote to Jason Brady <=-

> I don't have any problems receiving netmail, but they aren't going
out.

Ah, understood. Can you send netmail directly to another node via poll or pickup, or is the issue only with routed outbound netmail?

I don't have the means to send direct netmail.

Why not? Why can't you send a direct netmail?

Nope, my feed is seeing if his netmail goes out sometime soon. He's on vacation at the moment.

Your feed has nothing to do with sending direct netmail.



... Gone crazy, be back later, please leave message.
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

Martin Kazmaier wrote to Dan Clough <=-

I don't have the means to send direct netmail.

Why not? Why can't you send a direct netmail?

I'm using binkd and fastecho with my bbs software (ele) and can't send direct! How is that so hard to understand?

Well..... that's the first time I've seen you mention that, and it's
*NOT* hard to understand. In fact, what software you're using is
COMPLETELY IRRELEVANT to your ability to send direct netmail. What
don't you understand about that?

Are you trying to say that binkd can't send direct netmail?

Your whole problem is that you don't know how to properly configure your software. Do some reading and set up your mailer correctly.


... So easy, a child could do it. Child sold separately.
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

Hi Martin,

I took the liberty of directly contacting your node via poll action. Successful handshake and the message packet appears to be accepted by your node.

Please check your inbound to see if my message arrived.

If so, reply to the message and e-mail me. I can either poll your node again to pick up the response or you can poll my node to return the response message packet.

Let me know if the message was received on your side and how you would like to proceed.

Regards,
Jason

--- FMMS - OpenVMS AXP 8.4-2L1
* Origin: Shady Labs (1:218/910)

On Sat, Nov 09 2024 14:19:00 -0600, you wrote:

Of course I got it. I always receive netmail, it just doesn't go out routed. I wouldn't know how to poll your node to return the message. binkd will only poll nodes I have manually set up in it's config.

FYI, there are scripts out there that can convert any nodelist into the
format binkd can read, so you wouldn't have to manually do any of that.

However, this seems like your hub (340/400) isn't able to route netmail properly. I believe we already brought up the idea that he was probably
linked with the former Z1C for netmail routing, if not for echomail as
well. That system he was linked to has been gone for months now. If your uplink can't fix his system, you might be better off getting a new uplink.

Regards,
Nick

... Take my advice, I don't use it anyway.
--- SBBSecho 3.21-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hello Martin!

09 Nov 24 21:32, you wrote to Dan Clough:

Help me to do that! I've done as much reading as I can to get to the point where I'm at. What you don't seem to understand is that I don't have the slightest inclination to get direct netmail working. I want
it routing. That's what's not working at the moment and I think my
feed is the issue. If you'd read my posts, I NEVER stated that I
wanted direct netmail working. I've been trying to get routing working this whole time. If you can't help, go away. Others are at least
trying to help. You're just trying to agitate me.

As most people think: it is not your system's issue but an uplink issue, is it not interesting
to try to contact the uplink and see what is wrong? Or wait until the uplink returns?

As I read (I hope) correctly some netmails were routed correctly some are at a stand-still, is it not worth investing time to see why a crash netmail would not be sent by binkd? To get an alterative way of communicating and get in touch with other uplinks to see if it is indeed another uplinks issue?

for what I know: binkd is using its own system to send crashmail
there are tools like BinkD-compatible nodelist extraction
through the file: binkd_nodelister.php version 1.4.0 which is based on perl binkd_nodelister.pl available
which is able to convert the nodelist to the binkd call list.
that file generated needs to be included in the config of binkd and with that you can send crash mail
and if needed you still can do the routing. I just noticed my system is not configured to update that call list and I converted it. Now I need to create a script to do that daily (or weekly)

I was on hiatus for 24 years, and now 2 months back into Fidonet. I know the lessons to get things running again is sometimes hard and sometimes you have to take a breath, wait, adapt, change and take
alternative ways to get your things going.


When I was starting again I had an issue of a pkt password issue I saw in the log. I could not see what was the issue from my site nor it seems to be an issue as all was working well even some other little things from my side looked wrong. In the end: other people software could also be not correctly configured which affects your site. So my uplink had an issue.

Try to get crashmail working, in the end it will be helping you solving other issues as well.


Dennis


--- GoldED+/LNX 1.1.5-b20240309
* Origin: ---- BOFH: Problem solved, user deleted. (2:280/2060)

Hi Martin,

On 2024-11-09 21:32:00, you wrote to Dan Clough:

Are you trying to say that binkd can't send direct netmail?

Help me to do that!

If you have these settings in your binkd config:

#
# Overrides root domain for DNS lookups, see 'node' below.
#
root-domain binkp.net

#
# Default node flags. Binkd will call an unlisted node if "defnode" is defined. #
defnode -nd *


You don't need to specify every node you want to direct mail. Binkd will use dns lookup on binkp.net, to find out where to connect to.

(Disclaimer: I don't use this myself, so I might have some of the details not right ;-))


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

On 09 Nov 2024, Martin Kazmaier said the following...

Of course I got it. I always receive netmail, it just doesn't go out routed. I wouldn't know how to poll your node to return the message. binkd will only poll nodes I have manually set up in it's config.

Another thing you can try is routing your netmail through Z1C.

Add a new node in FESETUP for 1:229/426. In Routing-F2 route all netmail for 1:* 2:* 3:* 4:* to that new node & remove any wildcard routes in other nodes.

In binkd.conf you'd add:

node 1:229/426@fidonet bbs.darkrealms.ca -

You don't need a password to route netmail


Jay

... You know what they say about cliffhangers...

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Northern Realms (1:229/664)

Hi Martin,

On 2024-11-10 14:55:00, you wrote to me:

If you have these settings in your binkd config:

# # Overrides root domain for DNS lookups, see 'node' below. #
root-domain binkp.net

# # Default node flags. Binkd will call an unlisted node if "defnode"
is defined. # defnode -nd *

You don't need to specify every node you want to direct mail. Binkd will
use dns lookup on binkp.net, to find out where to connect to.

(Disclaimer: I don't use this myself, so I might have some of the details
not right ;-))

Thanks Wilfred! I'll try that if what I'm currently trying (routing through Z1C) doesn't work.

You can do both at the same time! ;-)


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

On 10 Nov 2024, Martin Kazmaier said the following...

I sent you a netmail with this setup. We'll see if it works...
fastecho seemed to do it's think, but binkd didn't.

I got a netmail from you & just replied to it!


Jay

... Why did the stadium get hot after the game? Because all of the fans left

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Northern Realms (1:229/664)

Hi Martin.

10 Nov 24 14:54:00, you wrote to Jay Harris:

I know that fastecho knows the difference. Will binkd?

BTW, Are you using domains in Fastecho? If so, it will use 5D bso outbound.

Also, Fastecho may by default put netmail to arcmail bundles. Every system may not process arc'd mail from insecure inbound.

'Tommi

---
* Origin: Point One (2:221/1.1)

On 11 Nov 2024, Martin Kazmaier said the following...

Ok, things seem to at least be working between the two of us...

I received your reply to my reply.

I can see the path from you is 340/1101 -> 229/426 -> 229/664.


Jay

... I'm reading a book about anti-gravity. It's impossible to put down!

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Northern Realms (1:229/664)

Hi Martin.

11 Nov 24 00:53, you wrote to me:

Also, Fastecho may by default put netmail to arcmail bundles. Every system TK>> may not process arc'd mail from insecure inbound.

Would this be effected by "fastecho pack"? I use "fastecho pack -P" otherwise it doesn't even try to send teh messages.

That is exactly the command to export netmail to binkley-style-outbound. :)

Arcmail status is set to none. PKZIP is the archiver though, if it does archive it.

Does that all sound right?

Yes. :)

'Tommi

--- GoldED+/LNX 1.1.5-b20240309
* Origin: =-=---------------------------=-= (2:221/1)

MK>I sent you a netmail routing through Z1C. We'll see if it works!

Received and responded. Glad it's working now!

Regards,
Jason

--- FMMS - OpenVMS AXP 8.4-2L1
* Origin: Shady Labs (1:218/910)

Hello, Martin Kazmaier.
On 11/11/2024 10.44 you wrote:

Does that all sound right?

Yes. :)

Yay! Jay Harris and August Abolins both received zone 1 netmails from me. Zone 2 and points still aren't working.

Then you need a direct link to zone2. Feel free to send all zone2 mail via 2:221/0. ;)

---
* Origin: jamnntpd/lnx (2:221/1.0)

On Monday November 11 2024, Martin Kazmaier said the following...

Yay! Jay Harris and August Abolins both received zone 1 netmails from
me. Zone 2 and points still aren't working.

I just routed a ping through 1:229/426 to 2:221/1 and it worked.

You should be able to send netmails addressed to any zone through 229/426 and it'll get routed onward.


Jay

... There is much to be said for failure. It is more interesting than success --- GoldED+/LNX 1.1.5-b20240309
* Origin: Northern Realms (1:229/664)

Awesome; Aug got my netmails as well on Rusty Mailbox. I still am not sending to points or zone 2 though.

I just got a netmail from you dated early October. I responded.

Mike


* SLMR 2.1a * Is it magic.... or is it SessionManager?
--- SBBSecho 3.20-Linux
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)

Hello Martin!

11 Nov 24 23:07, you wrote to Jay Harris:

I've got:
domain fidonet c:\\ele\\irex\\outbound 32767

That is wrong... Your in zone 1, so put a 1 at the end and not that 32767 number.

address 1:340/1101@fidonet
node 1:229/426@fidonet bbs.darkrealms.ca - i
node 2:221/0@fidonet f0.n221.z2.rbb.fidonet.fi - i

fastecho has routing for 1:229/426 as 1:*, 2:*, 3:* and 4:*. Do I
need anything else?

That is fine to send *all* netmail to 1:229/426.

If you want to send direct to other nodes you need to adjust the routing.




Stephen


--- GoldED+/LNX 1.1.5-b20240302
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)

Hi Martin.

11 Nov 24 14:27:00, you wrote to me:

Then you need a direct link to zone2. Feel free to send all zone2
mail via
2:221/0. ;)

Ok, added: f0.n221.z2.rbb.fidonet.fi to 2:221/0@fidonet in binkd. I
think that's all I need. Outbound is set to "c:\ele\irex\outbound 1"
for fidonet zone 1. I don't have a zone 2 address, so I don't know
what else to do for that. It was suggested that I put 32767 instead
of 1 to account for other zones, so I changed that just now. We'll
see.

Then you need to add a node 2:221/0 to your fastecho setup so that it routes all 2:* via 2:221/0.

From the command line "fastecho pack -p 2:* via 2:221/0" would also work.

'Tommi

---
* Origin: - rbb.fidonet.fi - Finland - (2:221/360)

On 17.11.2024 15.41, Martin Kazmaier wrote:

Then you need to add a node 2:221/0 to your fastecho setup so that it
routes all 2:* via 2:221/0.

From the command line "fastecho pack -p 2:* via 2:221/0" would also work.

I've got zone 2 working with realms now, but thanks!

But it's good to have multiple ways to send netmail. Always try to send first crash, if failed, then via hub/host of the destination. The last option is to send via your own hub/host. ;)

'Tommi

---
* Origin: smapinntpd/lnx (2:221/1.0)

Hello Tommi!

I've got zone 2 working with realms now, but thanks!

But it's good to have multiple ways to send netmail. Always try to send first crash, if failed, then via hub/host of the destination. The last option is to send via your own hub/host. ;)

But his netmail replies my point do not arrive.

--
../|ug

--- OpenXP 5.0.58
* Origin: The ONLY point that matters --> . <-- (1:153/757.21)

I've got a zone 2 hub now, so I'm sending via that. 2:221/0 I think. I still need one for zone 4, and maybe zone 3 (though I've never sent to that one).

1:229/426 will have links with all z1 regions as well as z2, z3 and z4, so you could route everything there.

--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Martin!

25 Nov 24 15:44, you wrote to Tommi Koivula:

I still need one for zone 4, and maybe zone 3 (though I've never sent
to that one).

@PATH: 340/1101 400 128/187 229/426 633/280

Do you have a link to 1:229/426 (The path above says you do)? I thought there was a post from you a while
ago saying you did?

If you do, then Nick (Z1C) is linked to Scott (Z3C) and the nets of z3 are already linked to each other.




Stephen


--- GoldED+/LNX 1.1.5-b20240302
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)

Hi Martin.

25 Nov 24 15:44, you wrote to me:

From the command line "fastecho pack -p 2:* via 2:221/0" would also

work.

I've got zone 2 working with realms now, but thanks!

But it's good to have multiple ways to send netmail. Always try to send TK>> first crash, if failed, then via hub/host of the destination. The last TK>> option is to send via your own hub/host. ;)

I've got a zone 2 hub now, so I'm sending via that. 2:221/0 I think. I still need one for zone 4, and maybe zone 3 (though I've never sent to that one).

I see a few netmail bundles coming from your node. :)

'Tommi

--- GoldED+/LNX 1.1.5-b20240309
* Origin: =-=---------------------------=-= (2:221/1)

Hello Martin!

26 Nov 24 16:06, you wrote to me:

Do you have a link to 1:229/426 (The path above says you do)? I
thought there was a post from you a while ago saying you did?

If you do, then Nick (Z1C) is linked to Scott (Z3C) and the nets of
z3 are already linked to each other.

Yeah, but as I keep saying, fastecho isn't routing properly. It only routes to the first zone in the list.

Not having used fastecho, but would this work?:

1:229/426 1:* 2:* 3:* 4:*



Stephen


--- GoldED+/LNX 1.1.5-b20240302
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)

1:229/426 will have links with all z1 regions as well as z2, z3 and z4, so >> you could route everything there.

I've tried, but just like another user has reported, I'm getting outbound.002, outbound.004 created and the outbound directory is only for zone 1, so they aren't going out unless I have them routed. For some reason, fastecho isn't routing properly.

That is normal. When you poll a node or if they poll you binkd will create directories in the outbound based on the zones and AKA's those nodes present.

There is a keywork you can add or uncomment and binkd will delete unused directories, but I wouldn't worry to much about it.

Binkd itself doesn't do any routing, it delivers mail or files directly to nodes based on the contents of the flow files in the outbound.

It is your tosser that decides if mail will be sent directly or routed according to your routing rules by placing mail in a directory for that node along with a flow file.

--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Martin!

26 Nov 24 21:35, you wrote to me:

1:229/426 1:* 2:* 3:* 4:*

In routing for 1:229/426. I've got a separate hub for 2:* so I'm not attempting to route that any more. It wasn't working.
Here is most of my 1:229/426 node.
---start paste---
Addresses
Main: 1:229/426 É Route NetMail to ÍÍÍÍÍÍÍ»
ARCmail: 1:229/426 º 1:* º
º 3:* º
Name: darkrealmsº 4:* º
º º

Perhaps it needs to be?:

1:*/*
3:*/*
4:*/*

have seen that in the past, as well as the first one I gave as a example.




Stephen


--- GoldED+/LNX 1.1.5-b20240302
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)

Hello Martin!

29 Nov 24 14:41, you wrote to me:

I checked the help in fastecho and it also defaulted 1:*/* to 1:* as
well as the help suggesting that. It's just not working past the
first line in a node for routing. I don't know if it's a bug or my particular setup.

With all the issues you've been having, perhaps it's time to look at another mail processor.




Stephen


--- GoldED+/LNX 1.1.5-b20240302
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)

Stephen Walsh wrote to Martin Kazmaier <=-

I checked the help in fastecho and it also defaulted 1:*/* to 1:* as
well as the help suggesting that. It's just not working past the
first line in a node for routing. I don't know if it's a bug or my particular setup.

With all the issues you've been having, perhaps it's time to look at another mail processor.

Ding! Ding! Ding!

We have a winner!!!



... Gone crazy, be back later, please leave message.
=== MultiMail/Linux v0.52
--- SBBSecho 3.23-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)