I ran into a strange case of MIME handling by VM today.

When VM can't find any way to display a particular MIME object, it calls the handler for application/octet-stream as a last resort, which then prompts for a file name and saves the attachment there.

I wonder why VM should save an attachment as part of a displaying operation, while we can easily save it ourselves through a mouse-click or $s if you prefer.

This behavior is not described in the manual either.

Does anybody know why VM saves the attachments in this way?

Cheers,
Uday

Reply via email to