How do I enable crash netmail sending from my system? I am able to
receive crash netmails well, but when I send a reply they go through
the routed option always..
Hello,
How do I enable crash netmail sending from my system? I am able to
receive crash netmails well, but when I send a reply they go through the routed option always..
Hello,
How do I enable crash netmail sending from my system? I am able to receive crash netmails well, but when I send a reply they go through the routed option always..
I could be wrong, but I think you mean direct, not crash. Crash just sends immediately instead of waiting for a scheduled poll. Direct means it's not routed. And this isn't very helpful because I'm not a mystic sysop, so I don't know the answer :P.
Crash means direct (not routed) *and* immediate.
Crash means direct (not routed) *and* immediate.
Crash means direct (not routed) *and* immediate.
deon wrote to All <=-
Re: Crash Netmail
By: Rob Swindell to Martin Kazmaier on Fri Apr 12 2024 11:35 pm
Crash means direct (not routed) *and* immediate.
What's the difference between "Crash" and "immediate"?
Crash means direct (not routed) *and* immediate.
What's the difference between "Crash" and "immediate"?
... There are two types of people; those who finish what they start and
Re: Crash Netmail
By: Rob Swindell to Martin Kazmaier on Fri Apr 12 2024 11:35 pm
Howdy,
Crash means direct (not routed) *and* immediate.
What's the difference between "Crash" and "immediate"?
Jon Robertson wrote to Dan Clough <=-
Re: Re: Crash Netmail
By: Dan Clough to deon on Sun Apr 14 2024 08:46 am
... There are two types of people; those who finish what they start and
Sychronet has a "upvote message" and I really wanted to upvote
just for that tagline. Unfortunately I
BinkIT (Synchronet's FTN/BinkP mailer) treats .d (Direct), .i, and .c flow files all the same, FWIW.
Can you give me an example of what's happening now and what you would
like to happen?
On 13 Apr 2024, Paul Hayton said the following...
Can you give me an example of what's happening now and what you would like to happen?
All right, my node is 4:801/188 and I connect to the hub at 4:80/1.
4:80/1 has a direct link to 2:292/854. Route Info at Hub states that all netmail towards 2:* should go through there.
4:801/188 has the Crash Netmail flag on at the Configuration part.
If I send a message to Bjorn Felten, 2:203/0, despite my nodelist is updated inside Mystic, netmail is routed through 4:80/1 -> 2:292/854 -> 2:203/0 instead of going directly to 2:203/0....
Flavio Bessa wrote to Paul Hayton <=-
Can you give me an example of what's happening now and what you would
like to happen?
All right, my node is 4:801/188 and I connect to the hub at
4:80/1.
4:80/1 has a direct link to 2:292/854. Route Info at Hub
states that all netmail towards 2:* should go through there.
4:801/188 has the Crash Netmail flag on at the Configuration
part.
If I send a message to Bjorn Felten, 2:203/0, despite my
nodelist is updated inside Mystic, netmail is routed through
4:80/1 -> 2:292/854 -> 2:203/0 instead of going directly to
2:203/0....
Flavio Bessa wrote to Paul Hayton <=-
But that is the point... If I have the CRASH flag enabled for
Netmail, Mystic should (according to the FTSC specs) read the
nodelist, find out the Binkp address for Bjorn's system, and
issue an unsecured session towards 2:203/0. That is what the
other mailers do, and that is why we have nodelists in the first
place...
I don't know how to set it in Mystic, but having the Crash flag set is not enough. You also need to set a DIRECT flag. A message can have a "Crash" status but that does not mean it will go directly to the recipient unless it is ALSO set to DIRECT.
... 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)
So confirming Route Info for the echomail node 2:292/854 defined at
4:80/1 has 2:* ?? Just checking I understand this.
Also does 4:80/1 have any other echomail nodes with Zone 2 systems that are defined and active or is 2:292/854 the only one?
Understood, so this just means any netmail you send is sent quickly off
to it's next hop.
this sounds correct.
I am assuming your system routes all netmail to your HUB 4:80/1 ?
Do you have any other echomail nodes setup with systems in Fidonet on
your BBS?
Based on the rule 2:* you have stated at 4:80/1 then Mystic would look
to that to route all Zone 2 netmail via 2:292/854 ...so that behavior
is also expected at the HUB system.
Mystic will check to see if you have a direct connection with a system
you are sending netmail to and if it find that, it will route the
netmail directly to that echomail node and not look at the Route Info
line you may (I am assuming here) have set up for your HUB system ... presume something like a Route Info statement like 1:* 2:* 3:* 4:* or similar?
Nope. The CRASH flag is not the same as, nor does it specify, the
DIRECT flag. You need to have both set for the behavior you desire.
Well, I tried both, but the netmail keeps getting routed through 4:80/1. I am starting to think that this is the expected behavior from Mystic.
Based on the rule 2:* you have stated at 4:80/1 then Mystic would loo to that to route all Zone 2 netmail via 2:292/854 ...so that behavio is also expected at the HUB system.
Mystic will check to see if you have a direct connection with a syste you are sending netmail to and if it find that, it will route the netmail directly to that echomail node and not look at the Route Info line you may (I am assuming here) have set up for your HUB system ... presume something like a Route Info statement like 1:* 2:* 3:* 4:* similar?
But that is the point... If I have the CRASH flag enabled for
Netmail, Mystic should (according to the FTSC specs) read the nodelist, find out the Binkp address for Bjorn's system, and issue an unsecured session towards 2:203/0. That is what the other mailers do, and that is why we have nodelists in the first place...
No. The CRASH flag won't in itself be enough for Mystic to do what you hope it will do. Also note that just because you may have run the MergeNodelists function in MUTIL this will only scan the nodelists you point to and build a text file in the data directory of Mystic. This is
in turn used by the nodelist browser feature, but that feature is like looking up a phone book for a number, nothing more.
Mystic has it's own logic as to how it will route netmail. Refer to whatsnew.txt to see what this is. g00r00 has documented it there. Look
for 'netmail routing' in that document and read this to understand the steps Mystic takes.
If you are unhappy with the way Mystic acts, then it's best to post some feedback to this echo and suggest what you think it could do differently/better etc. and why... and then you will need to wait for
the software author to reply.
Based on the rule 2:* you have stated at 4:80/1 then Mystic would
loo to that to route all Zone 2 netmail via 2:292/854 ...so that
behavio is also expected at the HUB system.
Mystic will check to see if you have a direct connection with a
syste you are sending netmail to and if it find that, it will route
the netmail directly to that echomail node and not look at the Route
Info line you may (I am assuming here) have set up for your HUB
system ... presume something like a Route Info statement like 1:*
2:* 3:* 4:* similar?
But that is the point... If I have the CRASH flag enabled for Netmail,
Mystic should (according to the FTSC specs) read the nodelist, find out
the Binkp address for Bjorn's system, and issue an unsecured session
towards 2:203/0. That is what the other mailers do, and that is why we
have nodelists in the first place...
I wish that whomever has the mystic support group tied into Dovenet-General would knock it off already..
I wish that whomever has the mystic support group tied into Dovenet-General would knock it off already..
I wish that whomever has the mystic support group tied into Dovenet-General would knock it off already..
Re: Re: Crash Netmail
By: kk4qbn to Paul Hayton on Wed Apr 24 2024 01:56 pm
I wish that whomever has the mystic support group tied into Dovenet-General would knock it off already..
Is there any way to find out the source if this issue?
Is there any way to find out the source if this issue?
Yes, they all came from "RETRO" a Mystic system.
Re: Re: Crash Netmail
By: Digital Man to Neoshock on Thu Apr 25 2024 11:20:24
Is there any way to find out the source if this issue?
Yes, they all came from "RETRO" a Mystic system.
It was just a matter of timing before it would start. <grin>
Sysop: | Immortal |
---|---|
Location: | Spanish Fork, UT |
Users: | 16 |
Nodes: | 10 (0 / 10) |
Uptime: | 20:35:17 |
Calls: | 560 |
Files: | 3,435 |
Messages: | 103,383 |