Hi All,

I discovered a bug in Mystic when generating new emails using MUtil. My system is fast enough that MSGIDs are duplicated causing multiple dupes to be generated.

I have a program that repeatably calls MUtil to post text files one at a time, but when there are many to post, the dupes crop up. My work around has been to incur a 2 second pause between posts to force the MsgID to be recalculated. At 2 secs I get sequential IDs but at least they are unique! {sigh}

Hey g00r00, long break, eh???


.- Keep the faith, --------------------------------------------------.
| |
| Ben aka cMech Web: http|ftp|binkp|telnet://cmech.dynip.com |
| Email: fido4cmech(at)lusfiber.net |
| (:) Home page: http://cmech.dynip.com/homepage/ | `----------- WildCat! Board 24/7 +1-337-984-4794 any BAUD 8,N,1 ---'

... Is it just me, or is 9600 not as fast as it used to be?
--- GoldED+/W32-MSVC v1.1.5-b20161221 ... via Mystic BBS!
* Origin: FIDONet - The Positronium Repository (1:393/68)

On 03/15/17, Ben Ritchey pondered and said...

I discovered a bug in Mystic when generating new emails using MUtil. My system is fast enough that MSGIDs are duplicated causing multiple dupes
to be generated.

Thanks Ben.

Yes this was noted among other users and the same work around suggested.

In my case I add a 5 second pause between pauses.

Best, Paul

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)

Ben Ritchey wrote to All <=-

I discovered a bug in Mystic when generating new emails using MUtil. My system is fast enough that MSGIDs are duplicated causing multiple dupes
to be generated.

I have a program that repeatably calls MUtil to post text files one at
a time, but when there are many to post, the dupes crop up. My work
around has been to incur a 2 second pause between posts to force the
MsgID to be recalculated. At 2 secs I get sequential IDs but at least
they are unique! {sigh}

This is a known issue in the Mystic community, and your workaround is what most of us do when auto posting multiple messages from Mystic. Unfortunately, the same issue also affects QWK replies, so multiple replies from .REP packets can also get suplicate MSGIDs. :(


... Real Sysops read the documentation; or at least skim them
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

On 2017 Mar 17 06:54:00, you wrote to Ben Ritchey:

I discovered a bug in Mystic when generating new emails using MUtil.
My system is fast enough that MSGIDs are duplicated causing multiple
dupes to be generated.

I have a program that repeatably calls MUtil to post text files one
at a time, but when there are many to post, the dupes crop up. My
work around has been to incur a 2 second pause between posts to force
the MsgID to be recalculated. At 2 secs I get sequential IDs but at
least they are unique! {sigh}

This is a known issue in the Mystic community, and your workaround is
what most of us do when auto posting multiple messages from Mystic. Unfortunately, the same issue also affects QWK replies, so multiple replies from .REP packets can also get suplicate MSGIDs. :(

what's truely sad is that i pointed this out in the 11 alphas and it was taken care of then... the there was this new stuff, effectively being chased across multiple networks, with no response and now, sadly, the author is completely uncontactable... at least from all reports...

this is like your high school sweetheart is going to go to the prom with you but then you don't hear from her again... at least a "fuck you" from james would be welcome... but this is crap... especially with no response in so long... is this BlueWave all over again? where the author was crippled and then
just fell away from the project?

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... I'd give you a piece of my mind, but I'm on the last one.
---
* Origin: (1:3634/12.73)

Hi Mark,

this is like your high school sweetheart is going to go to the prom with you but then you don't hear from her again... at least a "fuck you" from james would be welcome... but this is crap... especially with no response in so
long... is this BlueWave all over again? where the author was crippled and the
just fell away from the project?

It looks like James need a verry long brake...

Rudi

--- BBBS/LiR v4.10 Toy-3
* Origin: Web: xtreme.dynv6.net:81 (2:292/140)

On 01/04/18, Paul Hayton pondered and said...

@MSGID: 1:340/800.0 c03a1153
@PID: Imp-Mail 2.01
@TID: hpt/dpmi-djgpp 1.9.0-cur 24-06-16
@SEEN-BY: 57/0 116/102 130/512 154/10 226/100 250/3 317/2 3 393/68
712/848
@SEEN-BY: 770/0 1 3 100 340 772/0 1 210 500
@PATH: 340/800 154/10 770/1
On 03/15/17, Ben Ritchey pondered and said...

Something amiss there...

* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)

Best, Paul


`I'm not expendable, I'm not stupid, and I'm not going' - Kerr Avon, Blake's 7

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

@MSGID: 1:340/800.0 c03a1153
@PID: Imp-Mail 2.01
@TID: hpt/dpmi-djgpp 1.9.0-cur 24-06-16

Something amiss there...

Yeah, ancient message from not even the involved systems.

I was like "wait what? I fixed that bug like 2 years ago!" lol

--- Mystic BBS v1.12 A39 2018/01/05 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)

Hello g00r00,

On Fri Jan 05 2018 13:53:00, g00r00 wrote to Paul Hayton:

@MSGID: 1:340/800.0 c03a1153
@PID: Imp-Mail 2.01
@TID: hpt/dpmi-djgpp 1.9.0-cur 24-06-16

Something amiss there...

Yeah, ancient message from not even the involved systems.

I was like "wait what? I fixed that bug like 2 years ago!" lol

Nope. The bug is IMP-MAIL (and a very big one at that), and has happened plenty
of times before. I've let him know about it.

Regards,
Nick

... "?? ????. ? ????? ?????? ???????."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

On 01/05/18, Nicholas Boel pondered and said...

I was like "wait what? I fixed that bug like 2 years ago!" lol

Nope. The bug is IMP-MAIL (and a very big one at that), and has happened plenty of times before. I've let him know about it.

I've seen other posts in other echos along the same lines... hope he can sort it. That original post really threw me too.. I needed to check PATHs to suss what was going on :)

Best, Paul


`I'm not expendable, I'm not stupid, and I'm not going' - Kerr Avon, Blake's 7

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Hello Paul,

On Sat Jan 06 2018 19:16:18, Paul Hayton wrote to Nicholas Boel:

Nope. The bug is IMP-MAIL (and a very big one at that), and has
happened plenty of times before. I've let him know about it.

I've seen other posts in other echos along the same lines... hope he
can sort it. That original post really threw me too.. I needed to
check PATHs to suss what was going on :)

I've let him know that using alpha code as a production system is not a good idea for Fidonet, and that it should be more thoroughly tested before throwing it out to the wolves.

Regards,
Nick

... "?? ????. ? ????? ?????? ???????."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)