🚀 go-pugleaf

Jeffrey (J.D.) Sparkes writes:
 >         Given the message included at the end, VM does not hide all of
 > headers not specified in vm-visible-headers. Specifically, it does not
 > hide any of the headers after the first "Date:".  Unfortunately, my
 > mail passes through a mainframe which moves the headers that it
 > understands to the front.  (This is VM 5.31, with vm-visible-headers
 > and vm-invisible-header-regexp set to their default values.)

When you first read a message, VM reorders the headers, putting
the visible headers at the end of the header section.  It also
calculates a regular expression that will find the beginning of
the visible headers the next time you read the message.  This is
done because reordering the heraders every time you read a
message is wasteful and slow.  If the message headers are
reordered after this, then the regular expression will be wrong
and you won't see the right headers.  You can use `j' to get vVM
to forget the cached information about a message and its headers,
and to recalculate everything.

What I can't figure out is why your system reordering the headers
in your messages AFTER the mail has been delivered and has been
moved out of the system mail spool.  If this is really what your
system is doing, you're going to have other problems.