Easy <Easy@lantis.com> wrote:
/snipT
>
>>FYI
in
MiD: <68f0c5tahb0gprmjgfe4kv44m5mjgchrsi@4ax.com>
>An encoding error was detected in the attachment
>Us Agent users
>
You can tell I never attempted downloading and decoding?
Code view of one article was the most I would go to, today.
I have been at this (fixing NB posts) quite a while now <s>
>
>For Hopper OESD 12250 "OESD 12250 Swan Lace.zip" (*/5) yEnc 2015195
>Bytes
>This is what we see.
>Normally the word yEnc should be infront of (*/5)
>the Bytes size should not be there, too
>
This (Subject header borking) is a left over from those who used Chris
Morse's code in building their own 'flavour' of PowerPost.
As an aside, Sharkpost does not allow these errors. Byte size display
is optional in SP also. Everything else aside, SP was built to work
around that which newbs would aptly fall into as traps when posting
for the first time. There is why I do support SP.
>If yoy can post it as
>For Hopper OESD 12250 "OESD 12250 Swan Lace.zip" yEnc (*/5)
>then it might work
>Title "$F"
>is all you need to do.
>
If, after five years of posting , "bluerope81" requires this level of
coaching then what hope is there of educating other users of tools
like NL and web based NNTP access.. etc?
I quote directly.
<IIqdnac0jfz7JiLXnZ2dnUVZ_jmdnZ2d@giganews.com>
" I have been using Newsbin for over five
years and have never had any problems
posting or receiving."
And..
I drag your followup back to this thread as it is my experience that
following up to anything posted in binary by "bluerope81" is ignored.
Possibly because the poster does not see follow-ups to binary.
Don't know really.. but it (keeping to this thread s/he IS reading) is
worth a shot.
thanks... again.
|
|