Subj : Re: CrashMail
To   : ACCESS DENIED
From : WKITTY42
Date : Thu Jan 31 2019 07:20 pm

On 09/06/14, Access Denied said the following...
 
 AD>  te> Mystic should ignore that on newly arrived messages that are intransi
 AD>  te> to other systems... it should also strip it out of locally written
 AD>  te> messages being exported... not only the crash bit but also the direct
 AD>  te> bit and i'm thinking maybe another one or two...
 AD>
 AD> Doesn't that kinda defeat the entire purpose of the crash and direct bits
 AD> you're referring to?

no because they only pertain to the system originating the netmail messages in
question... no other system's routing settings should be overridden by my
system's settings... consider POTS connections and i drop off netmail on your
system for delivery to a node in australia... are you going to be happy when
your phone bill comes in and you are the one paying for a phone call to OZ
instead of me? ;)

 AD> Also, is there some kind of FTSC standard or proposal documented on this
 AD> so I can refer it to the Synchronet developers?

not really... this comes from the "school of hard knocks" and lessons
learned... this is also done when packing the mail... the local copy, if one
remains, still has those bits set plus the sent bit...

i might have something around here from historical development conversations
concerning this... let me look for it... there's a lot to dig through,
though...

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

.