sieve/vacation: bad parsing of 'References' header
Hello there, I see a strange behavior in the sieve plugin. If I send an email containing the 'References' field with multiple values like this:
References: <56CF3A8E.3060603@email.com> <74cc03f4-899f-e76f-81ea-d0e8a0efce9e@email.com> <CY1PR1001MB11630EC0D1DD48FBB12DDAC1DE090@CY1PR1001MB1163.namprd10.prod.outlook.com> <db3ee17f-33eb-b15c-8599-60b6dfa623e0@email.com> <YTXPR01MB01112EB28C7BECB5A5EF14C5DEE10@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <734f9013-c4a2-eab4-9c0d-2cfc3deafaee@email.com> <YTXPR01MB0111660D7D5A73451F3E5B66DEE00@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <9e3e3c00-a0d8-c061-7c7e-20e660533264@email.com> <e702bae4-b1d1-6671-fa74-87349282ce46@email.com> <YTXPR01MB01119930E4D876F91008D465DE3A0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <69c6be47-b17f-9f9a-5a0c-f389c6877f82@email.com> <YTXPR01MB01116BC86CBA49677A29C607DE3A0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <YTXPR01MB0111564E38C21BB293DCAE97DECA0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <YTXPR01MB01117A258CD09E1E84A1CBC1DECA0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
The vacation sieve script will add extra line breaks into the reply email as follows:
References: <56CF3A8E.3060603@email.com> <74cc03f4-899f-e76f-81ea-d0e8a0efce9e@email.com>
<CY1PR1001MB11630EC0D1DD48FBB12DDAC1DE090@CY1PR1001MB1163.namprd10.prod.outlook.com> <db3ee17f-33eb-b15c-8599-60b6dfa623e0@email.com>
<YTXPR01MB01112EB28C7BECB5A5EF14C5DEE10@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <734f9013-c4a2-eab4-9c0d-2cfc3deafaee@email.com>
<YTXPR01MB0111660D7D5A73451F3E5B66DEE00@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <9e3e3c00-a0d8-c061-7c7e-20e660533264@email.com> <e702bae4-b1d1-6671-fa74-87349282ce46@email.com>
<YTXPR01MB01119930E4D876F91008D465DE3A0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <69c6be47-b17f-9f9a-5a0c-f389c6877f82@email.com>
<YTXPR01MB01116BC86CBA49677A29C607DE3A0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
<YTXPR01MB0111564E38C21BB293DCAE97DECA0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
<YTXPR01MB01117A258CD09E1E84A1CBC1DECA0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <d0e5c311-bc89-c085-d597-f3a5744edd59@email.com>
The problem is this is rendered as follows in the email client (this is what a user will see when he/she receives the auto reply):
<CY1PR1001MB11630EC0D1DD48FBB12DDAC1DE090@CY1PR1001MB1163.namprd10.prod.outlook.com> <db3ee17f-33eb-b15c-8599-60b6dfa623e0@email.com>
<YTXPR01MB01112EB28C7BECB5A5EF14C5DEE10@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <734f9013-c4a2-eab4-9c0d-2cfc3deafaee@email.com>
<YTXPR01MB0111660D7D5A73451F3E5B66DEE00@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <9e3e3c00-a0d8-c061-7c7e-20e660533264@email.com> <e702bae4-b1d1-6671-fa74-87349282ce46@email.com>
<YTXPR01MB01119930E4D876F91008D465DE3A0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <69c6be47-b17f-9f9a-5a0c-f389c6877f82@email.com>
<YTXPR01MB01116BC86CBA49677A29C607DE3A0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
<YTXPR01MB0111564E38C21BB293DCAE97DECA0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
<YTXPR01MB01117A258CD09E1E84A1CBC1DECA0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <d0e5c311-bc89-c085-d597-f3a5744edd59@email.com> Auto-Submitted: auto-replied (vacation) Precedence: bulk MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit
I am on holydays right now. I will revert to you ASAP.....
I can reproduce this bug on the version 2.2.9 of managersieve/dovecot. Does anyone know how to fix this? Thank you.
Krzysztof Witek
Op 29-6-2017 om 10:33 schreef Krzysztof Witek:
Hello there, I see a strange behavior in the sieve plugin. If I send an email containing the 'References' field with multiple values like this:
What version of Pigeonhole is this? This looks like a problem that was solved ages ago.
Regards,
Stephan.
References: <56CF3A8E.3060603@email.com> <74cc03f4-899f-e76f-81ea-d0e8a0efce9e@email.com> <CY1PR1001MB11630EC0D1DD48FBB12DDAC1DE090@CY1PR1001MB1163.namprd10.prod.outlook.com> <db3ee17f-33eb-b15c-8599-60b6dfa623e0@email.com> <YTXPR01MB01112EB28C7BECB5A5EF14C5DEE10@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <734f9013-c4a2-eab4-9c0d-2cfc3deafaee@email.com> <YTXPR01MB0111660D7D5A73451F3E5B66DEE00@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <9e3e3c00-a0d8-c061-7c7e-20e660533264@email.com> <e702bae4-b1d1-6671-fa74-87349282ce46@email.com> <YTXPR01MB01119930E4D876F91008D465DE3A0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <69c6be47-b17f-9f9a-5a0c-f389c6877f82@email.com> <YTXPR01MB01116BC86CBA49677A29C607DE3A0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <YTXPR01MB0111564E38C21BB293DCAE97DECA0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <YTXPR01MB01117A258CD09E1E84A1CBC1DECA0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
The vacation sieve script will add extra line breaks into the reply email as follows:
References: <56CF3A8E.3060603@email.com> <74cc03f4-899f-e76f-81ea-d0e8a0efce9e@email.com>
<CY1PR1001MB11630EC0D1DD48FBB12DDAC1DE090@CY1PR1001MB1163.namprd10.prod.outlook.com> <db3ee17f-33eb-b15c-8599-60b6dfa623e0@email.com>
<YTXPR01MB01112EB28C7BECB5A5EF14C5DEE10@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <734f9013-c4a2-eab4-9c0d-2cfc3deafaee@email.com>
<YTXPR01MB0111660D7D5A73451F3E5B66DEE00@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <9e3e3c00-a0d8-c061-7c7e-20e660533264@email.com> <e702bae4-b1d1-6671-fa74-87349282ce46@email.com>
<YTXPR01MB01119930E4D876F91008D465DE3A0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <69c6be47-b17f-9f9a-5a0c-f389c6877f82@email.com>
<YTXPR01MB01116BC86CBA49677A29C607DE3A0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
<YTXPR01MB0111564E38C21BB293DCAE97DECA0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
<YTXPR01MB01117A258CD09E1E84A1CBC1DECA0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <d0e5c311-bc89-c085-d597-f3a5744edd59@email.com>
The problem is this is rendered as follows in the email client (this is what a user will see when he/she receives the auto reply):
<CY1PR1001MB11630EC0D1DD48FBB12DDAC1DE090@CY1PR1001MB1163.namprd10.prod.outlook.com> <db3ee17f-33eb-b15c-8599-60b6dfa623e0@email.com>
<YTXPR01MB01112EB28C7BECB5A5EF14C5DEE10@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <734f9013-c4a2-eab4-9c0d-2cfc3deafaee@email.com>
<YTXPR01MB0111660D7D5A73451F3E5B66DEE00@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <9e3e3c00-a0d8-c061-7c7e-20e660533264@email.com> <e702bae4-b1d1-6671-fa74-87349282ce46@email.com>
<YTXPR01MB01119930E4D876F91008D465DE3A0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <69c6be47-b17f-9f9a-5a0c-f389c6877f82@email.com>
<YTXPR01MB01116BC86CBA49677A29C607DE3A0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
<YTXPR01MB0111564E38C21BB293DCAE97DECA0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
<YTXPR01MB01117A258CD09E1E84A1CBC1DECA0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <d0e5c311-bc89-c085-d597-f3a5744edd59@email.com> Auto-Submitted: auto-replied (vacation) Precedence: bulk MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit
I am on holydays right now. I will revert to you ASAP.....
I can reproduce this bug on the version 2.2.9 of managersieve/dovecot. Does anyone know how to fix this? Thank you.
Krzysztof Witek
Hi Stephan Thank you for your reply.
I'm using dovecot 2.2.9 packaged with ubuntu packages: dovecot-managesieved 1:2.2.9-1ubuntu2.1 amd64 secure POP3/IMAP server - ManageSieve server dovecot-sieve 1:2.2.9-1ubuntu2.1 amd64 secure POP3/IMAP server - Sieve filters support
If I'm not mistaken Pigeonhole is part of those packages. Regards
-- Krzysztof Witek
On Thursday, June 29, 2017 10:37 CEST, Stephan Bosch <stephan@rename-it.nl> wrote: Op 29-6-2017 om 10:33 schreef Krzysztof Witek:
Hello there, I see a strange behavior in the sieve plugin. If I send an email containing the 'References' field with multiple values like this:
What version of Pigeonhole is this? This looks like a problem that was solved ages ago.
Regards,
Stephan.
References: <56CF3A8E.3060603@email.com> <74cc03f4-899f-e76f-81ea-d0e8a0efce9e@email.com> <CY1PR1001MB11630EC0D1DD48FBB12DDAC1DE090@CY1PR1001MB1163.namprd10.prod.outlook.com> <db3ee17f-33eb-b15c-8599-60b6dfa623e0@email.com> <YTXPR01MB01112EB28C7BECB5A5EF14C5DEE10@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <734f9013-c4a2-eab4-9c0d-2cfc3deafaee@email.com> <YTXPR01MB0111660D7D5A73451F3E5B66DEE00@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <9e3e3c00-a0d8-c061-7c7e-20e660533264@email.com> <e702bae4-b1d1-6671-fa74-87349282ce46@email.com> <YTXPR01MB01119930E4D876F91008D465DE3A0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <69c6be47-b17f-9f9a-5a0c-f389c6877f82@email.com> <YTXPR01MB01116BC86CBA49677A29C607DE3A0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <YTXPR01MB0111564E38C21BB293DCAE97DECA0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <YTXPR01MB01117A258CD09E1E84A1CBC1DECA0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
The vacation sieve script will add extra line breaks into the reply email as follows:
References: <56CF3A8E.3060603@email.com> <74cc03f4-899f-e76f-81ea-d0e8a0efce9e@email.com>
<CY1PR1001MB11630EC0D1DD48FBB12DDAC1DE090@CY1PR1001MB1163.namprd10.prod.outlook.com> <db3ee17f-33eb-b15c-8599-60b6dfa623e0@email.com>
<YTXPR01MB01112EB28C7BECB5A5EF14C5DEE10@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <734f9013-c4a2-eab4-9c0d-2cfc3deafaee@email.com>
<YTXPR01MB0111660D7D5A73451F3E5B66DEE00@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <9e3e3c00-a0d8-c061-7c7e-20e660533264@email.com> <e702bae4-b1d1-6671-fa74-87349282ce46@email.com>
<YTXPR01MB01119930E4D876F91008D465DE3A0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <69c6be47-b17f-9f9a-5a0c-f389c6877f82@email.com>
<YTXPR01MB01116BC86CBA49677A29C607DE3A0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
<YTXPR01MB0111564E38C21BB293DCAE97DECA0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
<YTXPR01MB01117A258CD09E1E84A1CBC1DECA0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <d0e5c311-bc89-c085-d597-f3a5744edd59@email.com>
The problem is this is rendered as follows in the email client (this is what a user will see when he/she receives the auto reply):
<CY1PR1001MB11630EC0D1DD48FBB12DDAC1DE090@CY1PR1001MB1163.namprd10.prod.outlook.com> <db3ee17f-33eb-b15c-8599-60b6dfa623e0@email.com>
<YTXPR01MB01112EB28C7BECB5A5EF14C5DEE10@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <734f9013-c4a2-eab4-9c0d-2cfc3deafaee@email.com>
<YTXPR01MB0111660D7D5A73451F3E5B66DEE00@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <9e3e3c00-a0d8-c061-7c7e-20e660533264@email.com> <e702bae4-b1d1-6671-fa74-87349282ce46@email.com>
<YTXPR01MB01119930E4D876F91008D465DE3A0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <69c6be47-b17f-9f9a-5a0c-f389c6877f82@email.com>
<YTXPR01MB01116BC86CBA49677A29C607DE3A0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
<YTXPR01MB0111564E38C21BB293DCAE97DECA0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
<YTXPR01MB01117A258CD09E1E84A1CBC1DECA0@YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM> <d0e5c311-bc89-c085-d597-f3a5744edd59@email.com> Auto-Submitted: auto-replied (vacation) Precedence: bulk MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit
I am on holydays right now. I will revert to you ASAP.....
I can reproduce this bug on the version 2.2.9 of managersieve/dovecot. Does anyone know how to fix this? Thank you.
Krzysztof Witek
On 2017-06-29 11:28, Krzysztof Witek wrote:
Hi Stephan Thank you for your reply.
I'm using dovecot 2.2.9 packaged with ubuntu packages: dovecot-managesieved 1:2.2.9-1ubuntu2.1 amd64 secure POP3/IMAP server - ManageSieve server dovecot-sieve 1:2.2.9-1ubuntu2.1 amd64 secure POP3/IMAP server - Sieve filters support
If I'm not mistaken Pigeonhole is part of those packages. Regards
doveconf -n reports the version number of dovecot and pigeonhole
-- Christian Kivalo
Op 29-6-2017 om 12:02 schreef Christian Kivalo:
On 2017-06-29 11:28, Krzysztof Witek wrote:
Hi Stephan Thank you for your reply.
I'm using dovecot 2.2.9 packaged with ubuntu packages: dovecot-managesieved 1:2.2.9-1ubuntu2.1 amd64 secure POP3/IMAP server - ManageSieve server dovecot-sieve 1:2.2.9-1ubuntu2.1 amd64 secure POP3/IMAP server - Sieve filters support
If I'm not mistaken Pigeonhole is part of those packages. Regards
doveconf -n reports the version number of dovecot and pigeonhole
That is a pretty recent feature. Anyway, the fact that it is Dovecot 2.2.9 tells me that it is ancient.
Regards,
Stephan.
Hi Christian, doveconf -n only dump dovecot version and its configuration: # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.14.21-grsec x86_64 Ubuntu 14.04.5 LTS auth_cache_negative_ttl = 0 auth_master_user_separator = * auth_mechanisms = plain apop login managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave
...
I downloaded the ubutu packages and it saw that the pigeonhole version used in those packages is 0.4.2
Regards.
Krzysztof Witek
On Thursday, June 29, 2017 12:02 CEST, Christian Kivalo <ml+dovecot@valo.at> wrote: On 2017-06-29 11:28, Krzysztof Witek wrote:
Hi Stephan Thank you for your reply.
I'm using dovecot 2.2.9 packaged with ubuntu packages: dovecot-managesieved 1:2.2.9-1ubuntu2.1 amd64 secure POP3/IMAP server - ManageSieve server dovecot-sieve 1:2.2.9-1ubuntu2.1 amd64 secure POP3/IMAP server - Sieve filters support
If I'm not mistaken Pigeonhole is part of those packages. Regards
doveconf -n reports the version number of dovecot and pigeonhole
-- Christian Kivalo
On 2017-06-29 13:44, Krzysztof Witek wrote:
Hi Christian, doveconf -n only dump dovecot version and its configuration: # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.14.21-grsec x86_64 Ubuntu 14.04.5 LTS auth_cache_negative_ttl = 0 auth_master_user_separator = * auth_mechanisms = plain apop login managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave
...
I downloaded the ubutu packages and it saw that the pigeonhole version used in those packages is 0.4.2
Stephan Bosch already mentioned in this thread that it's is a more recent feature of doveconf to also report the version of pigeonhole. I didn't know that this hadn't existed in dovecot v2.2.9.
-- Christian Kivalo
On Thursday, June 29, 2017 16:38 CEST, Christian Kivalo <ml+dovecot@valo.at> wrote:Stephan Bosch already mentioned in this thread that it's is a more recent feature of doveconf to also report the version of pigeonhole. I didn't know that this hadn't existed in dovecot v2.2.9.Yes sorry I saw his reply after I sent my email. Any thoughts about this issue in the version 0.4.2? I read the dovecot changlog and having seen anything about it.
Thank you BR Krzysztof
Op 6/29/2017 om 5:56 PM schreef Krzysztof Witek:
On Thursday, June 29, 2017 16:38 CEST, Christian Kivalo <ml+dovecot@valo.at> wrote:Stephan Bosch already mentioned in this thread that it's is a more recent feature of doveconf to also report the version of pigeonhole. I didn't know that this hadn't existed in dovecot v2.2.9.Yes sorry I saw his reply after I sent my email. Any thoughts about this issue in the version 0.4.2? I read the dovecot changlog and having seen anything about it.
It is not in the Dovecot changelog. This is Pigeonhole. This change fixed it :
https://github.com/dovecot/pigeonhole/commit/8d1b081028d340b8de64bc615e67e09...
Regards,
Stephan.
On 29/06/2017 20:02, Stephan Bosch wrote:
Op 6/29/2017 om 5:56 PM schreef Krzysztof Witek:
On Thursday, June 29, 2017 16:38 CEST, Christian Kivalo <ml+dovecot@valo.at> wrote:Stephan Bosch already mentioned in this thread that it's is a more recent feature of doveconf to also report the version of pigeonhole. I didn't know that this hadn't existed in dovecot v2.2.9.Yes sorry I saw his reply after I sent my email. Any thoughts about this issue in the version 0.4.2? I read the dovecot changlog and having seen anything about it. It is not in the Dovecot changelog. This is Pigeonhole. This change fixed it :
https://github.com/dovecot/pigeonhole/commit/8d1b081028d340b8de64bc615e67e09...
Greate, thank you Stephan I'll update my pigeonhole package. Regards Krzysztof
participants (3)
-
Christian Kivalo
-
Krzysztof Witek
-
Stephan Bosch