--Message-Boundary-28670
Content-type: text/plain; charset=US-ASCII
Content-disposition: inline
Content-description: Attachment information.
The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.
---- File information -----------
File: FILE32099.JPG
Date: 14 Feb 2010, 15:08
Size: 31776 bytes.
Type: Unknown
--Message-Boundary-28670
--Message-Boundary-28670
Content-type: Application/Octet-stream; name="FILE32099.JPG"
Content-ID: <5089953.1266189193.11068>
Content-disposition: attachment; filename="FILE32099.JPG"
Content-transfer-encoding: BASE64
[followed by the JPG code]
The message text is displayed as intended in full HTML, and only the
images refuse to show. Pegasus is the only email client that does
this, so I had the originator resend it to my Hotmail address wherein
everything displayed (in Firefox) properly inline.
What is peculiar with Pegasus Mail?
dave r
I think the problem is with content-type:
Content-type: Application/Octet-stream; name="FILE32099.JPG"
Application/Octet-stream is for generic binary data with no specific application
assigned to open it. When attaching in Pegasus Mail there are options to select
file type and encoding with "Mailer Decides" as the defaults. Maybe Pegasus
Mail is selecting the wrong type, the sender needs to check that Pegasus Mail
has selected JPEG. It selected correctly for me but I did find that for .png
files it selected "UNKNOWN".
--
G. R. Woodring
From my point of view, the problem is with Thunderbird. ;-}"
It is just strange that Pegasus is the only email client that causes
Thunderbird to balk at displaying the images inline
I sent myself an email from Pegasus with a .png image that PM does not seem to
recognize (also, there is no way to select .PNG or "Portable Network Graphics"
from the menu). It was sent with content-type: Application/Octet-stream and was
not displayed in Thunderbird but could be saved.
IMHO this is correct behavior. The content-type tells Thunderbird that the file
should *NOT* be opened, executed or displayed. It seems PM's file type handling
is limited. There is a filetype.PM file which can be edited to add file types
but it isn't obvious how PM then determines content-type from this info. I may
see if I can get PM to correctly identify .png files but that is a project for
the weekend :-)
--
G. R. Woodring