> Someone sends me a pdf file as an attachment. I receive it in Eudora,
> open it with Adobe Reader, or Acrobat, and it has no text or images.
> All pages are blank.
>
> If I go to the server website -- before Eudora has processed the
> attachment -- and open it there it works fine.
> So it looks as if Eudora is scrambling the file somehow.
> On Thu, 24 May 2007 10:39:40 -0500:
>
> Do you mean that you *download*the*attachment* from that server
> to your computer, and then open it locally on your computer,
> or that the "web server" itself interprets it,
> and then displays it in your web browser?
I've tried both. I use Eudora to download the message and attachments
to my hard disk, then open with Acrobat Reader and get blank pages.
Or I use Firefox to go to my inbox on the server and open the
attachment there, still in Firefox, and get the text.
> Could it have been marked (by the sender) as if text, say, and not binary?
How do I tell if it is so marked or not?
> Can you see the "MIME headers" of the original message?
Is the following what you had in mind?
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="------=_Next_Part_3011653798.529"
> (what "server website,"
My institution provides a web-based interface with the mail server so
I can use a browser to see mail in my inbox.
and does it provide a "raw" view
> of the original message?)
If "raw" means something like this --
<x-html><!x-stuff-for-pete base="" src="" id="0" charset="/
macintosh"><HTML><HEAD><style type="text/css">body {font-family:
arial, sans-serif;}</style></HEAD><BODY><P>Here is an itemised
itinerary for your forthcoming travel arrangements for booking
reference CPF004643465, a copy of which you may want to leave with a
friend or relative.</P><P>Have a pleasant trip<P><P>
-- then I can see that after downloading via Eudora, but not when the
message is in the Inbox.
Does this help with a diagnosis? Thanks for your interest.
John
John H Meyers - 28 May 2007 22:50 GMT
On Sun, 27 May 2007 09:46:29 -0500, John wrote:
> Is the following what you had in mind?
> MIME-Version: 1.0
> Content-Type: multipart/mixed;
> boundary="------=_Next_Part_3011653798.529"
That specifies what string
will separate each subsequent attachment,
but I meant the header part of the PDF attachment itself,
like this one which I just sent to myself:
--=====================_361293081==_
Content-Type: application/pdf; name="SevenColors.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="SevenColors.pdf"
The first few characters of the PDF file should also be
a standard PDF header; for this file it happens to be:
%PDF-1.2
%<bh:c7>
If you can't obtain the actual first bytes from the stored file,
the first line of the "base64" encoding (following the header)
would suffice, as we can decode that, such as on-line at:
http://www.securitystats.com/tools/base64.php
Any comparison of PDF attachments (headers and first bytes)
which are okay, vs. those not okay, might also be helpful.
--