- dovecot - dovecot.org

[Dovecot] Weird mirgration problem
by Stewart Dean 27 Aug '09

27 Aug '09

Most likely non-Dovecot, but I'd appreciate any comments on WTF might be going on here. Preparatory to migration from mbox to maildir format on our AIX mail server, I am migrating from the JFS filesystem (being deprecated by IBM) to JFS2 to better handling the jump in the number of files. Two nights ago, I took the first step and migrated the IT homedir filesystem: copied it to a scratch disk, melted down the FS and recreated it as a JFS2 FS. In order to keep changes from happening to it during this process, I killed off DC (dovecot -n ouput is appended to bottom of this note) and dropped the export of the FS. The bringup was a little ragged due to time constraints and the fact that I had trouble re-establishing the export. FWIW, the homedirs and Inobx FSes are mounted by a majordomo mailing list server. Everything went fine except for an anomaly with old pre-existing mailing list emails in my INBOX and that of a few others. Note that the inbox FS wasn't touched by this process, just the homedir FS for the IT department. What happened there was that the mbox headers went from looking like this: From owner-hcrcstaff Mon Aug 24 14:53:29 2009 >From majordom Mon Aug 24 14:53:29 2009 the rest of the normal header here To looking like this: From owner-hcrcstaff Mon Aug 24 14:53:29 2009 Status: RO X-UID: 871476 Content-Length: 1915 >From majordom Mon Aug 24 14:53:29 2009 normal header lines here It appears that the Status, X-UID and Content-Length lines were inserted just under the top line of the header in every old mailing list mailing email header...and not in any other mailing As a result of this, = these emails appear in the email client's TOC listing with blank Sender and Subject fields, even though the data for that is properly in the header further down = This happens both in TBird and Horde webmail. = All these emails (some 300, going back to 2008) are listed in one block, in proper order for their actual date, as having the datestamp of 5AM, when I was bringing everything back up. Unfortunately, because of time pressures, I can say exactly what I was doing then. = I never took down my TBird session while doing this process...and I imagine that others, who haven't said anything and presumably didn't have this problem, left their TBird or IMAP email client up... Does this anomaly bring to mind anything to you? FWIW, I plan on doing the students' homedir FS early tomorrow morning. This time I'll be more scrupulous about tracking things AND I will take down the mailing list and login servers to remove the possibility that they had something to do with this... dovecot -n output # 1.1.15: /usr/local/etc/dovecot.conf # OS: AIX 3 0001378F4C00 listen: *:143 ssl_listen: *:993 disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_processes_count: 12 login_max_processes_count: 774 max_mail_processes: 1024 verbose_proctitle: yes first_valid_uid: 200 mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=/var/dcindx/%u mbox_write_locks: fcntl mbox_dirty_syncs: no auth default: passdb: driver: pam userdb: driver: passwd -- ==== Once upon a time, the Internet was a friendly, neighbors-helping-neighbors small town, and no one locked their doors. Now it's like an apartment in Bed-Stuy: you need three heavy duty pick-proof locks, one of those braces that goes from the lock to the floor, and bars on the windows.... ==== Stewart Dean, Unix System Admin, Bard College, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 1

[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