1. Forum
  2. Fsxnet Message
  3. FSX MYS

  • Re: Suggestion (2)

    From Avon@21:1/101 to g00r00 on Monday, January 08, 2018 11:48:30
    On 01/08/18, Avon pondered and said...

    In Echomail Node editor, page 4 (BinkP) can you please make the hostname

    I'm on a roll..

    On page one, would you consider adding two extra fields for the echomail record?

    1. Sysop Name
    2. System/BBS Name

    I currently use description for both but would think if there was a way to
    (in the future) to generate reports ex Mystic of Echomail Node information
    that might be posted (stats traffic by node for example) or exported /
    imported between Mystic systems (migrating some nodes between HUBs as NETs grow) then these two extra fields would be good to have in addition to the description field... which can become more of a comments field...

    Just a thought :)

    Best, Paul


    `I'm not expendable, I'm not stupid, and I'm not going' - Kerr Avon, Blake's 7

    --- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Nugax@21:1/107 to All on Sunday, January 07, 2018 17:14:49
    Agree

    On 05:48 08/01 , Avon wrote:
    On 01/08/18, Avon pondered and said...

    In Echomail Node editor, page 4 (BinkP) can you please make the hostname

    I'm on a roll..

    On page one, would you consider adding two extra fields for the echomail >record?

    1. Sysop Name
    2. System/BBS Name

    I currently use description for both but would think if there was a way to >(in the future) to generate reports ex Mystic of Echomail Node information >that might be posted (stats traffic by node for example) or exported / >imported between Mystic systems (migrating some nodes between HUBs as NETs >grow) then these two extra fields would be good to have in addition to the >description field... which can become more of a comments field...

    Just a thought :)

    Best, Paul


    `I'm not expendable, I'm not stupid, and I'm not going' - Kerr Avon, Blake's 7

    --- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)


    --
    yrNews Usenet Reader for iOS
    http://appstore.com/yrNewsUsenetReader

    --- Mystic BBS/NNTP v1.12 A38 2018/01/01 (Linux/64)
    * Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)
  • From g00r00@21:1/108 to Avon on Monday, January 08, 2018 15:07:03
    On page one, would you consider adding two extra fields for the echomail record?

    1. Sysop Name
    2. System/BBS Name

    I am going to add in the Sysop Name field for now, so you'll have to continue usiong the Description has the BBS Name (which is sort of what it is intended for anyway).

    The reason I am adding in 'Sysop' field is because I plan to add in options
    to:

    1) Send Areafix
    2) Send Filefix
    3) Netmail SysOp

    All directly from the echomail node editor.

    --- Mystic BBS v1.12 A39 2018/01/08 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From Static@21:2/140 to g00r00 on Monday, January 08, 2018 16:28:35
    On 01/08/18, g00r00 said the following...

    3) Netmail SysOp

    Any way to set netmail flags on compose?

    --- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
    * Origin: Subcarrier BBS (21:2/140)
  • From Avon@21:1/101 to g00r00 on Tuesday, January 09, 2018 11:53:55
    On 01/08/18, g00r00 pondered and said...

    I am going to add in the Sysop Name field for now, so you'll have to continue usiong the Description has the BBS Name (which is sort of what
    it is intended for anyway).

    Thank you.

    The reason I am adding in 'Sysop' field is because I plan to add in options to:

    1) Send Areafix
    2) Send Filefix
    3) Netmail SysOp

    Sounds reasonable. Do you think you can add some MCI codes to take advantage
    of the description field also?

    Best, Paul


    `I'm not expendable, I'm not stupid, and I'm not going' - Kerr Avon, Blake's 7

    --- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From g00r00@21:1/108 to Static on Monday, January 08, 2018 19:02:40
    3) Netmail SysOp

    Any way to set netmail flags on compose?

    What would you set? Direct vs not?

    --- Mystic BBS v1.12 A39 2018/01/08 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From g00r00@21:1/108 to Avon on Monday, January 08, 2018 19:03:25
    Sounds reasonable. Do you think you can add some MCI codes to take advantage of the description field also?

    I am a little confused by this one. Where would this be used?

    --- Mystic BBS v1.12 A39 2018/01/08 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From Avon@21:1/101 to g00r00 on Tuesday, January 09, 2018 13:58:13
    On 01/08/18, g00r00 pondered and said...

    Sounds reasonable. Do you think you can add some MCI codes to take advantage of the description field also?

    I am a little confused by this one. Where would this be used?

    Well I was thinking if you could use the Sysop field in some templates that could be edited to send Areafix / Filefix responses from a HUB, then having
    the ability to include the data stored in the description field in that template (if the sysop so wished to include it) would be a nice option to
    have. Likewise if there was a netmail template that could be used with your proposed send netmail option, then having the same kind of thing there..

    I hope that kind of makes sense. :)

    Best, Paul


    `I'm not expendable, I'm not stupid, and I'm not going' - Kerr Avon, Blake's 7

    --- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Static@21:2/140 to g00r00 on Monday, January 08, 2018 21:34:48
    On 01/08/18, g00r00 said the following...

    Any way to set netmail flags on compose?
    What would you set? Direct vs not?

    Likely Freq, Killsent and/or Direct. Crash/Immediate might also be useful for anyone not already crashing by default. Mind you I'm not 100% certain of how Mystic handles direct. My old Frontdoor setup would just pull the node's number from the nodelist and dial it if available.

    --- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
    * Origin: Subcarrier BBS (21:2/140)
  • From Nugax@21:1/107 to All on Monday, January 08, 2018 22:22:54
    Sweet

    On 09:07 08/01 , g00r00 wrote:
    On page one, would you consider adding two extra fields for the echomail record?

    1. Sysop Name
    2. System/BBS Name

    I am going to add in the Sysop Name field for now, so you'll have to continue >usiong the Description has the BBS Name (which is sort of what it is intended >for anyway).

    The reason I am adding in 'Sysop' field is because I plan to add in options >to:

    1) Send Areafix
    2) Send Filefix
    3) Netmail SysOp

    All directly from the echomail node editor.

    --- Mystic BBS v1.12 A39 2018/01/08 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)


    --
    yrNews Usenet Reader for iOS
    http://appstore.com/yrNewsUsenetReader

    --- Mystic BBS/NNTP v1.12 A38 2018/01/01 (Linux/64)
    * Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)