🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: gnu.emacs.vm.bug
Article #9247

Re: FCC to an open folder fails

#9247
From: k p c
Date: Wed, 29 Jan 1992 23:55
43 lines
2839 bytes
i've been following this thread and it's apropos to lots of great
things that vm can do.  why not implement the great (imho) idea
described below?

In article <9201292211.AA20375@wendy-fate.UU.NET>
kyle@wendy-fate.uu.net writes:

    > > Using FCC is not "saving".  I don't support the use of FCC.  If
    > > you want a copy of all your outbound messages, the right way to do
    > > it is to set mail-self-blind to t.
    > 
    > Egads, why? That involves yet another step in order to get your message
    > saved to an archive file (you have to read the mail that you sent
    > yourself then save it). 
    > 
    > FCC = 'File Carbon Copy' -- why is this not "saving"?

   I was afraid this argument was going to get started again... :-)

   The problem with FCC is that the message you're saving is usually
   missing some headers.  One of these, Message-ID, is significant
   if you ever want to use the IDs to index the old messages.  It's
   better to save the copy of the message that the MTA sends you.
   It will have all the proper headers added.

add a header like 'X-VM-V5-FCC-files: ("filename")', and act as if
mail-self-blind were t.  then, when vm is called to get mail, have it
automatically mark messages that have this header as deleted
(optionally not even showing them) and save them to the appropriate
file.

this way we get to have Message-Id for wonderful searching and
threading features, lack of the bug (or pseudobug) appending to the
out folder, and the ability to have customized out folders.

all with a simple change!

(ok, yes, it will cause xbiff to call more.  but there are versions
that can filter out self-blind messages.)

--
o I seek a cottage, an in-law unit, or shared housing (with ethical nonsmokers)
  in Palo Alto, Woodside, Portola V., Los Altos Hills, Los Altos, or Cupertino.
Technical Details
Message-ID: <KPC.92Jan29155521@zog.arc.nasa.gov>
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!ames!kronos.arc.nasa.gov!pluto.arc.nasa.gov!kpc
References: <9201291654.AA16159@wendy-fate.UU.NET> <OLANO.92Jan29011251@gemini.gemini> <RATINOX.92Jan29111617@splinter.coe.northeastern.edu> <TYNOR.92Jan29165124@hydra.gatech.edu> <9201292211.AA20375@wendy-fate.UU.NET>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f6829,ec94aee338af15e0
X-Google-Attributes: gidf6829,public
X-Google-ArrivalTime: 1992-01-29 16:34:42 PST
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!ames!kronos.arc.nasa.gov!pluto.arc.nasa.gov!kpc
From: kpc@pluto.arc.nasa.gov (k p c)
Newsgroups: gnu.emacs.vm.bug
Subject: Re: FCC to an open folder fails
Message-ID: <KPC.92Jan29155521@zog.arc.nasa.gov>
Date: 29 Jan 92 23:55:21 GMT
References: <9201291654.AA16159@wendy-fate.UU.NET>
 <OLANO.92Jan29011251@gemini.gemini>
 <RATINOX.92Jan29111617@splinter.coe.northeastern.edu>
 <TYNOR.92Jan29165124@hydra.gatech.edu>
 <9201292211.AA20375@wendy-fate.UU.NET>
Sender: usenet@kronos.arc.nasa.gov (Will Edgington, wedgingt@ptolemy.arc.nasa.gov)
Organization: NASA Ames Research Center (Sterling)
Lines: 43
In-Reply-To: kyle@wendy-fate.uu.net's message of Wed, 29 Jan 92 17:11:03 -0500
Nntp-Posting-Host: zog.arc.nasa.gov