@MSGID: 2:263/1.1 67a13ada
@REPLYADDR sean@nobody.knows
@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)
@MSGID: 2:263/1.1 67a13ada
@REPLYADDR sean@nobody.knows
@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.
@MSGID: 2:263/1.1 67a13ada
@PID: SmapiNNTPd/Linux 1.1
@REPLYADDR sean@nobody.knows
@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.
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 sean@nobody.knows
@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...
@MSGID: 2:263/1.1 67a13ada
@PID: SmapiNNTPd/Linux 1.1
@REPLYADDR sean@nobody.knows
@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 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
@MSGID: 2:263/1.1 67a13ada
@PID: SmapiNNTPd/Linux 1.1
@REPLYADDR sean@nobody.knows
@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
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 102 |
Nodes: | 16 (0 / 16) |
Uptime: | 01:49:10 |
Calls: | 5,869 |
Files: | 8,496 |
D/L today: |
242 files (39,888K bytes) |
Messages: | 344,352 |