imported mailsHEADmaster

2 files changed, 286 insertions, 0 deletions

diff --git a/tickets/abc93b44517543a8a5892e8c1bddce2b/Maildir/new/1511191530.M105822P31598Q2.koom b/tickets/abc93b44517543a8a5892e8c1bddce2b/Maildir/new/1511191530.M105822P31598Q2.koom
new file mode 100644
index 0000000..df3eeb3
--- /dev/null
+++ b/tickets/abc93b44517543a8a5892e8c1bddce2b/Maildir/new/1511191530.M105822P31598Q2.koom
@@ -0,0 +1,123 @@
+Return-Path: <obnam-support-bounces@obnam.org>
+X-Original-To: distix@pieni.net
+Delivered-To: distix@pieni.net
+Received: from yaffle.pepperfish.net (yaffle.pepperfish.net [88.99.213.221])
+	by pieni.net (Postfix) with ESMTPS id 3174C42A91
+	for <distix@pieni.net>; Mon, 20 Nov 2017 09:24:03 +0000 (UTC)
+Received: from platypus.pepperfish.net (unknown [10.112.101.20])
+	by yaffle.pepperfish.net (Postfix) with ESMTP id C9CAA4187B;
+	Mon, 20 Nov 2017 09:24:02 +0000 (GMT)
+Received: from ip6-localhost.nat ([::1] helo=platypus.pepperfish.net)
+	by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
+	id 1eGiJ8-0000Rd-Q0; Mon, 20 Nov 2017 09:24:02 +0000
+Received: from koom.pieni.net ([88.99.190.206] helo=pieni.net)
+ by platypus.pepperfish.net with esmtpsa (Exim 4.80 #2 (Debian))
+ id 1eGNMr-0001QU-9d; Sun, 19 Nov 2017 11:02:29 +0000
+Received: from exolobe3.liw.fi (unknown [92.187.39.54])
+ by pieni.net (Postfix) with ESMTPSA id CD80B46C0E;
+ Sun, 19 Nov 2017 11:02:28 +0000 (UTC)
+Received: from exolobe3 (localhost [127.0.0.1])
+ by exolobe3.liw.fi (Postfix) with ESMTPS id C27EC7C0731;
+ Sun, 19 Nov 2017 12:02:27 +0100 (CET)
+Date: Sun, 19 Nov 2017 12:02:26 +0100
+From: Lars Wirzenius <liw@liw.fi>
+To: Andreas <mailing@duering-andreas.de>
+Message-ID: <20171119110226.qwbed6x4cpvbhiam@exolobe3>
+References: <42bd837a-4b4b-6cb4-252f-9ab322f70dba@duering-andreas.de>
+MIME-Version: 1.0
+In-Reply-To: <42bd837a-4b4b-6cb4-252f-9ab322f70dba@duering-andreas.de>
+User-Agent: NeoMutt/20170113 (1.7.2)
+X-Pepperfish-Transaction: 6855-576d-bca5-8e98
+X-Pepperfish-Transaction-By: platypus
+X-Mailman-Approved-At: Mon, 20 Nov 2017 09:24:01 +0000
+Cc: obnam-support@obnam.org
+Subject: Re: ERROR: Node cannot be found in the node store clientlist
+X-BeenThere: obnam-support@obnam.org
+X-Mailman-Version: 2.1.5
+Precedence: list
+List-Id: Obnam backup software discussion <obnam-support-obnam.org>
+List-Unsubscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org>,
+ <mailto:obnam-support-request@obnam.org?subject=unsubscribe>
+List-Archive: <http://listmaster.pepperfish.net/pipermail/obnam-support-obnam.org>
+List-Post: <mailto:obnam-support@obnam.org>
+List-Help: <mailto:obnam-support-request@obnam.org?subject=help>
+List-Subscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org>,
+ <mailto:obnam-support-request@obnam.org?subject=subscribe>
+Content-Type: multipart/mixed; boundary="===============3273633122374331017=="
+Mime-version: 1.0
+Sender: obnam-support-bounces@obnam.org
+Errors-To: obnam-support-bounces@obnam.org
+
+
+--===============3273633122374331017==
+Content-Type: multipart/signed; micalg=pgp-sha512;
+ protocol="application/pgp-signature"; boundary="cnzyj3daxlr64v7f"
+Content-Disposition: inline
+
+
+--cnzyj3daxlr64v7f
+Content-Type: text/plain; charset=us-ascii
+Content-Disposition: inline
+Content-Transfer-Encoding: quoted-printable
+
+On Sat, Nov 18, 2017 at 12:28:25PM +0100, Andreas wrote:
+> I created a backup with obnam quite a while ago, under Gentoo (the file
+> modification time is back in December 2015). When I try to run obnam
+> fsck or obnam mount now (I tried both versions 1.19.1 and 1.22), I get
+> the following error:
+>=20
+> ERROR: Node 0x2 cannot be found in the node store clientlist: 2: No such
+> file or directory: /path/to/obnam/clientlist/nodes/0/0/0/2
+>=20
+> What does this error mean? Is there any way I can make the backup
+> accessible again?
+
+I suspect it means your backup repository is partially corrupted.
+Sorry. That's bad news.
+
+https://obnam.org/faq/missing-node/ may or may not be useful to you.
+
+Obnam does not have a way to fix that or to recover from that. I
+recommend you can switch to a new backup program before you need to
+restore data. (In any case, you should do that by the end of the year,
+as Obnam is retiring.)
+
+--=20
+I want to build worthwhile things that might last. --joeyh
+
+--cnzyj3daxlr64v7f
+Content-Type: application/pgp-signature; name="signature.asc"
+
+-----BEGIN PGP SIGNATURE-----
+
+iQIzBAABCgAdFiEETNTnrewG6wEE1EJ3bC+mFux6IDEFAloRZMEACgkQbC+mFux6
+IDF1RA/+O2d24n6H8iUopAlXBZSAWNXXuO0LygFWSc4XksFSJWjTPKjt2fHcsJAN
+bXUTkSqNZ3PMNUG/yM0Pw88Xw31DIroIwwgwkbo2GK7emCu8c3WH0upE9P647Ia4
+YJdlOqgiZE2311t4zOrwp48Twpl92UrAGtPYCVZBsiWNj3tWEZanHG8YMRJlu2WN
+K6Qyq9S4S9jcOCbLC6Bs3u2Xnp8jHKmWhkKuwKoDb35nc2f2KIpvlEEyjA5wg5UD
+0pgB93lSzRGkYf+s8QaPu6MOXRNdOLrGx2mDzPyIJ5nNFYA1tHuSWf6OZab7F2sQ
+6oLh9AmiY8eHLTQk1D3XHWmFtisaKTUVXkEtQbsUjyYcSp+UdAQl8xjbzd0CG/Uh
+a0VrwJKq8zC3NQEotP35Xnw9GIb5mS8OAZQJUNJnIWXrz/DY3rhhgrYmlqgVnZrw
+D3+8YeaEM6i22sle3rY7ZKpczEhhgNM8IGknpA4si0Uj2XzmOJsZJ7BA4+kis/vG
+TwLGt29HY3B51KthWvDBq7chVyD2D2PTAPIHxjmkU7+NxfEZJIsY51r8Ug+M4s40
+ANbV3B7zgEHxxaslRSTgySLg+5VSfx9MMXNnLj7ScFpRJHWeTwqMBSmnhQELdYK8
+TTOSKNbUnfqPR8M+USmevYECMyChOkYY17nKyTEeQ12WFxjE3LM=
+=9DR0
+-----END PGP SIGNATURE-----
+
+--cnzyj3daxlr64v7f--
+
+
+--===============3273633122374331017==
+Content-Type: text/plain; charset="us-ascii"
+MIME-Version: 1.0
+Content-Transfer-Encoding: 7bit
+Content-Disposition: inline
+
+_______________________________________________
+obnam-support mailing list
+obnam-support@obnam.org
+http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
+
+--===============3273633122374331017==--
+
diff --git a/tickets/abc93b44517543a8a5892e8c1bddce2b/Maildir/new/1511191530.M37026P31598Q1.koom b/tickets/abc93b44517543a8a5892e8c1bddce2b/Maildir/new/1511191530.M37026P31598Q1.koom
new file mode 100644
index 0000000..0721628
--- /dev/null
+++ b/tickets/abc93b44517543a8a5892e8c1bddce2b/Maildir/new/1511191530.M37026P31598Q1.koom
@@ -0,0 +1,163 @@
+Return-Path: <obnam-support-bounces@obnam.org>
+X-Original-To: distix@pieni.net
+Delivered-To: distix@pieni.net
+Received: from yaffle.pepperfish.net (yaffle.pepperfish.net [88.99.213.221])
+	by pieni.net (Postfix) with ESMTPS id 093F242A91
+	for <distix@pieni.net>; Mon, 20 Nov 2017 09:24:45 +0000 (UTC)
+Received: from platypus.pepperfish.net (unknown [10.112.101.20])
+	by yaffle.pepperfish.net (Postfix) with ESMTP id E6A3B41886;
+	Mon, 20 Nov 2017 09:24:44 +0000 (GMT)
+Received: from ip6-localhost.nat ([::1] helo=platypus.pepperfish.net)
+	by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
+	id 1eGiJo-0000Tu-Tn; Mon, 20 Nov 2017 09:24:44 +0000
+Received: from [10.112.101.21] (helo=mx3.pepperfish.net)
+ by platypus.pepperfish.net with esmtps (Exim 4.80 #2 (Debian))
+ id 1eGU75-0005gS-AP
+ for <obnam-support@obnam.org>; Sun, 19 Nov 2017 18:14:39 +0000
+Received: from mail-qt0-f178.google.com ([209.85.216.178])
+ by mx3.pepperfish.net with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
+ (Exim 4.89) (envelope-from <sanskritfritz@gmail.com>)
+ id 1eGU72-00080y-N0
+ for obnam-support@obnam.org; Sun, 19 Nov 2017 18:14:39 +0000
+Received: by mail-qt0-f178.google.com with SMTP id a19so12405009qtb.3
+ for <obnam-support@obnam.org>; Sun, 19 Nov 2017 10:14:30 -0800 (PST)
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
+ h=mime-version:in-reply-to:references:from:date:message-id:subject:to
+ :cc; bh=KEI2ueOZxqEQYyKjGnh4p76ugkQTPyEP3U8/Del5nGQ=;
+ b=YpXoD5DNQYTz3MmyZ9s8udsMlVe7ahlM+c6M0gJ6vmFuq6nsUeIcNWZYrpCkz/cLPb
+ RrzrLE8OUPtLR6ZDrMkzT0rZf5rQ7G1zmIFKGKLsCbOkeRaZ9L4+VCmmWASjIjyxZzGJ
+ ekToZSefwtGV7P54JD+6IzFxmi4dfm9XdMEVEarjkn+DZsgnpYdeQKRLQ1k5NSJwI6IK
+ V/IuwYFT4uRpkuee3Gnj3tfDWBRlQucAdsNSk6kDKXvRyJNwRhmtGxNBrtNJmj2PXGSl
+ 9uhO5msN5+yRIWs+iaAFPmHJiG7R1gF9GcniySzu9u5P89+VlV3Gyuxq3bMHzBsy7MIE
+ nQiQ==
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
+ d=1e100.net; s=20161025;
+ h=x-gm-message-state:mime-version:in-reply-to:references:from:date
+ :message-id:subject:to:cc;
+ bh=KEI2ueOZxqEQYyKjGnh4p76ugkQTPyEP3U8/Del5nGQ=;
+ b=IDxzV/FNE+MritDmVqg/z6YKM5zinpf4LM5UZFhfURFXW5Vr+mNKVDdUc9QjHHbWW4
+ IOM12qvlVQUQNOnWpjlgf/JVRRqdGQJQS3QFPxVIO762HbeRrYMX4GbRuEI5CnjCcndT
+ w8izrhC08nxK0k7C6Z+6N9N1HoR69Z8uTqu5SicPlA1A4pjyBzeMqmbhoMkzVauCFoSc
+ pg1+wUG1NdXV2fOWBRa5kFtQ3D4FV5HlU+4s3nA213HnCLzHewyj6S/w3vrANhLnMUGG
+ cZ5A0tmbYi9w933qHmwfdMBvg3ALr6cBy4bpyDYrK3jTilvDfZPL1tgGtlQSDe1bfb5h
+ GzyA==
+X-Gm-Message-State: AJaThX7dAecBgapy+parUHdnjBI+dXNCngvzAbMxUv4A/eQckXV222ne
+ jx0Ob7oM7LuRmltJ0j30sN1RKRFRFlcG5gBIxSY=
+X-Google-Smtp-Source: AGs4zMan4ExnUexvRG4Tdv1j66RaCV2rEOEEDM9EsNf5ZDeDbPrGRQ/m0lGohUDpugxtaNfOOGktWOTCFxMAuJ4mwKM=
+X-Received: by 10.200.49.166 with SMTP id h35mr17576075qte.293.1511115268963; 
+ Sun, 19 Nov 2017 10:14:28 -0800 (PST)
+MIME-Version: 1.0
+Received: by 10.237.42.2 with HTTP; Sun, 19 Nov 2017 10:13:48 -0800 (PST)
+In-Reply-To: <42bd837a-4b4b-6cb4-252f-9ab322f70dba@duering-andreas.de>
+References: <42bd837a-4b4b-6cb4-252f-9ab322f70dba@duering-andreas.de>
+From: SanskritFritz <sanskritfritz@gmail.com>
+Date: Sun, 19 Nov 2017 19:13:48 +0100
+Message-ID: <CAExbbMw9CPqYqH=-LbNGYdWotZ8i10XKBid2dXvRcpF0o+EkHg@mail.gmail.com>
+To: Andreas <mailing@duering-andreas.de>
+X-Pepperfish-Transaction: 4cfa-6f43-466d-1688
+X-Spam-Score: 1.5
+X-Spam-Score-int: 15
+X-Spam-Bar: +
+X-Scanned-By: pepperfish.net, Sun, 19 Nov 2017 18:14:39 +0000
+X-Spam-Report: Content analysis details: (1.5 points)
+ pts rule name              description
+ ---- ---------------------- --------------------------------------------------
+ 0.2 PPF_ALTERNATIVES       Body in multipart/alternative
+ 1.0 PPF_FROM_CONTAINS_MAIL The From header contains 'mail'
+ 0.5 PPF_RECEIVED_HTTP      Received header mentions http
+ 1.2 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
+ (sanskritfritz[at]gmail.com)
+ -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
+ [score: 0.0000]
+ 0.3 HTML_MESSAGE           BODY: HTML included in message
+ 1.0 PPF_BLANK              RAW: Body contains _blank
+ 0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
+ not necessarily valid
+ -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
+ -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's
+ domain -0.0 RCVD_IN_MSPIKE_H3      RBL: Good reputation (+3)
+ [209.85.216.178 listed in wl.mailspike.net]
+ -0.7 RCVD_IN_DNSWL_LOW      RBL: Sender listed at http://www.dnswl.org/, low
+ trust [209.85.216.178 listed in list.dnswl.org]
+ -0.0 RCVD_IN_MSPIKE_WL      Mailspike good senders
+X-ACL-Warn: message may be spam
+X-Scan-Signature: 2c50e0cfd6ac8342e87940d191065d4f
+X-Mailman-Approved-At: Mon, 20 Nov 2017 09:24:43 +0000
+Cc: Obnam <obnam-support@obnam.org>
+Subject: Re: ERROR: Node cannot be found in the node store clientlist
+X-BeenThere: obnam-support@obnam.org
+X-Mailman-Version: 2.1.5
+Precedence: list
+List-Id: Obnam backup software discussion <obnam-support-obnam.org>
+List-Unsubscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org>,
+ <mailto:obnam-support-request@obnam.org?subject=unsubscribe>
+List-Archive: <http://listmaster.pepperfish.net/pipermail/obnam-support-obnam.org>
+List-Post: <mailto:obnam-support@obnam.org>
+List-Help: <mailto:obnam-support-request@obnam.org?subject=help>
+List-Subscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org>,
+ <mailto:obnam-support-request@obnam.org?subject=subscribe>
+Content-Type: multipart/mixed; boundary="===============6201400071940807189=="
+Mime-version: 1.0
+Sender: obnam-support-bounces@obnam.org
+Errors-To: obnam-support-bounces@obnam.org
+
+--===============6201400071940807189==
+Content-Type: multipart/alternative; boundary="001a11c13428d2429b055e59f01e"
+
+--001a11c13428d2429b055e59f01e
+Content-Type: text/plain; charset="UTF-8"
+
+On Sat, Nov 18, 2017 at 12:28 PM, Andreas <mailing@duering-andreas.de>
+wrote:
+
+> ERROR: Node 0x2 cannot be found in the node store clientlist: 2: No such
+> file or directory: /path/to/obnam/clientlist/nodes/0/0/0/2
+>
+> What does this error mean? Is there any way I can make the backup
+> accessible again?
+>
+
+This means, some files are missing from the repository. Maybe disk
+corruption, or partial download, you have to figure it out.
+If nothing helps, try
+obnam fsck --fsck-fix
+and see if obnam does rescue parts of the repository.
+
+--001a11c13428d2429b055e59f01e
+Content-Type: text/html; charset="UTF-8"
+Content-Transfer-Encoding: quoted-printable
+
+<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
+On Sat, Nov 18, 2017 at 12:28 PM, Andreas <span dir=3D"ltr">&lt;<a href=3D"=
+mailto:mailing@duering-andreas.de" target=3D"_blank">mailing@duering-andrea=
+s.de</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
+rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
+1ex">ERROR: Node 0x2 cannot be found in the node store clientlist: 2: No su=
+ch<br>
+file or directory: /path/to/obnam/clientlist/<wbr>nodes/0/0/0/2<br>
+<br>
+What does this error mean? Is there any way I can make the backup<br>
+accessible again?<br></blockquote></div></div><div class=3D"gmail_extra"><b=
+r></div><div class=3D"gmail_extra">This means, some files are missing from =
+the repository. Maybe disk corruption, or partial download, you have to fig=
+ure it out.</div><div class=3D"gmail_extra">If nothing helps, try <br></div=
+><div class=3D"gmail_extra">obnam fsck --fsck-fix</div><div class=3D"gmail_=
+extra">and see if obnam does rescue parts of the repository.<br></div><div =
+class=3D"gmail_extra"><br></div></div>
+
+--001a11c13428d2429b055e59f01e--
+
+
+--===============6201400071940807189==
+Content-Type: text/plain; charset="us-ascii"
+MIME-Version: 1.0
+Content-Transfer-Encoding: 7bit
+Content-Disposition: inline
+
+_______________________________________________
+obnam-support mailing list
+obnam-support@obnam.org
+http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
+
+--===============6201400071940807189==--
+