LM Breaking Attachments

It seems that Live Mail is breaking my attachments. These attachments are
tab-delimited data files some 103 columns wide. After attaching and sending,
the attached file has been modifed with line breaks inserted every ~76
characters.

Uh, wha?

The data itself is all very standard TSV, no unusual characters (I'm not
posting a sample as all I have is client data at the moment).

The version of LM is 2008 build 12.0.1606

Has anybody else encountered this and, hopefully, found a solution?

On Mon, 28 Apr 2008 14:04:01 -0700, Scott wrote:
Tools > Options > Send > Mail Sending Format > Plain Text Settings...

Standard text wrap is 72 - 76 characters (WLM default is 76). If you are
sending from WLM, and seeing wrap at 76 characters, change it. I have not
checked the effect of changing it on received email; could be that the
sending client (if different) also needs to be adjusted.
Hopefully, changing the setting as described will help.

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum

Should text-wrap settings be affecting attachments?
I don't think so.

--
Gary VanderMolen, MS-MVP (WLMail)


"N. Miller" <anonymous@xxxxxx> wrote in message news:1ig7kdo9smfbx$.dlg@xxxxxx

Take a look at the message source (Ctrl-F3) for the message in your Sent
Items. What does it show the attachment encoding. Assuming you are
using MIME format, it's probably

Content-Type: application/octet-stream;
name=
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;

In the source you would see the longer lines broken with the first part
ending in an = at the line wrap point.

But it should be put back together on the recipient's end.

If you send it to yourself, does it come back OK in WLM? If so it could
be an issue with the recipient's program not handling quoted-printable
attachments. Or an anti-spam or anti-virus program could be mangling
the quoted-printable.

In that case, you might try zipping the file and sending that.

I just did a quick test with a CSV file with long lines sending and
receiving in WLM and it came back fine.

--

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


"Scott" <Scott@xxxxxx> wrote in message
news:F3127137-FA9D-4B4F-8756-86CEA06ACE08@xxxxxx

I can't think of a reason why there would be any difference between CSV and
TSV file handling, but the TSV is getting a Mime type of text/plain. Could
that inhibit the receiving application from correctly reassembling the file?

The source mime header looks like:

Content-Type: text/plain;
format=flowed;
name="A0802_Data_0008a.tab";
reply-type=original
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="A0802_Data_0008a.tab"

Yes, sending to myself Live Mail: I can read the resulting file correctly.
However, I don't necessarily think this is on the receiving end as I have
been sending this same file, more or less, on a regular basis from Outlook/OE
to the same recipient. The only process change appears to be WLM.

I do always have my mail readers set to send/receive plain text only. This
shouldn't affect attachments though, right?

Thanks for your help.

"Michael Santovec" wrote:

That you can send the file to yourself and that it arrives OK says that
the attachment is OK.

That means that something is going wrong on the recipient's end, or
something in between you and the recipient, such as a mail server or
anti-virus/anti-spam software.

The Content-Type: text/plain; format=flowed;
looks risky. Some software has no qualms about reformatting text in
messages.

I don't have a .TAB file type, so I'm guessing that's something you
created and gave the text/plain MIME type. What you could do is rename
the file extension before sending to something like .XXX. That should
get the Content-Type: application/octet-stream; since it's an unknown
file type in your Windows and see if that makes it to the recipient OK.

But the safest thing to do is to zip the file before sending. That
makes a bit more work for you and the recipient. but the file will
arrive in tact.

You mention previously using Outlook and Outlook Express. I don't know
how Outlook handles text file attachments, but WLM is doing the same
thing that Outlook Express always has.

If things have suddenly changed, it might be a new anti-virus or
anti-spam program on the recipient's end.

--

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


"Scott" <Scott@xxxxxx> wrote in message
news:3E3157EF-C39B-4F0E-A470-4329F2E3E3B1@xxxxxx