 | | NNTP interface broken?
|
|
Did something change in the NNTP interface lately? I am seeing the same behavior as described in this article: (URL) had assumed that my Outlook Express installation had gotten confused (although it has never happened previously) and marked it up as (...) (21 years ago, 27-May-03, to lugnet.admin.nntp)
|
| |
| | Re: Problems with Outlook Express and LUGNet
|
|
Hey! I am having the same trouble! Don't know the cause nor cure :-( I have it with the same groups you have and lugnet.cad.ray and I had it with lugnet.loc.nl Jaco "Carsten Schmitz" <casz@gmx.de> schreef in bericht news:HFJq8L.1oC8@lugnet.com... (...) (21 years ago, 27-May-03, to lugnet.admin.nntp, lugnet.cad)
|
| |
| | Problems with Outlook Express and LUGNet
|
|
Hi! Recently i have some very strange problems with Outlook Express and the LUGNet News server. Newsgroups where these problems occur are: lugnet.cad lugnet.cad.dev lugnet.cad.dev.org.ldraw lugnet.cad.mlcad This error is reproducable. I am (...) (21 years ago, 27-May-03, to lugnet.admin.nntp, lugnet.cad)
|
| |
| | Re: Posting with MIME encoded FROM header
|
|
(...) (Just came across this old thread and realized this hadn't yet been fixed.) OK, I've just installed a filter which does this conversion based on the RFC 2047 specification. This eliminiates nasties like =?ISO-8859-1?Q?f=F2=...=20b=E2r?= in (...) (21 years ago, 27-May-03, to lugnet.admin.general, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) Correct -- it never breaks a URL, even if it's 300 characters long or more. It may still break the *line* the URL appears on (and this is why I didn't list this in the conditions above) but it will never break the URL itself. The line-breaking (...) (21 years ago, 21-May-03, to lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) O-Ya, I agree in theory. But it becomes my problem, too, when someone running a dumb client quotes the un-decoded content in a reply, and people suffer from broken links and weird looking text. And if someone posts a qp reply to that, then the (...) (21 years ago, 21-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) Oops, sorry about that. 2,187. Forgot to fill that in when the script completed. --Todd (21 years ago, 21-May-03, to lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) For what value of xx,xxx? (21 years ago, 21-May-03, to lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) [...] The additional step of wrapping (...) I was only speaking of the web interface. That's why I didn't cc admin.nntp on my original posting... Any newsreader that can't handle quoted-printable is obsolete and it's the user's problem. (...) (21 years ago, 21-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) Does this also prevent breaking of URLs? Frank (21 years ago, 21-May-03, to lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
I have installed a filter so that incoming articles with the header: Content-Transfer-Encoding: quoted-printable are converted to 8bit encoding. The header is replaced with: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable (...) (21 years ago, 21-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) oooh...thanks...that looks like a very, very nice module. And by Damian Conway no less. --Todd (21 years ago, 21-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) check out Text::Autoformat - it does the right thing. Dan (21 years ago, 21-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) Unfortunately, Text::Wrap doesn't handle mail- and news-style quotations, and would happily convert: > >> >really especially long line of quoted text to (bad): > >> >really especially long line of quoted text instead of to (good): > >> >really (...) (21 years ago, 20-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) Yes, I've seen that too. You could always use Text::Wrap to reformat anything over 80 characters... (...) The biggest problem is the =3D in Brickshelf URL's. Even a special case to change =3D to = would be a huge help. (...) I assumed you (...) (21 years ago, 20-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) On the well-behaved e-mail clients, yes. On the worse clients, they jam a whole paragraph into a single line. I saw one which resulted in a line 890 characters long.(!) (...) I agree -- a hideously long line is better than one that's full of (...) (21 years ago, 20-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) Yes, that's what I meant. (...) It's usually at a line break, though, isn't it? And even so it is better than what is currently displayed; further refinements could be made to make it better yet... Or just let the browser do the word wrapping (...) (21 years ago, 19-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) Adding a second newline? You mean $body =~ s/=\n/\n/g or $body =~ s/=$//m ? Any of those would break words in half. (The = at the end isn't guaranteed to occur at a line break.) --Todd (21 years ago, 18-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) I think s/=$/\n/ would be adequate for that case. You could always improve it later. --Bill. (21 years ago, 18-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) Heh heh, funny you should mention that... Last night I was just thinking about this again and am 98% ready to deploy a fix. I've really noticed the increase in these posts lately too (especially coming in through the News-by-Mail gateways). A (...) (21 years ago, 16-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
