From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news2.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!t-online.de!news.karotte.org!news.musoftware.de!wum.musoftware.de!news.tornevall.net!news.jacob-sparre.dk!pnx.dk!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: Howto read line from a stream Date: Tue, 2 Jun 2009 16:15:16 -0500 Organization: Jacob Sparre Andersen Message-ID: References: <83317a97-dae5-4c84-a1ac-88a87833cf3f@q14g2000vbn.googlegroups.com> <1a90e055-44a3-4d00-b4cd-64798c731a55@e24g2000vbe.googlegroups.com> <16949835-6528-4a7a-a653-fd466b37bb45@s21g2000vbb.googlegroups.com> <18nn8atp3gdq1$.6g5cqv5h6u1c.dlg@40tude.net> <1dlvlys7r0tyh$.zyytlf2vt5zm.dlg@40tude.net> NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net X-Trace: munin.nbi.dk 1243977342 17676 69.95.181.76 (2 Jun 2009 21:15:42 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Tue, 2 Jun 2009 21:15:42 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5512 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Xref: g2news2.google.com comp.lang.ada:6180 Date: 2009-06-02T16:15:16-05:00 List-Id: "Dmitry A. Kazakov" wrote in message news:1dlvlys7r0tyh$.zyytlf2vt5zm.dlg@40tude.net... > On Mon, 1 Jun 2009 18:30:31 -0500, Randy Brukardt wrote: ... > I don't think it is a good idea, how to handle poorly designed and badly > implemented protocols. We are living in a real world. It is silly to imply > that an incoherent implementation should indicate a security problem. The > problem is elsewhere, in the protocol itself. Anyways, I doubt that > somebody could statistically confirm that the percentage of malformed line > terminators is higher among unwanted postings. Maybe in general, but in the case of spam, there is a very strong correlation, simply because the majority of all legitimate mail is sent by only a few mail clients (Outlook, Thunderbird, GMail, etc.) and these do in fact follow the protocol standards. So anything that doesn't follow it is much more likely to be junk. Indeed, spam filtering is 100% about apply statistical models, since there is really no way to predict what good mail will look like. It's possible that there is more of this problem with other mail these days; I would think that spammers would be more careful these days if for no reason than such malformed mail never gets delivered. But there still is an amazing amount of malformed mail. Note that I created and manage the spam filter (in Ada, of course) on our mail servers, and we average 100,000 spams per week (about 99% spam). So I see a lot of spam in a week, even now when 97% or so gets automatically blocked or deleted. > P.P.S. There are lots of text-oriented protocols used in automotive. The > device vendors just do not care to handle LFs and CRs as specified (if > specified! (:-)). You buy a $10**5+ device and have to communicate with > it. > Guess which side has to be fixed? I would argue that is mainly a problem with the specifications, rather than the device. But I feel your pain; hardly anything in the real world quite follows the specifications. Generally, you have handle screwed up line endings, but remember that fact so that you can then quarantine the mail (the reason being that you still need to scan the mail to see if it would be automatically deleted for other reasons). So it's pretty much the worst of both worlds. Browsers and HTML are even worse; if they refused to display a lot of improper junk, filtering would not be so hard. Randy.