NA> - What is the maximum size of an Areafix request in Mystic?
Short answer is it can do what you want. But I'll expand...
Mystic will process the first 1000 lines before I decides its a troll message,
but you can use wildcards, boolean searches, and/or %ALL type commands to sub
to large numbers. There is no limitation.
NA> - How many total Echomail areas can Mystic handle?
65000 but I can easily expand that to 4 billion if needed. I just haven't
because it involves a record change, and no one has ever came close. Highest I
have seen is in the 10,000s with Mystic.
NA> - If he chose to use Mystic, and if Mystic handles Passthru areas, does
NA> it automatically clean-up unused passthru areas (areas with one link
NA> left, that of the uplink). For example, this downlink gets a rescan of
NA> the last 100 messages, and most of these Usenet groups are deadwood. He
NA> decides later that he wants to un-Areafix the deadwood from my system. Can
NA> he run some sort of report or process on his proverbial Mystic
NA> system to do so?
Yes it can do all of these things although some is just being enabled in the
A48 versions.
You can configure a threshold to interact with echomail areas based on the date
they were created and the date of the last message and then take actions which
can be any combination or all of:
1) Send a report to the SysOp with candidates for removal
2) Physically remove the base from configuration and disk
3) Automatically unsubscribe via Areafix with your uplink
The report goes to the SysOp account which will then push to mobile devices via
Internet e-mail if using those servers. If you choose to do ONLY the report,
Mystic also has options to instantly delete and unsubscribe with automatically
generated AreaFix within the Message base editor at the touch of a button. You
simply highlight the base and select "Unsubscribe" and Mystic does everything
else from removing uplinks via Areafix, removing downlinks, cleaning up
diskspace.
Or like I said, you can have Mystic automate all of it and then send you a
report of what it did.
Mystic also has automation for creating echomail areas as well when it
encounters them so it can handle automating the full lifecycle of an echo.
You can also do wildcard-based excludes from the unlinking so if you wanted FSX
network to be excluded you could say exclude any echotag that starts with FSX_
for example.
Here are some things it does in terms of hub features off the top of my head:
Automatic create of echomail/file echo areas
Automatic generation of Area/Filefix unsubscribe messages from config UI
Automatic reset of echomail stats per node after time intervals
Automatic deactivation of up/downlinks after configured node inactivity
Automatic unsubscribe of msg/file networked bases for inactive downlinks
Automatic outbound file cleanup for inactive downlinks
Automatic convert from crash to hold if connection errors threshhold is met
Automatic Areafix/Filefix request generation from config UI
Automatic SysOp Netmail generation from config UI
Automatic removal of inactive message bases including auto Areafix generation
Automatic removal of inactive file bases including Filefix generation
AES-256 encrypted Fix requests when communicating with compatible hub (no
cleartext passwords flying around).
And here is an example of a report that it generates when set to "Notify" only
scanning for dormant echomail bases:
The following bases are candidates for removal due to inactivity:
ID EchoTag Created Last Post
------ ---------------------------------------- ------------ -----------
8 SCIMYSTIC 16 Jan 2021 19 Jun 2021
14 FSX_TST 21 Oct 2021 21 Oct 2021
This feature in the current A48 is actually disabled until I finish testing the
automated delete stuff but I will make it a point to do that tonight and upload
a new version with it enabled so it'll be available within the next day or so.
--- Mystic BBS v1.12 A48 2022/02/10 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)
|
