Paul wrote: > ralph wrote: > > Hi Ken, > > > > > - You could use format=flowed email; paragraph lines that you want to > > > autoflow properly have to end in a SP CRLF sequence. That is defined > > > in RFC 2646. > > > > Obsoleted by RFC 3676. https://www.rfc-editor.org/info/rfc3676 > > > > From a quick glance, it insists ‘>’-quoting has no spaces. > > > > >>> This is quoted three deep. > > > > > > > This is only one deep. The unquoted text starts ‘> > This’. > > So you're saying they created a new standard that completely ignores > existing well-established practice, and makes the result less > readable, to boot? Well done. Oh! I see from the abstract that it > also relies on trailing whitespace! Clever.
I think that what Ken said about format=flowed from RFC 2646 (from 1999) was retained by RFC 3676 (in 2004). Though that's based on a very quick glance. I just added a quick test to show that repl followed by mhbuild do properly encode (RFC 2047) header field bodies. So storing message files with UTF-8 instead of 2047 encoding is fine from that standpoint, given that I use a UTF-8 locale. And grep-friendly. David
