Subj : ping as crash reply
To   : Jay Harris
From : Dennis Slagers
Date : Sat Nov 16 2024 11:43:42


Hello Jay!

15 Nov 24 12:08, you wrote to me:

Just added the features you described.

Now ping.pl supports PING/TRACE with routed mail reply
but when send to PINGC as a node you will receive a direct/imm reply back, however if you do this as a point than it is HUB delivered and/or routed ..

People can test to my system. I am open for business <grin>

Thanks Jay!

Dennis

 JH> You could do something like:

 JH> # If $fromaddr is not a point
 JH> if ( $fromaddr !~ /\./ || $fromaddr =~ /\.0$/ ) {
 JH>     $direct = "\x01FLAGS DIR IMM\r";
 JH> }

 JH> # Prepend kludge lines
 JH> $msgtext = "\x01MSGID: $myaddr $mid\r\x01TZUTC:
 JH> $tz\r".$direct.$msgtext;

 JH> This should only add the FLAGS kludge if you get a message from node
 JH> (e.g. 1:229/664 or 1:229/664.0).  If it's a point address the kludge
 JH> is not added and should be sent routed.


 JH> You could also try adding:

 JH> else {
 JH>     $direct = "\x01FLAGS HUB\r";
 JH> }

 JH> To the bottom of the above if statement and the message *should* be
 JH> routed through the host or hub.  I've never tried/used this flag so
 JH> I'm not sure how well (or if) it works.


 JH> http://ftsc.org/docs/fsc-0053.002

 JH> HUB:
 JH> Host- or Hub-route message (as appropriate).

 JH> DIR:
 JH> Message must be sent directly to its destination and may not be
 JH> routed.

 JH> IMM:
 JH> NOW!-priority mail. Send at first opportunity, override any
 JH> transmission restrictions enforced by events, costs, or qualification.


 JH> Jay

 JH> ... I stayed up all night to see where the sun went. Then it dawned on
 JH> me

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

Dennis


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

.