Gnus development mailing list
 help / color / mirror / Atom feed
From: lantz moore <lantz_moore@contigo.com>
Subject: saving all incoming and outgoing mail in the same nnfolder
Date: 22 Oct 1998 11:59:41 -700	[thread overview]
Message-ID: <86hfwwa0de.fsf@godzilla.contigo.com> (raw)


for a couple years now, i've been saving all my outgoing mail (using
default archiving method) and incoming mail (using nnfolder and a procmail
rule).  yesterday i had the bright idea (why it took me so long i have no
idea) to save both incoming and outgoing mail in the same nnfolder.  this
seems to be working rather nicely, except that i seem to randomly lose
incoming messages.  i cannot seem to repeat it no matter what i try.

so, i guess i have two questions:
1) has anyone else seen behavior like this (pgnus v.33)?
b) am i a moron for archiving this way?  is there a better way archive
   incoming/outgoing messags, other than using a bcc back to myself
   instead of a gcc?

thanks.

-- 
lantz moore, contigo software                              lmoore@contigo.com


             reply	other threads:[~1998-10-22 18:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-22 18:59 lantz moore [this message]
1998-10-23  7:56 ` Kai Grossjohann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86hfwwa0de.fsf@godzilla.contigo.com \
    --to=lantz_moore@contigo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).