• Sending to a SUB via email

    From Amessyroom@VERT/TL-QWK to All on Thursday, December 19, 2024 21:16:30
    Dec 19 21:10:34 vmi1943160 synchronet[1350579]: mail 0089 SEND !Delivery attempt #1 FAILED (127.0.0.1 replied with: "550 Insufficient access" instead of the expected reply: "250 ...") for message #4398 from Amessyroom to testlist@toolazy.synchro.net
    Dec 19 21:10:34 vmi1943160 synchronet[1350579]: mail 0089 SEND !Bouncing message back to Amessyroom
    Dec 19 21:10:34 vmi1943160 synchronet[1350579]: mail 0089 SEND !Delivery failure notification (message #4399) created for Amessyroom
    Dec 19 21:10:34 vmi1943160 synchronet[1350579]: mail 0090 SMTPS dbg 'Received TLS alert message: Close notify' (-24) popping data



    /home/sbbs/ctrl/alias.cfg has this entry
    testlistsub:LOCAL-TESTLIST

    LOCAL-TESTLIST being the Internal Code for the message area.

    When I try to sendmail to testlist@toolazy.synchro.net , why do I get
    this insufficient error. There are no access or posting restrictions on the message area (LOCAL) or the subboard (TESTLIST).
    ---
    Amessyroom
    toolazy.synchro.net:2323 (telnet)

    ---
    þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323
  • From Amessyroom@VERT/TL-QWK to All on Thursday, December 19, 2024 21:19:40
    Re: Sending to a SUB via email
    By: Amessyroom to All on Thu Dec 19 2024 09:16 pm

    /home/sbbs/ctrl/alias.cfg has this entry
    testlistsub:LOCAL-TESTLIST

    This was a paste error.

    testlist sub:LOCAL-TESTLIST

    there is white space between the two columns as expected
    ---
    Amessyroom
    toolazy.synchro.net:2323 (telnet)

    ---
    þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323
  • From Amessyroom@VERT/TL-QWK to All on Thursday, December 19, 2024 21:34:00
    Re: Sending to a SUB via email
    By: Amessyroom to All on Thu Dec 19 2024 09:16 pm

    Dec 19 21:10:34 vmi1943160 synchronet[1350579]: mail 0089 SEND !Delivery attempt #1 FAILED (127.0.0.1 replied with: "550 Insufficient access" instead of the expected reply: "250 ...") for message #4398 from Amessyroom to testlist@toolazy.synchro.net
    Dec 19 21:10:34 vmi1943160 synchronet[1350579]: mail 0089 SEND !Bouncing message back to Amessyroom Dec 19 21:10:34 vmi1943160 synchronet[1350579]: mail 0089 SEND !Delivery failure notification (message #4399) created for Amessyroom
    Dec 19 21:10:34 vmi1943160 synchronet[1350579]: mail 0090 SMTPS dbg 'Received TLS alert message: Close notify' (-24) popping data



    /home/sbbs/ctrl/alias.cfg has this entry
    testlist sub:LOCAL-TESTLIST

    -- there is white space between alias and sub board definition.

    LOCAL-TESTLIST being the Internal Code for the message area.

    When I try to sendmail to testlist@toolazy.synchro.net , why do I get this insufficient error. There are no access or posting restrictions on the message area (LOCAL) or the subboard (TESTLIST).

    Here is my mailauth config
    [MailAuth]
    Command=mailauth.js
    AccessRequirements=user equal 0 or guest
    Disabled=false

    So the message is being sent via netmail from sysop user, so assume user would be 0. So not sure why this determines it is insufficient. Unless it is
    evaulating from a smtp / host perspective? Not clear to me.
    ---
    Amessyroom
    toolazy.synchro.net:2323 (telnet)

    ---
    þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323
  • From Amessyroom@VERT/TL-QWK to All on Thursday, December 19, 2024 22:11:55
    Re: Sending to a SUB via email
    By: Amessyroom to All on Thu Dec 19 2024 09:34 pm

    What is reason 13 ?

    !Amessyroom@toolazy.synchro.net (user #0) cannot post on testlist (reason: 13) LOL

    Maybe this will shed some light on failing tests.
    ---
    Amessyroom
    toolazy.synchro.net:2323 (telnet)

    ---
    þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323
  • From Digital Man@VERT to Amessyroom on Thursday, December 19, 2024 23:26:08
    Re: Sending to a SUB via email
    By: Amessyroom to All on Thu Dec 19 2024 09:16 pm

    Dec 19 21:10:34 vmi1943160 synchronet[1350579]: mail 0089 SEND !Delivery attempt #1 FAILED (127.0.0.1 replied with: "550 Insufficient access" instead of the expected reply: "250 ...") for message #4398 from Amessyroom to testlist@toolazy.synchro.ne

    Look at the log of the mail server that rejected the post for more details. The log message would be notice-level similar to the following:
    "!username (user #x) cannot post on sub (reason: why)"

    /home/sbbs/ctrl/alias.cfg has this entry
    testlistsub:LOCAL-TESTLIST

    Hopefully you have a space before "sub:" ?

    When I try to sendmail to testlist@toolazy.synchro.net , why do I get
    this insufficient error. There are no access or posting restrictions on the message area (LOCAL) or the subboard (TESTLIST).

    Look at the log.
    --
    digital man (rob)

    This Is Spinal Tap quote #28:
    We've got Armadillos in our trousers. It's really quite frightening.
    Norco, CA WX: 61.3øF, 38.0% humidity, 1 mph ENE wind, 0.00 inches rain/24hrs ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to Amessyroom on Thursday, December 19, 2024 23:30:15
    Re: Insufficent access - reason: 13
    By: Amessyroom to All on Thu Dec 19 2024 10:11 pm

    Re: Sending to a SUB via email
    By: Amessyroom to All on Thu Dec 19 2024 09:34 pm

    What is reason 13 ?

    !Amessyroom@toolazy.synchro.net (user #0) cannot post on testlist (reason: 13) LOL

    Maybe this will shed some light on failing tests.

    Reason 13 correlates with text.dat string 13: TooManyPostsToday

    So my guess, you have SCFG->Security->Level 0->Posts per day set to 0 (the default). This configuration tip is actually covered here:
    https://wiki.synchro.net/module:listgate#configuration
    --
    digital man (rob)

    Rush quote #60:
    Plays fast forward just long as he can, he won't need a bed, he's a digital man Norco, CA WX: 61.3øF, 38.0% humidity, 1 mph ENE wind, 0.00 inches rain/24hrs ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Errol Casey@VERT to Digital Man on Friday, December 20, 2024 08:12:14
    Re: Insufficent access - reason: 13
    By: Digital Man to Amessyroom on Thu Dec 19 2024 11:30 pm

    Reason 13 correlates with text.dat string 13: TooManyPostsToday

    So my guess, you have SCFG->Security->Level 0->Posts per day set to 0 (the default). This configuration tip is actually covered here: https://wiki.synchro.net/module:listgate#configuration --

    Now getting 120
    !Amessyroom@toolazy.synchro.net (user #0) cannot post on testlist (reason: 120) ---
    Amessyroom
    toolazy.synchro.net:2323 (telnet)
    --- SBBSecho 3.23-Linux
    * Origin: Too Lazy BBS - toolazy.synchro.net:2323 (1:3634/58)
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From nelgin@VERT/EOTLBBS to Errol Casey on Friday, December 20, 2024 10:41:55
    Re: Insufficent access - reason: 120
    By: Errol Casey to Digital Man on Fri Dec 20 2024 08:12:14

    Now getting 120
    !Amessyroom@toolazy.synchro.net (user #0) cannot post on testlist (reason:

    Just look up what line 120 is in text.dat

    "\r\nYou can't post on this sub.\r\n" 120 CantPostOnSub

    ---
    þ Synchronet þ End Of The Line BBS - endofthelinebbs.com
  • From Digital Man@VERT to Errol Casey on Friday, December 20, 2024 12:19:42
    Re: Insufficent access - reason: 120
    By: Errol Casey to Digital Man on Fri Dec 20 2024 08:12 am

    Re: Insufficent access - reason: 13
    By: Digital Man to Amessyroom on Thu Dec 19 2024 11:30 pm

    Reason 13 correlates with text.dat string 13: TooManyPostsToday

    So my guess, you have SCFG->Security->Level 0->Posts per day set to 0 (the default). This configuration tip is actually covered here: https://wiki.synchro.net/module:listgate#configuration --

    Now getting 120
    !Amessyroom@toolazy.synchro.net (user #0) cannot post on testlist (reason: 120)

    String 120 in ctrl/text.dat is: CantPostOnSub

    This indicates that the user (User #0 in this case) doesn't have permission to access or post on the sub-board based on the configuration in SCFG->Message Areas.
    --
    digital man (rob)

    Steven Wright quote #18:
    Hard work pays off in the future; laziness pays off now.
    Norco, CA WX: 72.2øF, 24.0% humidity, 2 mph SSW wind, 0.00 inches rain/24hrs ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Amessyroom@VERT/TL-QWK to nelgin on Friday, December 20, 2024 15:01:42
    Re: Insufficent access - reason: 120
    By: nelgin to Errol Casey on Fri Dec 20 2024 10:41 am

    Re: Insufficent access - reason: 120
    By: Errol Casey to Digital Man on Fri Dec 20 2024 08:12:14

    Now getting 120
    !Amessyroom@toolazy.synchro.net (user #0) cannot post on testlist (reason:

    Really doesn't explain why. The error says cannot post. So I knew that.

    But cannot find data structure that explains what the codes mean; so will
    have to wait til Digital Man or other person can decode the error code.

    Thanks for looking.
    ---
    Amessyroom
    toolazy.synchro.net:2323 (telnet)

    ---
    þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323
  • From Amessyroom@VERT/TL-QWK to nelgin on Friday, December 20, 2024 15:28:00
    Re: Insufficent access - reason: 120
    By: nelgin to Errol Casey on Fri Dec 20 2024 10:41 am

    Sorry nelgin.

    I guess I should have stated I was trying to see why
    I'm being denied the right to post via an incoming email.

    !can_user_post(&scfg,subnum,&relay_user,&client,&reason)

    I have found the function, but still haven't been able to
    figure out what is triggering this to return false.

    Thanks for trying to help.
    ---
    Amessyroom
    toolazy.synchro.net:2323 (telnet)

    ---
    þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323
  • From Amessyroom@VERT/TL-QWK to Digital Man on Friday, December 20, 2024 16:23:55
    Re: Insufficent access - reason: 120
    By: Digital Man to Errol Casey on Fri Dec 20 2024 12:19 pm

    Re: Insufficent access - reason: 120
    By: Errol Casey to Digital Man on Fri Dec 20 2024 08:12 am

    Re: Insufficent access - reason: 13
    By: Digital Man to Amessyroom on Thu Dec 19 2024 11:30 pm

    Reason 13 correlates with text.dat string 13: TooManyPostsToday

    So my guess, you have SCFG->Security->Level 0->Posts per day set to 0
    (the default). This configuration tip is actually covered here:
    https://wiki.synchro.net/module:listgate#configuration --

    Now getting 120
    !Amessyroom@toolazy.synchro.net (user #0) cannot post on testlist (reason:
    120)

    String 120 in ctrl/text.dat is: CantPostOnSub

    This indicates that the user (User #0 in this case) doesn't have permission to access or post on the sub-board based on the configuration in SCFG->Message Areas.
    --
    digital man (rob)


    I see no restrictions . I'll go through menu and "clear" 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.
    ---
    Amessyroom
    toolazy.synchro.net:2323 (telnet)

    ---
    þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323
  • From Digital Man@VERT to Amessyroom on Friday, December 20, 2024 18:32:09
    Re: Insufficent access - reason: 120
    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

    Re: Insufficent access - reason: 120
    By: Errol Casey to Digital Man on Fri Dec 20 2024 08:12 am

    Re: Insufficent access - reason: 13
    By: Digital Man to Amessyroom on Thu Dec 19 2024 11:30 pm

    Reason 13 correlates with text.dat string 13: TooManyPostsToday

    So my guess, you have SCFG->Security->Level 0->Posts per day set to 0
    (the default). This configuration tip is actually covered here:
    https://wiki.synchro.net/module:listgate#configuration --

    Now getting 120
    !Amessyroom@toolazy.synchro.net (user #0) cannot post on testlist (reason:
    120)

    String 120 in ctrl/text.dat is: CantPostOnSub

    This indicates that the user (User #0 in this case) doesn't have permission to access or post on the sub-board based on the configuration in SCFG->Message Areas.

    I see no restrictions . I'll go through menu and "clear" restrictions.

    Restrictions are aplied to users (in one of the user editors). You 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.

    The SCFG settings you want to look at are "Access Requirements" and "Posting Requirements" for SCFG->Message Areas, specifically the Message Group and Sub-board in which you're trying to post via SMTP.
    --
    digital man (rob)

    Steven Wright quote #28:
    The hardness of the butter is proportional to the softness of the bread.
    Norco, CA WX: 60.5øF, 56.0% humidity, 1 mph WNW wind, 0.00 inches rain/24hrs ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From MRO@VERT/BBSESINF to Amessyroom on Friday, December 20, 2024 20:55:06
    Re: Insufficent access - reason: 120
    By: Amessyroom to nelgin on Fri Dec 20 2024 03:01 pm


    Really doesn't explain why. The error says cannot post. So I knew that.

    But cannot find data structure that explains what the codes mean; so will have to wait til Digital Man or other person can decode the error code.

    Thanks for looking.

    When you can't post you need to look at your security setup.
    it's misconfigured most likely. just like everyone is saying.

    it's nothing serious and you shouldn't wait around. When you encounter an error open up the docs and look and then retrace and recheck the steps you made.

    I think it's weird to giver an error code in that way, i'd rather it can can not post.



    ---
    þ Synchronet þ ::: BBSES.info - free BBS services :::
  • From Amessyroom@VERT/TL-QWK to Digital Man on Saturday, December 21, 2024 09:56:14
    Re: Insufficent access - reason: 120
    By: Digital Man to Amessyroom on Fri Dec 20 2024 06:32 pm

    Re: Insufficent access - reason: 120
    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

    Restrictions are aplied to users (in one of the user editors). You 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.

    The SCFG settings you want to look at are "Access Requirements" and "Posting Requirements" for SCFG->Message Areas, specifically the Message Group and Sub-board in which you're trying to post via SMTP.
    --

    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 ?

    I created a second one in the same new message area, and it reports that it cannot find the subboard. internal code NEW_ is defined for message area 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

    But when listserver.js is ran it does see the list as SUBLIST which is how
    it is named in the ini file.


    [sublist]
    sub = new_sublist
    readonly = false
    disabled = false
    closed = false
    subject_mod = true

    So trying to figure out why it cannot see the new suboard and use it a a list. ---
    Amessyroom
    toolazy.synchro.net:2323 (telnet)





    ...What's the speed of dark?

    ---
    þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323
  • From Amessyroom@VERT/TL-QWK to MRO on Saturday, December 21, 2024 10:03:27
    Re: Insufficent access - reason: 120
    By: MRO to Amessyroom on Fri Dec 20 2024 08:55 pm

    Re: Insufficent access - reason: 120
    By: Amessyroom to nelgin on Fri Dec 20 2024 03:01 pm
    When you can't post you need to look at your security setup. it's misconfigured most likely. just like everyone is saying.

    it's nothing serious and you shouldn't wait around. When you encounter an error open up the docs and look and then retrace and recheck the steps you made.


    I have looked at the settings, but could not see a problem. I recreated a new message area/subboard and it worked (for one list), tried a second list and it says it is unknown. (see previous message).

    I just find it frustrating having to go through menus, to search for something and not see anything "set". As I asked in previous post, would be nice to have a tool to list settings in a report format possibly via a cli tool rather than having to step thorugh menus in scfg.

    Maybe I'm overlooking an existing tool. I obviously overlooked some of the setup for the listserver. Love the wiki, but it seems it is easy to read through one page; and not get all the knowledge needed. Maybe someone needs to add an option to display page with all links; so you can read them one after another.


    ...Make no little plans. They have no Magic to stir Men's blood.
    ---
    Amessyroom
    toolazy.synchro.net:2323 (telnet)

    ---
    þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323
  • From Digital Man@VERT to Amessyroom on Sunday, December 22, 2024 23:02:23
    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

    Re: Insufficent access - reason: 120
    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

    Restrictions are aplied to users (in one of the user editors). You 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.

    The SCFG settings you want to look at are "Access Requirements" and "Posting Requirements" for SCFG->Message Areas, specifically the Message Group and Sub-board in which you're trying to post via SMTP.
    --

    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 ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net