> The "id" line should start with tab or space. That's how Postfix creates the
> line.
And my pipe script killed the blank.
Now the Python parser works fine.
Thanks very much for your help,
Jürgen
[('Return-Path', '<[email protected]>'), ('X-Original-To',
'[email protected]'), ('Delivered-To', '[email protected]'),
('Received', 'by host.my.tld (Postfix, from userid 1001)\n id
D3DFD783; Sun, 21 Nov 2021 19:11:19 +0100 (CET)'), ('To',
'[email protected]'), ('Subject', 's1'), ('Message-Id',
'<[email protected]>'), ('Date', 'Sun, 21 Nov 2021
19:11:19 +0100 (CET)'), ('From', 'Jürgen Weber
<[email protected]>')]
Am Mi., 24. Nov. 2021 um 00:17 Uhr schrieb Wietse Venema <[email protected]>:
>
> J?rgen Weber:
> > From [email protected] Sun Nov 21 19:11:19 2021
> > Return-Path: <[email protected]>
> > X-Original-To: [email protected]
> > Delivered-To: [email protected]
> > Received: by host.my.tld (Postfix, from userid 1001)
> > id D3DFD783; Sun, 21 Nov 2021 19:11:19 +0100 (CET)
>
> The "id" line should start with tab or space. That's how
> Postfix creates the line.
>
> > To: [email protected]
> > Subject: s1
> > Message-Id: <[email protected]>
> > Date: Sun, 21 Nov 2021 19:11:19 +0100 (CET)
> > From: J?rgen Weber <[email protected]>
>
> Non-ASCII header text should be encoded with RFC 2o47.
>
> > Can you prevent Postfix from adding these lines?
>
> Use egrep.
>
> If Python's email.Parser can't handle non-ASCII headers, then you
> should not use it for real email management.
>
> Wietse
