7 messages in net.sourceforge.lists.courier-usersRe: [courier-users] makemime and sqwe...| From | Sent On | Attachments |
|---|---|---|
| Peer Oliver Schmidt | Jan 24, 2002 7:54 am | |
| Roland Schneider | Jan 24, 2002 10:07 am | |
| Peer Oliver Schmidt | Jan 24, 2002 11:07 am | |
| Roland Schneider | Jan 24, 2002 12:07 pm | |
| Peer Oliver Schmidt | Jan 24, 2002 2:10 pm | |
| Sam Varshavchik | Jan 24, 2002 2:45 pm | |
| Sam Varshavchik | Jan 24, 2002 2:46 pm |
| Subject: | Re: [courier-users] makemime and sqwebmail | |
|---|---|---|
| From: | Roland Schneider (list...@serv.ch) | |
| Date: | Jan 24, 2002 10:07:45 am | |
| List: | net.sourceforge.lists.courier-users | |
--Peer Oliver Schmidt wrote on 24.01.2002 16:54 +0100:
Hi list, I was playing around with makemime and sending me a PDF file using makemime -c auto -a "To: pos" test.pdf|sendmail Looking at the message in SQWebmail shows the contents of the binary PDF file. ie. the start of the file with %PDF etc. (The mime type says application/octet-stream) Looking at the message from Outlook shows an empty message plus the attachment, except the name is now ATT0058.DAT Same happens if I change the type to -c application/pdf. What am I missing here?
Probably some headers, any the *.pdf was not encoded at all.
Create the same message from within SQWebmail (or any other mime-compatible client) and compare the headers and content.
Mime-messages usually have a text/plain-part first, but it also works without on compatible clients like SQWebmail and a few others: (sorry, no OutLuck here...)
MIME-Version: 1.0 Content-Type: application/pdf; name="myfile.pdf" Content-Transfer-Encoding: base64 Content-Disposition: inline
JVBERi0xLj... (like `base64 -e ...` would create)
I dont know why SQWebmail shows any type of application/* as plain text, if the message is formatted as above you get a link for downloading, types of image/* could even be viewed.
Roland