- dovecot - dovecot.org

userdb lookup not possible with only userdb prefetch
by Yves Goergen 08 Dec '14

08 Dec '14

Hello, I am setting up a new server and migrating my Dovecot 1.2.9 config to the new 2.2.9 version. There wasn't much to keep from the old version so I had to recreate the config from scratch. Now I think I'm done but I can't login to IMAP. The log says this: > dovecot: auth: Error: prefetch(box@****.de,2001:****:7765,<bzAOP5QJXwAgAQpgEAXJAZyOMB1qBXdl>): userdb lookup not possible with only userdb prefetch > dovecot: auth: Error: userdb(box@****.de,2001:****:7765,<bzAOP5QJXwAgAQpgEAXJAZyOMB1qBXdl>): user not found from userdb prefetch > dovecot: imap: Error: Authenticated user not found from userdb, auth lookup id=178651137 (client-pid=13711 client-id=1) > dovecot: imap-login: Internal login failure (pid=13711 id=1) (internal failure, 1 successful auths): user=<box(a)****.de>, method=PLAIN, rip=2001:****:7765, lip=2a01:****:2, mpid=13717, TLS, session=<bzAOP5QJXwAgAQpgEAXJAZyOMB1qBXdl> That doesn't help me a lot. Here's parts of my configuration, dumped with 'dovecot -n': > # 2.2.9: /etc/dovecot/dovecot.conf > # OS: Linux 3.13.0-40-generic x86_64 Ubuntu 14.04.1 LTS > auth_mechanisms = plain login > disable_plaintext_auth = no > namespace inbox { > inbox = yes > location = > mailbox Drafts { > special_use = \Drafts > } > mailbox Junk { > special_use = \Junk > } > mailbox Sent { > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Trash { > special_use = \Trash > } > prefix = > } > passdb { > args = /etc/dovecot/dovecot-sql.conf.ext > driver = sql > } > plugin { > quota = maildir > } > protocols = imap pop3 > userdb { > driver = prefetch > } > protocol imap { > mail_max_userip_connections = 100 > mail_plugins = quota imap_quota > } What's the problem here? How can I resolve this issue? -- Yves Goergen http://unclassified.de http://dev.unclassified.de

4 4

Missing metadata on Dovecot 2.2.14, on Kolab 3.3, Centos 6.6
by Max Raafat 08 Dec '14

08 Dec '14

Hello everyone, We were trying to provision a system with Dovecot instead of another working cyrus kolab system. I am stuck with a problem with the metadata, especially when it comes to the Special Folders in Kolab 3.3, like Calenders, Tasks, etc, as well as any user created Folders. Emails work perfectly, and all the types are correct. But for example, If I try to change the type of Calenders, or create a new folder from inside roundcube and set it to type "Calenders", it stays at the default which is "mail". Therefore it causes problems, when sharing events, since they are displayed as "mail" type and not "event" type. We've tracked the problem down to the metadata not existing for special folders. A simple search only shows the default "mail" metadata, but nothing for shared folders, or special folders, etc. Here is the doveconf -n ------------------------------------------------------------------------------------------------------------- [root@m3 ~]# doveconf -n # 2.2.14: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-504.el6.x86_64 x86_64 CentOS release 6.6 (Final) imap_metadata = yes mail_attribute_dict = file:Maildir/dovecot-metadata mail_gid = 5000 mail_location = maildir:~/Maildir mail_plugins = " acl" mail_uid = 5000 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave mbox_write_locks = fcntl namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%u/ separator = / type = shared } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes pass = yes } passdb { driver = shadow } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes.db sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = vmail user = vmail } } service dict { unix_listener dict { group = vmail mode = 0666 user = vmail } } service lmtp { executable = lmtp unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve { address = 127.0.0.1 ::1 port = 4190 } } service managesieve { process_limit = 1024 } ssl = required ssl_cert = </etc/ssl/m3.company.includingchain.crt ssl_key = </etc/ssl/m3.company.de.key userdb { driver = passwd } userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol lmtp { mail_plugins = " acl sieve" } protocol lda { mail_plugins = " acl sieve" } protocol imap { mail_plugins = " acl imap_acl" } ------------------------------------------------------------------------------------------------------------ Would appreciate any help or ideas as to what I can do to fix this. Thanks Max

1 0

MD5-CRYPT/CRAM-MD5 vs SHA512-CRYPT/PLAIN
by ML mail 06 Dec '14

06 Dec '14

Hello, I am wondering which variant is more secure for user authentication and password scheme. Basically I am looking at both variants: 1) MD5-CRYPT password scheme storage with CRAM-MD5 auth mechanism 2) SHA512-CRYPT password scheme storage with PLAIN auth mechanism In my opinion the option 2) should be safer although it is using PLAIN auth mechanism. Of course I would always use STARTTLS and not allow unencrypted connection. What is your opinion? Best, ML

6 7

Size of array hosts, vhosts_count and modulo operation
by rub zorghy 05 Dec '14

05 Dec '14

Hi, Timo Sirainen wrote (May 19, 2010 1:50:34 am) : "When a connection from a newly seen user arrives, it gets assigned to a mail server according to a function: host = vhosts[ md5(username) mod vhosts_count ]" This hash function is it still used as it is without modification ? My another question sounds pretty innocent but I have doubts about vhosts_count. Taking two directors with three backend Dovecot as an example, the number of (v)hosts assigned for each host is "100" (default value of the vhost_count variable). I gather that the value for vhosts_count (to perform the modulo operation) and the size or length of the array (vhosts[]) in terms of number of elements are equal to 300. Thx so much. gdrub

1 0

doveadm backup gmail using imapc
by List 05 Dec '14

05 Dec '14

I am trying to sync a gmail inbox with dovecot 2.2.10 using the following config: imapc_host = 64.233.171.108 imapc_user = %u imapc_master_user = master imapc_password = secret imapc_features = rfc822.size imapc_features = $imapc_features fetch-headers mail_prefetch_count = 20 # If the old IMAP server uses INBOX. namespace prefix, set: #imapc_list_prefix = INBOX # for SSL: imapc_port = 993 imapc_ssl = imaps #imapc_ssl_ca_dir = /etc/ssl imapc_ssl_verify = no And the doveadm command: doveadm -D -o imapc_user=test(a)domain.tld -o imapc_password=password backup -R -x '\All' -x '\Flagged' -x '\Important' -u test(a)domain.tld imapc: I am getting the error: dsync(test(a)domain.tld: Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted. What I really want to do is just sync Gmail's inbox, drafts, sent, trash/archive, and spam folders to my new system. Is this possible using imapc?

1 0

Dovecot Director and Dovecot proxy
by rub zorghy 05 Dec '14

05 Dec '14

Hi, Dovecot Director is used to keep a temporary user -> Dovecot backend server mapping. So, Director decides which backend handles each user and the user is always redirected to the same server. All user data is stored in shared storage (NFS). The Dovecot presentation featured during this webinar <http://knowledgebase.open-xchange.com/fileadmin/user_upload/open-xchange/mi…> mentions (slide 7) a Dovecot proxy cluster (doing credentials and user info lookup) behind the LB device (F5 Big-IP) Why Dovecot Director server isn't used to perform this without Dovecot proxy ? Thus, the load balancer (F5 Big-IP) can distribute requests based on IMAP protocol to Dovecot Director cluster. Thx so much. gdrub

2 2

speed up doveadm search
by Vu Ngoc VU 05 Dec '14

05 Dec '14

Hello, I have recently migrated our mail accounts from old setup with courier-imapd to Dovecot 2. I thought that I can search quicky messages in mailboxes with doveadm because of indexes. Our users are asking (sometimes) to remove messages that they have sent wrongly. Some of them are coming from Exchange, and there is a feature in Outlook to recall (to delete) a message. So basically, they give me some infos (date, sender, subject) of message to remove. And I planned to do "doveadm search", then "doveadm fetch" and at last "doveadm expunge" on the found results. But it appears that the first run of doveadm is very slow. I don't know if it is because some indexes/caches are missing at this time. But when I run again same commands it is fast. Could you tell me if I speed up search on our maildir storage? I have no idea if I must manually (or with cron) run "doveadm index" on all our accounts because index/cache is only generated when users access their mailboxes. Or do I have to tune some settings like : mail_always_cache_fields, mail_cache_fields, mail_cache_min_mail_count, mail_never_cache_fields Thanks

1 0

does lda_save_to_detail_mailbox exist?
by A. Schulze 04 Dec '14

04 Dec '14

Hello, there is a nice feature in lmtp to save messages to user+foo@domain in INBOX/foo Looks like that doesn't work as good if lda is used. I have dovecot-2.2.13 mail_location = maildir:%h/ lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes *lmtp*_save_to_detail_mailbox = yes messages to user+foo generate an error and are saved to INBOX not matter if INBOX/foo exist or not: Dec 4 09:40:59 mail dovecot: lda(user(a)example.org): Debug: Effective uid=10020, gid=10020, home=/var/mail/user(a)example.org/ Dec 4 09:40:59 mail dovecot: lda(user(a)example.org): Debug: Destination address: user(a)example.org (source: user@hostname) Dec 4 09:40:59 mail dovecot: lda(user(a)example.org): msgid=<3jtWlm3FCHz52KG@localhost>: save failed to open mailbox foo: Mailbox can't be created Dec 4 09:40:59 mail dovecot: lda(user(a)example.org): msgid=<3jtWlm3FCHz52KG@localhost>: saved mail to INBOX # doveadm user -u user(a)example.org userdb: user(a)example.org home : /var/mail/user(a)example.org/ quota_rule: *:bytes=1000000 master_user: user(a)example.org # doveadm mailbox list -u user(a)example.org INBOX INBOX/bar Possible, that *lda*_save_to_detail_mailbox is simply not implemented? Thanks, Andreas

2 2

"maildir_empty_new = yes" not working
by Nikola Derikonjic 04 Dec '14

04 Dec '14

I need for my dovecot-uidlist to be updated with next id when new email arrives (moved from new/ to cur/). This only happens now when I check for new email with my client. Setting maildir_empty_new = yes is not working. Do I have to uncomment something else as well maybe? I want to do some proemial pipe lets say for 10 emails. All of them will have same UID since dovecot-uidlist is not updated. I am suing 2.2.13 dovecot on Gentoo 64bit. This is my dovecot -n: # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.5-gentoo x86_64 Gentoo Base System release 2.2 auth_mechanisms = plain login digest-md5 first_valid_gid = 500 last_valid_gid = 2000 last_valid_uid = 2000 login_greeting = Santa server is ready. mail_gid = vmail mail_location = /var/vmail/%d/%n/:INDEX=/var/vmail/%d/%n/indexes mail_uid = vmail maildir_empty_new = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave duplicate namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } ssl_ca = </etc/ssl/dovecot/server.in.crt ssl_cert = </etc/ssl/dovecot/server.csr.rapid ssl_key = </etc/ssl/dovecot/server.key.rapid ssl_key_password = notshown userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } -- Nikola Derikonjic Sent with Sparrow (http://www.sparrowmailapp.com/?sig)

2 2

Manual (file system level) message deletion
by absolutely_free＠libero.it 04 Dec '14

04 Dec '14

Hi,I use Dovecot + Postfix on CentOS server. I use maildir. What happen if I manually delete some messages (eg. the ones older than 6 months) for every use?I think that dovecot's indexes will be wrong... is this a potential performance issue?If so, how can I "rebuild" index file for every user? Thank you

2 1