@TID: Mystic BBS 1.12 A45
@MSGID: 21:2/131 0987e81c
@TZUTC: -0600
testing
----
Thanks!
Orbitman (Allen)
Orbit BBS, Opp, AL USA
orbitbbs.ddns.net:7210
--- Mystic BBS v1.12 A45 2020/02/18 (Linux/32)
# Origin: Orbit BBS-Opp, AL. USA | orbitbbs.ddns.net:7210 (21:2/131)
* Origin: Ham Inter-network Echomail Gateway. (432:1/100.0)
SEEN-BY: 1/100 101 102 103 105 106 107 108 109 110 111 113 114 115 116
117 118
SEEN-BY: 1/119 120 121 122 123 124 125 126 127 128 129 130 132 133 134
135 136
SEEN-BY: 1/137 138 139 140 141 142 143 144 145 146 147 148 149 151 154
155 156
SEEN-BY: 1/157 159 160 161
@PATH: 1/100 160
On 01-23-22 06:19, Orbitman wrote to All <=-
testing
----
Thanks!
Orbitman (Allen)
Orbit BBS, Opp, AL USA
orbitbbs.ddns.net:7210
--- Mystic BBS v1.12 A45 2020/02/18 (Linux/32)
# Origin: Orbit BBS-Opp, AL. USA | orbitbbs.ddns.net:7210 (21:2/131)
* Origin: Ham Inter-network Echomail Gateway. (432:1/100.0)
--- Mystic BBS v1.12 A45 2020/02/18 (Linux/32)
Hello Orbitman!
25 Jan 22 12:03, you wrote to Vk3jed:
--- Mystic BBS v1.12 A45 2020/02/18 (Linux/32)
First thing I would do is to upgrade, as that version of mystic is seriously out of date.
On 01-25-22 12:03, Orbitman wrote to Vk3jed <=-
Thanks guys.
I posted that because this message base keeps showing a new message in
the index reader...but when I select it while inside the index reader,
it won't let me in to read the message.
Just before posting this message, I backed out of index reader and it's still showing a new message and once again, I'm not able to get in
through the index reader. Any idea what may be up with that?
still showing a new message and once again, I'm not able to get in
through the index reader. Any idea what may be up with that?
--- Mystic BBS v1.12 A45 2020/02/18 (Linux/32)I suggest you Update to the latest before trying to fix in a now outdated version, I had a stuck NEW message showing the same situation you describe - I just deleted the message and all was well.
That STUCK new message happened to a few other SysOps using Mystic
--- Mystic BBS v1.12 A45 2020/02/18 (Linux/32)I suggest you Update to the latest before trying to fix in a now outdated version, I had a stuck NEW message showing the same situation you
describe - I just deleted the message and all was well.
I updated to A47 a few weeks ago and not had the problem.
Hope this info is of help.:)
Sysop: | Immortal |
---|---|
Location: | Spanish Fork, UT |
Users: | 16 |
Nodes: | 10 (0 / 10) |
Uptime: | 17:17:40 |
Calls: | 560 |
Files: | 3,435 |
Messages: | 103,364 |