Hello g00r00!

I though I would purge and then rescan a bunch of message areas from my uplinks to "repair" the damaged messages resulting from the previous (now fixed) addition of newlines by the mutil PackMessageBases function.

However, this turned out to be a bad idea (kind of), as all messages written by myself (exported from my node to my uplink) will get caught by the circular path reference checking performed by mutil ImportEchoMail when the rescanned messages arrive.

Is there some way to work around this in order to really get all messages imported?

Thanks in advance! =)

Best regards
Björn

--- Mystic BBS v1.12 A47 2021/12/10 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

However, this turned out to be a bad idea (kind of), as all messages written by myself (exported from my node to my uplink) will get caught
by the circular path reference checking performed by mutil
ImportEchoMail when the rescanned messages arrive.

Is there some way to work around this in order to really get all messages imported?

Hmmm this is a tough one. I am not sure there really is a way around that except I could probably add an option in to disable circular dupe checking.

You'd have to manually disable it, perform the rescan, and then reenable it.

I'll add this in for you in the next prealpha build.

... Tech support is just a busy signal away

--- Mystic BBS v1.12 A47 2021/12/10 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hello g00r00!

Thank you for your reply!

On 13 Dec 2021, g00r00 said the following...

Hmmm this is a tough one. I am not sure there really is a way around
that except I could probably add an option in to disable circular dupe checking.

You'd have to manually disable it, perform the rescan, and then reenable it.

I'll add this in for you in the next prealpha build.

Thanks a lot! It's a nice feature to have for those special occasions. =)

Best regards
Björn

--- Mystic BBS v1.12 A47 2021/12/10 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

Hello g00r00!

On 13 Dec 2021, Björn Wiberg said the following...

that except I could probably add an option in to disable circular dup checking.
I'll add this in for you in the next prealpha build.

Thanks a lot! It's a nice feature to have for those special occasions. =)

I just wanted to let you know that the dupe_circular setting seems to be working fine. Thanks a lot!

However, there was no mention of it in mutil.ini, only in whatsnew.txt. Perhaps it would be good to add it to the stock mutil.ini?

Thanks again!

Best regards
Björn

--- Mystic BBS v1.12 A47 2021/12/13 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

However, there was no mention of it in mutil.ini, only in whatsnew.txt. Perhaps it would be good to add it to the stock mutil.ini?

That was half intentional and half laziness ;)

I really believe it should always be enabled except in those ultra rare situations like you had, so I was thinking I would leave it out but mention it on the Wiki or something.

If you guys think it should be included for completeness I will do it though.

... Everyone has a photographic memory. Some don't have film.

--- Mystic BBS v1.12 A47 2021/12/13 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hello g00r00!

Thank you for your reply!

On 20 Dec 2021, g00r00 said the following...

However, there was no mention of it in mutil.ini, only in whatsnew.tx

That was half intentional and half laziness ;)

;)

I really believe it should always be enabled except in those ultra rare situations like you had, so I was thinking I would leave it out but mention it on the Wiki or something.

You're right!

I'll keep a commented-out copy of it in my mutil.ini in case I would need it for any future rescans. :)

Best regards
Björn

--- Mystic BBS v1.12 A47 2021/12/13 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

On 20 Dec 2021 at 11:25a, g00r00 pondered and said...

I really believe it should always be enabled except in those ultra rare situations like you had, so I was thinking I would leave it out but mention it on the Wiki or something.

I'd suggest just the Wiki.

--- Mystic BBS v1.12 A47 2021/11/06 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

On 20 Dec 2021 at 11:25a, g00r00 pondered and said...

If you guys think it should be included for completeness I will do it though.

Actually the more I think of it I would suggest you do both. Better to have the ini cover it all as well as documented on the wiki.

--- Mystic BBS v1.12 A47 2021/11/06 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

If you guys think it should be included for completeness I will do it though.

Actually the more I think of it I would suggest you do both. Better to have the ini cover it all as well as documented on the wiki.

I will add it into the default .ini and then leave a comment in there that it should be enabled in 99.99% of cases or something!

... Message encrypted: Press ALT-F4 to read encoded message
--- Mystic BBS v1.12 A47 2021/12/13 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)