🚀 go-pugleaf

Hi Kevin,

Kevin Rodgers <ihs_4664@yahoo.com> writes:

> Michael Welle wrote:
>  > vm seems to create world readable tmp files under some conditions. If
>  > I read an email with an image attached, tmp files are created. If the
>  > image is a jpeg for example, the tmp files are chmod 600. That is the
>  > expected behaviour. But if the image is a png, some tmp files are
>  > chmod 644 and these files are not deleted after finishing vm. This is
>  > rather annoying. Any hints?
>
> Are you sure the attachments are PNG files?  (What are their
> Content-Type and Content-Disposition headers?)
the attachments are png files, if I can trust the file cmd.

Content-Type: image/png
Content-Disposition: inline; filename="Bildschirmphoto1.png"


> Assuming they're image/png MIME attachments, are they being converted
> to some other format, via `vm-mime-type-converter-alist' or
> `vm-mime-image-type-converter-alist'?
No, I have set this variable only for text/html.


> `vm-mime-use-image-strips' defaults to t.  Does the problem occur if
> you set it to nil?
Ah, that seems to be much better. There is only a tmp file with
restricted permissions. I have looked at the code yesterday and find
the place with the stripping. But my knowledge about list is very
vague. Is the handling of png images so different from the handling of
other image types?


> Does the problem occur if you clean out the temp directory before
> selecting such a message (so that you can be sure the file didn't
> already exist with the wrong permission)?
The files are newly created every time an image is showed.

Thank you
Michael