From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6241806232044175360 X-Received: by 10.50.51.37 with SMTP id h5mr3543438igo.8.1453299775518; Wed, 20 Jan 2016 06:22:55 -0800 (PST) X-BeenThere: supmua@googlegroups.com Received: by 10.140.100.175 with SMTP id s44ls3987163qge.94.gmail; Wed, 20 Jan 2016 06:22:55 -0800 (PST) X-Received: by 10.129.25.212 with SMTP id 203mr33448012ywz.35.1453299775096; Wed, 20 Jan 2016 06:22:55 -0800 (PST) Return-Path: Received: from sasl.smtp.pobox.com (pb-smtp0.int.icgroup.com. [208.72.237.35]) by gmr-mx.google.com with ESMTPS id w126si2623921ywe.6.2016.01.20.06.22.54 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Jan 2016 06:22:54 -0800 (PST) Received-SPF: pass (google.com: domain of marka@pobox.com designates 208.72.237.35 as permitted sender) client-ip=208.72.237.35; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of marka@pobox.com designates 208.72.237.35 as permitted sender) smtp.mailfrom=marka@pobox.com Authentication-Results: mx.google.com; dkim=pass header.i=@pobox.com Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp0.pobox.com (Postfix) with ESMTP id 8556438478; Wed, 20 Jan 2016 09:22:54 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=content-type :from:to:cc:subject:in-reply-to:references:date:message-id :content-transfer-encoding; s=sasl; bh=iIwSNOfrP/Eba7T5ukjZ8PfYY R8=; b=AEAxCljbR3loKn9wB7ZUm/22RAKb/0Iv0dLyIIZnUnjTLcoO0sZiyuy3N 4JLHR8HvhwHyoVOOn6uoiqnLm1nYgrO3Juw6wvcrJtEt8TeaHkIF79vfq/Dt8YZY kGok5nFfagCoRKEj8qQc4xZr448K3q9MbIGWqIMRX93VYv23D0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=content-type :from:to:cc:subject:in-reply-to:references:date:message-id :content-transfer-encoding; q=dns; s=sasl; b=tJlP3Tl8T7UwD0YQu+Q JHyt2sphxJEfaITrfXCHsOHfC1gd++hzo1RmtLXgsqkejE7yGXMQuG3A/fDQTgrA 14N2GGBorYJYphZH3y71eJkkyb/qn2uN+ovP7dh6brFRL6bRa6V3CaAaidfpGtNT vV0/huDeJqOIm08B5/Xos3Vs= Received: from pb-smtp0.int.icgroup.com (unknown [127.0.0.1]) by pb-smtp0.pobox.com (Postfix) with ESMTP id 7D6B838477; Wed, 20 Jan 2016 09:22:54 -0500 (EST) Received: from localhost (unknown [71.161.204.138]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by pb-smtp0.pobox.com (Postfix) with ESMTPSA id 0620338476; Wed, 20 Jan 2016 09:22:53 -0500 (EST) Content-Type: text/plain; charset=UTF-8 From: Mark Alexander To: =?utf-8?q?Martin_B=C3=A4hr?= Cc: supmua Subject: Re: [sup] offsets for mbox broken In-reply-to: <1453283603-sup-5823@email.archlab.tuwien.ac.at> References: <1453283603-sup-5823@email.archlab.tuwien.ac.at> Date: Wed, 20 Jan 2016 09:22:53 -0500 Message-Id: <1453299579-sup-1626@t60p> User-Agent: Sup/0.22.1 X-Pobox-Relay-ID: 4B57F076-BF81-11E5-807A-6BD26AB36C07-04141195!pb-smtp0.pobox.com Content-Transfer-Encoding: quoted-printable Excerpts from Martin B=C3=A4hr's message of 2016-01-20 10:56:00 +0100: > 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.