TZUTC: -0800   
   MSGID: 53303.sync@1:103/705 2bcd4036   
   REPLY: 53296.sync@1:103/705 2bcce8b6   
   PID: Synchronet 3.20a-Linux master/445394f9f Dec 20 2024 GCC 12.2.0   
   TID: SBBSecho 3.23-Linux master/445394f9f Dec 20 2024 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.105   
     Re: Insufficent access - reason: 120   
     By: Amessyroom to Digital Man on Sat Dec 21 2024 09:56 am   
      
    >   Re: Insufficent access - reason: 120   
    >   By: Digital Man to Amessyroom on Fri Dec 20 2024 06:32 pm   
    >   
    >  DM> Re: Insufficent access - reason: 120   
    >  DM> By: Amessyroom to Digital Man on Fri Dec 20 2024 04:23 pm   
    >   
    >  >> Re: Insufficent access - reason: 120 By: Digital Man to Errol Casey on   
    > Fri   
    >  >> Dec 20 2024 12:19 pm   
    >   
    >  DM> Restrictions are aplied to users (in one of the user editors). You   
    >  DM> won't have a user #0, so there's way they could have any restrictions.   
    >   
    >  >> Is there a restriciton that should be set to allow unauthenticated smtp   
    >  >> messages to be posted; I assume that was fixed with the post/day setting   
    >  >> which I tuned and got rid of the error 13 message.   
    >   
    >  DM> The SCFG settings you want to look at are "Access Requirements" and   
    >  DM> "Posting Requirements" for SCFG->Message Areas, specifically the   
    >  DM> Message Group and Sub-board in which you're trying to post via SMTP.   
    >  DM> --   
    >   
    > I walked through the access requirement menus without finding anything. I   
    > created a new message area and subboard and got it to work.   
    >   
    > Is there any tool that can list settings on message bases, other than   
    > walking through menus in scfg ?  like a cli tool to just list settings ?   
      
   Yes, https://wiki.synchro.net/module:exportcfg   
      
    > I created a second one in the same new message area, and it reports that it   
    > cannot find the subboard.   
      
   Has the server recycled (reloaded the configuration files) since you added the   
   new sub-board?   
      
    > internal code NEW_ is defined for message area   
      
   "message group"   
      
    > and subboard was EXTERNALSUB, hence I was using NEW_EXTERNALSUB and have not   
    > been able to get it to accept it.   
    >   
    > Renamed subboard to NEW_SUBLIST   
    >   
    > Dec 21 01:17:23 vmi1943160 synchronet[1391474]: mail 0157 SMTPS [127.0.0.1]   
    > !UNKNOWN SUB-BOARD: NEW_sublist   
      
   Did the mail server reyccle (reload config files) since you added that   
   sub-board?   
      
    > But when listserver.js is ran it does see the list as SUBLIST which is how   
    > it is named in the ini file.   
      
   listserver.js is typically run in the event thread of the Terminal Server.   
   It's possible that the terminal server had recycled, but the mail server had   
   not. Check the logs to find out why.   
      
    > So trying to figure out why it cannot see the new suboard and use it a a   
    > list. ---   
      
   The servers normally automatically recycle when they're not in use and there's   
   a detected configuration change. There are exceptions that can prevent that   
   from happening, but there are logged warnings for those exceptions that you   
   should be able to find in your server log output if it's that the case.   
   --    
                                               digital man (rob)   
      
   Synchronet/BBS Terminology Definition #58:   
   NUP = New User Password   
   Norco, CA WX: 69.7øF, 33.0% humidity, 10 mph WSW wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.23-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 153/757 7715 154/10   
   SEEN-BY: 154/30 203/0 218/700 221/0 226/30 227/114 229/110 114 206   
   SEEN-BY: 229/317 400 426 428 470 550 700 705 240/1120 5832 266/512   
   SEEN-BY: 280/464 5003 5006 282/1038 291/111 292/8125 301/1 310/31   
   SEEN-BY: 320/219 322/757 341/66 234 342/200 396/45 423/120 460/58   
   SEEN-BY: 460/256 1124 467/888 633/280 712/848 770/1 902/26 5020/400   
   SEEN-BY: 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426