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: Fri, 09 Nov 2001 12:50:45 -0600	[thread overview]
Message-ID: <q6meln7n5h6.fsf@spartacus.utdallas.edu> (raw)
In-Reply-To: <vafbsibvqft.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Fri, 09 Nov 2001 17:50:46 +0100")

>>>>> On Fri, 09 Nov 2001 17:50:46 +0100,
>>>>> Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> (kg) writes:

kg> Suppose I've got an nnimap group for a mailing list and compose a
kg> message to the list.  The message has a Gcc header pointing to that
kg> group (via gcc-self).

[...]

kg> Using Cyrus 1.6.22.

Hmmm... is duplicate delivery check enabled on the Cyrus server?  I
think it uses the Message-ID for this check.  Perhaps this would
take care of the dups for you??


-- 
Amos




  parent reply	other threads:[~2001-11-09 18:50 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 [this message]
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

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=q6meln7n5h6.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).