problem with pdf attachment

problem with pdf attachment

[lconrad]

The message where this bug occurred involved a very large attachment,
so if anyone needs to see the problem _in situ_, I can forward it to
them, or put it on my website.

I got an application/pdf attachment sent from:

X-Mailer: Mozilla 4.7 [fr] (Win98; I)

When I saved the attachment by right-clicking the button, I got a file 
that pdf viewers didn't recognize.  It looked like it was still
encoded -- all the lines were the same length, and consisted entirely
of ascii characters.  When my correspondent zipped the pdf and sent it 
as an application/octet-stream it decoded and unzipped fine.  I don't
know whether this is a problem with the mozilla encoding or the gnus
decoding, but something is wrong.

-- 
Laura (mailto:lconrad@world.std.com , http://www.world.std.com/~lconrad/ )
(617) 661-8097	fax: (801) 365-6574 
233 Broadway, Cambridge, MA 02139

Re: problem with pdf attachment

[Kai Großjohann]

lconrad@world.std.com writes:

> When I saved the attachment by right-clicking the button, I got a file 
> that pdf viewers didn't recognize.  It looked like it was still
> encoded -- all the lines were the same length, and consisted entirely
> of ascii characters.

Can you say `C-u g' on that message and show us the headers of that
MIME part?  Maybe the Content-transfer-encoding is wrong?

kai
-- 
~/.signature: No such file or directory

Re: problem with pdf attachment

[Laura Conrad]

>>>>> "Kai" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:

    Kai> lconrad@world.std.com writes:
    >> When I saved the attachment by right-clicking the button, I got a file 
    >> that pdf viewers didn't recognize.  It looked like it was still
    >> encoded -- all the lines were the same length, and consisted entirely
    >> of ascii characters.

    Kai> Can you say `C-u g' on that message and show us the headers of that
    Kai> MIME part?  Maybe the Content-transfer-encoding is wrong?

--------------57B40B3B82B6796B6B5E4E86
Content-Type: application/pdf;
 name="oeuvres.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="oeuvres.pdf"

JVBERi0xLjIgDQol4uPP0w0KIA0KNyAwIG9iag0KPDwNCi9MZW5ndGggOCAwIFINCi9GaWx0
ZXIgL0xaV0RlY29kZSANCj4+DQpzdHJlYW0NCoAMRBAoEcjOIAaMhwLhmMhANxwM4YNhANRn


-- 
Laura (mailto:lconrad@world.std.com , http://www.world.std.com/~lconrad/ )
(617) 661-8097	fax: (801) 365-6574 
233 Broadway, Cambridge, MA 02139

Re: problem with pdf attachment

[Kai Großjohann]

Laura Conrad <lconrad@world.std.com> writes:

> JVBERi0xLjIgDQol4uPP0w0KIA0KNyAwIG9iag0KPDwNCi9MZW5ndGggOCAwIFINCi9GaWx0
> ZXIgL0xaV0RlY29kZSANCj4+DQpzdHJlYW0NCoAMRBAoEcjOIAaMhwLhmMhANxwM4YNhANRn

The headers look good, but does the stuff that Gnus is saving into the
file also start like this?

Maybe the sender has base64-encoded the PDF file twice?

kai
-- 
~/.signature: No such file or directory