alt.windows7.general01.nfo (1/1)

MariJuana wrote:



This is not a binary newsgroup.

"VanguardLH" wrote:
This is not a binary newsgroup.

That must be why I cant see the original post.
Do individual.net carry binary groups? They're not managing their
server very well if they allow binary posts in text-only groups.

VanguardLH wrote:
MariJuana wrote:


This is not a binary newsgroup.

A lot of servers sniff for "yenc" in the message,
and reject it in cases where it doesn't belong.

That's why the original message did not appear
on my news server.

Even the howard archive has a filter of sorts, where
they use truncation to "ruin" binary uploads of this type.
Rather than sniff for "yenc", howard just cuts the
end off every post which is slightly too big.

It would appear the originating server is misconfigured.
And since it's listed as a "reseller", that means someone
bought the right to access a binary server, and then that
customer didn't configure their stuff right on that
reseller connection.

Paul

In message , Apd writes
"VanguardLH" wrote:
This is not a binary newsgroup.

That must be why I cant see the original post.
Do individual.net carry binary groups?

No, they don't.

They're not managing their
server very well if they allow binary posts in text-only groups.


Perhaps not, but in mitigation they do an excellent job of filtering out
the much bigger problem of spam.
--
John Hall
"Hegel was right when he said that we learn from history
that man can never learn anything from history."
George Bernard Shaw (1856-1950)

"Paul" wrote:
It would appear the originating server is misconfigured.
And since it's listed as a "reseller", that means someone
bought the right to access a binary server, and then that
customer didn't configure their stuff right on that
reseller connection.

Whatever the condition of the originating server, it would appear that
Vanguard's server (individual.net) is misconfigured since it accepted
the post.