Re: Long lines with postmap

Victor.Duchovni@MorganStanley.com:
[ Charset ISO-8859-1 unsupported, converting... ]
> On Sun, 9 May 2004, Magnus B?ck wrote:
>
> > On Friday, May 07, 2004 at 17:51 CEST,
> > Victor.Duchovni@MorganStanley.com wrote:
> >
> > [...]
> >
> > > Someone should contribute a "-l" switch for "postmap" that supports
> > > header checks by turning on reading of "long lines" in the input
> > > stream. A very simple change for anyone who wants to get their feet
> > > wet contributing new Postfix code (a full patch should include
> > > documentation updates and must follow the existing coding style).
....
>
> Empty lines can reasonably be ignored, but whitespace only lines cannot:
>
> To: user1@domain.tld,<CRLF>
> <TAB><CRLF>
> <TAB>user2@domain.tld<CRLF>
>
> is a valid folded header with *two* header recipients. (<CRLF> will of
> course be just <LF> when headers are stored on UNIX systems rather than
> transmitted between systems).

I suggest giving the user interface some thought. "-l" for "long"
neither rings a bell that RFC822 is involved, nor does it ring a
bell that it controls table lookups.

In addition, it would be nice if the code gave consistent
treatment to:

+-------------
|% postmap -q - maptype:mapname <<EOF
|some
| multi-line
| text
|EOF
+-------------

and

+-------------
|% postmap -q 'some
| multi-line
| text' maptype:mapname
+-------------

That's more a matter of not intentionally breaking things.

Wietse