From WHATSNEW.TXT

[snip]

+ The Echomail node editor now has three new options in the / menu:

1 - Send Areafix request to the selected node
2 - Send Filefix request to the selected node
3 - Send Netmail message to Sysop of the selected node

[snip]

works really well, nice interface and easy to use. :) I do think areafix/filefix passwords should be mandatory for a given echonode before
this command is allowed to send the netmail away for a filefix/areafix
request.

[snip]

+ Mystic Message Base and File Base editors now have an /U Unsubscribe option
This command will automatically generate an Areafix or Filefix Netmail
request to unsubscribe from a base (and option to delete the base after)

[snip]

well how easy is this now :) I did a test from 1/101 to 1/100 asking for fsx_bot to be unsubbed and it worked really well. Again I think these are commands that should not work unless a areafix/filefix is loaded into a given echonodes settings. I suppose there's a very *small* chance a node and hub would run with no passwords but I'm not thinking this would have that often
if at all. So yep, something to ponder much like the above comments for the first feature mentioned earlier.

[snip]

+ The install program now has an "extract" function to go along with the
replace function. Type "install help" for more details.

[snip]

Ran this and saw..

[snip]

Syntax:

install Begin full installation
install replace <dir> Replace executables in <dir> with latest
install extract <mask> <dir> Extract file or mask into <dir>

Example:

install replace c:\mystic
install extract userchat* c:\mystic\text

[snip]

Then tested by creating a std test install from an earlier build then ran

[snip]

C:\Users\BBS\Downloads\mis112a43-20190216>install replace c:\a123test

Searching "c:\a123test\" for binaries to replace...

Replacing: c:\a123test\scripts\mide.exe OK Replacing: c:\a123test\scripts\mplc.exe OK Replacing: c:\a123test\fidopoll.exe OK Replacing: c:\a123test\mis.exe OK Replacing: c:\a123test\mutil.exe OK Replacing: c:\a123test\mystic.exe OK Replacing: c:\a123test\nodespy.exe OK Replacing: c:\a123test\qwkpoll.exe OK Replacing: c:\a123test\upgrade.exe OK

Operations complete
[snip]

also tested

[snip]

C:\Users\BBS\Downloads\mis112a43-20190216>install extract m*.mnu c:\a123test\menus

Extracting Mask: "m*.mnu to "c:\a123test\menus\"

Extracting: c:\a123test\menus\main.mnu OK Extracting: c:\a123test\menus\matrix.mnu OK Extracting: c:\a123test\menus\message.mnu OK Extracting: c:\a123test\menus\mnewscan.mnu OK Extracting: c:\a123test\menus\msearch.mnu OK

Operations complete

[snip]

It's working well... I would suggest the installer creates an install.log
file in the same directory as install.exe just to show what was installed
where and when. This would be especially useful from a debugging point of
view if the 'replace' and/or 'extract' switches are deployed. At present the output the the command prompt seems to be the only record of what was copied where, unless I am missing something?

[snip]

+ Mystic now logs the user's country in the node log along with their IP
and hostname (when country blocking is enabled)

[snip]

Yep working as intended - here's what I am seeing at 1/101

[snip]

------------------- Node 1 (Mystic v1.12 A43 2019/02/15)
2019.02.17 05:39:40 Connect from 219.89.202.104 (219-89-202-104.adsl.xtra.co.nz)
2019.02.17 05:39:40 Country: New Zealand
2019.02.17 05:39:40 Connection by Telnet


------------------- Node 1 (Mystic v1.12 A43 2019/02/15)
2019.02.17 06:01:09 Connect from 2601:0989:C100:4A50:D02E:0087:C06A:07E3 (Unknown)
2019.02.17 06:01:09 Country: United States of America
2019.02.17 06:01:09 Connection by Telnet


------------------- Node 1 (Mystic v1.12 A43 2019/02/15)
2019.02.17 06:05:34 Connect from 185.202.129.0 (Unknown)
2019.02.17 06:05:34 Country: Italy
2019.02.17 06:05:34 Connection by Telnet

[snip]

I also took a look at this one

[snip]

+ You can now press CTRL-E when editing menu settings on the Display File
field to open up the ANSI editor.

[snip]

firstly I appreciate it was a while ago but I'm kicking myself for only just noticing this change :)

WAS: Press / for command list
NOW: Press / for Menu Settings, other options

I tested the feature and it works well, it's a nice complementary feature to include.

Lastly this one goes back a little while to A40...

[snip]

+ Mystic Area/Filefix will now accept commands that start and end with a
percentage sign (as opposed to just starting with) so: %LIST and %LIST%
will work, for example.

[snip]]

I wanted to test this so used the new echonode feature mentioned at the start of this post to set up an areafix command of %list% to 1/100 and all worked well, back came the reply.

[snip]

Your AREAFIX request has been processed

Command: %LIST%
Result: List of all areas:
FSX_GEN General Chat
FSX_MYS Mystic BBS Support/Dev
FSX_BOT fsxNet BOTS
FSX_CRY Cryptographics
FSX_BBS BBS Support/Dev
FSX_DAT InterBBS Data
FSX_MAG Magicka BBS Support/Dev

[snip]

But it occurs to me the default areafix and filefix docs in /text don't
mention the changes to the command syntax, so it might pay to amend these slightly in the stock install. Just a thought.

I've yet to test MUTIL hatching, that's next up after some breakfast :)

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/02/15 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I wanted to test this so used the new echonode feature mentioned at the start of this post to set up an areafix command of %list% to 1/100 and
all worked well, back came the reply.

Thanks Paul, you've just reminded me of something that has bugged me, for
quite some time, but I'm not sure it's a bug more just me doing something odd or being lazy.

When I send an AreaFix / FileFix to the HUB, I more often than not forget to turn off my auto signature which results in AreaFix / FileFix telling me on a few lines that each line of my auto sig is not a valid command.

Is there a way to capture the fact that I am being especially lazy and didn't turn off my auto sig, and just supply me with the output from the commands I did, or to somehow recognise that I am sending a netmail to *Fix and not use auto sig for that message? I hope I'm not the only one that this happens to, and totally understand if it's just being lazy, but if there was a way to recognise the netmail to *fix would just not use the auto sig if it's enabled would be super.

This is obviously not a critical issue, it's merely aesthetics but wonder if it's already an option I have overlooked or is something easy to implement sometime?

Thanks for your thoughts and comments.

|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÄ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ

--- Mystic BBS v1.12 A43 2019/02/10 (Linux/64)
* Origin: The Quantum Wormhole, Ramsgate, UK. bbs.erb.pw (21:1/158)

On 16 Feb 2019 at 07:45p, MeaTLoTioN pondered and said...

When I send an AreaFix / FileFix to the HUB, I more often than not
forget to turn off my auto signature which results in AreaFix / FileFix telling me on a few lines that each line of my auto sig is not a valid command.

I get hit with this also. I guess g00r00 could code something to ignore it
but given it's in the message body that may be tough.

Best bet it to turn off signatures in netmail base.

L Template ³ ansimlst
Real Names ³ Yes
Autosigs ³ No
Private ³ No

That would do the trick for you :)

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/02/15 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I get hit with this also. I guess g00r00 could code something to ignore
it but given it's in the message body that may be tough.

Best bet it to turn off signatures in netmail base.

L Template ³ ansimlst
Real Names ³ Yes
Autosigs ³ No
Private ³ No

That would do the trick for you :)

Best, Paul

Genius! I never thought to look at that! I'm doing that, makes total sense. Thank you =)

|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÄ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ

--- Mystic BBS v1.12 A43 2019/02/10 (Linux/64)
* Origin: The Quantum Wormhole, Ramsgate, UK. bbs.erb.pw (21:1/158)

When I send an AreaFix / FileFix to the HUB, I more often than not
forget to turn off my auto signature which results in AreaFix /
FileFix telling me on a few lines that each line of my auto sig is not
a valid command.

When I am using an editor that adds a sig and I am sending a message to Area/Filefix I add a tearline (three "-" and a space) before I save and every Area/Filefix I have encountered stops processing commands there.

I do have to remember to add it though.. :)

Ttyl :-),
Al

... Admit Nothing..... Deny EVERYTHING..... Demand PROOF!
--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

works really well, nice interface and easy to use. :) I do think areafix/filefix passwords should be mandatory for a given echonode before this command is allowed to send the netmail away for a filefix/areafix request.

Fixed! Well, not fixed but added. :) Thanks for catching that miss!

I've cleaned up all of the functions now a bit (the Unsub did check the
proper data unlike the Area/Filefix editors but I went through and also added reasonable error messages for when/if it fails because of lack of data to generate a request.

--- Mystic BBS v1.12 A43 2019/02/15 (Linux/64)
* Origin: Sector 7 (21:1/108)

When I send an AreaFix / FileFix to the HUB, I more often than not
forget to turn off my auto signature which results in AreaFix / FileFix telling me on a few lines that each line of my auto sig is not a valid command.

There are two solutions to this. You can disable auto signatures for the Netmail base. But if you want to keep them on for regular netmails then you need to use the functions that make sending Area/Filefix requests trivial in the System Configuration (echomail nodes can netmail area/file fix or the Sysop, File/Msg base editors can automatically generate Fix messages for you).

These functions that generate the mail for you do not add your auto signature and they also make it so you don't have to worry about address or passwords
or posting to the wrong base, etc.

--- Mystic BBS v1.12 A43 2019/02/15 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 16 Feb 2019 at 02:41p, g00r00 pondered and said...

Fixed! Well, not fixed but added. :) Thanks for catching that miss!

Cool, thanks. Your welcome :)

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/02/15 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 02-16-19 14:06, Al wrote to MeaTLoTioN <=-

When I am using an editor that adds a sig and I am sending a message to Area/Filefix I add a tearline (three "-" and a space) before I save and every Area/Filefix I have encountered stops processing commands there.

I do it as standard for any Areafix message that I send. It's a habit I picked up in the 90s. :)


... Moderator Rule #4: Everyone hates you - so hate 'em back!
=== MultiMail/Linux v0.51
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

MeaTLoTioN wrote to Avon, g00r00 <=-

When I send an AreaFix / FileFix to the HUB, I more often than not
forget to turn off my auto signature which results in AreaFix / FileFix telling me on a few lines that each line of my auto sig is not a valid command.

I had the same issue here with the signature. What I did, was add a line that contained '---' into my sig file. That way, when I send an area/filefix message, it will only be processed until it gets to that line... :)



---

Black Panther
A.K.A. - Dan Richter
Sysop - Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
The sparrows are flying again...


... Steal this tagline and I'll tie-dye your cat!

___ MultiMail/Linux v0.51

--- Mystic BBS/QWK v1.12 A43 2019/02/08 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

I had the same issue here with the signature. What I did, was add a line that contained '---' into my sig file. That way, when I send an area/filefix message, it will only be processed until it gets to that line... :)

Ahh that make sense, sounds like a great idea. I might do that instead of disabling auto signature for Netmail group. Seems like a nicer way of
handling it.

|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÄ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ

--- Mystic BBS v1.12 A43 2019/02/10 (Linux/64)
* Origin: The Quantum Wormhole, Ramsgate, UK. bbs.erb.pw (21:1/158)

Ahh that make sense, sounds like a great idea. I might do that instead of disabling auto signature for Netmail group. Seems like a nicer way of handling it.

Just use the echomail node editor to send Areafix requests, its easier and you don't have to do either of those! :)

--- Mystic BBS v1.12 A43 2019/02/17 (Linux/64)
* Origin: Sector 7 (21:1/108)