Yay! Jay Harris and August Abolins both received zone 1 netmails from me. Zone 2 and points still aren't working.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.
Awesome; Aug got my netmails as well on Rusty Mailbox. I still am not sending to points or zone 2 though.
Hotdoged/1727691443000 HotdogEd/2.13.5. Hello, Martin Kazmaier. On 11/11/2024 10.44 you wrote:
from me.Yay! Jay Harris and August Abolins both received zone 1 netmailsDoes that all sound right?Yes. :)
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. ;)
On Monday November 11 2024, Martin Kazmaier said the following...
Yay! Jay Harris and August Abolins both received zone 1 netmailsfrom
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.
I've got:
domain fidonet c:\\ele\\irex\\outbound 32767
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?
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)
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.
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.
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!
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. ;)
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.
work.From the command line "fastecho pack -p 2:* via 2:221/0" would also
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. ;)
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 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
work.From the command line "fastecho pack -p 2:* via 2:221/0" would also
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've got a zone 2 hub now, so I'm sending via that. 2:221/0 I think. Istill
need one for zone 4, and maybe zone 3 (though I've never sent to thatone).
1:229/426 will have links with all z1 regions as well as z2, z3 and z4, so you could route everything there.
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.
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.
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.
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:*
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:* �
� �
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.
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.
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.
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.
Sysop: | Angel Ripoll |
---|---|
Location: | Madrid, Spain |
Users: | 15 |
Nodes: | 8 (0 / 8) |
Uptime: | 38:33:19 |
Calls: | 900 |
Calls today: | 1 |
Files: | 15,311 |
D/L today: |
5 files (10K bytes) |
Messages: | 70,374 |