offsets for mbox broken
27 views
Skip to first unread message
Martin Bähr
Jan 20, 2016, 4:56:02 AM1/20/16
to supmua
hi,
i just made the mistake of accessing my inbox with imap, and now all the
offsets in the sup database are broken.
how can i get sup to resync to the new offsets?
greetings, martin.
--
eKita - the online platform for your entire academic life
--
chief engineer eKita.co
pike programmer pike.lysator.liu.se caudium.net societyserver.org
secretary beijinglug.org
mentor fossasia.org
foresight developer foresightlinux.org realss.com
unix sysadmin
Martin Bähr working in china http://societyserver.org/mbaehr/
i just made the mistake of accessing my inbox with imap, and now all the
offsets in the sup database are broken.
how can i get sup to resync to the new offsets?
greetings, martin.
--
eKita - the online platform for your entire academic life
--
chief engineer eKita.co
pike programmer pike.lysator.liu.se caudium.net societyserver.org
secretary beijinglug.org
mentor fossasia.org
foresight developer foresightlinux.org realss.com
unix sysadmin
Martin Bähr working in china http://societyserver.org/mbaehr/
Mark Alexander
Jan 20, 2016, 9:22:55 AM1/20/16
to Martin Bähr, supmua
Excerpts from Martin Bähr's message of 2016-01-20 10:56:00 +0100:
1. Use sup-dump to make an ASCII dump of the message state and tags.
2. Move the Xapian index (~/.sup/xapian) to some other location.
3. Used sup-restore to read the dump created in step 1.
I don't know if this going to work for you, but it might be worth
a try since your index is broken.
> how can i get sup to resync to the new offsets?
In the past, when I've had problems with the Xapian index, I've done this:
1. Use sup-dump to make an ASCII dump of the message state and tags.
2. Move the Xapian index (~/.sup/xapian) to some other location.
3. Used sup-restore to read the dump created in step 1.
I don't know if this going to work for you, but it might be worth
a try since your index is broken.
Mark Alexander
Jan 20, 2016, 9:25:53 AM1/20/16
to Mark Alexander, Martin Bähr, supmua
Excerpts from Mark Alexander's message of 2016-01-20 09:22:53 -0500:
> 3. Used sup-restore to read the dump created in step 1.
Sorry, I meant sup-sync. There is no sup-restore.
Martin Bähr
Jan 20, 2016, 12:15:08 PM1/20/16
to Mark Alexander, supmua
On Wed, Jan 20, 2016 at 09:22:53AM -0500, Mark Alexander wrote:
> 1. Use sup-dump to make an ASCII dump of the message state and tags.
> 2. Move the Xapian index (~/.sup/xapian) to some other location.
> 3. Used sup-restore to read the dump created in step 1.
>
> I don't know if this going to work for you, but it might be worth
> a try since your index is broken.
wow, thank you!
> 1. Use sup-dump to make an ASCII dump of the message state and tags.
> 2. Move the Xapian index (~/.sup/xapian) to some other location.
> 3. Used sup-restore to read the dump created in step 1.
>
> I don't know if this going to work for you, but it might be worth
> a try since your index is broken.
i don't see how it could not work. sup-dump only stores the message-id
and the
labels, that means on restore sup-sync has to find that message and then
recreate
everything else from the original mbox data.
it is essentially doing a fresh import of everything, with the only
added
information of setting the labels. looks fool-proof to me.
the only downside is that at 6GB of emails, this is going to take a
loooong time. (and so i need to write this with mutt :-(
i am certainly going to complete this, but i wonder if there is a faster
way, something that doesn't rebuild the whole index, but just resyncs
the offsets.
Reply all
Reply to author
Forward
0 new messages