1. Forum
  2. Fsxnet Message
  3. FSX MYS

  • (MW) Send New e-mail

    From KnightMare@21:2/126.1 to All on Saturday, March 14, 2020 12:41:00
    Is anyone using this command effectively?

    I've still got the default menu commands set for Messaging/Comment to
    Sysop; neither of which works.

    The data string is set -> /to:SysOp

    The only thing that occurs is a redirect to the NetMail Search query.


    What am I missing?

    Salutations from Rochester, NY - (SysOp KnightMare)

    --- OpenXP 5.0.42
    * Origin: Pont KnightMare, Rochester, NY (21:2/126.1)
  • From Zip@21:1/202 to KnightMare on Saturday, March 14, 2020 20:01:35
    Hello KnightMare!

    On 14 Mar 2020, KnightMare said the following...
    The data string is set -> /to:SysOp

    Have you entered your handle in the Sysop Name field in Configuration --> General Settings? As I believe that's the one it uses...

    Best regards
    Zip

    --- Mystic BBS v1.12 A46 2020/03/11 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
  • From Bucko@21:4/131 to KnightMare on Saturday, March 14, 2020 15:01:26
    On 14 Mar 2020, KnightMare said the following...

    Is anyone using this command effectively?

    I've still got the default menu commands set for Messaging/Comment to Sysop; neither of which works.

    The data string is set -> /to:SysOp

    The only thing that occurs is a redirect to the NetMail Search query.



    I am still using it exactly like that in A45. Works fine I have just tested
    it a couple of times because I saw messages on Facebook saying it doesn't
    work. Unless it is broken in A46 it works here..

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
    * Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)
  • From g00r00@21:1/108 to KnightMare on Sunday, March 15, 2020 06:54:17
    I've still got the default menu commands set for Messaging/Comment to Sysop; neither of which works.

    Did you set your Sysop Name/Feedback fields in the System Configuration?

    --- Mystic BBS v1.12 A46 2020/03/15 (Windows/64)
    * Origin: Sector 7 (21:1/108)
  • From KnightMare@21:2/126.1 to g00r00 on Saturday, March 14, 2020 20:47:00
    Hey g00r00... Thx for the response!

    Yes... This was one of the first things I checked.

    Question... Does the /to:{name} function expect the 'e-mail' base to be
    Base ID 1... Because it is not. My fidonet netmail base holds this
    position

    Thx,

    -k

    ** 15.03.20 - 06:54, g00r00 wrote to KnightMare:

    I've still got the default menu commands set for Messaging/Comment to
    Sysop; neither of which works.

    Did you set your Sysop Name/Feedback fields in the System Configuration?

    -+- Mystic BBS v1.12 A46 2020/03/15 (Windows/64)
    + Origin: Sector 7 (21:1/108)
    Salutations from Rochester, NY - (SysOp KnightMare)

    --- OpenXP 5.0.42
    * Origin: Point KnightMare, Rochester, NY (21:2/126.1)
  • From g00r00@21:1/108 to KnightMare on Sunday, March 15, 2020 13:57:50
    Question... Does the /to:{name} function expect the 'e-mail' base to be Base ID 1... Because it is not. My fidonet netmail base holds this position

    The e-mail base is the first physical record in the message base data. There is no way to change that unless you personally modify the data files outside of Mystic. The ID itself does not matter but how did you get a different ID unless you personally modified the data files?

    --- Mystic BBS v1.12 A46 2020/03/15 (Windows/64)
    * Origin: Sector 7 (21:1/108)
  • From KnightMare@21:2/126.1 to g00r00 on Sunday, March 15, 2020 09:51:00
    I was able to shift some stuff around making the Local email base 'ID 1' again like it is in the default installation. All is well again.

    Yes... The IDs were changed many moons ago after a disagreement with
    Symantec AV. Re-added all the message bases by hand after a crash but lead with the fidonet netmail base... which now explains why I was getting the errors I did. All, said, this tail chasing excercise has been informative

    Thx for the feedback and safe travels!

    -k

    ** 15.03.20 - 13:57, g00r00 wrote to KnightMare:

    Question... Does the /to:{name} function expect the 'e-mail' base to be Kn>> Base ID 1... Because it is not. My fidonet netmail base holds this
    position

    The e-mail base is the first physical record in the message base data.
    There is no way to change that unless you personally modify the data files outside of Mystic. The ID itself does not matter but how did you get a different ID unless you personally modified the data files?

    -+- Mystic BBS v1.12 A46 2020/03/15 (Windows/64)
    + Origin: Sector 7 (21:1/108)

    Salutations from Rochester, NY - (SysOp KnightMare)

    --- OpenXP 5.0.42
    * Origin: Point KnightMare, Rochester, NY (21:2/126.1)
  • From KnightMare@21:2/126 to Zip on Sunday, March 15, 2020 21:43:46
    Yes... Looked at all the obvious stuff without resolution. g00r00 put me on
    the right path. Had the local email base located where it couldn't be
    located.

    All is fixed now... Thx for the input though!

    -k

    On 14 Mar 2020, KnightMare said the following...
    The data string is set -> /to:SysOp

    Have you entered your handle in the Sysop Name field in Configuration --> General Settings? As I believe that's the one it uses...

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
    * Origin: Rust Belt BBS, Rochester, NY, USA (21:2/126)
  • From Zip@21:1/202 to KnightMare on Monday, March 16, 2020 22:13:10
    Hello KnightMare!

    On 15 Mar 2020, KnightMare said the following...
    on the right path. Had the local email base located where it couldn't be located.

    All is fixed now... Thx for the input though!

    You're very welcome! :)

    Best regards
    Zip

    --- Mystic BBS v1.12 A46 2020/03/15 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)