[Alpine-info] CentOS 6 upgrade breaks JPEG attachment viewer

[Roger Davis]

Hi Dave,

Thanks, I just finished looking through your sample mailcap and 
octet-stream examples.

It would seem (see my previous response to Eduardo's message) that my 
biggest problem here is that not knowing much about how mail works I have 
no idea where these components (as they currently exist on my system) all 
came from, i.e., were they installed by alpine or CentOS? How would I know 
if I am using the mailcap or octet-stream that has been used with alpine?

I assume that your mailcap example I should install as ~/.mailcap (after
modifying it as desired). Where would your octet-stream example file
get installed?

Thanks!

Roger

On Sat, 18 Feb 2012, David Forrest wrote:


> On Sat, 18 Feb 2012, Roger Davis wrote:

>> 

>> I just upgraded my Linux release from CentOS 5.7 to CentOS 6.2 (via a fresh 

>> re-install), and I can no longer view image attachments within alpine. I 

>> had been running alpine 1.10 (recompiled for CentOS 6.2), so I then 

>> downloaded and built alpine 2.0 but that breaks in exactly the same way. 

>> When I try to look at a .jpg attachment within alpine and type 'y' in 

>> response to the question "View selected attachment?", alpine starts up eog 

>> (eye of gnome) which immediately displays the message "No images found in 

>> 'file:///tmp/img-Capribos-34810.jpg'." where the name of the embedded JPEG 

>> attachment was "Capribos-34810.jpg". In fact there is no file 

>> "/tmp/img-Capribos-34810.jpg". And yes, /tmp is world-writable:

>

> If you are using the mailcap or octet-stream that has been used with alpine, 

> the below write-up may be of some help as I use it on alpine 2.02.

>

> http://www.maplepark.com/~drf/consults/octet-stream.html

>

> Dave

>

> -- 

> David Forrest                   e-mail   drf @ maplepark.com

> Maple Park Development Corporation  http://xen.maplepark.com

> St. Louis, Missouri    (Sent by ALPINE 2.02 FEDORA 11 LINUX)

>