Gnus development mailing list
 help / color / mirror / Atom feed
From: Amos Gouaux <amos+lists.ding@utdallas.edu>
Subject: Re: Mailing list and Gcc header in nnimap groups
Date: Sun, 11 Nov 2001 01:15:55 -0600	[thread overview]
Message-ID: <q6mn11trd5g.fsf@spartacus.utdallas.edu> (raw)
In-Reply-To: <m3668ihuqd.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Sat, 10 Nov 2001 22:05:56 -0500")

>>>>> On Sat, 10 Nov 2001 22:05:56 -0500,
>>>>> Paul Jarc <prj@po.cwru.edu> (pj) writes:

pj> Does it need to be?  By the time the list copy comes in, the Gcc'ed
pj> copy will already be there; won't the list copy be dropped then, since
pj> it does come through "deliver"?

The deliver process stores the Message-ID's of mail that it has
handled into a db.  Since, as Kai reminded me, a GCC just does a
save to that folder, it doesn't go through the steps to stash the
Message-ID into the duplicate delivery db.  So as far as deliver is
concerned, it hasn't seen this message before.

-- 
Amos




      reply	other threads:[~2001-11-11  7:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-09 16:50 Kai Großjohann
2001-11-09 17:02 ` Paul Jarc
2001-11-09 17:31   ` Ted Zlatanov
2001-11-09 17:52     ` Paul Jarc
2001-11-09 18:21       ` Ted Zlatanov
2001-11-09 18:38         ` Paul Jarc
2001-11-09 19:16       ` Matt Armstrong
2001-11-09 19:25         ` Paul Jarc
2001-11-09 19:58           ` Ted Zlatanov
2001-11-09 21:51   ` Kai Großjohann
2001-11-10  6:40     ` Matt Armstrong
2001-11-09 18:50 ` Amos Gouaux
2001-11-09 19:14   ` Matt Armstrong
2001-11-09 19:18     ` Paul Jarc
2001-12-29  6:42       ` Dynamic stuff (was: Mailing list and Gcc header in nnimap groups) Lars Magne Ingebrigtsen
2001-11-09 21:53   ` Mailing list and Gcc header in nnimap groups Kai Großjohann
2001-11-10  2:56     ` Amos Gouaux
2001-11-10 17:11       ` Kai Großjohann
2001-11-11  3:05     ` Paul Jarc
2001-11-11  7:15       ` Amos Gouaux [this message]

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=q6mn11trd5g.fsf@spartacus.utdallas.edu \
    --to=amos+lists.ding@utdallas.edu \
    /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).