- dovecot - dovecot.org

Trouble getting listescape plugin to work with "$" separator (as demonstrated in Wiki) in Dovecot 2.2.9
by Ben Johnson 03 Oct '14

03 Oct '14

Hello, I'm attempting to install the listescape plugin so that IMAP users are able to include periods (.) and forward slashes (/) in IMAP directory names. I'm following the instructions at http://wiki2.dovecot.org/Plugins/Listescape , which imply that this can be accomplished by enabling the listescape plugin and using the dollar sign ($) as the separator. With regard to my dovecot configuration, first, I changed protocol imap { mail_plugins = quota imap_quota antispam } to protocol imap { mail_plugins = quota imap_quota antispam listescape namespace private { separator = $ inbox = yes } } When I start dovecot, I receive the following error: doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:102: namespace private {} has been replaced by namespace { type=private } Pretty straightforward; I made the required change to yield protocol imap { mail_plugins = quota imap_quota antispam listescape namespace { type = private separator = $ inbox = yes } } But now, when I attempt to start dovecot, I receive the following error: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 104: Unknown variable: $ doveconf: Error: managesieve-login: dump-capability process returned 89 doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 104: Unknown variable: $ Is it possible that the instructions at the Wiki 2 URL cited above are out-of-date? If I try to escape the $ with any other character (I'm just shooting in the dark regarding possible escape characters, as I cannot find definitive documentation that pertains to escaping $ in the dovecot configuration), I receive yet another error: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: Namespace '': Hierarchy separator must be only one character long doveconf: Error: managesieve-login: dump-capability process returned 89 doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: Namespace '': Hierarchy separator must be only one character long Ultimately, I have two questions: 1.) Is the nesting structure that I've employed correct? The Wiki 2 page is not clear with regard to the nesting; is it correct to put the "namespace" block inside the "protocol imap" block, as I demonstrated above? 2.) Is it possible to escape the dollar sign so that it can be used as the separator? Full "doveconf -n" output is included below. Thanks for any assistance, -Ben # doveconf -n # 2.2.9: /etc/dovecot/dovecot.conf doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 104: Unknown variable: $ doveconf: Error: managesieve-login: dump-capability process returned 89 # OS: Linux 3.13.0-34-generic x86_64 Ubuntu 14.04.1 LTS auth_mechanisms = plain login disable_plaintext_auth = no listen = *,[::] log_timestamp = "%Y-%m-%d %H:%M:%S " mail_debug = yes mail_privileged_group = vmail passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { antispam_backend = pipe antispam_debug_target = syslog antispam_pipe_program = /bin/bash antispam_pipe_program_args = /usr/local/bin/sa-learn-pipe.sh antispam_pipe_program_notspam_arg = --ham antispam_pipe_program_spam_arg = --spam antispam_pipe_tmpdir = /tmp antispam_spam_pattern_ignorecase = SPAM;JUNK antispam_trash_pattern_ignorecase = trash;Deleted * antispam_verbose_debug = 1 quota = dict:user::file:/var/vmail/%d/%n/.quotausage quota_rule2 = Trash:storage=+100M quota_rule3 = Junk:ignore quota_rule4 = INBOX:storage=+100M quota_warning = storage=100%% quota-reached 100 %u %d quota_warning2 = storage=95%% quota-warning 95 %u %d quota_warning3 = storage=80%% quota-warning 80 %u %d quota_warning4 = -storage=100%% quota-below below %u %d sieve = /var/vmail/%d/%n/.sieve } postmaster_address = postmaster(a)localhost.com protocols = imap pop3 sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } user = root } service config { unix_listener config { group = vmail mode = 0600 user = vmail } } service imap-login { client_limit = 1000 process_limit = 500 } service quota-below { executable = script /usr/local/bin/quota-below.sh unix_listener quota-below { group = vmail mode = 0666 user = vmail } user = vmail } service quota-reached { executable = script /usr/local/bin/quota-reached.sh unix_listener quota-reached { group = vmail mode = 0666 user = vmail } user = vmail } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { group = vmail mode = 0666 user = vmail } user = vmail } ssl_cert = </etc/postfix/smtpd.cert ssl_key = </etc/postfix/smtpd.key userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = quota imap_quota antispam listescape namespace { inbox = yes location = prefix = separator = $ type = private } } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol lda { info_log_path = log_path = mail_plugins = sieve quota }

2 3

auth with entire email addr instead of just username
by Cliff Hayes 03 Oct '14

03 Oct '14

I am trying to configure a new IMAP based mail server. I thought I had everything correct. I have dovecot logging turned up and see that dovecot is processing the entire email address as the username like this... Oct 2 14:52:20 servername dovecot: auth: Debug: pam(testuser(a)domain.com,1.2.3.4): lookup service=dovecot ... and of course pam is reporting that as an invalid user. Moments ago when all was mbox, authentication worked fine. I can see Thunderbird has the username correct (no domain). What is tacking on the domain and how do I fix? Thanks in advance.

2 4

two dovecot instances
by jjhoffart 02 Oct '14

02 Oct '14

Hello, I am currently trying to setup two invocations of dovecot to run on a debian based server. One for director and the other a stock debian instance. The issue I am having is when I go to start the director instance, I receive multiple errors telling me that the listening ports are already in use. I have change these ports in the 10-master.conf file but am still presented with the same errors when starting the second instance. Is this the only file in which the ports need to be changed (10-master.conf) or is there another file in which the ports need to be set?

2 1

Re: Simply mysql quota check
by Alfredo Saldanha 02 Oct '14

02 Oct '14

Steffen, My problem was exactly what you said, the quota field in my query. I fixed it and now is working very well. Thank you very much. Alfredo ----- Mensagem original ----- De: "Steffen Kaiser" <skdovecot(a)smail.inf.fh-brs.de> Para: "Alfredo Saldanha" <asaldanha(a)infolink.com.br> Cc: dovecot(a)dovecot.org Enviadas: Quinta-feira, 2 de outubro de 2014 3:33:13 Assunto: Re: Simply mysql quota check -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 1 Oct 2014, Alfredo Saldanha wrote: > #/etc/dovecot/dovecot-sql.conf.ext > password_query = \ > SELECT username AS user, value AS password \ > FROM mailboxes WHERE username = '%n@%d' > > user_query = \ > SELECT username, domain, \ > CONCAT('*:storage=', SUBSTRING_INDEX(quota, 'm', 1)*1048576) AS userdb_quota_rule \ > FROM mailboxes, domains WHERE mailboxes.username = '%n@%d' \ > AND domains.domain = '%d' > > My idea is when a message is delivered, the dovecot to check quota in the mysql according to the value received in the "user_query" but he does not. > It shows a value of 2GB that I don't know where it gets. > > I execute a manual query in mysql to know the quota my test user and checked that are 5GB, but when I see the dovecot, it shows 2G. > > SELECT username, domain, CONCAT('*:bytes=', SUBSTRING_INDEX(quota, 'm', 1)*1048576) AS userdb_quota_rule > FROM mailboxes, domains WHERE mailboxes.username = 'junix(a)domain.com' AND domains.domain = 'domain.com' 1) your manual query uses '*:bytes=', whereas your conf uses '*:storage='. 2) you return the value as userdb_quota_rule, but it must read quota_rule in the user_query. In the password_query fields are prefixed by userdb_ . See http://wiki2.dovecot.org/Quota/Configuration - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBVCzxqnz1H7kL/d9rAQIneAgAukcibxJoQdtwdmrxHbXmKgQsCG22itH5 9VSFGigiPjXg/F1hkj7jHC/xB5uh2M8ayMos+hPxaJkKC4AKYEZu1QEwXAX2qrvN DXt7uPZHLJSMtlWCVb5s6h+v6K3JnbWRrjI4CIfYqB8i8MHKBWei0K02QZcOUOfy KeD7lAIPRuZPnIEiWYREpalRMGeQzZ69SHEmhxDx7VFO5FanlHDxdCwmO7qHoJen ZuNpUWMf5i5czxcDhHjLdtGODv005LFDCXhj48SqI17WzD3mPjJegOCjym6RfKmU RT+PtKieBkzygT1YzvjJbHISFxJSryVg8c48tCb0FgjkNKWXq/KsPg== =wzY8 -----END PGP SIGNATURE-----

1 0

Simply mysql quota check
by Alfredo Saldanha 02 Oct '14

02 Oct '14

Hi there, I'm setting up a new email server with Dovecot(2.2.9) and MySQL. My Dovecot configuration: #/etc/dovecot/conf.d/90-quota.conf service quota-warning { executable = script /usr/local/bin/quota-warning.sh user = dovecot unix_listener quota-warning { user = vmail } } plugin { quota = maildir:User quota quota_warning = storage=95%% quota-warning 95 %u@%d quota_warning2 = storage=80%% quota-warning 80 %u@%d args = /etc/dovecot/dovecot-sql.conf.ext } #/etc/dovecot/dovecot-sql.conf.ext password_query = \ SELECT username AS user, value AS password \ FROM mailboxes WHERE username = '%n@%d' user_query = \ SELECT username, domain, \ CONCAT('*:storage=', SUBSTRING_INDEX(quota, 'm', 1)*1048576) AS userdb_quota_rule \ FROM mailboxes, domains WHERE mailboxes.username = '%n@%d' \ AND domains.domain = '%d' My idea is when a message is delivered, the dovecot to check quota in the mysql according to the value received in the "user_query" but he does not. It shows a value of 2GB that I don't know where it gets. I execute a manual query in mysql to know the quota my test user and checked that are 5GB, but when I see the dovecot, it shows 2G. SELECT username, domain, CONCAT('*:bytes=', SUBSTRING_INDEX(quota, 'm', 1)*1048576) AS userdb_quota_rule FROM mailboxes, domains WHERE mailboxes.username = 'junix(a)domain.com' AND domains.domain = 'domain.com' +-------------------+----------------+--------------------+ | username | domain | userdb_quota_rule | +-------------------+----------------+--------------------+ | junix(a)domain.com | domain.com | *:bytes=5242880000 | +-------------------+----------------+--------------------+ $ sudo doveadm quota get -u junix Quota name Type Value Limit % User quota STORAGE 10 2097152 0 User quota MESSAGE 1 - How would the setting to simply verify the quota of users as userdb_quota_rule this query? BR, Alfredo Jr.

2 1

Dovecot fails to start - Unknown setting: socket
by Max Shortte 02 Oct '14

02 Oct '14

I’m receiving the following error(s) messages when trying reloading dovecot (Debian wheezy). doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 73: Unknown setting: socket doveconf: Error: managesieve-login: dump-capability process returned 89 Configuration file /etc/dovecot/dovecot.conf : # If you only want to use dovecot-auth, you can set this to "none". protocols = imap sieve log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/var/mail/%d/%n:INDEX=/var/mail/indexes/%d/%n mail_privileged_group = vmail mail_debug = no first_valid_uid = 5000 last_valid_uid = 5000 maildir_copy_with_hardlinks = yes mail_chroot = yes default_login_user = dovecot ssl_cert = /etc/ssl/certs/star_palibrary_org_combined.crt ssl_key = /etc/ssl/private/star_palibrary_org.key protocol imap { # imap_client_workarounds = outlook-idle delay-newmail } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } ## ## MANAGESIEVE specific settings ## protocol sieve { } plugin { sieve_storage = ~/sieve sieve_global_path = /var/vmail/globalsieverc sieve = ~/dovecot.sieve } protocol lda { #log_path = /var/vmail/dovecot-deliver.log auth_socket_path = /var/run/dovecot/auth-master postmaster_address = shortte(a)mvs.org mail_plugins = sieve } ################################### ## ## LDA specific settings ## auth_default_realm = mvs.org auth_debug = no auth_debug_passwords = no auth_mechanisms = auth_plain auth_login auth_digest-md5 auth_cram-md5 # dovecot-auth only needs to be able to connect to SQL # default_login_user = mail passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf.ext } userdb { driver= sql args = /etc/dovecot/dovecot-sql.conf.ext } socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail group = vmail } client { # The client socket is generally safe to export to everyone. Typical use # is to export it to your SMTP server so it can do SMTP AUTH lookups # using it. path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } Packages: ii dovecot-common 1:2.1.7-7+deb7u1 ii dovecot-core 1:2.1.7-7+deb7u1 ii dovecot-gssapi 1:2.1.7-7+deb7u1 ii dovecot-imapd 1:2.1.7-7+deb7u1 ii dovecot-ldap 1:2.1.7-7+deb7u1 ii dovecot-lmtpd 1:2.1.7-7+deb7u1 ii dovecot-managesieved 1:2.1.7-7+deb7u1 ii dovecot-mysql 1:2.1.7-7+deb7u1 ii dovecot-pgsql 1:2.1.7-7+deb7u1 ii dovecot-pop3d 1:2.1.7-7+deb7u1 Any ideas?

3 3

Re: Dovecot fails to start - Unknown setting: socket
by Alan McGinlay 02 Oct '14

02 Oct '14

you almost certainly have a missing closing bracket or double quote somewhere.

2 1

[Dovecot] mdbox-files over 2 MB
by Hardy Flor 01 Oct '14

01 Oct '14

Hello, I received an e-mail, this includes 9 forwarding, each with a file. These files are not removed from the e-mail and stored in the attachments-directory, although they are larger than 16 KB. For all files the "Content-Transfer-Encoding: base64" is set. The email is stored in completely in "m.00000034" ------------------------------------- doveconf: # 2.2.12: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4 ext4 mail_attachment_dir = /var/mail/attachments mail_attachment_hash = %{md5} mail_attachment_min_size = 16 k mail_location = mdbox:/var/mail/user/%n mdbox_rotate_interval = 1 weeks mdbox_rotate_size = 2 M ------------------------------------- directory: root@xxx:/var/mail/user/xxx/storage# ls -al ... -rw------- 1 vmail mail 14433784 Mär 16 13:51 m.00000034 ...

6 8

Master user and invalid credentials dovecot-2.2.13
by Götz Reinicke - IT Koordinator 30 Sep '14

30 Sep '14

Hi, I followed the docs from the dovecot wiki (http://wiki2.dovecot.org/Authentication/MasterUsers) and still have some problem: 1. uncommented "!include auth-ldap.conf.ext" in 10-auth.conf 2. htpasswd -b -c -s .... to create user/password for a masteruseruser 3. checked auth-master.conf.ext When I try to test the login, I always get an "invalid credentials" in the logs with auth_debug=yes set. dovecot can read /etc/dovecot/master-users The users are in ldap. The example wiki shows the passwords {SHA1}...., in my password file they are {SHA}.... The "master user" posting in september gave some clues what might be wrong, but did not help to solve my problem. Any suggestions are welcome! Thanks and regards. Götz -- Götz Reinicke IT-Koordinator Tel. +49 7141 969 82 420 E-Mail goetz.reinicke(a)filmakademie.de Filmakademie Baden-Württemberg GmbH Akademiehof 10 71638 Ludwigsburg www.filmakademie.de Eintragung Amtsgericht Stuttgart HRB 205016 Vorsitzender des Aufsichtsrats: Jürgen Walter MdL Staatssekretär im Ministerium für Wissenschaft, Forschung und Kunst Baden-Württemberg Geschäftsführer: Prof. Thomas Schadt

4 4

No AUTH PLAIN with dovecot 2.0.19
by Michael Wechner 30 Sep '14

30 Sep '14

Hi I have installed the package dovecot-postfix on Ubuntu 12.04 LTS: dovecot --version: 2.0.19 postconf -d | grep version: 2.9.6 and receiving email works very fine, but relaying email does not work. I think the problem is that after STARTTLS the authentication is not being executed 250-AUTH PLAIN 250-AUTH=PLAIN which means using telnet returns telnet mx2.wyona.com 587 Trying 50.116.54.197... Connected to node3.wyona.com. Escape character is '^]'. 220 node3.members.linode.com ESMTP Postfix (Ubuntu) EHLO letscallitevil.com 250-node3.members.linode.com 250-PIPELINING 250-SIZE 10240000 250-VRFY 250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN So far I have used dovecot version 1.2.9, which works very fine, but the configuration /etc/dovecot/dovecot.conf seems to be very different in the case of dovecot version 2.0.19. I have checked all kind of tutorials for several days now, like for example https://help.ubuntu.com/10.04/serverguide/postfix.html but nothing helped. Any pointers or help is very much appreciated. Thanks Michael

4 13