The message-id is not contained within <> in the log message but maybe that is 
correct, it just breaks logstash parsing but perhaps the parser is to blame. 

--
Tom Sommer

> On 14 Aug 2018, at 16.34, Dominic Raferd <[email protected]> wrote:
> 
> 
> 
>> On Tue, 14 Aug 2018 at 15:22, Tom Sommer <[email protected]> wrote:
>> I noticed a mail that broke logging syntax:
>> 
>> Aug 14 15:29:57 X postfix/cleanup[11962]: 41qYP05TZCz5xY9: 
>> message-id==?utf-8?Q?=3CE1F7DC2C-82B5-4927-B0DB-0179227E665C=40aalborgf?=? 
>> =?utf-8?Q?=C3=B8rstehj=C3=A6lp=2Edk=3E?=
>> 
>> I guess the message-id contains non-ascii chars that break logging, or 
>> something, is there any way to fix this or is it a bug?
>> 
>> mail_version = 3.3.1
> 
> Is the logging broken? It looks ok to me, just recording the UTF8-encoded 
> message-id.

Reply via email to