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

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