Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 8776  |
|  Nicholas Boel to Wilfred van Velzen  |
|  Re: binkd cfg question.  |
|  16 Nov 24 16:00:20  |
 TZUTC: -0600 MSGID: 3381.binkd@1:154/700 2b9e5929 PID: Synchronet 3.20a-Linux master/a7f1a24a2 Nov 16 202 GCC 14.2.1 TID: SBBSecho 3.22-Linux master/a7f1a24a2 Nov 16 2024 15:22 GCC 14.2.1 BBSID: PHARCYDE CHRS: ASCII 1 NOTE: slrn/pre1.0.4-9 (Linux) Hello Wilfred, On Sat, Nov 16 2024 11:34:04 -0600, you wrote: > Hi Nicholas, > On 2024-11-16 10:35:03, you wrote to me: > I'm not trying to stir the pot. I'm just trying to point out that sometimes > someone with a mailer publicly online 24/7, doesn't need, or want, or can't > have a full blown node number, a point number will suffice, and is much > easier to obtain... Point taken. However, what I originally said briefly covered this, but I didn't want to go too far into it, especially if it had nothing to do with what he was trying to do. > That's it. And of course these are exceptions to the normal, although still > valid use cases. And if a sender doesn't have the connection info for such a > point, although publicly available, he has no choice and has to route as you > say... Yeah. I wasn't talking about exceptions, though. I was trying to help someone fix their issue with normal operations. No need to go into extravagant, very minor use-case, abnormal circumstances (unless the original poster would have brought something like that up) that could possibly confuse the original poster even more. Do you agree? > Btw: Why doesn't your message have a REPLY: kludge? Probably because it was posted via NNTP with a very old linux console based client (slrn) that has no idea what an FTN REPLY kludge is. However, if this one does have a REPLY kludge, and while I'm using the same client via the same method, we can thank Rob (Synchronet) for fixing it. :) Regards, Nick ... He who laughs last, thinks slowest. --- SBBSecho 3.22-Linux * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700) SEEN-BY: 10/0 1 102/401 103/1 705 104/119 105/81 106/201 120/302 616 SEEN-BY: 123/10 124/5016 128/187 129/215 305 153/757 7715 154/10 30 SEEN-BY: 154/50 700 203/0 214/22 218/0 1 215 601 700 720 840 860 870 SEEN-BY: 218/880 930 940 220/90 221/0 6 226/18 30 44 50 227/114 229/110 SEEN-BY: 229/114 200 206 275 300 307 310 317 426 428 470 550 664 700 SEEN-BY: 240/1120 5832 266/512 280/464 5003 5006 5555 282/1038 291/111 SEEN-BY: 292/854 8125 301/1 310/31 320/219 322/757 341/66 234 342/200 SEEN-BY: 396/45 423/120 460/58 467/888 633/280 712/848 770/1 902/26 SEEN-BY: 2320/105 3634/12 5020/400 PATH: 154/700 10 280/464 103/705 218/700 229/426 |
[ << oldest | < older | list | newer > | newest >> ]