headers
Frank Ellermann | 1 Nov 14:14
Picon
Picon

draft-duerst-archived-at-04 (was: New Internet Draft: draft-duerst-archived-at-03.txt)


There's now a new draft-duerst-archived-at-04.
The change log says:

| 9.1.  Changes from -03.txt to -04.txt
|       Updated from RFC 2234 to RFC 4234.
|       Updated author's address/affiliation.

That doesn't address the comments posted here (= on the
rfc822 list) almost six months ago in:

<URL:http://mid.gmane.org/42212FB4.5AE1 <at> xyzzy.claranet.de>

So there's still a problem with folding excessively long
URLs, and the ABNF is still incorrect.

Minor nits:  Apparently "something eats" many empty lines
separating paragraphs and headers.  The IANA header field
registration form still says archived-at-02.  The new URI
in the author's address is apparently an IRI... </joke>

"Implementation report" (for a DS later):  GMaNe now also
implements Archived-At, for an example compare

<http://article.gmane.org/gmane.org.w3c.uri/684/raw> with
the URL <http://permalink.gmane.org/gmane.org.w3c.uri/684>.

                          Bye, Frank

(posted in <ietf-822.imc.org>)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Arnt Gulbrandsen | 1 Nov 14:52
Picon
Favicon
Gravatar

content-type parameter "reply-type"


I don't know any reference for this parameter. Here's one I saw yesterday:

Content-Type: text/plain; format=flowed; charset=iso-8859-1; 
reply-type=original

Is this specified anywhere (in an RFC, draft or elsewhere)?

Arnt
Permalink | Reply | 1 comment |
headers
Dave Crocker | 10 Nov 09:19

Re: content-type parameter "reply-type"


> Content-Type: text/plain; format=flowed; charset=iso-8859-1; 
> reply-type=original

Interesting.

"original" suggests all sorts of other values that might be defined...

reply-type=repeat

or

reply-type=unkind

or

reply-type=unresponsive

or

...

d/

--

-- 

Dave Crocker
Brandenburg InternetWorking
<http://bbiw.net>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Frank Ellermann | 11 Nov 06:10
Picon
Picon

OT: IMA (IEE BoF) jabber log


FYI, the IEE BoF jabber log is available at:
http://www.xmpp.org/ietf-logs/iee <at> ietf.xmpp.org/2005-11-10.html

Mailing list now also available at GMaNe (NNTP, RSS, search):
http://dir.gmane.org/gmane.ietf.ima

The project URL (until IEE is a WG) is apparently:
http://www.alvestrand.no/ietf/iee-bof/

Interesting snippets from the jabber log (thanks to Lisa):

[15:57:15] <lisa> Harald: There's a not-widely implemented
                          standard for tagging language of
                          email headers (RFC2231)

{16:04:42] <cyrus_daboo>  MUAs are important. There are still
                          many MUAs in use today that do not
                          support utf8 even in the message
                          body. So I agree with Chris.

[16:24:39] <cyrus_daboo>  PS If its not already on the list of
                          things to 'fix': the mailto URI
                          scheme will need some work too.

[16:29:36] <lisa> Keith:  There are multiple ways to fail, and
                          fragmenting the email system is one.
                          People to have to manually manage
                          their technology based on who they're
                          talking to is another. They're both
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jacob Palme | 30 Nov 18:51
Picon
Picon

Allowing non-quoted "." and "," in display-name?


I just received an e-mail which had the following headers (excerpted):

     Received: from SELDMSX01.corpusers.net ([10.129.0.161]) by
         seldcon01.corpusers.net with Microsoft SMTPSVC(6.0.3790.1830);
         Tue, 29 Nov 2005 10:14:09 +0100
     X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
     ...
     From: =?iso-8859-1?Q?H=E4ggstr=F6m=2C_Daniel?=
         <Daniel.Haggstrom.x <at> sonyericsson.com>

After MIME decoding, the From: field of this e-mail looks like this:

     From: Häggström, Daniel <Daniel.Haggstrom.x <at> sonyericsson.com>

This causes my mail program (Macintosh Eudora) to go wild,
believing that "Höggström" and "Daniel" are two different
people and trying to send my reply to both of them.

The way I understand it from RFC 2822, it is the sending mail program
(Microsoft Exchange V6.5.7226.0) which is faulty, since the
From: field should have been:

     From: "Häggström, Daniel" <Daniel.Haggstrom.x <at> sonyericsson.com>

RFC 2822 allows "." without quotes as "obs-phrase" i.e. something
you should receive but not produce. Is "," also going to be
accepted without quotes in the future?
--

-- 
Professor Jacob Palme <jpalme <at> dsv.su.se> (Stockholm University and KTH)
(Continue reading)

Permalink | Reply | 1 comment |
headers
ned+ietf-822 | 30 Nov 19:12

Re: Allowing non-quoted "." and "," in display-name?


> I just received an e-mail which had the following headers (excerpted):

>      Received: from SELDMSX01.corpusers.net ([10.129.0.161]) by
>          seldcon01.corpusers.net with Microsoft SMTPSVC(6.0.3790.1830);
>          Tue, 29 Nov 2005 10:14:09 +0100
>      X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
>      ...
>      From: =?iso-8859-1?Q?H=E4ggstr=F6m=2C_Daniel?=
>          <Daniel.Haggstrom.x <at> sonyericsson.com>

> After MIME decoding, the From: field of this e-mail looks like this:

>      From: Häggström, Daniel <Daniel.Haggstrom.x <at> sonyericsson.com>

> This causes my mail program (Macintosh Eudora) to go wild,
> believing that "Höggström" and "Daniel" are two different
> people and trying to send my reply to both of them.

This is a bug in Eudora IMO and needs to be treated as such.

> The way I understand it from RFC 2822, it is the sending mail program
> (Microsoft Exchange V6.5.7226.0) which is faulty, since the
> From: field should have been:

>      From: "Häggström, Daniel" <Daniel.Haggstrom.x <at> sonyericsson.com>

Your understanding is incorrect. RFC 2822 doesn't deal with encoded words; they
are done as a layer on top of RFC 2822. The string RFC 2822 saw was
=?iso-8859-1?Q?H=E4ggstr=F6m=2C_Daniel?=, which is syntactically legal without
(Continue reading)

Permalink | Reply | 0 comments |

Gmane