- dovecot - dovecot.org

[Dovecot] Panic: file mailbox-list-maildir.c: line 133: unreached
by Raúl Massano Brás 07 Jan '14

07 Jan '14

Hi I am using dovecot 2.0.9 on CentOS 6.4 The following error appears in the logs when users connect to the imap server using MACs. All other clients that I tested work fine. ###### BEGIN ERROR ###### Jan 5 18:04:25 mail dovecot: imap(jcf): Panic: file mailbox-list-maildir.c: line 133: unreached Jan 5 18:04:25 mail dovecot: imap(user): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x3ca6a) [0x7f991df2ca6a] -> /usr/lib64/dovecot/libdovecot.so.0(+0x3cab6) [0x7f991df2cab6] -> /usr/lib64/dovecot/libdovecot.so.0(+0x16dba) [0x7f991df06dba] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x3eace) [0x7f991e1aface] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_list_is_valid_pattern+0x26) [0x7f991e1a4f86] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x3c861) [0x7f991e1ad861] -> /usr/lib64/dovecot/libdovecot-storage.so.0(fs_list_iter_next+0x2f) [0x7f991e1ad3ff] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_list_iter_next+0xa) [0x7f991e1a490a] -> dovecot/imap() [0x40b399] -> dovecot/imap(cmd_list_full+0x426) [0x40c246] -> dovecot/imap() [0x40f8cd] -> dovecot/imap() [0x40f9ba] -> dovecot/imap(client_handle_input+0x135) [0x40fbe5] -> dovecot/imap(client_input+0x5f) [0x41050f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x48) [0x7f991df37e08] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x9f) [0x7f991df38d7f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f991df37d98] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f991df26203] -> dovecot/imap(main+0x2f9) [0x418809] -> /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f991d76fcdd] -> dovecot/imap() [0x408229] ###### END ERROR ###### The dovecot configuration is: ###### BEGIN CONFIG ###### # dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-358.23.2.el6.x86_64 x86_64 CentOS release 6.4 (Final) disable_plaintext_auth = no mail_access_groups = mail mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u mbox_write_locks = fcntl namespace { hidden = yes inbox = yes list = yes location = mbox:~/mail:INBOX=/var/spool/mail/%u prefix = "#mbox/" separator = / type = private } namespace { location = maildir:~/Maildir prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } ssl_ca = </etc/pki/tls/certs/TERENA.crt ssl_cert = </etc/pki/tls/certs/mail.iseg.ulisboa.pt.crt ssl_key = </etc/pki/tls/private/mail.iseg.ulisboa.pt.key syslog_facility = local0 userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } ###### END CONFIG ###### I don't know what to do to allow MAC users to use the system. Can anyone help? Thank you, -- Raúl Brás Instituto Superior de Economia e Gestão Universidade de Lisboa

2 2

[Dovecot] using OR in doveadm search query
by W. de Hoog 07 Jan '14

07 Jan '14

Hi, I am trying to create an OR query but no success yet: $ doveadm search mailbox shared/* OR SUBJECT "a" SUBJECT "b" doveadm(neil): Fatal: Use parenthesis when mixing ANDs and ORs $ doveadm search mailbox shared/* OR $SUBJECT "a"$ $SUBJECT "b"$ doveadm(neil): Fatal: Unknown argument (SUBJECT $ doveadm search mailbox shared/* $OR \(SUBJECT "a"$ $SUBJECT "b"$\) doveadm(neil): Fatal: Unknown argument (OR What is the correct syntax for such a query? -- Willem-Jan de Hoog

2 2

[Dovecot] What's the parameter -w for dovecot-auth: dovecot -w
by ldaamandy 07 Jan '14

07 Jan '14

hello: What's the parameter -w for dovecot-auth: dovecot -w my service of dovecot-auth always activing two: one is" dovecot-auth" , the other is" dovecot-auth -w" i don't know the diffevent between them amandy thanks!

2 4

[Dovecot] need assistance migrating between apple servers
by Raymond Norton 06 Jan '14

06 Jan '14

I am attempting to move imap folders from an Apple Snow Leopard server to a new Apple Mavericks server. Dovecot --version is not working , but I believe the old server is running dovecot 1.1.2 and can confirm the new one is running 2.2.x. I have tried taring and moving folders, but have not been able to get the transfered messages and folders to show up in user accounts (new messages show up fine). I have attempted to recreate index files, but that has not worked either. The last attempt I made to migrate was to use dsync, but it does not exist on the old server and I do not see a way to install it. What method would work best to migrate or move files and folders from the old server and get them to show up for clients on using the new server? -- Raymond Norton LCTN 952.955.7766 Sent from My Desktop

2 1

[Dovecot] virtual mailboxes folder structure
by Marco Cusano 06 Jan '14

06 Jan '14

Hi, I am trying to find a way to list my virtual mailboxes hiding the namespace prefix into my imap client. Fore example now my “All” mailbox is listed under virtual/ as: Inbox Sent Drafts Spam Trash virtual All I would like to list as this: Inbox Sent Drafts Spam Trash All This is my 10-mail.conf: http://pastebin.com/DumEbbmy and this is my 15-mailboxes.conf: http://pastebin.com/QFzWGzyC I thought that the list = children paramenter would do but it did not. Thank you

1 0

[Dovecot] virtual mailboxes folder structure
by Marco Cusano 06 Jan '14

06 Jan '14

Hi, I am trying to find a way to list my virtual mailboxes hiding the namespace prefix into my imap client. Fore example now my “All” mailbox is listed under virtual/ as: Inbox Sent Drafts Spam Trash virtual All I would like to list as this: Inbox Sent Drafts Spam Trash All This is my 10-mail.conf: http://pastebin.com/DumEbbmy and this is my 15-mailboxes.conf: http://pastebin.com/QFzWGzyC I thought that the list = children paramenter would do but it did not. Thank you

1 0

[Dovecot] [SIEVE] Locking Errors with vnd.dovecot.duplicate Extension
by Daniel Parthey 06 Jan '14

06 Jan '14

Hi, we are running a 4 host setup which each hosts a director+mailbox which is mounted via NFSv4 from a DRBD cluster. * Dovecot upstream release 2.1.16 * Doveadm batch subcommand fix - http://hg.dovecot.org/dovecot-2.1/raw-rev/850b5d8bbcc9 * Pigeonhole release 0.3.4 Now we would like to remove duplicate Mails using the vnd.dovecot.duplicate extension using a SIEVE script like this: require ["vnd.dovecot.duplicate", "fileinto", "mailbox", "regex", "vacation", "variables"]; if duplicate { fileinto :create "Trash"; } But as soon as we start delivering duplicate mails, we're sometimes getting locking errors from the mailbox (which is responsible for the user) according to the director: Dec 27 16:36:30 10.129.3.213 dovecot: lmtp(27975, user001(a)example.org) Error: Creating lock file for /mail/dovecot/example.org/user001/.dovecot.lda-dupes timed out in 20 secs Dec 27 16:36:33 10.129.3.213 dovecot: lmtp(27987, user001(a)example.org) Error: Creating lock file for /mail/dovecot/example.org/user001/.dovecot.lda-dupes timed out in 20 secs Dec 27 16:36:35 10.129.3.213 dovecot: lmtp(27994, user001(a)example.org) Error: Creating lock file for /mail/dovecot/example.org/user001/.dovecot.lda-dupes timed out in 20 secs Dec 27 16:36:36 10.129.3.213 dovecot: lmtp(28011, user001(a)example.org) Error: Creating lock file for /mail/dovecot/example.org/user001/.dovecot.lda-dupes timed out in 20 secs Dec 27 16:36:36 10.129.3.213 dovecot: lmtp(28013, user001(a)example.org) Error: Creating lock file for /mail/dovecot/example.org/user001/.dovecot.lda-dupes timed out in 20 secs Dec 27 16:36:38 10.129.3.213 dovecot: lmtp(28017, user001(a)example.org) Error: Creating lock file for /mail/dovecot/example.org/user001/.dovecot.lda-dupes timed out in 20 secs Dec 27 16:36:39 10.129.3.213 dovecot: lmtp(28025, user001(a)example.org) Error: Creating lock file for /mail/dovecot/example.org/user001/.dovecot.lda-dupes timed out in 20 secs Dec 27 16:36:42 10.129.3.213 dovecot: lmtp(28037, user001(a)example.org) Error: Creating lock file for /mail/dovecot/example.org/user001/.dovecot.lda-dupes timed out in 20 secs Dec 27 16:36:43 10.129.3.213 dovecot: lmtp(27973, user001(a)example.org) Error: Creating lock file for /mail/dovecot/example.org/user001/.dovecot.lda-dupes timed out in 20 secs Configs and Error log is attached. Any idea how to mitigate these locking issues? Regards Daniel

1 0

[Dovecot] disable_plaintext_auth = yes not showing in doveconf -n output?
by Charles Marcus 04 Jan '14

04 Jan '14

I have it set, but it doesn't show up. However, I noticed that it does show as enabled by default in doveconf -a output. Is this why it doesn't show up in doveconf -n output? -- Best regards, Charles

4 5

[Dovecot] RFE: IMAP LIST Extension for Special-Use Mailboxes
by Patrick Ben Koetter 03 Jan '14

03 Jan '14

Timo, would you consider adding support for "IMAP LIST Extension for Special-Use Mailboxes" <http://www.rfc-editor.org/rfc/rfc6154.txt> any time near in the future? I would really love to get rid of all those folders created by all those different mail clients just because they can't agree to use the same folder for special purpose. Obviously clients need to support it too. Having Dovecot support it certainly would make them adopt the standard sooner. p@rick -- state of mind Digitale Kommunikation http://www.state-of-mind.de Franziskanerstraße 15 Telefon +49 89 3090 4664 81669 München Telefax +49 89 3090 4666 Amtsgericht München Partnerschaftsregister PR 563

10 17

[Dovecot] Allow both SSL/993 and STARTTLS/143 connections (secure only)
by Charles Marcus 03 Jan '14

03 Jan '14

Hi all, Ok, up until now, I've only always allowed IMAPS connections to dovecot on port 993. I want to also start allowing clients to user port143+STARTTLS, but I walso want to make sure both ports are locked down to ONLY allow secure connections. So... is disable_plaintext_auth = yes in the main config enough to accomplish this? http://wiki2.dovecot.org/SSL/DovecotConfiguration says: There are a couple of different ways to specify when SSL/TLS is required: * disable_plaintext_auth=yes allows plaintext authentication <http://wiki2.dovecot.org/Authentication/Mechanisms> only when SSL/TLS is used first. * ssl = required requires SSL/TLS also for non-plaintext authentication <http://wiki2.dovecot.org/Authentication/Mechanisms>. * If you have only plaintext mechanisms enabled (auth { mechanisms = plain login } ), you can use either (or both) of the above settings. They behave exactly the same way then and the comments in 10-auth.conf say: # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that if the remote IP # matches the local IP (ie. you're connecting from the same computer), the # connection is considered secure and plaintext authentication is allowed. # See also ssl=required setting. #disable_plaintext_auth = yes These seem to be saying that all I need to do is set either or both (ssl-required and/or disable_plaintext_auth=yes). I'm looking for the simplest, and don't like redundant/unnecessary settings, so... which is the best/preferred way? And what is the difference between ssl=required and disable_plaintext_auth=yes? Thanks, -- Best regards, */Charles/***

2 3