public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Marc G. Fournier <[email protected]>
Cc: Andrew Sullivan <[email protected]>
Cc: PostgreSQL www <[email protected]>
Subject: Re: Email issues unanswered
Date: Mon, 29 Jan 2007 18:36:55 -0500 (EST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Marc G. Fournier wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> - --On Monday, January 29, 2007 18:11:38 -0500 Bruce Momjian <[email protected]>
> 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 header field 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 before any 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 lexical tokens (and even
within some of the lexical tokens), folding SHOULD be limited to
placing the CRLF at higher-level syntactic breaks. For instance, if
a field body is defined as comma-separated values, it is recommended
that folding occur after the comma separating the structured items in
preference to other places where the field could be folded, even if
it is allowed elsewhere.
The process of moving from this folded multiple-line representation
of a header field to its single line representation is called
"unfolding". Unfolding is accomplished by simply removing any CRLF
that is immediately followed by 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 [email protected]
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
view thread (17+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Email issues unanswered
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox