Yenc will never be supported by MS products. MS states that there are too
many problems with it and suggested revisions to bring it to a decent format
before usage became popular but many of the News/eMail client people
wouldn't listen so now you have a de facto standard that isn't up to the
current technology elsewhere. What is the point? There is really no benefit
to it anymore.

Since most people use the news client that their system came with Yenc will
disappear but then so will Usenet.

-------
"Swingman" wrote in message
...
Does yEnc now comply with the RFC 977/3977 for NNTP?

Unless there has been a recent change it never has; and although it did
become popular during the days of dialup, last time I ran an nntp server
a few years back yEnc was still NON STANDARD in that it was not RFC
977/3977 compliant.

My problem with yEnc was that there always seemed to be plenty of errors
that resulted in corrupted files when least expected ... it was simply
not always reliable.

.... and just because a news reader can't read yEnc does not mean that
newsreader is "crippled".

Anything that can _post and read_ UseNet messages to NNTP standards in
the applicable RFC's is a "real" nttp client.

The proof is in the pudding ... and unless there has been a recent
change, yEnc is not one of the ingredients for compliance with the
appropriate NNTP RFC's.