Re: Email issues unanswered - Mailing list pgsql-www
From | Bruce Momjian |
---|---|
Subject | Re: Email issues unanswered |
Date | |
Msg-id | 200701292336.l0TNata12560@momjian.us Whole thread Raw |
In response to | Re: Email issues unanswered ("Marc G. Fournier" <scrappy@postgresql.org>) |
Responses |
Re: Email issues unanswered
Re: Email issues unanswered |
List | pgsql-www |
Marc G. Fournier wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > > - --On Monday, January 29, 2007 18:11:38 -0500 Bruce Momjian <bruce@momjian.us> > wrote: > > > My long subject email going out looks like: > > > > From bruce Fri Jan 26 21:00:37 2007 > > Subject: Re: [GENERAL] Predicted lifespan of different PostgreSQL > > branches > > Looks like something has add a carriage return at the end of PostgreSQL, which > breaks the RFC ... if it was all one line (as per the RFC quote that Andrew Yes, my emaler does that, but see below on the RFC issue. > sent), it wouldn't have gone through (as per the valid long Subject that I just > sent to you) ... > > You are talking about 'multi line' (against RFCs) vs 'long subjects that wrap' > (not against RFCs) ... Right, I am talking about multi-line, and here is the RFC part Andrew mentioned: 2.2.3. Long Header Fields Each header field is logically a single line of characters comprising the field name, the colon, and the field body. For convenience however, and to deal with the 998/78 character limitations per line, the field body portion of a headerfield can be split into a multiple line representation; this is called "folding". The general rule is that wherever this standard allows for folding white space (not simply WSP characters), a CRLF may be inserted beforeany WSP. For example, the header field: Subject: This is a test can be represented as: Subject: This is a test Note: Though structured field bodies are defined in such a way that folding can take place between many of the lexicaltokens (and even within some of the lexical tokens), folding SHOULD be limited to placing the CRLF at higher-levelsyntactic breaks. For instance, if a field body is defined as comma-separated values, it is recommended thatfolding occur after the comma separating the structured items in preference to other places where the field could befolded, even if it is allowed elsewhere. The process of moving from this folded multiple-line representation of a header field to its single line representationis called "unfolding". Unfolding is accomplished by simply removing any CRLF that is immediately followedby WSP. Each header field should be treated in its unfolded form for further syntactic and semantic evaluation. It seems clear here that my emailer is fine and following the RFC. -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +