delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2003/07/26/17:46:45

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Hannu E K Nevalainen \(garbage mail\)" <garbage_collector AT telia DOT com>
To: "ML CygWIN" <cygwin AT cygwin DOT com>
Subject: ezml problem? Subject line malformed at times.
Date: Sat, 26 Jul 2003 23:44:22 +0200
Message-ID: <NGBBLLIAMFLGJEOAJCCEOEDGDCAA.garbage_collector@telia.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal

------=_NextPart_000_0004_01C353CF.D71A8140
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit


As MS-Outtaluck (Outlook) seems to have one single usable grouping option
(i.e. the subject) a malformed subject becomes an irritating issue. I'm not
sure where it originates though, but I'm pretty sure it hasn't shown up
(on)in other mail(ing lists).

Actual Subject line of four recent messages: (also attached)

> Re: Error message from gcc: "entry point putc_unlocked could not 	be l
ocated ..."
> RE: Error message from gcc: "entry point putc_unlocked could not be l
ocated ..."
> RE: Error message from gcc: "entry point putc_unlocked could not be l
ocated ..."
> Error message from gcc: "entry point putc_unlocked could not be located
..."

$ echo 'RE: Error message from gcc: "entry point putc_unlocked could not be
l' | wc -c
     70

 With these in the mailbox, it is HARD to read thread-postings in the order
they were posted. i.e. one has only one option, check all three of the
subject groups for message::time_sent and thus determine in which order to
read messages.

NOTE: "Re:" is IMO of no relevance here;
       I do expect the initial posting to be individually "grouped".
       The problem increases with the amount of msg's in a thread.

 Anyone else seeing something similar?

/Hannu E K Nevalainen, B.Sc EE/Microcomputer systems, 59°14'N, 17°12'E.
--END OF MESSAGE--

------=_NextPart_000_0004_01C353CF.D71A8140
Content-Type: text/plain;
	name="Subjects.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="Subjects.txt"

Re: Error message from gcc: "entry point putc_unlocked could not 	be l =
ocated ..."
RE: Error message from gcc: "entry point putc_unlocked could not be l =
ocated ..."
RE: Error message from gcc: "entry point putc_unlocked could not be l =
ocated ..."
Error message from gcc: "entry point putc_unlocked could not be located =
..."



------=_NextPart_000_0004_01C353CF.D71A8140
Content-Type: text/plain; charset=us-ascii

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/
------=_NextPart_000_0004_01C353CF.D71A8140--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019