Hi,
I tried to set up imap4d to access my local Debian testing mailbox; the example
mailutils.rc found at
http://gnu.ist.utl.pt/software/mailutils/manual/html_node/config-sample.html
works, but by trying to introduce TLS (both "required" and "connection") with
the following mailutils.conf:
program imap4d {
pam {
service mailutils;
};
mailbox {
mail-spool /var/mail;
};
pidfile /run/imap4d.pid;
server 127.0.0.1:993 {
tls-mode connection;
tls {
ssl-certificate-file /etc/ssl/certs/mycert.pem;
ssl-key-file /etc/ssl/private/mykey.key;
ssl-ca-file /usr/local/share/ca-certificates/mylocalca.crt;
};
};
}
causes segfaults in libmailutils.so.8.0.0:
Feb 14 17:15:09 mybox imap4d[266644]: imap4d (GNU Mailutils 3.14) started
Feb 14 17:15:42 mybox imap4d[266942]: TLS established using AES-128-GCM-AEAD
(TLS1.3)
Feb 14 17:15:42 mybox imap4d[266941]: TLS established using AES-128-GCM-AEAD
(TLS1.3)
Feb 14 17:15:42 mybox imap4d[266644]: process 266941 terminated on signal 11
Feb 14 17:15:42 mybox imap4d[266644]: process 266942 terminated on signal 11
Feb 14 17:15:42 mybox kernel: [36389.811980] imap4d[266941]: segfault at 0 ip
00007fb80f22e479 sp 00007ffd38de5f40 error 4 in
libmailutils.so.8.0.0[7fb80f198000+a4000]
Feb 14 17:15:42 mybox kernel: [36389.811991] imap4d[266942]: segfault at 0 ip
00007fb80f22e479 sp 00007ffd38de5f40 error 4
Feb 14 17:15:42 mybox kernel: [36389.811994] Code: 89 7d f8 48 89 75 f0 48 8b 45 f8 8b
40 28 25 ff ff ff 00 89 c2 48 8b 45 f0 89 10 90 5d c3 55 48 89 e5 48 89 7d f8 48 8b 45
f8 <8b> 00 8d 50 01 48 8b 45 f8 89 10 90 5d c3 55 48 89 e5 48 83 ec>
Feb 14 17:15:42 mybox kernel: [36389.812003] in
libmailutils.so.8.0.0[7fb80f198000+a4000]
Feb 14 17:15:42 mybox kernel: [36389.812007] Code: 89 7d f8 48 89 75 f0 48 8b 45 f8 8b
40 28 25 ff ff ff 00 89 c2 48 8b 45 f0 89 10 90 5d c3 55 48 89 e5 48 89 7d f8 48 8b 45
f8 <8b> 00 8d 50 01 48 8b 45 f8 89 10 90 5d c3 55 48 89 e5 48 83 ec>
Feb 14 17:15:43 mybox imap4d[266955]: TLS established using AES-128-GCM-AEAD
(TLS1.3)
Feb 14 17:15:43 mybox imap4d[266956]: TLS established using AES-128-GCM-AEAD
(TLS1.3)
Feb 14 17:15:43 mybox kernel: [36390.279626] imap4d[266955]: segfault at 0 ip
00007fb80f22e479 sp 00007ffd38de5f40 error 4 in
libmailutils.so.8.0.0[7fb80f198000+a4000]
Feb 14 17:15:43 mybox kernel: [36390.279639] Code: 89 7d f8 48 89 75 f0 48 8b 45 f8 8b
40 28 25 ff ff ff 00 89 c2 48 8b 45 f0 89 10 90 5d c3 55 48 89 e5 48 89 7d f8 48 8b 45
f8 <8b> 00 8d 50 01 48 8b 45 f8 89 10 90 5d c3 55 48 89 e5 48 83 ec>
Feb 14 17:15:43 mybox kernel: [36390.284017] imap4d[266956]: segfault at 0 ip
00007fb80f22e479 sp 00007ffd38de5f40 error 4 in
libmailutils.so.8.0.0[7fb80f198000+a4000]
Feb 14 17:15:43 mybox kernel: [36390.284033] Code: 89 7d f8 48 89 75 f0 48 8b 45 f8 8b
40 28 25 ff ff ff 00 89 c2 48 8b 45 f0 89 10 90 5d c3 55 48 89 e5 48 89 7d f8 48 8b 45
f8 <8b> 00 8d 50 01 48 8b 45 f8 89 10 90 5d c3 55 48 89 e5 48 83 ec>
Feb 14 17:15:43 mybox imap4d[266644]: process 266955 terminated on signal 11
Feb 14 17:15:43 mybox imap4d[266644]: process 266956 terminated on signal 11
Feb 14 17:16:03 mybox imap4d[266644]: imap4d (GNU Mailutils 3.14) terminated
The client behaves like login was accepted, but obviously the mailbox can't be
accessed. Tried both with testing (v1:3.13-1) and with unstable (v1:3.14-1)
versions: both behave the same.
I'm already using pop3d with TLS and it uses to work like a charm.
Am I missing something or I ran into a bug?
Thanks
Maurizio
