1. Forum
  2. USENET
  3. alt.bbs.synchronet

  • Tickit processing problem

    From RickV@rickv@1:154/110.remove-sqd-this to All on Fri Jan 2 07:11:58 2026
    From Newsgroup: alt.bbs.synchronet

    Hello everybody!

    For some reason I'm getting this error.

    2026-01-02 06:08:59 TICKIT Running native timed event: ?tickit.js -force-replace
    2026-01-02 06:08:59 TICKIT TickIT 2.0
    2026-01-02 06:08:59 TICKIT Parsing /sbbs/fido/inbound/syl2uti9.tic
    2026-01-02 06:08:59 TICKIT Configured TicFilePwd is empty, but TIC file has a password, node: 86:300/1
    2026-01-02 06:08:59 TICKIT Configured TicFilePwd is empty, but TIC file has a password, node: 86:300/1@nixnet
    2026-01-02 06:08:59 TICKIT No password matched for sender 86:300/1 or 86:300/1@nixnet.
    2026-01-02 06:08:59 TICKIT Please check the defined password for this sender.

    I'm not sure where this "TicFilePwd" file is, but my uplink node has the right password defined, so why would it not process correctly?

    Thanks,
    RickV


    --- SBBSecho 3.33-Linux
    * Origin: Live Wire BBS [livewirebbs.com:1025] (1:154/110)
    --- Synchronet 3.21a-Linux NewsLink 1.2
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Digital Man@digital.man@vert.synchro.net.remove-dx-this to RickV on Fri Jan 2 13:49:39 2026
    From Newsgroup: alt.bbs.synchronet

    To: RickV
    Re: Tickit processing problem
    By: RickV to All on Fri Jan 02 2026 07:11 am

    Hello everybody!

    For some reason I'm getting this error.

    2026-01-02 06:08:59 TICKIT Running native timed event: ?tickit.js -force-replace
    2026-01-02 06:08:59 TICKIT TickIT 2.0
    2026-01-02 06:08:59 TICKIT Parsing /sbbs/fido/inbound/syl2uti9.tic 2026-01-02 06:08:59 TICKIT Configured TicFilePwd is empty, but TIC file has a password, node: 86:300/1
    2026-01-02 06:08:59 TICKIT Configured TicFilePwd is empty, but TIC file has a password, node: 86:300/1@nixnet
    2026-01-02 06:08:59 TICKIT No password matched for sender 86:300/1 or 86:300/1@nixnet.
    2026-01-02 06:08:59 TICKIT Please check the defined password for this sender.

    I'm not sure where this "TicFilePwd" file is, but my uplink node has the right password defined, so why would it not process correctly?

    TicFilePwd is configured in sbbsecho.ini, per linked node.
    --
    digital man (rob)

    Rush quote #82:
    The clouds prepare for battle in the dark and brooding silence
    Norco, CA WX: 62.6øF, 90.0% humidity, 0 mph WNW wind, 0.02 inches rain/24hrs --- Synchronet 3.21a-Linux NewsLink 1.2
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Digital Man@digital.man@vert.synchro.net.remove-afv-this to RickV on Fri Jan 2 13:51:42 2026
    From Newsgroup: alt.bbs.synchronet

    To: RickV
    Re: Tickit processing problem
    By: Digital Man to RickV on Fri Jan 02 2026 01:49 pm

    TicFilePwd is configured in sbbsecho.ini, per linked node.

    and configurable via echocfg in Linked Nodes-><node>->TIC File Password.
    --
    digital man (rob)

    Sling Blade quote #1:
    Karl: I've killed Doyle with a lawn mower blade. Yes, I'm right sure of it. Norco, CA WX: 62.6øF, 90.0% humidity, 0 mph WNW wind, 0.02 inches rain/24hrs --- Synchronet 3.21a-Linux NewsLink 1.2
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From RickV@rickv@1:154/110.remove-6tw-this to Digital Man on Sat Jan 3 07:53:41 2026
    From Newsgroup: alt.bbs.synchronet

    To: Digital Man

    Hello Digital!

    21 Feb 70 23:36, you wrote to me:

    Re: Tickit processing problem
    By: Digital Man to RickV on Fri Jan 02 2026 01:49 pm

    TicFilePwd is configured in sbbsecho.ini, per linked node.

    and configurable via echocfg in Linked Nodes-><node>->TIC File
    Password.
    --
    digital man (rob)

    --- SBBSecho 3.34-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

    I found it. It did ring a bell with me. So in my sbbsecho.ini I had my different fido nodes defined, the one giving me the problem also had a @fsxnet after it. I removed that and it worked fined.

    Thanks,
    RickV


    --- SBBSecho 3.33-Linux
    * Origin: Live Wire BBS [livewirebbs.com:1025] (1:154/110)
    --- Synchronet 3.21b-Linux NewsLink 1.2
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    --- Synchronet 3.21a-Linux NewsLink 1.2