From: Julien Cubizolles <j.cubizolles@free.fr>
To: ding@gnus.org
Subject: Re: duplicates with offlineimap+dovecot
Date: Tue, 02 Feb 2016 09:49:40 +0100 [thread overview]
Message-ID: <87d1sffqe3.fsf@free.fr> (raw)
In-Reply-To: <m237tcukjj.fsf@magog.office.atlassian.com>
Malcolm Purvis <malcolmp@xemacs.org> writes:
>>>>>> "Julien" == Julien Cubizolles <j.cubizolles@free.fr> writes:
>
> Julien> I have Gnus doing some splitting (including the detection of
> Julien> duplicates) on the local IMAP folders and some spam
> Julien> autodetection. Since the duplicates are not synced back to the
> Julien> remote server, could it be a problem with Gnus accessing the
> Julien> same message a second time and thinking it's a duplicate of the
> Julien> first one ?
>
> I have been experiencing a related problem for some time a direct
> connection to a dovecot IMAP server. In my case Gnus performs the local
> splitting but occasionally does not delete the message from the INBOX.
> A second fetch splits the messages again (causing duplicates) and
> generally deletes the messages from the INBOX.
That would explain what I'm experiencing. I'm not sure Dave's suggestion
of using mbsync instead of offlineimap would fix it but maybe the dbox
format for dovecot would do ? I'm not too eager to play with it though,
my current setup took me long enough to come up with.
> This is with a month old copy of gnus from git.
Mine might be older than that. I'll try upgrading and see if it
improves.
Thanks, I'm somewhat relieved to know I'm not alone with this problem.
Julien.
next prev parent reply other threads:[~2016-02-02 8:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 17:31 Julien Cubizolles
2016-02-01 22:34 ` Malcolm Purvis
2016-02-02 8:49 ` Julien Cubizolles [this message]
2016-02-09 11:05 ` Emilio Jesús Gallego Arias
2016-02-09 23:42 ` Lars Ingebrigtsen
2016-02-10 1:17 ` Emilio Jesús Gallego Arias
2016-02-10 2:56 ` Lars Ingebrigtsen
2016-02-10 22:18 ` Emilio Jesús Gallego Arias
2016-02-10 23:56 ` Emilio Jesús Gallego Arias
2016-02-13 6:52 ` Lars Ingebrigtsen
2016-02-13 14:03 ` Emilio Jesús Gallego Arias
2016-02-14 2:34 ` Lars Ingebrigtsen
2016-02-14 4:05 ` Emilio Jesús Gallego Arias
2016-02-14 4:36 ` Lars Ingebrigtsen
2016-02-14 4:56 ` Emilio Jesús Gallego Arias
2016-02-14 5:23 ` Lars Ingebrigtsen
2016-02-14 12:19 ` Emilio Jesús Gallego Arias
2016-02-15 7:54 ` Lars Ingebrigtsen
2016-02-20 7:52 ` Steinar Bang
2016-02-20 8:21 ` Lars Ingebrigtsen
2016-02-20 14:47 ` Steinar Bang
2016-02-22 23:12 ` Emilio Jesús Gallego Arias
2016-02-23 0:58 ` Lars Ingebrigtsen
2016-02-23 18:54 ` Emilio Jesús Gallego Arias
2016-02-23 22:05 ` Dan Christensen
2016-02-24 1:10 ` Lars Ingebrigtsen
2016-02-24 1:11 ` Lars Ingebrigtsen
2016-02-24 17:59 ` Emilio Jesús Gallego Arias
2016-02-01 22:40 ` Dave Abrahams
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=87d1sffqe3.fsf@free.fr \
--to=j.cubizolles@free.fr \
--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).