From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1GE4LV-0008M1-9e for garchives@archives.gentoo.org; Fri, 18 Aug 2006 13:25:09 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.7/8.13.6) with SMTP id k7IDMxX9029249; Fri, 18 Aug 2006 13:22:59 GMT Received: from smtp19.wxs.nl (smtp19.wxs.nl [195.121.247.10]) by robin.gentoo.org (8.13.7/8.13.6) with ESMTP id k7IDKkCo020452 for ; Fri, 18 Aug 2006 13:20:46 GMT Received: from graskamp (ip51cfa1ef.direct-adsl.nl [81.207.161.239]) by smtp19.wxs.nl (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0J4700F9K3QM9J@smtp19.wxs.nl> for gentoo-user@lists.gentoo.org; Fri, 18 Aug 2006 15:20:46 +0200 (CEST) Date: Fri, 18 Aug 2006 15:20:05 +0200 From: Benno Schulenberg Subject: Re: [gentoo-user] Re: Stefans posts on gentoo-user In-reply-to: <20060818113127.GA18007@xs4all.nl> To: gentoo-user@lists.gentoo.org Message-id: <200608181520.05537.benno.schulenberg@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-disposition: inline User-Agent: KMail/1.9.4 References: <20060817154058.GA7891@nibiru.local> <5873584.ayGoQ11FZm@m-id.message-center.info> <20060818113127.GA18007@xs4all.nl> Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by robin.gentoo.org id k7IDMxXd029249 X-Archives-Salt: 43ebf01a-325d-4e25-a3c2-79b51214ac84 X-Archives-Hash: 38a64cf7f11ccff3b14cbd27e74667e6 Stefan Wimmer wrote: > Only if I post to gmane.linux.gentoo.amd64 or > gmane.linux.gentoo.user the problem with the headers in the body > appears :( It is probably a bug at Gentoo: look at the "X-Virus-Scanned:=20 amavisd-new at gentoo.org" header that is inserted in Stefan's=20 slrn-messages at a correct place. But after that the other extra=20 headers get misplaced. Maybe this bug is being triggered by the=20 first line of Stefan's slrn-messages starting with a space? As=20 such a space normally means "continuation of previous line". Could you try adapting the attribution line of slrn to not start=20 with a space, Stefan? > Still want to blame me that I'm messed up my slrn config? Sorry, but I don't think Alexander suggested that anything was wrong=20 with your config, Stefan, just with slrn itself. Benno --=20 Cetere mi opinias ke ne =C4=89io tradukenda estas. --=20 gentoo-user@gentoo.org mailing list