From: Konstantin Ryabitsev <mricon@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: tools@kernel.org
Subject: Re: korgalore delivering duplicates
Date: Tue, 27 Jan 2026 17:26:26 -0500 [thread overview]
Message-ID: <20260127-polite-literate-koala-4c8ccb@lemur> (raw)
In-Reply-To: <26435143-82c8-452b-a06c-e47de6772802@app.fastmail.com>
On Tue, Jan 27, 2026 at 07:18:18PM +0100, Ard Biesheuvel wrote:
> - messages received directly that are also pulled by korgalore, potentially
> multiple times if they were cross-posted to multiple mailing lists;
> - outgoing messages that are cc'ed to multiple mailing lists, which are then
> looped back and delivered by korgalore in the same manner.
Okay, for JMAP and IMAP targets, korgalore now checks if a message with the
same Message-ID already exists in the target folder before attempting to
import it. This uses JMAP's Email/query with a header filter for JMAP targets,
and IMAP's SEARCH HEADER for IMAP targets. Gmail already deduplicates
automatically via its API, so no changes were needed there.
Not doing anything for Maildir targets for now, because I don't want to
iterate through potentially thousands of messages.
I've also added an X-Korgalore-Trace header to all delivered messages, e.g.:
X-Korgalore-Trace: from feed=lei:myquery for delivery=fastmail
by korgalore/0.5-dev; Mon, 27 Jan 2026 17:10:09 -0500
This should help you identify which messages came through korgalore and
from which feed, at least.
The changes are in the 0.5 master branch and need more testing, if you are
able to do that via the git repo directly.
Best wishes,
-K
prev parent reply other threads:[~2026-01-27 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 18:18 korgalore delivering duplicates Ard Biesheuvel
2026-01-27 19:36 ` Konstantin Ryabitsev
2026-01-27 22:26 ` Konstantin Ryabitsev [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=20260127-polite-literate-koala-4c8ccb@lemur \
--to=mricon@kernel.org \
--cc=ardb@kernel.org \
--cc=tools@kernel.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