I'm using OE6 (6.00.2800.1123) on Win2K SP4, everything is up to date.
When I send an email with a pdf attached, it is being attached with the
headers:
Content-Type: application/pdf;
name="200411SB1043-S-0.pdf"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="200411SB1043-S-0.pdf"

When this email is received by a Hotmail recipient, the pdf is corrupt. I've
compared the original and received pdf, and certain lines of data are being
truncated. Hence the corruption.

I've checked, and as expected other binary attachments are being encoded in
base64. Admittedly, Hotmail is the only client that appears to corrupt the
file, but this encoding behaviour shouldn't be occuring. A PDF not always,
but will often contain binary data, and should be encoded in base64 to get
around this type of problem.

Many thanks
John

OE decides on Base64 or quoted-printable encoding based on the file
contents. If the beginning of the file is mostly simple text, it uses
Quoted-printable.

If you look at the PDF file in Notepad, you'll see what OE sees.

This probably typically occurs with small, simple PDF files. Larger PDF
files including those with various fonts and graphics will be sent in
Base64.

A couple of things you can do, but neither of them great:

Use Uuencode rather than MIME in the mail sending format. But this
isn't idea and isn't compatible with HTML messages.

Or Zip the PDF file before sending. That will force the Base64. But
the recipient will have to unzip it.

--

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


"oobayly" wrote in message
...
I'm using OE6 (6.00.2800.1123) on Win2K SP4, everything is up to date.
When I send an email with a pdf attached, it is being attached with
the
headers:
Content-Type: application/pdf;
name="200411SB1043-S-0.pdf"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="200411SB1043-S-0.pdf"

When this email is received by a Hotmail recipient, the pdf is
corrupt. I've
compared the original and received pdf, and certain lines of data are
being
truncated. Hence the corruption.

I've checked, and as expected other binary attachments are being
encoded in
base64. Admittedly, Hotmail is the only client that appears to corrupt
the
file, but this encoding behaviour shouldn't be occuring. A PDF not
always,
but will often contain binary data, and should be encoded in base64 to
get
around this type of problem.

Many thanks
John

Michael,
Thanks for the response, I had kinda guessed the OE isn't looking to far
down the file, the 1st 520 odd bytes are plain ascii and then the binary data
begins. This is in a 85KB pdf, so it's a tiny percentage that is ascii (0.01%
in fact).
Out pdfs have several embedded fonts & images, so I'd have hoped that OE
could pick this up.
Regarding your solution, zipping was my 1st thought, but not a viable option
in our office. We also prefer sending mails in html, so UUencoding is not
ideal, as you said.
Maybe it's a good excuse to get Thunderbird on everyones machines.

"Michael Santovec" wrote:

OE decides on Base64 or quoted-printable encoding based on the file
contents. If the beginning of the file is mostly simple text, it uses
Quoted-printable.

If you look at the PDF file in Notepad, you'll see what OE sees.

This probably typically occurs with small, simple PDF files. Larger PDF
files including those with various fonts and graphics will be sent in
Base64.

A couple of things you can do, but neither of them great:

Use Uuencode rather than MIME in the mail sending format. But this
isn't idea and isn't compatible with HTML messages.

Or Zip the PDF file before sending. That will force the Base64. But
the recipient will have to unzip it.

--

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


"oobayly" wrote in message
...
I'm using OE6 (6.00.2800.1123) on Win2K SP4, everything is up to date.
When I send an email with a pdf attached, it is being attached with
the
headers:
Content-Type: application/pdf;
name="200411SB1043-S-0.pdf"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="200411SB1043-S-0.pdf"

When this email is received by a Hotmail recipient, the pdf is
corrupt. I've
compared the original and received pdf, and certain lines of data are
being
truncated. Hence the corruption.

I've checked, and as expected other binary attachments are being
encoded in
base64. Admittedly, Hotmail is the only client that appears to corrupt
the
file, but this encoding behaviour shouldn't be occuring. A PDF not
always,
but will often contain binary data, and should be encoded in base64 to
get
around this type of problem.

Many thanks
John

You might be able to fake out the system via changing the registry
information.

Go to

HKEY_CLASSES_ROOT\.pdf

and change the

Content type application/pdf

to

application/octet-stream

which is what is used for generic binary files.

See then how OE embeds the pdf file. If that fixes it, then make sure that
change didn't affect Acrobat or any other program that uses pdf files. I
don't think it will.

steve



"oobayly" wrote in message
...
Michael,
Thanks for the response, I had kinda guessed the OE isn't looking to far
down the file, the 1st 520 odd bytes are plain ascii and then the binary
data
begins. This is in a 85KB pdf, so it's a tiny percentage that is ascii
(0.01%
in fact).
Out pdfs have several embedded fonts & images, so I'd have hoped that OE
could pick this up.
Regarding your solution, zipping was my 1st thought, but not a viable
option
in our office. We also prefer sending mails in html, so UUencoding is not
ideal, as you said.
Maybe it's a good excuse to get Thunderbird on everyones machines.

"Michael Santovec" wrote:

OE decides on Base64 or quoted-printable encoding based on the file
contents. If the beginning of the file is mostly simple text, it uses
Quoted-printable.

If you look at the PDF file in Notepad, you'll see what OE sees.

This probably typically occurs with small, simple PDF files. Larger PDF
files including those with various fonts and graphics will be sent in
Base64.

A couple of things you can do, but neither of them great:

Use Uuencode rather than MIME in the mail sending format. But this
isn't idea and isn't compatible with HTML messages.

Or Zip the PDF file before sending. That will force the Base64. But
the recipient will have to unzip it.

--

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


"oobayly" wrote in message
...
I'm using OE6 (6.00.2800.1123) on Win2K SP4, everything is up to date.
When I send an email with a pdf attached, it is being attached with
the
headers:
Content-Type: application/pdf;
name="200411SB1043-S-0.pdf"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="200411SB1043-S-0.pdf"

When this email is received by a Hotmail recipient, the pdf is
corrupt. I've
compared the original and received pdf, and certain lines of data are
being
truncated. Hence the corruption.

I've checked, and as expected other binary attachments are being
encoded in
base64. Admittedly, Hotmail is the only client that appears to corrupt
the
file, but this encoding behaviour shouldn't be occuring. A PDF not
always,
but will often contain binary data, and should be encoded in base64 to
get
around this type of problem.

Many thanks
John

The potential problem with that is that OE inserts the content type in
the attachment MIME header. Some non-Microsoft mail programs give
priority to the content type over the file extension, so they might not
recognize the attachment as being for Acrobat but rather some generic
unknown file type.

--

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


"Steve Cochran" wrote in message
...
You might be able to fake out the system via changing the registry
information.

Go to

HKEY_CLASSES_ROOT\.pdf

and change the

Content type application/pdf

to

application/octet-stream

which is what is used for generic binary files.

See then how OE embeds the pdf file. If that fixes it, then make sure
that change didn't affect Acrobat or any other program that uses pdf
files. I don't think it will.

steve



"oobayly" wrote in message
...
Michael,
Thanks for the response, I had kinda guessed the OE isn't looking to
far
down the file, the 1st 520 odd bytes are plain ascii and then the
binary data
begins. This is in a 85KB pdf, so it's a tiny percentage that is
ascii (0.01%
in fact).
Out pdfs have several embedded fonts & images, so I'd have hoped that
OE
could pick this up.
Regarding your solution, zipping was my 1st thought, but not a viable
option
in our office. We also prefer sending mails in html, so UUencoding is
not
ideal, as you said.
Maybe it's a good excuse to get Thunderbird on everyones machines.

"Michael Santovec" wrote:

OE decides on Base64 or quoted-printable encoding based on the file
contents. If the beginning of the file is mostly simple text, it
uses
Quoted-printable.

If you look at the PDF file in Notepad, you'll see what OE sees.

This probably typically occurs with small, simple PDF files. Larger
PDF
files including those with various fonts and graphics will be sent
in
Base64.

A couple of things you can do, but neither of them great:

Use Uuencode rather than MIME in the mail sending format. But this
isn't idea and isn't compatible with HTML messages.

Or Zip the PDF file before sending. That will force the Base64.
But
the recipient will have to unzip it.

--

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


"oobayly" wrote in message
...
I'm using OE6 (6.00.2800.1123) on Win2K SP4, everything is up to
date.
When I send an email with a pdf attached, it is being attached
with
the
headers:
Content-Type: application/pdf;
name="200411SB1043-S-0.pdf"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="200411SB1043-S-0.pdf"

When this email is received by a Hotmail recipient, the pdf is
corrupt. I've
compared the original and received pdf, and certain lines of data
are
being
truncated. Hence the corruption.

I've checked, and as expected other binary attachments are being
encoded in
base64. Admittedly, Hotmail is the only client that appears to
corrupt
the
file, but this encoding behaviour shouldn't be occuring. A PDF not
always,
but will often contain binary data, and should be encoded in
base64 to
get
around this type of problem.

Many thanks
John

Yeah, but if you look under that registry key, it still defines Acrobat as
the program to open it, so it might work. I've seen image associations
messed up with that content-type and they had some problems rendering in OE,
I think , but would still open when saved and then opened with whatever
program. For a pdf, you aren't going to render that with OE.

I thought it might be a neat tricky workaround, but maybe it won't work.

steve

"Michael Santovec" wrote in message
...
The potential problem with that is that OE inserts the content type in the
attachment MIME header. Some non-Microsoft mail programs give priority to
the content type over the file extension, so they might not recognize the
attachment as being for Acrobat but rather some generic unknown file type.

--

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


"Steve Cochran" wrote in message
...
You might be able to fake out the system via changing the registry
information.

Go to

HKEY_CLASSES_ROOT\.pdf

and change the

Content type application/pdf

to

application/octet-stream

which is what is used for generic binary files.

See then how OE embeds the pdf file. If that fixes it, then make sure
that change didn't affect Acrobat or any other program that uses pdf
files. I don't think it will.

steve



"oobayly" wrote in message
...
Michael,
Thanks for the response, I had kinda guessed the OE isn't looking to far
down the file, the 1st 520 odd bytes are plain ascii and then the binary
data
begins. This is in a 85KB pdf, so it's a tiny percentage that is ascii
(0.01%
in fact).
Out pdfs have several embedded fonts & images, so I'd have hoped that OE
could pick this up.
Regarding your solution, zipping was my 1st thought, but not a viable
option
in our office. We also prefer sending mails in html, so UUencoding is
not
ideal, as you said.
Maybe it's a good excuse to get Thunderbird on everyones machines.

"Michael Santovec" wrote:

OE decides on Base64 or quoted-printable encoding based on the file
contents. If the beginning of the file is mostly simple text, it uses
Quoted-printable.

If you look at the PDF file in Notepad, you'll see what OE sees.

This probably typically occurs with small, simple PDF files. Larger
PDF
files including those with various fonts and graphics will be sent in
Base64.

A couple of things you can do, but neither of them great:

Use Uuencode rather than MIME in the mail sending format. But this
isn't idea and isn't compatible with HTML messages.

Or Zip the PDF file before sending. That will force the Base64. But
the recipient will have to unzip it.

--

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


"oobayly" wrote in message
...
I'm using OE6 (6.00.2800.1123) on Win2K SP4, everything is up to
date.
When I send an email with a pdf attached, it is being attached with
the
headers:
Content-Type: application/pdf;
name="200411SB1043-S-0.pdf"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="200411SB1043-S-0.pdf"

When this email is received by a Hotmail recipient, the pdf is
corrupt. I've
compared the original and received pdf, and certain lines of data are
being
truncated. Hence the corruption.

I've checked, and as expected other binary attachments are being
encoded in
base64. Admittedly, Hotmail is the only client that appears to
corrupt
the
file, but this encoding behaviour shouldn't be occuring. A PDF not
always,
but will often contain binary data, and should be encoded in base64
to
get
around this type of problem.

Many thanks
John

Hi John,

You can try our product Advanced PDF Repair. It is a powerful tool to
repair corrupt or damaged PDF documents.

Please visit http://www.datanumen.com/apdfr/index.htm for detailed
information about Advanced PDF Repair.

And you can also download a free demo version at
http://www.datanumen.com/apdfr/apdfr.exe

Alan Chen
DataNumen, Inc. - World leader in data recovery technologies
Website: http://www.datanumen.com
Fax: +1-800-9917-FAX (US Toll-Free), +852-31829286 (HONG KONG)