1. Forum
  2. fsxNet
  3. FSX MYS

  • Mailin

    From bcw142@21:1/145 to All on Mon Mar 22 11:58:39 2021
    I had noticed no mailin the last few days and check the logs. The last time
    it came in was 3/18, so I forced './mutil mailin.ini' from the command line
    and in it flooded. The mailin event is shown last (below) is there something wrong in it?

    ----------------- MUTIL v1.12 A47 2021/02/12 Thu, Mar 18 2021 (loglevel 3)
    + Mar 18 16:57:12 Startup using mailin.ini
    - Mar 18 16:57:12 EXEC ImportEchoMail
    - Mar 18 16:57:12 EXEC LinkMessages
    - Mar 18 16:57:12 EXEC FileToss
    + Mar 18 16:57:12 Process: Toss FDN/TIC Files
    + Mar 18 16:57:12 Waiting for BUSY nodes
    + Mar 18 16:57:12 Scanning Hatches
    + Mar 18 16:57:12 Results: 0 import, 0 toss, 0 hatch, 0 bad in 0.02s
    + Mar 18 16:57:12 Process: Importing EchoMail
    + Mar 18 16:57:12 Waiting for BUSY nodes
    ! Mar 18 16:57:12 Import from /mystic/echomail/in/
    ! Mar 18 16:57:12 Unknown inbound file ep210303.1.zip
    ! Mar 18 16:57:12 Unknown inbound file ep210303.zip
    + Mar 18 16:57:12 Extracting 53bbfd29.fr0
    - Mar 18 16:57:12 unzip -oqqjC "/mystic/echomail/in/53bbfd29.fr0" "*.pkt" -d
    /mystic/temputil/ /dev/null 2>&1
    + Mar 18 16:57:12 Importing 53bbfc2d.pkt (21:1/100 to 21:1/145)
    + Mar 18 16:57:12 Import #521 to FSX_DAT
    + Mar 18 16:57:12 Export FSX_DAT #521 to 21:1/145.2@fsxnet
    + Mar 18 16:57:12 Extracting 53be6c28.fr0
    - Mar 18 16:57:13 unzip -oqqjC "/mystic/echomail/in/53be6c28.fr0" "*.pkt" -d
    /mystic/temputil/ /dev/null 2>&1
    + Mar 18 16:57:13 Importing 53be6b2d.pkt (21:1/100 to 21:1/145)
    + Mar 18 16:57:13 Import #1001 to FSX_BBS
    + Mar 18 16:57:13 Export FSX_BBS #1001 to 21:1/145.2@fsxnet
    + Mar 18 16:57:13 Export FSX_BBS #1001 to 21:1/145.4@fsxnet
    + Mar 18 16:57:13 Bundling Messages
    ! Mar 18 16:57:13 ERROR: Unable to find echonode 0 while bundling (._file_id.pk
    t)(._file_id.diz)
    - Mar 18 16:57:13 EXEC: zip -qj9 /mystic/echomail/out/fidonet/00010091.pnt/00
    000004.th0 /mystic/temputil/0b17b601.pkt /dev/null 2>&1
    + Mar 18 16:57:13 Adding PKT to FLO (addr=21:1/145.4 pkt=/mystic/echomail/out
    /fidonet/00010091.pnt/00000004.th0 flo=/mystic/echomail/out/fidonet/00010091.pnt
    /00000004.flo)
    ! Mar 18 16:57:13 ERROR: Unable to find echonode 0 while bundling (._FILE_ID.pk
    t)(._FILE_ID.DIZ)
    - Mar 18 16:57:13 EXEC: zip -qj9 /mystic/echomail/out/fidonet/00010091.pnt/00
    000002.th2 /mystic/temputil/0b17b601.pkt /dev/null 2>&1
    + Mar 18 16:57:13 Adding PKT to FLO (addr=21:1/145.2 pkt=/mystic/echomail/out
    /fidonet/00010091.pnt/00000002.th2 flo=/mystic/echomail/out/fidonet/00010091.pnt
    /00000002.flo)
    + Mar 18 16:57:13 Results: 2 echo, 0 net, 0 dupes, 3 tossed in 0.10s
    + Mar 18 16:57:13 Process: Linking Messages
    + Mar 18 16:57:14 Base: FSX_BBS
    + Mar 18 16:57:14 Link #997 ReplyTo:992 1st:1001 Next:998
    + Mar 18 16:57:14 Link #1001 ReplyTo:997 1st:0 Next:0
    + Mar 18 16:57:14 Results: Linked 2 msgs in 1.58s
    + Mar 18 16:57:14 Shutdown Normal (0)
    pi@dmz:/mystic $ date
    Mon Mar 22 11:28:45 EDT 2021
    pi@dmz:/mystic $ ./mutil mailin.ini
    ▄▄ ▄▄ ░▓ ▄ ▄ ▓▄▄ ▄▓ ░▒▓▄▄▄ ░▄
    ▐█▄▄ ■ ▀ ▌ ░░░▐ ▓▀▀▀▀▀▀▀▀▀ ▀▀▀▀▀▀▀▀▀▀▀ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ ▀▀▀▀█▓
    ░███▄▄ ▄▀▄▄███▐░▌ ▐ % ░▒ ▀ ▓████▄▄▀█▓▀▄█████▓▐ ▐ 100 ▓ ▓ ▒▓▓▓█▀▀█▄▄█▀▀█▓▓▓▒▐░■·───────────────────────────────────────────── ─· ░▓█ ▀ █░░░█ ▀▀▀▀ █░░░█ ▐ % ░▓ ░░▓████ ▓▄▄▄▄▓ █████ ▒▌ ▐ 100 ▓ ▄▄■ ▀▀▓ ▒ ░░▓▄▄▄▄▄▄▄▓▄▄▄▄▄▄▄▄▄▄▄▓ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄ ▄ ▄▄▄▄▄▄▄ ▄▓█
    ░ mUTIL v1.12 ▄▀ ▀ ▀▀ ░ ▀ ░
    ░ ▀ ▄▄▀ mailin.ini (3/3)

    ▐ Process ───────────── ─ Status ────────────────────────────── Result ────·
    ┌───────────────────────│─────────────────────────────────────│────────────┐
    Toss FDN/TIC Files 2 import, 4 toss, 0 hatch, 1 bad DONE 0.14s
    Importing EchoMail 545 echo, 0 net, 0 dupes, 914 tosse DONE 11.52s
    Linking Messages Linked 114 msgs DONE 2.38s




    └──────────────────────────────────────────────────────────────────────────┘
    > Execution of 3 processes complete

    ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
    ▄
    █ Configuration Networking Servers Editors Other Exit █ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

    █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Event Editor ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄
    █ █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Event ID 10 ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄ █
    █ Act█ █s █
    ▄▄ █ ───█ Active │ Yes █──── █▓gj!
    ▐█▄▄█ Yes█ Description │ Toss incoming echomail Sun │ No █ ░█▄▄
    ░████ Yes█ Event Type │ Semaphore Mon │ No █ ░██▒■ ▀ ▓███ Yes█ Exec Hour │ 0 Tue │ No █WTFS ░██▌▐ ▓ ▒▓▓█ No █ Exec Min │ 0 Wed │ No █WTFS ░▓░ ▓ ▀ █░░█ Yes█ Shell │ ./mutil mailin.ini Thu │ No █-T-- ░█░ ▓ ░░▓███ Yes█ Semaphore │ echomail.in|netmail.in Fri │ No █WTFS ▓ ▄▄█ ▄▄■ ▀█ Yes█ Kill After │ echomail.in|netmail.in Sat │ No █WTFS ░ ▌░░
    █ No █ Warning │ 0 █---- ░ ▀▄
    █ █ █ ░
    █ ───▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█──── █
    █ Press / for command list █
    ▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█


    +++────────────────────────────────────────────────────────────── ─── ── ─ ─ · ::: (Events) -> Active...

    So why didn't this ever run from 3/18-3/22 when I forced one on the command line
    ?

    --- Mystic BBS v1.12 A47 2021/02/12 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)
  • From Fusion to bcw142 on Mon Mar 22 19:37:16 2021
    Re: Mailin
    By: bcw142 to All on Mon Mar 22 2021 11:58 am

    ▀ █░░█ Yes█ Shell │ ./mutil mailin.ini Thu │ No █-T-- ░█░ ▓

    are you sure that wherever "." is is where the mutil binary is? does "./" override mystic's default search path?

    you could probably make an event like: "touch 123.txt" and find out where this 123.txt file is placed and see if mutil is also there..

    just random ideas ;)
  • From bcw142@21:1/145 to Fusion on Tue Mar 23 05:20:06 2021
    On 22 Mar 2021, Fusion said the following...

    Re: Mailin
    By: bcw142 to All on Mon Mar 22 2021 11:58 am

    ▀ █░░█ Yes█ Shell │ ./mutil mailin.ini Thu │ No █-T-- ░█░ ▓are you su that wherever "." is is where the mutil binary is? does "./" override mystic's default search path?you could probably make an event like: " 123.txt" and find out where this 123.txt file is placed and see if mu is also there..just random ideas ;)

    Mystic stuff all defaults to Mystic root as ".", so yes mutil is in ./mutil
    or in full /mystic/mutil so either will work there. To help counter what was happening I've created a Force Mailin & Force Mailout which say the same thing and run using DD (Unix command line basically). It works fine thus proving that ./mutil mailin.ini works since it's the same line. Linux can run most things using DD unlike Windows that needs to use a full door setup.
    I just used the Force Mailin and it worked as designed complete with feedback. The Feedback is the default mutil screen showing it working followed by a pause so you can read it then continue.

    --- Mystic BBS v1.12 A47 2021/02/12 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)