similar to: Dovecot 1.1.4 crash

Hello, after upgrade from beta8 to beta9 deliver process crashes with segfault. Deleting old maildirs does not help. Here is backtrace: Program received signal SIGSEGV, Segmentation fault. 0x0808e36d in mail_cache_field_get_decision (cache=0x8114da0, field_idx=128) at mail-cache-lookup.c:301 301 i_assert(field_idx < cache->fields_count); (gdb) bt #0 0x0808e36d in

To some users happens this assertion failure while deleting a message. dovecot: Mar 10 08:40:44 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists (&ibox->recent_flags, uid)) dovecot: Mar 10 08:40:44 Error: IMAP(user): Raw backtrace: [see bleow] dovecot: Mar 10 08:40:44 Error: child 17683 (imap) killed with signal 6 And the

Ive been getting a LOT of these errors since 1.1.2: So far ive seen this with 1800 customers, and we're getting active complaints about errors in imap clients. When I check the users log I always see this error.. This always happens with COPY commands in Squirrelmail. Sep 2 20:09:35 userimap4.xs4all.nl dovecot: IMAP(xxxxxxx):

Hey guys, got a question about the expire plugin. According to the wiki, the expire plugin "keeps an internal database (Berkeley DB or SQL)". I was wondering what fields in the mysql table are needed for expire to work. I assume it is setup is similar to the quota dict setup, so was just wondering what fields are required (i.e: select_field, where_field, username_field, for quota).

Hi, Wrong UIDs are returned from mailbox_transaction_commit_get_uids() in dovecot-1.1.rc3. The problem is in: int mailbox_transaction_commit(struct mailbox_transaction_context **t) { uint32_t tmp; return mailbox_transaction_commit_get_uids(t, &tmp, &tmp, &tmp); } It should be: int mailbox_transaction_commit(struct mailbox_transaction_context **t) { uint32_t tmp1,

Following version and content of .conf file ---------------------------------------------------------------------------------------- root at ABCD:/CavE/download/delete_to_trash# dovecot --version 2.2.9 root at ABCD:/CavE/download/delete_to_trash# dovecot -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-32-generic x86_64 Ubuntu 14.04.1 LTS auth_mechanisms = plain login log_path =

Hi, I?d like to extend the mail_log plugin to log the uid and keywords of a mail delivered by LDA. The keywords are set by the sieve plugin. I added a mail_log_save_finish() function hook listed below. However, the uid of the mail is always zero and trying to get the keywords results in assertion failure, probably because the message is not committed yet: Feb 13 08:07:42 ha-test1 deliver(test1

Hi! Using the latest cvs from HEAD, I'm experiencing problems after sending a message and the client is trying upload the message to the appropriate (Sent/Queue) folder. I get only one error in dovecot.log: dovecot: Nov 25 14:21:31 Error: child 19554 (imap) killed with signal 11 So my client disconnects, and asks for the password again, and in dovecot.info I get nothing, but the logs of the

Hi, when the attached mail was stored in a maildir, fetching mail via POP3 lead to multiple delivery of mails in that maildir to the client (Outlook). I replaced the domain with dots. This is the dovecot configuration: --snip-- protocols = imap imaps pop3 pop3s listen = * disable_plaintext_auth = no ssl_cert_file = /etc/ssl/dovecot/server.pem ssl_key_file = /etc/ssl/dovecot/server.key

Program received signal SIGSEGV, Segmentation fault. 0x00007f1975cccdee in expire_mailbox_transaction_commit (t=<value optimized out>, changes_r=<value optimized out>) at expire-plugin.c:169 169 } else if (strcmp(value, "0") == 0) { (gdb) bt #0 0x00007f1975cccdee in expire_mailbox_transaction_commit (t=<value optimized out>,

The maildir_mail_gate_save_date routine (lib-storage/index/maildir/maildir-mail.c) returns the save date when that was determined by looking at the ctime of the corresponding file. This is different from all other get_save_date routines which either return -1 if the date could not be determined or 0 to signal success. A particular problem caused by this would be that the

On 09/23/2016 08:05 AM, Aki Tuomi wrote: > On 29.07.2016 15:35, Nagy, Attila wrote: >> I use pass and userdb with dict protocol in a similar way: >> >> key passdb { >> key = passdb^MAuth-User: %u^MAuth-Pass: %w^MAuth-Protocol: >> %s^MClient-IP: %r >> format = json >> } >> >> (^M is an \r character, inserted with vi CTRL-v + enter)