Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 188  |
|  Fabio Bizzi to Wilfred van Velzen  |
|  Node originating a message  |
|  26 Sep 19 10:46:02  |
 REPLY: 2:280/464 5d8b9a0d MSGID: 2:335/364.1 5d8c7c4b CHRS: UTF-8 2 TZUTC: 0200 TID: hpt/lnx 1.9.0-cur 2019-01-08 Hello Wilfred! 25 Sep 19 18:47, you wrote to me: WV> Then you have to figure out how the header is represented in that WV> intercepted message from HPT. Yes, I have access to all the headers, kludges and so on. :) FB>> and you can do all that you want with perl scripts. WV> 'perl'!? You're a masochist! ;) Naaaa, the devil is not ugly as it's painted. :) WV> Well in an echomail message you have 4 possible sources: WV> Header WV> MSGID kludge WV> Origin line WV> PATH line WV> If you don't trust any, you could compare the ones that are present. WV> And if there are inconsistencies report/log/move-to-bad or do whatever WV> you seem appropriate with it. I don't think it's worth it... Ok, I see that to forge any header you need to have a full editor like golded or msged or similar, with a normal user access like BBS, QWK or NNTP you can't forge these fields. Well, now I have enough informations and options to choose in. Man Thanks,your help was precious! :) Ciao! Fabio --- GoldED+/LNX 1.1.5-b20180707 * Origin: ]\/[imac Rebirth Boss Point (2:335/364.1) SEEN-BY: 1/123 15/2 18/200 221/1 227/114 229/354 426 1014 240/1120 SEEN-BY: 240/5832 249/206 317 280/464 292/854 8125 301/520 317/3 322/757 SEEN-BY: 333/808 335/206 364 342/200 410/9 633/280 PATH: 335/364 292/854 229/426 |
[ << oldest | < older | list | newer > | newest >> ]