🚀 go-pugleaf

On 2010-01-05, blueman <NOSPAM@nospam.com> wrote:
> Well, that was the whole reason that Robert *added* the command
> vm-pipe-messages-to-command (where the 's' is plural) ... You keep
> talking about this command as if it is yet to exist...

Oh dear. I owe you an apology.

Yes, I didn't notice the the "s". That's because it doesn't exist in
my VM (where almost nothing Rob added is included, except a few known
safe bits from rfaddons, so when I looked for it, auto-completion of
course gave me vm-pipe-message-to-command and my brain failed to
observe the inconsistency.

I apologize!

> I am talking about (and using) the vm-pipe-messages-to-command...
>
> And I would guess that if you used that command it would break at least
> as many programs since external programs *need* to see a separator
> because otherwise they have *no* way of separating messages. Indeed,
> that is the whole purpose of message separators.

However, looking at that function, I see that Rob has already
anticipated your need: you can simply set

(setq vm-pipe-messages-to-command-start
      "From Bogus From Line to Satisfy sa-learn\n")
or however much it needs to look like a real From line to satisfy 
sa-learn.

But now I understand what you're saying (and I promise to read more
carefully next time you say something!), I could see an argument for
changing THAT COMMAND (but absolutely not vm-pipe-message-part) so
that it uses the current default mailbox format. (Though what it
should do with maildir format, I don't know.)