🚀 go-pugleaf

>>>>> "david" == David S. Browning <browning@willard.nas.nasa.gov> writes:


david>    Harald Fuchs writes:
    > I think this would be a fixed bug rather than an additional feature.
    > Who is interested in "X-VM-v5-Data:" and "Received:" lines?

david>    Kyle Jones writes:
   > Some people are interested in Received lines.  I agree about the
   > uselessness of preserving X-VM-v5-Data though.

david> So, it sounds like "X-VM-v5-Data:" should be nixed completely, and the
david> "Received:" lines should be optional, e.g. with the variable
david> vm-reply-include-receipts or something.  Is there a consensus?

Well, I wouldn't mind if forwarding used a 'vm-header-nuke-list' patterned
after (or even using, since we're probably equally uninterested in these
headers in both cases) 'sc-header-nuke-list'.  Here's mine, for example,
but it doesn't work for vm-mail forwarding:

sc-header-nuke-list's value is ("via" "origin" "status" "received" "remailed" "cc" "sender" "replied" "organization" "keywords" "distribution" "xref" "references" "expires" "approved" "summary" "precedence" "subject" "newsgroup[s]?" "\\(\\(followup\\|apparently\\|errors\\|\\(in-\\)?reply\\)-\\)?to" "x-[a-z0-9---]+" "[a-z---]*message-id" "\\(summary-\\)?line[s]" "\\(\\(return\\|reply\\)-\\)?path" "\\(posted-\\)?date" "\\(mail-\\)?from" "^Delivery-Date:\\|" "^Content-Length:\\|" "^NNTP-Posting-Host:\\|" "^St


atus:\\|" "^Return-Path:\\|" "^Received:\\|" "^X-VM-v5-Data:")

Documentation:
*List of mail headers to remove from body of reply.
--
Mike Northam    mbn@oregon.cray.com   Home:123 11' 40"W   45 37' 14"N
(503) 641-3151 (work) (503) 324-1831 (home) {cray|sun|ucsd}!fpssun!mbn
We are now Cray Research Superservers, Inc. (RIP FPS Computing)
"Yeah, or they relieve their anxiety by tearing out the throats of two-bit
quacks expounding psychobabble just to hear themselves talk." Adam, the
eccentric chef, explains how to deal with tension on Northern Exposure