🚀 go-pugleaf

[Please don't top-post.]

Jorge Gonzalez wrote:
 > Okay, I stumbled on the reason why my text/plain mail looked like a
 > binary file to vm, and was being opaquely encoded instead of
 > qp-encoded.
 >
 > vm-pcrisis has a variable called vmpc-intangible-sig, which I had set
 > to t.  The setting prevents the cursor from entering the signature.
 > (I'm not sure why that's any great benefit.)
 >
 > That setting, when combined with a message that had paragraphs longer
 > than six lines or so, resulted (in my case) in
 > vm-mime-8bit-transfer-encoding being overrided with a base64 encoding.
 > (Perhaps intangible-sig introduces <CR>s into the buffer??)

I think it's more likely that the last long paragraph didn't contain any
newlines, and combined with your signature formed one line longer than
the 998-character limit.  Can you verify that?

 > Anyway, that's the reason; I wish I were knowledgeable enough to
 > determine the cause, but I have to leave that to others.

I'm guessing that a newline between the last line of message text and
the signature would prevent the two from being counted as one long line
-- unless your signature is larger than 998 characters by itself.  Then
VM needs to be told to ignore the intangible property.  That's probably
a good idea anyway, so here's a patch to
vm-determine-proper-content-transfer-encoding; does it help?

*** vm-7.18/vm-mime.el~	Mon Oct 13 13:30:18 2003
--- vm-7.18/vm-mime.el	Tue Jun  8 09:45:14 2004
***************
*** 1332,1338 ****
   	(and (re-search-forward "[\000\015]" nil t)
   	     (throw 'done "binary"))

! 	(let ((toolong nil) bol)
   	  (goto-char (point-min))
   	  (setq bol (point))
   	  (while (and (not (eobp)) (not toolong))
--- 1332,1340 ----
   	(and (re-search-forward "[\000\015]" nil t)
   	     (throw 'done "binary"))

! 	(let ((inhibit-point-motion-hooks t)
! 	      (toolong nil)
! 	      bol)
   	  (goto-char (point-min))
   	  (setq bol (point))
   	  (while (and (not (eobp)) (not toolong))

-- 
Kevin