TID: FMail-lnx64 2.1.0.18-B20170815
RFC-X-No-Archive: Yes
TZUTC: 0200
CHRS: UTF-8 2
PID: GED+LNX 1.1.5-b20161221
MSGID: 2:280/464 6077fed3
REPLY: 1:153/7001 60775c7c
Hi Maurice,

On 2021-04-14 21:19:56, you wrote to me:

 WvV>> It doesn't conform to the standard.

 MK> Understood.  Not a big deal as it could easily become redundant and
 MK> unneeded once a real standard is in place that doesn't require ANY
kludges.

So you want to replace FTN with something else? Good luck with that...

Don't be that Don Quichot fighting the imaginary windmills... ;-)

 WvV>> It doesn't conform to the standard either...

 MK> I believe you are wrong about that but then again you're spin on it might
 MK> have validity simply because of obsolesence.  So far the only issue I have
 MK> seen is on one particular point software that buggers up the REPLY kludge
 MK> but has no effect on what really matters.

Your sample is way to small to conclude anything...

 MK> Speaking of nonconformity and obsolesence what is the deal with your
 MK> bogus CHRS kludge? -> "CHRS: UTF-8 2"

I am aware of it, but havent' taken the time to fix it. More important things
to do...

 MK> It might make someone question your credibilty on mattters of
 MK> conformance to "standards".  Not me of course but then I am not that
 MK> anal when it comes to conformance to phoney-baloney kludges.

Yet you viciously mention it...


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 1/123 18/200 90/1 105/81 120/340 123/131 124/5016 129/305
SEEN-BY: 154/10 203/0 221/0 226/30 227/114 229/101 424 426 452 664
SEEN-BY: 229/700 1016 1017 240/5832 249/110 206 317 400 280/464 5003
SEEN-BY: 282/1038 288/100 292/8125 301/1 310/31 317/3 322/757 342/200
SEEN-BY: 396/45 423/120 460/58 633/280 770/1
PATH: 280/464 229/101 426