1. Forum
  2. fsxNet
  3. FSX MYS

  • Messages Not Showing UP

    From Mike Dippel@21:4/176 to All on Sat Apr 23 17:57:22 2022
    I have a strange problem with the Fido conferences. I am apparently receiving the
    incoming packets because they show in the c:\mystic\msgs folder and the file names
    match the name exactly, but they don't appear when I try to read them. I have permissions to read them, so I have no idea on what the problem is.

    Any ideas?

    Mike Dippel
    mystic-hobbies.us



    --- Platinum Xpress/Win/WINServer v7.0
    * Origin: The Hobby Line! Internet - hobbylinebbs.com (21:4/176)
  • From Zip@21:1/202 to Mike Dippel on Sun Apr 24 00:39:14 2022
    Hello Mike!

    On 23 Apr 2022, Mike Dippel said the following...
    I have a strange problem with the Fido conferences. I am apparently receiving the
    incoming packets because they show in the c:\mystic\msgs folder and the file names
    match the name exactly, but they don't appear when I try to read them.

    Are the incoming packets processed by mutil (imported into the message bases)? Does mutil.log say anything?

    Best regards
    Zip

    --- Mystic BBS v1.12 A48 2022/04/03 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
  • From Mike Dippel@21:4/176 to Zip on Sat Apr 23 20:38:36 2022
    On 4/24/2022 12:37 AM, Zip wrote to Mike Dippel:

    Hello Mike!

    On 23 Apr 2022, Mike Dippel said the following...
    I have a strange problem with the Fido conferences. I am apparently receiving the
    incoming packets because they show in the c:\mystic\msgs folder and the file names
    match the name exactly, but they don't appear when I try to read them.

    Are the incoming packets processed by mutil (imported into the message bases)?
    Does mutil.log say anything?

    Best regards
    Zip

    A typical response in the logs is:

    - Apr 22 09:13:32 Execute Res: 0 Cmd: zip -qj9 c:\mystic\echomail\out\fidonet.003\fdbffc60.fr1 c:\mystic\temputil\0d4f9ca1.pkt 2>nul
    + Apr 22 09:13:32 Adding PKT to FLO (addr=3:712/1321 pkt=c:\mystic\echomail\out\fidonet.003\fdbffc60.fr1 flo=c:\mystic\echomail\out\fidonet.003\02c80529.clo)
    + Apr 22 09:13:32 Results: 0 echo, 1 net, 0 skipped in 0.30s

    It really doesn't tell me much. I receive 3 other networks fine, but not Fido. The only
    difference is: I have the Fido mail set to also transfer to my point node of 1:135/393.1
    but I don't think this is causing the problem.

    It worked fine until Terry Roati had to change his node number. Ever since then, it
    stpped working. I DO have the new node number listed in my Importmai.ini file

    The Netmail works though. I can see in the logs when it imprts and exports AREAFIX
    and FILEFIX requests.

    Mike


    --- Platinum Xpress/Win/WINServer v7.0
    * Origin: The Hobby Line! Internet - hobbylinebbs.com (21:4/176)
  • From Zip@21:1/202 to Mike Dippel on Sun Apr 24 13:52:16 2022
    Hello Mike!

    On 23 Apr 2022, Mike Dippel said the following...
    Are the incoming packets processed by mutil (imported into the message bases)?
    Does mutil.log say anything?
    A typical response in the logs is:

    - Apr 22 09:13:32 Execute Res: 0 Cmd: zip -qj9 c:\mystic\echomail\out\fidonet.003\fdbffc60.fr1

    However those are the outbound packets, not the inbound ones, or?

    Best regards
    Zip

    --- Mystic BBS v1.12 A48 2022/04/03 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
  • From Mike Dippel@21:4/176 to Zip on Sun Apr 24 09:05:42 2022
    On 4/24/2022 1:50 PM, Zip wrote to Mike Dippel:

    Hello Mike!

    On 23 Apr 2022, Mike Dippel said the following...
    Are the incoming packets processed by mutil (imported into the message
    bases)?
    Does mutil.log say anything?
    A typical response in the logs is:

    - Apr 22 09:13:32 Execute Res: 0 Cmd: zip -qj9 c:\mystic\echomail\out\fidonet.003\fdbffc60.fr1

    However those are the outbound packets, not the inbound ones, or?

    Best regards
    Zip

    You are correct. Originally I said I must be receiving incoming packets because of the
    recent date stamp, but then I realized the newer date stamp is a result of the nightly
    maintenance where it purges old messages and resets the time and date for each conference area. I used to get the feed before, so there were messages in every
    conference area already.

    It looks like I am not getting anything, so I will have to get with Terry to figure this out.

    Thanks

    Mike

    --- Platinum Xpress/Win/WINServer v7.0
    * Origin: The Hobby Line! Internet - hobbylinebbs.com (21:4/176)
  • From Zip@21:1/202 to Mike Dippel on Sun Apr 24 15:22:55 2022
    Hello Mike!

    On 24 Apr 2022, Mike Dippel said the following...
    recent date stamp, but then I realized the newer date stamp is a result
    of the nightly
    maintenance where it purges old messages and resets the time and date
    for each conference area.

    Ah, yes, that's easy to get tricked by...

    It looks like I am not getting anything, so I will have to get with
    Terry to figure this out.

    Sounds good! Keeping fingers crossed!

    Best regards
    Zip

    --- Mystic BBS v1.12 A48 2022/04/03 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
  • From Mike Dippel@21:4/175 to Zip on Sun Apr 24 15:28:16 2022
    recent date stamp, but then I realized the newer date stamp is a resu of the nightly
    maintenance where it purges old messages and resets the time and date for each conference area.

    Ah, yes, that's easy to get tricked by...

    It looks like I am not getting anything, so I will have to get with Terry to figure this out.

    Sounds good! Keeping fingers crossed!

    Got it working! Turns out that I didn't edit the mail.ini file to reflect the change in the hub's node number. I did a %RESCAN * and the messages came pouring in.

    Now I can have a great weekend!

    Mike Dippel

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/64)
    * Origin: Mystic Hobbies BBS (21:4/175)
  • From Zip@21:1/202 to Mike Dippel on Sun Apr 24 19:01:04 2022
    Hello Mike!

    On 24 Apr 2022, Mike Dippel said the following...
    Got it working! Turns out that I didn't edit the mail.ini file to
    reflect the change in the hub's node number. I did a %RESCAN * and the messages came pouring in.

    Ah! That's great news! :)

    Now I can have a great weekend!

    Enjoy! :)

    Myself, I've been editing events, moving some Mystic directories off the NAS and other stuff like that today. Time for some rest soon... :)

    Best regards
    Zip

    --- Mystic BBS v1.12 A48 2022/04/03 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
  • From Mike Dippel@21:4/176 to Zip on Sun Apr 24 19:54:30 2022
    On 4/24/2022 6:59 PM, Zip wrote to Mike Dippel:

    Hello Mike!

    On 24 Apr 2022, Mike Dippel said the following...
    Got it working! Turns out that I didn't edit the mail.ini file to reflect the change in the hub's node number. I did a %RESCAN * and the messages came pouring in.

    Ah! That's great news! :)

    Now I can have a great weekend!

    Enjoy! :)

    Myself, I've been editing events, moving some Mystic directories off the NAS and other stuff like that today. Time for some rest soon... :)

    Best regards
    Zip

    Enjoy!

    Mike

    --- Platinum Xpress/Win/WINServer v7.0
    * Origin: The Hobby Line! Internet - hobbylinebbs.com (21:4/176)