Sieve redirect is broken in 2.3.7.2 - signal 11

[Stephan Bosch]

Op 4-10-2019 om 12:10 schreef Demonhost via dovecot:
> Hi,
>
> If we use sieve redirect under dovecot 2.3.7.2 we end up with
>
> Oct 04 03:30:31 dockerhost docker[12154]: 2019-10-04T03:30:31 
> 53ac2ae27650 postfix: 0605F207B0F36: to=<xxxx at xxxx.xx>, 
> relay=127.0.0.1[127.0.0.1]:10024, delay=1.5, delays=0.36/0/0/1.1, 
> dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 
> 250 2.0.0 Ok: queued as 6FC89207B0F38)
> Oct 04 03:30:31 dockerhost docker[12154]: 2019-10-04T03:30:31 
> 53ac2ae27650 postfix: 6FC89207B0F38: to=<xxxx at xxxx.xx>, relay=dovecot, 
> delay=0.31, delays=0.05/0/0/0.26, dsn=4.3.0, status=deferred (Command 
> died with signal 11: "/usr/libexec/dovecot/dovecot-lda")
>
> Using docker with official alpine image.
>
> / # cat /etc/alpine-release
> 3.8.4
>
> / # apk info -v | grep dovecot
> WARNING: Ignoring APKINDEX.adfa7ceb.tar.gz: No such file or directory
> WARNING: Ignoring APKINDEX.efaa1f73.tar.gz: No such file or directory
> dovecot-2.3.7.2-r0
> dovecot-fts-solr-2.3.7.2-r0
> dovecot-ldap-2.3.7.2-r0
> dovecot-pigeonhole-plugin-2.3.7.2-r0
> dovecot-pigeonhole-plugin-ldap-2.3.7.2-r0
>
> Sieve rule is:
> # rule:[test]
> if header :contains "subject" "test"
> {
>         redirect "testemail at gmail.com";
> }
>
> In host's dmesg we found the following:
> [213184.882341] traps: dovecot-lda[6128] general protection 
> ip:7ff6cf8144f7 sp:7fff5f800b30 error:0 in 
> libdovecot.so.0.0.0[7ff6cf724000+360000]
>
> Sorry, not knowledgeable enough on how to do the GBD debug.
> -----------------
> We went back to previous version and issue disappeared.
>
> 8b45bb255b67:/# cat /etc/alpine-release
> 3.8.4
> 8b45bb255b67:/# apk info -v | grep dovecot
> WARNING: Ignoring APKINDEX.adfa7ceb.tar.gz: No such file or directory
> WARNING: Ignoring APKINDEX.efaa1f73.tar.gz: No such file or directory
> dovecot-2.3.6-r0
> dovecot-fts-solr-2.3.6-r0
> dovecot-ldap-2.3.6-r0
> dovecot-pigeonhole-plugin-2.3.6-r0
> dovecot-pigeonhole-plugin-ldap-2.3.6-r0
>
> Anyone else already had this problem or you know how to fix it?

I can't readily reproduce it with the information available so far. Do 
you have the opportunity to obtain a GDB backtrace? You can e.g. run LDA 
manually at the command line with the same arguments and message input 
Postfix provides and wrap it in GDB if you can reproduce the crash.

Your configuration may also help (output from `dovecot -n`)

Regards,

Stephan.