It turns out the message wasn't synced back to the remote side - and it has
also disappeared from another machine that's synced to the same remote. So
perhaps my proposed hack wasn't a fix after all. Sorry for posting an
unsatisfactory solution.
Is there a way to get mbsync to recognise the message again and sync it
back to the server?
On Sun, Oct 15, 2017 at 12:02 PM, Oswald Buddenhagen <
oswald.buddenha...@gmx.de> wrote:
> On Wed, Oct 11, 2017 at 09:21:43AM +0100, Seb Frank wrote:
> > Sorry, this is over my head. What actions would I need to perform
> > answer these questions?
> >
> you posted instructions how to hack the system without actually
> understanding what the system does and why?! :o
>
> look at the full message headers. just inspect the file you hacked
> locally, and for the remote side you can use thunderbird (you can enable
> showing the UID (column "order received")).
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> isync-devel mailing list
> isync-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/isync-devel
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
