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..

Regards,
Flavio

.... What was the best thing before sliced bread?

On Friday April 12 2024, Flavio Bessa said the following...

FB> How do I enable crash netmail sending from my system? I am able to
FB> receive crash netmails well, but when I send a reply they go through
FB> the routed option always..

In mystic -cfg go to to:

Configuration
Message Base Settings

Set Netmail Direct & Netmail Crash to Yes

Crash will have it sent right away & Direct won't route it through your uplink.

Jay

.... Try milking a kangaroo, you'll get a kick out of it

On 12 Apr 2024 at 01:07p, Flavio Bessa pondered and said...
FB> Hello,
FB>
FB> How do I enable crash netmail sending from my system? I am able to
FB> receive crash netmails well, but when I send a reply they go through the
FB> routed option always..

well crash and routed are two separate things... crashing means sending
something off as soon as it can be done, but it may still be routed via another
system depending on how you have your echomail nodes set up and some inbuilt
Mystic routing logic.

Can you give me an example of what's happening now and what you would like to
happen?

Best, Paul

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going'
avon[at]bbs.nz | bbs.nz | fsxnet.nz

FB> Hello,

FB> How do I enable crash netmail sending from my system? I am able to receive
FB> crash netmails well, but when I send a reply they go through the routed
FB> 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.

--- shsbbs.net
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').

*** THE READER V4.50 [freeware]

Re: Crash Netmail
By: Martin Kazmaier to Flavio Bessa on Fri Apr 12 2024 03:00 pm

> 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.
--
digital man (rob)

Synchronet "Real Fact" #20:
Michael Swindell was directly responsible for Synchronet's commercial success
Norco, CA WX: 53.7�F, 83.0% humidity, 1 mph NW wind, 0.00 inches rain/24hrs

On 13 Apr 2024, Paul Hayton said the following...
PH> Can you give me an example of what's happening now and what you would
PH> 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....

On 22 Apr 2024 at 01:26a, Flavio Bessa pondered and said...
FB> On 13 Apr 2024, Paul Hayton said the following...
FB>
FB> PH> Can you give me an example of what's happening now and what you would
FB> PH> like to happen?
FB>
FB> All right, my node is 4:801/188 and I connect to the hub at 4:80/1.

OK

FB> 4:80/1 has a direct link to 2:292/854. Route Info at Hub states that
FB> all netmail towards 2:* should go through there.

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?

FB> 4:801/188 has the Crash Netmail flag on at the Configuration part.

Understood, so this just means any netmail you send is sent quickly off to it's
next hop.

FB> If I send a message to Bjorn Felten, 2:203/0, despite my nodelist is
FB> updated inside Mystic, netmail is routed through 4:80/1 -> 2:292/854 ->
FB> 2:203/0 instead of going directly to 2:203/0....

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.

If you are wanting to send netmail direct to Bjorn at 2:203/0 then I'd suggest
establish a direct link with him and add his system as an echomail node to your
BBS.

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?

Best, Paul

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going'
avon[at]bbs.nz | bbs.nz | fsxnet.nz

-=> Flavio Bessa wrote to Paul Hayton <=-

PH> Can you give me an example of what's happening now and what you would
PH> like to happen?

FB> All right, my node is 4:801/188 and I connect to the hub at
FB> 4:80/1.

FB> 4:80/1 has a direct link to 2:292/854. Route Info at Hub
FB> states that all netmail towards 2:* should go through there.

FB> 4:801/188 has the Crash Netmail flag on at the Configuration
FB> part.

FB> If I send a message to Bjorn Felten, 2:203/0, despite my
FB> nodelist is updated inside Mystic, netmail is routed through
FB> 4:80/1 -> 2:292/854 -> 2:203/0 instead of going directly to
FB> 2:203/0....

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

On 22 Apr 2024, Paul Hayton said the following...
PH> So confirming Route Info for the echomail node 2:292/854 defined at
PH> 4:80/1 has 2:* ?? Just checking I understand this.

Correct.

PH> Also does 4:80/1 have any other echomail nodes with Zone 2 systems that
PH> are defined and active or is 2:292/854 the only one?

Is the only one.

PH>
PH> Understood, so this just means any netmail you send is sent quickly off
PH> to it's next hop.

Correct.

PH>
PH> this sounds correct.
PH>
PH> I am assuming your system routes all netmail to your HUB 4:80/1 ?

Yes, it does.

PH> Do you have any other echomail nodes setup with systems in Fidonet on
PH> your BBS?

No, just the HUB does.

PH> Based on the rule 2:* you have stated at 4:80/1 then Mystic would look
PH> to that to route all Zone 2 netmail via 2:292/854 ...so that behavior
PH> is also expected at the HUB system.

PH> Mystic will check to see if you have a direct connection with a system
PH> you are sending netmail to and if it find that, it will route the
PH> netmail directly to that echomail node and not look at the Route Info
PH> line you may (I am assuming here) have set up for your HUB system ...
PH> presume something like a Route Info statement like 1:* 2:* 3:* 4:* or
PH> 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...

-=> Flavio Bessa wrote to Paul Hayton <=-

FB> But that is the point... If I have the CRASH flag enabled for
FB> Netmail, Mystic should (according to the FTSC specs) read the
FB> nodelist, find out the Binkp address for Bjorn's system, and
FB> issue an unsecured session towards 2:203/0. That is what the
FB> other mailers do, and that is why we have nodelists in the first
FB> place...

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.

.... So easy, a child could do it. Child sold separately.
=== MultiMail/Linux v0.52

On 22 Apr 2024 at 12:07p, Flavio Bessa pondered and said...
FB> PH> Based on the rule 2:* you have stated at 4:80/1 then Mystic would loo
FB> PH> to that to route all Zone 2 netmail via 2:292/854 ...so that behavio
FB> PH> is also expected at the HUB system.
FB>
FB> PH> Mystic will check to see if you have a direct connection with a syste
FB> PH> you are sending netmail to and if it find that, it will route the
FB> PH> netmail directly to that echomail node and not look at the Route Info
FB> PH> line you may (I am assuming here) have set up for your HUB system ...
FB> PH> presume something like a Route Info statement like 1:* 2:* 3:* 4:*
FB> PH> similar?
FB>
FB> But that is the point... If I have the CRASH flag enabled for
FB> Netmail, Mystic should (according to the FTSC specs) read the nodelist,
FB> find out the Binkp address for Bjorn's system, and issue an unsecured
FB> session towards 2:203/0. That is what the other mailers do, and that is
FB> 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.

It does not impact on how Mystic deals with netmail (g00r00 may care to jump in
when next active to confirm or update these thoughts ;))

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.

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going'
avon[at]bbs.nz | bbs.nz | fsxnet.nz

On 23 Apr 2024, Paul Hayton said the following...
PH> No. The CRASH flag won't in itself be enough for Mystic to do what you
PH> hope it will do. Also note that just because you may have run the
PH> MergeNodelists function in MUTIL this will only scan the nodelists you
PH> point to and build a text file in the data directory of Mystic. This is
PH> in turn used by the nodelist browser feature, but that feature is like
PH> looking up a phone book for a number, nothing more.

Yeah, that was what I was suspecting. I even tried to do a mis poll towards
Bjorn's system, but it did not deliver the netmail since it was routed towards
4:80/1 by default.

PH> Mystic has it's own logic as to how it will route netmail. Refer to
PH> whatsnew.txt to see what this is. g00r00 has documented it there. Look
PH> for 'netmail routing' in that document and read this to understand the
PH> steps Mystic takes.

Yeah, I did go through the docs and the process is pretty smart actually.

However there is no provision for the crash logic.

PH> If you are unhappy with the way Mystic acts, then it's best to post some
PH> feedback to this echo and suggest what you think it could do
PH> differently/better etc. and why... and then you will need to wait for
PH> the software author to reply.

Thanks! Will do that.

.... Just another prisoner of gravity!