Re: Panic when runing "doveadm mailbox status ... vsize"
Thank you for pushing me in the right direction! I originally used "lock_method = dotlock" on this server. I had gotten to a point in trouble-shooting where i thought I should change to fcntl, which I did. BUT I did not restart dovecot! I just did that, and now "vsize" works. I don't have a theory for why dotlock wouldn't be supported in that path. Thanks again, Mark On Wed, Jul 20, 2016 at 01:25:44AM +0200, Michael Kliewe wrote: > Hi Mark, > > Am 19.07.2016 um 21:23 schrieb Mark Costlow: > > I have converted some test users and they generally work fine. But > > when I run "doveadm mailbox status" I get a Panic if I ask for the > > vsize field (or "all"), but other fields work fine. For example: > > > > # doveadm mailbox status -u bubbacheex3 "messages" INBOX > > INBOX messages=53 > > > > # doveadm mailbox status -u bubbacheex3 "guid" INBOX > > INBOX guid=bf976912f3748957761d0100f906a3d0 > > > > # doveadm mailbox status -u bubbacheex3 "unseen" INBOX > > INBOX unseen=52 > > > > # doveadm mailbox status -u bubbacheex3 "vsize" INBOX > > doveadm(bubbacheex3): Panic: file file-lock.c: line 269: unreached > > Abort trap > > > Have you checked that line 269 in file-lock.c? > https://github.com/dovecot/core/blob/master/src/lib/file-lock.c#L269 > > Do you have write access to the mail folder of the user? > > I'm not sure anymore, maybe a workaround for me was: > -o lock_method=fcntl > Using fcntl instead of dotlock for that command... > Or I made sure to have write access to the mail folder of the user... Or > both I don't remember anymore. > > Maybe someone can explain why dotlock is not supported in that code path. > > Michael -- Mark Costlow| Southwest Cyberport | Fax: +1-505-232-7975 che...@swcp.com | Web: www.swcp.com | Voice: +1-505-232-7992 Mail Minder - Intelligent Push Notifications for Email on the iPhone http://mailminderapp.com/download or in the App Store
Re: Panic when runing "doveadm mailbox status ... vsize"
Hi Mark, Am 19.07.2016 um 21:23 schrieb Mark Costlow: I have converted some test users and they generally work fine. But when I run "doveadm mailbox status" I get a Panic if I ask for the vsize field (or "all"), but other fields work fine. For example: # doveadm mailbox status -u bubbacheex3 "messages" INBOX INBOX messages=53 # doveadm mailbox status -u bubbacheex3 "guid" INBOX INBOX guid=bf976912f3748957761d0100f906a3d0 # doveadm mailbox status -u bubbacheex3 "unseen" INBOX INBOX unseen=52 # doveadm mailbox status -u bubbacheex3 "vsize" INBOX doveadm(bubbacheex3): Panic: file file-lock.c: line 269: unreached Abort trap Have you checked that line 269 in file-lock.c? https://github.com/dovecot/core/blob/master/src/lib/file-lock.c#L269 Do you have write access to the mail folder of the user? I'm not sure anymore, maybe a workaround for me was: -o lock_method=fcntl Using fcntl instead of dotlock for that command... Or I made sure to have write access to the mail folder of the user... Or both I don't remember anymore. Maybe someone can explain why dotlock is not supported in that code path. Michael
Re: Managesieve problem
Sorry, meant to include the dovecot version. root@4s-mail:~# dovecot --version 2.0.19 -Original Message- From: Joseph Mays Sent: Tuesday, July 19, 2016 7:03 PM To: dovecot@dovecot.org Subject: Managesieve problem Trying to get either avelsieve or server side filters to work with managesieve. Managesieve is running but whenever avelsieve or the server settings backend try to talk to it the same thing happens. So I guess it's really a problem with something about managesieve at this point. I hit the Message Filters option, it takes a long time for it to come back, though it finally just times out and does nothing, and immediately when I click on the Message Filters link the following two messages appear in /var/log/dovecot 2016-07-18 17:03:02 managesieve-login: Error: auth: connect(login) in directory / failed: Permission denied (euid=108() egid=65534() missing +x perm: /, dir owned by 0:111 mode=0750) 2016-07-18 17:03:02 managesieve-login: Error: auth: connect(login) in directory / failed: Permission denied (euid=108() egid=65534() missing +x perm: /, dir owned by 0:111 mode=0750) Seems to be straightforwardly a permissions error on a directory, but I don't believe it's really the / directory, so which directory is it? Any insights on where to look would be appreciated.
Managesieve problem
Trying to get either avelsieve or server side filters to work with managesieve. Managesieve is running but whenever avelsieve or the server settings backend try to talk to it the same thing happens. So I guess it's really a problem with something about managesieve at this point. I hit the Message Filters option, it takes a long time for it to come back, though it finally just times out and does nothing, and immediately when I click on the Message Filters link the following two messages appear in /var/log/dovecot 2016-07-18 17:03:02 managesieve-login: Error: auth: connect(login) in directory / failed: Permission denied (euid=108() egid=65534() missing +x perm: /, dir owned by 0:111 mode=0750) 2016-07-18 17:03:02 managesieve-login: Error: auth: connect(login) in directory / failed: Permission denied (euid=108() egid=65534() missing +x perm: /, dir owned by 0:111 mode=0750) Seems to be straightforwardly a permissions error on a directory, but I don't believe it's really the / directory, so which directory is it? Any insights on where to look would be appreciated.
Re: Panic when runing "doveadm mailbox status ... vsize"
> On July 19, 2016 at 10:23 PM Mark Costlow wrote: > > > I'm using dovecot 2.2.24 on FreeBSD 10.3. I'm working on converting > users from maildir to mdbox, for the usual reasons. > > I have converted some test users and they generally work fine. But > when I run "doveadm mailbox status" I get a Panic if I ask for the > vsize field (or "all"), but other fields work fine. For example: > Any hope for gdb with bt full on the corefile? --- Aki Tuomi Dovecot oy
Panic when runing "doveadm mailbox status ... vsize"
I'm using dovecot 2.2.24 on FreeBSD 10.3. I'm working on converting users from maildir to mdbox, for the usual reasons. I have converted some test users and they generally work fine. But when I run "doveadm mailbox status" I get a Panic if I ask for the vsize field (or "all"), but other fields work fine. For example: # doveadm mailbox status -u bubbacheex3 "messages" INBOX INBOX messages=53 # doveadm mailbox status -u bubbacheex3 "guid" INBOX INBOX guid=bf976912f3748957761d0100f906a3d0 # doveadm mailbox status -u bubbacheex3 "unseen" INBOX INBOX unseen=52 # doveadm mailbox status -u bubbacheex3 "vsize" INBOX doveadm(bubbacheex3): Panic: file file-lock.c: line 269: unreached Abort trap I've only converted a few users, but they all exhibit this problem. I converted them with: dsync -u bubbacheex3 mirror maildir:/var/tmp/bubbacheex3 I have done a force-resync, which succeeds but doesn't change the behavior. I spent a little time trying to get gdb running but didn't get very far (couldn't seem to get it to find the source files once I got a few levels deep in the call stack). Before I beat my head on the gdb issue more, I thought I'd check here to see if anyone has any ideas. I didn't turn up anything in google or searching this list. Here's my "doveconf -n" output: -- # 2.2.24 (a82c823): /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.3-RELEASE-p3 amd64 ufs auth_failure_delay = 1 secs auth_mechanisms = plain login auth_winbind_helper_path = /usr/local/bin/ntlm_auth auth_worker_max_count = 60 base_dir = /var/run/dovecot/ disable_plaintext_auth = no first_valid_gid = 100 first_valid_uid = 1000 listen = * login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_location = mdbox:/var/mail/%u:INDEX=/var/dovecot/%u mail_log_prefix = "%Us(%u): " mail_nfs_storage = yes mail_privileged_group = mail mdbox_rotate_interval = 1 days mdbox_rotate_size = 4 M mmap_disable = yes namespace { inbox = yes location = prefix = separator = . } passdb { args = session=yes dovecot driver = pam } protocols = imap pop3 service auth { unix_listener auth-client { mode = 0660 } unix_listener auth-master { mode = 0600 } user = root vsz_limit = 256 M } service imap-login { chroot = login process_limit = 128 process_min_avail = 10 service_count = 1 user = dovecot vsz_limit = 64 M } service imap { drop_priv_before_exec = no process_limit = 512 vsz_limit = 256 M } service pop3-login { chroot = login process_limit = 128 process_min_avail = 5 service_count = 1 user = dovecot vsz_limit = 64 M } service pop3 { drop_priv_before_exec = no process_limit = 512 vsz_limit = 256 M } ssl_cert = was automatically rejected:%n%r sendmail_path = /usr/sbin/sendmail } -- Thanks, Mark -- Mark Costlow| Southwest Cyberport | Fax: +1-505-232-7975 che...@swcp.com | Web: www.swcp.com | Voice: +1-505-232-7992 Mail Minder - Intelligent Push Notifications for Email on the iPhone http://mailminderapp.com/download or in the App Store
Re: an e-mail client for dovecot ?
Please do NOT send to me directly, I am on the list. Anyone who wishes direct responses should say so by setting explicit Reply-To. On 7/19/2016 11:42 AM, Miquel van Smoorenburg wrote: > On 18/07/16 11:46, Stephan Bosch wrote: >> >> >> Op 16-7-2016 om 18:12 schreef Charles Marcus: >>> >>> On July 16, 2016 4:02:33 AM EDT, Spyros Tsiolis >>> wrote: Since I have quite some experiece with thunderbird, I know most of its shortcomings >>> Care to elaborate? Thunderbird is far from perfect, but is by far the >>> best IMAP client available. >>> >>> Most times you can work around supposed short comings (if what you >>> think are short comings actually are, often they are not)... >> >> I agree. I haven't seen anything better so far. Still, with my 100+ >> folders it regularly hangs for a few seconds while it is presumably >> doing stuff in the background. So, for example composing a message is >> often a frustrating activity. This is enough reason for me to look for >> an alternative client, but there is no real alternative... > > Known problem. Sort of a indexing thundering herd problem. > > Preferences -> Advanced -> Config Editor, set mail.db.idlelimit to a > large number. I set it to 3000. Fixed it for me.. > > Mike. >
Re: an e-mail client for dovecot ?
On 18/07/16 11:46, Stephan Bosch wrote: > > > Op 16-7-2016 om 18:12 schreef Charles Marcus: >> >> On July 16, 2016 4:02:33 AM EDT, Spyros Tsiolis >> wrote: >>> Since I have quite some experiece with thunderbird, I know most of >>> its shortcomings >> Care to elaborate? Thunderbird is far from perfect, but is by far the >> best IMAP client available. >> >> Most times you can work around supposed short comings (if what you >> think are short comings actually are, often they are not)... > > I agree. I haven't seen anything better so far. Still, with my 100+ > folders it regularly hangs for a few seconds while it is presumably > doing stuff in the background. So, for example composing a message is > often a frustrating activity. This is enough reason for me to look for > an alternative client, but there is no real alternative... Known problem. Sort of a indexing thundering herd problem. Preferences -> Advanced -> Config Editor, set mail.db.idlelimit to a large number. I set it to 3000. Fixed it for me.. Mike.
Virtual mailboxes
I have been banging my head to the walls for the past couple of days to make virtual mailboxes work and I finally found the problem. It seems when prefetch is used the user_query is not working at all. However, I have not found any reference to this one. http://wiki.dovecot.org/Plugins/Virtual I have tried to add the SQL statements to the password_query with prefetch but it did not work. It seems that it only works with prefetch off.
Re: Replication sieve scripts.
On 2016.07.19. 15:03, Luescher Claude wrote: Hello, Are you sure about that I would need so recent version? That is ok to have some bugfixes but you are talking about the latest cutting edge debian jessie backports package. Even the mainline debian jessie only have 2.2.13 in it and my system is a complex wheezy installation, the last thing I want to do is to move all my components into jessie just because of this or do you know 2.2.15 deb packages built for wheezy? My installation is a multi-node cluster already I would have to update all the nodes but if it would be only to install a couple of new debs on them I would not hesitate trying a newer dovecot version. Thank you. If you have a huge multi node system, then you need to have testing system also. It's easy to compile Dovecot by yourself and make deb packages, if needed. -- KSB
Re: Replication sieve scripts.
Hello, Are you sure about that I would need so recent version? That is ok to have some bugfixes but you are talking about the latest cutting edge debian jessie backports package. Even the mainline debian jessie only have 2.2.13 in it and my system is a complex wheezy installation, the last thing I want to do is to move all my components into jessie just because of this or do you know 2.2.15 deb packages built for wheezy? My installation is a multi-node cluster already I would have to update all the nodes but if it would be only to install a couple of new debs on them I would not hesitate trying a newer dovecot version. Thank you. On Tue, 19 Jul 2016 11:54:27 +0200, Stephan Bosch wrote: Op 19-7-2016 om 11:30 schreef Luescher Claude: Hello, Following up on old thread: http://www.dovecot.org/pipermail/dovecot/2014-December/099003.html [1] I have the exact same issue with 2.2.10: It did not help. If there is one way I would like to get this work without upgrading dovecot. Many bugs were fixed since this version. That is likely Pigeonhole 0.4.2, which is very old (26-09-2013). The synchronization didn't work flawlessly until at least version 0.4.4, which goes with Dovecot 2.2.15. Regards, Stephan. Links: -- [1] http://www.dovecot.org/pipermail/dovecot/2014-December/099003.html
Re: Replication sieve scripts.
Op 19-7-2016 om 11:30 schreef Luescher Claude: Hello, Following up on old thread: http://www.dovecot.org/pipermail/dovecot/2014-December/099003.html I have the exact same issue with 2.2.10: It did not help. If there is one way I would like to get this work without upgrading dovecot. Many bugs were fixed since this version. That is likely Pigeonhole 0.4.2, which is very old (26-09-2013). The synchronization didn't work flawlessly until at least version 0.4.4, which goes with Dovecot 2.2.15. Regards, Stephan.
Replication sieve scripts.
Hello, Following up on old thread: http://www.dovecot.org/pipermail/dovecot/2014-December/099003.html I have the exact same issue with 2.2.10: ii dovecot-antispam 2.0+20130822-2amd64 Dovecot plugins for training spam filters ii dovecot-core 1:2.2.10-1amd64 secure POP3/IMAP server - core files ii dovecot-imapd 1:2.2.10-1amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-ldap 1:2.2.10-1amd64 secure POP3/IMAP server - LDAP support ii dovecot-lmtpd 1:2.2.10-1amd64 secure POP3/IMAP server - LMTP server ii dovecot-managesieved 1:2.2.10-1amd64 secure POP3/IMAP server - ManageSieve server ii dovecot-mysql 1:2.2.10-1amd64 secure POP3/IMAP server - MySQL support ii dovecot-pop3d 1:2.2.10-1amd64 secure POP3/IMAP server - POP3 daemon ii dovecot-sieve 1:2.2.10-1amd64 secure POP3/IMAP server - Sieve filters support As even his version should already support sieve replication through dsync mine would have to support it for sure but I would like to hear a confirmation from the developers. The mail sync just works perfectly between the 2 nodes, it is only the sieve scripts which don't get replicated. I have tried to add additional sieve related options to the replicator: service replicator { process_min_avail = 1 } plugin { mail_replica = tcp:1.2.3.4 replication_full_sync_interval = 1 hours #Added (makes no difference) sieve = ~/.dovecot.sieve sieve_dir = ~/sieve_after sieve_extensions = +vnd.dovecot.duplicate sieve_duplicate_period = 1h #Added (makes no difference) } service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } It did not help. If there is one way I would like to get this work without upgrading dovecot. Thank you.
dovecot --version tarball
Hi, Trying to understand what the version numbers mean. I typically build from the stable tarball and then apply patches as needed.. however since 2.2.25 this hasn't been working (not sure if it worked before or never really looked closely TBH). http://dovecot.org/releases/2.2/dovecot-2.2.25.tar.gz - shows GITID 7be1766 however it has commits / changes newer than this. Also the github tag for 2.2.25 is c1527e5 which doesn't match the source tarball as well. Should the source tarball and git commit hash be related? Thanks Leon