Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 1115  |
|  August Abolins to Maurice Kinal  |
|  which is why I built my own..  |
|  27 Dec 25 10:17:00  |
 MSGID: 2:221/1.58@fidonet 27d478c5 REPLY: 1:153/7001 694f30aa PID: OpenXP/5.0.64 (Win32) CHRS: ASCII 1 TZUTC: -0500 Hello Maurice! ** On Saturday 27.12.25 - 01:04, you wrote: >> So, basically you list your messages with ls? MK> As of this writing, all incoming is dumped into a single MK> file with individual msgs occupying a line. Thus "wc -l" MK> incoming.file will yeild the number of msgs in the file. MK> Each msg (line) contains five fields; MK> $DateTime\0$To\0$From\0$Subject\0\$Body\n One line per message.. sounds very efficient. +1 >> And I suppose you can't display msgid-relationships for navigating a >> thread? MK> Yes. kludges are part of $Body and are easily be MK> 'grep'ped from that field. They stick out like a sore MK> thumb given the leading '\1' character. However I could MK> easily be convinced to putting kludges into their own MK> field. You'd need extra logic to produce a FULL list of threaded/ connected messages. But two at a time isn't too bad. You should produce a vid illustrating how you do typical reading/searching/replying activities. -- ../|ug --- OpenXP 5.0.64 * Origin: (2:221/1.58) SEEN-BY: 50/22 103/705 105/81 106/201 124/5016 128/187 129/14 153/757 SEEN-BY: 153/7715 154/10 30 110 203/0 218/700 221/1 6 226/30 227/114 SEEN-BY: 229/110 112 134 206 300 317 400 426 428 470 664 700 705 240/1120 SEEN-BY: 240/5832 263/1 266/512 280/464 5003 291/111 292/8125 301/1 SEEN-BY: 310/31 320/219 322/757 341/66 234 342/200 396/45 423/81 460/58 SEEN-BY: 460/256 1124 5858 633/280 712/848 770/1 902/26 5020/400 8912 SEEN-BY: 5054/30 5075/35 PATH: 221/1 280/464 460/58 229/426 |
[ << oldest | < older | list | newer > | newest >> ]