TZUTC: -0700
MSGID: 54864.sync@1:103/705 2d29651a
REPLY: 73958.sync@723:320/1 2d295041
PID: Synchronet 3.21a-Linux master/7acaccaf1 Sep 08 2025 GCC 12.2.0
TID: SBBSecho 3.29-Linux master/7acaccaf1 Sep 08 2025 GCC 12.2.0
COLS: 80
BBSID: VERT
CHRS: CP437 2
FORMAT: flowed
NOTE: FSEditor.js v1.105
  Re: sbbsecho issue
  By: Dumas Walker to DIGITAL MAN on Thu Sep 11 2025 11:31 am

 > So it will show up in the sbbs console, and the syslog, if set to
 > "informational"?

Correct.

 > > SBBSecho is behaving exactly as designed and documented, it appears to me.
 >
 > That might be but if sbbsecho is getting a "lock" on a non-existant file
 > (which it should be able to tell because it cannot find the proper time to
 > display - it displays ??:??), I would strongly suggest the message in that
 > case is more than just "informational"...  there *is* something wrong that
 > *will* require intervention if you want mail to keep flowing.

The "Node (x) external locked ..." messages is actually NOTICE (not INFO)
level already. But you had your Log Level set to WARNING.

The "Giving up after ..." log message is a WARNING level already, so that
would be found in your sbbsecho.log file with how you had it configured.
-- 
                                            digital man (rob)

Steven Wright quote #22:
What happens if you get scared half to death twice?
Norco, CA WX: 78.7øF, 53.0% humidity, 7 mph WNW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.29-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 10/0 1 102/401 103/1 17 705 105/81 106/201 124/5016 128/187
SEEN-BY: 129/14 153/7715 154/110 218/0 1 215 601 610 700 840 860 880
SEEN-BY: 226/30 227/114 229/110 206 317 400 426 428 470 700 705 266/512
SEEN-BY: 280/464 291/111 301/1 320/219 322/757 342/200 396/45 460/58
SEEN-BY: 633/280 712/848 902/26 5075/35
PATH: 103/705 218/700 229/426