On 19 Jan 2022 at 10:38a, Jonathan Martin pondered and said...
JM> g0> I'll hold off a little to see if he sees this and is able to provide
JM> g0> some more detail as its his network. If he doesn't see this I'll do
JM> g0> what I can to help you get sorted out.
JM> I think I'm good now actually. I figured out how to get NetMail to work,
JM> sent some rescan commands, and was able to get old messages.
JM> It's crazy how intuitive this stuff was in the 80s and 90s, and now I'm
JM> like "duh what?"
:)
If you are using the test AKA 21:1/999 then you will be (for want of a better
term) competing with others also testing using the same AKA. This leads to some
folks posting echomail into the fsxNet echos but then wondering why their
replies are few/far between. It's usually because someone else testing with
/999 has beaten them to mail packets with their replies..
So yep, grab a full node number and then at least all message and/or files
traffic you want will be sitting at a HUB waiting for you to poll and
collect it. The other thing to be aware of is that some echomail areas in
fsxNet are not linked to the test /999 AKA (this is by design) if you want
those you should consider getting a full node number. :)
If you're following the older videos, sending a netmail to 'Areafix' at
21:1/100 using the password mentioned, is the way to go if you want to send a
%rescan command to get older messages.
Hope that helps.
Best, Paul aka Avon
--- Mystic BBS v1.12 A47 2021/11/06 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
|
