It's been a while and I am fuzzy on what the final agreed issues were for
this. As I am not an active QWK user it makes it hard to recall, that and I
am tired as I write this and have not been able to find a concise post in
this echo quickly to sum it up.

Can someone please just summarize what we think the issue is again and I will make sure I'll pass it back to g00r00 when I next have some contact with him. I'm not clear if the current A32 we're testing addresses the previously discussed issue. But you will see in the notes there are aspects around

[snip]

Fixed a problem in QWK packets that could cause packet corruption when
processing messages greater than 64kb.

[snip]

that have been purportedly addressed.

Thanks guys. I need some more zzz :)

Best, Paul

--- Mystic BBS v1.12 A32 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 04/22/17, Avon said the following...

It's been a while and I am fuzzy on what the final agreed issues were for this. As I am not an active QWK user it makes it hard to recall, that
and I am tired as I write this and have not been able to find a concise post in this echo quickly to sum it up.

Paul,

It's the issue where if multiple messages are entered into Mystic at the same time, they will all receive the same MSGID. It's the same issue with posting multiple text files to messages at the same time. Some other systems will see the same MSGID and determine they are duplicate messages.

It is a major issue with QWK, as people will upload multiple messages at the same time in their .REP packets.

Evidently Mystic uses a time stamp to assign the MSGID for a message, so
there needs to be a few second delay between message replies.

I think that pretty much sums it up...


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

Paul,

Just an FYI, the issue with the MSGID being the same on messages uploaded at the same time is still there. I ran a test with the new alpha.

It's not a huge problem here, as I don't use an offline mail reader.

Tell g00r00 to keep up the good work! :)


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A32 (Windows)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

On 04/21/17, Black Panther pondered and said...

Paul,

Just an FYI, the issue with the MSGID being the same on messages
uploaded at the same time is still there. I ran a test with the new
alpha.

OK thanks, that's with a QWK upload right?

Best, Paul

--- Mystic BBS v1.12 A32 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 04/22/17, Avon said the following...

Just an FYI, the issue with the MSGID being the same on messages uploaded at the same time is still there. I ran a test with the new alpha.

OK thanks, that's with a QWK upload right?

That was with MUTIL posting multiple text files. I'm still working on getting
a QWK reader set up to test that end.


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A32 (Windows)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

On 04/21/17, Black Panther pondered and said...

That was with MUTIL posting multiple text files. I'm still working on getting a QWK reader set up to test that end.

Gotcha, the size of a QWK packet being able to be downloaded seems to be
fixed, bcw142 managed to pull down a 4 gig packet about 2 hours ago from Agency.

Best, Paul

--- Mystic BBS v1.12 A32 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Avon wrote to All <=-

It's been a while and I am fuzzy on what the final agreed issues were
for this. As I am not an active QWK user it makes it hard to recall,
that and I am tired as I write this and have not been able to find a concise post in this echo quickly to sum it up.

[snip]

Fixed a problem in QWK packets that could cause packet corruption when
processing messages greater than 64kb.

[snip]

that have been purportedly addressed.

It's been addressed and works fine:
bcw@lenotv2:/mystic$ du -hc *.qwk
4.3M AGENCY.qwk <- A32 Works fine with mmail v0.49
280K oAGENCY.qwk
1.6M OMPI.qwk <- A31 won't load with mmail v0.49
6.2M total
bcw@lenotv2:/mystic$ mm OMPI.qwk <- Just hangs forever
bcw@lenotv2:/mystic$ mm AGENCY.qwk <- Works fine. Used it do send this
Reply packet!

Not testing the reply packet problem with MSGID as I see nothing that should address that, but the size problem is fixed and it works with an unpatched mmail v.49 under Ubuntu 14.04 LTS 64 Bit. That said I tried in the past under Pi (32 bit) and other setups and they all had the problem, so I suspect they all work now. AGENCY.qwk worked on the Pi (32 bit) & Ubuntu 16.04.2 64 bit
and 32 bit, they all work. That's all I'm going to check for tonight.


... MultiMail, the new multi-platform, multi-format offline reader!
___ MultiMail/Linux v0.49

--- Mystic BBS/QWK v1.12 A32 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 04/22/17, Avon said the following...

Gotcha, the size of a QWK packet being able to be downloaded seems to be fixed, bcw142 managed to pull down a 4 gig packet about 2 hours ago from Agency.

I downloaded a 700 meg packet here, and was able to open it in BlueWave. It took forever though...

I also sent two messages within BW and uploaded the packet. Mystic did give each message it's own MSGID.


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A32 (Windows)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

On 04/22/17, Avon pondered and said...

Gotcha, the size of a QWK packet being able to be downloaded seems to be fixed, bcw142 managed to pull down a 4 gig packet about 2 hours ago from Agency.

Took a look and found it was only 4M, but that is still well over 64K and it worked fine. I'm sure the size issue is solved. I think the rep issue is
still there which is why I uploaded the last one as just one message, but I guess it's also important to test and put an example up here so I'll go do that.

--- Mystic BBS v1.12 A32 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 04/21/17, Black Panther said the following...

Paul,
Just an FYI, the issue with the MSGID being the same on messages
uploaded at the same time is still there. I ran a test with the new
alpha.
It's not a huge problem here, as I don't use an offline mail reader.
Tell g00r00 to keep up the good work! :)

you can send a donation via his website ;)

|08 .|05ú|13ù|15Dr|07e|08am Ma|07st|15er|13ù|05ú|08.
|08 øù|05ú|13ùø |13øù|05ú|08ùø
|11 DoRE|03!|11ACiDiC|03!|11Demonic |08[|15dreamland|09.|15darktech|09.|15org|08]

--- Mystic BBS v1.12 A31 (Windows)
* Origin: |08--[|15!|07dreamland BBS dreamland.darktech.org (21:1/163)

On 04/21/17, dream master said the following...

Tell g00r00 to keep up the good work! :)

you can send a donation via his website ;)

I think I'm gonna have to do that. :)


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A32 (Windows)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

On 04/21/17, Black Panther said the following...

I also sent two messages within BW and uploaded the packet. Mystic did give each message it's own MSGID.

---
Dan Richter
aka Black Panther
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...
--- Mystic BBS v1.12 A32 (Windows)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

Odd, not what I found on Agency BBS, I sent two replies with MultiMail v0.49 and both had @MSGID: 21:1/101 00efc273. That being said it was never
something that happened on all messages - it depends on how fast your system
is receiving the rep packets. If the system is slower or timed just right it will have unique MSGIDs. Do you know what version of MultiMail you used?
I used MultiMail/Linux v0.49 according to the top line of the screen and I
used Type: QWKE personal, Door: Mystic BBS 1.12 A32. All that info comes up with the first screen of the MultiMail being used. In this case it's Ubuntu 14.04 LTS 64bit, but it's really the receiving system that causes the issue
as QWK/QWKE rep packets don't create the MSGID, Mystic has to when it's received. The faster the receiving system, the more likely we get duplicate MSGIDs - or so it seems from all testing done so far. In the past I send 5 or more messages in the rep packet and 4 of the 5 had duplicate MSGIDs when received by my Mystic Pi BBS setup (Pi 2B with Mystic A31).

--- Mystic BBS v1.12 A31 (Linux)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

On 04/22/17, bcw142 said the following...

I also sent two messages within BW and uploaded the packet. Mystic di give each message it's own MSGID.

Odd, not what I found on Agency BBS, I sent two replies with MultiMail v0.49 and both had @MSGID: 21:1/101 00efc273. That being said it was
never something that happened on all messages - it depends on how fast your system is receiving the rep packets. If the system is slower or

That test was actually done with Bluewave 3.20. I didn't have MultiMail installed on here. I have it now, and will run more tests later. The version
of MultiMail is 0.49 for Windows, so we'll see what happens with that one.


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A32 (Windows)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

Hi Avon!

22 Apr 2017 10:18, from Avon -> All:

Can someone please just summarize what we think the issue is again and
I will make sure I'll pass it back to g00r00 when I next have some
contact with him.

MUtil (or whatever the posting utility is called) and QWK generate often the same MSGID.
I think this was a bug that it is ONLY based on the time the REP import is run. This clearly violates standards, as different messages need to have different MSGIDs.

That is a huge bug ... I hope that people will quickly stop using the buggy version.

Good to hear that at least the second mangling will stop as soon as people update.

CU, Ricsi

--- GoldED+/LNX
* Origin: Born to be wiiiillllllddddddddddd (21:1/104)

On 04/22/17, Avon said the following...

Gotcha, the size of a QWK packet being able to be downloaded seems to be fixed, bcw142 managed to pull down a 4 gig packet about 2 hours ago from Agency.

4 GIGS!!! That is a lot of messages.

Immortal

--- Mystic BBS v1.12 A31 (Linux)
* Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)

On 04/23/17, Immortal said the following...

On 04/22/17, Avon said the following...

Gotcha, the size of a QWK packet being able to be downloaded seems to fixed, bcw142 managed to pull down a 4 gig packet about 2 hours ago f Agency.

4 GIGS!!! That is a lot of messages.

Nope was just over 4M really, but still over the 65k limit that had hung MultiMail before g00r00 fixed it. I have downloaded echos that were in the
1-4G range before from Synchonet systems.

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

It is a major issue with QWK, as people will upload multiple messages at the same time in their .REP packets.

I cannot reproduce any of this in any fashion, and its been very thoroughly tested here. I've added some logging into MUTIL but even the tests that are sent to me to show the problem run perfectly fine here.

Evidently Mystic uses a time stamp to assign the MSGID for a message, so there needs to be a few second delay between message replies.

Mystic uses a very complex MSGID generation system, its not supposed to
require any amount of time between assignments.

--- Mystic BBS v1.12 A32 (Windows)
* Origin: flupH | fluph.darktech.org (21:1/105)

Nope was just over 4M really, but still over the 65k limit that had hung MultiMail before g00r00 fixed it. I have downloaded echos that were in
the 1-4G range before from Synchonet systems.

Just for clarification, the problem was when a single message was larger than 64kb not the packet size itself. Glad to hear its working better now! :)

--- Mystic BBS v1.12 A32 (Windows)
* Origin: flupH | fluph.darktech.org (21:1/105)

On 05/06/17, g00r00 said the following...

It is a major issue with QWK, as people will upload multiple messages the same time in their .REP packets.

I cannot reproduce any of this in any fashion, and its been very thoroughly tested here. I've added some logging into MUTIL but even the tests that are sent to me to show the problem run perfectly fine here.

I can honestly say that until A32, I hadn't tested it personally. I have
tested A32 and have not had any problems with the QWK or QWKE packets or the REP packets. They seem to be working fine.

Evidently Mystic uses a time stamp to assign the MSGID for a message, there needs to be a few second delay between message replies.

Mystic uses a very complex MSGID generation system, its not supposed to require any amount of time between assignments.

There is, however, still an issue when posting text messages to message base via MUTIL. Both Paul and I were running tests with A32, and it will still duplicate MSGIDs on the Windows systems. I'm running the 64 bit version,
while Paul is running 32 bit. It seems with 8 text message postings, Paul
would have 4 - 6 duplicates, while I was getting 2 duplicates. Evidently the rPi version didn't have any problems, and I'm hoping that I can text the
32bit Linux version this weekend.


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A32 (Windows)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)