Hi,

I'm getting three types of errors with latest Dovecot compiled for x86_64 GNU/Linux Debian.

Oct 29 12:47:57 rouge imap-login: unable to dlopen /usr/lib/sasl2/libntlm.so.2: /usr/lib/sasl2/libntlm.so.2: failed to map segment from shared object: Cannot allocate memory Oct 29 12:47:57 rouge pop3-login: unable to dlopen /usr/lib/sasl2/libntlm.so.2: /usr/lib/sasl2/libntlm.so.2: failed to map segment from shared object: Cannot allocate memory

I have no idea why there is this error, but it comes each time a user logs in, with no other severe effect.

Oct 29 01:28:54 rouge dovecot: imap(glondu): pool_system_malloc(): Out of memory Oct 29 01:28:54 rouge dovecot: child 5642 (imap) returned error 83 (Out of memory) Oct 29 01:38:10 rouge dovecot: imap(glondu): pool_system_malloc(): Out of memory Oct 29 01:38:10 rouge dovecot: child 5639 (imap) returned error 83 (Out of memory) Oct 29 01:49:22 rouge dovecot: imap(glondu): pool_system_malloc(): Out of memory Oct 29 01:49:22 rouge dovecot: child 8839 (imap) returned error 83 (Out of memory)

The mailbox for this user is not bigger that 10MB and dovecot mail_process_size is set to default setting so I don't see why there could be a "Out of memory" error.

Oct 28 18:00:45 rouge dovecot: imap(vidal): Lost transaction log file /var/dovecot-indexes/vidal/.INBOX/dovecot.index.log seq 1 Oct 28 18:00:45 rouge dovecot: imap(vidal): Lost transaction log file /var/dovecot-indexes/vidal/.INBOX/dovecot.index.log seq 1 Oct 28 18:00:56 rouge dovecot: imap(vidal): Lost transaction log file /var/dovecot-indexes/vidal/.INBOX/dovecot.index.log seq 1 Oct 28 18:00:56 rouge dovecot: imap(vidal): Lost transaction log file /var/dovecot-indexes/vidal/.INBOX/dovecot.index.log seq 1

This error caused the user's mailbox to be unreadable, and erasing the indexes resolved the problem, but I would have expected Dovecot to have done it itself if the indexes were corrupted ?

Hope this feedback helps,

-- Nico