From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: Why is MIME hard?
Date: Tue, 02 Oct 2007 17:03:53 +1000 [thread overview]
Message-ID: <873awum206.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: v9lkao1an9.fsf@marauder.physik.uni-ulm.de
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> On Sun, Sep 30 2007, Tim X wrote:
>
>> Recently, I have had problems with Apple mail attachments, but they
>> appear to be doing some strange stuff with their attachment handling
>> (it is embedded inside the html part of the mail message - so if
>> your configured like me to prefer the text version, you can't easily
>> access the attachment (this is fixed in dev VM)).
>
> Are you talking about attachments (e.g. images) inside
> multipart/related MIME parts? If so, what Apple mail is doing is
> correct. Cf. `gnus-mime-display-multipart-related-as-mixed' in Gnus:
>
> ,----[ (info "(gnus)MIME Commands") ]
> | `gnus-mime-display-multipart-related-as-mixed'
> | Display "multipart/related" parts as "multipart/mixed".
> |
> | If displaying "text/html" is discouraged, see
> | `mm-discouraged-alternatives', images or other material inside a
> | "multipart/related" part might be overlooked when this variable is
> | `nil'. *Note Display Customization: (emacs-mime)Display
> | Customization.
> `----
>
The attachments I was referring to in my case were word documents. From
memory, they were not multipart/related. I'm no expert on the MIME
standard, but various groups I asked this question on and posted examples
said that what Apple Mail was doing was not forbidden by the standard, but
it was an unusual interpretation.
From memory (and its been a while since I looked at one of these messages,
so I could be wrong), the atachment was inside the text/html part and was
not marked as multipart/alternative. I did try opening it with gnus, but
this failed. I also tried it with mutt, but that failed as well. gmail was
able to give me the attachment. Note however, as I don't normally use gnus
for mail, the inability of gnus to access the attachment could easily be
due to mis/lack of ocnfiguration.
Tim
--
tcross (at) rapttech dot com dot au
prev parent reply other threads:[~2007-10-02 7:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 14:14 Why is MIME hard? Girish Kulkarni
2007-09-27 19:15 ` Reiner Steib
2007-09-27 20:52 ` Eli Zaretskii
2007-09-28 7:17 ` Dmitri Minaev
2007-09-28 15:42 ` Stefan Monnier
2007-09-30 13:28 ` Tim X
2007-09-30 14:38 ` Reiner Steib
2007-10-02 7:03 ` Tim X [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=873awum206.fsf@lion.rapttech.com.au \
--to=timx@nospam.dev.null \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).