From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding <ding@gnus.org>
Subject: Re: nnimap and duplicates
Date: Tue, 29 Jan 2002 16:45:23 +0100 [thread overview]
Message-ID: <vafvgdljh4c.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <vqor8o9fkz6.fsf@ubaye.imag.fr> (Nicolas Kowalski's message of "Tue, 29 Jan 2002 12:35:41 +0100")
Nicolas Kowalski <Nicolas.Kowalski@imag.fr> writes:
> There is variable `nnmail-treat-duplicates' set to `delete' by
> default. It does not seem to work with nnimap. Did I miss something ?
Yes, nnimap is not based on nnmail. (Though there might be changes
in the most recent CVS that make nnimap use the duplicate detection
code from nnmail -- anyone?)
I think the other feature in Gnus that has to do with duplicates is
"suppression", not treatment.
kai
--
~/.signature is: umop 3p!sdn (Frank Nobis)
prev parent reply other threads:[~2002-01-29 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-29 11:35 Nicolas Kowalski
2002-01-29 15:45 ` Kai Großjohann [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=vafvgdljh4c.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).