- dovecot - dovecot.org

userdb / user map with director
by Will Yardley 10 Aug '15

10 Aug '15

This is with dovecot-ee 2.2.18.2 on RHEL6.... To handle backend and frontend on same machine, I'm using the following hack, as previously outlined here: [in director instance config] passdb { # See thread ending in: # http://dovecot.org/pipermail/dovecot/2012-June/083817.html # for why this has to be sql instead of 'static' driver = sql args = /etc/dovecot/dovecot-sql.conf } [in /etc/dovecot/dovecot-sql.conf] driver = sqlite connect = /etc/dovecot/empty.db password_query = select 'y' as proxy, \ NULL as password, \ 'y' as nopassword, \ case '%a' \ when '110' then '10110' \ when '995' then '10110' \ when '143' then '10143' \ when '993' then '10143' end \ as port; This works, but I was getting a failure on usernames, since director instance didn't have a userdb. So I tried the following: [in config] passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf } userdb { driver = prefetch } and appended the following to the SQL query: password_query = select '%u' AS user, \ Then I see the following error in the log when I try to run the map "Trying to iterate users, but userdbs don't support it" and doveadm -i director director map returns: Error: User listing returned failure Error: user listing failed [...] I'm sure I'm missing something obvious, so is there an easy fix to make this mapping work? w

1 0

Dovecot sends "OK Logged in" with empty tag
by Simon Thelen 10 Aug '15

10 Aug '15

Hello, I'm currently writing my own IMAP client and testing it against Dovecot, and when doing PLAIN AUTH Dovecot sends the "OK Logged in" with an empty tag at the start. I tried reproducing the conversation with netcat, but Dovecot sends a correctly tagged OK at the end of the AUTH so I assume it's timing related. I've attached pcap dumps of the TCP conversation in both situations as well as the output of dovecot -n. Side Note: Why does Dovecot send the updated capabilities before OK'ing the authentication? Seems strange to me as the client can't assume that the authentication proceeded successfully until it actually receives the OK so it has to assume that those capabilities are pre login. -- Simon Thelen

1 1

Using a separate passdb per service
by Gerry 10 Aug '15

10 Aug '15

Situation: one front-facing server running Dovecot as IMAP/POP3/ ManageSieve proxy, a mixture of IMAP servers (Dovecot, Exchange, ...) in the back-end. Dovecot's passdb does lookups against MySQL which contains a simple user/host mapping, the actual authentication happens on the back-end IMAP servers. The configuration is more or less as described here: http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy Now I would like to add a Postfix instance on the front-facing server which listens on the submission port and authenticates users via SASL using the local Dovecot's UNIX socket. The idea being that a user only needs to remember one single hostname, one username and one password for all mail-related services. The problem is that Dovecot is operating in proxy mode, which means that the password_query returns NULL as the password and explicitly returns a field "nopasswd" containing "Y". Thus, users can not authenticate against the UNIX socket. What I think I want to do is convince Dovecot to use one passdb for the imap/pop3/managesieve services and different one for the "auth" service. The configuration snippet below doesn't work, but it should illustrate what I want to achieve: > protocols = imap pop3 sieve > > service auth { > passdb sql { > driver = sql > args = /etc/dovecot/mysql-auth-sasl.conf.ext > } > > unix_listener /var/spool/postfix/private/auth { > user = postfix > group = postfix > mode = 0666 > } > } > > # IMAP/POP3/ManageSieve auth against MySQL > passdb sql { > driver = sql > args = /etc/dovecot/mysql-auth-default.conf.ext > } Example mysql-auth-sasl.conf.ext > driver = mysql > connect = host=127.0.0.1 dbname=mail user=mail password=somethingrandom > password_query = SELECT password AS password FROM users WHERE login = '%u' Example mysql-auth-default.conf.ext: > driver = mysql > connect = host=127.0.0.1 dbname=mail user=mail password=somethingrandom > password_query = SELECT NULL AS password, 'Y' as nopassword, host, 'Y' AS proxy FROM users WHERE login = '%u' Any pointers? Gerry

3 4

How to import an mbox to an existing user as a new mailbox
by Paul Hoffman 09 Aug '15

09 Aug '15

Greetings. I have a bunch of mbox files that I want to import to an existing user, each into a new mailbox. That is, I want to import the file project1.mbox to user Foo, into a newly-created mailbox called "Project 1". Is there a dovecot tool to do this on the server? --Paul Hoffman

4 10

Trying to back
by Kevin Laurie 09 Aug '15

09 Aug '15

Hi, I am trying to backup multiple mail accounts by using imapsync and Dovecot on my local machine. I am using maildir as a mail storage format and currently have the following setting on my local machine :- mail_location = maildir:~/Maildir I am afraid that if I imapsync multiple accounts they will all get stored in the same location. Is there a way to seperate the accounts based on the email address? Appreciate if someone could advise. Thanks! Kevin

3 3

2.2.18: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted.
by Dale Gallagher 08 Aug '15

08 Aug '15

Hello I have 2.2.18 built with: ./configure \ --prefix="$prefix" \ --bindir="$prefix/bin" \ --sbindir="$prefix/bin" \ --sysconfdir="/etc" \ --with-storages="maildir,imapc,pop3c" \ --without-vpopmail \ --without-ldap I'm attempting to sync (backup) from another Dovecot server running version 2.0.21: Both servers don't have no explicit namespaces configured and both are using the Maildir storage plugin. doveadm -Dv -o imapc_user=remote_user -o imapc_host=source.host -o imapc_port=993 -o imapc_ssl=imaps -o imapc_password=remote_pass -o imapc_features="rfc822.size fetch-headers" backup -R -u local_user imapc: All seems to go well, showing local and remote mailbox syncing without errors, then finally: dsync(mcg): Debug: brain M: Deleting mailbox 'INBOX' (GUID 59023c2a911dc255842b0000d09efc50): UIDVALIDITY changed (1355416734 -> 1438784913) dsync(mcg): Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted. No mail is synced to the local server (2.2.18) after this error halts execution. What should I be looking for, in terms of possible causes of this error? I've tried syncing on a completely fresh mailbox, which hasn't been accessed by a mail client and the same error occurs. I've seen similar reports of this error before, without clear solutions / suggestions. Help would be greatly appreciated. Thanks

1 2

opening a maildir ?
by Kevin Laurie 07 Aug '15

07 Aug '15

Hello, I have a maildir on my Ubuntu PC. I used imapsync + dovecot to copy all my emails on it. What would be a convenient way to access all the emails ( I want to go through and download all attachments). So a tool with some GUI will be nice. Appreciate if someone could help here. Thanks Kevin

2 1

Dovecot under Linux with mail-extension and case insesitiv
by Sascha 06 Aug '15

06 Aug '15

Hello, i use doevecot 2.2.18 current. My Problem is with email-extension and case sensitiv folders. Example: user+extenstion will be delivered to the user and subfolder extenstion so this is okay. but user+extenstion will not be delivert to the user and exiting subfolder Extenstion so that is not okay. The mail will be also delivered in the subfolder extension. The exiting Folder Extension will not used. Give's a way to tell dovecot, use the extension as a Folder, if a exiting folder with Upper/Lower Cases will be detect and use the right folder to delivery? -- Regards Sascha --- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus

6 7

Dovecot/Pigeonhole Issue (UTC modtime instead of localtime)
by Christoph Gröver 06 Aug '15

06 Aug '15

Hi List, We are using the following setup: Dovecot-2.2.18 Pigeonhole-0.4.8 (for Dovecot-2.2) After the mail is finally delivered via a fileinto by the Sieve filter it gets an updated timestamp (modification time). The server has localtime setup correctly IMO (UTC +0200), but still the delivered mail is setup as being two hours old. I think I found out that the function sieve_file_storage_update_mtime() is the cause of this problem. But perhaps there has to be some kind of setup, that tells pigeonhole to use the 2 hour offset of CEST. I think to reset the mtime by utime(s) is a bit strange. It already gets the correct modtime just by storing it in the filesystem. Last version we used (0.2.5) did not have this poblem. So it must be there for some reason? Perhaps you can enlighten me. Thanks for your time. Greetings -- Sitepark Gesellschaft für Informationsmanagement mbH Rothenburg 14-16, 48143 Münster Telefon: +49 251 482655-0, Telefax: +49 251 482655-55 http://www.sitepark.com http://www.facebook.com/sitepark Geschäftsführer: Thorsten Liebold Amtsgericht Münster, HRB 5017

2 5

Dovecot sieve pigeonhole permission
by Gerhard Wiesinger 05 Aug '15

05 Aug '15

Hello, I'm running dovecot in a classical vmail.vmail setup with pigeonhole and LMTP. Permission worked well in the initial setup but currently (maybe after Fedora 22 update) I'm having the following permission issue: lmtp(root): Error: 7fPZFOL9wFXePQAABcdabc: sieve: binary open: failed to open: open(/etc/dovecot/sieve_after.svbin) failed: Permission denied (euid=9999(vmail) egid=9999(vmail) missing +r perm: /etc/dovecot/sieve_after.svbin, we're not in group 0(root), dir owned by 0:0 mode=0755) lmtp(root): Error: 7fPZFOL9wFXePQAABcdabc: sieve: binary save: failed to create temporary file: open(/etc/dovecot/sieve_after.svbin.myserver.mydomain.15838.) failed: Permission denied (euid=9999(vmail) egid=9999(vmail) missing +w perm: /etc/dovecot, dir owned by 0:0 mode=0755) lmtp(root): Error: 7fPZFOL9wFXePQAABcdcbc: sieve: The LDA Sieve plugin does not have permission to save global Sieve script binaries; global Sieve scripts like `/etc/dovecot/sieve_after.sieve' need to be pre-compiled using the sievec tool rpm -V dovecot dovecot-pigeonhole doesn't report any permission issues Versions: dovecot-2.2.18-2.fc22.x86_64 dovecot-pigeonhole-2.2.18-2.fc22.x86_64 Relevant config parts: mail_gid = vmail mail_uid = vmail plugin { sieve = ~/.dovecot.sieve sieve_after = /etc/dovecot/sieve_after.sieve sieve_dir = ~/sieve } ls -lad /etc/dovecot/ drwxr-xr-x. 3 root root 4096 Jul 30 18:13 /etc/dovecot/ ls -la /etc/dovecot/*sieve* -rwxr-x--- 1 vmail vmail 288 Aug 8 2014 /etc/dovecot/sieve_after.sieve -rw-r----- 1 root root 355 Jul 30 18:13 /etc/dovecot/sieve_after.svbin What's are the recommended permissions for the files/directories (also for root service startup of dovecot)? Did something change in permissions management? Thanx. Ciao, Gerhard -- http://www.wiesinger.com/

2 3