Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 15676  |
|  Dan Clough to Flavio Bessa  |
|  Re: Crash Netmail  |
|  22 Apr 24 11:16:00  |
 TZUTC: -0500 MSGID: 4260.fido_mystic@1:135/115 2a8bd4b1 REPLY: 4:801/188 0085b28d PID: Synchronet 3.20a-Linux master/ad12b9b21 Apr 13 2024 GCC 11.2.0 TID: SBBSecho 3.20-Linux master/ad12b9b21 Apr 13 2024 GCC 11.2.0 BBSID: PALANTIR CHRS: ASCII 1 -=> Flavio Bessa wrote to Paul Hayton <=- FB> But that is the point... If I have the CRASH flag enabled for FB> Netmail, Mystic should (according to the FTSC specs) read the FB> nodelist, find out the Binkp address for Bjorn's system, and FB> issue an unsecured session towards 2:203/0. That is what the FB> other mailers do, and that is why we have nodelists in the first FB> place... Nope. The CRASH flag is not the same as, nor does it specify, the DIRECT flag. You need to have both set for the behavior you desire. ... So easy, a child could do it. Child sold separately. === MultiMail/Linux v0.52 --- SBBSecho 3.20-Linux * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115) SEEN-BY: 1/120 15/0 18/0 90/1 103/705 105/81 106/201 116/116 120/616 SEEN-BY: 123/0 10 25 180 200 525 755 1185 3001 124/5016 128/260 129/215 SEEN-BY: 129/305 135/0 115 205 210 211 212 220 225 385 388 390 391 SEEN-BY: 135/395 153/757 7715 154/10 30 40 50 700 203/0 218/700 220/90 SEEN-BY: 221/0 6 222/2 226/30 70 227/114 229/110 111 112 113 206 275 SEEN-BY: 229/307 310 317 400 426 428 470 550 664 700 240/1120 5832 SEEN-BY: 250/1 266/512 275/1000 280/464 5003 282/1038 291/111 292/854 SEEN-BY: 292/8125 299/6 301/1 320/219 322/757 341/66 234 342/200 396/45 SEEN-BY: 423/120 460/58 256 1124 467/888 633/280 712/848 1321 770/1 SEEN-BY: 2320/105 3634/0 12 27 56 57 119 5020/400 1042 5054/30 5075/35 PATH: 135/115 3634/12 154/10 280/464 460/58 229/426 |
[ << oldest | < older | list | newer > | newest >> ]