From: Vegard Vesterheim <vegard.vesterheim@uninett.no>
To: ding@gnus.org
Subject: Re: Gcc to IMAP is slow
Date: Mon, 25 Oct 2010 23:42:48 +0200 [thread overview]
Message-ID: <87sjzut0dj.fsf@uninett.no> (raw)
In-Reply-To: <87hbgaw5tv.fsf@dod.no> (Steinar Bang's message of "Mon, 25 Oct 2010 19:16:44 +0200")
On Mon, 25 Oct 2010 19:16:44 +0200 Steinar Bang <sb@dod.no> wrote:
>>>>>> Vegard Vesterheim <vegard.vesterheim@uninett.no>:
>
>> In order to preserve threads as much as possible, I Gcc my own messages
>> both into the folder I am in,
>
> FWIW I do the same thing with BCC and letting it hit the same procmail
> filtering that handles incoming email.
Yes, I could do that, but it seems kinda silly to send the message on
this round-trip, when I can stash it directly in the correct folder
directly.
>
>> and to the Sent-folder (via gnus-outgoing-message-group)).
>
> I don't do that, though. Why two copies?
Primary laziness, it makes searching for my own sent messages much
easier.
- Vegard V -
next prev parent reply other threads:[~2010-10-25 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 8:03 Vegard Vesterheim
2010-10-25 17:16 ` Steinar Bang
2010-10-25 21:42 ` Vegard Vesterheim [this message]
2010-10-29 22:47 ` Lars Magne Ingebrigtsen
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=87sjzut0dj.fsf@uninett.no \
--to=vegard.vesterheim@uninett.no \
--cc=ding@gnus.org \
/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).