Gnus development mailing list
 help / color / mirror / Atom feed
From: Julien Cubizolles <j.cubizolles@free.fr>
To: ding@gnus.org
Subject: duplicates with offlineimap+dovecot
Date: Mon, 01 Feb 2016 18:31:55 +0100	[thread overview]
Message-ID: <878u34uyk4.fsf@free.fr> (raw)

I've the following setup:

Two different IMAP accounts (free.fr and gmail.com). Both are
synchronized with offlineimap and dovecot to local IMAP folders, both
accessed from Gnus with nnimap. This setup is used on 2 different
computers.

It's working fine except that I very often (almost at every
synchronization) I end up with duplicates of some messages on the local
IMAP folder, they are however not propagated to the distance IMAP
server.

It's not very inconvenient since gnus-suppress-duplicates takes care of
if but I'm confused:

+ It seems to only happen with the free.fr account, although I couldn't
  be sure since I don't have a lot of traffic on the gmail.com one
+ I never have the two computers running at the same time so there can't
  be 2 offlineimap running at the same time.

I have Gnus doing some splitting (including the detection of duplicates)
on the local IMAP folders and some spam autodetection. Since the
duplicates are not synced back to the remote server, could it be a
problem with Gnus accessing the same message a second time and thinking
it's a duplicate of the first one ? Have you ever experienced something
similar ?

Julien.






             reply	other threads:[~2016-02-01 17:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01 17:31 Julien Cubizolles [this message]
2016-02-01 22:34 ` Malcolm Purvis
2016-02-02  8:49   ` Julien Cubizolles
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=878u34uyk4.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).