🚀 go-pugleaf

Kevin Rodgers writes:
>
> Tim Freedom wrote: 
> > I'm using VM-7.07 on emacs-21.2.3 and recently got a pdf attachment
> > that is bafflling me.  Here is my INBOX Summary,
> > 
> >   507  Joe Schmo  Jul 24  201245/13163128  "new spec"
> > 
> > The mime header notes the following,
> > 
> >   Content-Type: application/octet-stream;
> > 	  name="new_spec.pdf"
> >   Content-Transfer-Encoding: quoted-printable
> >   Content-Disposition: attachment;
> > 	  filename="new_spec.pdf"
> > 
> > the quirk is I click to save the attachment and wait and wait...
> > 
> > After about an hour worth of waiting (on a pretty decent SUN
> > machine with 2GB of Ram), I get the following message (note
> > the attachment is not saved either).
> > 
> >      Warning: memory in use exceeds lisp pointer size
> >      Killing some buffers may delay running out of memory.
> >      However, certainly by the time you receive the 95% warning,
> >      you should clean up, kill this Emacs, and start a new one.
> > 
> > What's going on ?  Others who were CC'ed on the email were able
> > to save-off the attachment, view it, etc (they're using other mail
> > clients).
> 
> VM is decoding the attachment within Emacs.  Do you have an external QP
> decoder installed?  (You can get one in the VM source distribution.)
> Have you set vm-mime-qp-decoder-program and vm-mime-qp-decoder-switches
> accordingly?

I've used VM's internal decoder for years now without so much as a hitch;
is it normal for a 13Meg file to take emacs down to "its knees" like this ?

I know nothing about any external QP decoders.  Could you give me a URL
or some more info ?  What should those "vm-mime-qp-decoder-*" values be
set to ?

While on the subject, can't VM complain given a certain file size and note
the need to use an external decoder ?  Why is it that other mailors don't
complain nor get down on their "knees" ?  Very curious; I need to know how
to defend myself against those microcrap users et al and their taunts :-) ?

BTW: I had an 9Meg pdf attachment like a week ago and it decoded fine in
     a matter of seconds, what am I missing - is the decoding not linear ?

Regards,

 .tf.