Gnus development mailing list
 help / color / mirror / Atom feed
From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: auto-marking my own messages
Date: Sun, 09 Mar 2003 15:23:42 +0100	[thread overview]
Message-ID: <84wuj8r53l.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <ubs0kveil.fsf@boost-consulting.com>

David Abrahams <dave@boost-consulting.com> writes:

> I'm hoping someone can help with this; I can't find the answer in the
> manual, but it seems like such an obvious thing that someone must've
> solved it.  I have myself set up as a Cc: recipient on all of my
> outgoing messages, mostly so that I can browse complete mail threads
> in my INBOX summary buffer using `A T' and `^'.  However, I'm really
> not interested when one of these emails from _me_ comes in -- I wrote
> it so I probably don't need to read it -- I just want it there for
> bookeeping purposes.  What I'd like is for Gnus to automatically mark
> it as 'read' so that I don't see it by default, and preferably not
> download it from the IMAP server unless I ask to look at it.

In Oort Gnus, you can use the Gcc header instead of the Cc header to
get your local copy, and you can use the variable
gnus-gcc-mark-as-read to mark it as read automatically.

Not sure what to do about the `download' part, though -- messages are
normally not downloaded from the server unless you actually select
them for reading.  So maybe you're talking about the headers?  Or you
use the agent?  Or something else entirely is going on?

-- 
A preposition is not a good thing to end a sentence with.



  reply	other threads:[~2003-03-09 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-09 13:46 David Abrahams
2003-03-09 14:23 ` Kai Großjohann [this message]
2003-03-10  2:00   ` David Abrahams
2003-03-10 14:15     ` Kai Großjohann

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=84wuj8r53l.fsf@lucy.is.informatik.uni-duisburg.de \
    --to=kai.grossjohann@uni-duisburg.de \
    /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).