1. Forum
  2. FidoNet
  3. MYSTIC

  • Skipping Unsecure Echomail

    From Jeff Earle@1:229/700 to g00r00 on Friday, February 04, 2022 21:34:41
    Found another problem, seems to be skipping inbound echomail from a new net I joined.
    Before this we had an issue that the PKT password didn't match even though we have the same PKT password set. That we fixed on the hub end.

    This I have never come across before. It finds the PKT, unzips, importing, them says skip unsecure echomail in area.

    Here is the exerpt from the log (redacted of course):

    ! Feb 04 20:16:45 Import from c:\mystic\echomail\in\unsecure\
    + Feb 04 20:16:45 Extracting 7BC94307.FR1
    - Feb 04 20:16:45 Execute Res: 0 Cmd: unzip -oqqjC "c:\mystic\echomail\in\unsecure\7BC94307.FR1" "*.pkt" -d c:\mystic\temputil\ 2>nul
    + Feb 04 20:16:45 Importing 2C60A051.PKT (??:??/0 to ??:?/106)
    ! Feb 04 20:16:45 Skip unsecure echomail in area "********"
    + Feb 04 20:16:45 Results: 0 echo, 0 net, 0 dupes, 0 tossed in 0.17s

    I cannot find any reference to skipping unsecured echomail in the .ini files. Am I missing something?

    ... There will be a rain dance Friday night, weather permitting!

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/64)
    * Origin: Mystic Realms - A Social Media Alternative (1:229/700)
  • From Jay Harris@1:229/664 to Jeff Earle on Saturday, February 05, 2022 08:08:37
    On 04 Feb 2022, Jeff Earle said the following...

    I cannot find any reference to skipping unsecured echomail in the .ini files. Am I missing something?

    I believe if you don't have a bink session password set the packet file goes to unsecure which is really only for tossing netmail.


    Jay

    ... It is not enough to succeed. Others must fail.

    --- Mystic BBS v1.12 A47 2021/12/24 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From Jeff Earle@1:229/700 to Jay Harris on Saturday, February 05, 2022 09:28:02
    On 05 Feb 2022, Jay Harris said the following...

    On 04 Feb 2022, Jeff Earle said the following...

    I cannot find any reference to skipping unsecured echomail in the .in files. Am I missing something?

    I believe if you don't have a bink session password set the packet file goes to unsecure which is really only for tossing netmail.


    Yes I believe you are correct on that. But thats not the issue. I have the setting in the .ini to process echomail mail from the unsecure folder. It does process the .PKT but skips tossing in to the msg base. The hub has it setup for no session password for many of the nodes that are mystic bbs and they don't have this problem. Something is prventing the toss to the message base.
    I will keep looking for a solution.

    Thanks

    ... System halted - Press all keys at once to continue

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/64)
    * Origin: Mystic Realms - A Social Media Alternative (1:229/700)
  • From g00r00@1:129/215 to Jeff Earle on Saturday, February 05, 2022 10:33:56
    I believe if you don't have a bink session password set the packet JE> JH> JE> JH> JE> JH> JE> JH> fi
    goes to unsecure which is really only for tossing netmail.

    Yes I believe you are correct on that. But thats not the issue. I have
    the setting in the .ini to process echomail mail from the unsecure
    folder. It does process the .PKT but skips tossing in to the msg base.

    As Jay mentioned: At least one of the issues here is that echomail will never be allowed from unsecure packets. If it was, then anyone could easily destroy networks with spam posts and floods (and trust me there are spammers and others childish people enough to do stuff like that unfortunately).

    When processing unsecured PKTs is enabled, it will only process netmail and skip over any echomail. That is what you see happening in your logs.

    If you want to accept echomail from an incoming connection they have to be a known connection. To do this they need to be setup in your echomail nodes, they need to present the same address you've set them up for, and they need to have an agreed password to authenticate.

    If you do have them setup and its still going to unsecured, then the issue is likely found in the mis.log which will detail the BINKP authentication. Most likely in this case they are not presenting the same address to you that you have configured for them.

    ... If you can't make it good, make it LOOK good. -Bill Gates.

    --- Mystic BBS v1.12 A48 2022/02/03 (Windows/64)
    * Origin: Sector 7 * Mystic WHQ (1:129/215)