Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 182  |
|  Fabio Bizzi to Wilfred van Velzen  |
|  Node originating a message  |
|  25 Sep 19 16:41:18  |
 REPLY: 2:280/464 5d8b750d MSGID: 2:335/364.1 5d8b7e30 CHRS: UTF-8 2 TZUTC: 0200 TID: hpt/lnx 1.9.0-cur 2019-01-08 Hello Wilfred! 25 Sep 19 16:04, you wrote to me: FB>> Many Thanks, what header are you referring to, WV> That depends where you intercept the messages to get the information. WV> Is it from the .pkt file or is it already in a message base? In the between. :) In HPT you can intercept the single message unpacked from the bundle before the delivery to the message base, there you are in GOD MODE [(c) DOOM] and you can do all that you want with perl scripts. FB>> all the informations of the headers or an Echo message can be FB>> forged. FB>> :) WV> If everything can be forged, your software can't know if some part or WV> all of the message is forged, so it doesn't have to consider that. And WV> it's not a consideration to not use the header, instead of other parts WV> of the message. ;) You're right, but there should be someting that is injected by the main node to know where the message is originated and not forgeable by a user editor (BBS/Point/JAMNNTPD and so on), do you know about something like this? Are you sure that the first node of the path can be rewritten? Many Thanks! :) 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 >> ]