| Re: PING Leeky |
EasyNews, UseNet made Ea .. |
| TH1 (th1@x.invalid) |
2006/02/07 17:28 |
On Tue, 07 Feb 2006 22:04:40 GMT, "ben" <ben@home.com> wrote:
>Hi - why aren't any of your posts complete in EasyNews, do you know? I use
>Forte.
>thks
>B
I recently signed up for Forte's free trial offer and I was a little
surprised to find that alt.fan.poly was still downloading from
Easynews since I have set Forte as the highest priority server to
download from in Agent 3.2. When I looked up the newsgroup listing,
it alt.fan.poly was carried by Forte, but all the binary posts were
completely missing from Forte. Small text messages only are getting
through to Forte.
So you appear to have things back to front - the posts are complete on
Easynews, and virtually non-existent on Forte.
There are two possible explanations that I can see for this. The
first one is that the recent posts here are mostly from leeky, and he
is posting using a news article size of around 750 kbytes. This is
well over the maximum of around 500 kbytes that a lot of news services
accept. So either Forte or one of the news servers between the
posting server and Forte could be dropping all oversize news articles.
Other posters too may be using oversize news articles - I have not
checked. This is a really bad idea unless you deliberately want to
limit the propagation of your post.
The other possible explanation is that this is not an official binary
group (it is not in the alt.binaries tree), and so either Forte or one
of the news servers between Forte and the posters is dropping all
binary posts. This is sometimes done by checking for UUencoding or
yEnc encoding in the body of the news articles, but more often seems
to be done by just setting the maximum allowed news article size to a
much smaller setting, typically around 100 kbytes.
So, if the posters would like to get their posts to most news servers,
instead of just those that accept news articles over the standard 500
kbytes limit, they should adjust their PowerPost "Default Max Lines
Per Part:" setting to no more than 3000 lines. yEnc lines are 128
bytes each, so 3000 lines is 384,000 bytes, well clear of the 500
kbyte limit and allowing plenty of room for header overheads and
expansion when a post contains characters that the yEnc encoding has
to escape.
If the posts still do not get through, then setting "Default Max Lines
Per Part:" to say 640 or 750 lines would produce news articles well
clear of the 100 kbytes size. It would be worth trying such a post to
see if it gets through. Having lots more smaller news articles does
mean that you get higher overheads, as there are headers on each news
article, but the extra overheads are not too huge.
If any of the posters out there are interested, I have written a guide
that explains how it all works and contains some examples and
recommended settings for posting software. I will try posting a copy
of it and a larger binary file using 640 lines in PowerPost as a test
to see if it will get through to Forte.
|
|
|