Re: [nail-devel] Something has broken mime-encoding

[David R. <ro...@ro...>]

Hi Gunnar, 

Thanks for the quick reply.  Are you saying that when you use nail to
send a .pdf file, the resulting Content-Type is application/pdf?  Or are
you saying that your mail reader can figure it out anyway (e.g., by
doing some sort of content sniffing or looking at the filename and using
some built in mime-types)?

David



On Mon, 2007-10-08 at 01:22 +0200, Gunnar Ritter wrote:
> David Ronis <ro...@mo...> wrote:
> 
> > I have an web application that generates e-mails and PDF-attachements,
> > and uses nail to send them with the -a flag.  The attachment files were
> > initially created as postscript and converted using ps2pdf.
> >
> > This has worked fine until several months ago (I just discovered this
> > now) where the PDF files are now being encoded as 
> >
> >         Content-Type: application/octet-stream
> >         Content-Transfer-Encoding: base64
> >         
> > while in the past (at least as of June 23 2006) they were encoded as:
> >
> >         Content-Type: application/pdf
> >         Content-Transfer-Encoding: base64
> 
> I have no problem to send a PDF document with the
> appropriate content-type header field. Maybe one of
> your mime.types files has changed and is lacking the
> correct
> 
>     application/pdf        pdf
> 
> entry now?
> 
> 	Gunnar
>