> Responding to you via NNTP; I use it full time as well, though from
> Thunderbird, and posted just a couple of seconds ago, so I presume it’s
> working.
Yeah, if it was an interface problem it was real short lived…
But I suspect it might have been something that crept in to my habitual hand coding
of the message body with vim. I have a vague memory of having a similar problem that
boiled down to using vim’s insert mode’s ^K to select certain non-keyboard characters,
Such as wrapping some text string in opening and closing single quotes:
Which I did NOT do this time. But I may have pasted in some text that wasn’t
restricted to pure ASCII…
> If you find this post helpful and are logged into the web interface,
> show your appreciation and click on the star below…
Sorry, once again using NNTP so ‘no got star to click on…’
Thank you for your quick response. I was mentally burned out trying to debug my
laptop’s clean install of Leap, with (at the time) a backlight issue that made it
hard to see the text I was editing. Since then I got some wonderful help on the
Applications Forum that has resolved most of those issues. So real soon I expect to be
back working on my book…
> But I suspect it might have been something that crept in to my habitual
> hand coding of the message body with vim. I have a vague memory of
> having a similar problem that boiled down to using vim’s insert mode’s
> ^K to select certain non-keyboard characters,
Yep, that’s likely it. What you saw wasn’t a gateway error, it was an
NNTP server response. The gateway periodically scrapes the web side and
NNTP side (not precisely, but close enough for discussion) and keeps
things in sync.
The 441 you received was content-related. No idea what was tripping it,
but we have a post filter that looks for certain things that we know
might choke the gateway.
It would appear that on Jun 20, Jim Henderson did say:
> Yep, that’s likely it. What you saw wasn’t a gateway error, it was an
> NNTP server response. The gateway periodically scrapes the web side and
> NNTP side (not precisely, but close enough for discussion) and keeps
> things in sync.
>
> The 441 you received was content-related. No idea what was tripping it,
> but we have a post filter that looks for certain things that we know
> might choke the gateway.
And that is why, when I get such an error, an exact copy of the entire
message body of the rejected post can usually be pasted into the web interface’s
compose editor’s content field, and post successfully. What the gateway gets when
it 'scrapes the web side’must be able to accept many of non-ASCII characters,
that it might have choked on, coming from the ‘NNTP server’??
> And that is why, when I get such an error, an exact copy of the
> entire message body of the rejected post can usually be pasted into the
> web interface’s compose editor’s content field, and post successfully.
> What the gateway gets when it 'scrapes the web side’must be able
> to accept many of non-ASCII characters,
> that it might have choked on, coming from the ‘NNTP server’??
No idea, that’s just one reason why it would reject the post - there are
others, such as incorrect character encoding, I think if it’s multipart/
MIME it’ll reject it, and so on.