- dovecot - dovecot.org

autocreating folders with special chars stored in mysql-userdb
by Hajo Locke 03 Jul '15

03 Jul '15

Hello, i use dovecot 2.2.18 and do some tests with an utf8 mysqlbackend. I use MySQL to authenticate Users and for retrieving some individual settings like autocreating folders etc. by userdb-settings in user-query. Yet no problems with standard language. Now i try to provide userdb-settings in exotic languages. My MySQL table uses utf8 charset. I store some data in my userdb-column. Here an polish example: "namespace/inbox/mailbox=example namespace/inbox/mailbox/example/name=postępować namespace/inbox/mailbox/example/auto=subscribe" Result is a new folder in dovecot, but in client every special char ę and ć is replaced with a "?" I seems that at some point a conversion to latin1 is performed which ruins the utf8 chars. Creating a folder postępować by imap-client is no problem. Hmm, what should i do now? I dont know how to influence dovecot to process retrieved utf8 data furthermore as utf8. Which charset is using dovecot when connecting to mysqldb and how to take influence? Thanks, Hajo

1 1

the file dovecot-uidlist.lock appear then deadlock
by 刘莹莹 03 Jul '15

03 Jul '15

hi: sometimes i can't use imap command to get mails, when this problem appear i find out the file dovecot-uidlist.lock appear at the same time . I don't know Why is this happening ? can you help me ? thanks !

2 2

Dovecot auth username mapping
by Laz C. Peterson 02 Jul '15

02 Jul '15

I have an interesting case here … Virtual mailboxes, domain/username/aliases stored in MySQL, authentication done using PAM. PAM authenticates through Kerberos, which are internal realms and not the email domains — for example, my username would be laz(a)PARAVIS.LOCAL <mailto:laz@PARAVIS.LOCAL> and my email address would be laz(a)paravis.net <mailto:laz@paravis.net>. All of this works just fine. But what I want to do is allow the users to log in using their email address and not their full Kerberos name. It is becoming laborious to help the users understand the difference between their username(a)LOCAL.REALM and username(a)email.address <mailto:username@email.address> and why we have to have two separate identities that mean the same thing. I have the SQL statements to convert either the Kerberos login or the email address to the actual Kerberos login (so they may use either). But I cannot seem to figure out how to get Dovecot to acknowledge this as the mapped username. I’m sure there has to be a way. Any help will be greatly appreciated. Thank you! ~ Laz Peterson Paravis, LLC

4 7

Outlook 2013 not fetching new mail/synchronization issues
by Dragos Pacher 02 Jul '15

02 Jul '15

Hi all, Dovecot 2.2.10 CentOS 6 64 bit. We are having terrible synchronization issues with Outlook 2013 (all updates) on Windows 7 SP1 and 8.1 hosts (all updates). Scenario: 1. Emails were sent since user closed Outlook 2. Next day: start computer, open outlook 3. No new email (even though email were sent overnight) 4. half a day later Outlook fetches emails like nothing happened Second issue: folders created or email send in Outlook 2013 does not synchronize on IMAP, they remain only local .. But I am mostly interested into finding a fix for the first synchronization issue described in scenario. Second is also important but I have a feeling its connected to the first. Any help will be highly appreciated! dovecot.conf listen = * #base_dir = /var/run/dovecot # Enabled mail protocols. #protocols = pop3 imap sieve protocols = pop3 imap # User/group who owns the message files: mail_uid = 89 mail_gid = 89 # Assign uid to virtual users. first_valid_uid = 89 last_valid_uid = 89 mail_max_userip_connections = 200 default_client_limit = 3000 namespace inbox { separator = . prefix = INBOX. inbox = yes # These mailboxes are widely used and could perhaps be created automatically: mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Trash { special_use = \Trash } # For \Sent mailboxes there are two widely used names. We'll mark both of # them as \Sent. User typically deletes one of them if duplicates are created. mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } } # Logging. Reference: http://wiki2.dovecot.org/Logging log_path = /var/log/dovecot.log mail_debug = no auth_verbose = no auth_debug = no auth_debug_passwords = no auth_verbose_passwords = no auth_worker_max_count = 2048 # SSL: Global settings. # Refer to wiki site for per protocol, ip, server name SSL settings: # http://wiki2.dovecot.org/SSL/DovecotConfiguration ssl = yes verbose_ssl = no ssl_ca = </etc/ssl/savvy.cz-CA.pem ssl_cert = </etc/ssl/savvy.cz.crt ssl_key = </etc/ssl/savvy.cz.key disable_plaintext_auth = no # Mail location and mailbox format. #mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/ mail_location = maildir:~/Maildir:INDEX=/home/dovecotindex/%Lh/Maildir/ # Authentication related settings. # Append this domain name if client gives empty realm. auth_default_realm = # Authentication mechanisms. auth_mechanisms = PLAIN LOGIN service imap-login { client_limit = 3024 process_limit = 2048 process_min_avail = 64 vsz_limit = 64 M } service auth { client_limit = 3072 unix_listener auth-userdb { } inet_listener { port = 12345 } } service imap { vsz_limit = 256M # Max. number of IMAP processes (connections) process_limit = 2048 #imap_idle_notify_interval = 2 mins } service pop3 { # Max. number of POP3 processes (connections) process_limit = 1024 } # Virtual mail accounts. userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } plugin { auth_socket_path = /var/run/dovecot/auth-master # Plugin: autocreate. Create and subscribe to default IMAP folders. autocreate = INBOX autocreate2 = Sent autocreate3 = Trash autocreate4 = Drafts autocreate5 = Junk autosubscribe = INBOX autosubscribe2 = Sent autosubscribe3 = Trash autosubscribe4 = Drafts autosubscribe5 = Junk # Plugin: expire. expire = Trash 7 Trash/* 7 Junk 30 expire_dict = proxy::expire # Pigeonhole managesieve service. # Reference: http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration # Per-user sieve settings. sieve_dir = /%Lh/sieve sieve = /%Lh/sieve/dovecot.sieve # Global sieve settings. sieve_global_dir = /home/vpopmail/sieve sieve_global_path = /home/vpopmail/sieve/dovecot.sieve #sieve_before = #sieve_after = } service dict { unix_listener dict { # mode = 0660 # user = vmail # group = vmail } } protocol lda { # Reference: http://wiki2.dovecot.org/LDA #mail_plugins = quota sieve autocreate #auth_socket_path = /var/run/dovecot/auth-master #log_path = /var/log/sieve.log #lda_mailbox_autocreate = yes #postmaster_address = root } protocol imap { mail_max_userip_connections = 2048 imap_client_workarounds = tb-extra-mailbox-sep #mail_plugins = quota imap_quota autocreate #mail_plugins = autocreate } protocol pop3 { #mail_plugins = quota pop3_uidl_format = UID%u-%v pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } Regards, Pacher Dragos

3 12

duplicate namespace prefix
by jjhoffart 02 Jul '15

02 Jul '15

Hello, I am in the process of setting up a server that is running to invocations of dovecot. One of the invocations is acting as a backend and the other as a Director. I believe I have most of the configuration complete but I keep running into the following error: Jul 01 14:17:04 lda(postmaster(a)mydomain.com: Error: user postmaster(a)mydomain.com: Initialization failed: namespace configuration error: Duplicate namespace prefix: "" Jul 01 14:17:04 lda(postmaster(a)xn--mydomain-8za.com: Fatal: Invalid user settings. Refer to server log for more information. Not sure where to go from here and most of my searches on the error have lead me to dead ends hoping someone can help me out. Thanks.

3 2

Using PAM and passwdfile together
by Jim Garrison 02 Jul '15

02 Jul '15

Dovecot 2.0.9 on Centos 6.6 I have some local users and some Postfix virtual mailboxes. The config currently has: > # 2.0.9: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.32-504.12.2.el6.x86_64 x86_64 CentOS release 6.6 (Final) > first_valid_uid = 190 > log_path = /var/log/dovecot.log > mail_access_groups = mail > mail_location = mbox:~/mail:INBOX=/var/mail/%u > mbox_write_locks = fcntl > passdb { > driver = pam > } > passdb { > args = scheme=MD5 username_format=%u /etc/dovecot/auth/%d.passwd > driver = passwd-file > } > protocols = imap pop3 > ssl_ca = </etc/pki/tls/certs/ca-bundle.crt > ssl_cert = </etc/pki/dovecot/certs/mailcert.pem > ssl_key = </etc/pki/dovecot/private/mailkey.pem > ssl_parameters_regenerate = 48 > userdb { > driver = passwd > } > userdb { > args = uid=199 gid=199 home=/var/mail/vhosts/%d/%n mail=mbox:/var/mail/vhosts/%d/%n:INBOX=/var/mail/vhosts/%d/%n/mail > driver = static > } Each time a virtual mailbox user logs in, PAM writes a set of Authentication Failure messages to /var/log/secure when it attempts to find the virtual user, which it then successfully authenticates in the passwd-file. Is there a way to prevent PAM from loggin this spurious error and having dovecot log an authentication failure only if BOTH methods fail? -- Jim Garrison (jhg(a)acm.org) PGP Keys at http://www.jhmg.net RSA 0x04B73B7F DH 0x70738D88

2 1

dovecot-lmtp
by Steven Hopps 02 Jul '15

02 Jul '15

Hi, I'm trying to use dovecot-lmtp so that I can filter messages with sieve, however it doesn't appear to be working. I followed the instructions on wiki2.dovecot.org. I'm running Debian Wheezy. I've got runit configured to execute postfix and dovecot, which may be the source of the problem (runit executes /usr/sbin/dovecot -F). I've got mail_debug turned on and there is nothing in the mail log about lmtp. Any help would be appreciated. -- Steven Hopps || shopps(a)pridetechdesign.com 424-888-0443 || http://www.pridetechdesign.com = Ask about my Security Tune-Up & 24/7 Server Monitoring! =

2 4

Dovecot deleting files and directories
by Jan Ekholm 01 Jul '15

01 Jul '15

Hi, I’m a new Dovecot user and using version 2.2.18 on an OpenSuse system. In general it all works quite nicely and clients can connect to Dovecot and manage mails normally. The layout used is maildir. The users are all virtual, i.e. they do not exist on the Linux system. They all log in without any authentication due to a very specialized and internal setup. However, sometimes Dovecot simply deletes mails from the maildir structure. It also seems to delete entire users too. This is not a simple case of clients deleting mails, but the entire folder for the user seems to sometimes get nuked. I’ve also seen that only the mails and Dovecot’s admin files (indexes etc) are deleted. The log file is not really too informative, mostly lines of this form: Jul 01 14:00:36 imap(firstname.lastname(a)domain.x): Info: Disconnected: IMAP session state is inconsistent, please relogin. in=781 out=2630 Jul 01 14:00:36 imap(operators-east(a)east.domain.x): Debug: Namespace : /opt/mail/operators-east doesn't exist yet, using default permissions Jul 01 14:00:36 imap(operators-east(a)east.domain.x): Debug: Namespace : /opt/mail/operators-east doesn't exist yet, using default permissions Jul 01 14:00:36 imap(operators-east(a)east.domain.x): Debug: Namespace : Using permissions from /opt/mail/operators-east: mode=0700 gid=default Jul 01 14:00:36 imap(firstname.lastname(a)domain.x): Debug: Namespace : /opt/mail/firstname.lastname doesn't exist yet, using default permissions Jul 01 14:00:36 imap(firstname.lastname(a)domain.x): Debug: Namespace : /opt/mail/firstname.lastname doesn't exist yet, using default permissions Jul 01 14:00:36 imap(firstname.lastname(a)domain.x): Debug: Namespace : Using permissions from /opt/mail/firstname.lastname: mode=0700 gid=default Jul 01 14:01:03 imap-login: Info: Login: user=<firstname.lastname(a)domain.x>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=9326, secured, session=<2+YiPc4ZGwB/AAAB> Jul 01 14:01:03 imap(firstname.lastname(a)domain.x): Debug: Effective uid=1001, gid=100, home=/opt/mail/firstname.lastname Jul 01 14:01:03 imap(firstname.lastname(a)domain.x): Debug: maildir++: root=/opt/mail/firstname.lastname, index=, indexpvt=, control=, inbox=/opt/mail/firstname.lastname, alt= Jul 01 14:01:07 imap-login: Info: Login: user=<operators-east(a)east.domain.x>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=9333, secured, session=<11NpPc4ZHAB/AAAB> Jul 01 14:01:07 imap(operators-east(a)east.domain.x): Debug: Effective uid=1001, gid=100, home=/opt/mail/operators-east Jul 01 14:01:07 imap(operators-east(a)east.domain.x): Debug: maildir++: root=/opt/mail/operators-east, index=, indexpvt=, control=, inbox=/opt/mail/operators-east, alt= I’ve changed the name and domain. Not sure if the namespace complaints have anything to do with the directories on disk, but normally they are there when the logging comes. Below is the used config file. I can’t see anything that would trigger deletions and there is no logging or similar about it. To me it’s quite serious that an IMAP server randomly deletes mails and its own files. ########################################################################################### # support only IMAP, no pop3 protocols = imap # listen only on IPv4 (the default is: "* ::") listen = * # where logging gets sent log_path = /var/log/dovecot.log # disable SSL ssl = no disable_plaintext_auth = no # we're using maildir without any extra folders in the user's home directory (set in userdb) mail_location = maildir:~ # user ids default_login_user = dovenull default_internal_user = dovecot # auth config auth_verbose = yes auth_mechanisms = plain # password scheme. Uses an external Python application to verify the password. It gets # sent the username and password and can perform authentication. The current one # simply accepts anything. passdb { driver = checkpassword args = /opt/dovecot-2.2.18/bin/checkpassword.py } # user database userdb { driver = static args = uid=navie gid=users home=/opt/mail/maildir/%n } ########################################################################################### Anything obviously wrong? I’ve seen that mail_location and mail_home should not be the same, but using mail_location = maildir:~/mail gives the exact same behavior. Best regards, Jan Ekholm

2 1

LDAP default value variable interpolation
by Leon Kyneur 01 Jul '15

01 Jul '15

I'm wondering if there is a way I can dynamically generate an LDAP default value by using variables. I have a configuration that works something like this on my front end proxy: pass_attrs = mail=user,\ =nopassword=y,\ =proxy=y,\ =host=mail.%d The above works perfectly well even though it seems a bit hack. I want to fetch the host field from LDAP and default it to "mail.%d" if the attribute isn't populated for the user. I have tried the following : pass_attrs = mail=user,\ =nopassword=y,\ =proxy=y,\ =host=%{ldap:mailHost:mail.%d} however the interpolation doesn't occur on the default. Just wondering if there is a way to achieve this? thanks

2 2

Getting regularly mailbox desyncs while syncing with imapc
by Michael 30 Jun '15

30 Jun '15

Hello list! I sync approximately ~1000 Mailboxes actually without any problems, except my very own mailbox - Dovecot 2.2.18 (mdbox format) running here. The server from where I sync my mails from runs Dovecot 1.2.4 (with mbox format). The last log line that I receive is: dsync(ms(a)ddnetservice.de): Warning: Mailbox changes caused a desync. You may want to run dsync again. dovecot error log: 2015-06-30 13:09:50 imap(ms(a)ddnetservice.de): Error: Corrupted transaction log file /var/vmail/ddnetservice.de/ms/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.log seq 2: indexid changed 1435401731 -> 1435662589 (sync_offset=0) This is the command for running my syncs: doveadm -o imapc_user=<remote_user> -o imapc_password=<remote_pw> -o imapc_host=<remote_host> -o imapc_features="rfc822.size fetch-headers" -o mail_prefetch_count=20 -v -D sync -R -u<local_user> imapc: &> $LOGS/$BOX.log A re-run of this command for my mailbox doesn't fix the problem. The "Inbox" remains empty. Only a "doveadm force-resync -ums(a)ddnetservice.de" fixes this problem with the exception that the Inbox still remains empty. So after force-resyncing I need to run the sync again and my Inbox remains consistent until the next imapc sync run. Actually the desync message is self-explanatory, but I wonder why this behaviour only occurs for my own Inbox (only Inbox, other directories aren't affected) and not anywhere else. Is there any possiblity to debug this? Could also the amount of new incoming mails cause this or do I have maybe a bugged mail in my original mailbox that is causing my trouble? Any hint is appreciated. Thanks, Michael

1 0