• Node originating a message

    From Fabio Bizzi@2:335/364.1 to All on Wed Sep 25 14:28:28 2019
    Hello All!

    I'm trying to develop something on fido and I need to know where to look at to find the node that originated a message.

    Do I have to look at the MSGID or at the PATH? :)

    Many thanks.

    Ciao!
    Fabio

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)
  • From Nick Andre@1:229/426 to Fabio Bizzi on Wed Sep 25 08:51:19 2019
    On 25 Sep 19 14:28:28, Fabio Bizzi said the following to All:

    I'm trying to develop something on fido and I need to know where to look
    at
    find the node that originated a message.

    Do I have to look at the MSGID or at the PATH? :)

    The PATH.

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Wilfred van Velzen@2:280/464 to Fabio Bizzi on Wed Sep 25 15:11:16 2019
    Hi Fabio,

    On 2019-09-25 14:28:28, you wrote to All:

    I'm trying to develop something on fido and I need to know where to
    look at to find the node that originated a message.

    Do I have to look at the MSGID or at the PATH? :)

    MSGID's aren't mandatory. PATH's could be cleaned, or not reliable when re-exported from a message base on a rescan.

    So use the origin line:

    * Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)

    Which should always be present, and/or the header of the mail.

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Fabio Bizzi@2:335/364.1 to Nick Andre on Wed Sep 25 15:28:04 2019
    Hello Nick!

    25 Sep 19 08:51, you wrote to me:

    I'm trying to develop something on fido and I need to know where
    to look at find the node that originated a message.

    Do I have to look at the MSGID or at the PATH? :)

    The PATH.

    Many Thank, but now I have to ask how to get the Zone? :)

    In the path you have the first node that is the originating node plus all the traversed nodes, but it's without the preceding zone.

    eg the path of this message as it was received on my point:

    @PATH: 229/426 292/854 335/364

    Many Thanks.

    Ciao!
    Fabio

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)
  • From Wilfred van Velzen@2:280/464 to Fabio Bizzi on Wed Sep 25 15:39:59 2019
    Hi Fabio,

    On 2019-09-25 15:28:04, you wrote to Nick Andre:

    The PATH.

    Many Thank, but now I have to ask how to get the Zone? :)

    In the path you have the first node that is the originating node plus all the traversed nodes, but it's without the preceding zone.

    That's another reason why you shouldn't use the PATH... ;)


    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Fabio Bizzi@2:335/364.1 to Wilfred van Velzen on Wed Sep 25 15:41:46 2019
    Hello Wilfred!

    25 Sep 19 15:11, you wrote to me:

    So use the origin line:

    * Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)

    Which should always be present, and/or the header of the mail.

    Many Thanks, what header are you referring to, all the informations of the headers or an Echo message can be forged. :)

    Ciao!
    Fabio

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)
  • From The Evil@6:666/666.6 to Wilfred van Velzen on Wed Sep 25 15:47:16 2019
    Hello Wilfred!

    25 Sep 19 15:11, you wrote to me:

    * Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)

    Which should always be present, and/or the header of the mail.

    Everything can be forged. ;)

    Ciao!
    Fabio

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: ]\/[imac Rebirth Boss Point (6:666/666.6)
  • From Fabio Bizzi@2:335/364.1 to Wilfred van Velzen on Wed Sep 25 15:53:14 2019
    Hello Wilfred!

    25 Sep 19 15:39, you wrote to me:

    The PATH.

    Many Thank, but now I have to ask how to get the Zone? :)

    In the path you have the first node that is the originating node
    plus all the traversed nodes, but it's without the preceding
    zone.

    That's another reason why you shouldn't use the PATH... ;)

    Ok, but:

    - The PATH can be cleared
    - The MSGID is not mandatory and can be omitted
    - The Origin can be forged
    - The Headers can be forged

    So, how can I determine the originating node of a message? :D

    Ciao!
    Fabio

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)
  • From Wilfred van Velzen@2:280/464 to Fabio Bizzi on Wed Sep 25 16:04:31 2019
    Hi Fabio,

    On 2019-09-25 15:41:46, you wrote to me:

    So use the origin line:

    * Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)

    Which should always be present, and/or the header of the mail.

    Many Thanks, what header are you referring to,

    That depends where you intercept the messages to get the information. Is it from the .pkt file or is it already in a message base?

    all the informations of the headers or an Echo message can be forged.
    :)

    If everything can be forged, your software can't know if some part or all of the message is forged, so it doesn't have to consider that. And it's not a consideration to not use the header, instead of other parts of the message. ;)

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Fabio Bizzi@2:335/364.1 to Wilfred van Velzen on Wed Sep 25 16:41:18 2019
    Hello Wilfred!

    25 Sep 19 16:04, you wrote to me:

    Many Thanks, what header are you referring to,

    That depends where you intercept the messages to get the information.
    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.

    all the informations of the headers or an Echo message can be
    forged.
    :)

    If everything can be forged, your software can't know if some part or
    all of the message is forged, so it doesn't have to consider that. And it's not a consideration to not use the header, instead of other parts
    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)
  • From mark lewis@1:3634/12 to Fabio Bizzi on Wed Sep 25 12:19:45 2019
    Re: Node originating a message
    By: Fabio Bizzi to All on Wed Sep 25 2019 14:28:28

    I'm trying to develop something on fido and I need to know where to look at
    to find the node that originated a message.

    Do I have to look at the MSGID or at the PATH? :)

    the Origin Line!

    MSGID should only be used for identifying a message...

    Path should only be used for noting the path of the message...


    )\/(ark
    --- SBBSecho 3.09-Linux
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
  • From Wilfred van Velzen@2:280/464 to Fabio Bizzi on Wed Sep 25 18:47:08 2019
    Hi Fabio,

    On 2019-09-25 16:41:18, you wrote to me:

    That depends where you intercept the messages to get the information.
    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]

    Then you have to figure out how the header is represented in that intercepted message from HPT.

    and you can do all that you want with perl scripts.

    'perl'!? You're a masochist! ;)

    If everything can be forged, your software can't know if some part or
    all of the message is forged, so it doesn't have to consider that.
    And it's not a consideration to not use the header, instead of other
    parts 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?

    Well in an echomail message you have 4 possible sources:

    Header
    MSGID kludge
    Origin line
    PATH line

    If you don't trust any, you could compare the ones that are present. And if there are inconsistencies report/log/move-to-bad or do whatever you seem appropriate with it. I don't think it's worth it...

    Are you sure that the first node of the path can be rewritten?

    It's generated on the originating system, so someone that really wants to fiddle with it, could.

    The problem with the PATH line is the lack of zone and point fields. And they could have been stripped somewhere along the path. So the first system in the first PATH line doesn't have to be the originating system.

    Btw: The header (in a packed message) has the same limitation as the PATH, it doesn't contain the Zone and Point number of the originating system.

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Ward Dossche@2:292/854 to The Evil on Thu Sep 26 01:07:45 2019

    * Origin: ]\/[imac Rebirth Boss Point (6:666/666.6)

    Don't ... do ... that ... !!

    \%/@rd

    --- D'Bridge 3.99
    * Origin: Do not meddle in the affairs of wizards (2:292/854)
  • From Rob Swindell@1:103/705 to Fabio Bizzi on Wed Sep 25 16:19:08 2019
    Re: Node originating a message
    By: Fabio Bizzi to Wilfred van Velzen on Wed Sep 25 2019 03:53 pm

    Hello Wilfred!

    25 Sep 19 15:39, you wrote to me:

    The PATH.

    Many Thank, but now I have to ask how to get the Zone? :)

    In the path you have the first node that is the originating node
    plus all the traversed nodes, but it's without the preceding
    zone.

    That's another reason why you shouldn't use the PATH... ;)

    Ok, but:

    - The PATH can be cleared
    - The MSGID is not mandatory and can be omitted
    - The Origin can be forged
    - The Headers can be forged

    So, how can I determine the originating node of a message? :D

    If you're referring to EchoMail, then FTS-4 is the spec (http://ftsc.org/docs/fts-0004.001) and it instructs you to use the Origin line to determine where a message originated.

    digital man

    Synchronet/BBS Terminology Definition #19:
    DOCSIS = Data Over Cable Service Interface Specification
    Norco, CA WX: 83.3øF, 53.0% humidity, 14 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.10-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Fabio Bizzi@2:335/364.1 to Ward Dossche on Thu Sep 26 10:44:40 2019
    Hello Ward!

    26 Sep 19 01:07, you wrote to The Evil:


    * Origin: ]\/[imac Rebirth Boss Point (6:666/666.6)

    Don't ... do ... that ... !!

    I beg your pardon, It's only a proof of concept, my only and last demostration. :)

    Ciao!
    Fabio

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)
  • From Fabio Bizzi@2:335/364.1 to Wilfred van Velzen on Thu Sep 26 10:46:02 2019
    Hello Wilfred!

    25 Sep 19 18:47, you wrote to me:

    Then you have to figure out how the header is represented in that intercepted message from HPT.

    Yes, I have access to all the headers, kludges and so on. :)

    and you can do all that you want with perl scripts.

    'perl'!? You're a masochist! ;)

    Naaaa, the devil is not ugly as it's painted. :)

    Well in an echomail message you have 4 possible sources:

    Header
    MSGID kludge
    Origin line
    PATH line

    If you don't trust any, you could compare the ones that are present.
    And if there are inconsistencies report/log/move-to-bad or do whatever
    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)
  • From Fabio Bizzi@2:335/364.1 to Rob Swindell on Thu Sep 26 10:52:34 2019
    Hello Rob!

    25 Sep 19 16:19, you wrote to me:

    If you're referring to EchoMail, then FTS-4 is the spec (http://ftsc.org/docs/fts-0004.001) and it instructs you to use the
    Origin line to determine where a message originated.

    Many Thanks, I'll take a look at it asap. :)

    Ciao!
    Fabio

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)
  • From Wilfred van Velzen@2:280/464 to Fabio Bizzi on Thu Sep 26 11:20:52 2019
    Hi Fabio,

    On 2019-09-26 10:46:02, you wrote to me:

    Well in an echomail message you have 4 possible sources:

    Header
    MSGID kludge
    Origin line
    PATH line

    If you don't trust any, you could compare the ones that are present.
    And if there are inconsistencies report/log/move-to-bad or do whatever
    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.

    Indeed.

    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)
  • From Fabio Bizzi@2:335/364.1 to Wilfred van Velzen on Thu Sep 26 12:43:46 2019
    Hello Wilfred!

    26 Sep 19 11:20, you wrote to me:

    [...]
    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...
    ;)

    Correct! :)

    Well, let me dig into and I hope in few time I'll release a nice tool for the hpt tosser. ;)

    Ciao!
    Fabio

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)
  • From Tommi Koivula@2:221/360 to Fabio Bizzi on Thu Sep 26 21:58:12 2019
    "Fabio Bizzi" <1@364.335.2> wrote:

    Well, let me dig into and I hope in few time I'll release a nice tool
    for the hpt tosser. ;)

    +1 :)

    'Tommi

    --- Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
    * Origin: - nntp://rbb.fidonet.fi - Lake Ylo - Finland - (2:221/360)