Howdy,

I've noticed for a while that I havent received the imsg alert when incoming mail is addressed to me. Not sure if it applies to netmail/email, but it is true for echomail.

(It's such a useful feature :)

I think I've narrowed it down to being logged in or not.

If I am logged in, I see the message (and notice that the data/msg/0001.msg is created). If I am logged of, I do not get the message and data/msg/0001.msg is not created.

Any chance it can be returned?



...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

Re: imsg on incoming echomail
By: deon to Digital Man on Sat Jan 18 2025 03:44 pm

I've noticed for a while that I havent received the imsg alert when incoming mail is addressed to me. Not sure if it applies to netmail/email, but it is true for echomail.

(It's such a useful feature :)

I think I've narrowed it down to being logged in or not.

If I am logged in, I see the message (and notice that the data/msg/0001.msg is created). If I am logged of, I do not get the message and data/msg/0001.msg is not created.

Any chance it can be returned?

There's been no known change in this feature. When I logon, I see echomail notifications from SBBSecho, so it does seem to be working. I'll keep an eye on it, but currently see no issue. Maybe something is deleting the messages as you logon with your seeing them?
--
digital man (rob)

Rush quote #10:
To you, is it movement or is it action? Is it contact or just reaction?
Norco, CA WX: 48.2øF, 85.0% humidity, 0 mph NE wind, 0.00 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: imsg on incoming echomail
By: Digital Man to deon on Fri Jan 17 2025 09:27 pm

If I am logged in, I see the message (and notice that the data/msg/0001.msg is created). If I am logged of, I do not get the message and data/msg/0001.msg is not created.

Any chance it can be returned?

There's been no known change in this feature. When I logon, I see echomail notifications from SBBSecho, so it does seem to be working. I'll keep an eye on it, but currently see no issue. Maybe something is deleting the messages as you logon with your seeing them?

BTW, you can test this theory by just writing/appending to that 0001.msg file and see if you see the contents as you logon or if the file just disappears.
--
digital man (rob)

Breaking Bad quote #30:
Damn, chick's got an ass like an onion - makes me want to cry. - Hank Schrader Norco, CA WX: 47.8øF, 85.0% humidity, 0 mph NE wind, 0.00 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: imsg on incoming echomail
By: Digital Man to deon on Fri Jan 17 2025 09:27 pm

Howdy,

There's been no known change in this feature. When I logon, I see echomail notifications from SBBSecho, so it does seem to be working. I'll keep an eye on it, but currently see no issue. Maybe something is deleting the messages as you logon with your seeing them?

So further update, it seems the QWK posts do generate a notification. I'm looking for data/msgs/0001.msg before I login, and I saw it there with your messages.

But no, the messages are not being deleted (Scan all new to me reveals them), and I have nothing outside of sync deleting data/msgs/0001.msg.

Incently, when I manually create data/msgs/0001.msg outside of sync (I've been copying an old one to data/msgs/0001.msg, it doesnt trigger the alert - should it? Only when a new one is added to it does.)


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

Re: imsg on incoming echomail
By: Digital Man to deon on Fri Jan 17 2025 09:37 pm

Howdy,

BTW, you can test this theory by just writing/appending to that 0001.msg file and see if you see the contents as you logon or if the file just disappears.

Yup, in the previous messages I was doing that, and no, no alert appears when I'm logged in. But if I log off and on I think it does. I'll test that now to be sure.


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

Re: imsg on incoming echomail
By: deon to Digital Man on Sat Jan 18 2025 08:23 pm

Howdy,

BTW, you can test this theory by just writing/appending to that 0001.msg file and see if you see the contents as you logon or if the file just disappears.

Yup, in the previous messages I was doing that, and no, no alert appears when I'm logged in. But if I log off and on I think it does. I'll test that now to be sure.

So I noticed when I logged of data/msgs/0001.msg was removed. But confirmed, if I create it and login I get the notification. (However, I dont seem to get it while logged in, until another notification comes in...)


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

Re: imsg on incoming echomail
By: deon to Digital Man on Sat Jan 18 2025 08:22 pm

Incently, when I manually create data/msgs/0001.msg outside of sync (I've been copying an old one to data/msgs/0001.msg, it doesnt trigger the alert - should it? Only when a new one is added to it does.)

If you're logged in, you won't see the message "pop-up" unless the "Message Waiting" node status flag is set:
https://wiki.synchro.net/ref:node_status

You can use the ;msgs command (assuming you're using a command shell that supports string commands) to view currently waiting and previously displayed short messsages.
--
digital man (rob)

Rush quote #49:
Some will sell their dreams for small desires or lose the race to rats
Norco, CA WX: 47.4øF, 86.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: imsg on incoming echomail
By: Digital Man to deon on Sat Jan 18 2025 03:04 am

Re: imsg on incoming echomail
By: deon to Digital Man on Sat Jan 18 2025 08:22 pm

Incently, when I manually create data/msgs/0001.msg outside of sync (I've been copying an old one to data/msgs/0001.msg, it doesnt trigger the alert - should it? Only when a new one is added to it does.)

If you're logged in, you won't see the message "pop-up" unless the "Message Waiting" node status flag is set:
https://wiki.synchro.net/ref:node_status

You can use the ;msgs command (assuming you're using a command shell that supports string commands) to view currently waiting and previously displayed short messsages.

Again, I tested and got a short message notification from sbbsecho of received echomail:

þ Main þ 0:09:20 [3] FidoNet [27] FIDOTEST:

RBB Test Robot sent you EchoMail on FidoNet FIDOTEST

þ Private þ Telegram, Message, Chat, InterBBS, View, or [Quit]:

... so seems to still be working.
--
digital man (rob)

Sling Blade quote #5:
Karl Childers (to father): You ought not killed my little brother...
Norco, CA WX: 47.4øF, 86.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: imsg on incoming echomail
By: Digital Man to deon on Sat Jan 18 2025 03:10 am

Howdy,

... so seems to still be working.

So how do I turn up logging to see that SBBSecho is creating the file.

Because I know its not (I've looked), and I'll like to figure out why.

My method has been, send a test message to my clrghouz mailer, log off, watch sbbsecho process the reply packet, no data/msgs/0001.msg is created.


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

Re: imsg on incoming echomail
By: deon to Digital Man on Sun Jan 19 2025 11:00 am

Howdy,

My method has been, send a test message to my clrghouz mailer, log off, watch sbbsecho process the reply packet, no data/msgs/0001.msg is created.

So I just tried this again, and on this occassion it was created, and yes I got the alert when I logged on. I did this yesterday and the file wasnt created.

I know something is not working correctly because it has been many occassions when I've been reading new mail that I've seen one to me (and didnt get a notification). I'm now doing a scan all to me first when logging on (and finding some), when I dont get a notification on login.




...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

Re: imsg on incoming echomail
By: deon to Digital Man on Sun Jan 19 2025 11:00 am

Re: imsg on incoming echomail
By: Digital Man to deon on Sat Jan 18 2025 03:10 am

Howdy,

... so seems to still be working.

So how do I turn up logging to see that SBBSecho is creating the file.

Because I know its not (I've looked), and I'll like to figure out why.

My method has been, send a test message to my clrghouz mailer, log off, watch sbbsecho process the reply packet, no data/msgs/0001.msg is created.

Here's the relevant code in sbbsecho.c, feel free to add more lprintf() calls or maybe step through with a debugger if you're so inclined:

if (result == SMB_SUCCESS) { /* Successful import */
user_t user;
if (i != cfg.badecho && cfg.echomail_notify
&& (user.number = lookup_user(&scfg, &user_list, hdr.to)) != 0
&& getuserdat(&scfg, &user) == 0
&& user_can_read_sub(&scfg, cfg.area[i].sub, &user, NULL)) {
char tmp[128];
safe_snprintf(str, sizeof(str), text[FidoEchoMailReceived]
, timestr(&scfg, time32(NULL), tmp)
, hdr.from
, scfg.grp[scfg.sub[cfg.area[i].sub]->grp]->sname
, scfg.sub[cfg.area[i].sub]->sname);
putsmsg(&scfg, user.number, str);
}
--
digital man (rob)

Breaking Bad quote #47:
He said he'll break my legs, he meant It... he gave me the dead mackerel eyes. Norco, CA WX: 61.7øF, 52.0% humidity, 1 mph SSW wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: imsg on incoming echomail
By: deon to Digital Man on Sun Jan 19 2025 11:06 am

Re: imsg on incoming echomail
By: deon to Digital Man on Sun Jan 19 2025 11:00 am

Howdy,

My method has been, send a test message to my clrghouz mailer, log off, watch sbbsecho process the reply packet, no data/msgs/0001.msg is created.

So I just tried this again, and on this occassion it was created, and yes I got the alert when I logged on. I did this yesterday and the file wasnt created.

Did you try the ;msgs command to see if it's there in your message history?
--
digital man (rob)

This Is Spinal Tap quote #7:
Nigel Tufnel: That's just nitpicking, isn't it?
Norco, CA WX: 61.7øF, 52.0% humidity, 1 mph SSW wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: imsg on incoming echomail
By: Digital Man to deon on Sat Jan 18 2025 04:19 pm

Howdy,

Did you try the ;msgs command to see if it's there in your message history?

Doesnt the ;msgs command just read the 0001.last.x.msg files? I didnt use the msgs command, but did look at those files and the one I was expecting wasnt there.

I'm going to monitor it more closely to see if I can find out why I'm not seeing the message as I expect...


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

Re: imsg on incoming echomail
By: deon to Digital Man on Sun Jan 19 2025 12:18 pm

Re: imsg on incoming echomail
By: Digital Man to deon on Sat Jan 18 2025 04:19 pm

Howdy,

Did you try the ;msgs command to see if it's there in your message history?

Doesnt the ;msgs command just read the 0001.last.x.msg files?

Yup.

I didnt use
the msgs command, but did look at those files and the one I was expecting wasnt there.

I'm going to monitor it more closely to see if I can find out why I'm not seeing the message as I expect...

Okay, please let me know what you find.
--
digital man (rob)

Synchronet/BBS Terminology Definition #81:
SyncEdit = A defunct 3rd party full-screen editor written for Synchronet
Norco, CA WX: 54.8øF, 68.0% humidity, 6 mph W wind, 0.00 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: imsg on incoming echomail
By: Digital Man to deon on Sat Jan 18 2025 06:10 pm

Howdy,

I'm going to monitor it more closely to see if I can find out why I'm not seeing the message as I expect...

Okay, please let me know what you find.

OK, I think I've figured out the sequence. As background, I access SBBS via my laptop (using Muffinterm - but that shouldnt matter), and often leave the terminal open for hours at a time.

Over night, my laptop will go to sleep, so the connection to SBBS would eventually be terminated.

So this afternoon I did this:

a) Sent a test message to clrghouz (which would generate a reply), and killed my network connection (simulating my laptop going to sleep and not logging off).
b) Sync exported the message
c) Sync imported the reply
d) No update to msgs/0001.msg (when there should have been).

Here is some logging:

1) I checked the status of the 0001*msgs before doing (a).

[deon@rl8-2-1 data]$ ls -al msgs/0001.*msg
-rw------- 1 root root 367 Jan 19 16:32 msgs/0001.last.0.msg
-rw------- 1 root root 285 Jan 12 16:25 msgs/0001.last.10.msg
-rw------- 1 root root 82 Jan 9 18:14 msgs/0001.last.11.msg
-rw------- 1 root root 207 Jan 9 13:03 msgs/0001.last.12.msg
-rw------- 1 root root 59 Jan 9 08:22 msgs/0001.last.13.msg
-rw------- 1 root root 64 Jan 8 13:11 msgs/0001.last.14.msg
-rw------- 1 root root 133 Jan 8 08:13 msgs/0001.last.15.msg
-rw------- 1 root root 58 Jan 7 22:23 msgs/0001.last.16.msg
-rw------- 1 root root 567 Jan 7 22:10 msgs/0001.last.17.msg
-rw------- 1 root root 567 Jan 7 22:07 msgs/0001.last.18.msg
-rw------- 1 root root 235 Jan 19 12:13 msgs/0001.last.1.msg
-rw------- 1 root root 71 Jan 19 11:02 msgs/0001.last.2.msg
-rw------- 1 root root 306 Jan 19 10:57 msgs/0001.last.3.msg
-rw------- 1 root root 71 Jan 18 20:24 msgs/0001.last.4.msg
-rw------- 1 root root 235 Jan 18 20:19 msgs/0001.last.5.msg
-rw------- 1 root root 142 Jan 18 15:36 msgs/0001.last.6.msg
-rw------- 1 root root 71 Jan 18 15:31 msgs/0001.last.7.msg
-rw------- 1 root root 64 Jan 16 17:00 msgs/0001.last.8.msg
-rw------- 1 root root 59 Jan 16 11:04 msgs/0001.last.9.msg
-rw------- 1 root root 71 Jan 19 16:37 msgs/0001.last.msg
-rw------- 1 root root 0 Jan 19 16:37 msgs/0001.msg

2) Output of sbbsecho when the test message was sent, and the reply received (b) and (c)

2025-01-19 17:11:01 Exported: 1 msgs pvt_test -> PVT_TEST
2025-01-19 17:11:01 Exported: 1 msgs total
2025-01-19 17:11:02 SBBSecho (PID 309988) exiting with error level 0, Packets(0 imported, 2 sent), EchoMail(0 imported, 1 exported)
2025-01-19 17:11:30 Importing /opt/sbbs/fido/inbound/000a1ebe.pkt (type 2e, 1.8KB) from 10:1/1 to 10:1/4
2025-01-19 17:11:30 Imported: 1 msgs pvt_test <- PVT_TEST
2025-01-19 17:11:30 Imported: 1 msgs total
2025-01-19 17:11:30 SBBSecho (PID 309999) exiting with error level 0, Packets(1 imported, 1 sent), EchoMail(1 imported, 0 exported)

3) A list of the 0001*msg files after the import - notice that 0001.msg is still 0 bytes in size (and no change in mtime), and no other *last.msg files have been changed.

[deon@rl8-2-1 data]$ ls -al msgs/0001.*msg
-rw------- 1 root root 367 Jan 19 16:32 msgs/0001.last.0.msg
-rw------- 1 root root 285 Jan 12 16:25 msgs/0001.last.10.msg
-rw------- 1 root root 82 Jan 9 18:14 msgs/0001.last.11.msg
-rw------- 1 root root 207 Jan 9 13:03 msgs/0001.last.12.msg
-rw------- 1 root root 59 Jan 9 08:22 msgs/0001.last.13.msg
-rw------- 1 root root 64 Jan 8 13:11 msgs/0001.last.14.msg
-rw------- 1 root root 133 Jan 8 08:13 msgs/0001.last.15.msg
-rw------- 1 root root 58 Jan 7 22:23 msgs/0001.last.16.msg
-rw------- 1 root root 567 Jan 7 22:10 msgs/0001.last.17.msg
-rw------- 1 root root 567 Jan 7 22:07 msgs/0001.last.18.msg
-rw------- 1 root root 235 Jan 19 12:13 msgs/0001.last.1.msg
-rw------- 1 root root 71 Jan 19 11:02 msgs/0001.last.2.msg
-rw------- 1 root root 306 Jan 19 10:57 msgs/0001.last.3.msg
-rw------- 1 root root 71 Jan 18 20:24 msgs/0001.last.4.msg
-rw------- 1 root root 235 Jan 18 20:19 msgs/0001.last.5.msg
-rw------- 1 root root 142 Jan 18 15:36 msgs/0001.last.6.msg
-rw------- 1 root root 71 Jan 18 15:31 msgs/0001.last.7.msg
-rw------- 1 root root 64 Jan 16 17:00 msgs/0001.last.8.msg
-rw------- 1 root root 59 Jan 16 11:04 msgs/0001.last.9.msg
-rw------- 1 root root 71 Jan 19 16:37 msgs/0001.last.msg
-rw------- 1 root root 0 Jan 19 16:37 msgs/0001.msg

Interestingly, when I reconnected to the wifi (5 or so minutes later) and logged another minute or so after that, Sync thought I was still connected to Node 1 (obviously not long enough yet to kick me off, even though Muffinterm had noticed (after rejoining the wifi) the TCP session was severed.

It also didnt show the message waiting status (M)?

Node Status
ÄÄÄÄ ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
1 deon posting message via telnet (P) [UQ]

Anyway, hopefully this is enough to see it in action. Its annoying, but I guess I get why I dont see those messages alerts.

(And yes, I did a scan all new mail to me after I logged on, and saw the 1 new message from PVT_TEST as expected).


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

Re: imsg on incoming echomail
By: deon to Digital Man on Sun Jan 19 2025 05:36 pm

Anyway, hopefully this is enough to see it in action. Its annoying, but I guess I get why I dont see those messages alerts.

No, I don't really get it. Did you add lprintf() messages to sbbsecho.c like I suggested?
--
digital man (rob)

Steven Wright quote #31:
The sooner you fall behind, the more time you'll have to catch up.
Norco, CA WX: 46.9øF, 87.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: imsg on incoming echomail
By: deon to Digital Man on Sun Jan 19 2025 05:36 pm

It also didnt show the message waiting status (M)?

Node Status
ÄÄÄÄ ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
1 deon posting message via telnet (P) [UQ]

If the node was in a state that it could read/display the message to the user (or it thought it could/did), then it would automatically clear the (M) status flag too. But I would expect the *.last.msg file to have the message contents (after read/display to the user) as well.
--
digital man (rob)

This Is Spinal Tap quote #10:
Dozens of people spontaneously combust each year... just not widely reported. Norco, CA WX: 46.8øF, 87.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: imsg on incoming echomail
By: Digital Man to deon on Sun Jan 19 2025 12:34 am

Howdy,

Anyway, hopefully this is enough to see it in action. Its annoying, but I guess I get why I dont see those messages alerts.

No, I don't really get it. Did you add lprintf() messages to sbbsecho.c like I suggested?

What dont you get?

No, I didnt modify sbbsecho.

But I think I've reproduced the scenario that results in me not getting the messages, that new echomail has come in addressed to me.


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

Re: imsg on incoming echomail
By: Digital Man to deon on Sun Jan 19 2025 12:48 am

Howdy,

But I would expect the *.last.msg file to have the message
contents (after read/display to the user) as well.

Me to.

When I connected and saw that idle node still logged in, I used ;spy 1 to check to see if anything was displayed. I didnt expect anything to display since the 0001.msg file was blank (and nothing was).

And the fact that no *.msg files changed, means that the message was never sent nor consumed right?


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

Re: imsg on incoming echomail
By: deon to Digital Man on Sun Jan 19 2025 11:28 pm

Re: imsg on incoming echomail
By: Digital Man to deon on Sun Jan 19 2025 12:34 am

Howdy,

Anyway, hopefully this is enough to see it in action. Its annoying, but I guess I get why I dont see those messages alerts.

No, I don't really get it. Did you add lprintf() messages to sbbsecho.c like I suggested?

What dont you get?

I don't get why SBBSecho would sometimes send you a short message when importing echomail and sometimes not. I'm doubtful that is true.

No, I didnt modify sbbsecho.

I committed changes to log details when the notification messages are created (or not, due to error).

But I think I've reproduced the scenario that results in me not getting the messages, that new echomail has come in addressed to me.

Most likely the notification message was created and "displayed" on the node that you left connected. I realize you think you have evidence to the contrary, but I'm skeptical. Do you have custom message reading script or shell or something that could be deleting the message without saving it to the *.last.msg chain?
--
digital man (rob)

Rush quote #42:
Media messiahs preying on my fears, pop culture prophets playing in my ears Norco, CA WX: 55.8øF, 70.0% humidity, 3 mph WSW wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: imsg on incoming echomail
By: deon to Digital Man on Sun Jan 19 2025 11:32 pm

When I connected and saw that idle node still logged in, I used ;spy 1 to check to see if anything was displayed. I didnt expect anything to display since the 0001.msg file was blank (and nothing was).

;spy only shows *new* text sent to the client on that node however. If the message was already read/displayed (before you started spying), you wouldn't see it.

And the fact that no *.msg files changed, means that the message was never sent nor consumed right?

Normally, yes, but not if something just read and truncated the .msg file.
--
digital man (rob)

This Is Spinal Tap quote #10:
Dozens of people spontaneously combust each year... just not widely reported. Norco, CA WX: 55.8øF, 70.0% humidity, 3 mph WSW wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: imsg on incoming echomail
By: Digital Man to deon on Sun Jan 19 2025 01:07 pm

Howdy,

Do you have custom message reading script or
shell or something that could be deleting the message without saving it to the *.last.msg chain?

No I have nothing that modifies the msg files - in fact "my" access to SBBS is via the default shell (Classic?) - and its all stock standard.

(You might be thinking of my ansi/videotex - I'm running two instance of SBBS (sharing the same dirs), and the second instance is where my custom shell is, and it's own mods dir. But even then I dont do anything with msg files, nor do I login with user #1.)

Anyway, lets see if I can get the SBBSecho log to show "Error x notifying recipient".


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

Re: imsg on incoming echomail
By: deon to Digital Man on Mon Jan 20 2025 08:46 am

Re: imsg on incoming echomail
By: Digital Man to deon on Sun Jan 19 2025 01:07 pm

Howdy,

Do you have custom message reading script or
shell or something that could be deleting the message without saving it to the *.last.msg chain?

No I have nothing that modifies the msg files - in fact "my" access to SBBS is via the default shell (Classic?) - and its all stock standard.

Okay, good to know.

Anyway, lets see if I can get the SBBSecho log to show "Error x notifying recipient".

Increase your sbbsecho log level to debug and you should see the positive message, or at least, that's what I'd expect:

1/19/25 10:46:32 Successfully notified recipient (user #1)
--
digital man (rob)

Sling Blade quote #2:
Karl (re: killing Doyle): I hit him two good whacks in the head with it.
Norco, CA WX: 59.0øF, 66.0% humidity, 3 mph WNW wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: imsg on incoming echomail
By: Digital Man to deon on Sun Jan 19 2025 01:07 pm

Howdy,

I realize you think you have evidence to the contrary, but I'm skeptical.

OK, so yesterday I rebuilt sync from commit c03035b87e

When I started it, I did the same thing, send a message, disconnect from the network, reconnect a few mins later - and there was a notification.

2025-01-20 08:26:32 Successfully notified recipient (user #1)
2025-01-20 08:57:54 Successfully notified recipient (user #1)

Stumped.

So this afternoon I did the same thing again (so 7ish hours later), and no notification (one was expected - a Scan all to me showed it.)

-rw------- 1 root root 82 Jan 20 12:24 msgs/0001.last.msg
-rw------- 1 root root 71 Jan 20 09:39 msgs/0001.last.0.msg *
-rw------- 1 root root 164 Jan 20 08:40 msgs/0001.last.1.msg
-rw------- 1 root root 71 Jan 20 08:29 msgs/0001.last.2.msg *
-rw------- 1 root root 71 Jan 20 08:16 msgs/0001.last.3.msg *

(The files with size 71 are my test messages, the other two are triggered by you sending me messages. The last one .3.msg I didnt have debugging on, so no corresponding sbbsecho.log message.)

I would have expected the files to be updated as of 14:30:22 which is when the new message came in to me, which should have triggered a notification.

Here is the sbbsecho run for the incoming message that was to me (another packet arrived at the same time, that didnt have echomail addressed to me.)

2025-01-20 14:30:22 SBBSecho 3.23-Linux master/c0305b87e Jan 19 2025 GCC 10.2.1 (PID 9135) invoked with options: -ce
2025-01-20 14:30:22 Configured: 7 archivers, 52 linked-nodes, 13 echolists 2025-01-20 14:30:22 NetMail directory: /opt/sbbs/data/netmail/
2025-01-20 14:30:22 Secure Inbound directory: /opt/sbbs/fido/inbound/ 2025-01-20 14:30:22 Non-secure Inbound directory: /opt/sbbs/fido/nonsecure/ 2025-01-20 14:30:22 Outbound (BSO root) directory: /opt/sbbs/fido/outbound 2025-01-20 14:30:22 Read 335 areas from ../data/areas.bbs
2025-01-20 14:30:22 Bad-echo area: local-badarea
2025-01-20 14:30:22 Read 14 areas from ../data/badareas.lst
2025-01-20 14:30:26 Read 395 echo statistics from ../data/echostats.ini

2025-01-20 14:30:26 Importing /opt/sbbs/fido/inbound/000a20b7.pkt (type 2e, 2.1KB) from 3:633/2744 to 3:633/509
2025-01-20 14:30:26 ERROR 1 (smb_addmsg duplicate TEXT_BODY: hash found in message #12) line 3792 adding message to fdn_bbs_ads
2025-01-20 14:30:26 BBS_ADS Duplicate message from paul lee (1:105/420) to All, subject: 2o fOr beeRS bbS
2025-01-20 14:30:26 Deleting /opt/sbbs/fido/inbound/000a20b7.pkt (from line 6310)

2025-01-20 14:30:26 Importing /opt/sbbs/fido/inbound/000a20bc.pkt (type 2e, 1.8KB) from 10:1/1 to 10:1/4
2025-01-20 14:30:26 Creating outbound packet from 10:1/4 to 10:999/900: /opt/sbbs/temp/sbbsecho/678dc352.pkt
2025-01-20 14:30:26 New password-protected packet (type 2.2) created for linked-node: 10:999/900
2025-01-20 14:30:26 Adding PVT_TEST message from Clearing Houz (10:1/1) to packet for 10:999/900: /opt/sbbs/temp/sbbsecho/678dc352.pkt
2025-01-20 14:30:26 Added PVT_TEST message from Clearing Houz (10:1/1) to packets for 1 links (exceptions: 1 seen)
2025-01-20 14:30:26 Deleting /opt/sbbs/fido/inbound/000a20bc.pkt (from line 6310)
2025-01-20 14:30:26 Imported: 1 msgs pvt_test <- PVT_TEST
2025-01-20 14:30:26 Duplicate: 1 detected in BBS_ADS
2025-01-20 14:30:26 Imported: 1 msgs total

2025-01-20 14:30:26 Finalizing outbound packet from 10:1/4 to 10:999/900: /opt/sbbs/temp/sbbsecho/678dc352.pkt
2025-01-20 14:30:26 Node (10:999/900) successfully locked via: ../fido/outbound.00a/03e70384.bsy
2025-01-20 14:30:26 Sending packet (/opt/sbbs/temp/sbbsecho/678dc352.pkt, 1.8KB) from 10:1/4 to 10:999/900
2025-01-20 14:30:26 Moving packet for 10:999/900: /opt/sbbs/temp/sbbsecho/678dc352.pkt to ../fido/outbound.00a/678dc352.pkt
2025-01-20 14:30:26 Deleting /opt/sbbs/temp/sbbsecho/678dc352.pkt (from line 3009)
2025-01-20 14:30:26 File (../fido/outbound.00a/678dc352.pkt, 1.8KB) for 10:999/900 added to BSO/FLO file: ../fido/outbound.00a/03e70384.clo
2025-01-20 14:30:26 Touching outgoing semfile: ../data/binkout.now
2025-01-20 14:30:26 Writing 14 areas to ../data/badareas.lst
2025-01-20 14:30:26 Deleting ../fido/outbound.00a/03e70384.bsy (from line 3169) 2025-01-20 14:30:26 Deleting /opt/sbbs/ctrl/sbbsecho.bsy (from line 3175) 2025-01-20 14:30:26 SBBSecho (PID 9135) exiting with error level 0, Packets(2 imported, 1 sent), EchoMail(1 imported, 0 exported)

I would have expected something from the logging you added right?


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

Re: imsg on incoming echomail
By: deon to Digital Man on Mon Jan 20 2025 03:03 pm

I would have expected something from the logging you added right?

Only if there was an echomail message successfully imported and it was addressed to you (or one of your other BBS users). I'll add some more debug-level log messages to sbbsecho so it's obvious when messages are imported and whom each was addressed to.
--
digital man (rob)

Synchronet "Real Fact" #46:
Synchronet External X/Y/ZMODEM protocol driver (SEXYZ) was introduced in 2005 Norco, CA WX: 46.5øF, 90.0% humidity, 0 mph NNW wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: imsg on incoming echomail
By: Digital Man to deon on Sun Jan 19 2025 10:32 pm

Re: imsg on incoming echomail
By: deon to Digital Man on Mon Jan 20 2025 03:03 pm

I would have expected something from the logging you added right?

Only if there was an echomail message successfully imported and it was addressed to you (or one of your other BBS users). I'll add some more debug-level log messages to sbbsecho so it's obvious when messages are imported and whom each was addressed to.

Okay, I've commited a change that adds more log messages around this area of question and a successfuly notification looks like this:

01/19/25 22:55:19 FIDOTEST: Imported message from RBB Test Robot (2:221/360) to Rob Swindell, subject: Re: Another test
01/19/25 22:55:19 FIDOTEST: Local message recipient (Rob Swindell): user #1 01/19/25 22:55:19 FIDOTEST: Successfully notified recipient (Digital Man #1) of echomail from RBB Test Robot

And if any of the reasons that a user would not be notified (failure to read user record, user doesn't have access) occur, there will be other/different log messages.
--
digital man (rob)

This Is Spinal Tap quote #16:
David St. Hubbins: I believe virtually everything I read...
Norco, CA WX: 46.2øF, 90.0% humidity, 1 mph ENE wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: imsg on incoming echomail
By: Digital Man to deon on Sun Jan 19 2025 11:00 pm

Howdy,

I would have expected something from the logging you added right?

Only if there was an echomail message successfully imported and it was addressed to you (or one of your other BBS users). I'll add some more debug-level log messages to sbbsecho so it's obvious when messages are imported and whom each was addressed to.

OK, updated.

2025-01-20 18:50:17 PVT_TEST: Imported message from Clearing Houz (10:1/1) to deon, subject: Test Reply
2025-01-20 18:50:17 PVT_TEST: Local message recipient (deon): user #1 2025-01-20 18:50:17 PVT_TEST: Successfully notified recipient (deon #1) of echomail from Clearing Houz
2025-01-20 18:50:17 Deleting /opt/sbbs/fido/inbound/000a214d.pkt (from line 6325)
2025-01-20 18:50:17 Imported: 1 msgs pvt_test <- PVT_TEST

Lets see what it looks like as time goes by...




...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

Re: imsg on incoming echomail
By: deon to Digital Man on Mon Jan 20 2025 06:53 pm

Howdy,

addressed to you (or one of your other BBS users). I'll add some more debug-level log messages to sbbsecho so it's obvious when messages are imported and whom each was addressed to.

OK, updated.

OK, got something:

2025-01-21 15:07:54 Adding PVT_TEST message from Clearing Houz (10:1/1) to packet for 10:999/900: /opt/sbbs/temp/sbbsecho/678f1d9a.pkt
2025-01-21 15:07:54 Added PVT_TEST message from Clearing Houz (10:1/1) to packets for 1 links (exceptions: 1 seen)
2025-01-21 15:07:54 PVT_TEST: Imported message from Clearing Houz (10:1/1) to deon, subject: Test Reply
2025-01-21 15:07:54 PVT_TEST: Local message recipient (deon): user #1

2025-01-21 15:07:54 PVT_TEST: User (deon #1) doesn't have read access to sub-board

2025-01-21 15:07:54 Deleting /opt/sbbs/fido/inbound/000a2338.pkt (from line 6325)
2025-01-21 15:07:54 Imported: 1 msgs pvt_test <- PVT_TEST

So sbbsecho thinks I dont have access to the sub board now - and no, I havent made any changes, havent run scfg/echocfg nor edited any of the config files.

-rw------- 1 root root 131 Jan 21 10:08 msgs/0001.last.msg
-rw------- 1 root root 71 Jan 20 21:54 msgs/0001.last.0.msg
-rw------- 1 root root 71 Jan 20 21:51 msgs/0001.last.1.msg

-rw-r--r-- 1 deon deon 30395 Jan 20 08:18 ctrl/sbbsecho.ini
-rw-r--r-- 1 deon deon 11398 Jan 10 14:06 ctrl/sbbs.ini
-rw-r--r-- 1 root root 147354 Jan 10 14:06 ctrl/msgs.ini


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

Re: imsg on incoming echomail
By: deon to Digital Man on Tue Jan 21 2025 03:20 pm

OK, got something:

2025-01-21 15:07:54 PVT_TEST: User (deon #1) doesn't have read access to sub-board

Okay, that's a good find. What are the access requirements for the message group that the echo is in and the access and reading requirements for the sub-board (in SCFG)?
--
digital man (rob)

Sling Blade quote #19:
Doyle: I can't so much as drink a damn glass of water around a midget
Norco, CA WX: 54.4øF, 13.0% humidity, 1 mph NE wind, 0.01 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: imsg on incoming echomail
By: Digital Man to deon on Mon Jan 20 2025 08:24 pm

Howdy,

Okay, that's a good find. What are the access requirements for the message group that the echo is in and the access and reading requirements for the sub-board (in SCFG)?

From msgs.ini:

[grp:0010:PVT]
description=PrivateNet
ars=PROT != IMAP AND PROT != IMAPS

[sub:0010:PVT:TEST]
description=Test Messages
ars=
read_ars=
post_ars=
operator_ars=
moderated_ars=
area_tag=PVT_TEST


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

Re: imsg on incoming echomail
By: deon to Digital Man on Tue Jan 21 2025 04:54 pm

Howdy,

Okay, that's a good find. What are the access requirements for the message group that the echo is in and the access and reading requirements for the sub-board (in SCFG)?

Oh, and its not just that sub:

2025-01-21 01:04:34 FSX_BBS: User (deon #1) doesn't have read access to sub-board
2025-01-21 14:24:04 FSX_GEN: User (deon #1) doesn't have read access to sub-board
2025-01-21 15:07:54 PVT_TEST: User (deon #1) doesn't have read access to sub-board

What will be common, is the ars for IMAP:
ars=PROT != IMAP AND PROT != IMAPS

But that might not be it. I did used to have "ars=PROT NOT IMAP" before (which did nothing at the time).


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

Re: imsg on incoming echomail
By: deon to Digital Man on Tue Jan 21 2025 04:54 pm

Re: imsg on incoming echomail
By: Digital Man to deon on Mon Jan 20 2025 08:24 pm

Howdy,

Okay, that's a good find. What are the access requirements for the message group that the echo is in and the access and reading requirements for the sub-board (in SCFG)?

From msgs.ini:

[grp:0010:PVT]
description=PrivateNet
ars=PROT != IMAP AND PROT != IMAPS

[sub:0010:PVT:TEST]
description=Test Messages
ars=
read_ars=
post_ars=
operator_ars=
moderated_ars=
area_tag=PVT_TEST

So at some point you're probably connecting with IMAP[S] which sets your user account protocol to IMAP[S] and then disqualifies your account from reading the "PVT" message group. Removing those access restrictions would resolve the issue. I'll look into making a service option to not change the user protocol (something you could enable for IMAP and IMAPS to prevent this situation).
--
digital man (rob)

Steven Wright quote #19:
I intend to live forever ... So far, so good.
Norco, CA WX: 54.3øF, 13.0% humidity, 6 mph NNE wind, 0.01 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: imsg on incoming echomail
By: deon to Digital Man on Tue Jan 21 2025 05:00 pm

What will be common, is the ars for IMAP:
ars=PROT != IMAP AND PROT != IMAPS

But that might not be it. I did used to have "ars=PROT NOT IMAP" before (which did nothing at the time).

No, I think that's definitely it.
--
digital man (rob)

Rush quote #50:
I've always been a big sponge. - Neil Peart
Norco, CA WX: 54.3øF, 13.0% humidity, 6 mph NNE wind, 0.01 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: imsg on incoming echomail
By: Digital Man to deon on Mon Jan 20 2025 11:04 pm

Howdy,

So at some point you're probably connecting with IMAP[S] which sets your user account protocol to IMAP[S] and then disqualifies your account from reading the "PVT" message group. Removing those access restrictions would resolve the issue. I'll look into making a service option to not change the user protocol (something you could enable for IMAP and IMAPS to prevent this situation).

So this should be easy to validate. I only have the IMAP connection on my mac mini which I actually dont use as much as my laptop (and so most of the time its asleep).

I think it must wake up every now and again and get mail, but if I quit mail, then there wont be any IMAP connection to SBBS...

That should proove if thats it...


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

Hey deon!

On Mon, Jan 20 2025 22:20:42 -0600, you wrote ..

So sbbsecho thinks I dont have access to the sub board now - and no, I havent made any changes, havent run scfg/echocfg nor edited any of the config files.

-rw------- 1 root root 131 Jan 21 10:08 msgs/0001.last.msg
-rw------- 1 root root 71 Jan 20 21:54 msgs/0001.last.0.msg
-rw------- 1 root root 71 Jan 20 21:51 msgs/0001.last.1.msg

-rw-r--r-- 1 deon deon 30395 Jan 20 08:18 ctrl/sbbsecho.ini
-rw-r--r-- 1 deon deon 11398 Jan 10 14:06 ctrl/sbbs.ini
-rw-r--r-- 1 root root 147354 Jan 10 14:06 ctrl/msgs.ini

Are permissions an issue here? Looks like your *.msg files are being created by 'root', and sbbsecho.ini is owned by 'deon'. I don't think sbbsecho.ini would be able to read/post these messages properly if they're owned by 'root'.

Regards,
Nick

... He who laughs last, thinks slowest.
---
þ Synchronet þ _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)

Re: Re: imsg on incoming echomail
By: Accession to deon on Tue Jan 21 2025 06:58 am

Howdy,

Are permissions an issue here? Looks like your *.msg files are being created by 'root', and sbbsecho.ini is owned by 'deon'. I don't think sbbsecho.ini would be able to read/post these messages properly if they're owned by 'root'.

No, my sync runs as root (inside a container), and I dont have selinux enabled.

But if it was a problem, (because it dropped privileges - which I dont have that set either), then I would expect the core issue to be consistently failing trying to update those files.


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

Re: Re: imsg on incoming echomail
By: deon to Accession on Wed Jan 22 2025 07:40 am

No, my sync runs as root (inside a container), and I dont have selinux enabled.

Even if it's in a container, I imagine it's probably not a good idea to run a public-facing server as root.

Nightfox

---
þ Synchronet þ Digital Distortion: digitaldistortionbbs.com

On 21 Jan 2025, Nightfox said the following...

Even if it's in a container, I imagine it's probably not a good idea to run a public-facing server as root.

not to poke sticks, but running things as root usually means the operator doesn't know how to fix other problems they were having ;)

--- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
* Origin: cold fusion - cfbbs.net - grand rapids, mi

deon wrote to Accession <=-

Re: Re: imsg on incoming echomail
By: Accession to deon on Tue Jan 21 2025 06:58 am

Are permissions an issue here? Looks like your *.msg files are being created by 'root', and sbbsecho.ini is owned by 'deon'. I don't think sbbsecho.ini would be able to read/post these messages properly if they're owned by 'root'.

No, my sync runs as root (inside a container), and I dont have selinux enabled.

But if it was a problem, (because it dropped privileges - which I dont have that set either), then I would expect the core issue to be consistently failing trying to update those files.

But...... why? Why run as root? Makes no sense, and is likely the
cause of the issue(s).



... White dwarf seeks red giant for binary relationship.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL

Re: Re: imsg on incoming echomail
By: Gamgee to deon on Tue Jan 21 2025 09:50 pm

But...... why? Why run as root? Makes no sense, and is likely the
cause of the issue(s).

We already identified the root (the "PROT" keyword in the access requirements to his message group excluded "IMAP") and provided a work-around. root or not was not an issue.
--
digital man (rob)

Rush quote #17:
Leave out fiction, the fact is this friction will only be worn by persistence Norco, CA WX: 54.3øF, 12.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Digital Man wrote to Gamgee <=-

Re: Re: imsg on incoming echomail
By: Gamgee to deon on Tue Jan 21 2025 09:50 pm

But...... why? Why run as root? Makes no sense, and is likely the
cause of the issue(s).

We already identified the root (the "PROT" keyword in the access requirements to his message group excluded "IMAP") and provided a work-around. root or not was not an issue.

Okay, that's fantastic. But really, I wanted to know the answer to my question there... Is it something I'm not aware of when running in a Docker/container that you have to be root? Just can't come up with any
good reason to be doing that.



... Gone crazy, be back later, please leave message.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL