Vista - .txt file attachments corrupted

I attach a .txt file containing lines exceeding 76 characters to a Plain Text
message in WLM and it corrupts the file on send by putting a line feed after
each 76 characters.

I attach the same file to a Rich Text message in WLM and the file displays
correctly when received in WLM

For comparison, I attached the same text file in both Plain and Rich Text
format in Thunderbird and the file is intact in both cases.

Surely WLM should not modify attached files?

Pop3 or Hotmail account(hotmail.com, live.com, msn.com) ?
Does the same occur when sending the file with both types of accounts ?

--
...winston
ms-mvp mail

"John A" <JohnA@xxxxxx> wrote in message news:81CD988D-5544-4FAD-BE28-D61CA7E8004E@xxxxxx

Line length is configurable. See Tools, Options, Send, Mail Sending Format,
Plain Text Settings, "Automatically wrap text at XX characters when sending".

--
Gary VanderMolen, MS-MVP (Mail)


"John A" <JohnA@xxxxxx> wrote in message news:81CD988D-5544-4FAD-BE28-D61CA7E8004E@xxxxxx

Thanks Gary, but I assumed that referred to in-line message text, not .txt
file attachments.

"Gary VanderMolen" wrote:

It happens if I send the attachment using either my hotmail or bigpond (POP)
accounts using WLM.

However, if I send the attachment in a plain text message using Hotmail via
IE8, the attachment is sent intact.

"...winston" wrote:

I'm having exactly the same problem.

When I attach a .TXT file (with a width of >76 chars), it is
reformatted by WLMD.

Its definitely WLMD doing the reformatting as I can see the corrupted
file in "Sent Items".

I've tried various settings in WLMD but can't seem to fix it.

Does anyone have any ideas?

Thanks
Paul


On May 24, 5:43*am, John A <Jo...@xxxxxx> wrote:

You have two choices, neither of which is great.

1) Use Uuencode rather than MIME for the message format (Tools, Options,
Send. Mail, Plain Text Settings.). However if you are using HTML
format for you messages, MIME is required and you can't use this option.

2) Zip the TXT file and attach the zip file. The recipient will have to
unzip it.

This is a design flaw that goes back to the IE3 Internet Mail and News
program and was carried forward to Outlook Express and Window Live Mail.

When using MIME format, the program looks at the contents of the
attachment and if it starts with mostly text (doesn't even have to be a
TXT file), the program uses Quoted-printable encoding rather than
Base64. The designer probably thought he was being smart since in that
case their would be less encoding overhead. Unfortunately, the
quoted-printable encoding can result in corrupted attachments due to
inserted line breaks.

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm



<paulwalk@xxxxxx> wrote in message
news:04cd8603-59cb-4bbd-a7a0-ca6475c68ac5@xxxxxx

Thanks for the explanation Mike. However, this problem (for me at
least) is limited to WLMD.

My clients have been using OE for years to send TXT files that are 80
characters wide.

Its only my clients that are running WLMD that have the problem of the
text lines wrapping at 76 characters.

Paul

On Jun 4, 4:14*am, "Michael Santovec" <michael_santo...@xxxxxx>
wrote:

The design flaw doesn't guarantee that the text files will get
corrupted. It just opens a hole for that.

Look at the message source (Ctrl-F3) for the a problem message.

If the attachment shows
Content-Transfer-Encoding: quoted-printable
then it is open to problems. If it shows Base64, then it will be fine.
It will also be fine is the user used Uuencode.

An additional complication can be the implementation of

Content-Type: text/plain;
format=flowed;

Older versions of OE do not support the format=flowed; I don't recall
exactly when the format=flowed was added to OE but users on XP SP2 or
later probably have it but older versions don't.



One of the issues is the implementation of

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm



<paulwalk@xxxxxx> wrote in message
news:51cf325f-023c-4d31-a1a9-ac551b4dd30a@xxxxxx