REPLY: 1:229/664 10724e0c
MSGID: 2:221/1.1 5ff88e3f
CHRS: UTF-8 4
TZUTC: 0200
TID: hpt/w32-mvc 1.9.0-cur 2020-10-16
* Originally in wat.netmail
* Crossposted in points

* Replying to a msg in points (points)

Hi Jay.

08 Jan 21 11:11:22, you wrote to August Abolins:

 JH> On 08 Jan 2021, August Abolins said the following...

 AA>> MEANWHILE, I send a netmail routed.
 AA>>
 AA>> And, I just delivered another crash netmail but this time I used
 AA>> a zone that we have in common, "21:"
 AA>>
 AA>> My logs don't record your Z:N/F number.  :(   But the packet
 AA>> number might help you look for it if you have to:

 JH> Weird, Mystic is still trying to toss it as echomail:

 JH> + Jan 08 11:08:09    Importing 08091311.PKT (2:221/1.58 to 21:3/110)
 JH> ! Jan 08 11:08:09    No echomail node configured for 2:221/1.58
 JH> ! Jan 08 11:08:09    Moving /home/pi/mystic/echomail/in/uns
cure/08091311.PKT to
 JH> /home/pi/mystic/echomail/bad/08091311.PKT

 JH> I had a look at the packet and I do see an INTL kludge in there, which I
believe only netmail has.
 JH> (Correct me if I'm wrong) - So I'm not sure what the issue is here.

 JH> At any rate, if I get you setup as a point, my system will then at least
know
 JH> who you are... lol

This is a crashmail test reply from a point of GoldED/HPT/Binkd.

 JH> Jay

 JH> --- Mystic BBS v1.12 A47 2021/01/05 (Raspberry Pi/32)
 JH>  * Origin: Northern Realms (1:229/664)

'Tommi


---
 * Origin: IPv6 Point at [2001:470:1f15:cb0:2:221:1:1] (2:221/1.1)
SEEN-BY: 1/123 90/1 105/81 120/340 123/131 124/5016 154/10 203/0 221/1
SEEN-BY: 221/6 360 226/30 227/114 702 229/101 424 426 664 1016 1017
SEEN-BY: 240/2100 5138 5411 5824 5832 5853 249/206 317 400 280/464
SEEN-BY: 280/5003 288/100 292/854 8125 310/31 317/3 320/219 322/757
SEEN-BY: 342/200 396/45 423/81 120 712/848 770/1 2432/390 2452/250
SEEN-BY: 2454/119
PATH: 221/1 280/464 240/5832 229/426