@TID: Mystic BBS 1.12 A33
@MSGID: 4:801/188 5a1a88b2
@REPLYADDR fcbessa@gmail.com
@PID: JamNNTPd 20161111
@CHRS: IBMPC 2
@TZUTC: -0200
Hello,
Just testing this NNTP client.
--
Flavio Bessa <fcbessa@gmail.com>
--- Sylpheed 3.4.1 (GTK+ 2.24.21; x86_64-apple-darwin10.8.0)
* Origin: JAMNNTPD@Saturn's Orbit BBS - Rio de Janeiro, Brasil (4:801/188)
SEEN-BY: 15/0 19/36 34/999 90/1 116/18 120/302 331 123/140 153/7715 218/700
SEEN-BY: 220/60 222/2 230/150 240/1120 250/1 261/38 100 1466 266/404
512
SEEN-BY: 267/155 275/100 280/1027 282/1031 1056 291/1 292/908 320/119
219
SEEN-BY: 340/400 342/13 393/68 396/45 712/848 801/161 189 2320/100
3634/12
SEEN-BY: 5020/1042
@PATH: 801/188 189 261/38
@TID: Mystic BBS 1.12 A33
@MSGID: 4:801/188 5a1a88b2
@REPLYADDR fcbessa@gmail.com
@PID: JamNNTPd 20161111
@CHRS: IBMPC 2
@TZUTC: -0200
Hello,
Just testing this NNTP client.
--
Flavio Bessa <fcbessa@gmail.com>
___ Sylpheed 3.4.1 (GTK+ 2.24.21; x86_64-apple-darwin10.8.0) *
Origin: JAMNNTPD@Saturn's Orbit BBS - Rio de Janeiro, Brasil
(4:801/188)
@ATH: 801/188 189 261/38 2320/100 280/464 229/426 3828/7
Hello Flavio,
+ 22:17 [2652] call to 4:801/188@fidonet
22:17 [2652] trying f188.n801.z4.binkp.net [52.24.249.28]...
22:17 [2652] connected
+ 22:17 [2652] outgoing session with f188.n801.z4.binkp.net:24554 [52.24.249.28] - 22:17 [2652] OPT CRAM-MD5-a9cf5ca95b72a58b4a1f358dae07c709
+ 22:17 [2652] Remote requests MD mode
- 22:17 [2652] SYS Saturn's Orbit BBS
- 22:17 [2652] ZYZ Flavio Bessa
- 22:17 [2652] VER Mystic/1.12A33 binkp/1.0
+ 22:17 [2652] addr: 4:801/188@fidonet
+ 22:17 [2652] addr: 21:1/146@fsxnet (n/a or busy)
+ 22:17 [2652] addr: 80:21/0@retronet (n/a or busy)
? 22:17 [2652] rerror: Unsecured session not allowed
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+ 22:17 [2652] holding 4:801/188@fidonet (2017/12/11 23:17:43)
+ 22:17 [2652] done (to 4:801/188@fidonet, failed, S/R: 0/0 (0/0
bytes))
22:17 [2652] session closed, quitting...
+ 22:17 [2652] addr: 21:1/146@fsxnet (n/a or busy)
+ 22:17 [2652] addr: 80:21/0@retronet (n/a or busy)
? 22:17 [2652] rerror: Unsecured session not allowed
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+ 22:17 [2652] holding 4:801/188@fidonet (2017/12/11 23:17:43)
+ 22:17 [2652] done (to 4:801/188@fidonet, failed, S/R: 0/0 (0/0
v1.12A36 (at least) is available... there is an important change
related to the below problem...
22:17 [2652] session closed, quitting...
yeah, that breaks connectivity... if one is a *C, they definitely
should not be doing this... especially if they expect unknown FTN type systems to be connecting and trying to drop off node applications...
+ 22:17 [2652] addr: 21:1/146@fsxnet (n/a or busy)
+ 22:17 [2652] addr: 80:21/0@retronet (n/a or busy)
? 22:17 [2652] rerror: Unsecured session not allowed
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+ 22:17 [2652] holding 4:801/188@fidonet (2017/12/11 23:17:43)
+ 22:17 [2652] done (to 4:801/188@fidonet, failed, S/R: 0/0 (0/0
Sorry for taking that long to reply.
Is it recommended to allow unsecured sessions?
yeah, that breaks connectivity... if one is a *C, they definitely
should not be doing this... especially if they expect unknown FTN type
systems to be connecting and trying to drop off node applications...
Well, I am not a *C, but will make the change at Saturn's Orbit as soon as possible.
Thanks to you and Michiel for the heads-up.
+ 22:17 [2652] addr: 21:1/146@fsxnet (n/a or busy)
+ 22:17 [2652] addr: 80:21/0@retronet (n/a or busy)
? 22:17 [2652] rerror: Unsecured session not allowed
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+ 22:17 [2652] holding 4:801/188@fidonet (2017/12/11 23:17:43)
+ 22:17 [2652] done (to 4:801/188@fidonet, failed, S/R: 0/0 (0/0
Sorry for taking that long to reply.
Is it recommended to allow unsecured sessions?
Is it recommended to allow unsecured sessions?
absolutely! if you do not, then random mailers cannot drop netmail destined for your system... they would have to route it and hope that
the routing works properly... consider the situation where a NC or a
RC is trying to deliver mail to nodes in their area... maybe some sort
of C-level notifications... possibly an election coming up or maybe
just needing to contact you about something...
Is it recommended to allow unsecured sessions?
Of course. Fidonet was designed as a peer to peer network. The whole
idea of the public nodelist is that everyone can connect to your
system and drop mail. So yes, it is not just recommended to allow
unsecure sessions, it is an obligation to your fellow sysops to accept unsecure connections.
Now what you do with unsecure mail is another matter. Automatically processing of compressed mail from the unsecure inbound is definitely
not recommended. Automatically processing uncompressed (*.pkt) netmail from the unsecure inbound usually is no problem.
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495928:17:27 |
| Calls: | 82 |
| Files: | 1,070 |
| Messages: | 286,841 |