Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 190  |
|  Wilfred van Velzen to Fabio Bizzi  |
|  Re: Node originating a message  |
|  26 Sep 19 11:20:52  |
 TID: FMail-lnx64 2.1.0.18-B20170815 RFC-X-No-Archive: Yes TZUTC: 0200 CHRS: UTF-8 2 PID: GED+LNX 1.1.5-b20161221 MSGID: 2:280/464 5d8c82f5 REPLY: 2:335/364.1 5d8c7c4b Hi Fabio, On 2019-09-26 10:46:02, you wrote to me: 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... FB> Ok, I see that to forge any header you need to have a full editor like FB> golded or msged or similar, with a normal user access like BBS, QWK or NNTP FB> you can't forge these fields. Indeed. FB> Well, now I have enough informations and options to choose in. Well, not really multiple options. You will have to use the Origin line for the full address. You can only use the others, to verify... ;) Bye, Wilfred. --- FMail-lnx64 2.1.0.18-B20170815 * Origin: FMail development HQ (2:280/464) SEEN-BY: 1/123 15/2 18/200 103/705 154/10 203/0 221/0 227/114 229/354 SEEN-BY: 229/426 1014 240/5832 249/206 317 280/464 5003 292/854 310/31 SEEN-BY: 317/3 322/757 342/200 396/45 423/120 633/280 712/848 770/1 PATH: 280/464 229/426 |
[ << oldest | < older | list | newer > | newest >> ]