Sveiks All!

Is there a setting in golded that enables the distinction of read .vs. unread messages in L)ist view?







--- GoldED+/W32-MINGW 1.1.5-b20180707
* Origin: ----> Point Of VeleNo BBs (http://www.velenobbs.net) (2:333/808.7)

Hi August!

13 May 2020 23:20, from August Abolins -> All:

Is there a setting in golded that enables the distinction of read .vs. unread messages in L)ist view?

The color.
Unread Msgs are cyan.

CU, Ricsi

... If everything seems to be OK, you've overlooked something.
--- GoldED+/LNX
* Origin: Mobius strippers never show you their back side. (2:310/31)

Sveiks Richard!

13 May 20 23:27, you wrote to me:

Is there a setting in golded that enables the distinction of read
.vs. unread messages in L)ist view?

The color.
Unread Msgs are cyan.

I've tried a variety of different theme colour combinations. But the L)ist view looks the same for every line. The only lines that stand out are the ones that have my name.


--- GoldED+/W32-MINGW 1.1.5-b20180707
* Origin: ----> Point Of VeleNo BBs (http://www.velenobbs.net) (2:333/808.7)

Hi August!

15 May 2020 01:26, from August Abolins -> Richard Menedetter:

The color.
Unread Msgs are cyan.

I've tried a variety of different theme colour combinations. But the L)ist view looks the same for every line. The only lines that stand
out are the ones that have my name.

COLOR MENU UNREAD Cyan on Black ; msg is unread

CU, Ricsi

... Progress is made by lazy men trying to find easier ways to do something. --- GoldED+/LNX
* Origin: Some people will believe anything whispered to them. (2:310/31)

Re: golded, show read/unread msgs - how?
By: August Abolins to Richard Menedetter on Fri May 15 2020 01:26:56

I've tried a variety of different theme colour combinations. But the
L)ist view looks the same for every line. The only lines that stand
out are the ones that have my name.

maybe i'm not understanding but when i start my golded+, the list of areas has 8 basic columns...

the 1st may contain a ">" indicating new/unreaed messages in that area...

the 2nd contains the group letter...

3rd is area description...

4th is areatag...

5th may contain a "+" indicating new/unread messages to me in that area...

6th may contain a "*" indicating new/unread messages in that area... this seems
to go with the ">" in the 1st column...

7th is the number of new messages in the area...

8th is the total number of messages in the area...

the 1st, 5th, and 6th columns do not have a title on them...

i have my list settings set to show the list in the listed order... it does not
rearrange itself based on new messages and/or on new messages to me...

when i start my golded, if i'm interested only in messages to me, i move to those areas with a "+" in the 5th column and start reading... otherwise, and most normally, i just start at the top of the list and read all messages in all
the areas as i go through them...


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

//Hello Richard, //

On *15.05.20* At *11:15:52* you replied to a post in *GOLDED*
from *August Abolins* About *"golded, show read/unread msgs - how?"*.

COLOR MENU UNREAD Cyan on Black ; msg is unread

This is what I have as well, it works..

Another question for you, is there a setting about how to handle dupes? I believe the reason I get a dupe for every message I compose in golded is because when I create a message in golded it exists in golded, then gets sent to my uplink which then sends it back to my point so now there are two copies? The one I wrote originally and the one that gets sent to me. So each message I write always produces a dupe in the dupes area? Is there a setting to avoid this?

Regards ...
Rick Smith

--- WinPoint Beta 5 (359.1)
* Origin: Abacus Sysop Point..... bbs.abon.us:2323 (1:340/202.1)

Re: golded, show read/unread msgs - how?
By: Rick Smith to Richard Menedetter on Fri May 15 2020 06:59:24

Another question for you, is there a setting about how to handle dupes?
I believe the reason I get a dupe for every message I compose in golded
is because when I create a message in golded it exists in golded, then gets sent to my uplink which then sends it back to my point so now
there are two copies? The one I wrote originally and the one that gets sent to me. So each message I write always produces a dupe in the dupes area? Is there a setting to avoid this?

the question is why is your BOSS node sending the message back to your point...
it should not be doing that... your BOSS node is the place to fix this problem...


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

the question is why is your BOSS node sending the message back to your point... it should not be doing that... your BOSS node is the place to
fix this problem...

Perfect do you know where that is in Mystic? I have scanned around the
settings and nothing obvious jumped out at me.. I will have a look at the
wiki see if there are any clues?

---
Regards,

Rick // Nitro

--- Mystic BBS v1.12 A46 2020/04/29 (Windows/64)
* Origin: Abacus BBS! ---> bbs.abon.us:2323 (1:340/202)

Hi Rick!

15 May 2020 06:59, from Rick Smith -> Richard Menedetter:

Another question for you, is there a setting about how to handle
dupes? I believe the reason I get a dupe for every message I compose
in golded is because when I create a message in golded it exists in golded,

It does not exit "in golded".
Golded is your editor.
It inserts a message into your messagebase.

then gets sent to my uplink which then sends it back to my
point so now there are two copies?

There is something SERIOUSLY wrong with your setup, if it sends you BACK your own messages!!!

The one I wrote originally and the one that gets sent to me. So each message I write always produces a dupe in the dupes area? Is there a setting to avoid this?

Yes ... configure your tosser correctly.
Golded only inserts the message, the rest is up to your tosser!
Nothing to do with golded!

CU, Ricsi

... If "pro" is the opposite of "con", what's the opposite of "progress"?
--- GoldED+/LNX
* Origin: I distinctly remember forgetting that. (2:310/31)

Re: Re: golded, show read/unread msgs - how?
By: Rick Smith to mark lewis on Fri May 15 2020 01:59 pm

the question is why is your BOSS node sending the message back to
your point... it should not be doing that... your BOSS node is the
place to fix this problem...

Perfect do you know where that is in Mystic? I have scanned around the settings and nothing obvious jumped out at me.. I will have a look at the wiki see if there are any clues?

I was going to ask if your BOSS was a mystic node - Mystic has been doing some unusual things with messages of late when its acting as a hub...
...ëîåã

... Professionals build the Titanic, amateurs built the Ark.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)

Rick wrote (2020-05-15):

the question is why is your BOSS node sending the message back to
your point... it should not be doing that... your BOSS node is the
place to fix this problem...

Perfect do you know where that is in Mystic? I have scanned around the settings and nothing obvious jumped out at me.. I will have a look at the wiki see if there are any clues?

It's easy. Don't use Mystic as the tosser for your node, but some software that
is known to work reliable. And please use the MYSTIC area for Mystic related questions.



* Origin: (2:280/464.47)

Hello Richard!

15 May 20, Richard Menedetter wrote to August Abolins:

COLOR MENU UNREAD Cyan on Black ; msg is unread

Where is the read/unread information saved?

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Rick!

15 May 20, Rick Smith wrote to Richard Menedetter:

Another question for you

Sorry, i couldn't resist to adjust the subject line. ;)

is there a setting about how to handle dupes?

Yes, but there are many systems involved and the dupes may be set up on purpose. Since the change from POTS to Fido over IP the dupe rationale turned by 180 deg. POTS dupes are for cost reduction. FoIP dupes are for network stability. It's a question of routing. Chain routes from node 1 to node 2 to node 3 are broken if node 2 goes offline and node 3 would never receive mails from node 1. That could be avoided with mesh routing where node 1 have direct links to node 2 and node 3.

Because links to any system in the network is a lot of work to set up not all nodes do have links to any other system. If there is node 4 with links to node 2 and node 3 but not to node 1 then node 2 and 3 will see that new mail from node 1 is unseen by node 4 and both 2 and 3 will export the mail to node 4. Tadaa, node 4 got dupes. But node 4 will receive mail even if node 2 or 3 goes down.

So if you have links to more than one system dupes can be normal. Dupes are not
normal if you are a point with one link only (uplink to your boss).

I believe the reason I get a dupe for every message I compose in
golded is because when I create a message in golded it exists in
golded, then gets sent to my uplink which then sends it back to my
point so now there are two copies?

Yes, but i can't imagine a misconfiguration of golded that could be responsible
for that. Hm, maybe if the from addressing does not match the aka of the "first
contact" tosser.

The one I wrote originally and the one that gets sent to me. So each message I write always produces a dupe in the dupes area? Is there a setting to avoid this?

--- WinPoint Beta 5 (359.1)
* Origin: Abacus Sysop Point..... bbs.abon.us:2323 (1:340/202.1)

You don't have dupes with WinPoint?
I suppose WinPoint does use it's own internal tosser.

Check the path kludges in golded (alt-k in reader) in the dupe area. If you see
your aka only, then it's a config problem on your side. If not they may be wanted dupes for network stability.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hi Kai!

16 May 2020 00:11, from Kai Richter -> Richard Menedetter:

COLOR MENU UNREAD Cyan on Black ; msg is unread

Where is the read/unread information saved?

In the messagebase, where else?

CU, Ricsi

... To be intoxicated is to feel sophisticated but not be able to say it.
--- GoldED+/LNX
* Origin: Caution: Breathing may be hazardous to your health. (2:310/31)

Hello Richard,

On Sat May 16 2020 00:57:40, Richard Menedetter wrote to Rick Smith:

Yes ... configure your tosser correctly.
Golded only inserts the message, the rest is up to your tosser!
Nothing to do with golded!

I almost wonder if he is composing and saving this message in Golded, and then sees it when he newscans messages in Mystic...?

...because he is sharing his Mystic message base with Golded, this is actually exactly what would happen. He may just be seeing his locally stored Golded message as a new message when he's on his BBS.

But yeah, if his BOSS node is sending it back to him then there's definitely a problem. In the original message, he mentioned uplink as well. In that case, he
shouldn't be linked to his BOSS node's uplink with his point whatsoever, but that could be taking too much out of context here. Just looking at any possible
options and causes.

Also, if NOT using the latest Mystic prealpha, there were point issues in some of the older versions that have since been fixed.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20181215
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Re: Re: golded, show read/unread msgs - how?
By: Rick Smith to mark lewis on Fri May 15 2020 13:59:58

the question is why is your BOSS node sending the message back to
your point... it should not be doing that... your BOSS node is the
place to fix this problem...

Perfect do you know where that is in Mystic? I have scanned around
the settings and nothing obvious jumped out at me.. I will have a
look at the wiki see if there are any clues?

there are no settings... it is a normal part of echomail processing... it sounds like the tosser is not properly detecting the point has already seen the
message... this is a code defect that the maintainer must fix... it might already be fixed in the latest version, too... i would start by ensuring you have the latest version installed...


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Re: golded, show read/unread msgs - how?
By: Kai Richter to Richard Menedetter on Sat May 16 2020 00:11:54

COLOR MENU UNREAD Cyan on Black ; msg is unread

Where is the read/unread information saved?

the last read pointer determines what has been read and what hasn't...


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Re: golded, show read/unread msgs - how?
By: Nicholas Boel to Richard Menedetter on Sat May 16 2020 08:00:24

But yeah, if his BOSS node is sending it back to him then there's definitely a problem. In the original message, he mentioned uplink
as well. In that case, he shouldn't be linked to his BOSS node's
uplink with his point whatsoever, but that could be taking too much
out of context here.

i think it is also a terminology problem in some respects... points should refer to their uplink as their BOSS node since that's the term used for them for clarity between them and other types of uplinks... points should only contact their BOSS node for mail and files distributed via FDN... the only time
a point might connect to another system is if they are FREQing a file from that
other system...

FTN has some terminology and practises that take some time to learn to use properly ;)


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

//Hello mark, //

On *16.05.20* At *10:36:29* you replied to a post in *GOLDED*
from *Rick Smith* About *"Re: golded, show read/unread msgs - how?"*.

@AREA:GOLDED @TZUTC: -0400 @MSGID: 247.fido-golded@1:3634/12 23253164 @REPLY: 1:340/202 529fdf3b @PID: Synchronet 3.18a-Linux May 5 2020 GCC 7.5.0 @TID: SBBSecho 3.11-Linux r3.172 May 5 2020 GCC 7.5.0 @CHRS: ASCII 1 @NOTE: FSEditor.js v1.104 Re: Re: golded, show read/unread msgs -
how? By: Rick Smith to mark lewis on Fri May 15 2020 13:59:58

\

there are no settings... it is a normal part of echomail processing... it sounds like the tosser is not properly detecting the point has already seen the message... this is a code defect that the maintainer must fix... it might already be fixed in the latest version, too... i would start by ensuring you have the latest version installed...

Thank you Mark for explaining that, I now pretty much understand or atleast I think I do, I will reach out to g00r00. While this started as a golded ? because I noticed it in golded I assumed it was golded, however now that I understand it better and that it is probably Mystic I will move my discussion there..

Thanks again I really appreciate the guidance.

Rick

)\/(ark
-+- SBBSecho 3.11-Linux

@ ORIGINAL: SouthEast Star Mail HUB - SESTAR (1:3634/12)

@SEEN-BY: 1/120 106/201 116/116 18 123/0 140 150 170 25 50 755 135/300 14/5 6 SEEN-BY: 15/0 153/7715 154/10 16/101 18/0 19/36 218/700 222/2 230/150 152 SEEN-BY: 2320/105 240/1120 250/1 261/100 38 266/512 267/155 275/100 282/1031 SEEN-BY: 282/1056 291/100 111 298/26 300/5 6 320/119 219 340/0 201 202 400 7 SEEN-BY: 340/800 341/66 3634/0 119 12 15 27 50 396/45 5020/1042 640/1321 SEEN-BY: 712/848 801/161 189 @PATH: 3634/12 261/38 340/400 202

Regards ...
Rick Smith

--- WinPoint Beta 5 (359.1)
* Origin: Abacus Sysop Point..... bbs.abon.us:2323 (1:340/202.1)

Sveiks mark!

16 May 20 10:44, you wrote to Nicholas Boel:

points should only contact their BOSS node for mail and files
distributed via FDN... the only time a point might connect to another system is if they are FREQing a file from that other system...

Points (like me waving madly!) can send direct/crash netmail akin to what parent nodes do. That is particularly a fine feature of OpenXP. The advantages are obvious and should be encouraged. ;)




--- GoldED+/W32-MINGW 1.1.5-b20180707
* Origin: ----> Point Of VeleNo BBs (http://www.velenobbs.net) (2:333/808.7)

Hello Richard!

16 May 20, Richard Menedetter wrote to Kai Richter:

COLOR MENU UNREAD Cyan on Black ; msg is unread

Where is the read/unread information saved?

In the messagebase, where else?

That color line does not change anything here - so that's the question exactly.

Does it depend on the msgbase format? I do use squish.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello mark!

16 May 20, mark lewis wrote to Kai Richter:

COLOR MENU UNREAD Cyan on Black ; msg is unread

Where is the read/unread information saved?

the last read pointer determines what has been read and what hasn't...

That's my concept of daily usage with a squish msgbase and the reason for my question. The lastread pointer is stored with a user index number in the *.sql file (not mySQL, it's squish-lastread) of the echoarea.

If there is a read/unread flag per mail i would like to know.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Re: /points should only..
By: August Abolins to mark lewis on Sun May 17 2020 23:24:05

points should only contact their BOSS node for mail and files
distributed via FDN... the only time a point might connect to
another system is if they are FREQing a file from that other
system...

Points (like me waving madly!) can send direct/crash netmail akin
to what parent nodes do.

yes... that falls in with the FREQ example i gave ;)


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Hello Richard!

18 May 20, Richard Menedetter wrote to Kai Richter:

I just changed from cyan to yellow, and all me unread messages were
shown in yellow ;)

I disabled all color lines but yours to go back to the defaults. My colors are gone but no difference for read/unread.

--- GoldED+/LNX

Version?

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hi mark!

16 May 2020 10:44, from mark lewis -> Nicholas Boel:

points should only contact their BOSS node for mail and files
distributed via FDN... the only time a point might connect to another system is if they are FREQing a file from that other system...

????

Points can contact ANY system they want.

CU, Ricsi

... I don't have any solution, but I certainly admire the problem.
--- GoldED+/LNX
* Origin: The severity of the itch is proportional to the reach. (2:310/31)

Hi Kai!

17 May 2020 23:26, from Kai Richter -> Richard Menedetter:

COLOR MENU UNREAD Cyan on Black

Where is the read/unread information saved?

In the messagebase, where else?

That color line does not change anything here - so that's the question exactly.

I just changed from cyan to yellow, and all me unread messages were shown in yellow ;)

Does it depend on the msgbase format? I do use squish.

It should be supported on any msgbase.
I use JAM, but Squish is 100% also supported.

CU, Ricsi

... Sounds like you've been snacking on some of the local mushrooms!
--- GoldED+/LNX
* Origin: A small carafe of wine is immoral and inadequate. (2:310/31)

Hi Martin!

22 May 2020 13:11, from Martin Foster -> Richard Menedetter:

I just changed from cyan to yellow, and all me unread messages
were shown in yellow ;)

I disabled all color lines but yours to go back to the defaults.
My colors are gone but no difference for read/unread.

Very strange ...

Still doesn't work for me :(

Honestly no clue.
This has worked for me for over 20 years.

You can netmail me your config (with passwords etc. xxxxed out).
I can try to reproduce here.

CU, Ricsi

... The more you sweat in training, the less you bleed in battle.
--- GoldED+/LNX
* Origin: When you're through changing, you're through. (2:310/31)

Hi Martin!

22 May 2020 13:11, from Martin Foster -> Richard Menedetter:

Still doesn't work for me :(

I completely forfogt that you need to enable this feature with:
HIGHLIGHTUNREAD Yes

Sorry!

CU, Ricsi

... The fact that no one understands you doesn't mean you're an artist.
--- GoldED+/LNX
* Origin: I program, therefore I exist. (2:310/31)

Hello Richard!

*** Thursday 28.05.20 at 11:12, Richard Menedetter wrote to Martin Foster:

Still doesn't work for me :(

I completely forfogt that you need to enable this feature with: HIGHLIGHTUNREAD Yes

OK, that works a treat, thanks.

Sorry!

No problem :-)

Regards,
Martin

--- OpenXP 5.0.43
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hi Kai!

20 May 2020 17:24, from Kai Richter -> Richard Menedetter:

I just changed from cyan to yellow, and all me unread messages
were shown in yellow ;)

I disabled all color lines but yours to go back to the defaults. My
colors are gone but no difference for read/unread.

I forgot that you need to set:

HIGHLIGHTUNREAD Yes

CU, Ricsi

... It is enjoyment and not possession that makes for true happiness.
--- GoldED+/LNX
* Origin: First you take 16 habaneros... (2:310/31)

Hello Richard!

28 May 20, Richard Menedetter wrote to Martin Foster:

I completely forfogt that you need to enable this feature with: HIGHLIGHTUNREAD Yes

It's working now, but not as expected. I thought i will see my mails in read status but they are all unread. If i open them again then the status changes to
read.

But at least if done once then the read/unread information is saved for restart. But i still don't have an idea where that save is kept.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)