1. Forum
  2. Fsxnet Message
  3. FSX MYS

  • Error Message

    From Warp 4@21:2/135 to All on Friday, January 18, 2019 16:17:42
    So, getting the following error message when trying to process mail from my WINServer machine:

    5cae1aca.pkt does not match an AKA (1:116/17)

    This AKA _IS_ indeed set up in Mystic and is marked as active. All passwords are correct. Not sure what is going on here as nothing changed. Any ideas would be appreciated.

    --- Mystic BBS v1.12 A42 2018/12/27 (Windows/32)
    * Origin: Omicron Theta * Southaven MS * winserver.org:2300 (21:2/135)
  • From bcw142@21:1/145 to Warp 4 on Saturday, January 19, 2019 16:34:26
    On 18 Jan 2019, Warp 4 said the following...

    So, getting the following error message when trying to process mail from my WINServer machine:

    5cae1aca.pkt does not match an AKA (1:116/17)

    --- Mystic BBS v1.12 A42 2018/12/27 (Windows/32)
    * Origin: Omicron Theta * Southaven MS * winserver.org:2300 (21:2/135)

    So are you running A42 which is a pre-alpha? It just might be bug related. Check the executables and if it still fails fall back to A41 release, which
    is what I'm running (on the Pi). While A42 is known to work for most, it is still a pre-alpha.

    --- Mystic BBS v1.12 A41 2018/12/27 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)
  • From Avon@21:1/101 to Warp 4 on Sunday, January 20, 2019 15:37:11
    On 18 Jan 2019, Warp 4 pondered and said...

    So, getting the following error message when trying to process mail from my WINServer machine:

    5cae1aca.pkt does not match an AKA (1:116/17)

    This AKA _IS_ indeed set up in Mystic and is marked as active. All passwords are correct. Not sure what is going on here as nothing
    changed. Any ideas would be appreciated.

    When you say the AKA is set up are you meaning your system is flying that or have you got an echonode your connecting to defined with that node number?

    Best, Paul

    ---- E-avon@bbs.nz ------ W-bbs.nz ---
    ---- K-keybase.io/avon --------------

    --- Mystic BBS v1.12 A42 2018/12/30 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Warp 4@21:2/135 to Avon on Saturday, January 26, 2019 13:28:28
    On 20 Jan 2019, Avon said the following...

    This AKA _IS_ indeed set up in Mystic and is marked as active. All passwords are correct. Not sure what is going on here as nothing changed. Any ideas would be appreciated.

    When you say the AKA is set up are you meaning your system is flying
    that or have you got an echonode your connecting to defined with that
    node number?

    I have an echonode defined with that node number.

    --- Mystic BBS v1.12 A42 2018/12/27 (Windows/32)
    * Origin: Omicron Theta * Southaven MS * winserver.org:2300 (21:2/135)