On 09/07/14, Psi-Jack said the following...

In there has Netmail Crash, Netmail Hold, and Netmail Killsent. Now, I agree with only 2 of these being there, Netmail Hold, and Netmail Killsent. but Crash, should NEVER be globally enabled because it's not likely to be able to get to its destination unless Mystic itself is able to directly, and securely establish a connection to the destination node it's intended for.

i allow some of my users to crash netmails to remote systems... yes, even systems that i do not have a secure password with... the crash option is a sysop selectable choice and i see no problems with it... if users can choose
it is another option that the sysop can decide on...

Netmail flags like this would actually be better in actual message editor options to be able to set certain features. In fact, just an example
that Janis provided me with for BBBS, which Mystic could still do better with the editor menu options more dynamically:

let's not forget that BBBS is a completely different animal... keep reading...

In BBBS's example though, when setting the subject, one could use various subject lines, the first character (or first few characters, I guess depending on if it supports multiple flags or not), would be something like:

BBBS is the /only/ system that i'm aware of that allows choices like this via the subject line... pretty much every other system uses the normal message status bits and the operator's choice if users can set these bits or not...

This could be done in Mystic's Menu to set Crash, or if you set crash
and then set hold, remove crash and set hold. Attach of course would let you upload a file that would be attached to the specific message. I
don't recall what file request would be used for though.

crash/hold has a specific meaning in the BSO world... it is how the old style binkleyterm compatible software handles the DIRect message status bit...

the filre request bit is set when a FREQ is created... the subject line contains the name of the file being requested as well as an possible password necessary to access the file... one file may be requested per message... if multiple files are being requested in one session, then the system should create multiple netmails with the FREQ bit set and the name of the file in the subject line with the password if needed...

This, on a per-message basis, with ACS restrictions to be able to set attach, crash, hold, and possibly file request messages, all
specifically and only on any Message Base where type is NetMail. There
was one missing one I think from Janis's example, which is Direct, which Crash itself simply means, Direct AND Now, rather than just Direct when the system does it's normal polls.

ummm, no... CRAsh means when the events allow... IMMediate means now regardless of the event settings... there's also routing to deal with... DIRect overrides routing... but then BSO has some limitations and these are right up in the midst of those limitations...

Anyway, I hope to see something like this fixed, because the global
option for Netmail Crash is generally a horrendously bad idea. :)

really? if the sysop has no problems with the netmail going out right now if the current event allows for it?

oh wait... mystic doesn't (yet??) allow for mailer events which qualify mail
to be sent or not...

;)

--- Mystic BBS v1.10 A51 (Windows)
* Origin: (46:1/132)
þ Synchronet þ thePharcyde_ >> telnet://bbs.pharcyde.org (Wisconsin)