🚀 go-pugleaf

The various routines that use vm-pipe-message-part reference:
  "Runs a shell command with contents from the current message as input.
  By default, the entire message is used.
  With one \\[universal-argument] the text portion of the message is used.
  With two \\[universal-argument]'s the header portion of the message is used.
  With three \\[universal-argument]'s the visible header portion of the message
  plus the text portion is used.

HOWEVER, vm-pipe-message-part is skipping the initial 'From' line since
it is using (vm-headers-of m) as the start rather than (vm-start-of m).
Similarly, it uses (vm-text-end-of m) rather than (vm-end-of m)

Since the usual reason for splitting/piping messages to an external
shell command is to pass the message to some standard 3rd program, it
would be helpful to use standard conventions -- by which I mean
something relatively consistent with 'formail' or better yet the RFC's.
In particular, when you ask for the "entire message", I at least expect
the entire message.

In my case, spamassassin thinks a collection of messages is just one big
message since it doesn't see the 'From' line.

I would suggest making the following change so that the default "entire
message" truly includes the entire message and perhaps add an option
with four universal arguments that gives the current default behavior.

(defun vm-pipe-message-part (m arg)
  "Return (START END) bounds for piping to external command, based on ARG."
  (cond ((equal prefix-arg '(4))
	 (list (vm-text-of m) (vm-text-end-of m)))
	((equal prefix-arg '(16))
	 (list (vm-headers-of m) (vm-text-of m)))
	((equal prefix-arg '(64))
	 (list (vm-vheaders-of m) (vm-text-end-of m)))
+	((equal prefix-arg '(256))
+	 (list (vm-headers-of m) (vm-text-end-of m)))
	(t 
-	 (list (vm-headers-of m) (vm-text-end-of m)))))
+	 (list (vm-start-of m) (vm-end-of m)))))