Hi,
My build of Pan here is having extreme difficulties with binary postings that
are in yEnc format but not marked on the Subject line as such.
See the clips below for what I mean, please.
I looked into where Pan stores each Message-ID (its articles-cache).
I see the poster is using a beta of Yenc-Power-Post.
I clearly remember this has been such a common mistake with some m$ software
over the years, and I do remember his posting app has been 'implicated',
historically speaking.
I told the poster via email, first of all, that the software is not following
established posting criteria -- it is suppose to put the chars 'yEnc'
SOMEWHERE on the SUBJECT line for EACH msg.
There is no real way for a newsreader to tell what a msg has in it UNTIL it
is too late -- i.e. until the body of the msg has been fetched, and by that
time Pan has probably already botched it.
Once the Subject line has the correct clue with 'yEnc' coded there, I think
these bugs will hopefully disappear. This _has_ been the historical fix in
almost all such circumstances for a wide variety of softwares.
Secondly, Pan is definitely generating junk Message-ID strings somehow, we do
not see the simple ending of .com as his msg clip shows below. Again I say
if the Subject line had the proper clue-string of yEnc, I think maybe this
might be fixed also.
A clip from one of his posts as we see it:
-begin-
Path:
Xby.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.co[…]
From: address@hidden (Squee)
Sender: address@hidden
Newsgroups: alt.binaries.chaka,alt.binaries.multimedia.teen-idols
Subject: Crazy Christmas Lights-2009-12-06-0.tp (0666/6746)
X-Newsposter: Yenc-Power-Post-GB-12 Beta 7 12.2.7.0 (Modified POWER-POST)
Organization: UseNetServer - www.usenetserver.com
X-Complaints-To: address@hidden
Message-ID:<address@hidden>
Date: 31 Dec 2009 04:41:49 GMT
Lines: 1984
Bytes: 258116
Xref: number.nntp.dca.giganews.com alt.binaries.multimedia.teen-idols:42219634
alt.binaries.chaka:14263130
=ybegin part=666 line=128 size=1683555808 name=Crazy Christmas
Lights-2009-12-06-0.tp
=ypart begin=165984001 end=166233600
[…]
-end-
his posted Subject line is:
Subject: Crazy Christmas Lights-2009-12-06-0.tp (0666/6746)
for yencoded binary, it needs to be like this:
Subject: Crazy Christmas Lights-2009-12-06-0.tp yEnc (0666/6746)
. the diff here ---------------------------------^^^^^
Yes a simple fix like that has been well-known to fix it for people grabbing
these kinds of files.
I cannot find relevent material using Ask.com, this kind m$ crap "pollutes"
most databases like that. But I most-definitely rmbr this has been a
terrible sore-point with Usenet users using crap software.
Also, as far as what Pan sees, his Message-ID line is:
"Message-ID:<address@hidden>"
where we ought to be getting the msg-id string as this:
"address@hidden"
but instead we are getting a much-longer junk string as this:
"address@hidden ^U%838%973235)"
I do not know where the extra stuff is coming from, e.g.
past '.com' on-thru the close-parens ')' .
See what I mean?
Using that junk cache-filename and sending such request to news-servers, then
Pan cannot find the parts anywhere.
And so the posts have been failing very miserably on our end.
I still think doing the Subject-line-fix-'yEnc' above is a possible solution,
very definitely his posting app is not following those standards.
Please help?
Am I anywhere near correct with Pan?
(If some of you do not mind, please try fetching the binary postings yourself
using the clip's info … the tp file should be directly playable with VLC)
(info for my own Pan build is in the header for this very post itself, I am
using it to post thru gmane)
Thank you for any help.
_______________________________________________
Pan-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/pan-users