FUDforum
Fast Uncompromising Discussions. FUDforum will get your users talking.

Home » FUDforum Development » Bug Reports » NNTP - cannot handle recursive boundaries
Show: Today's Messages :: Polls :: Message Navigator
Switch to threaded view of this topic Create a new topic Submit Reply
NNTP - cannot handle recursive boundaries [message #163088] Sun, 26 September 2010 02:50 Go to next message
tux99   Switzerland
Messages: 44
Registered: September 2010
Karma: 0
Member
I have the same problem.
I'm trying to import into FUDforum (3.0.1) from news.gmane.org the group gmane.linux.mageia.devel (currently 216 msgs)

The import works but some messages are blank apart from the mailing list footer.

Here is the source of one of these messages:
Path: news.gmane.org!not-for-mail
From: Tomasz =?ISO-8859-2?B?UGF3ZbM=?= Gajc <phenomenal-5tc4TXWwyLM(at)public(dot)gmane(dot)org>
Newsgroups: gmane.linux.mageia.devel
Subject: Re: i686 must be Pentium II ?
Date: Tue, 21 Sep 2010 23:38:01 +0200
Organization: TPG
Lines: 67
Approved: news(at)gmane(dot)org
Message-ID: <20100921233801(dot)05e0bde2(at)wp(dot)pl>
References: <20100920113601(dot)1E732770(at)resin18(dot)mta(dot)everyone(dot)net>
	<20100920223121(dot)27eb7d67(at)wp(dot)pl>
	<201009212334(dot)07561(dot)anssi(dot)hannula(at)iki(dot)fi>
Reply-To: Mageia development mailing-list <mageia-dev-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org>
NNTP-Posting-Host: lo.gmane.org
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1177452004=="
X-Trace: dough.gmane.org 1285105096 16453 80.91.229.12 (21 Sep 2010 21:38:16 GMT)
X-Complaints-To: usenet(at)dough(dot)gmane(dot)org
NNTP-Posting-Date: Tue, 21 Sep 2010 21:38:16 +0000 (UTC)
To: mageia-dev-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org
Original-X-From: mageia-dev-bounces-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org Tue Sep 21 23:38:15 2010
Return-path: <mageia-dev-bounces-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org>
Envelope-to: glmd-mageia-dev(at)m(dot)gmane(dot)org
Original-Received: from ryu.zarb.org ([212.85.158.22])
	by lo.gmane.org with esmtp (Exim 4.69)
	(envelope-from <mageia-dev-bounces-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org>)
	id 1OyAXW-0006LR-I1
	for glmd-mageia-dev(at)m(dot)gmane(dot)org; Tue, 21 Sep 2010 23:38:14 +0200
Original-Received: from localhost (localhost [127.0.0.1])
	by ryu.zarb.org (Postfix) with ESMTP id 86C74964FC;
	Tue, 21 Sep 2010 23:38:13 +0200 (CEST)
X-Virus-Scanned: amavisd-new at zarb.org
Original-Received: from ryu.zarb.org ([127.0.0.1])
	by localhost (ryu.zarb.org [127.0.0.1]) (amavisd-new, port 10025)
	with ESMTP id oEoajQNT5XSK; Tue, 21 Sep 2010 23:38:12 +0200 (CEST)
Original-Received: from ryu.zarb.org (localhost [127.0.0.1])
	by ryu.zarb.org (Postfix) with ESMTP id EF44496508;
	Tue, 21 Sep 2010 23:38:11 +0200 (CEST)
X-Original-To: mageia-dev-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org
Delivered-To: mageia-dev-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org
Original-Received: from localhost (localhost [127.0.0.1])
	by ryu.zarb.org (Postfix) with ESMTP id B4A2F96508
	for <mageia-dev-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org>; Tue, 21 Sep 2010 23:38:09 +0200 (CEST)
X-Virus-Scanned: amavisd-new at zarb.org
Original-Received: from ryu.zarb.org ([127.0.0.1])
	by localhost (ryu.zarb.org [127.0.0.1]) (amavisd-new, port 10025)
	with ESMTP id VbFomjhnorfz for <mageia-dev-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org>;
	Tue, 21 Sep 2010 23:38:08 +0200 (CEST)
Original-Received: from mx4.wp.pl (mx4.wp.pl [212.77.101.8])
	by ryu.zarb.org (Postfix) with ESMTPS id 23B4D964FC
	for <mageia-dev-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org>; Tue, 21 Sep 2010 23:38:08 +0200 (CEST)
Original-Received: (wp-smtpd smtp.wp.pl 8437 invoked from network);
	21 Sep 2010 23:38:06 +0200
Original-Received: from abcz29.neoplus.adsl.tpnet.pl (HELO localhost)
	(phenomenal-5tc4TXWwyLM(at)public(dot)gmane(dot)org@[83.6.241.29]) (envelope-sender <phenomenal-5tc4TXWwyLM(at)public(dot)gmane(dot)org>)
	by smtp.wp.pl (WP-SMTPD) with SMTP
	for <mageia-dev-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org>; 21 Sep 2010 23:38:06 +0200
In-Reply-To: <201009212334(dot)07561(dot)anssi(dot)hannula-X3B1VOXEql0(at)public(dot)gmane(dot)org>
X-Mailer: Claws Mail 3.7.6 (GTK+ 2.21.8; x86_64-mandriva-linux-gnu)
X-WP-AV: skaner antywirusowy poczty Wirtualnej Polski S. A.
X-WP-SPAM: NO 0000000 [URP1]                               
X-BeenThere: mageia-dev-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mageia development mailing-list <mageia-dev.mageia.org>
List-Unsubscribe: <https //www mageia.org/mailman/options/mageia-dev>,
	<mailto mageia-dev-request-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org?subject=unsubscribe>
List-Archive: </pipermail/mageia-dev>
List-Post: <mailto:mageia-dev-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org>
List-Help: <mailto:mageia-dev-request-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org?subject=help>
List-Subscribe: <https //www.mageia.org/mailman/listinfo/mageia-dev>,
	<mailto:mageia-dev-request-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org?subject=subscribe>
Original-Sender: mageia-dev-bounces-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org
Errors-To: mageia-dev-bounces-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org
Xref: news.gmane.org gmane.linux.mageia.devel:120
Archived-At: <http //permalink.gmane.org/gmane.linux.mageia.devel/120>

--===============1177452004==
Content-Type: multipart/signed; micalg=PGP-SHA1;
	boundary="Sig_/hpQ1nrrUF86gahk2I1_n.1W";
	protocol="application/pgp-signature"

--Sig_/hpQ1nrrUF86gahk2I1_n.1W
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: quoted-printable

Dnia 2010-09-21, o godz. 23:34:07
Anssi Hannula <anssi(dot)hannula-X3B1VOXEql0(at)public(dot)gmane(dot)org> napisa=B3(a):

> On Monday 20 September 2010 23:31:21 Tomasz Pawe=B3 Gajc wrote:
> > Dnia 2010-09-20, o godz. 11:36:01
> >=20
> > Andr=E9 Machado <afmachado-pnw+BTqYLJhBDgjK7y7TUQ(at)public(dot)gmane(dot)org> napisa=B3(a):
> > > Guys,
> > >=20
> > > Mandriva - and many other distros, such like Arch Linux - are
> > > optimized to i686 architeture, what means Pentium II. Despite the
> > > need to keep compatibility with older machines, what would be the
> > > problem if packages was compiled aganist Pentium III or 4? Would
> > > the system gain more speed?
> >=20
> > x86 is a dead end. It would be nice to see sse/sse2 enabled by
> > default for x86_64
>=20
> It always has been enabled there.
>=20

iirc it wasn't because of some geode compatibility crap, but i can be
wrong here

--=20
Regards
TPG

http //cia.vc/stats/author/tpg
---

--Sig_/hpQ1nrrUF86gahk2I1_n.1W
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

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

iEYEARECAAYFAkyZJbkACgkQXdLYfhsJ+rg5kwCcCbZ4J+xtpTyNb0pky82x7NJB
t4MAnjkxJaLa/s+a4qjW0xeDcTAU+cQZ
=mA1Y
-----END PGP SIGNATURE-----

--Sig_/hpQ1nrrUF86gahk2I1_n.1W--

--===============1177452004==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mageia-dev mailing list
Mageia-dev-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org
https //www.mageia.org/mailman/listinfo/mageia-dev

--===============1177452004==--


The only part that shows up in FUDforum is:

Quote:
_______________________________________________
Mageia-dev mailing list
Mageia-dev-odJJhXpcy38dnm+yROfE0A(at)public(dot)gmane(dot)org
https //www.mageia.org/mailman/listinfo/mageia-dev

--


(I had to edit the http links in the above msg since I'm not allowed links as a newbie)
Re: NNTP - empty message bodies [message #163095 is a reply to message #163088] Sun, 26 September 2010 10:28 Go to previous messageGo to next message
naudefj is currently offline  naudefj   South Africa
Messages: 3771
Registered: December 2004
Karma: 28
Senior Member
Administrator
Core Developer
The problem is in parse_mime_attachments() in nntp.inc. However, I have no idea how we are going to fix it.

The function splits the message by boundary="===============1177452004==", but cannot handle the nested boundary="Sig_/hpQ1nrrUF86gahk2I1_n.1W" in the first part. As the first section doesn't look like text, it only uses the second part of the message.

We need to somehow implement recursive boundary checking.
Re: NNTP - empty message bodies [message #163100 is a reply to message #163095] Sun, 26 September 2010 16:59 Go to previous messageGo to next message
tux99   Switzerland
Messages: 44
Registered: September 2010
Karma: 0
Member
Thanks for looking at it, isn't there maybe some php mime library that could be used?

I find this, don't know if it could help since I'm not a PHP programmer:
http://www.phpclasses.org/package/3169-PHP-Decode-MIME-e-mail-messages.html
Re: NNTP - empty message bodies [message #163101 is a reply to message #163100] Sun, 26 September 2010 17:29 Go to previous messageGo to next message
naudefj is currently offline  naudefj   South Africa
Messages: 3771
Registered: December 2004
Karma: 28
Senior Member
Administrator
Core Developer
It might just work, I'll check it out.
Re: NNTP - empty message bodies [message #163133 is a reply to message #163101] Fri, 01 October 2010 20:50 Go to previous messageGo to next message
naudefj is currently offline  naudefj   South Africa
Messages: 3771
Registered: December 2004
Karma: 28
Senior Member
Administrator
Core Developer
I've managed to abstract the MIME code from the Mailing List Manager into a separate class that can also be used for Usenet posts.
Looks like it's working like a charm.
Will commit it after more testing.
Re: NNTP - empty message bodies [message #163139 is a reply to message #163133] Sat, 02 October 2010 06:31 Go to previous message
tux99   Switzerland
Messages: 44
Registered: September 2010
Karma: 0
Member
naudefj wrote on Fri, 01 October 2010 22:50
I've managed to abstract the MIME code from the Mailing List Manager into a separate class that can also be used for Usenet posts.
Looks like it's working like a charm.
Will commit it after more testing.


That sounds great, I'm looking forward to it.
I was actually wondering why the same messages that import fine directly from the ML, have these MIME problems when going through gmane.org (which is a ML to NNTP gateway).

[Updated on: Sat, 02 October 2010 06:32]

Report message to a moderator

  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: post.php parse error with safe mode FUD install
Next Topic: Fudforum ML import doesnt seem to like UTF8 From: lines
Goto Forum:
  

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Sat May 18 17:49:07 GMT 2024

Total time taken to generate the page: 0.03053 seconds