From mboxrd@z Thu Jan  1 00:00:00 1970
From: Sven Eckelmann <sven.eckelmann@gmx.de>
Subject: Re: [B.A.T.M.A.N.] [PATCH] Send TUNNEL_IP_REQUEST as response of
	TUNNEL_IP_REQUEST
Date: Fri, 26 Sep 2008 13:39:30 +0200
References: <20080924215939.GA9277@sven-desktop.lazhur.ath.cx>
	<200809251133.19049.sven.eckelmann@gmx.de>
	<98ded638d254e60e1038e55af9dd7c1e.squirrel@wm.ddmesh.de>
In-Reply-To: <98ded638d254e60e1038e55af9dd7c1e.squirrel@wm.ddmesh.de>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart2058467.E0ZmzRlNgm";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <200809261339.33036.sven.eckelmann@gmx.de>
Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
List-Id: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n.open-mesh.net>
List-Unsubscribe: <https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n>,
	<mailto:b.a.t.m.a.n-request@open-mesh.net?subject=unsubscribe>
List-Archive: <http://list.open-mesh.net/pipermail/b.a.t.m.a.n>
List-Post: <mailto:b.a.t.m.a.n@open-mesh.net>
List-Help: <mailto:b.a.t.m.a.n-request@open-mesh.net?subject=help>
List-Subscribe: <https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n>,
	<mailto:b.a.t.m.a.n-request@open-mesh.net?subject=subscribe>
To: The list for a Better Approach To Mobile Ad-hoc Networking <b.a.t.m.a.n@open-mesh.net>

--nextPart2058467.E0ZmzRlNgm
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Friday 26 September 2008 13:19:19 Stephan Enderlein (Freifunk Dresden)=20
wrote:
> [...]
> When I display the complete email header of you emails I have the followi=
ng
> line:
> "In-Reply-To: <6fd627b9bdd448cd88026446baddb8a5.squirrel@wm.ddmesh.de>"
> For some reason you are creating emails with that header entry instead
> without it.
Can you please say which mail you mean? I checked different [PATCH] mails f=
rom=20
me (send by mailman back to me) and cannot find it. The only ones which hav=
e=20
them are the the real answers to your mails - which off course have referen=
ces=20
to them.

grep -rli "6fd627b9bdd448cd88026446baddb8a5.squirrel@wm.ddmesh.de" *|xargs=
=20
grep Subject                                                               =
                   =20
1222335445.3922.Wd6Iu:2,S:Subject: Re: [B.A.T.M.A.N.] [PATCH] Send=20
TUNNEL_IP_REQUEST as response of

1222334362.3922.FhPMA:2,RS:Subject: Re: [B.A.T.M.A.N.] [PATCH] Send=20
TUNNEL_IP_REQUEST as response of

1222428286.3965.lxuDX:Subject: Re: [B.A.T.M.A.N.] [PATCH] Send=20
TUNNEL_IP_REQUEST as response o


> Please also look at the archive at
> https://list.open-mesh.net/pipermail/b.a.t.m.a.n/2008-September/thread.ht=
ml
>. You will see that only your mails are always appended to other threads a=
nd
> are not starting as a new thread. All answers are currently under
> "[B.A.T.M.A.N.] batman-exp hang on 95% CPU load" which definitively do not
> belong to the subject.
> Please check your environment.
I have asked dotslash to check it on his machine and he doesn't see my mail=
s=20
in your threads in mutt. It's the same with kmail and probably with many ot=
her=20
mail clients. I cannot find the problem on my site so I would say that it i=
s a=20
problem of mailman's archive output. I have contacted the postmaster of ope=
n-
mesh, but got no answer until now.

Best regards
	Sven Eckelmann

--nextPart2058467.E0ZmzRlNgm
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkjcyfIACgkQqQGwKVlMoDuSFgCg56PoHNB0NwChIZwzbg6rW2DI
S6sAn3PagiPlbJF8TGcPxmBscIdZzktd
=Jsjf
-----END PGP SIGNATURE-----

--nextPart2058467.E0ZmzRlNgm--