Re: [Dovecot] Thinderbird+delete+move to Trash folder
On Tue, Dec 22, 2009 at 12:32:00AM +0100, Papp Tamás wrote: It's like when a messages is deleted from TB, the message get moved to the Trash folder, and it's expunged(?) at the same time. Is it possible? Do you use TB2? And do you have two trash folders? Like: - INBOX.Trash - Trash Then have a look at this bugreport: https://bugzilla.mozilla.org/show_bug.cgi?id=479226 TB3 behaves differently, but still wrong. So long, Aiko -- :wq ✉
[Dovecot] Openbsd Postfix-Dovecot-SASL
Greetings all, I have a OpenBSD /Dovecot server at home running and sending / receiving email internally without issue.. Recently, I set up the same at our Parish, but one of our users wants to get their email externally. The user can read their email but has to send via the local ISP server.. The problem After much searching I have not found an answer to my question. I would like the user to authenticate to be able to send email through the server.. OpenBSD uses bsdauth by default in Dovecot. After reading the Postfix http://www.postfix.org/SASL_README.html and the Dovecot Wiki http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL I have tried multiple configurations but I can't seem to get this to work.. It may be something very simple that I am missing.. All users on the Server have accounts in /etc/passwd (just no shell) Postfix - main.cf mailbox_command = /usr/local/libexec/dovecot/deliver mynetworks = 127.0.0.0/8 smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination dovecot --version 1.1.16 dovecot -n # OS: OpenBSD 4.6 i386 base_dir: /var/dovecot/ protocols: imaps listen: *, [::] ssl_cert_file: /etc/ssl/dovecotcert.pem disable_plaintext_auth: no login_dir: /var/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: _dovecot login_max_processes_count: 256 max_mail_processes: 32 mail_location: maildir:~/Maildir mbox_write_locks: fcntl imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep auth default: cache_size: 1024 passdb: driver: bsdauth args: cache_key=%u userdb: driver: passwd socket: type: listen client: path: /var/run/auth-client mode: 432 user: _postfix master: path: /var/run/auth-master mode: 384 user: _postfix Error using bsdauth Dec 21 15:07:09 aml000t3 dovecot: dovecot v1.1.16 starting up Dec 21 15:07:09 aml000t3 dovecot: Panic: auth(default): file passdb.c: line 190 (passdb_init): assertion failed: (passdb-passdb-default_pass_scheme != NULL || passdb-passdb-cache_key == NULL) Dec 21 15:07:09 aml000t3 dovecot: child 18954 (auth) killed with signal 6 (core not dumped) Dec 21 15:07:09 aml000t3 dovecot: Fatal: Auth process died too early - shutting down It looks like bsdauth has a bug and even though this thread lists a patch, I haven't been able to find it.. http://old.nabble.com/bsdauth-with-cache_key-failed-ts25800484.html#a25800484 so I guess I am looking for an alternative to be able to allow users to send through the server Thx for any pointers tk -- View this message in context: http://old.nabble.com/Openbsd-Postfix-Dovecot-SASL-tp26890148p26890148.html Sent from the Dovecot mailing list archive at Nabble.com.
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
I'm seeing both of these dumps on multiple users now with 1.2.9, so I went ahead and did backtraces for them both. maildir_uidlist_records_array_delete panic: http://pastebin.com/f20614d8 ns_get_listed_prefix panic: http://pastebin.com/f1420194c On 12/21/2009 12:43 PM, David Halik wrote: Just wanted to update you that I just upgraded all of our servers to 1.2.9 and I'm still seeing the array_delete panic: Dec 21 12:10:16 gehenna11.rutgers.edu dovecot: IMAP(user1): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 21 12:15:12 gehenna19.rutgers.edu dovecot: IMAP(user2): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) I also started receiving a good deal of these, but only from one user so far: Dec 21 12:16:42 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Dec 21 12:18:20 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Dec 21 12:18:20 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Dec 21 12:19:57 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Let me know if you need full backtraces from the core dump. On 12/17/2009 02:06 PM, David Halik wrote: On 12/17/2009 01:07 PM, Timo Sirainen wrote: On Thu, 2009-12-17 at 12:49 -0500, David Halik wrote: I applied those patches to my 1.2.8 installation before 1.2.9 was released and that immediately fixed the expunge crash, but the array_delete bug is still there. Do you also see the duplicate file entry before the crash? Yes, the duplicate file entry is always reported immediately before the crash, just as Ralf reported too. You can see it in this example pastebin I took from one of our users: http://pastebin.com/f29c55de5 maildir:~/Maildir:INDEX=/rci/nqu%h/dovecot:CONTROL=/rci/nqu%h/dovecot Are the index/control files on NFS? Are there multiple different servers accessing mail data? Correct. All index, control files, amd mail storage are located on NFS and there are multiple load balanced servers accessing the NFS data. We're currently running with: mmap_disable = yes dotlock_use_excl = yes fsync_disable = no mail_nfs_storage = yes mail_nfs_index = yes -- David Halik System Administrator OIT-CSS Rutgers University dha...@jla.rutgers.edu
Re: [Dovecot] Openbsd Postfix-Dovecot-SASL
On 12/22/2009 04:37 PM thekat wrote: … The user can read their email but has to send via the local ISP server.. The problem After much searching I have not found an answer to my question. I would like the user to authenticate to be able to send email through the server.. OpenBSD uses bsdauth by default in Dovecot. After reading the Postfix http://www.postfix.org/SASL_README.html and the Dovecot Wiki http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL I have tried multiple configurations but I can't seem to get this to work.. It may be something very simple that I am missing.. All users on the Server have accounts in /etc/passwd (just no shell) Postfix - main.cf mailbox_command = /usr/local/libexec/dovecot/deliver mynetworks = 127.0.0.0/8 smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth ^^ smtpd_sasl_auth_enable = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination dovecot --version 1.1.16 dovecot -n … socket: type: listen client: path: /var/run/auth-client mode: 432 user: _postfix master: path: /var/run/auth-master mode: 384 user: _postfix Check your logs. I think Postfix should have logged something, because it was unable to find $(postconf -h queue_directory)/private/auth Please read http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL again. Then check path setting of the client auth socket. Regards, Pascal -- The trapper recommends today: fabaceae.0935...@localdomain.org
Re: [Dovecot] Openbsd Postfix-Dovecot-SASL
On 12/22/2009 04:37 PM thekat wrote: … Error using bsdauth Dec 21 15:07:09 aml000t3 dovecot: Panic: auth(default): file passdb.c: line 190 (passdb_init): assertion failed: (passdb-passdb-default_pass_scheme != NULL || passdb-passdb-cache_key == NULL) It looks like bsdauth has a bug and even though this thread lists a patch, I haven't been able to find it.. http://old.nabble.com/bsdauth-with-cache_key-failed-ts25800484.html#a25800484 so I guess I am looking for an alternative to be able to allow users to send through the server Sorry, I misread this part. My reply http://old.nabble.com/bsdauth-with-cache_key-failed-ts25800484.html#a25845782 includes the patch. The patch is also available in the official Dovecot repository: http://hg.dovecot.org/dovecot-1.1/rev/b521d13ea89e But the best alternative would be to update to v1.1.20 or even better to v1.2.9 Regards, Pascal -- The trapper recommends today: deadbeef.0935...@localdomain.org
Re: [Dovecot] Openbsd Postfix-Dovecot-SASL
Pascal Volk-3 wrote: Sorry, I misread this part. My reply http://old.nabble.com/bsdauth-with-cache_key-failed-ts25800484.html#a25845782 includes the patch. The patch is also available in the official Dovecot repository: http://hg.dovecot.org/dovecot-1.1/rev/b521d13ea89e But the best alternative would be to update to v1.1.20 or even better to v1.2.9 Regards, Pascal Thx for the reply... OpenBSD is one of the systems that I have never done a third party patch on.. and my guess is that v1.1.20 will not be available until 4.7 .. v1.1.20 is available in 4.6 -current That being said can you provide the configure and compile options for OpenBSD ? Or would a better route be to use a different authentication other than bsdauth ? Thx tk -- View this message in context: http://old.nabble.com/Openbsd-Postfix-Dovecot-SASL-tp26890148p26893055.html Sent from the Dovecot mailing list archive at Nabble.com.
Re: [Dovecot] Openbsd Postfix-Dovecot-SASL
On 12/22/2009 08:30 PM thekat wrote: Thx for the reply... OpenBSD is one of the systems that I have never done a third party patch on.. and my guess is that v1.1.20 will not be available until 4.7 .. v1.1.20 is available in 4.6 -current That being said can you provide the configure and compile options for OpenBSD ? My config.log contains: $ ./configure --prefix=/usr/local --build=i386-unknown-openbsd --host=i386-unknown-openbsd --with-bsdauth --with-checkpassword --with-libiconv-prefix --with-passwd --with-passwd-file --with-pgsql --with-ssl=openssl --with-zlib --without-db --without-gssapi --without-ldap --without-mysql --without-nss --without-pam --without-shadow --without-sqlite --without-static-userdb --without-vpopmail When configured use gmake, not make. Or would a better route be to use a different authentication other than bsdauth ? Depends on your demands. Regards, Pascal -- The trapper recommends today: c01dcofe.0935...@localdomain.org
[Dovecot] Dovecot quota not working
Hi everyone, I'm trying to make quota to work in dovecot 1.0.rc15 in a Debian machine. Setting the limit to 1GB and starting to fill up the mailbox and nothing stopped me. It just kept growing and nothing happened. Restarted the service and nothing. I had already exceeded the 1 GB limit and nothing happens, the mailbox still goes bigger and bigger... The *check_quota* plugin for squirrelmail shows 0.0% of 1.0GB in my browser. 1GB is exactly what it is defined in dovecot.conf by maildir. Is it necessary to configure something in postfix? Details: # dovecot --version 1.0.rc15 # dovecot -n # /etc/dovecot/dovecot.conf IEffective uid=65534, gid=65534 ILoading modules from directory: /usr/lib/dovecot/modules/imap IModule loaded: /usr/lib/dovecot/modules/imap/lib01_quota_plugin.so IModule loaded: /usr/lib/dovecot/modules/imap/lib02_imap_quota_plugin.so log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login first_valid_uid: 0 first_valid_gid: 0 mail_privileged_group: users mail_location: mbox:/home/%u:INBOX=/var/mail/%u mail_debug: yes mmap_disable: yes mbox_read_locks: flock mbox_write_locks: flock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: passdb: driver: pam userdb: driver: passwd regards, -- Bruno Guimarães Sousa www.ifba.edu.br PONTONET - DGTI - IFBA Ciência da Computação UFBA Registered Linux user #465914
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
We've started seeing the maildir_uidlist_records_array_delete assert crash as well. It always seems to be preceded by a 'stale NFS file handle' error from a the same user on a different connection. Dec 22 10:12:20 oh-popmap5p dovecot: imap: user=apbao, rip=a.a.a.a, pid=2439: fdatasync(/home11/apbao/Maildir/dovecot-uidlist) failed: Stale NFS file handle Dec 22 10:12:20 oh-popmap5p dovecot: imap: user=apbao, rip=a.a.a.a, pid=2439: /home11/apbao/Maildir/dovecot-uidlist: next_uid was lowered (2642 - 2641, hdr=2641) Dec 22 11:17:26 cc-popmap2p dovecot: imap: user=apbao, rip=b.b.b.b, pid=28088: Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 22 11:17:26 cc-popmap2p dovecot: imap: user=apbao, rip=b.b.b.b, pid=28088: Raw backtrace: imap [0x4d8986] - imap [0x4d97b0] - imap(i_fatal+0) [0x4d8c7a] - imap [0x44f2cc] - imap [0x44f814] - imap [0x4500a2] - imap(maildir_uidlist_refresh+0x9d) [0x450686] - imap [0x44bff1] - imap [0x44c0a8] - imap [0x44c178] - imap(maildir_storage_sync_init+0x7c) [0x44c6e6] - imap(mailbox_sync_init+0x44) [0x489922] - imap(imap_sync_init+0xab) [0x42e02b] - imap [0x42f107] - imap(cmd_sync_delayed+0x1c6) [0x42f663] - imap(client_handle_input+0x119) [0x4244d4] - imap(client_input+0xb4) [0x424594] - imap(io_loop_handler_run+0x17d) [0x4e5020] - imap(io_loop_run+0x3b) [0x4e4214] - imap(main+0xa6) [0x4300af] - /lib64/libc.so.6(__libc_start_main+0xf4) [0x3c4ea1d994] - imap [0x419aa9] Dec 22 11:17:26 cc-popmap2p dovecot: dovecot: child 28088 (imap) killed with signal 6 (core dumped) Dec 22 13:16:49 cc-popmap3p dovecot: imap: user=ndunn, rip=x.x.x.x, pid=3908: fdatasync(/home2/ndunn/Maildir/dovecot-uidlist) failed: Stale NFS file handle Dec 22 13:25:16 cc-popmap3p dovecot: imap: user=ndunn, rip=y.y.y.y, pid=3228: Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 22 13:25:16 cc-popmap3p dovecot: imap: user=ndunn, rip=y.y.y.y, pid=3228: Raw backtrace: imap [0x4d8986] - imap [0x4d97b0] - imap(i_fatal+0) [0x4d8c7a] - imap [0x44f2cc] - imap [0x44f814] - imap [0x4500a2] - imap(maildir_uidlist_refresh+0x9d) [0x450686] - imap [0x44bff1] - imap [0x44c0a8] - imap [0x44c178] - imap(maildir_storage_sync_init+0x7c) [0x44c6e6] - imap(mailbox_sync_init+0x44) [0x489922] - imap(imap_sync_init+0xab) [0x42e02b] - imap [0x42f107] - imap(cmd_sync_delayed+0x1c6) [0x42f663] - imap(client_handle_input+0x119) [0x4244d4] - imap(client_input+0xb4) [0x424594] - imap(io_loop_handler_run+0x17d) [0x4e5020] - imap(io_loop_run+0x3b) [0x4e4214] - imap(main+0xa6) [0x4300af] - /lib64/libc.so.6(__libc_start_main+0xf4) [0x3e5021d994] - imap [0x419aa9] Dec 22 13:25:16 cc-popmap3p dovecot: dovecot: child 3228 (imap) killed with signal 6 (core dumped) I will note that we did not start seeing this crash until we took 'noac' out of our NFS mount options, as discussed on this list late last week. On the other hand, load on our NFS server (as measured in IOPS/sec) has dropped by a factor of 10. -Brad -Original Message- From: dovecot-bounces+brandond=uoregon@dovecot.org [mailto:dovecot- bounces+brandond=uoregon@dovecot.org] On Behalf Of David Halik Sent: Tuesday, December 22, 2009 7:48 AM To: dovecot@dovecot.org Subject: Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace) I'm seeing both of these dumps on multiple users now with 1.2.9, so I went ahead and did backtraces for them both. maildir_uidlist_records_array_delete panic: http://pastebin.com/f20614d8 ns_get_listed_prefix panic: http://pastebin.com/f1420194c On 12/21/2009 12:43 PM, David Halik wrote: Just wanted to update you that I just upgraded all of our servers to 1.2.9 and I'm still seeing the array_delete panic: Dec 21 12:10:16 gehenna11.rutgers.edu dovecot: IMAP(user1): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 21 12:15:12 gehenna19.rutgers.edu dovecot: IMAP(user2): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) I also started receiving a good deal of these, but only from one user so far: Dec 21 12:16:42 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Dec 21 12:18:20 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Dec 21 12:18:20 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Dec 21 12:19:57 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Let me know if you need full backtraces from the core
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
I just double checked and we're seeing the same thing here, although we were never running with noac to begin with. Our poor NFS server would melt probably. ;) This is immediately before the crash: Dec 22 13:09:20 gehenna14.rutgers.edu dovecot: IMAP(user): fdatasync(/rci/nqu/rci/u5/bruben/dovecot/.INBOX/dovecot-uidlist) failed: Stale NFS file handle Dec 22 13:09:20 gehenna14.rutgers.edu dovecot: IMAP(user): /rci/nqu/rci/u5/bruben/dovecot/.INBOX/dovecot-uidlist: next_uid was lowered (1507 - 1506, hdr=1506) Dec 22 13:12:06 gehenna14.rutgers.edu dovecot: IMAP(user): /rci/nqu/rci/u5/bruben/dovecot/.INBOX/dovecot-uidlist: Duplicate file entry at line 3: 1249348137.M369064P26267V04240006I01ED7E09_0.gehenna5.rutgers.edu,S=15857:2,S (uid 1208 - 1508) On 12/22/2009 04:33 PM, Brandon Davidson wrote: We've started seeing the maildir_uidlist_records_array_delete assert crash as well. It always seems to be preceded by a 'stale NFS file handle' error from a the same user on a different connection. Dec 22 10:12:20 oh-popmap5p dovecot: imap: user=apbao, rip=a.a.a.a, pid=2439: fdatasync(/home11/apbao/Maildir/dovecot-uidlist) failed: Stale NFS file handle Dec 22 10:12:20 oh-popmap5p dovecot: imap: user=apbao, rip=a.a.a.a, pid=2439: /home11/apbao/Maildir/dovecot-uidlist: next_uid was lowered (2642 - 2641, hdr=2641) Dec 22 11:17:26 cc-popmap2p dovecot: imap: user=apbao, rip=b.b.b.b, pid=28088: Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 22 11:17:26 cc-popmap2p dovecot: imap: user=apbao, rip=b.b.b.b, pid=28088: Raw backtrace: imap [0x4d8986] - imap [0x4d97b0] - imap(i_fatal+0) [0x4d8c7a] - imap [0x44f2cc] - imap [0x44f814] - imap [0x4500a2] - imap(maildir_uidlist_refresh+0x9d) [0x450686] - imap [0x44bff1] - imap [0x44c0a8] - imap [0x44c178] - imap(maildir_storage_sync_init+0x7c) [0x44c6e6] - imap(mailbox_sync_init+0x44) [0x489922] - imap(imap_sync_init+0xab) [0x42e02b] - imap [0x42f107] - imap(cmd_sync_delayed+0x1c6) [0x42f663] - imap(client_handle_input+0x119) [0x4244d4] - imap(client_input+0xb4) [0x424594] - imap(io_loop_handler_run+0x17d) [0x4e5020] - imap(io_loop_run+0x3b) [0x4e4214] - imap(main+0xa6) [0x4300af] - /lib64/libc.so.6(__libc_start_main+0xf4) [0x3c4ea1d994] - imap [0x419aa9] Dec 22 11:17:26 cc-popmap2p dovecot: dovecot: child 28088 (imap) killed with signal 6 (core dumped) Dec 22 13:16:49 cc-popmap3p dovecot: imap: user=ndunn, rip=x.x.x.x, pid=3908: fdatasync(/home2/ndunn/Maildir/dovecot-uidlist) failed: Stale NFS file handle Dec 22 13:25:16 cc-popmap3p dovecot: imap: user=ndunn, rip=y.y.y.y, pid=3228: Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 22 13:25:16 cc-popmap3p dovecot: imap: user=ndunn, rip=y.y.y.y, pid=3228: Raw backtrace: imap [0x4d8986] - imap [0x4d97b0] - imap(i_fatal+0) [0x4d8c7a] - imap [0x44f2cc] - imap [0x44f814] - imap [0x4500a2] - imap(maildir_uidlist_refresh+0x9d) [0x450686] - imap [0x44bff1] - imap [0x44c0a8] - imap [0x44c178] - imap(maildir_storage_sync_init+0x7c) [0x44c6e6] - imap(mailbox_sync_init+0x44) [0x489922] - imap(imap_sync_init+0xab) [0x42e02b] - imap [0x42f107] - imap(cmd_sync_delayed+0x1c6) [0x42f663] - imap(client_handle_input+0x119) [0x4244d4] - imap(client_input+0xb4) [0x424594] - imap(io_loop_handler_run+0x17d) [0x4e5020] - imap(io_loop_run+0x3b) [0x4e4214] - imap(main+0xa6) [0x4300af] - /lib64/libc.so.6(__libc_start_main+0xf4) [0x3e5021d994] - imap [0x419aa9] Dec 22 13:25:16 cc-popmap3p dovecot: dovecot: child 3228 (imap) killed with signal 6 (core dumped) I will note that we did not start seeing this crash until we took 'noac' out of our NFS mount options, as discussed on this list late last week. On the other hand, load on our NFS server (as measured in IOPS/sec) has dropped by a factor of 10. -Brad -Original Message- From: dovecot-bounces+brandond=uoregon@dovecot.org [mailto:dovecot- bounces+brandond=uoregon@dovecot.org] On Behalf Of David Halik Sent: Tuesday, December 22, 2009 7:48 AM To: dovecot@dovecot.org Subject: Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace) I'm seeing both of these dumps on multiple users now with 1.2.9, so I went ahead and did backtraces for them both. maildir_uidlist_records_array_delete panic: http://pastebin.com/f20614d8 ns_get_listed_prefix panic: http://pastebin.com/f1420194c On 12/21/2009 12:43 PM, David Halik wrote: Just wanted to update you that I just upgraded all of our servers to 1.2.9 and I'm still seeing the array_delete panic: Dec 21 12:10:16 gehenna11.rutgers.edu dovecot: IMAP(user1): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 21 12:15:12 gehenna19.rutgers.edu dovecot: IMAP(user2): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos
Re: [Dovecot] Dovecot quota not working
On 2009-12-22, Bruno Guimarães Sousa (brgso...@gmail.com) wrote: Details: # dovecot --version 1.0.rc15 Upgrade. No point in even discussing this until you do. 1.0rc15 is way, way too old and buggy. -- Best regards, Charles
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
On 22.12.2009, at 16.42, David Halik wrote: I just double checked and we're seeing the same thing here, although we were never running with noac to begin with. Our poor NFS server would melt probably. ;) This is immediately before the crash: Dec 22 13:09:20 gehenna14.rutgers.edu dovecot: IMAP(user): fdatasync(/rci/nqu/rci/u5/bruben/dovecot/.INBOX/dovecot-uidlist) failed: Stale NFS file handle The interesting this is that this function is called only when dovecot-uidlist.lock has been created, i.e. when uidlist is locked, meaning nothing should have deleted the dovecot-uidlist while it was being written to, so this error just shouldn't happen.. So apparently the dotlocking just isn't working properly for your NFS servers. See if dotlock_use_excl=no helps?
