Subj : Re: CrashMail
To : WKITTY42
From : ACCESS DENIED
Date : Thu Jan 31 2019 07:20 pm
Hello wkitty42,
On 06 Sep 14 21:58, wkitty42 wrote to Access Denied:
AD>> Doesn't that kinda defeat the entire purpose of the crash and
AD>> direct bits you're referring to?
wk> no because they only pertain to the system originating the netmail
wk> messages in question... no other system's routing settings should be
wk> overridden by my system's settings... consider POTS connections and i
wk> drop off netmail on your system for delivery to a node in australia...
wk> are you going to be happy when your phone bill comes in and you are
wk> the one paying for a phone call to OZ instead of me? ;)
Phone lines/modems are a thing of the past these days (at least for me). I can
understand why something was done (your explanation) about it years ago, most
definitely. Nowadays it could sing a different tune, though.
AD>> Also, is there some kind of FTSC standard or proposal documented
AD>> on this so I can refer it to the Synchronet developers?
wk> not really... this comes from the "school of hard knocks" and lessons
wk> learned... this is also done when packing the mail... the local copy,
wk> if one remains, still has those bits set plus the sent bit...
wk> i might have something around here from historical development
wk> conversations concerning this... let me look for it... there's a lot
wk> to dig through, though...
Just for my own knowledge, that would be awesome. Even if you'd like to netmail
me it that would be fine.
I'm actually leaning to be on board with you on this one. I actually mentioned
this exact idea to Rob a few days ago, when we figured out that it was the
crash bit on the Mystic downlink that made my system send directly to Janis,
even when I didn't have her configured anywhere here.
The only reason it made it to her is because of the BINKD.TXT I include in my
binkd config. Unfortunately, it ended up in her unsecure inbound directory (I'm
still trying to figure that one out, especially if she uses BINKD.TXT too, it
should have been a passwordless secure connection), and wasn't found until
about a week later. That's not a good thing, IMO.
