On Sat, 22 Mar 2008, Tim Connors wrote: > Package: slrn > Version: 0.9.9~pre97-1 > Severity: normal > > I don't know whether this is a new "feature", or one that has been > exposed by a recent change at google, but slrn now nags with: > > Your message is not acceptable for the following reason(s): > > One word of the header is too long to get folded. > > This message was generated while looking at the following line > > References: <[EMAIL PROTECTED]> > > Sure it's long, and a weak violation of the RFC's, but the alternative > is to break the reference header altogether. Since any half decent > software out there will be programmed competantly enough not to get a > buffer overflow when presented with a long header of this sorts, does > it really matter if we send out a header that is slightly too long? > > This has been discussed in news.software.readers, but I don't know > what the long term plan is - I was under the impression that this had > been recently fixed, but then it seems that there were actually > several header-breaking bugs and this one might have slipped under the > radar.
Since this is a rather useless feature, I have just wholesale disabled it in the following patch. Presumably every user who follows up to google groups postings would find such a patch useful (or fear getting used to having to press "f" to force posting otherwise, which will one day come back to bite them when they accidentally end up forcing something that was a real warning) See also the posts in this thread: http://newsgroups.derkeiler.com/Archive/Misc/news.software.readers/2008-02/msg00482.html --- src/mime.c.bak 2008-08-04 21:27:44.000000000 +1000 +++ src/mime.c 2008-08-04 21:24:52.000000000 +1000 @@ -1288,9 +1288,9 @@ slrn_free (*s_ptr); *s_ptr = folded_text; - if (long_words) - return slrn_add_mime_error(NULL, _("One word of the header is too long to get folded."), *s_ptr, 0, MIME_ERROR_WARN); - else +// if (long_words) +// return slrn_add_mime_error(NULL, _("One word of the header is too long to get folded."), *s_ptr, 0, MIME_ERROR_WARN); +// else return NULL; } (other warnings about non-rfc compliant messages can stay - this is the only one that has proven to be a useless check, so far). -- TimC New!: Sysadmin Barbie! Complete with tiny pager, Leatherman, selection of LARTs, and makeup kit for that haven't-slept-in-3-days look. --unknown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
