Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 15746  |
|  Paul Hayton to g00r00  |
|  Re: Crash Netmail  |
|  14 May 24 14:21:16  |
 TID: Mystic BBS 1.12 A48 MSGID: 3:770/100 d6828eed REPLY: 1:129/215 5962c51a TZUTC: 1200 On 13 May 2024 at 12:35a, g00r00 pondered and said... g0> One challenge I could use suggestions on for the community is what g0> happens when a netmail is flagged direct and there is no nodelist entry g0> or the entry is there but the system doesn't answer or doesn't have an g0> IP address/hostname etc. If there's non delivery after X attempts I'd suggest an auto netmail to the sender is generated and something to sysop as well / noted in MUTIL logs. Not sure if the logic is in there but if a netmail is routed to another Mystic system and the routing at destination sends the netmail back to the originating system... and you start getting a back and forth loop happening... there needs to be something there to detect this, cease the loop and send a netmail to the sender and sysop of the source system alerting them to the failed delivery... Nice to see you active, hope things are going well. Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz --- Mystic BBS v1.12 A48 (Linux/64) * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100) SEEN-BY: 15/0 90/1 103/705 105/81 106/201 124/5016 128/260 129/305 SEEN-BY: 135/220 225 153/757 7715 154/10 30 203/0 218/700 840 220/70 SEEN-BY: 221/0 226/17 30 100 227/114 229/110 111 112 113 206 275 300 SEEN-BY: 229/307 317 400 426 428 470 550 664 700 240/1120 5832 266/512 SEEN-BY: 267/800 280/464 5003 282/1038 291/111 292/854 8125 301/1 SEEN-BY: 320/219 322/757 341/66 234 342/200 396/45 423/120 460/58 SEEN-BY: 460/256 1124 467/888 633/280 712/848 770/1 3 100 340 772/210 SEEN-BY: 772/220 230 5020/400 5054/30 5075/35 PATH: 770/100 1 280/464 460/58 229/426 |
[ << oldest | < older | list | newer > | newest >> ]