Subject: "From" in message list.

From: Alexander V Alekseev <[email-masked]>
Date: Tue, 5 Aug 2003 10:47:35 +0400 (MSD)

Hello!

	Some mail lists rewrite "From" address of messages
to list address, inserting non-address part of it into
brackets. Like this:

    From: "Alexander V Alekseev" <[email-masked]> 

becomes like this:
    From: <[email-masked]> (Alexander V Alekseev)
or even like this:
    From: <[email-masked]>(Дюкова Екатерина)

    In such case, pine shows only list address in "From"
header field. Is the a way to see part in () ?

		Bye. Alex.
-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Birl <[email-masked]>
Date: Tue, 5 Aug 2003 09:48:31 -0400 (EDT)

As it was written on Aug 5, thus Alexander V Alekseev spake unto Pine...:

Alex:  Date: Tue, 5 Aug 2003 10:47:35 +0400 (MSD)
Alex:  From: Alexander V Alekseev <[email-masked]>
Alex:  To: Pine Discussion Forum <[email-masked]>
Alex:  Subject: "From" in message list.
Alex:
Alex:  		Hello!
Alex:
Alex:  	Some mail lists rewrite "From" address of messages
Alex:  to list address, inserting non-address part of it into
Alex:  brackets. Like this:
Alex:
Alex:      From: "Alexander V Alekseev" <[email-masked]>
Alex:
Alex:  becomes like this:
Alex:      From: <[email-masked]> (Alexander V Alekseev)
Alex:  or even like this:
Alex:      From: <[email-masked]>(Дюкова Екатерина)
Alex:
Alex:      In such case, pine shows only list address in "From"
Alex:  header field. Is the a way to see part in () ?
Alex:
Alex:  		Bye. Alex.

Have you tried turning on full headers?

 Thanks

 Scott Birl
 Senior Systems Administrator            Computer Services   Temple University
 1805 North Broad Street  Philadelphia   Pennsylvania 19122  United States
====*====*====*====*====*====*====*====+====*====*====*====*====*====*====*====*

---

From: Alexander V Alekseev <[email-masked]>
Date: Tue, 5 Aug 2003 18:05:32 +0400 (MSD)

Hello!

> Have you tried turning on full headers?
	Yes. Of course it works (it would be strange, if it doesn't).
But:
     1) I can't see 'full headers' in message list.
     2) It's rather difficult to read undecoded mail (in full headers
        mode). ;-))

	Bye. Alex.

---

From: Alexander V Alekseev <[email-masked]>
Date: Tue, 5 Aug 2003 19:56:44 +0400 (MSD)

Hello!

	BTW: pine has a bug in decoding. Header like this:
--------------------------------------------------------
Subject: Re: [apache-talk] Re[2]: [apache-talk]
=?KOI8-R?Q?=ED=CF=D6=CE=CF?=
=?KOI8-R?Q?_=CC=C9_=D3=C4=C5=CC=C1=D4=D8_=D2=C5=C7=C9=D3=D4=D2=CF=CE?=
=?KOI8-R?Q?=C5=DA=D2=C5=C7=C9=D3=D4=D2=CF=CE=C5=DA=C1=D7=C9=D
--------------------------------------------------------
        is decoded only up to the 3rd line, leaving the last line "as
is". It looks like:
--------------------------------------------------------
Subject Re: [apache-talk] Re[2]: [apache-talk] <...skipped...> =?KOI8-R?Q?=C5=DA=D2=C5=C7=C9=D3=D4=D2=CF=CE=C5=DA=C1=D7=C9=D
--------------------------------------------------------

	Does anyone knows why?

	Bye. Alex.

---

From: Bernhard Kaindl <[email-masked]>
Date: Wed, 6 Aug 2003 09:06:51 +0200

Hello Alexander,

> 	BTW: pine has a bug in decoding. Header like this:

Does the last line really look like what I quote it above?

While the two lines above it look like containing valid encoded-words
as specified, in RFC 2047, it looks the last line is not a 'encoded-word'
like I read http://www.ietf.org/rfc/rfc2047.txt.

Naturally speaking it says:

| Generally, an "encoded-word" is a sequence of printable ASCII characters
| that begins with "=?", ends with "?=", and has two "?"s in between.

The exact syntax is:

| encoded-word = "=?" charset "?" encoding "?" encoded-text "?="

More rules apply, but this is the basic requirement for an 'encoded-word'
and it must not contain line breaks, so even if the "?=" would come later,
it would be too late.

To a human, the last line looks like containing such 'encoded-word', but
while the word suspectible to be a 'encoded-word', it does not end with "?=",
and so it does not conform to the syntax covered by RFC 2047, as I read it,
so it has to be displayed as-is, which pine does.

Maybe it conforms to an other RFC which tells how to handl such strings,
but I don't know it, but I'm also not an expert in these issues.

>         is decoded only up to the 3rd line, leaving the last line "as

This looks correct according to RFC 2047 to me, the last line does
not contain anything which is covered by it, and I think at least
pine does not implement other RFCs for MIME Message Header Header
Extensions which encode non US-ASCII strings.

My assumption is that the message may have been corrupted on the
way to pine, maybe by the sending email program. Maybe it has
a limited number of bytes it can use internally to handle long
encoded subject strings and maybe this limit has been reached
or even overflown(which would be bad for the user of this program)

Maybe you want to ask the sender if his program crashed some time
after sending this mail(which would also have security implications)

Bernhard
--
"The exclusive right to invention [is] given not of natural right,
but for the benefit of society." -- Thomas Jefferson
--
The European Parliament has postponed the vote on the software patent directive,
enforcing 30.000 patents on abstract rules as used in software back to the
original date of 1st of September, thereby rejecting initially successful
efforts to rush to vote on June 30th. There is time again, but not much:
--
The democratic process to prevent this, will have ended in 25 days!
http://www.softwarepatents.co.uk/now/

---

From: Alexander V Alekseev <[email-masked]>
Date: Wed, 6 Aug 2003 11:18:22 +0400 (MSD)

Hello!

	It seems, you're right.

> Does the last line really look like what I quote it above?
	Yes.

> | encoded-word = "=?" charset "?" encoding "?" encoded-text "?="

[...skipped...]

> way to pine, maybe by the sending email program. Maybe it has
	It seems, it's bug on sender side. Searching in mail archive,
I found exactly last line as a substring of another encoded line.
So, it's really corrupted.

	Thank you for valuable help.

	Bye. Alex.