- dovecot - dovecot.org

[Dovecot] fchown() failed
by Arthur Dent 26 Aug '09

26 Aug '09

Hello all, I'm not sure if this question is better posed to a Fedora group because I have only had this problem since I upgraded from F9 to F11, but I figured that the specialised knowledge here might help me more... I have been getting these entries in syslog since upgrading. Today for instance I got: **Unmatched Entries** dovecot: Dovecot v1.2.0 starting up (core dumps disabled): 1 Time(s) dovecot: IMAP(mark): fchown() failed with file /home/mark/Mail/.imap/INBOX/dovecot.index.log.newlock: Operation not permitted: 1 Time(s) dovecot: IMAP(mark): fchown() failed with file /home/mark/Mail/.imap/INBOX/dovecot.index.tmp: Operation not permitted: 1 Time(s) and yesterday I had: **Unmatched Entries** dovecot: IMAP(helena): fchown() failed with file /home/wife/mail/.imap/INBOX/dovecot.index.tmp: Operation not permitted: 1 Time(s) dovecot: IMAP(toby): fchown() failed with file /home/son/mail/.imap/INBOX/dovecot.index.cache.lock: Operation not permitted: 1 Time(s) dovecot: IMAP(toby): fchown() failed with file /home/son/mail/.imap/INBOX/dovecot.index.log.newlock: Operation not permitted: 1 Time(s) dovecot: IMAP(toby): fchown() failed with file /home/son/mail/.imap/INBOX/dovecot.index.tmp: Operation not permitted: 3 Time(s) The permissions are as follows: ls -la /home/mark/Mail/.imap/INBOX/ total 328 drwx------. 2 mark mark 4096 2009-08-18 15:32 . drwx------. 84 mark mark 4096 2009-03-05 21:53 .. -rw-------. 1 mark mark 7472 2009-08-18 15:32 dovecot.index -rw-------. 1 mark mark 286720 2009-08-19 11:46 dovecot.index.cache -rw-------. 1 mark mark 5380 2009-08-19 12:43 dovecot.index.log Those of wife and son are similar. As I access my mailbox several times a day (and certainly did yesterday) from several different mail clients I am surprised that the error count is only 1 for most the above entries. Is this being caused by some sort of cron job (logrotate perhaps)? Any ideas? All help / suggestions gratefully received... Thanks Mark

2 2

[Dovecot] Load spikes on NFS server, multiple index updaters.
by Jorgen Lundman 26 Aug '09

26 Aug '09

We are occasionally experiencing trouble where the NFS server's load will shoot over 60+. (Normal of sub 1.0). I have been hunting this for a while, and I believe it comes down to "deliver". System setup: NFS servers: x4540 Solaris 10 x64 ZFS over NFS. NFS clients: Solaris 10 x64 postfix-2.4.1 with dovecot-1.1.11 deliver. What appears to happen, when I check for nfsstat per process, is that I see 4 processes (in this case on vmx04) taking up majority of NFS ops: root@vmx04:/var/tmp# ./nfsclientstats.pl process read write readdir getattr setattr lookup access create remove rename mkdir rmdir 24303 0 0 1 19 0 190 171 0 0 0 0 0 24551 0 0 1 18 0 180 162 0 0 0 0 0 26099 0 0 1 18 0 180 162 0 0 0 0 0 295 0 0 1 18 0 180 162 0 0 0 0 0 6793 3 0 0 0 0 5 5 0 0 0 0 0 7234 0 1 0 2 0 9 9 0 1 0 0 0 Checking what these processes are doing, I find the following happening: 26099: getdents64(8, 0xCE7A4000, 8192) = 8136 26099: stat64("/export/censored/mail/cur/1223013930.V4700010I69f93eM483098.vmx02.unix:2,S", 0x08047930) = 0 26099: stat64("/export/censored/mail/cur/1222066290.V4700007I67562bM241839.vmx04.unix:2,S", 0x08047930) = 0 26099: stat64("/export/censored/mail/cur/1225325373.V4700008I94a1f9M286935.vmx04.unix:2,S", 0x08047930) = 0 26099: stat64("/export/censored/mail/cur/1236170307.V4700002I67ca03M310418.vmx06.unix:2,", 0x08047930) = 0 26099: stat64("/export/censored/mail/cur/1223581462.V4700011I69ffd6M720814.vmx02.unix:2,S", 0x08047930) = 0 Very well, so it is rebuilding the dovecot.index, or recalculating the user's quota usage. Is the directory large? root@vmx04# ls -l /export/censored/mail/cur/|wc -l 199626 You bet! But what is annoying is that if I also check process 24303, 24551 and 295, they are scanning the SAME user's directory. 295: stat64("/export/censored/mail/cur/1230544947.V4700004I11d1d7fM492433.vmx04.unix:2,S", 0x08047930) = 0 295: stat64("/export/censored/mail/cur/1223003964.V4700007I68932dM763546.vmx04.unix:2,S", 0x08047930) = 0 So, in vmx04 we have 4 processes working in one user's giant directory, and on the other vmx clients, many more. Could the semantics to 're-computing dovecot.index' be done such that the first "deliver" process locks it to do the work, and sub-sequent deliver processes will return temporary failures, until the work has finished. Has it been already addresses in dovecot-1.1.18? Advice please. Lund -- Jorgen Lundman | <lundman(a)lundman.net> Unix Administrator | +81 (0)3 -5456-2687 ext 1017 (work) Shibuya-ku, Tokyo | +81 (0)90-5578-8500 (cell) Japan | +81 (0)3 -3375-1767 (home)

2 4

Re: [Dovecot] LDAP: Connection lost to LDAP server,
by Andrés A. Gómez Palacio 25 Aug '09

25 Aug '09

Hi i have: [root@mail log]# rpm -q dovecot dovecot-1.2.4-0_99.el5 and have the same problem with ldap (AD), in this release is not include the patch? (http://hg.dovecot.org/dovecot-1.2/rev/355d5a40f7a7) is normal the reconnection to ldap server? or exist any reazon for lose the connection? Aug 25 11:27:03 mail dovecot: auth-worker(default): LDAP: Connection lost to LDAP server, reconnecting Aug 25 11:37:34 mail dovecot: auth-worker(default): LDAP: Connection lost to LDAP server, reconnecting Aug 25 11:46:04 mail dovecot: auth-worker(default): LDAP: Connection lost to LDAP server, reconnecting Aug 25 11:52:34 mail dovecot: auth-worker(default): LDAP: Connection lost to LDAP server, reconnecting Aug 25 11:56:06 mail dovecot: auth-worker(default): LDAP: Connection lost to LDAP server, reconnecting Aug 25 12:01:07 mail dovecot: auth-worker(default): LDAP: Connection lost to LDAP server, reconnecting Aug 25 12:11:06 mail dovecot: auth-worker(default): LDAP: Connection lost to LDAP server, reconnecting Aug 25 12:16:07 mail dovecot: auth-worker(default): LDAP: Connection lost to LDAP server, reconnecting Aug 25 12:28:07 mail dovecot: auth-worker(default): LDAP: Connection lost to LDAP server, reconnecting ....... Message: 1 Date: Tue, 25 Aug 2009 18:13:28 +0400 From: McShel <McShel(a)yandex.ua> Subject: Re: [Dovecot] LDAP: Connection lost to LDAP server, reconnecting To: "Dovecot Mailing List"<dovecot(a)dovecot.org> Message-ID: <37911251209608(a)webmail126.yandex.ru> Content-Type: text/plain 25.08.09, 17:32, "Timo Sirainen" <tss(a)iki.fi>: > On Tue, 2009-08-25 at 16:09 +0400, McShel wrote: > > Hi! Sorry by my english. Set Postfix + dovecot + AD + ldap, everything works well, but appears in the logs, every 15 minutes: > > > > auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting > > > > Standart limit ldap connect to AD 15 minutes. > > Can somehow fix this problem without increasing the time of connection to the AD? > This is actually a bug. Fixed: > http://hg.dovecot.org/dovecot-1.2/rev/355d5a40f7a7 > (The patch applies to v1.1 too) Thank you! You include this fix in the next release? ------------------------------ Message: 2 Date: Tue, 25 Aug 2009 10:24:58 -0400 From: Charles Marcus <CMarcus(a)Media-Brokers.com> Subject: Re: [Dovecot] LDAP: Connection lost to LDAP server, reconnecting To: McShel <McShel(a)yandex.ua> Cc: Dovecot Mailing List <dovecot(a)dovecot.org> Message-ID: <4A93F43A.8050009(a)Media-Brokers.com> Content-Type: text/plain; charset=ISO-8859-1 On 8/25/2009, McShel (McShel(a)yandex.ua) wrote: > Thank you! You include this fix in the next release? He always does... :) -- Best regards, Charles ------------------------------------------------------------------------------------------------------- DISCLAIMER NOTE: Este mensaje y/o sus anexos son para uso exclusivo de su destinatario intencional y puede contener información legalmente protegida por ser privilegiada o confidencial. Si usted no es el destinatario del mensaje, debe informarnos de inmediato, eliminar el mensaje y sus anexos de su computador. Le comunicamos que cualquier retención, revisión no autorizada, distribución, divulgación, reenvío, copia, impresión, reproducción o uso indebido de este mensaje y/o sus anexos, está estrictamente prohibida y sancionada legalmente. Este mensaje igualmente, puede contener información de carácter personal que no necesariamente refleja la opinión de AVANSOFT S.A. Este mensaje y sus anexos han sido sometidos a control con programas antivirus, por lo cual consideramos se encuentra libre de virus o cualquier anomalía que pueda afectar a terceros; sin embargo, el destinatario debe verificar con sus propios medios de protección, que lo recibido no está afectado por virus u otros defectos, en cuyo caso, el remitente no asume responsabilidad alguna por el recibo, transmisión y uso de este material.

2 1

[Dovecot] scalability and arhive ideas
by fernando＠dfcom.com.br 25 Aug '09

25 Aug '09

Hi, I´m reading the past topics related to archive and scalability of dovecot, they are all very interesting. Here, I´m using two dovecot proxies in front of five storages pairs, and we split the domain´s accounts among those servers. So, we can share the i/o load and if one server goes down only few accounts of the domain stops (not all of them). But, we began to have space problems - and the solution would be insert more and more storage servers. So I was searching for some archive solutions (hard links - at S.O level, or some dovecot extension). A friend told me that he knows an ISP that share even the mailbox of the users among many servers - this is very weird and (at same time) very interesting approach. Instead of put all messages into one maildir and this maildir into one server, this "maildir" (?) is spplited among many servers - so, if one servers fails the account is still acessible and they move old/big messages to a new "cheap" storage - archiving transparently. Well, maybe it´s an stupid idea, but couldn´t dovecot imap/pop proxy do the same ? I mean, imagine the following scenario: 1- Proxy does an user account sql - today the return is (among other data), the final server IP, but it could be the storage servers for this account 2- Proxy does parallel connections (instead of today´s one connection with the final server). Retrieve the messages and caches locally where the message is. If the cache is lost, no problem, it just connects again and re-cache them. 3- When a message is deleted/flagged, etc - it has the cache (allowing it to know where send the command to), when a message inserted (as sent folder) - the system can have the 'default storage' where the messages are delivered and saved to - the other storages are just for archiving (or even a round-robin delivery !? - hard to control). Problems: 1- Have the cache at proxy level. 2- Quota calculation (how the delivery process can check this ?) 3- Maybe mixing proxy connection and this new approach is not easy way. 4- the more servers, the more time waiting their answers (imagine one of them answering slowly). Advantages: 1- No local mounts at storage level - (as nfs and other network mounted partitions). 2- Servers independency - if space is at a critical value, insert a pair of servers, move messages there, insert the servers in the sql answer (server1, server2, server3, ... , serverN). 3- Scalability - the more servers, the more i/o load you can share. Well, sorry for the long post...but I hope to collaborate with some ideas (even if they are stupid :( ) Regards, Fernando Bertasso Figaro

3 8

[Dovecot] dovecot-auth failed: Not enough space
by S. A. Woltering 25 Aug '09

25 Aug '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, I've been trying to get a Dovecot IMAP service running under HP-UX 11.23, IA64. The system has 6GB of spare space under /var and at least the same amount of RAM free at the current time. I've compiled from the latest source (1.2.4), using the following options: # CC="/opt/aCC/bin/aCC" ./configure --prefix=/opt/dovecot ... usual make && make install My config file follows at the end. In essence, every time I attempt to start dovecot (/opt/dovecot/sbin/dovecot, with no options) I get the following on the command line: Warning: Last died with error (see error log for more information): Auth process died too early - shutting down Info: If you have trouble with authentication failures, enable auth_debug setting. See http://wiki.dovecot.org/WhyDoesItNotWork Looking into /var/adm/syslog/mail.log, the lines associated with this run read: Aug 24 14:46:25 bilbo dovecot: Dovecot v1.2.4 starting up Aug 24 14:46:25 bilbo dovecot: Fatal: execv(/opt/dovecot/libexec/dovecot/dovecot-auth) failed: Not enough space Aug 24 14:46:25 bilbo dovecot: Fatal: Auth process died too early - shutting down I've switched over to using a static passwd file type auth and I still get the same error. Hoping someone has some idea why this is happening... Thanks, Ashley ## Dovecot configuration file ## base_dir = /var/run/dovecot protocols = imap listen = * disable_plaintext_auth = no shutdown_clients = yes ## ## Logging ## log_timestamp = "%b %d %H:%M:%S " syslog_facility = mail ## ## SSL settings ## #ssl_listen = ssl = no ## ## Login processes ## login_dir = /var/run/dovecot/login login_chroot = yes login_user = dovecot ## ## Mailbox locations and namespaces ## mail_location = maildir:/mail%h/Maildir ## ## IMAP specific settings ## protocol imap { login_executable = /opt/dovecot/libexec/dovecot/imap-login mail_executable = /opt/dovecot/libexec/dovecot/imap #imap_max_line_length = 65536 mail_max_userip_connections = 10 #mail_plugins = mail_plugin_dir = /opt/dovecot/lib/dovecot/imap imap_logout_format = bytes=%i/%o #imap_capability = #imap_idle_notify_interval = 120 #imap_id_send = #imap_id_log = #imap_client_workarounds = } ## ## Authentication processes ## auth_executable = /opt/dovecot/libexec/dovecot/dovecot-auth auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth default { passdb passwd-file { args = /opt/dovecot/etc/imap-passwd.txt } } - -- Steven-Ashley Woltering, Systems Analyst, ECMWF, Shinfield Park, Reading, RG2 9AX, UK Tel.: +44 1189 499473 (internal x2473) Email: Steven.Woltering(a)ecmwf.int -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFKkpsnh854NVK99FMRAtVZAJ9nOt/HP1ODSTSMkLPNsPOfRK/EsACghPQ7 aFNOxf4hAKV7NKkiZ/4Z7X8= =5Ww9 -----END PGP SIGNATURE-----

2 4

[Dovecot] LDAP: Connection lost to LDAP server, reconnecting
by McShel 25 Aug '09

25 Aug '09

Hi! Sorry by my english. Set Postfix + dovecot + AD + ldap, everything works well, but appears in the logs, every 15 minutes: auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Standart limit ldap connect to AD 15 minutes. Can somehow fix this problem without increasing the time of connection to the AD?

3 3

Re: [Dovecot] Dovecot and LDAP-Quotas
by south africa 25 Aug '09

25 Aug '09

> Do you have any other userdbs now? What does dovecot-ldap-userdb.conf > now contain? Is it only quota that's now broken or the logins > completely? The dovecot-ldap-userdb.conf is only a symbolic link on the original dovecot-ldap.conf. Only the ldap-quota is broken. The normal ldap-authentification goes like clockwork. >Set auth_debug=yes and log in, what does it say? "login" ------- Aug 25 11:51:18 auth(default): Info: client in: AUTH 1 PLAIN service=pop3 secured lip=123.456.789.72 rip=192.168.1.2 lport=995 rport=1984 Aug 25 11:51:18 auth(default): Info: client out: CONT 1 Aug 25 11:51:18 auth(default): Info: client in: CONT 1 Aug 25 11:51:18 auth(default): Info: client out: OK 1 user=testuser Aug 25 11:51:18 auth(default): Info: master in: REQUEST 1 21237 1 Aug 25 11:51:18 auth(default): Info: master out: USER 1 testuser uid=500 gid=500 home=/home/vmail/testuser Aug 25 11:51:18 pop3-login: Info: Login: user=<testuser>, method=PLAIN, rip=192.168.1.2, lip=123.456.789.72, TLS Aug 25 11:51:18 POP3(testuser): Info: Loading modules from directory: /usr/lib64/dovecot/pop3 Aug 25 11:51:18 POP3(testuser): Info: Module loaded: /usr/lib64/dovecot/pop3/lib10_quota_plugin.so Aug 25 11:51:18 POP3(testuser): Info: Effective uid=500, gid=500, home=/home/vmail/testuser Aug 25 11:51:18 POP3(testuser): Info: Quota root: name=User quota backend=maildir args= Aug 25 11:51:18 POP3(testuser): Info: Quota rule: root=User quota mailbox=* bytes=8388608 messages=0 Aug 25 11:51:18 POP3(testuser): Info: Quota warning: bytes=7549747 (90%) messages=0 command=/usr/local/bin/quota-warning.sh 90 Aug 25 11:51:18 POP3(testuser): Info: Quota warning: bytes=6291456 (75%) messages=0 command=/usr/local/bin/quota-warning.sh 75 Aug 25 11:51:18 POP3(testuser): Info: maildir: data=/home/vmail/testuser/Maildir/ Aug 25 11:51:18 POP3(testuser): Info: maildir++: root=/home/vmail/testuser/Maildir, index=, control=, inbox=/home/vmail/testuser/Maildir Aug 25 11:51:18 POP3(testuser): Info: Namespace : Using permissions from /home/vmail/testuser/Maildir: mode=0700 gid=-1 Aug 25 11:51:18 POP3(testuser): Info: Disconnected: Logged out top=0/0, retr=1/2608, del=1/1, size=2591 Aug 25 11:51:18 auth(default): Info: new auth connection: pid=21247 "email delivery" ---------------- Aug 25 11:53:02 auth(default): Info: new auth connection: pid=21248 Aug 25 11:53:02deliver(testuser@core.uk): Info: Loading modules from directory: /usr/lib64/dovecot/lda Aug 25 11:53:02deliver(testuser@core.uk): Info: Module loaded: /usr/lib64/dovecot/lda/lib10_quota_plugin.so Aug 25 11:53:02 auth(default): Info: master in: USER 1 testuser(a)core.uk service=deliver Aug 25 11:53:02 auth(default): Info: master out: USER 1 testuser uid=500 gid=500 home=/home/vmail/testuser Aug 25 11:53:02deliver(testuser@core.uk): Info: auth input: uid=500 Aug 25 11:53:02deliver(testuser@core.uk): Info: auth input: gid=500 Aug 25 11:53:02deliver(testuser@core.uk): Info: auth input: home=/home/vmail/testuser Aug 25 11:53:02deliver(testuser@core.uk): Info: userdb changed username to testuser Aug 25 11:53:02deliver(testuser): Info: Quota root: name=User quota backend=maildir args= Aug 25 11:53:02deliver(testuser): Info: Quota rule: root=User quota mailbox=* bytes=8388608 messages=0 Aug 25 11:53:02deliver(testuser): Info: Quota warning: bytes=7549747 (90%) messages=0 command=/usr/local/bin/quota-warning.sh 90 Aug 25 11:53:02deliver(testuser): Info: Quota warning: bytes=6291456 (75%) messages=0 command=/usr/local/bin/quota-warning.sh 75 Aug 25 11:53:02deliver(testuser): Info: maildir: data=/home/vmail/testuser/Maildir/ Aug 25 11:53:02deliver(testuser): Info: maildir++: root=/home/vmail/testuser/Maildir, index=, control=, inbox=/home/vmail/testuser/Maildir Aug 25 11:53:02deliver(testuser): Info: Namespace : Using permissions from /home/vmail/testuser/Maildir: mode=0700 gid=-1 Aug 25 11:53:02deliver(testuser): Info: msgid=<E74BF4D485115048AF3A7D77FA7A75610B00F594(a)exc1.three.core.uk>: saved mail to INBOX _____________________________________________________________ Get your FREE TheDoghouseMail email address at http://www.thedoghousemail.com

2 1

[Dovecot] log for each user
by Thomas G. Lau 25 Aug '09

25 Aug '09

Dear all, does anyone did any scripting to log every user activity such as remove message? we got some user keep blaming us about message lost on email server, wondering if any of you did anything about this? Thanks.

4 5

[Dovecot] rawlog not work
by Thomas G. Lau 25 Aug '09

25 Aug '09

Dear all, I am trying to setup dovecot on centos 5.3, dovecot.rawlog is created in user home dir and change to user as owner. But when I try to telnet into pop3 and use list command, nothing is logged and dovecot.rawlog remain empty. should I run rawlog even on login_executable ? Please advice. dovecot --version 1.2.4 # 1.2.4: /etc/dovecot.conf # OS: Linux 2.6.18-128.4.1.el5 x86_64 CentOS release 5.3 (Final) protocols: pop3 login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/pop3-login login_processes_count: 1 mail_debug: yes mail_executable: /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/pop3 mail_plugin_dir: /usr/lib64/dovecot/pop3 lda: postmaster_address: postmaster(a)example.com auth default: passdb: driver: pam userdb: driver: passwd

1 1

[Dovecot] Aborted: Worker is buggy
by David Jonas 25 Aug '09

25 Aug '09

I upgraded from 1.1 to 1.2 a couple months ago and now we are seeing this: Aug 20 05:34:38 kelly dovecot: auth(default): auth workers: Auth request was queued for 7 seconds, 10 left in queue ... Aug 20 05:34:38 kelly dovecot: auth(default): BUG: Worker sent reply with id 53, expected 54 Aug 20 05:34:38 kelly dovecot: auth(default): worker-server(xxx(a)example.com,dd.dd.dd.dd): Aborted: Worker is buggy Aug 20 05:34:38 kelly dovecot: auth(default): passdb(xxx(a)example.com,dd.dd.dd.dd): Fallbacking to expired data from cache When I attempt to restart dovecot there is one dovecot-auth process that won't die and keeps the server from starting. A simple 'killall dovecot-auth' takes care of it and the server is able to start. I'm not using anything exotic, dovecot config below. The most curious fact is that we have identical servers running the same version of dovecot (1.2.3, happened under 1.2.1 as well) talking to the same MySQL database and both develop the problem at the same time. The database is under considerable stress at the time this occurs as the policyd tables are being cleaned. But this happens twice per hour and only sometimes does dovecot have trouble. I'm working to move the policyd database elsewhere, but of course this shouldn't happen in any case. Any help would be much appreciated. Thanks! David # 1.2.3: /etc/dovecot/dovecot.conf # OS: Linux 2.6.9-42.0.10.ELsmp i686 Red Hat Enterprise Linux ES release 4 (Nahant Update 7) protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/dovecot/dovecot.pem ssl_key_file: /etc/dovecot/dovecot.pem ssl_cipher_list: ALL:!LOW:!SSLv2 disable_plaintext_auth: no login_dir: /usr/local/dovecot-1.2/var/run/dovecot/login login_executable(default): /usr/local/dovecot-1.2/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot-1.2/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot-1.2/libexec/dovecot/pop3-login login_process_per_connection: no verbose_proctitle: yes first_valid_uid: 89 maildir_stat_dirs: yes mail_executable(default): /usr/local/dovecot-1.2/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot-1.2/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot-1.2/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/local/dovecot-1.2/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot-1.2/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot-1.2/lib/dovecot/pop3 pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %f pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh lda: postmaster_address: postmaster(a)no-ip.com hostname: no-ip.com mail_plugins: quota auth_socket_path: /var/run/dovecot/auth-master auth default: mechanisms: login plain cram-md5 cache_size: 5000 cache_ttl: 1800 cache_negative_ttl: 60 user: nobody username_chars: abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ username_translation: %@ username_format: %TLu verbose: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: prefetch userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: quota: dict:user:%LTd-%LTn:proxy::quota quote_rule: *:storage=100G dict: quota: mysql:/etc/dovecot/dovecot-dict-sql.conf ## dovecot-sql.conf driver = mysql connect = host=192.168.dd.dd dbname=xxx user=xxx password=xxx user_query=... password_query=... ## dovecot-dict-sql.conf connect = host=192.168.dd.dd dbname=xxx user=xxx password=xxx map { pattern = priv/quota/storage table = quota2 username_field = username value_field = bytes } map { pattern = priv/quota/messages table = quota2 username_field = username value_field = messages }

2 2