I really don’t want to have to paste the contents into an http gateway
posting… What does the 441 mean? I mean for what reasons would it be
rejected by the POST filter???
[Error posting message: 441 Posting Failed (Rejected by POST filter)]
On Sun, 12 Jul 2015 19:25:10 +0000, JtWdyP wrote:
> I really don’t want to have to paste the contents into an http gateway
> posting… What does the 441 mean? I mean for what reasons would it be
> rejected by the POST filter???
>
> [Error posting message: 441 Posting Failed (Rejected by
> POST filter)]
Which group were you trying to post to?
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
It would appear that on Jul 12, Jim Henderson did say:
> On Sun, 12 Jul 2015 19:25:10 +0000, JtWdyP wrote:
>
> > I really don’t want to have to paste the contents into an http gateway
> > posting… What does the 441 mean? I mean for what reasons would it be
> > rejected by the POST filter???
> >
> > [Error posting message: 441 Posting Failed (Rejected by
> > POST filter)]
>
> Which group were you trying to post to?
>
> Jim
=================== code ===================
=================== /code ===================
Perhaps I shouldn’t have abbreviated “Applications” as “Apps” when it would
have pattern matched a grep query better as “App*s”? (;-7#
I’m thinking of bothering to log in to the HTTP portal and see if it will
let me post the complete alpine (header view) message text inside code
tags in reply to this thread. Then perhaps the problem would be obvious to
some clever openSUSE Forums Administrator, named Jim?
–
JtWdyP
In alpine’s headder view this was “forwarded” from my postponed folder…
---------- Forwarded message ----------
Newsgroups: opensuse.org.help.applications
Date: Sun, 12 Jul 2015 16:44:10 -0400 (EDT)
From: JtWdyP <jtwdyp@no-mx.forums.microfocus.org>
Subject: opensuse 13.2: I can't watch live showtime content on hulu...
Fcc: sentit
Message-ID: <alpine.LSU.2.19.9991.1507121506590.3604@linux-dn7c.Belkin>
User-Agent: Alpine 2.19.9991 (LSU 64 2014-05-31)
X-NNTP-Server: nntp.opensuse.org
X-Cursor-Pos: : 0
X-Our-ReplyTo: Empty
X-Our-Headers: Followup-To,Reply-To,Return-Path,Return-Receipt-To,
Disposition-Notification-To,X-MSMail-Priority
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="1774642430-1425082332-1436727349=:1756"
Content-ID: <alpine.LSU.2.19.9991.1507121457170.1756@linux-dn7c.Belkin>
--1774642430-1425082332-1436727349=:1756
Content-Type: text/plain; CHARSET=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-ID: <alpine.LSU.2.19.9991.1507121457171.1756@linux-dn7c.Belkin>
First, let me say I don't have this problem using the same computer when
I'm running either my antix, or my mageia linux installations. Before I
discovered that, I started with hulu's support team. But since the problem
only happens when I'm running opensuse, I thought this was a more
appropriate venue.
I usually use Firefox for this. (currently Firefox 33.0) I do have the nosc=
ript
extension installed. But I permit both hulu.com & huluim.com.=20
*Also see the chromium info below. {I generaly only use Chromium for=20
facebook, and it has javascript wide open...}
I have no problems with other hulu content. Including {non-live} showtime
content. But if I'm running opensuse, when I select the "live" showtime
content, I get a short clip about the R rated content being intended for=20
Mature Viewers. Then this "one time loading experience" message appears:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D code =3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
http://tinypic.com/r/o0cqag/8
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D /code =3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Then, a few seconds later I get this hulu error code 2203:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D code =3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
http://tinypic.com/r/2133axw/8
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D /code =3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Hulu's support team made some initial suggestions: And this is what I told
them...
> Troubleshooting steps:
> =E2=80=A2 Lowering the video quality from hd to high didn't help.
> =E2=80=A2 Clearing my browser cache didn't help.
> =E2=80=A2 "Delete all sites" from my Flash cache via http://phtshp.us/2f=
Zi didn't help.
> =E2=80=A2 Turning off hardware acceleration in Flash via the right-click=
menu. didn't help.
> =E2=80=A2 Power-cycling my router, modem, and computer, didn't help.
> =E2=80=A2 Using other browsers didn't help:
> Both Opera and Chromium (with the latest pepper-flash plugin) could vi=
ew
> other hulu video streams, including one from the showtime listings. Bu=
t
> when I tried to use the showtime live option. Both failed.
>=20
> I had half expected the Chromium with latest pepperflash to work, if
> only because I despise that browser's user interface. And it did fail
> differently than the other browsers. Though, like the other browsers,
> the failure happened right after the "one time loading experience"
> message. But Chromium never gave me the error message. It just gives m=
e
> a blacked out player window...
>=20
> On the other hand, this problem seems to only affect my opensuse installa=
tion.
> Empirical testing revealed that using either my installed debian derivati=
ve
> "antiX" Or Mageia (a Mandriver fork) I can watch the live content.
>=20
> This is not convenient. I have a few current projects I'm working on in
> opensuse. Saving the changes, & rebooting just to watch the live showtime
> content, is a real pain...=20
>=20
> But since it's only when I'm running opensuse, that it fails, I think I
> should move the venue to the opensuse forum.=20
I probably wouldn't care about this, since I plan to cancel hulu's showtime
add on, when the free month is up. But for the rest of July, I can use it
to test any potential fixes to whatever in opensuse is causing this.
And frankly, having to reboot into another distro to watch this bugs me.
Does anybody have a clue what's happening?
--=20
JtWdyP
--1774642430-1425082332-1436727349=:1756--
And a better question is why wouldn’t the "POST filter, let me post that to the NNTP portal?
I’d like to fix the postponed folder message so that I can post a copy of that, without all the header mode encoding, to the Applications forum, where I think it belongs…
On Sun, 12 Jul 2015 21:25:07 +0000, JtWdyP wrote:
> It would appear that on Jul 12, Jim Henderson did say:
>
>> On Sun, 12 Jul 2015 19:25:10 +0000, JtWdyP wrote:
>>
>> > I really don’t want to have to paste the contents into an http
>> > gateway posting… What does the 441 mean? I mean for what reasons
>> > would it be rejected by the POST filter???
>> >
>> > [Error posting message: 441 Posting Failed (Rejected by
>> > POST filter)]
>>
>> Which group were you trying to post to?
>>
>> Jim
>
> =================== code ===================
>
> =================== /code ===================
>
> Perhaps I shouldn’t have abbreviated “Applications” as “Apps” when it
> would have pattern matched a grep query better as “App*s”? (;-7#
Fair point. 
We’re not all perfect, and clearly, I didn’t read the
subject line closely enough.
> I’m thinking of bothering to log in to the HTTP portal and see if it
> will let me post the complete alpine (header view) message text inside
> code tags in reply to this thread. Then perhaps the problem would be
> obvious to some clever openSUSE Forums Administrator, named Jim?
I’ll have to have our tech admin look at it, as I don’t have access to
the current post filter. My guess is that your newsreader is adding the
=20 style encoding and that’s causing the filter to reject the message,
but that’s just a guess based on the post you made with the full message
in it.
Jim
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On 2015-07-12 23:25, JtWdyP wrote:
> =================== code ===================
>
> =================== /code ===================
> I’m thinking of bothering to log in to the HTTP portal and see if it will
> let me post the complete alpine (header view) message text inside code
> tags in reply to this thread.
Are you sure you used code tags properly?
Because the above block is not really enclosed in code tags.
Maybe the gateway saw the headers lines inside the body text, and got
confused, thinking they were real headers, and out of place as that…
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
It would appear that on Jul 13, Carlos E. R. did say:
> On 2015-07-12 23:25, JtWdyP wrote:
>
> > =================== code ===================
> >
> > =================== /code ===================
>
>
> > I’m thinking of bothering to log in to the HTTP portal and see if it will
> > let me post the complete alpine (header view) message text inside code
> > tags in reply to this thread.
>
> Are you sure you used code tags properly?
>
> Because the above block is not really enclosed in code tags.
True enough. I can’t remember exactly. But it seems to me that when real
code tags are used on the http gateway, something like the above gets
substituted for the nntp version of the post. I remember that even when you
copy/paste the exact substituted code lines into a new nntp posting, the
http gateway doesn’t see them as code tags. So I simply inserted descriptive
code marker lines around the actual “quote” tag encoding that I was
composing from stale memory. And which, I’m pleased to say, performed as
expected in the http version of that nntp posting.
> Maybe the gateway saw the headers lines inside the body text, and got
> confused, thinking they were real headers, and out of place as that…
It was the other posting, the one to the applications forum, that had a
problem getting through…
But thank you Carlos, I’ve learned to value your opinion over the years.
–
JtWdyP
It would appear that on Jul 12, Jim Henderson did say:
> On Sun, 12 Jul 2015 21:25:07 +0000, JtWdyP wrote:
> > =================== code ===================
> >
> > =================== /code ===================
> >
> > Perhaps I shouldn’t have abbreviated “Applications” as “Apps” when it
> > would have pattern matched a grep query better as “App*s”? (;-7#
>
> Fair point. We’re not all perfect, and clearly, I didn’t read the
> subject line closely enough.
You mean I’m not the only one who falls short of perfection? Too bad my ex
will never read that. 
> I’ll have to have our tech admin look at it, as I don’t have access to
> the current post filter. My guess is that your newsreader is adding the
> =20 style encoding and that’s causing the filter to reject the message,
> but that’s just a guess based on the post you made with the full message
> in it.
Possibly, but I’m fairly sure the “=20 style encoding” was part of alpine’s
“header mode” view. Such encoding wouldn’t have been included in the
original message body that the post filter rejected. I posted the header
mode version because I thought it might provide somebody like the “tech
admin” with a clearer idea of what alpine was doing, in case the actual
headers had something to do with it.
Perhaps I should post the message body portion of the message body as it
would be forwarded when header mode is off…
–
JtWdyP
And this is the text body of that rejected message without the header mode encoding, the way it was when alpine tried to post it to the Apps forum, via the nntp gateway…
---------- Forwarded message ----------
First, let me say I don’t have this problem using the same computer when
I’m running either my antix, or my mageia linux installations. Before I
discovered that, I started with hulu’s support team. But since the problem
only happens when I’m running opensuse, I thought this was a more
appropriate venue.
I usually use Firefox for this. (currently Firefox 33.0) I do have the noscript
extension installed. But I permit both hulu.com & huluim.com.
*Also see the chromium info below. {I generaly only use Chromium for
facebook, and it has javascript wide open…}
I have no problems with other hulu content. Including {non-live} showtime
content. But if I’m running opensuse, when I select the “live” showtime
content, I get a short clip about the R rated content being intended for
Mature Viewers. Then this “one time loading experience” message appears:
================ code ================
http://tinypic.com/r/o0cqag/8
================ /code ================
Then, a few seconds later I get this hulu error code 2203:
================ code ================
http://tinypic.com/r/2133axw/8
================ /code ================
Hulu’s support team made some initial suggestions: And this is what I told
them…
> Troubleshooting steps:
> • Lowering the video quality from hd to high didn’t help.
> • Clearing my browser cache didn’t help.
> • “Delete all sites” from my Flash cache via http://phtshp.us/2fZi didn’t help.
> • Turning off hardware acceleration in Flash via the right-click menu. didn’t help.
> • Power-cycling my router, modem, and computer, didn’t help.
> • Using other browsers didn’t help:
> Both Opera and Chromium (with the latest pepper-flash plugin) could view
> other hulu video streams, including one from the showtime listings. But
> when I tried to use the showtime live option. Both failed.
>
> I had half expected the Chromium with latest pepperflash to work, if
> only because I despise that browser’s user interface. And it did fail
> differently than the other browsers. Though, like the other browsers,
> the failure happened right after the “one time loading experience”
> message. But Chromium never gave me the error message. It just gives me
> a blacked out player window…
>
> On the other hand, this problem seems to only affect my opensuse installation.
> Empirical testing revealed that using either my installed debian derivative
> “antiX” Or Mageia (a Mandriver fork) I can watch the live content.
>
> This is not convenient. I have a few current projects I’m working on in
> opensuse. Saving the changes, & rebooting just to watch the live showtime
> content, is a real pain…
>
> But since it’s only when I’m running opensuse, that it fails, I think I
> should move the venue to the opensuse forum.
I probably wouldn’t care about this, since I plan to cancel hulu’s showtime
add on, when the free month is up. But for the rest of July, I can use it
to test any potential fixes to whatever in opensuse is causing this.
And frankly, having to reboot into another distro to watch this bugs me.
Does anybody have a clue what’s happening?
–
JtWdyP
On 2015-07-14 01:06, jtwdyp wrote:
…
> Mature Viewers. Then this “one time loading experience” message
> appears:
>
> ================ code ================
> http://tinypic.com/r/o0cqag/8
> ================ /code ================
You know that is not a proper “code” block when sent via NNTP?
It should be (see on Alpine, not on web):
Whatever ...
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
On 2015-07-13 23:19, JtWdyP wrote:
(I just posted another post before seeing this one)
>> Maybe the gateway saw the headers lines inside the body text, and got
>> confused, thinking they were real headers, and out of place as that…
>
> It was the other posting, the one to the applications forum, that had a
> problem getting through…
Oh, I see.
I can’t imagine why that one was blocked,
> But thank you Carlos, I’ve learned to value your opinion over the years.
Well, thank you
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
On Tue, 14 Jul 2015 00:08:06 +0000, Carlos E. R. wrote:
> On 2015-07-14 01:06, jtwdyp wrote:
>
> …
>
>> Mature Viewers. Then this “one time loading experience” message
>> appears:
>>
>> ================ code ================ http://tinypic.com/r/o0cqag/8
>> ================ /code ================
>
>
> You know that is not a proper “code” block when sent via NNTP?
>
> It should be (see on Alpine, not on web):
>
>
> Whatever ...
>
That won’t cause the problem he’s seeing, though.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On Mon, 13 Jul 2015 21:49:09 +0000, JtWdyP wrote:
> It would appear that on Jul 12, Jim Henderson did say:
>
>> On Sun, 12 Jul 2015 21:25:07 +0000, JtWdyP wrote:
>> > =================== code ===================
>> >
>> > =================== /code ===================
>> >
>> > Perhaps I shouldn’t have abbreviated “Applications” as “Apps” when it
>> > would have pattern matched a grep query better as “App*s”? (;-7#
>>
>> Fair point. We’re not all perfect, and clearly, I didn’t read the
>> subject line closely enough.
>
> You mean I’m not the only one who falls short of perfection? Too bad my
> ex will never read that.
>> I’ll have to have our tech admin look at it, as I don’t have access to
>> the current post filter. My guess is that your newsreader is adding
>> the =20 style encoding and that’s causing the filter to reject the
>> message, but that’s just a guess based on the post you made with the
>> full message in it.
>
> Possibly, but I’m fairly sure the “=20 style encoding” was part of
> alpine’s “header mode” view. Such encoding wouldn’t have been included
> in the original message body that the post filter rejected. I posted the
> header mode version because I thought it might provide somebody like the
> “tech admin” with a clearer idea of what alpine was doing, in case the
> actual headers had something to do with it.
>
> Perhaps I should post the message body portion of the message body as it
> would be forwarded when header mode is off…
The weird thing (in looking at the relevant part of our post filter), is
that we don’t return that particular error in the script - so we’re going
to have to dig deeper to find the cause.
It might be interesting to try posting the message in this thread from
Alpine, and cut the message in halves to isolate where the problem is.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On Mon, 13 Jul 2015 01:14:06 +0000, Carlos E. R. wrote:
> Maybe the gateway saw the headers lines inside the body text, and got
> confused, thinking they were real headers, and out of place as that…
Nope. The gateway doesn’t do post filtering on the NNTP server -
entirely different code.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On 2015-07-14 07:06, Jim Henderson wrote:
>> It should be (see on Alpine, not on web):
>> >
>> >
>> > Whatever ...
>> >
> That won’t cause the problem he’s seeing, though.
No, you are right.
But still had in my mind the strangely formatted post he pasted earlier.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
On Tue, 14 Jul 2015 05:07:45 +0000, Jim Henderson wrote:
> The weird thing (in looking at the relevant part of our post filter), is
> that we don’t return that particular error in the script - so we’re
> going to have to dig deeper to find the cause.
Your client isn’t trying to do something like attach a digital signature
as a file attachment, is it?
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On 2015-07-14 18:21, Jim Henderson wrote:
> On Tue, 14 Jul 2015 05:07:45 +0000, Jim Henderson wrote:
>
>> The weird thing (in looking at the relevant part of our post filter), is
>> that we don’t return that particular error in the script - so we’re
>> going to have to dig deeper to find the cause.
>
> Your client isn’t trying to do something like attach a digital signature
> as a file attachment, is it?
Alpine would have problems doing that. As far as I know, it is only done
“inline”, not with mime - I think that’s the name, unsure. With
attachments. Unless there is another signing method which I haven’t noticed.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
It would appear that on Jul 14, Jim Henderson did say:
> The weird thing (in looking at the relevant part of our post filter), is
> that we don’t return that particular error in the script - so we’re going
> to have to dig deeper to find the cause.
OK maybe the error code was from alpine itself?
> It might be interesting to try posting the message in this thread from
> Alpine, and cut the message in halves to isolate where the problem is.
OK, lets try that. My process will be to resume the postponed message, open
the message body in the alternate editor (vim), and do a
:w! ~/tmpfile
======================
Then I’ll postpone it again, and resume this message. where I’ll do a:
:r ~/tmpfile
======================
The first attempt will try to include the entire message body. If that
fails, I’ll try splitting it up to see if we can isolate the problem.
This is attempt 2 (first 31 lines of message body)
===== everything below this line is from the original message =====
First, let me say I don’t have this problem using the same computer when
I’m running either my antix, or my mageia linux installations. Before I
discovered that, I started with hulu’s support team. But since the problem
only happens when I’m running opensuse, I thought this was a more
appropriate venue.
I usually use Firefox for this. (currently Firefox 33.0) I do have the noscript
extension installed. But I permit both hulu.com & huluim.com.
*Also see the chromium info below. {I generaly only use Chromium for
facebook, and it has javascript wide open…}
I have no problems with other hulu content. Including {non-live} showtime
content. But if I’m running opensuse, when I select the “live” showtime
content, I get a short clip about the R rated content being intended for
Mature Viewers. Then this “one time loading experience” message appears:
================ code ================
http://tinypic.com/r/o0cqag/8
================ /code ================
Then, a few seconds later I get this hulu error code 2203:
================ code ================
http://tinypic.com/r/2133axw/8
================ /code ================
Hulu’s support team made some initial suggestions: And this is what I told
them…
> Troubleshooting steps:
On Tue, 14 Jul 2015 17:38:10 +0000, JtWdyP wrote:
>> The weird thing (in looking at the relevant part of our post filter),
>> is that we don’t return that particular error in the script - so we’re
>> going to have to dig deeper to find the cause.
>
> OK maybe the error code was from alpine itself?
Not likely - it reads like a server error.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On Tue, 14 Jul 2015 17:34:06 +0000, Carlos E. R. wrote:
> On 2015-07-14 18:21, Jim Henderson wrote:
>> On Tue, 14 Jul 2015 05:07:45 +0000, Jim Henderson wrote:
>>
>>> The weird thing (in looking at the relevant part of our post filter),
>>> is that we don’t return that particular error in the script - so we’re
>>> going to have to dig deeper to find the cause.
>>
>> Your client isn’t trying to do something like attach a digital
>> signature as a file attachment, is it?
>
> Alpine would have problems doing that. As far as I know, it is only done
> “inline”, not with mime - I think that’s the name, unsure. With
> attachments. Unless there is another signing method which I haven’t
> noticed.
It would be a multipart message, but I think there are a couple standards
- and that is something we block at the server that’s not part of the
postfilter I looked at.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C