[Info-vax] VMS-based InfoServer

[Jan-Erik Soderholm]

On 2010-08-05 22:26, VAXman- @SendSpamHere.ORG wrote:
> In article<5m0ri7-68a.ln1 at Ubuntu.mike-r.com>, Mike Rechtman<mike at rechtman.com>  writes:
>> On 05/08/10 15:27, Richard B. Gilbert wrote:
>>> Phillip Helbig---undress to reply wrote:
>>>> In article<A5mdnUwOdJEcVsTRnZ2dnUVZ_uKdnZ2d at giganews.com>, "Richard B.
>>>> Gilbert"<rgilbert88 at comcast.net>  writes:
>>>>>> What's so wrong about reading a VMS news group on a VMS system?
>>>>> There's nothing intrinsically wrong with it. I was objecting to a
>>>>> complaint about VMS mail and how it handles message formats that are
>>>>> quite common and handled correctly by most mail readers.
>>>>>
>>>>> Do you see two spaces following my first sentence in the paragraph
>>>>> above? Apparently VMS MAIL treats this as an error and replaces the
>>>>> second space with "=A0".
>>>>
>>>> NO NO NO NO NO NO NO NO NO. NO. While there are some bugs in VMS mail,
>>>> this is NOT one of them. The replacement (for which there is
>>>> absolutely no justification) is done by the sender encoding his stuff
>>>> (for no reason) in quoted-printable.
>>>>
>>>
>>> I'm not purposely sending "quoted-printable". I don't encode anything.
>>>
>>> Perhaps you are objecting to the Mozilla/Thunderbird mail/news client
>>> and whatever it's doing.
>>>
>>> I've been using it for many years reading messages and, occasionally,
>>> replying. This is the FIRST time that I have seen any complaints about
>>> the formatting of messages I have sent.
>>
>> This message is sent using Thunderbird under Linux.  I am purposely ending the
>> sentences with a period (fullstop) followed by two spaces, and letting the lines
>> run on until they wrap.
>> Hopefully there will be no "=" signs in this message -- except the one placed on
>> purpose some words back.
>> If indeed there are none, posting without QP is possible from T-Bird.
>> OTOH if there are some, I apologize and abase myself.
>
> Well Mike, you've proved that others are just inept at configuring their
> Thunderbird.
>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Content-Transfer-Encoding: 7bit
>
> Thanks.  Absolutely perfectly legible here.

Maybe. But the misstake you are doing (and I do not think that
anything will make you change) is that you think that that
is of any importance. That is, what works (or not) for you.
Of any importance to anyone but you, of course... :-)

You are upset becuse not everyone sends stuff exactly like
your old tools want it.

I have a VMS application where I had to find a way to process
mails comming in using "Simplified Chinese" encoding. There
we are not even talking single byte characters. Yes, we did
try to ask the senders to switch to "plain text", "US-ASCII"
or any other one-byte-per-character encoding, but eventualy
had to give up.