Re: MimeMap being silly.
On 22 Oct, Peter Young wrote in message
<dc21859e53.pnyoung@...>:
> but the relevant lines seem to be:
>
> Content-Type: text/plain; charset=iso-8859-1
> Content-Transfer-Encoding: quoted-printable
>
> immediately before the actual message.
No, that looks like the content type of the message text itself (hence the
"text/plain"). Each part of the message will have its own content type
specified at the top of the associated block of content.
For example, a recent email that I sent out with a PDF attachment (which you
might recognise) had the following in the message header:
Content-Transfer-Encoding: binary
Content-Type: multipart/mixed; boundary="_----------=_138049560267882";
charset="iso-8859-1"
This told us that it was a multipart message (ie. one with attachments, or
perhaps with an HTML version included). It then went on to finish that
section and start the first block of data -- in this case, the message body
(hence it being "inline").
This is a multi-part message in MIME format.
--_----------=_138049560267882
Content-Disposition: inline
Content-Length: 933
Content-Transfer-Encoding: binary
Content-Type: text/plain
Hi WROCC Member,
Here is the October 2013 edition of The WROCC, in "one-up" A5 format.
The message body is plain text, and is the bit that you read in Messenger.
Once this ended, the attachment followed: being a PDF, it has the expected
type of "application/pdf".
--_----------=_138049560267882
Content-Disposition: attachment; filename="31.07-Oct13.pdf"
Content-Transfer-Encoding: base64
Content-Type: application/pdf; name="31.07-Oct13.pdf"
JVBERi0xLjMKJcfsj6IKNSAwIG9iago8PC9MZW5FIvRmlsdGVyIC9GbGF0ZURlY29k
ZT4+CnN0cmVhbQrg5B+bxdcpkKUraAlxLGaINT5a9CEOKPc2FRkPIj7+EZr5rQ83Z/
There was then a lot of this, before the message finally ended.
--_----------=_138049560267882--
--
Steve Fryatt - Leeds, England
http://www.stevefryatt.org.uk/
______________________________________________________________________
This message was sent via the messenger-l mailing list
To unsubscribe, mail messenger-l+unsubscribe@...
|