Looks like a restart was needed for Mystic to recongize the Allow Unsecure.
Just got a netmail from a fellow user and it appears to come
in just fine. The reply should go through the routed system as I
believe it should be. I will see what happens at this point.
Netmail unsecure seems fine, however, echomail on the other hand
should be disregarded and should be secure because of abusers.
Looks like a restart was needed for Mystic to recongize the Allow Unsecure.
I disagree with you on that point as how "it should be".
There is no real downside on sending netmails crash.
Looks like a restart was needed for Mystic to recongize the Allow Unsecure.
Good to hear you have sorted it out.
Even better to hear that this aehm ... "questionable default" (to put it very politely) will be changed in the future.
Just got a netmail from a fellow user and it appears to come
in just fine. The reply should go through the routed system as I believe it should be. I will see what happens at this point.
It depends on weather you set the crash flag on your reply.
I disagree with you on that point as how "it should be".
There is no real downside on sending netmails crash.
Netmail unsecure seems fine, however, echomail on the other hand should be disregarded and should be secure because of abusers.
We are completely on the same page here.
Echomail should only be accepted by known secure links.
I do not know of any tosser that would do it differently.
Looks like a restart was needed for Mystic to recongize the Allow Unsecure.
Did this reset, also affect the real name setting for this area? ;)
Hi all,
Looks like a restart was needed for Mystic to recongize the Allow Unsecure. >Just got a netmail from a fellow user and it appears to come in just fine. >The reply should go through the routed system as I believe it should be. I >will see what happens at this point.
Thanks guys for your input, regardless of how it was handled. It was >constructive. Netmail unsecure seems fine, however, echomail on the other >hand should be disregarded and should be secure because of abusers.
-- cr1mson
--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)
namesLooks like a restart was needed for Mystic to recongize theAllow
Unsecure.
Did this reset, also affect the real name setting for this area? ;)
No, that was intentional. ;) I did set my Fidonet echoes to use real
just a moment ago though. Let me know if you see my alias or otherwise.
Chad Adams wrote to All on 12-10-17 12:32 <=-
Yea anytime you change settings in Mystic, go ahead and restart mis
On 18:02 09/12 , cr1mson wrote:
Hi all,
Looks like a restart was needed for Mystic to recongize the Allow Unsecure.
Just got a netmail from a fellow user and it appears to come in just fine.
The reply should go through the routed system as I believe it should be. I
will see what happens at this point.
Thanks guys for your input, regardless of how it was handled. It was
constructive. Netmail unsecure seems fine, however, echomail on the other
hand should be disregarded and should be secure because of abusers.
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495934:04:26 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 286,919 |