Gnus development mailing list
 help / color / mirror / Atom feed
From: David Abrahams <dave@boost-consulting.com>
Subject: Re: auto-marking my own messages
Date: Sun, 09 Mar 2003 21:00:30 -0500	[thread overview]
Message-ID: <uheacou9t.fsf@boost-consulting.com> (raw)
In-Reply-To: <84wuj8r53l.fsf@lucy.is.informatik.uni-duisburg.de>

kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:

> 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.

Argh.  I was using Gcc to get my local copy, but this makes sending
mail painful when I'm connected because I use IMAP, and combined with
the long turnaround time for SMTP to send the message, the time to
stick the message in my remote IMAP mailbox pushes it over the
usability limit.  I was very relieved to discover today that I could
add myself to the Cc: line and eliminate that overhead.  It would
involve pushing fewer bytes over the network (potentially many fewer
if the message has attachments) if I could just pre-mark incoming
messages from myself in a given group as read.

> 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?

I use the agent, but yes, pre-marking the message as read so that it
doesn't appear in the summary buffer by default should be enough to
prevent it from being downloaded.

Thanks for your attention,
Dave
-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com




  reply	other threads:[~2003-03-10  2:00 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
2003-03-10  2:00   ` David Abrahams [this message]
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=uheacou9t.fsf@boost-consulting.com \
    --to=dave@boost-consulting.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).