Hi Oswald and list,
sorry for my late answer but I was stuck with other work. Last week I finally
deleted those duplicate emails. Just a short heads up for those interested. And
thanks for your input, Oswald!
> On Thu, Apr 02, 2015 at 10:10:56AM +0200, Markus Baader wrote:
> > I guess I could solve my problem by a small script that compares the
> > slave uuids from the state files with the uuids from the slave imap
> > server and delete all emails on the server that don't match an entry in
> > the correspondig state file. Would that be correct
> >
> sounds about right.
That's how I've done it in the end. I used python and needed just about 60
lines of code. Some parts are very specific to my setup however, if someone
would be interested in the script those parts would have to be adopted or,
preferable, generalized.
>
> > and is there some way to do this without writing a script but with
> > mbsync?
> >
> there is no obvious built-in operation for that in mbsync.
>
> you could hack it (basically, replace a propagation with a deletion)
> with only few lines changed, but it's still tricky.
I tried that but couldn't get it to work. Isync seems to do things quite
optimized and thus it was not always easy to figure out what is done when and
where exactly those few lines would have to be changed. Eventually I decided to
go with the script.
> you could set some flag ("draft" is usally unused) on all mails on the
> master server, sync it up, and then filter unmarked mails on the slave,
> and the reset the flag again. i don't know how much traffic that would
> cause and whether it would have some side effects (if draft means
> something to the server).
>
> you could open the mailboxes with mutt and delete duplicates by
> message-id (D=~), but that is not guaranteed to be reliable (a user
> could have distinct messages with the same id, f.ex. if they saved an
> edited copy of a message, or if they have an fcc of a mail and a copy
> received via a mailing list in the same folder).
Those possibilities weren't options in my case, mainly because the master
server is a production system not under my control and I couldn't take any
risks there.
Again, thanks for pointing out those alternatives!
Regards
Markus
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
