Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 367  |
|  Fred Riccio to Oli  |
|  Problem with legacy t  |
|  03 Dec 20 08:33:11  |
 MSGID: 1:132/174 5fc8a5f1 TZUTC: -0500 REPLY: 2:280/464.47@fidonet 5fc8c053 CHRS: IBMPC 2 CODEPAGE: 437 Hello Oli! 03 Dec 20 11:18, Oli wrote to Marc Lewis: O> For fixing the problem we have to know the real cause of the problem. O> Have you inspected the raw packets before tossing? Yes. My Packet Inspector program didn't note any problems. The zone IS in the packet header where it is supposed to be. I also ran the packet through GMD... ----- gmd.txt begins ----- GMD - Grunged Message Detect Utility, version 3.10 for PC/MS-DOS. Written by David Troendle (1:396/5) Documented and distributed by John Souvestre (1:396/1) + 08:30:28 4R108DBK.PKT (ID=FF, 2,533b) from 1:103/705 to 1:132/174 - 08:30:28 #1, From: Rob Swindell Area: Net Mail * 08:30:28 1 Packet (2,533b), 1 msg (0 bad), Time: 0:00 ----- gmd.txt ends ----- IMHO, the REAL cause is the design of the "packed message" header in the packet. It does not have a place to put zone or point, forcing the tosser to get it somewhere else. Using the packet header is incorrect, since NetMail is often routed, and the packet header indicates the system who sent the message to me and not the original author. --- Msged/NT 6.0.1 * Origin: Somewhere in New Hampshire's White Mountains (1:132/174) SEEN-BY: 1/19 123 16/0 18/200 90/1 105/81 120/340 123/130 131 124/5016 SEEN-BY: 132/174 154/10 203/0 221/0 1 226/30 227/114 702 229/101 424 SEEN-BY: 229/426 550 664 1016 230/0 240/5832 249/110 206 317 400 261/38 SEEN-BY: 280/464 5003 292/854 8125 317/3 320/119 219 319 322/0 757 SEEN-BY: 342/200 396/45 633/280 PATH: 132/174 320/219 203/0 280/464 229/101 426 |
[ << oldest | < older | list | newer > | newest >> ]