Re: Problem with Attachments coming from Lotus Notes
On 2006-03-21 at 16:16 -0600, Bryan K. Walton wrote:
> Under scenario 2, when I open the email, lynx tries to dump the HTML
> to me, and it shows something like this:
>
> [cid:_2_04C54DF804C530F40078770D86257138]
RFC 2392 reference to another MIME part by its Content-ID header; the
only safe way to refer to images in email without requiring the receiver
be able to retrieve attachments from a remote server (and so track the
reading).
> 4 <no description> [image/jpeg, base64, 32K]
>
> The image attachment (line 4) is what is giving me grief. I can't
> view it apparently because it has no name.
I just made up an email with such an attachment, and mutt was able to
call the mailcap handler (ImageMagick's display(1) command) just fine.
I'm running current CVS + patches and nothing in the ChangeLog suggests
a change in behaviour here, although I could easily be wrong.
> Has anybody dealt with this before? Is there a way to instruct Mutt
> to give attachments a predefined name when they don't already have
> one ("image0.gif" -- for example).
My process listing shows:
display /tmp/muttVUGAfy
You can force a particular extension by using the mailcap facility for
this; your ~/.mailcap file should then contain a line something like:
image/jpeg; display %s; nametemplate="%s.jpg"; test=test -n $DISPLAY
Attached is a simple-ish test email to send yourself any way you like,
to see if you can trigger the problem with this, or if the problem is
something else which Notes may be doing. By attaching it, I'm more sure
that it will make it through to you without being mangled by an
intermediate system which adds or removes headers.
Regards,
-Phil
From: Phil Pennock <pdp@xxxxxxxxxxxx>
To: "Bryan K. Walton" <bryankwalton@xxxxxxxxxxxx>
Subject: MIME test, attachment w/o filename
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="_-_-=42X"
Message-Id: <E1FLqEW-0008Nj-Be@xxxxxxxxxxxxxxxxxx>
Date: Tue, 21 Mar 2006 23:25:57 +0000
Pre-mime message for compatibility
--_-_-=42X
Content-Type: multipart/alternative; boundary="_=MP_plain_vs_html_42X"
--_=MP_plain_vs_html_42X
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
This is the first part of the mail, in plain text.
If it were in HTML, you'd see a reference to the image;
see the alternative!
--_=MP_plain_vs_html_42X
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit
<html><head><title>This is the HTML version!</title></head>
<body><h1>HTML version, referring to nameless PNG</h1>
<p>See <img src="cid:hdlmylQ4mKR7fMO1ThmStiso" alt="some PNG"> for
more stuff.</p>
</body></html>
--_=MP_plain_vs_html_42X--
--_-_-=42X
Content-Type: image/png
Content-Transfer-Encoding: base64
Content-ID: hdlmylQ4mKR7fMO1ThmStiso
iVBORw0KGgoAAAANSUhEUgAAABAAAAAQAQMAAAAlPW0iAAAABlBMVEWZmZkAAP+uUvqGAAAA
AXRSTlMAQObYZgAAAAFiS0dEAf8CLd4AAAAJcEhZcwAAAEgAAABIAEbJaz4AAAAtSURBVAjX
Y2BgYGBiYagSYfBiYai+wuAUAkUQ4MDC8LyOwT+FwUOEIb0MKAAAp+EHiZdm09AAAAAeelRY
dFNvZnR3YXJlAAB42osISMzMK1Ew0jPXMwAAGVYDarvs82YAAAAASUVORK5CYII=
--_-_-=42X--