1. Forum
  2. FidoNET
  3. FIDOTEST

  • Tin jamnntpd test

    From Sean Rima@2:263/1.1 to All on Monday, February 03, 2025 21:53:38
    Testing tin with smapinntpd

    Sean

    --- tin/2.6.4-20241224 ("Helmsdale") (Darwin/20.6.0 (x86_64))
    * Origin: SmapiNNTPd/Linux 1.1 (2:263/1.1)
  • From RBB Test Robot@2:221/360 to Sean Rima on Monday, February 03, 2025 23:57:04
    03 Feb 25 21:53:38 Sean Rima (2:263/1.1) wrote:

    ==== begin of the message ====
    @MSGID: 2:263/1.1 67a13ada
    @REPLYADDR [email protected]
    @PID: SmapiNNTPd/Linux 1.1
    @TID: CrashMail II/Linux 1.5.1
    Testing tin with smapinntpd

    Sean

    -+- tin/2.6.4-20241224 ("Helmsdale") (Darwin/20.6.0 (x86_64))
    + Origin: SmapiNNTPd/Linux 1.1 (2:263/1.1)
    SEEN+BY: 1/120 18/0 19/10 116/116 123/0 25 180 755 3001 3002 134/100 135/115 SEEN+BY: 153/135 143 148 149 151 757 7083 7715 154/10 218/840 220/6 221/1 6 SEEN+BY: 221/360 222/2 240/1120 250/1 263/1 275/1000 280/464 301/1 335/364 SEEN+BY: 341/66 234 460/58 712/1321 3634/0 12 24 27 56 57 58 60 119 5020/1042 @PATH: 263/1 222/2 3634/12 153/757 221/6
    ==== end of the message ====

    ---
    * Origin: RBB Test Robot @ FIDOTEST (2:221/360)
  • From Jay Harris@1:229/664 to Sean Rima on Monday, February 03, 2025 17:41:44
    On 03 Feb 2025, Sean Rima said the following...

    @MSGID: 2:263/1.1 67a13ada
    @REPLYADDR [email protected]
    @PID: SmapiNNTPd/Linux 1.1
    @TID: CrashMail II/Linux 1.5.1
    @PATH: 263/1 222/2 3634/12 153/757 280/464 460/58 229/426
    Testing tin with smapinntpd

    Sean

    --- tin/2.6.4-20241224 ("Helmsdale") (Darwin/20.6.0 (x86_64))
    * Origin: SmapiNNTPd/Linux 1.1 (2:263/1.1)

    Got you here.


    Jay

    ... I'm glad I know sign language. It's pretty handy

    --- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
    * Origin: Northern Realms (1:229/664)
  • From Sean Rima@2:263/1.1 to Jay Harris on Monday, February 03, 2025 22:59:00
    1:229/664 wrote:
    @MSGID: 2:263/1.1 67a13ada
    @REPLYADDR [email protected]
    @PID: SmapiNNTPd/Linux 1.1
    @TID: CrashMail II/Linux 1.5.1
    @PATH: 263/1 222/2 3634/12 153/757 280/464 460/58 229/426
    Testing tin with smapinntpd

    Sean

    --- tin/2.6.4-20241224 ("Helmsdale") (Darwin/20.6.0 (x86_64))
    * Origin: SmapiNNTPd/Linux 1.1 (2:263/1.1)

    Got you here.



    Thanks Jay

    Sean

    --- tin/2.6.4-20241224 ("Helmsdale") (Darwin/20.6.0 (x86_64))
    * Origin: SmapiNNTPd/Linux 1.1 (2:263/1.1)
  • From Wilfred van Velzen@2:280/464 to Sean Rima on Tuesday, February 04, 2025 11:39:19
    Hi Sean,

    On 2025-02-03 21:53:38, you wrote to All:

    @MSGID: 2:263/1.1 67a13ada
    @PID: SmapiNNTPd/Linux 1.1
    @REPLYADDR [email protected]
    @TID: CrashMail II/Linux 1.5.1

    There is no TZUTC kludge.

    And also no CHRS kludge, but you don't need it in this case because your message has only ascii chars.

    Testing tin with smapinntpd

    Sean

    --- tin/2.6.4-20241224 ("Helmsdale") (Darwin/20.6.0 (x86_64))
    * Origin: SmapiNNTPd/Linux 1.1 (2:263/1.1)
    SEEN-BY: 1/120 18/0 103/705 116/116 123/0 25 180 755 3001 3002 124/5016 SEEN-BY: 134/100 135/115 153/135 143 148 149 151 757 7083 7715 154/10 SEEN-BY: 154/30 203/0 220/6 221/0 6 222/2 240/1120 5832 250/1 263/1 SEEN-BY: 275/1000 280/464 5003 5006 5555 292/854 8125 301/1 310/31 341/66 SEEN-BY: 341/234 396/45 423/120 460/58 467/888 633/280 712/848 1321 SEEN-BY: 770/1 3634/0 12 24 27 56 57 58 60 119 5020/400
    @PATH: 263/1 222/2 3634/12 153/757 280/464

    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Sean Rima@2:263/1 to Wilfred van Velzen on Tuesday, February 04, 2025 13:27:08
    Hello Wilfred!

    04 Feb 25 11:39, you wrote to me:


    @MSGID: 2:263/1.1 67a13ada
    @PID: SmapiNNTPd/Linux 1.1
    @REPLYADDR [email protected]
    @TID: CrashMail II/Linux 1.5.1

    There is no TZUTC kludge.

    Is that a setting in smapinntpd?

    And also no CHRS kludge, but you don't need it in this case because
    your message has only ascii chars.

    I had the -nochr in, removed it and will test later

    Testing tin with smapinntpd

    Sean

    --- tin/2.6.4-20241224 ("Helmsdale") (Darwin/20.6.0 (x86_64))
    * Origin: SmapiNNTPd/Linux 1.1 (2:263/1.1)
    SEEN-BY: 1/120 18/0 103/705 116/116 123/0 25 180 755 3001 3002
    124/5016
    SEEN-BY: 134/100 135/115 153/135 143 148 149 151 757 7083 7715
    154/10
    SEEN-BY: 154/30 203/0 220/6 221/0 6 222/2 240/1120 5832 250/1
    263/1
    SEEN-BY: 275/1000 280/464 5003 5006 5555 292/854 8125 301/1
    310/31 341/66
    SEEN-BY: 341/234 396/45 423/120 460/58 467/888 633/280 712/848
    1321
    SEEN-BY: 770/1 3634/0 12 24 27 56 57 58 60 119 5020/400
    @PATH: 263/1 222/2 3634/12 153/757 280/464

    Bye, Wilfred.

    Thanks

    Sean


    ---
    * Origin: Yet another forgotten area! (2:263/1)
  • From Wilfred van Velzen@2:280/464 to Sean Rima on Tuesday, February 04, 2025 15:26:57
    Hi Sean,

    On 2025-02-04 13:27:08, you wrote to me:

    @MSGID: 2:263/1.1 67a13ada
    @PID: SmapiNNTPd/Linux 1.1
    @REPLYADDR [email protected]
    @TID: CrashMail II/Linux 1.5.1

    There is no TZUTC kludge.

    Is that a setting in smapinntpd?

    I have no clue about how smapinntpd can be configured. ;-)

    And also no CHRS kludge, but you don't need it in this case because
    your message has only ascii chars.

    I had the -nochr in, removed it and will test later

    OK, we'll see...


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Sean Rima@2:263/1 to Wilfred van Velzen on Tuesday, February 04, 2025 16:46:37
    Hello Wilfred!

    04 Feb 25 15:26, you wrote to me:

    Hi Sean,

    On 2025-02-04 13:27:08, you wrote to me:

    @MSGID: 2:263/1.1 67a13ada
    @PID: SmapiNNTPd/Linux 1.1
    @REPLYADDR [email protected]
    @TID: CrashMail II/Linux 1.5.1

    There is no TZUTC kludge.

    Is that a setting in smapinntpd?

    I have no clue about how smapinntpd can be configured. ;-)

    Ah ok :)

    And also no CHRS kludge, but you don't need it in this case
    because your message has only ascii chars.

    I had the -nochr in, removed it and will test later

    OK, we'll see...

    Will do one now

    Sean


    ---
    * Origin: Yet another forgotten area! (2:263/1)