- dovecot - dovecot.org

[Dovecot] Dovecot - with LDAP auth backend
by Shahmat Dahlan 19 Mar '07

19 Mar '07

I have the following installed (1) CentOS 2.6.9-42.ELsmp (2) dovecot-1.0-3_50.rc27.el4.at, (3) openldap-2.2.13-6.4E (A) I have added the following schema into /etc/openldap/schema attributetype ( 1.3.6.1.4.1.14237.1.1.1.1 NAME 'mailquota' DESC 'The size of space the user can have until further messages get bounced.' EQUALITY integerMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SINGLE-VALUE ) objectclass ( 1.3.6.1.4.1.14237.1.1.2.1 NAME 'DovecotUser' DESC 'Dovecot-LDAP User' SUP top AUXILIARY MUST ( cn $ uid $ mail $ mailquota $ userPassword ) MAY ( sn ) ) (B) and added this into my /etc/openldap/slapd.conf include /etc/openldap/schema/dovecot.schema (C) And in my /etc/dovecot.conf, this is what I have protocol imap { mail_plugins = quota imap_quota mail_plugin_dir = /usr/lib/dovecot/imap } (D) also in my /etc/dovecot.conf plugin { quota = maildir:storage=10240 } (E) in my /etc/dovecot-ldap.conf user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,mailquota=quota user_filter = (&(objectClass=DovecotUser)(uid=%u)) pass_attrs = uid=user,userPassword=password Scenario 1 I have (D) set to quota = maildir:storage=10240, did a telnet localhost 143, and logged in, this is what I get Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. * OK Mail ready a1 login ldapuser password a1 OK Logged in. a2 getquota "" * QUOTA "" (STORAGE 0 10240) a2 OK Getquota completed. if I were to change (D) to quota = maildir And added in an attribute called "mailquota" in the entry uid=ldapuser,dc=mydomain,dc=com, give it a value 10240000 (is this correct? should it by in bytes or in kilobytes?), then reinitialize the mailbox by deleting the ~/Maildir directory (or in this case /home/ldapuser/Maildir) Did the telnet localhost 143, this is what I get instead Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. * OK Mail ready a1 login ldapuser password a1 OK Logged in. a2 getquota "" * QUOTA "" () a2 OK Getquota completed. Even after I've added the attribute mailquota in the ldap for the entry uid=ldapuser it still does not look like its taking any effect at all. Regards and thanks in advance.

2 1

[Dovecot] using sieve plugin
by Kendall Shaw 19 Mar '07

19 Mar '07

Hi, I have installed dovecot on ubuntu edgy linux by retrieving the source debian package, building and installing the package and then building and installing the sieve plugin. However, I get no log messages indicating errors and as far as I can tell, my .dovecot.sieve script is not being used. I have introduced a syntax error in the script and see no error message. In dovecot.conf I have: log_path = /var/log/dovecot.log invo_log_path = /var/log/dovecot.log protocol lda { module_dir = /usr/lib/dovecot/modules/lda mail_plugins = cmusieve log_path = /var/log/dovecot-deliver.log info_log_path = /var/log/dovecot-deliver.log } I am using exim with dovecot. I've tried using a .forward file (I'm the one user on the computer). Alternately, I've tried creating the dovecot_deliver "transport" in exim and changing the localuser router to use it. Still, I get no messages from deliver and no error messages from dovecot or exim. The file dovecot-deliver.log is not created. Do you have any suggestions that can help me get it working or to see why it is not working? Kendall

2 1

[Dovecot] One user having reproducible IMAP issues
by Alex Boster 19 Mar '07

19 Mar '07

Dovecot version upgraded to 1.0r26 (did not fix problem). The server is a CentOS 4 x86 box. Using ext3 filesystem. Previous attempts to fix the issue have included simply moving aside the user's INBOX to recreating a new account from scratch. Sometimes the email behaves for a while, but within a day is not working again. In Mail.app (the user's usual mail client) the INBOX folder simply appears empty. mutt (run locally on the server) shows the messages there correctly. The problem is easily reproducible. Move /var/spool/mail/[username] to a backup file and remove all .imap directories for that user. Mail may work for a while, but will stop within 24 hours. The SquirrelMail message is: ERROR: The server couldn't find the message you requested. Most probably your message list was out of date and the message has been moved away or deleted (perhaps by another program accessing the same mailbox). Click here to return to INBOX dovecot -n : # /etc/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.debug.log login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u mail_full_filesystem_access: yes mail_executable(default): /usr/libexec/dovecot/rawlog /usr/libexec/ dovecot/imap mail_executable(imap): /usr/libexec/dovecot/rawlog /usr/libexec/ dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: mechanisms: plain login passdb: driver: pam args: dovecot userdb: driver: passwd Thanks! Alex

4 8

[Dovecot] authenticating with LDAP and SSL
by Nathan Fiedler 19 Mar '07

19 Mar '07

I managed to configure Dovecot to use a local OpenLDAP server to authenticate clients, without using SSL. However, I would rather that LDAP is accessed using SSL, but I cannot get Dovecot to connect. All that I did was change "uris" to "ldaps://localhost", and this appears in the maillog: Mar 18 12:53:00 server dovecot: Dovecot v1.0.rc15 starting up Mar 18 12:53:01 server dovecot: auth(default): ldap_bind((null)) failed: Can't contact LDAP server Is there additional configuration that is needed for SSL? Note that I altered the slapd.conf file from not requiring SSL to requiring SSL when I changed the "uris" parameter. And, of course, accessing the directory using ldapsearch works just fine. It seems that there's only a problem when using SSL, but I don't know how to debug it. Thanks n

4 3

[Dovecot] Kerberos
by forum 18 Mar '07

18 Mar '07

Hey all new to this crack Ok so i have setup kerosene on my server i run mutt and it goes off and gets kerberos key from server I have added teh gssapi to config file but when the key seams to want to authenticate off dovecot it fail anyone help me? Mutt is returning No authentication available Dovecot logs are returning: Mar 18 01:34:31 bandicoot dovecot: auth(default): gssapi(?,MYIPADDRESS): While acquiring service credentials: Miscellaneous failure Mar 18 01:34:31 bandicoot dovecot: auth(default): gssapi(?,MYIPADDRESS): While acquiring service credentials: No principal in keytab matches desired name Mar 18 01:34:34 bandicoot dovecot: imap-login: Aborted login: method=GSSAPI, rip=MYIPADDRESS, lip=MYIPADDRESS, TLS Thanks

3 5

[Dovecot] 1.0.rc27 released
by Timo Sirainen 18 Mar '07

18 Mar '07

http://dovecot.org/releases/dovecot-1.0.rc27.tar.gz http://dovecot.org/releases/dovecot-1.0.rc27.tar.gz.sig A few new small features and lots of index/mbox fixes. I've been heavily stress testing this release, so I think it should be about perfect. :) I think the only thing still missing from v1.0 is documentation. There are some unwritten pages in the wiki, and I still haven't bothered to write the wiki -> doc/*.txt conversion script. The script will probably be pretty easy, but writing the docs can take a while. + mbox and index file code handles silently out of quota/disk space errors (maildir still has problems). They will give the user a "Not enough disk space" error instead of flooding the log file. + Added fsync_disable setting. + mail-log plugin: Log the mailbox name, except if it's INBOX + dovecot-auth: Added a lot more debug logging to passdbs and userdbs + dovecot-auth: Added %c variable which expands to "secured" with SSL/TLS/localhost. + dovecot-auth: Added %m variable which expands to auth mechanism name - maildir++ quota: With ignore=box setting the quota was still updated for the mailbox even though it was allowed to go over quota (but quota recalculation ignored the box). - Index file handling fixes - mbox syncing fixes - Wrong endianess index files still weren't silently rebuilt - IMAP quota plugin: GETQUOTAROOT returned the mailbox name wrong the namespace had a prefix or if its separator was non-default - IMAP: If client was appending multiple messages with MULTIAPPEND and LITERAL+ extensions and one of the appends failed, Dovecot treated the rest of the mail data as IMAP commands. - If mail was sent to client with sendfile() call, we could have hanged the connection. This could happen only if mails were saved with CR+LF linefeeds.

5 7

Re: [Dovecot] Login processes and a new performance/security compromise [was: Re: pre-1.0.rc27: Index and mbox fixes]
by Bill Boebel 18 Mar '07

18 Mar '07

On Sat, March 17, 2007 10:51 pm, Timo Sirainen <tss(a)iki.fi> said: > Oh, and as for when the rewrite is in CVS, I'm not really sure. I'm > still wondering if I should put it there soon and make the release after > v1.0 be v2.0, or if I should first stabilize the current new CVS HEAD > features (which shouldn't take too long), do a v1.2 release and only > then put this code to CVS and make it v2.0.. I vote for first stabilizing the current new CVS HEAD, do a v1.1 release, and then put the ssl rewrite into CVS and plan to make that either v1.2 or v2.0. That way people will start banging on the new features in current CVS HEAD sooner. Bill

2 1

[Dovecot] Connection closed by foreign host.
by tubauwe＠gmx.de 18 Mar '07

18 Mar '07

I installed dovecot on my system using the following configuration (in dovecot.conf): protocols = imap listen = * ssl_disable = yes login_user = nobody login_processes_count = 3 mail_extra_groups = nobody default_mail_env = maildir:/home/%u/Maildir auth default { mechanisms = plain passdb shadow { } userdb passwd { } user = root } After that I tested via telnet an got the message: Connection closed by foreign host. In the log-file I found the following lines: dovecot: Mar 12 22:49:18 Info: Dovecot v1.0.rc15 starting up dovecot: Mar 12 22:51:12 Info: imap-login: Login: user=<username>, method=PLAIN, rip=192.168.??.20, lip=192.168.??.3 dovecot: Mar 12 22:51:12 Error: setmntent(/etc/mtab) failed: No such file or directory dovecot: Mar 12 22:51:12 Error: child 616 (imap) killed with signal 11 Because I'm quite a newbie, I don't know what to do. Therefore I ask here for help. Thank you! -- "Feel free" - 5 GB Mailbox, 50 FreeSMS/Monat ... Jetzt GMX ProMail testen: www.gmx.net/de/go/mailfooter/promail-out

4 4

[Dovecot] M-Box benchmark
by Maykel Moya 18 Mar '07

18 Mar '07

A friend of mine passed me this[1] cause I'm recommending him Dovecot. My personal experience is very different to the one in that benchmark. I will appreciate similar links from those of you who had benchmarked Dovecot against other IMAP servers. I'm conscious that my personal experience is far to be a objetive comparison. I switched from UW-Imap/Mbox to Dovecot/Maildir a box with 45k local users, 3.5MB/s sustained IMAP/POP traffic in work hours. The main performance gain is from mbox -> maildir switching. Anyway the users (and myself) "perceive" a good performance with the new setup. Regards, maykel [1] http://www.isode.com/whitepapers/mbox-benchmark.html

8 13

[Dovecot] pre-1.0.rc27: Index and mbox fixes
by Timo Sirainen 18 Mar '07

18 Mar '07

I've been doing some stress testing in the last few days and fixing all the errors I saw. I'm hoping that I've finally really fixed all the index/mbox problems. So, again I think the only thing left for v1.0 is the documentation. Please test this nightly snapshot before I'll release rc27 tomorrow: http://dovecot.org/nightly/dovecot-latest.tar.gz If you've seen any of the following error messages in log files, these should all be fixed now: - index: Append with UID 56297, but next_uid = 56298 - mbox: UID inserted in the middle of mailbox /home/tss/mail/inbox (45769 > 45768, seq=28, idx_msgs=30) - mbox: Expunged message reappeared in mailbox /home/tss/mail/inbox (UID 86957 < 86958, seq=28, idx_msgs=27) These should be fixed for most cases, but they can still rarely happen: - index: Extension reset without intro prefix There's a really tiny possibility of it still happening with mmap_disable=no, but I think it's practically fixed now. A proper fix would require more changes than I want to do for v1.0 (either support for marking transaction start/end positions or getting rid of the stupid intro prefix completely). - Cached message offset 38340 is invalid for mbox file /home/tss/mail/inbox This should happen only if you're using in-memory indexes or mbox_min_index_size isn't 0. This happens if the mbox file's timestamp and file size are the exact same after some expunges+appends, so the only way to properly fix it would be to wait a second and update the mtime before unlocking the mbox file after expunges. This sleep is actually already done when Dovecot notices that a) mtime and size really are the same after modification and b) mails have been moved around inside the file (ie. flag changes were done but there weren't enough empty space in the mail's own headers so mails had to be moved to get the needed space). Should be pretty rare. Anyway, this error is completely invisible to users and it doesn't have any other side effects that mbox_dirty_syncs doesn't already have. The whole error message could even be removed if it's going to become a problem.. Other changes in the snapshot: + mail-log plugin: Log the mailbox name, except if it's INBOX + dovecot-auth: Added a lot more debug logging passdbs and userdbs + dovecot-auth: Added %c variable which expands to "secured" with SSL/TLS/localhost. + dovecot-auth: Added %m variable which expands to auth mechanism name - Wrong endianess index files still weren't silently rebuilt - IMAP quota plugin: GETQUOTAROOT returned the mailbox name wrong the namespace had a prefix or if its separator was non-default

5 24

[Dovecot] Lazy expunge
by meka＠ns-linux.org 17 Mar '07

17 Mar '07

When I try to use it i get undefined symbol: dlopen(/usr/lib/dovecot/pop3/lib02_lazy_expunge_plugin.so) failed: /usr/lib/dovecot/pop3/lib02_lazy_expunge_plugin.so: undefined symbol: namespace_find_prefix Does anyone has this problem or I've compiled it with too agresive flags? Thanx! PS. I've folowed http://wiki.dovecot.org/Plugins/Lazyexpunge word to word. -- FreeB(eer)S(ex)D(rugs) are the real daemons

3 2

[Dovecot] deliver to subfolder with dovecot's LDA
by Tom Bombadil 17 Mar '07

17 Mar '07

Hi all... How can deliver messages to a subfolder using the LDA? For example, I want a message to joe+spam(a)abc.com to be placed inside the 'spam' subfolder. Any hint is appreciated. Thanks ;)

3 2

[Dovecot] flock problems with index files and passwd-file
by Michal Soltys 17 Mar '07

17 Mar '07

While experimenting a bit, I found that for some reason, locking indexes with flock is problematic, but only if user is taken from passwd-file. The host system is openbsd 3.9, dovecot's configuration is added at the bottom. Authentication is from two places - first from mentioned passwd-file, then from passwd file using bsdauth (in this case, there're no problems with flock). So, if a user is i.e.: test@domain.tld:{plain}test:20000:10::/home/regular/test::userdb_mail=maildir:~/Maildir Then the mail client will timeout (thunderbird in this case), and dovecot will leave following info in the logs: Mar 15 11:13:38 rasengan dovecot: IMAP(test(a)domain.tld): Effective uid=20000, gid=10, home=/home/regular/test Mar 15 11:13:38 rasengan dovecot: IMAP(test(a)domain.tld): maildir: data=~/Maildir Mar 15 11:13:38 rasengan dovecot: IMAP(test(a)domain.tld): maildir: root=~/Maildir, index=~/Maildir, control=, inbox= Mar 15 11:15:38 rasengan dovecot: IMAP(test(a)domain.tld): Timeout while waiting for lock for transaction log file /home/regular/test/Maildir/dovecot.index.log Happens both if in maildir and mbox (userdb_mail=mbox:~/mail:INBOX=/home/regular/test/mbx) cases. Locking through dotlocks or fcntl works well in all situations (passwd-file or not). Dovecot 1.0 rc27 OpenBSD 3.9 (stable), i386 Dovecot config (dovecot -n): # /etc/dovecot.conf base_dir: /var/dovecot/ protocols: imap imaps pop3 pop3s ssl_listen: * ssl_ca_file: /etc/ssl/cert_bundle.pem ssl_cert_file: /etc/ssl/ca_ppgk/certs/fetch_crt.pem ssl_key_file: /etc/ssl/ca_ppgk/private/fetch_key.pem verbose_ssl: yes login_dir: /var/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting: Dovecot IMAP server ready. login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no valid_chroot_dirs: /var/mail:/home/regular verbose_proctitle: yes first_valid_uid: 1999 first_valid_gid: 10 mail_location: mbox:~/Mail:INBOX=/var/mail/%u mail_debug: yes lock_method: flock maildir_copy_with_hardlinks: yes mbox_read_locks: flock mbox_write_locks: flock mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: verbose: yes debug: yes passdb: driver: passwd-file args: /etc/dovecot.passwd passdb: driver: bsdauth userdb: driver: passwd-file args: /etc/dovecot.passwd userdb: driver: passwd /etc/dovecot.passwd is just a single line: test@domain.tld:{plain}test:20000:10::/home/regular/test::userdb_mail=maildir:~/Maildir

2 5

[Dovecot] LOCKD errors
by Jay Chandler 16 Mar '07

16 Mar '07

Running the nightly from two days ago. The Dovecot log shows no errors, but I keep getting login errors for a few users. top shows: 71486 user1 1 96 0 4552K 2408K lockd 0 0:00 0.00% imap 11170 user2 1 96 0 4440K 2480K lockd 0 0:00 0.00% imap And a ps aux shows that these processes have been open for hours. If I move the mbox that contains their mail, the same error still shows up. The mboxes reside on our NetApp which is NFS mounted-- does anyone have any wisdom regarding this? As best I can tell this hasn't been a problem before the last few RCs, though I could be mistaken on this. -- Jay Chandler Network Administrator Chapman University

3 4

[Dovecot] wiki -> txt
by Timo Sirainen 16 Mar '07

16 Mar '07

I've been trying to fix MoinMoin's text_plain formatter to produce readable output. It's almost correct, except I don't understand why I can't get the LF-adding rules correct. Either there are too many LFs or too few. And whenever I change something, something else breaks.. It's getting pretty annoying. So if anyone else wants to try getting it fixed that'd be great. :) Attached the current version that I have. For testing you'll need your own MoinMoin installation. Then replace the included text_plain.py with the attached version. Then test it with for example: http://localhost/wiki/SomePage?action=format;mimetype=text/plain

3 5

Re: [Dovecot] I keep getting password mismatches
by Mark 16 Mar '07

16 Mar '07

i`m still not getting in.. i now have this error:Feb 17 23:48:42 School-Mail dovecot: Dovecot v1.0.rc15 starting upFeb 17 23:49:04 School-Mail dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AG1hcmsAbWFyaw==Feb 17 23:49:04 School-Mail dovecot: auth(default): pam(mark,127.0.0.1): pam_authenticate() failed: Authentication failureFeb 17 23:49:05 School-Mail dovecot: imap-login: Disconnected: user=<mark>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, securedFeb 17 23:49:05 School-Mail dovecot: auth(default): client out: FAIL 1 user=markand just to be sure.. here is my dovecot.conf file:## Dovecot configuration file# If you're in a hurry, see http://wiki.dovecot.org/QuickConfiguration# '#' character and everything after it is treated as comments. Extra spaces# and tabs are ignored. If you want to use either of these explicitly, put the# value inside quotes, eg.: key = "# char and trailing whitespace "# Default values are shown for each setting, it's not required to uncomment# any of the lines.# Base directory where to store runtime data.#base_dir = /var/run/dovecot/# Protocols we want to be serving: imap imaps pop3 pop3s# If you only want to use dovecot-auth, you can set this to "none".#protocols = imap imaps pop3 pop3sprotocols = imap pop3# IP or host address where to listen in for connections. It's not currently# possible to specify multiple addresses. "*" listens in all IPv4 interfaces.# "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4# interfaces depending on the operating system.## If you want to specify ports for each service, you will need to configure# these settings inside the protocol imap/pop3 { ... } section, so you can# specify different ports for IMAP/POP3. For example:# protocol imap {# listen = *:10143# ssl_listen = *:10943# ..# }# protocol pop3 {# listen = *:10100# ..# }#listen = [::]listen =# Disable LOGIN command and all other plaintext authentications unless# SSL/TLS is used (LOGINDISABLED capability). Note that if the remote IP# matches the local IP (ie. you're connecting from the same computer), the# connection is considered secure and plaintext authentication is allowed.disable_plaintext_auth = no# Should all IMAP and POP3 processes be killed when Dovecot master process# shuts down. Setting this to "no" means that Dovecot can be upgraded without# forcing existing client connections to close (although that could also be# a problem if the upgrade is eg. because of a security fix). This however# means that after master process has died, the client processes can't write# to log files anymore.#shutdown_clients = yes#### Logging### Use this logfile instead of syslog(). /dev/stderr can be used if you want to# use stderr for logging (ONLY /dev/stderr - otherwise it is closed).#log_path =# For informational messages, use this logfile instead of the default#info_log_path =# Prefix for each line written to log file. % codes are in strftime(3)# format.#log_timestamp = "%b %d %H:%M:%S "# Syslog facility to use if you're logging to syslog. Usually if you don't# want to use "mail", you'll use local0..local7. Also other standard# facilities are supported.#syslog_facility = mail#### SSL settings### IP or host address where to listen in for SSL connections. Defaults# to above if not specified.#ssl_listen =ssl_listen =# Disable SSL/TLS support.#ssl_disable = no# PEM encoded X.509 SSL/TLS certificate and private key. They're opened before# dropping root privileges, so keep the key file unreadable by anyone but# root. Included doc/mkcert.sh can be used to easily generate self-signed# certificate, just make sure to update the domains in dovecot-openssl.cnf#ssl_cert_file = /etc/pki/dovecot/certs/dovecot.pem#ssl_key_file = /etc/pki/dovecot/private/dovecot.pem# If key file is password protected, give the password here. Alternatively# give it when starting dovecot with -p parameter.#ssl_key_password =# File containing trusted SSL certificate authorities. Usually not needed.# The CAfile should contain the CA-certificate(s) followed by the matching# CRL(s). CRL checking is new in dovecot .rc1#ssl_ca_file =# Request client to send a certificate.#ssl_verify_client_cert = no# How often to regenerate the SSL parameters file. Generation is quite CPU# intensive operation. The value is in hours, 0 disables regeneration# entirely.#ssl_parameters_regenerate = 168# SSL ciphers to use#ssl_cipher_list = ALL:!LOW# Show protocol level SSL errors.#verbose_ssl = no#### Login processes### Directory where authentication process places authentication UNIX sockets# which login needs to be able to connect to. The sockets are created when# running as root, so you don't have to worry about permissions. Note that# everything in this directory is deleted when Dovecot is started.#login_dir = /var/run/dovecot/login# chroot login process to the login_dir. Only reason not to do this is if you# wish to run the whole Dovecot without roots.# http://wiki.dovecot.org/Rootless#login_chroot = yes# User to use for the login process. Create a completely new user for this,# and don't use it anywhere else. The user must also belong to a group where# only it has access, it's used to control access for authentication process.# Note that this user is NOT used to access mails.# http://wiki.dovecot.org/UserIds#login_user = dovecot# Set max. process size in megabytes. If you don't use# login_process_per_connection you might need to grow this.#login_process_size = 32# Should each login be processed in it's own process (yes), or should one# login process be allowed to process multiple connections (no)? Yes is more# secure, espcially with SSL/TLS enabled. No is faster since there's no need# to create processes all the time.#login_process_per_connection = yes# Number of login processes to keep for listening new connections.#login_processes_count = 3# Maximum number of login processes to create. The listening process count# usually stays at login_processes_count, but when multiple users start logging# in at the same time more extra processes are created. To prevent fork-bombing# we check only once in a second if new processes should be created - if all# of them are used at the time, we double their amount until the limit set by# this setting is reached.#login_max_processes_count = 128# Maximum number of connections allowed per each login process. This setting# is used only if login_process_per_connection=no. Once the limit is reached,# the process notifies master so that it can create a new login process.# You should make sure that the process has at least# 16 + login_max_connections * 2 available file descriptors.#login_max_connections = 256# Greeting message for clients.#login_greeting = Dovecot ready.# Space-separated list of elements we want to log. The elements which have# a non-empty variable value are joined together to form a comma-separated# string.#login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c# Login log format. %$ contains login_log_format_elements string, %s contains# the data we want to log.#login_log_format = %$: %s#### Mailbox locations and namespaces### Location for users' mailboxes. This is the same as the old default_mail_env# setting. The default is empty, which means that Dovecot tries to find the# mailboxes automatically. This won't work if the user doesn't have any mail# yet, so you should explicitly tell Dovecot the full location.## If you're using mbox, giving a path to the INBOX file (eg. /var/mail/%u)# isn't enough. You'll also need to tell Dovecot where the other mailboxes are# and where Dovecot can place its index files. This is called the "root mail# directory", and it must be the first path given in the mail_location setting.## There are a few special variables you can use, eg.:## %u - username# %n - user part in user@domain, same as %u if there's no domain# %d - domain part in user@domain, empty if there's no domain# %h - home directory## See doc/variables.txt for full list. Some examples:## mail_location = maildir:~/Maildir# mail_location = mbox:~/mail:INBOX=/var/mail/%u# mail_location = mbox:/var/mail/%d/%1n/%n:INDEX=/var/indexes/%d/%1n/%n## http://wiki.dovecot.org/MailLocation##mail_location =# If you need to set multiple mailbox locations or want to change default# namespace settings, you can do it by defining namespace sections:## You can have private, shared and public namespaces. The only difference# between them is how Dovecot announces them to client via NAMESPACE# extension. Shared namespaces are meant for user-owned mailboxes which are# shared to other users, while public namespaces are for more globally# accessible mailboxes.## REMEMBER: If you add any namespaces, the default namespace must be added# explicitly, ie. mail_location does nothing unless you have a namespace# without a location setting. Default namespace is simply done by having a# namespace with empty prefix.#namespace private { # Hierarchy separator to use. You should use the same separator for all # namespaces or some clients get confused. '/' is usually a good one. # The default however depends on the underlying mail storage format. #separator = # Prefix required to access this namespace. This needs to be different for # all namespaces. For example "Public/". #prefix = # Physical location of the mailbox. This is in same format as # mail_location, which is also the default for it. #location = # There can be only one INBOX, and this setting defines which namespace # has it. #inbox = yes # If namespace is hidden, it's not advertised to clients via NAMESPACE # extension or shown in LIST replies. This is mostly useful when converting # from another server with different namespaces which you want to depricate # but still keep working. For example you can create hidden namespaces with # prefixes "~/mail/", "~%u/mail/" and "mail/". #hidden = yes#}# Grant access to these extra groups for mail processes. Typical use would be# to give "mail" group write access to /var/mail to be able to create dotlocks.#mail_extra_groups =# Allow full filesystem access to clients. There's no access checks other than# what the operating system does for the active UID/GID. It works with both# maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/# or ~user/.#mail_full_filesystem_access = no#### Mail processes### Enable mail process debugging. This can help you figure out why Dovecot# isn't finding your mails.#mail_debug = no# Log prefix for mail processes. See doc/variables.txt for list of possible# variables you can use.#mail_log_prefix = "%Us(%u): "# Use mmap() instead of read() to read mail files. read() seems to be a bit# faster with my Linux/x86 and it's better with NFS, so that's the default.# Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes.#mail_read_mmaped = no# Don't use mmap() at all. This is required if you store indexes to shared# filesystems (NFS or clustered filesystem).#mmap_disable = no# Don't write() to mmaped files. This is required for some operating systems# which use separate caches for them, such as OpenBSD.#mmap_no_write = no# Locking method for index files. Alternatives are fcntl, flock and dotlock.# Dotlocking uses some tricks which may create more disk I/O than other locking# methods. NOTE: If you use NFS, remember to change also mmap_disable setting!#lock_method = fcntl# Drop all privileges before exec()ing the mail process. This is mostly# meant for debugging, otherwise you don't get core dumps. It could be a small# security risk if you use single UID for multiple users, as the users could# ptrace() each others processes then.#mail_drop_priv_before_exec = no# Show more verbose process titles (in ps). Currently shows user name and# IP address. Useful for seeing who are actually using the IMAP processes# (eg. shared mailboxes or if same uid is used for multiple accounts).#verbose_proctitle = no# Valid UID range for users, defaults to 500 and above. This is mostly# to make sure that users can't log in as daemons or other system users.# Note that denying root logins is hardcoded to dovecot binary and can't# be done even if first_valid_uid is set to 0.#first_valid_uid = 500#last_valid_uid = 0# Valid GID range for users, defaults to non-root/wheel. Users having# non-valid GID as primary group ID aren't allowed to log in. If user# belongs to supplementary groups with non-valid GIDs, those groups are# not set.#first_valid_gid = 1#last_valid_gid = 0# Maximum number of running mail processes. When this limit is reached,# new users aren't allowed to log in.#max_mail_processes = 1024# Set max. process size in megabytes. Most of the memory goes to mmap()ing# files, so it shouldn't harm much even if this limit is set pretty high.#mail_process_size = 256# Maximum allowed length for mail keyword name. It's only forced when trying# to create new keywords.#mail_max_keyword_length = 50# Default umask to use for mail files and directories.#umask = 0077# ':' separated list of directories under which chrooting is allowed for mail# processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too).# This setting doesn't affect login_chroot or auth_chroot variables.# WARNING: Never add directories here which local users can modify, that# may lead to root exploit. Usually this should be done only if you don't# allow shell access for users. See doc/configuration.txt for more information.#valid_chroot_dirs =# Default chroot directory for mail processes. This can be overridden for# specific users in user database by giving /./ in user's home directory# (eg. /home/./user chroots into /home). Note that usually there is no real# need to do chrooting, Dovecot doesn't allow users to access files outside# their mail directory anyway.#mail_chroot =#### Mailbox handling optimizations### Space-separated list of fields to initially save into cache file. Currently# these fields are allowed:## flags, date.sent, date.received, size.virtual, size.physical# mime.parts, imap.body, imap.bodystructure## Different IMAP clients work in different ways, so they benefit from# different cached fields. Some do not benefit from them at all. Caching more# than necessary generates useless disk I/O, so you don't want to do that# either.## Dovecot attempts to automatically figure out what client wants and it keeps# only that. However the first few times a mailbox is opened, Dovecot hasn't# yet figured out what client needs, so it may not perform optimally. If you# know what fields the majority of your clients need, it may be useful to set# these fields by hand. If client doesn't actually use them, Dovecot will# eventually drop them.## Usually you should just leave this field alone. The potential benefits are# typically unnoticeable.#mail_cache_fields =# Space-separated list of fields that Dovecot should never save to cache file.# Useful if you want to save disk space at the cost of more I/O when the fields# needed.#mail_never_cache_fields =# The minimum number of mails in a mailbox before updates are done to cache# file. This allows optimizing Dovecot's behavior to do less disk writes at# the cost of more disk reads.#mail_cache_min_mail_count = 0# When IDLE command is running, mailbox is checked once in a while to see if# there are any new mails or other changes. This setting defines the minimum# time to wait between those checks. Dovecot is however able to use dnotify# and inotify with Linux to reply immediately after the change occurs.#mailbox_idle_check_interval = 30# Save mails with CR+LF instead of plain LF. This makes sending those mails# take less CPU, especially with sendfile() syscall with Linux and FreeBSD.# But it also creates a bit more disk I/O which may just make it slower.# Also note that if other software reads the mboxes/maildirs, they may handle# the extra CRs wrong and cause problems.#mail_save_crlf = no#### Maildir-specific settings### By default LIST command returns all entries in maildir beginning with dot.# Enabling this option makes Dovecot return only entries which are directories.# This is done by stat()ing each entry, so it causes more disk I/O.# (For systems setting struct dirent->d_type, this check is free and it's# done always regardless of this setting)#maildir_stat_dirs = no# Copy mail to another folders using hard links. This is much faster than# actually copying the file. This is problematic only if something modifies# the mail in one folder but doesn't want it modified in the others. I don't# know any MUA which would modify mail files directly. IMAP protocol also# requires that the mails don't change, so it would be problematic in any case.# If you care about performance, enable it.#maildir_copy_with_hardlinks = no#### mbox-specific settings### Which locking methods to use for locking mbox. There are four available:# dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe# solution. If you want to use /var/mail/ like directory, the users# will need write access to that directory.# fcntl : Use this if possible. Works with NFS too if lockd is used.# flock : May not exist in all systems. Doesn't work with NFS.# lockf : May not exist in all systems. Doesn't work with NFS.## You can use multiple locking methods; if you do the order they're declared# in is important to avoid deadlocks if other MTAs/MUAs are using multiple# locking methods as well. Some operating systems don't allow using some of# them simultaneously.#mbox_read_locks = fcntl#mbox_write_locks = fcntl# Maximum time in seconds to wait for lock (all of them) before aborting.#mbox_lock_timeout = 300# If dotlock exists but the mailbox isn't modified in any way, override the# lock file after this many seconds.#mbox_dotlock_change_timeout = 120# When mbox changes unexpectedly we have to fully read it to find out what# changed. If the mbox is large this can take a long time. Since the change# is usually just a newly appended mail, it'd be faster to simply read the# new mails. If this setting is enabled, Dovecot does this but still safely# fallbacks to re-reading the whole mbox file whenever something in mbox isn't# how it's expected to be. The only real downside to this setting is that if# some other MUA changes message flags, Dovecot doesn't notice it immediately.# Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK# commands.#mbox_dirty_syncs = yes# Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE,# EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored.#mbox_very_dirty_syncs = no# Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK# commands and when closing the mailbox). This is especially useful for POP3# where clients often delete all mails. The downside is that our changes# aren't immediately visible to other MUAs.#mbox_lazy_writes = yes# If mbox size is smaller than this (in kilobytes), don't write index files.# If an index file already exists it's still read, just not updated.#mbox_min_index_size = 0#### dbox-specific settings### Maximum dbox file size in kilobytes until it's rotated.#dbox_rotate_size = 2048# Minimum dbox file size in kilobytes before it's rotated# (overrides dbox_rotate_days)#dbox_rotate_min_size = 16# Maximum dbox file age in days until it's rotated. Day always begins from# midnight, so 1 = today, 2 = yesterday, etc. 0 = check disabled.#dbox_rotate_days = 0#### IMAP specific settings##protocol imap { # Login executable location. #login_executable = /usr/libexec/dovecot/imap-login # IMAP executable location. Changing this allows you to execute other # binaries before the imap process is executed. # # This would write rawlogs into ~/dovecot.rawlog/ directory: # mail_executable = /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap # # This would attach gdb into the imap process and write backtraces into # /tmp/gdbhelper.* files: # mail_executable = /usr/libexec/dovecot/gdbhelper /usr/libexec/dovecot/imap # #mail_executable = /usr/libexec/dovecot/imap # Maximum IMAP command line length in bytes. Some clients generate very long # command lines with huge mailboxes, so you may need to raise this if you get # "Too long argument" or "IMAP command line too large" errors often. #imap_max_line_length = 65536 # Support for dynamically loadable plugins. mail_plugins is a space separated # list of plugins to load. #mail_plugins = #mail_plugin_dir = /usr/lib/dovecot/imap # Send IMAP capabilities in greeting message. This makes it unnecessary for # clients to request it with CAPABILITY command, so it saves one round-trip. # Many clients however don't understand it and ask the CAPABILITY anyway. #login_greeting_capability = no # Override the IMAP CAPABILITY response. #imap_capability = # Workarounds for various client bugs: # delay-newmail: # Send EXISTS/RECENT new mail notifications only when replying to NOOP # and CHECK commands. Some clients ignore them otherwise, for example # OSX Mail. Outlook Express breaks more badly though, without this it # may show user "Message no longer in server" errors. Note that OE6 still # breaks even with this workaround if synchronization is set to # "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. # netscape-eoh: # Netscape 4.x breaks if message headers don't end with the empty "end of # headers" line. Normally all messages have this, but setting this # workaround makes sure that Netscape never breaks by adding the line if # it doesn't exist. This is done only for FETCH BODY[HEADER.FIELDS..] # commands. Note that RFC says this shouldn't be done. # tb-extra-mailbox-sep: # With mbox storage a mailbox can contain either mails or submailboxes, # but not both. Thunderbird separates these two by forcing server to # accept '/' suffix in mailbox names in subscriptions list. # The list is space-separated. #imap_client_workarounds = outlook-idle}#### POP3 specific settings##protocol pop3 { # Login executable location. #login_executable = /usr/libexec/dovecot/pop3-login # POP3 executable location. See IMAP's mail_executable above for examples # how this could be changed. #mail_executable = /usr/libexec/dovecot/pop3 # Don't try to set mails non-recent or seen with POP3 sessions. This is # mostly intended to reduce disk I/O. With maildir it doesn't move files # from new/ to cur/, with mbox it doesn't write Status-header. #pop3_no_flag_updates = no # Support LAST command which exists in old POP3 specs, but has been removed # from new ones. Some clients still wish to use this though. Enabling this # makes RSET command clear all \Seen flags from messages. #pop3_enable_last = no # If mail has X-UIDL header, use it as the mail's UIDL. #pop3_reuse_xuidl = no # Keep the mailbox locked for the entire POP3 session. #pop3_lock_session = no # POP3 UIDL format to use. You can use following variables: # # %v - Mailbox UIDVALIDITY # %u - Mail UID # %m - MD5 sum of the mailbox headers in hex (mbox only) # %f - filename (maildir only) # # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier version 0 : %f # Courier version 1 : %u # Courier version 2 : %v-%u # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # Older Dovecots : %v.%u # tpop3d : %Mf # # Note that Outlook 2003 seems to have problems with %v.%u format which was # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. # # NOTE: Nowadays this is required to be set explicitly, since the old # default was bad but it couldn't be changed without breaking existing # installations. %08Xu%08Xv will be the new default, so use it for new # installations. # #pop3_uidl_format = %08Xu%08Xv # POP3 logout format string: # %t - number of TOP commands # %p - number of bytes sent to client as a result of TOP command # %r - number of RETR commands # %b - number of bytes sent to client as a result of RETR command # %d - number of deleted messages # %m - number of messages (before deletion) # %s - mailbox size in bytes (before deletion) #pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s # Support for dynamically loadable plugins. mail_plugins is a space separated # list of plugins to load. #mail_plugins = #mail_plugin_dir = /usr/lib/dovecot/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. # oe-ns-eoh: # Outlook Express and Netscape Mail breaks if end of headers-line is # missing. This option simply sends it if it's missing. # The list is space-separated. #pop3_client_workarounds =}#### LDA specific settings##protocol lda { # Address to use when sending rejection mails. postmaster_address = postmaster(a)example.com # Hostname to use in various parts of sent mails, eg. in Message-Id. # Default is the system's real hostname. #hostname = # Support for dynamically loadable plugins. mail_plugins is a space separated # list of plugins to load. #mail_plugins = #mail_plugin_dir = /usr/lib/dovecot/lda # Binary to use for sending mails. #sendmail_path = /usr/lib/sendmail # UNIX socket path to master authentication server to find users. #auth_socket_path = /var/run/dovecot/auth-master}#### Authentication processes### Executable location#auth_executable = /usr/libexec/dovecot/dovecot-auth# Set max. process size in megabytes.#auth_process_size = 256# Authentication cache size in kilobytes. 0 means it's disabled.# Note that bsdauth, PAM and vpopmail require cache_key to be set for caching# to be used. Also note that currently auth cache doesn't work very well if# you're using multiple passdbs with same usernames in them.#auth_cache_size = 0# Time to live in seconds for cached data. After this many seconds the cached# record is no longer used, *except* if the main database lookup returns# internal failure. We also try to handle password changes automatically: If# user's previous authentication was successful, but this one wasn't, the# cache isn't used. For now this works only with plaintext authentication.#auth_cache_ttl = 3600# Space separated list of realms for SASL authentication mechanisms that need# them. You can leave it empty if you don't want to support multiple realms.# Many clients simply use the first one listed here, so keep the default realm# first.#auth_realms =# Default realm/domain to use if none was specified. This is used for both# SASL realms and appending @domain to username in plaintext logins.#auth_default_realm =# List of allowed characters in username. If the user-given username contains# a character not listed in here, the login automatically fails. This is just# an extra check to make sure user can't exploit any potential quote escaping# vulnerabilities with SQL/LDAP databases. If you want to allow all characters,# set this value to empty.#auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@# Username character translations before it's looked up from databases. The# value contains series of from -> to characters. For example "#@/@" means# that '#' and '/' characters are translated to '@'.#auth_username_translation =# Username formatting before it's looked up from databases. You can use# the standard variables here, eg. %Lu would lowercase the username, %n would# drop away the domain if it was given, or "%n-AT-%d" would change the '@' into# "-AT-". This translation is done after auth_username_translation changes.#auth_username_format =# If you want to allow master users to log in by specifying the master# username within the normal username string (ie. not using SASL mechanism's# support for it), you can specify the separator character here. The format# is then <username><separator><master username>. UW-IMAP uses "*" as the# separator, so that could be a good choice.#auth_master_user_separator =# Username to use for users logging in with ANONYMOUS SASL mechanism#auth_anonymous_username = anonymous# More verbose logging. Useful for figuring out why authentication isn't# working.auth_verbose = yes# Even more verbose logging for debugging purposes. Shows for example SQL# queries.auth_debug = yes# In case of password mismatches, log the passwords and used scheme so the# problem can be debugged. Requires auth_debug=yes to be set.auth_debug_passwords = yes# Maximum number of dovecot-auth worker processes. They're used to execute# blocking passdb and userdb queries (eg. MySQL and PAM). They're# automatically created and destroyed as needed.#auth_worker_max_count = 30# Kerberos keytab to use for the GSSAPI mechanism. Will use the system# default (usually /etc/krb5.keytab) if not specified.#auth_krb5_keytab =auth default { # Space separated list of wanted authentication mechanisms: # plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi mechanisms = plain # # Password database is used to verify user's password (and nothing more). # You can have multiple passdbs and userdbs. This is useful if you want to # allow both system users (/etc/passwd) and virtual users to login without # duplicating the system users into virtual database. # # http://wiki.dovecot.org/PasswordDatabase # # By adding master=yes setting inside a passdb you make the passdb a list # of "master users", who can log in as anyone else. Unless you're using PAM, # you probably still want the destination user to be looked up from passdb # that it really exists. This can be done by adding pass=yes setting to the # master passdb. # # http://wiki.dovecot.org/MasterPassword # Users can be temporarily disabled by adding a passdb with deny=yes. # If the user is found from that database, authentication will fail. # The deny passdb should always be specified before others, so it gets # checked first. Here's an example: #passdb passwd-file { # File contains a list of usernames, one per line #args = /etc/dovecot.deny #deny = yes #} # PAM authentication. Preferred nowadays by most systems. # Note that PAM can only be used to verify if user's password is correct, # so it can't be used as userdb. If you don't want to use a separate user # database (passwd usually), you can use static userdb. # REMEMBER: You'll need /etc/pam.d/dovecot file created for PAM # authentication to actually work. # http://wiki.dovecot.org/PasswordDatabase/PAMpassdb pam { # use /etc/pam.d/imap and /etc/pam.d/pop3 args = *} # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. # http://wiki.dovecot.org/AuthDatabase/Passwd #passdb passwd { #} # /etc/shadow or similiar, using getspnam(). Deprecated by PAM nowadays. # http://wiki.dovecot.org/PasswordDatabase/Shadow #passdb shadow { #} # PAM-like authentication for OpenBSD. # http://wiki.dovecot.org/PasswordDatabase/BSDAuth #passdb bsdauth { # [cache_key=<key>] - See cache_key in PAM for explanation. #args = #} # passwd-like file with specified location # http://wiki.dovecot.org/AuthDatabase/PasswdFile #passdb passwd-file { # Path for passwd-file #args = #} # checkpassword executable authentication # NOTE: You will probably want to use "userdb prefetch" with this. # http://wiki.dovecot.org/PasswordDatabase/CheckPassword #passdb checkpassword { # Path for checkpassword binary #args = #} # SQL database # http://wiki.dovecot.org/AuthDatabase/SQL #passdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for example #args = #} # LDAP database # http://wiki.dovecot.org/AuthDatabase/LDAP #passdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example #args = #} # vpopmail authentication # http://wiki.dovecot.org/AuthDatabase/VPopMail #passdb vpopmail { # [cache_key=<key>] - See cache_key in PAM for explanation. #args = #} # # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # # http://wiki.dovecot.org/UserDatabase # # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. WARNING: nss_ldap is known to be broken # with Dovecot. Don't use it, or users might log in as each others! # http://wiki.dovecot.org/AuthDatabase/Passwd userdb passwd { } # passwd-like file with specified location # http://wiki.dovecot.org/AuthDatabase/PasswdFile #userdb passwd-file { # Path for passwd-file #args = #} # static settings generated from template # http://wiki.dovecot.org/UserDatabase/Static #userdb static { # Template for the fields. Can return anything a userdb could normally # return. For example: # # args = uid=500 gid=500 home=/var/mail/%u # #args = #} # SQL database # http://wiki.dovecot.org/AuthDatabase/SQL #userdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for example #args = #} # LDAP database # http://wiki.dovecot.org/AuthDatabase/LDAP #userdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example #args = #} # vpopmail # http://wiki.dovecot.org/AuthDatabase/VPopMail #userdb vpopmail { #} # "prefetch" user database means that the passdb already provided the # needed information and there's no need to do a separate userdb lookup. # This can be made to work with SQL and LDAP databases, see their example # configuration files for more information how to do it. # http://wiki.dovecot.org/UserDatabase/Prefetch #userdb prefetch { #} # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # That user is specified by userdb above. user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. # Note that valid_chroot_dirs isn't needed to use this setting. #chroot = # Number of authentication processes to create #count = 1 # Require a valid SSL client certificate or the authentication fails. #ssl_require_client_cert = no # Take the username from client's SSL certificate, using # X509_NAME_get_text_by_NID() which returns the subject's DN's # CommonName. #ssl_username_from_cert = no # It's possible to export the authentication interface to other programs: #socket listen { #master { # Master socket is typically used to give Dovecot's local delivery # agent access to userdb so it can find mailbox locations. It can # however also be used to disturb regular user authentications. # WARNING: Giving untrusted users access to master socket may be a # security risk, don't give too wide permissions to it! #path = /var/run/dovecot/auth-master #mode = 0600 # Default user/group is the one who started dovecot-auth (root) #user = #group = #} #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/run/dovecot/auth-client #mode = 0660 #} #}}# If you wish to use another authentication server than dovecot-auth, you can# use connect sockets. They assumed to be already running, Dovecot's master# process only tries to connect to them. They don't need any other settings# than the path for the master socket, as the configuration is done elsewhere.# Note that the client sockets must exist in the login_dir.#auth external {# socket connect {# master {# path = /var/run/dovecot/auth-master# }# }#}#### Dictionary server settings### Dictionary can be used by some plugins to store key=value lists.# Currently this is only used by dict quota backend. The dictionary can be# used either directly or though a dictionary server. The following dict block# maps dictionary names to URIs when the server is used. These can then be# referenced using URIs in format "proxy:<name>".dict { #quota = mysql:/etc/dovecot-dict-quota.conf}#### Plugin settings##plugin { # Here you can give some extra environment variables to mail processes. # This is mostly meant for passing parameters to plugins. %variable # expansion is done for all values. # Quota plugin. Multiple backends are supported: # dirsize: Find and sum all the files found from mail directory # dict: Keep quota stored in dictionary (eg. SQL) # maildir: Maildir++ quota # fs: Read-only support for filesystem quota #quota = maildir # ACL plugin. vfile backend reads ACLs from "dovecot-acl" file from maildir # directory. You can also optionally give a global ACL directory path where # ACLs are applied to all users' mailboxes. The global ACL directory contains # one file for each mailbox, eg. INBOX or sub.mailbox. #acl = vfile:/etc/dovecot-acls # Convert plugin. If set, specifies the source storage path which is # converted to destination storage (mail_location). #convert_mail = mbox:%h/mail # Trash plugin. When saving a message would make user go over quota, this # plugin automatically deletes the oldest mails from configured mailboxes # until the message can be saved within quota limits. The configuration file # is a text file where each line is in format: <priority> <mailbox name> # Mails are first deleted in lowest -> highest priority number order #trash = /etc/dovecot-trash.conf}----------------and that is my dovecot.conf that comes with my dovecot installation automatically when i type: yum install dovecotif anyone is willing to share his dovecot.conf file.. ?? (a working one ofcause ;))Thanx.Mark. _________________________________________________________________ Probeer Live.com: jouw leven online met nieuws, sport, weer en nog veel meer. http://www.live.com/getstarted

3 3

[Dovecot] unable to connect to auth server
by Steven F Siirila 16 Mar '07

16 Mar '07

Upon rebooting our Dovecot server, I got these: Mar 16 09:49:16 peridot.tc.umn.edu dovecot: [ID 195972 local6.info] Dovecot v1.0.rc27 starting up Mar 16 09:49:18 myhost.mydomain dovecot: imap-login: Can't connect to auth server at default: Connection refused Mar 16 09:49:18 myhost.mydomain last message repeated 1 time Mar 16 09:49:18 myhost.mydomain dovecot: pop3-login: Can't connect to auth server at default: Connection refused Mar 16 09:49:18 myhost.mydomain dovecot: imap-login: Can't connect to auth server at default: Connection refused Mar 16 09:49:18 myhost.mydomain last message repeated 2 times Mar 16 09:49:18 myhost.mydomain dovecot: pop3-login: Can't connect to auth server at default: Connection refused Mar 16 09:49:18 myhost.mydomain last message repeated 2 times Mar 16 09:49:18 myhost.mydomain dovecot: imap-login: Can't connect to auth server at default: Connection refused Mar 16 09:49:18 myhost.mydomain last message repeated 1 time Mar 16 09:49:18 myhost.mydomain dovecot: pop3-login: Can't connect to auth server at default: Connection refused Mar 16 09:49:18 myhost.mydomain dovecot: imap-login: Can't connect to auth server at default: Connection refused However, everything does work okay. I believe we ran into this once before and reported it and I had thought Timo fixed it. It seems that imap-login and pop3-login attempt to connect to the auth server before it is fully operational. I don't recall what the fix was supposed to change, but it doesn't seem to have fully fixed it. (We are running RC27 on Solaris 10) # /opt/dovecot/sbin/dovecot -n # /etc/opt/dovecot/dovecot.conf syslog_facility: local6 protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_cert_file: /etc/opt/openssl/certs/dovecot.pem ssl_key_file: /etc/opt/openssl/private/dovecot.pem shutdown_clients: no login_dir: /var/opt/dovecot/run/dovecot/login login_executable(default): /opt/dovecot/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot/libexec/dovecot/imap-login login_executable(pop3): /opt/dovecot/libexec/dovecot/pop3-login login_processes_count: 32 login_max_processes_count: 4096 max_mail_processes: 8192 first_valid_uid: 100 default_mail_env: mbox:~/:INBOX=/var/mail/%u mail_location: mbox:~/:INBOX=/var/mail/%u mail_full_filesystem_access: yes mbox_lazy_writes: no mail_executable(default): /opt/dovecot/libexec/dovecot/imap mail_executable(imap): /opt/dovecot/libexec/dovecot/imap mail_executable(pop3): /opt/dovecot/libexec/dovecot/pop3 mail_plugin_dir(default): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /opt/dovecot/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv namespace: type: private separator: / location: mbox:~/:INBOX=/var/mail/%u inbox: yes hidden: yes auth default: username_format: %Lu verbose: yes debug: yes passdb: driver: pam args: session=yes * userdb: driver: passwd -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

2 1

[Dovecot] crypt missing (configure problem)
by Fabio Busatto 16 Mar '07

16 Mar '07

Hi, I need some feedback for the following problem I encountered compiling dovecot. It seems to be a wrong check in configure, that comes out in a fatal error (crypt symbol not found because the -lcrypt is omitted). With these configure parameters no crypt module is recognized (and so the need_crypt variable is still off), but at compile time gcc fails to create executables. I solve the issue forcing the need_crypt variable to on in configure, but maybe it can be solved clearly adding the right checks. Here is some info: Dovecot: tested on 1.0.rc17 and 1.0.rc27 OS: linux Configuration parameters: ./configure --without-passwd \ --without-passwd-file \ --without-shadow \ --without-pam \ --without-bsdauth \ --without-gssapi \ --without-sia \ --without-ldap \ --without-vpopmail \ --without-static-userdb \ --without-sql \ --without-pgsql \ --without-mysql \ --without-sqlite \ --without-deliver \ --without-sql-drivers \ --with-storages=maildir \ --disable-ipv6 Here there are the errors: Making all in auth make[3]: Entering directory `/usr/src/dovecot-1.0.rc27/src/auth' /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -export-dynamic -o dovecot-auth auth.o auth-cache.o auth-client-connection.o auth-master-connection.o auth-master-listener.o auth-module.o auth-request.o auth-request-handler.o auth-stream.o auth-worker-client.o auth-worker-server.o db-ldap.o db-sql.o db-passwd-file.o main.o mech.o mech-anonymous.o mech-plain.o mech-login.o mech-cram-md5.o mech-digest-md5.o mech-ntlm.o mech-gssapi.o mech-rpa.o mech-apop.o passdb.o passdb-blocking.o passdb-bsdauth.o passdb-cache.o passdb-ldap.o passdb-passwd.o passdb-passwd-file.o passdb-pam.o passdb-checkpassword.o passdb-shadow.o passdb-sia.o passdb-vpopmail.o passdb-sql.o userdb.o userdb-blocking.o userdb-ldap.o userdb-passwd.o userdb-passwd-file.o userdb-prefetch.o userdb-static.o userdb-vpopmail.o userdb-sql.o libpassword.a ../lib-settings/libsettings.a ../lib-ntlm/libntlm.a ../lib-sql/libsql.a ../lib/liblib.a -export-dynamic -ldl gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -o dovecot-auth auth.o auth-cache.o auth-client-connection.o auth-master-connection.o auth-master-listener.o auth-module.o auth-request.o auth-request-handler.o auth-stream.o auth-worker-client.o auth-worker-server.o db-ldap.o db-sql.o db-passwd-file.o main.o mech.o mech-anonymous.o mech-plain.o mech-login.o mech-cram-md5.o mech-digest-md5.o mech-ntlm.o mech-gssapi.o mech-rpa.o mech-apop.o passdb.o passdb-blocking.o passdb-bsdauth.o passdb-cache.o passdb-ldap.o passdb-passwd.o passdb-passwd-file.o passdb-pam.o passdb-checkpassword.o passdb-shadow.o passdb-sia.o passdb-vpopmail.o passdb-sql.o userdb.o userdb-blocking.o userdb-ldap.o userdb-passwd.o userdb-passwd-file.o userdb-prefetch.o userdb-static.o userdb-vpopmail.o userdb-sql.o -Wl,--export-dynamic libpassword.a ../lib-settings/libsettings.a ../lib-ntlm/libntlm.a ../lib-sql/libsql.a ../lib/liblib.a -ldl libpassword.a(mycrypt.o)(.text+0x5): In function `mycrypt': /usr/src/dovecot-1.0.rc27/src/auth/mycrypt.c:20: undefined reference to `crypt' collect2: ld returned 1 exit status make[3]: *** [dovecot-auth] Error 1 Making all in util make[3]: Entering directory `/usr/src/dovecot-1.0.rc27/src/util' /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -o dovecotpw dovecotpw.o ../auth/libpassword.a ../lib-ntlm/libntlm.a ../lib/liblib.a -export-dynamic -ldl gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -o dovecotpw dovecotpw.o -Wl,--export-dynamic ../auth/libpassword.a ../lib-ntlm/libntlm.a ../lib/liblib.a -ldl ../auth/libpassword.a(mycrypt.o)(.text+0x5): In function `mycrypt': /usr/src/dovecot-1.0.rc27/src/auth/mycrypt.c:20: undefined reference to `crypt' collect2: ld returned 1 exit status make[3]: *** [dovecotpw] Error 1 Bye Fabio -- Fabio Busatto <fabio.busatto(a)sikurezza.org>

2 3

[Dovecot] BUG: Unexpected input from auth master:
by Justin McAleer 16 Mar '07

16 Mar '07

deliver logs the error in the subject whenever the userdb lookup fails. I had a query discrepancy between postfix and dovecot, so messages were accepted that shouldn't have been, but I figured deliver should probably handle that a bit more gracefully :)

2 1

[Dovecot] Bug in dovecot 1.0 rc27
by Adrian P. van Bloois 16 Mar '07

16 Mar '07

Hi, My compiler AIX 5.2, complained about the following: cc -qlanglvl=ansi -DHAVE_CONFIG_H -I. -I../../../.. -I../../../../src/lib -I../../../../src/lib-mail -I../../../../src/lib-imap -I../../../../src/lib-index -I../../../../src/lib-storage -I../../../../src/lib-storage/index -I/usr/local/include -O2 -c mbox-file.c "mbox-sync-private.h", line 50.17: 1506-009 (S) Bit-field uid_broken must be of type signed int, unsigned int or int. "mbox-sync-private.h", line 51.17: 1506-009 (S) Bit-field expunged must be of type signed int, unsigned int or int. "mbox-sync-private.h", line 52.17: 1506-009 (S) Bit-field pseudo must be of type signed int, unsigned int or int. After changing these variables to uint32_t everything went fine, AND workts fine too. Adrian -- Adrian P. van Bloois Postbus 2575 email: adrian(a)accu.uu.nl 3500 GN Utrecht voice: +31-(0)-30-68-94649 The Netherlands fax: +31-30-68-94649 The whole point of cooking is to get as much flavour out of the ingredients as possible. -- Delia Smith

2 1

[Dovecot] sasl authentication via dovecot
by Frank Church 16 Mar '07

16 Mar '07

I am setting up a Postfix/Dovecot/Virtual Domains system, with virtual tables using Postfixadmin and MySQL. Incoming mail is accepted for the virtual mailboxes, but when I try to retrieve mail from Outlook or Thunderbird I get errors You cannot log in to abc.server.net because the server has disabled login. You may need to connect via SSL or TLS. Please check the account settings for your mail server As Dovecot is handling the auth I suspect that it is where the problem lies. Are they any faults in the settings below that could be the cause? As I understand it because Dovecot is handling the login and monitoring the IMAP and POP ports. All the initial authentication is supposed to be handled there before Postfix gets involved. Running lsof -i:port on ports 110, 143, 993 and 995 shows that dovecot is handling all those inbound connections. I am also seeing messages in the log as follows dovecot: imap-login: Aborted login: rip:81.150.x.x, lip=66.90.x.x my auth section in Dovecot is as follows auth default { mechanisms = plain login passdb sql { args = /etc/dovecot/sql.conf } userdb sql { args = /etc/dovecot/sql.conf } userdb prefetch { } user = nobody socket listen { master { # path = /var/run/dovecot/auth-master path = /usr/local/var/run/dovecot/auth-master mode = 0660 user = vmail group = mail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = mail } } } My sql.conf is as follows driver = mysql connect = host=localhost dbname=postfix user=dovecot password=password user_query = SELECT concat('/var/vmail/', maildir) as home, concat('maildir:/var/vmail/', maildir) as mail, 601 AS uid, 12 AS gid, concat('dirsize:storage=', quota) AS quota FROM mailbox WHERE username = '%u' AND active = '1' password_query = SELECT username as user, password, concat('/var/vmail/', maildir) as userdb_home, concat('maildir:/var/vmail/', maildir) as userdb_mail, 601 as userdb_uid, 12 as userdb_gid FROM mailbox WHERE username = '%u' AND active = '1' this is the smtpd section from main.cn # ---------------------- SASL PART START ---------------------- smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes #smtpd_sasl_local_domain = $myhostname smtpd_sasl_exceptions_networks = $mynetworks smtpd_sasl_security_options = noanonymous broken_sasl_auth_clients = yes # ---------------------- SASL PART END ----------------------

2 1

Re: [Dovecot] rc22 segv when over quota
by Steffen Kaiser 16 Mar '07

16 Mar '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 20 Feb 2007, Steffen Kaiser wrote: I have rebuilt rc23 to use "poll" instead of epoll, the same problem: warning: Can't read pathname for load map: Input/output error. Reading symbols from /lib/tls/i686/cmov/libdl.so.2...done. Loaded symbols for /lib/tls/i686/cmov/libdl.so.2 Reading symbols from /lib/tls/i686/cmov/libc.so.6...done. Loaded symbols for /lib/tls/i686/cmov/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /usr/local/lib/dovecot/imap/lib10_quota_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib10_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib11_imap_quota_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib11_imap_quota_plugin.so Core was generated by `imap [dvtest 10.20.10.63]'. Program terminated with signal 11, Segmentation fault. #0 mailbox_save_continue (ctx=0x80df574) at mail-storage.c:530 530 return ctx->transaction->box->v.save_continue(ctx); (gdb) bt full #0 mailbox_save_continue (ctx=0x80df574) at mail-storage.c:530 No locals. #1 0x08057193 in client_input (context=0x80df530) at cmd-append.c:67 client = (struct client *) 0x32c cmd = (struct client_command_context *) 0x80e27c0 #2 0x080ba522 in io_loop_handler_run (ioloop=0x80dd9b0) at ioloop-poll.c:199 ctx = (struct ioloop_handler_context *) 0x80dd9d8 pollfd = <value optimized out> tv = {tv_sec = 4, tv_usec = 762810} io = (struct io *) 0x80df610 t_id = 2 msecs = <value optimized out> ret = 135132464 call = <value optimized out> #3 0x080b9868 in io_loop_run (ioloop=0x80dd9b0) at ioloop.c:284 No locals. #4 0x08063910 in main (argc=Cannot access memory at address 0x8d4 ) at main.c:285 No locals. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRdr7NS9SORjhbDpvAQKXQQf/VHx/LEaC5zvz3C17iPuCSjro1Q9jznw2 GQA3FStiWhP3NsckSSQ+RxB8ih+lf+A8o2+nhF+pJ7N6qcBK3BVkum+WjQW5ddDv IEiAeo+dtFaP+7sO+qJeuq4ImXpiMDGpUVRt+PJYC1cAxWx+HYQ8im5UXEP4eTz7 uMu7MAX9vjwsWHmrfKMJf/36VQpTajMsfrfYbbTPPva++kuuNI33RIDvCeOsSmVF Vu38mRzP+wvwi/4YRV6UciVfrXV7sBl9Tk3oJjdEkn3gbxWPMfBYENxNRhAsj158 m+Zqz/bTJuThWlUFFM6uM/HDNrO39N3oWcHAJb7+zt8ULVMbD2WuVA== =9Ba1 -----END PGP SIGNATURE-----

2 10

[Dovecot] Warn before overquota
by Joan 16 Mar '07

16 Mar '07

Looking in the archives I found a message from dominik.saar(a)1und1.de on the 16/08/06, that is asking for a system to control the overquota warnings from within dovecot or dovecot LDA. The proposed solution is to use exim as MTA, since it has build in support. In my case I'm using postfix, what would be the recommended approach in that case? I was thinking of something like the cyrus LDA that you can with deliverquota [ -w percent ], something like that in a quota aware LDA would be quite useful for me. Any proposed solution would be welcome. Thanks

2 3

[Dovecot] running DC and UWIMAP on the same box
by Stewart Dean 15 Mar '07

15 Mar '07

It never hurts to ask...... I am bringing up DC on my production mailserver (which runs UWIMAP for production IMAP service) to learn and test it, much as I did when I introduced SSL protected IMAP, using an unpublicized non-standard port. The folder and mailbox location and format will remain the same. Questions: 1) Will DC be building indices for everything or just for the userid that I use to request client service for? 2) Are there any pitfalls others have experience doing this? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

3 2

[Dovecot] Postfix+Dovecot+LDAP
by Ejay Hire 15 Mar '07

15 Mar '07

This message does not contain a bug report or any issues. It is a summary of my experiences with Postfix, Dovecot, and Ldap. 1. Do not use Dovecot 0.99, even if it's what your vendor has packaged. 1a. ... When you upgrade past 0.99, you'll get some double mail because of UIDL's. 2. Do not use PAM and Ldap and then let dovecot talk to pam. It is bad. Don't do it. 2a. Unless you like users digging around in random mailboxes. 2b. NSCD is broken and should not be trusted. 3. Dovecot+Ldap works, and works well. 3a. If you don't do "Auth Binds", it cuts the work on the ldap server in half. 3b. User Prefetch cuts that in half again. 4. Postfix+Ldap works, and works well. 4a. If your server is underspec'd, you may get the occassional "Temporary lookup failure" 400 error during periods of heavy load, specifically when backups are running. 5. OpenLdap works. 5a. When you run as ldap, the config files need to be owned by ldap. 5b. ... And the database 5c. ... And the schema 5d. Adding slapd_db_recover to the init script isn't a bad idea. 6. Don't be dumb. 6a. ... Like me. 6b. If you are using ldap to lookup the attribute mail, index the mail attribute. 6c. If you add an index to Openldap, you have to reindex the database with slapindex 6d. ... Or you bounce a lot of mail before you figure it out. 6e. Make sure you can login to the console and/or ssh if the ldap server dies. 6f. ... Be Really sure. 6g. The convert plugin can switch users between maildirs and mboxes. Ejay Hire IT Manager, Confidential Business Resources 615-665-5555 (office) 615-456-9813 (mobile)

5 13

[Dovecot] tb-negative-fetch workaround
by bofh list 15 Mar '07

15 Mar '07

Hi, I notice in the Changelog that the tb-negative-fetch workaround shouldn't be needed any longer. We have a user running Thunderbird 1.5.0.8 that is experiencing the same problem described in https://bugzilla.mozilla.org/show_bug.cgi?id=263904 The current command did not succeed. the mail server responded: error in imap command uid: invalid body[..] parameter. Missing '>' in '<12288.-7215>' Any ideas? Thanks!

4 12

[Dovecot] pop3 uidl when migrating from mbox to maildir
by Giuseppe Giacomini 15 Mar '07

15 Mar '07

Thank you for the reply of my previous post (http://www.dovecot.org/list/dovecot/2007-March/020716.html) now it works, but I have another question about migrating pop3 account (with leave mail on server) to maildir. On this post -> http://www.dovecot.org/list/dovecot/2006-February/011464.html you explain how to create dovecot-uidlist preserving UIDVALIDITY. Is there someone that have build a script to generate such dovecot-uidlist? thank you all

2 1

[Dovecot] [PATCH 0/5] fix gcc warnings in CVS HEAD
by Max Kellermann 15 Mar '07

15 Mar '07

Hi, I have rewritten the patches I submitted earlier today for the CVS HEAD. Some of the changes were already committed months ago. On 2007/03/15 12:30, Timo Sirainen <tss(a)iki.fi> wrote: > That's ok, but I'm not sure about bsearch_insert_pos(). It's the way it > is mostly because I wanted to keep bsearch() API. If it can't return > void * then maybe it could be easier to just change the whole API to > something like: One of the patches changes exactly that. Timo, please review this patch carefully, because I havn't tested them yet. Max

2 6

[Dovecot] Alerts and pre-authenticated connections
by Mike Brudenell 15 Mar '07

15 Mar '07

Greetings - Work moves onward here at setting up our Dovecot IMAP service and I've got a couple more questions, I'm afraid... :-} ============================================== Q1. The UW IMAP Server supports "pre-authenticated connections" -- does Dovecot? Specifically, it is possible to create a symlink from /etc/rimapd to the UW IMAP server binary and then use rsh or ssh from within the Pine mail client to execute that on the server to establish the IMAP connection: rsh imap.york.ac.uk /etc/rimapd Pine uses this to open a "pre-authenticated" connection to the UW IMAP server to avoid the user having to enter their username and password -- the rsh/ssh mechanism provides the IMAP server with the user's login name. I've grepped the Dovecot source but it looks like it doesn't support this. Am I right in thinking this? ============================================== Q2. The UW IMAP Server can issue "IMAP Alerts" The UW IMAP server can issue a sequence of one-line notices to mail clients using IMAP's ALERT mechanism. The notices are formed formed from each line in a systemwide file (if non-empty) and a per-user file (~/.imapalert). Many, but by no means all, mail clients display these notices to the user -- currently we use this mechanism to advise people who have totally run out of mail quota. I've grepped the Dovecot source for "alert" but it looks like the IMAP Alert mechanism isn't supported. Am I right in thinking this? ============================================== Cheers, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. *

2 7

[Dovecot] imap connection problems
by Ivan Pesin 15 Mar '07

15 Mar '07

Hi, Have encountered some strange behavior of dovecot: after few days of work (5-7 days, ~50 users, imap over ssl or tls) dovecot stops respond with "* OK Dovecot ready.". I.e. connection gets accepted, but no response from dovecot: [ivan@dyn-226 bin]$ telnet imap 143 Trying 192.168.100.9... Connected to imap.n-ix.com.ua (192.168.100.9). Escape character is '^]'. while obvious should be [ivan@dyn-226 bin]$ telnet imap 143 Trying 192.168.100.9... Connected to imap.n-ix.com.ua (192.168.100.9). Escape character is '^]'. * OK Dovecot ready. After dovecot restart everything works OK. This behavior we started to observe since rc24, before that on rc9 we didn't see that problem. Currently running on rc26. Any ideas? Thanks, Iv

2 2

[Dovecot] convert_mail plugin doesn't work
by Giuseppe Giacomini 15 Mar '07

15 Mar '07

Hi I'm trying to use convert_mail plugin to convert wu-imap mailbox to maildir. I'm using dovecot rc 27 on Centos 4.4 linux. I have user INBOX in /var/spool/mail/ and mbox file in mail ~/mail When I do the first login with a test user (test1), the plugin convert all the mbox under ~mail, but doesn't do any conversion on the INBOX (/var/spool/mail/test1). After conversion those are file in MailDir where .testmail is converted from ~mail all other folder (cur,new) are empty rwx------ 2 test1 persone 4096 Mar 15 11:59 cur drwx------ 2 test1 persone 4096 Mar 15 11:59 new drwx------ 5 test1 persone 4096 Mar 15 11:59 .testmail drwx------ 2 test1 persone 4096 Mar 15 11:59 tmp Why doesn't mail in /var/spool/mail/test1 be converted? Thanks This is my dovecot -n protocols: imap imaps pop3 pop3s ssl_cert_file: /usr/share/ssl/certs/dovecot.pem ssl_key_file: /usr/share/ssl/private/dovecot.pem disable_plaintext_auth: no login_dir: /var/run/dovecot-login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login first_valid_uid: 200 mail_location: maildir:%h/MailDir:INDEX=%h/.index/%u:CONTROL=%h/.control/%u mail_debug: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins: convert mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xv%08Xu pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: passdb: driver: pam userdb: driver: passwd plugin: convert_mail: mbox:%h/mail:INBOX=/var/spool/mail/%u convert_skip_broken_mailboxes: yes and this is maillog dovecot: POP3(test1): Loading modules from directory: /usr/lib/dovecot/pop3 dovecot: POP3(test1): Module loaded: /usr/lib/dovecot/pop3/lib20_convert_plugin.so dovecot: POP3(test1): Effective uid=10400, gid=502 dovecot: POP3(test1): mbox: data=/homeH2/t/test1/mail:INBOX=/var/spool/mail/test1 dovecot: POP3(test1): mbox: root=/homeH2/t/test1/mail, index=/homeH2/t/test1/mail, inbox=/var/spool/mail/test1 dovecot: POP3(test1): mbox: data=/homeH2/t/test1/mail:INBOX=/var/spool/mail/test1 dovecot: POP3(test1): mbox: root=/homeH2/t/test1/mail, index=/homeH2/t/test1/mail, inbox=/var/spool/mail/test1 dovecot: POP3(test1): maildir: data=/homeH2/t/test1/MailDir:INDEX=/homeH2/t/test1/.index/test1:CONTROL=/homeH2/t/test1/.control/ test1 dovecot: POP3(test1): maildir: root=/homeH2/t/test1/MailDir, index=/homeH2/t/test1/.index/test1, control=/homeH2/t/test1/.contro l/test1, inbox= dovecot: POP3(test1): maildir: data=/homeH2/t/test1/MailDir:INDEX=/homeH2/t/test1/.index/test1:CONTROL=/homeH2/t/test1/.control/ test1 dovecot: POP3(test1): maildir: root=/homeH2/t/test1/MailDir, index=/homeH2/t/test1/.index/test1, control=/homeH2/t/test1/.contro l/test1, inbox= dovecot: POP3(test1): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0

2 1

Re: [Dovecot] Benchmarking CVS HEAD vs. v1.0
by Bill Boebel 15 Mar '07

15 Mar '07

On Wed, March 14, 2007 11:51 am, Timo Sirainen <tss(a)iki.fi> said: > Some new features in CVS HEAD are: > > - Mailbox list index. LIST command can be handled by reading the > mailboxes from the index. The index also contains the mailbox's message > counters, so STATUS command can be handled by only looking into the > index file. Nice. Now that it can pull this from index files, it would be pretty sweet if there was a variant of the STATUS command that would provide STATUS information for all mailboxes at once, rather than just for one. This could be used by webmail applications to update a folder listing that shows unseen mail counters with one command. Like maybe: a1 X-LIST-STATUS (MESSAGES UNSEEN) * X-LIST-STATUS "INBOX" (MESSAGES 8 UNSEEN 0) * X-LIST-STATUS "Drafts" (MESSAGES 0 UNSEEN 0) * X-LIST-STATUS "Trash" (MESSAGES 89 UNSEEN 3) a1 OK X-LIST-STATUS complete.

3 3

[Dovecot] [PATCH] fix gcc warnings in 1.0rc26
by Max Kellermann 15 Mar '07

15 Mar '07

Hi, I have made a small patchset to fix some of the GCC warnings. With these patches, I was able to compile dovecot r_1_0_rc26 with the following options: -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast Wstrict-prototypes -Wredundant-decls -Wcast-align -Wwrite-strings Wpacked -Winline -Wdisabled-optimization -Wno-long-long -Wundef Wfloat-equal -Wsign-compare -Waggregate-return -Werror Some of the changes may be arguable, escpecially the const warning fixes, example: char *pass = ""; I changed that to "pass = NULL" and changed the function call: - auth_request_verify_plain(request, pass, + auth_request_verify_plain(request, pass == NULL ? "" : pass, In other sources, I added "const" to parameters or to the return value where it seemed to make sense and didn't cause harm. Dealing with the const problem can be tricky, and sometimes dirty deconstification hacks are the only way to go.. however I believe we should always turn on "-Wconst" and explicitly add manual deconstitication where we assume it's not dangerous. I didn't fix all "const" and "missing noreturn" warnings, but my patches may be a good start... if there is further interest in fixing all of them, I'd be glad to do it. Max

2 1

[Dovecot] Problems with seen flag on OS X mail
by Nicolas Cianca 15 Mar '07

15 Mar '07

I'm having a problem with dovecot and apple mail not always remembering the seen flag. Some cases when mail is read it stays that way but other times it reverts back to unread on the next connection. I've tried to rebuild the Apple Mail mailbox but that doesn't do it. The mail is stored in Maildir format in the users home directory. All the connections Apple Mail are done via IMAP. I'm currently running rc27 on Centos and this has been ongoing since I switched from cyrus about 3 months ago. Any suggestions? nicolas cianca LIGHTBULB ncianca(a)lightbulb.com

2 1

[Dovecot] mbox and pop3, maildir and imap
by Hans Lammerts 15 Mar '07

15 Mar '07

Hi, Been reading a lot of posts about dovecot configuration, but can't really figure out if what I want is even possible or how to achieve this. My setup is simple : One linux machine that collects mail from my provider and sorts them for me and my wife, where my email is stored in Maildir format in ~myuser/.maildir and my wife's email is stored in mbox format in /var/spool/mail. Before making my wife crazy with a new way of getting and reading email with IMAP, I tried to do the following : My PC (not the linux server) runs either linux or XP, and the client I'm using is Evolution 2.8.2.2. I can get my email using IMAP without problems. My wife's PC just runs XP and the email client is Outlook which gets its email from the linux server through pop3. I've setup Dovecot to service both IMAP and POP3. The default_mail_env is now set to maildir:~%u/.maildir (which of course only reflects Evolution's IMAP need on my own PC) Now for the big question: How can I achieve that when I get email from the server using IMAP, I will automatically just look in the Maildir location (~%u/.maildir) __AND__ when my wife logs on through POP3, dovecot will only look for her email in her mbox directory /var/spool/mail/... ? In other words, different protocols used by (two) different users need to look for email in different locations (maildir and mbox). I tried to get this working using the Namespaces thingy in dovecot, but couldn't get it to work. Any suggestions (hyperlinks) are most welcome. Thanks, Hans

2 1

[Dovecot] solaris 10 + dovecot (1)
by aza zel 15 Mar '07

15 Mar '07

hi... i try to make dovecot (v1.0.r26) in solaris 10 and i have the following problem # ./configure --with-ldap ... ... Install prefix ...................... : /usr/local File offsets ........................ : 64bit I/O loop method ..................... : poll File change notification method ..... : none Building with SSL support ........... : yes (OpenSSL) Building with IPv6 support .......... : yes Building with pop3 server ........... : yes Building with mail delivery agent .. : yes Building with GSSAPI support ........ : no Building with user database modules . : static prefetch passwd passwd-file checkpassword ldap (modules) Building with password lookup modules : passwd passwd-file shadow pam checkpassword ldap (modules) Building with SQL drivers ............: # make ... ... Making all in pop3-login Making all in pop3 /bin/bash ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -I/usr/sfw/include -export-dynamic -o pop3 client.o commands.o mail-storage-callbacks.o main.o ../lib-storage/register/libstorage-register.a ../../src/lib-storage/index/maildir/libstorage_maildir.a ../../src/lib-storage/index/mbox/libstorage_mbox.a ../../src/lib-storage/index/dbox/libstorage_dbox.a ../../src/lib-storage/index/libstorage_index.a ../../src/lib-index/libindex.a ../lib-storage/libstorage.a ../lib-storage/subscription-file/libstorage_subscription_file.a ../lib-imap/libimap.a ../lib-mail/libmail.a ../lib-dict/libdict.a ../lib-charset/libcharset.a ../lib/liblib.a ../lib/mountpoint.o ../lib/str-sanitize.o -export-dynamic -lsocket -lnsl -lrt -lsendfile gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -I/usr/sfw/include -o pop3 client.o commands.o mail-storage-callbacks.o main.o ../lib/mountpoint.o ../lib/str-sanitize.o ../lib-storage/register/libstorage-register.a../../src/lib-storage/index/maildir/libstorage_maildir.a ../../src/lib-storage/index/mbox/libstorage_mbox.a ../../src/lib-storage/index/dbox/libstorage_dbox.a ../../src/lib-storage/index/libstorage_index.a ../../src/lib-index/libindex.a ../lib-storage/libstorage.a ../lib-storage/subscription-file/libstorage_subscription_file.a ../lib-imap/libimap.a ../lib-mail/libmail.a ../lib-dict/libdict.a ../lib-charset/libcharset.a ../lib/liblib.a -lsocket -lnsl -lrt -lsendfile ld: error de elf: archivo pop3: elf_update: Error de E/S: escritura en salida: No queda espacio de memoria en el dispositivo collect2: ld returned 1 exit status *** Error code 1 make: Fatal error: Command failed for target `pop3' Current working directory /maxi/dovecot-1.0.rc26/src/pop3 *** Error code 1 The following command caused the error: failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='lib lib-dict lib-sql lib-ntlm lib-settings lib-charset lib-mail lib-imap lib-index lib-storage lib-auth auth dict master login-common imap-login imap pop3-login pop3 deliver util plugins'; for subdir in $list; do \ echo "Making $target in $subdir"; \ if test "$subdir" = "."; then \ dot_seen=yes; \ local_target="$target-am"; \ else \ local_target="$target"; \ fi; \ (cd $subdir && make $local_target) \ || eval $failcom; \ done; \ if test "$dot_seen" = "no"; then \ make "$target-am" || exit 1; \ fi; test -z "$fail" make: Fatal error: Command failed for target `all-recursive' Current working directory /maxi/dovecot-1.0.rc26/src *** Error code 1 The following command caused the error: failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='src doc'; for subdir in $list; do \ echo "Making $target in $subdir"; \ if test "$subdir" = "."; then \ dot_seen=yes; \ local_target="$target-am"; \ else \ local_target="$target"; \ fi; \ (cd $subdir && make $local_target) \ || eval $failcom; \ done; \ if test "$dot_seen" = "no"; then \ make "$target-am" || exit 1; \ fi; test -z "$fail" make: Fatal error: Command failed for target `all-recursive' Current working directory /maxi/dovecot-1.0.rc26 *** Error code 1 make: Fatal error: Command failed for target `all' if i do # df -h Sistema de archivos tamaño usados aprovechar capacidad Montado en /dev/dsk/c0d0s0 4,4G 4,3G 57M 99% / /devices 0K 0K 0K 0% /devices ctfs 0K 0K 0K 0% /system/contract proc 0K 0K 0K 0% /proc mnttab 0K 0K 0K 0% /etc/mnttab swap 689M 652K 688M 1% /etc/svc/volatile objfs 0K 0K 0K 0% /system/object /usr/lib/libc/libc_hwcap1.so.1 4,4G 4,3G 57M 99% /lib/libc.so.1 fd 0K 0K 0K 0% /dev/fd swap 688M 40K 688M 1% /tmp swap 688M 24K 688M 1% /var/run /dev/dsk/c0d0s7 32G 583M 31G 2% /export/home /export/home/sunone 32G 583M 31G 2% /home/sunone ¿if a dovecot problem with solaris or my configuration of the solaris installation? ¿how i can fix this problem? ¿why this happends? -- Salu2 ;)

4 3

[Dovecot] Newbie index infrastructure and location questions
by Stewart Dean 15 Mar '07

15 Mar '07

I've been lurking for a year or more and am now actually bringing Dovecot up (it seems that any time I make a serious effort at this, something else falls in the pot and I have to give it up yet again). Index questions: I understand the indices should be placed in a non-file-system-quoted place. I have in mind to create /var/dcndx 1) Roughly how much space do indices take up (so I can size space for a directory for them)? I have 4000 users, average mbox inbox size is 5.5MB (totalling 22GB), the number of messages/user mailbox I'd guess to average around 100 and go as high as 5000. They have maybe as much as 3x times space and messages in folders, though I guess the average is about half that of INBOX 2) I'm clear that DC will automagically create the index files, but a) do I have to create a subdirectory for each user, ex: /var/dcndx/user1 b) Is there one index file theat handles a user's mailbox and folders or a separate one for each? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 1

[Dovecot] Newbie NFS question
by Stewart Dean 15 Mar '07

15 Mar '07

As is usually the case, I'm not sure enough of what the DC docs are referring to; there are some implicit info assumptions that I, the Newbie, miss... Anyway, here is my situation Dovecot is to run on one machine only, its index files are stored in on a separate, non-quotaed, not NFS filesystem. INBOX and folder filesystems (all mbox format) are native to this machine and are NFS exported to three machines with root access. NFS access can be NFS V2, or 3 or 4. 1) a user maintenance server that may add or delete users and their INBOXES/folders 2) a mailing list server that writes mailings email to the NFS mounted file system of user INBOXes 3) A user login machine where the users may access their INBOXes and folders All machines are running vanilla IBM AIX; I have never known there to be corruption from NFS locking problems, and am not aware of any locking/caching parameters for AIX's NFS implementation. All machines are running NTP synched to a common NTP master server My questions: 1) Since my index files are stored in on a separate, non-quotaed, not NFS filesystem, can I correctly assume this means I can ignore the nmap_disable and lock_method parms? 2) The docs say: > The easiest way to get better performance without caching problems is > to just make sure the user is always redirected to the same server. If > you can manage to do that, then it's safe to enable attribute caching. The INBOXes and folders live on the mail server where a) DC is going to run and b) they are exported to the three other machine. Does this mean that I don't have to mess with actimeo? 3) Pardon my ignorance....Is actimeo set on the NFS server as an attribute of exportation or on the NFS client on the imported FS...or both 4) Is there any reason related to data integrity or performance to prefer NFS V2 or 3 or 4? 5) Are there other questions I should ask of IBM about NFS client and Server daemon config Thanks in advance........... -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 1

[Dovecot] quota - dict - username = '(null)'
by Andreas Jørgensen 15 Mar '07

15 Mar '07

I am trying setting up at virtual domain with quota using postfix and dovecut. But I can't get the quota to work, every time I try sending a mail the following queries is run on the database. SELECT home, uid, gid FROM mail_view_tmp WHERE account = 'dummy' AND domain = 'example.com' SELECT current FROM mail_quota WHERE path = 'quota/storage' AND username = '(null)' BEGIN;INSERT INTO mail_quota (current, path, username) VALUES ('quota/ storage', 262, '(null)') ON DUPLICATE KEY UPDATE current = current + 262;COMMIT The mail is delivered, but the quota for the user is not updated. Instead I just have an other new row for the user (null). I am using the package dovecot-1.0.rc2p3-mysql on OpenBSD 4.0 for macppc My configuration: (posting the full content of alt the config files seemed unnecessary so I cut out the important bits) /etc/postfix/main.cf ... virtual_transport = dovecot /etc/postfix/master.cf : ... dovecot unix - n n - - pipe flags=DRhu user=vmail argv=/usr/local/libexec/dovecot/deliver -d $ {recipient} /etc/dovecot.conf .... protocol lda { mail_plugins = quota } .. auth default { user = root passdb sql { args = /etc/dovecot-mysql.conf } userdb static { args = uid=2000 gid=2000 home=/var/vmail/%d/%n/ } socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail group = vmail } } } dict { quota = mysql:/etc/dovecot-dict-quota.conf } plugin { quota = dict:storage=10240:messages=1000 proxy::quota } /etc/dovecot-mysql.conf: driver = mysql connect = host=localhost dbname=ingoBase user=dovecot password=dovecot default_pass_scheme = CRYPT password_query = SELECT password FROM mail_view_dovecot WHERE account = '%n' AND domain = '%d' user_query = SELECT home, uid, gid FROM mail_view_tmp WHERE account = '%n' AND domain = '%d' or account = '%u' /etc/dovecot-dict-quota.conf connect = host=localhost dbname=ingoBase user=dovecot password=dovecot table = mail_quota select_field = current where_field = path username_field = username Is there something wrong in my configuration or is this a bug in the version i am using ? Thanks in advance ! Andreas

2 1

[Dovecot] login authentication
by juan carlos 15 Mar '07

15 Mar '07

Hi everyone, i used postfix, dovecot and mysql. I have virtual users and domains. I have this configuration in dovecot-mysql.conf: db_host = localhost db_port = 3306 db_unix_socket = /var/run/mysqld/mysqld.sock db = postfix db_user = postfix db_passwd = bscidth46 db_client_flags = 0 default_pass_scheme = CRYPT password_query = SELECT password FROM mailbox WHERE username = '%u' user_query = SELECT maildir, 105 AS uid, 106 AS gid FROM mailbox WHERE username = '%u' The table mailbox: +-------------------+--------------+------------------+-----------+------------+ | username | home | maildir | quota | domain | +-------------------+--------------+------------------+-----------+------------+ | test(a)domain.com | /home/vmail/ | domain.com/test/ | 10240000 | domain.com | | test2(a)domain.com | /home/vmail/ | domain.com/test2/ | 10240000 | domain.com | | test3(a)domain.com | /home/vmail/ | domain.com/test3/ | 10240000 | domain.com | +-------------------+--------------+-------------------+----------+------------+ I have this configuration in smtpd.conf: pwcheck_method: auxprop mech_list: LOGIN CRAM-MD5 DIGEST-MD5 GSSAPI auxprop_plugin: sql sql_verbose: yes sql_engine: mysql sql_hostnames: localhost sql_database: postfix sql_user: postfix sql_passwd: bscidth46 sql_select: select password from mailbox where username = '%u@%r' What can i do to log in with only user part of user(a)domain.com? Thanks in advance

3 2

Re: [Dovecot] imap-login (proxy) Connection queue full
by Bill Boebel 15 Mar '07

15 Mar '07

On Wed, March 14, 2007 1:57 pm, Timo Sirainen <tss(a)iki.fi> said: > On Thu, 2006-08-10 at 23:15 -0400, Bill Boebel wrote: >> On Thu, August 10, 2006 5:22 pm, Timo Sirainen <tss(a)iki.fi> said: >> >> >> Aug 10 16:23:34 director5 dovecot: imap-login: Disconnected: Connection queue >> >> full: >> >> >> >> I am seeing this logged several times per minute. From netstat, the server >> has >> >> 650 proxied IMAP connections and 450 proxied IMAPS connections, there are >> >> currently 10 imap-login processes running, and using the following config: >> > >> > I did some changes to CVS which hopefully should fix this? >> >> It is still disconnecting with "Connection queue full", although less frequently. >> Testing with about 315 IMAP connections right now and same config as earlier >> today, so it should never hit this condition, right? > > BTW. Does this still happen? No, however I haven't had to touch our Dovecot proxies in several months. They just work. We're still running a copy I pulled from CVS just before 1.0.rc8. We're running the new code only on our backend mail servers. I guess we should update our proxies soon. Bill

1 0

[Dovecot] Courier keywords - anyone even tried?
by Troy Engel 14 Mar '07

14 Mar '07

I do realize from the Wiki that the formats are incompatible, and am looking at the Courier spec (http://www.courier-mta.org/imap/?README.imapkeywords.html) and the Dovecot spec (http://wiki.dovecot.org/MailboxFormat/Maildir) trying to see if there's any sane way I could try and write a shellscript. The pain here is the Courier spec, I think I lost a few brain cells trying to understand this convoluted methodology ("When encountering ".N.file" after another ".N.file" was encountered earlier, remove the file with the lesser N, unless the larger of the two Ns is greater than or equals to T." e.g.) Has anyone even started down this path and has some prototype code written that they gave up on? Is this just so painful trying to migrate that I should just give up? Any ideas welcome... -te -- Troy Engel | Systems Engineer Fluid, Inc | http://www.fluid.com

2 1

[Dovecot] Benchmarking CVS HEAD vs. v1.0
by Timo Sirainen 14 Mar '07

14 Mar '07

Some new features in CVS HEAD are: - v1.0 saves most of the data to dovecot.index.cache only when the client is FETCHing the messages. With mboxes the message headers are saved while parsing the mbox, which is almost the same thing. With CVS HEAD the dovecot.index.cache file is updated already when the new messages are being saved (with deliver or IMAP APPEND). This avoids reading the message second time (although if client fetches the new message bodies immediately it doesn't probably help that much). - Mailbox list index. LIST command can be handled by reading the mailboxes from the index. The index also contains the mailbox's message counters, so STATUS command can be handled by only looking into the index file. - Multiple commands can be handled simultaneously. For example you can start a long running SEARCH command and then at the same time continue FETCHing new messages. Or if you're doing a long FETCH (eg. fetching all message bodies) you can do a smaller FETCH while the long one is still running, and get the result in the middle of the long running FETCH reply. There are also indexing support for SORT and THREAD, and full text search indexes for SEARCH BODY/TEXT, but I didn't benchmark these now. It looks like CVS HEAD is quite a lot faster than v1.0. I think that's mostly because of the APPEND optimization. Here are the results: 100MB ext3 filesystem inside a file in XFS. C: CVS HEAD, fsync_disable=yes, mmap_disable=yes S: CVS branch_1_0 (upcoming 1.0.rc28), fsync_disable=yes, mmap_disable=yes ./imaptest seed=1 secs=60 Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe Logo C: 11275 5647 5597 11275 11264 16179 5571 4126 11256 6074 22531 C: 11287 5740 5606 11287 11275 16193 5698 4154 11267 6064 22553 S: 9201 4660 4575 9197 9190 13107 4614 2843 9184 3601 18382 S: 9271 4701 4657 9267 9260 13189 4580 2799 9256 3540 18522 82% 82% 59% ./imaptest seed=1 secs=60 no_pipelining Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe Logo C: 5756 2856 2795 5756 5747 8087 2796 1942 5746 5081 11489 C: 5779 2865 2872 5777 5768 8273 2929 1965 5768 5138 11532 S: 5016 2564 2467 5016 5008 7090 2512 1756 5006 4116 10012 S: 5009 2529 2481 5008 4999 7142 2503 1734 4997 4165 9998 87% 89% 81% ---------- Trying to see how much mailbox list indexing code affects the results by disabling LIST and STATUS (which means that CVS HEAD is doing more I/O by updating the list indexes which are never used). Looks like the indexes do help some, since CVS HEAD is ~5% less faster now. ./imaptest seed=1 secs=60 list=0 status=0 Logi Sele Fetc Fet2 Stor Dele Expu Appe Logo C: 11435 11432 11422 16341 5639 4122 11415 5941 22848 S: 9984 9984 9976 14347 5013 2987 9967 3840 19947 87% 65% ./imaptest seed=1 secs=60 list=0 status=0 no_pipelining Logi Sele Fetc Fet2 Stor Dele Expu Appe Logo C: 5778 5778 5768 8105 2922 2021 5767 5107 11533 S: 5240 5239 5230 7384 2525 1823 5229 4343 10460 90% 85% --------------- Any difference with just one client instead of 10 simultaneously running? Looks like with pipelining CVS HEAD is now even faster, but without pipelining it's a bit slower. I'm not sure why. I tried with different max. command queue lengths with CVS HEAD. The C1, C4 and C8 mean queue lengths of 1, 4 and 8 commands. 1 practically disables it, so it runs like v1.0. Doesn't look like the queue length makes much of a different. ./imaptest seed=1 secs=60 list=0 status=0 clients=1 Logi Sele Fetc Fet2 Stor Dele Expu Appe Logo C4: 9968 9968 9967 14244 5020 2664 9967 2990 19934 S : 6510 6510 6508 9340 3216 1729 6508 1942 13017 65% 63% C1: 9956 9956 9954 14314 4959 2642 9954 2987 19907 C4: 9968 9968 9967 14244 5020 2664 9967 2990 19934 C8: 9978 9978 9976 14329 4848 2618 9976 2962 19953 ./imaptest seed=1 secs=60 list=0 status=0 clients=1 no_pipelining Logi Sele Fetc Fet2 Stor Dele Expu Appe Logo C: 1942 1942 1941 2711 962 508 1941 605 3882 S: 1868 1868 1867 2669 965 520 1866 618 3734 96% 102% --------------- mmap_disable=no seems to work more slowly after all even with etx3..: Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe Logo C: 8254 4150 4139 8254 8244 11813 4126 2791 8234 3658 16487 S: 7833 3940 3910 7829 7821 11243 3846 2345 7816 2966 15646 95% 81%

2 1

Re: [Dovecot] imap-login (proxy) Connection queue full
by Bill Boebel 14 Mar '07

14 Mar '07

On Thu, August 10, 2006 5:22 pm, Timo Sirainen <tss(a)iki.fi> said: >> Aug 10 16:23:34 director5 dovecot: imap-login: Disconnected: Connection queue >> full: >> >> I am seeing this logged several times per minute. From netstat, the server has >> 650 proxied IMAP connections and 450 proxied IMAPS connections, there are >> currently 10 imap-login processes running, and using the following config: > > I did some changes to CVS which hopefully should fix this? It is still disconnecting with "Connection queue full", although less frequently. Testing with about 315 IMAP connections right now and same config as earlier today, so it should never hit this condition, right? The weird thing is sometimes when I am testing via telnet, my session encounters this condition and disconnects within the first 5 seconds. It does this with and without these patches. Bill

2 1

[Dovecot] Sieve plugin - install help - filters ignored
by Brent Hostetler 14 Mar '07

14 Mar '07

Hello, My setup consists of the following: * Freebsd 6.2 system with software installed from ports tree: * Postfix 2.3.8,1 * postfixadmin 2.1.0_7 * mysql 5.0.33 * dovecot-1.0.r25 * dovecot-sieve 1.0.1 * clamav 0.90_3 * SpamAssassin 3.1.8_1 * amavisd-new 2.4.5_1,1 My mail setup is a virtual user setup with all users/domains sharing same UID:GID. Postfix and dovecot get their User information from mysql tables that are administered with postfixadmin. Mail is filtered through clamav and spamassassin using amavisd-new setup as a content filter. All users mail is delivered such as their maildir is /usr/local/vmail/%d/%u using dovecot's lda 'deliver' agent. The system is working fine as configured.. Mail goes where it is supposed to. Trying to get sieve support and unable to get this going. First step is simulating home directories. >From dovecot-mysql.conf ... changed user_query to user_query = SELECT maildir, 5000 AS uid, 5000 AS gid, @home := maildir AS home FROM mailbox WHERE username = '%u' Added the following to a users maildir: .dovecot.sieve require "fileinto"; fileinto "test"; --- Restart all daemons.. Mail still delivers to inbox. Nothing appears in /var/log/maillog or /usr/local/vmail/dovecot-deliver.log that shows anything but the message being delivered to the inbox. HELP! Brent.

4 5

[Dovecot] userdb-vpopmail.c bug in rc27
by Gabor HALASZ 14 Mar '07

14 Mar '07

Hi! I discovered a bug in $subject. Next line caused a compilation error: auth_request_log_debug(auth_request, "vpopmail", "lookup user=%s domain=%s", vpop_user, vpop_domain); I think, te correct version is: auth_request_log_debug(request, "vpopmail", "lookup user=%s domain=%s", vpop_user, vpop_domain); -- Gabor HALASZ <halasz.g(a)freemail.hu>

2 1

[Dovecot] Variable %h not recognized in userdb_mail (passwd-file)
by Michal Soltys 14 Mar '07

14 Mar '07

As in subject, if you for instance create a simple passwd-file with: test@domain.tld:{plain}pass:20000:10::/home/regular/.test::userdb_mail=maildir:%h/maildir Dovecot (rc23 & 27) will expand %h to empty string, and try to make a directory under / Mar 14 14:25:28 rasengan dovecot: IMAP(test(a)domain.tld): mkdir(/maildir/cur) failed: Permission denied Mar 14 14:25:28 rasengan dovecot: IMAP(test(a)domain.tld): mkdir(/maildir/.Trash/cur) failed: Permission denied ... If tilde is used instead of %h, the expansion works properly. While checking it, I tested other variables (putting aside craziness of using some of them), so summing it up - h,w,i,a,b don't work, all the other ones do. In case %h is not actually intended to work in passwd-files, some wiki examples would have to be adjusted.

2 4

[Dovecot] Issue with pop3 & phpList
by Chris Harner 14 Mar '07

14 Mar '07

Hello, all. Dovecot really sparked my interest when I noticed it focused on security. It seems to be a great product thus far. Anyway... I'm new to the mail world (pop3/smtp), and I have a project in which I use a mass mailer known as phpList. If you aren't familiar with it, it has the ability to view and process bounces. Bounces are basically emails that don't quite make it (for the most part). In order for this to work, I must create a pop3 account. I installed Dovecot and now the port is open, which means the service is running. Here is where it gets confusing... When I goto process the bounces, it times out because of the fact that there were too many login attempts. Does dovecot have a default username/password? How do I set up a username and password? Is there a special way to just have the pop3 portion of Dovecot load? I went through the config file and took out some of the #'s like the docs said. Thanks! Server: OpenSUSE 10.1 -- Chris Harner [] Server Engineer [] Arnold Transportation Services

2 1

Re: [Dovecot] solaris 10 + dovecot (1)
by Gábor Lénárt 14 Mar '07

14 Mar '07

Re, On Wed, Mar 14, 2007 at 02:26:53PM +0000, aza zel wrote: > like other suggest me, the cause of problem is that i not have much space in > / (i think that 4.4gb is a lot of space but i wrong) > so, i move to /export/home where i have space and try again and i not have > any problems. > about memory... i don't remeber how much i have but swap have nearly 667mbs > free for proces compile (i only run these proces). Nice :) I've mentioned 'memory' because of the Spanish (is it Spanish? Just guessing) fragment 'espacio de memoria' remembered me to the English word of 'memory', I was wrong here it seems. So forget about memory, it was only my guesswork about your native language :) The lesson here: please translate all messages to English if you want to post to an English mailing list. Otherwise some people (like me) have no chance to understand just guessing ... :) -- - Gábor

1 0

[Dovecot] help with basic setup
by Perish Mutyanda 14 Mar '07

14 Mar '07

I am new to dovecot and would like to setup dovecot with mysql auth. I successfuly installed postfix admin and used the default table structure there, Mail delivery works fine as It gets delivered to mailboxes. My problem is the login, dovecot runs with no errors but I get the error: Mar 14 14:39:43 itecsouth dovecot: auth-worker(default): mysql: Connected to localhost (postfix) Mar 14 14:40:34 itecsouth dovecot: pop3-login: Disconnected: rip=41.xxx.xxx.190, lip=41.243.140.153 Mar 14 14:41:14 itecsouth dovecot: pop3-login: Login failed: Plaintext authentication disabled: rip=41.xxx.xxx.190, lip=41.xxx.xxx.153 Mar 14 14:41:14 itecsouth dovecot: pop3-login: Disconnected: rip=41.xxx.xxx.190, lip=41.xxx.xxx.153 I have tried to change the pass scheme in dovecot-mysql.conf to CRYPT as but says unknown auth_scheme a copy of my dovecot.conf protocols = pop3 listen = * login_process_size = 64 default_mail_env = maildir:/usr/local/virtual/%d/%u/ mail_extra_groups = postfix verbose_proctitle = yes first_valid_uid = 125 first_valid_gid = 125 mbox_read_locks = fcntl mbox_write_locks = fcntl protocol pop3 { pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_debug = yes auth_verbose = yes auth default { passdb sql { args = /usr/local/etc/dovecot-mysql.conf } userdb sql { args = /usr/local/etc/dovecot-mysql.conf } } -- and the dovecot-mysql.conf # Database driver: mysql, pgsql driver = mysql default_pass_scheme = PLAIN connect = host=localhost dbname=postfix user=dovecot password=dovecot password_query = SELECT password FROM mailbox WHERE username = '%u' AND active = '1' user_query = SELECT maildir, 125 AS uid, 125 AS gid FROM mailbox WHERE username = '%u' AND active = '1'

2 1

[Dovecot] Timed Out or Disconnect Errors on emails with attachments
by Tudor Holton 14 Mar '07

14 Mar '07

dovecot-request(a)dovecot.org wrote: > > On Tue, 2007-03-13 at 16:35 +1100, Tudor Holton wrote: > >> I've migrated our Maildir system from Courier-IMAP-SSL to Dovecot with >> SSL and now we're getting "Connection to <server> Timed Out" errors when >> sending mail with attachments. The mail gets sent, however it doesn't >> save the mail in the user's "Sent" folder. >> > > What OS is Dovecot running in? What Dovecot version? What configure > options? There have been bugs related to this, but I thought they were > all fixed. > I apologise, I just realised that I hadn't included that information. The server is a current Ubuntu Edgy Box. It has Dovecot 1.0rc2. I now see there have been 25 rc's since then. (Yikes!) So I guess I should be complaining upstream. I did search the net for several weeks, however, and found no mention of this problem, even in the Dovecot wiki or mailing list archive. So if you say it's fixed, then I'll put something in the wiki to that effect and go badger the Ubuntu guys for an upgrade. :-) Cheers, Tudor.

2 1

[Dovecot] HTML mails
by Timo Sirainen 14 Mar '07

14 Mar '07

I think I configured Mailman to drop all text/html MIME parts. Lets see if it works. html -> text translation is also enabled.

2 1

[Dovecot] Dovecot for "push email"
by Matthew Sheffield 14 Mar '07

14 Mar '07

Does anyone have experience here using a combination of Dovecot and a Windows or Palm client that supports IMAP IDLE to achieve "push email?" I'm doing some research into how feasible this is for companies and non-profits.

2 1

[Dovecot] imaptest updates
by Timo Sirainen 13 Mar '07

13 Mar '07

I spent the last 5 hours or so updating my imaptest tool. It's beginning to become almost like a real IMAP client. http://dovecot.org/tools/imaptest10.c contains a version that compiles against Dovecot v1.0 (instead of against CVS HEAD). imaptest is this tool that I've been using for a few years to do stress testing. It can create a lot of dummy IMAP client connections which execute some commands. Today I added some new features to it: - Support for pipelining commands (where allowed by IMAP spec). Looks like it about doubles the throughput. "no_pipelining" option disables this. - Support for MULTIAPPEND extension. When multiple mails are APPENDed one after another this extension is used to save them all in one transaction. - Previous versions gave an error when trying to append large mails. Now large mails work too. - By default the commands are executed in one specific order. Using "random" option randomizes the order. - You can separately specifify probabilities of how often to execute each command. 0 means never, 100 means always, 10 means 10% of the time and so on. 100,30 means that it's always executed, and then it's executed again and again with 30% probability. The basic way to run it is: ./imaptest user=test pass=password host=imap.domain.org mbox=/home/user/mail/dovecot clients=1 Or if you want to run multiple users, you can use user=test%d which will use users test1..test100 (the size is hardcoded in USER_RAND define). If you want to do benchmarking, you can set it to run for specified amount of time, and you should also give random number generator the same seed every time: ./imaptest seed=123 secs=300 If you want to test/benchmark only the login+logout speed, use: ./imaptest - select=0 To create a lot of long-running clients doing STATUS and NOOPs: ./imaptest clients=100 - logout=0 status=50 noop=50 delay=100 To test copying messages: ./imaptest copybox=Trash By default LOGIN command is used. If you want to try AUTHENTICATE: ./imaptest auth=100 Hmm. I guess that's about it. The list of commands that you can use starts from line 134. You can use either the long names or the short names.

3 4

[Dovecot] Timed Out or Disconnect Errors on emails with attachments
by Tudor Holton 13 Mar '07

13 Mar '07

Hello all, I've migrated our Maildir system from Courier-IMAP-SSL to Dovecot with SSL and now we're getting "Connection to <server> Timed Out" errors when sending mail with attachments. The mail gets sent, however it doesn't save the mail in the user's "Sent" folder. Our IMAP and SMTP servers are different. So the client sends to the SMTP server first, completes that, and then opens a channel to Dovecot and dovecot appears to receive the data (TB gives a progress bar as it's sending to dovecot) and then disconnects _after_. We have a mixed bag of clients here from Thunderbird on Linux and Windows, through Outlook Express to Outlook. All show similar errors. I enabled the logs on dovecot, however it wasn't very informative. At the time it occurred the only line in the log file was: dovecot: 2007-03-13 16:21:12 Info: IMAP(tudor): Disconnected This is obviously different from "Disconnected: Logged out". Emails without attachments behave ok, it only occurs with emails with attachments. Has anyone else had any experience of this? Cheers, Tudor.

3 3

[Dovecot] Prayer, Maildir and Folders whose names begin with "."
by Mike Brudenell 13 Mar '07

13 Mar '07

Greetings - I think I've just had one of my fears confirmed: not Dovecot-specific exactly, but it affects how we will use of Prayer (Webmail Software) with Dovecot... Currently our production service uses MBX-format mailboxes with the UW IMAP server; we also use the University of Cambridge "Prayer" software for Webmail. By default Prayer saves its preference settings, address book and so on in a regular IMAP folder called ".prayer" And one of the nice things about the UW IMAP server is that you can tell it not to include files whose names start "." when returning the list of folders for a LIST command. This means: * People don't see the secret ".prayer" folder when they look at the list; * But if something (eg, Prayer) knows its name it can open this folder to get at its content. The combination of these is that (a) Prayer can store its settings and (b) users don't see where, so can't open/tamper with the secret settings folder for Prayer. But I've just discovered that I can't create a folder called ".prayer" using Maildir-format mailboxes. The problem appears to be the leading "." I suspect it's because the Maildir++ specification at http://www.inter7.com/courierimap/README.maildirquota.html says this: > Folders are created as subdirectories under the main Maildir. The name of > the subdirectory always starts with a period. For example, a folder named > "Important" will be a subdirectory called ".Important". You can't have > subdirectories that start with two periods. A folder named ".prayer" would lead to a subdirectory being created called "..prayer" I think. Q. Can anyone confirm that you can't create Maildir folders called ".somename"? Q. Are there any other Prayer users out there using Dovecot and Maildir format mailboxes? What are you doing about the user-settings folder for Prayer? (And do you manage to hide it from view, so they can't tamper with its contents?) Cheers, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. *

4 10

[Dovecot] error with virtual users
by Antonio Casado Rodríguez 13 Mar '07

13 Mar '07

Hi, In my dovecot-deliver.log i have this: deliver(xxuser): Mar 13 11:36:49 Error: open(/home/xxuser/.temp.alboran.24421.63c6890e35b613e8) failed: No such file or directory deliver(yyuser): Mar 13 11:38:29 Error: open(/home/yyuser/.temp.alboran.26046.dcb46511eeb37f3d) failed: No such file or directory but i haven't homedir user. I have /var/spool/mail/xxuser/ maildir Is that a error? I have Dovecot-1.0-rc19 + dovecot-deliver + rhel 4.4 Thanks you

4 4

[Dovecot] index performance issues
by Netserve 13 Mar '07

13 Mar '07

Running 1.0.rc22 We have a single file server, running NFS (Single large sas disk) with about 80Gb of mail. mount -o remount,rsize=2048,wsize=2044,actimeo=0,soft,rw xx.xx.xx.xx:/mailboxes /nfs1 There are 3 front end pop/imap servers using an LVS director. Indexes are stored on each front end server. -rw------- 1 admin 500 144 Mar 12 17:47 dovecot.index -rw------- 1 admin 500 10272 Mar 12 17:47 dovecot.index.cache -rw------- 1 admin 500 120 Mar 12 17:47 dovecot.index.log Normally everything runs fine, there are about 1500 active pop accounts and 100 Imap. Typically, 10 to 20 pop accounts are downloading at anyone time, and there may be 10 or 20 active Imap sessions. If we find that the index partition has got to 100% full and corrupted the indexes then we'll delete the entire index dir and let dovecot rebuild all the indexes however, we end up with 100mbit / 10Mb/sec of network traffic between the NFS server and the pop/imap servers. The nfs server load climbs to 20+ as does the load on the front end mail servers. It can take 4 or 5 hours for the indexes to rebuild during which time imap is slow but works and pop downloads all end up with dead processes that need clearing every few minutes. admin 5869 0.0 0.1 4384 1060 ? D 17:56 0:00 \_ pop3 [info@.co.uk 180.98] admin 5877 0.0 0.1 4392 1112 ? D 17:57 0:00 \_ pop3 [bro94 62.182] admin 5879 0.0 0.1 4396 1052 ? D 17:57 0:00 \_ pop3 [spamcatch@.com 81.163] admin 5884 0.0 0.1 4392 1056 ? D 17:57 0:00 \_ pop3 [ctaylor@.com 81.175] Normally the nfs server delivers possibly 200Kbytes of traffic average spiking to 400Kbytes but the 900+Kbytes per second sustained rate for 5 or 6 hours is killing the service. Is there something we've got wrong here? (I know a Scsi raid NFS would help as would Gbit networking but I can't see the setup we've got as needing that sort of hardware spec?) Thanks John

5 11

[Dovecot] imap + unmounted home disk
by T. Horsnell 13 Mar '07

13 Mar '07

dovecot 0.99 still (RHEL4), I'm sorry to say. The config is for mbox's to live on the user's home disk. If the user tries to make an imap connection when his home disk is unmounted, various permission denied messages are logged, as expected, but then the imap process seems to hang around instead of aborting. The result is that eventually the imap process limit is reached, and even those users whose home disks are correctly mounted, cant get at their mail. Apologies if this has already been fixed - I cant find anything relevant in the archives. Cheers, Terry

2 4

[Dovecot] Password encoding
by David Mills 13 Mar '07

13 Mar '07

Hi, I've currently got a problem authenticating to my dovecot server (1.0rc15). The server is set up to authenticate against a mysql server, with a default password scheme of 'crypt'. The problem is that some of the passwords I need to transfer (all from /etc/shadow files) are md5 encoded, and when I put {md5-crypt} in front of the password to force the scheme, dovecot answers :"Unknown password scheme md5-crypt". If anyone has any ideas, I'd really appreciate it. TIA for your time. David -- David Mills Enki Technologies 01 76 00 71 20Unknown password scheme md5-crypt *De nouveaux sites voient le jour...* *...avec GenieBuilder !* Site de Vico <http://www.vico.fr> - enki.fr <http://www.enki.fr>

3 2

[Dovecot] Problems fetching mail
by Curt LeCaptain 13 Mar '07

13 Mar '07

I'm attempting to replace UW-IMAP with Dovecot, as my UW-IMAP implementation seems to be not working very well. Here's the problem I had with UW-IMAP: In Horde/IMP, messages just wouldn't appear at all. If I opened up the user's IMAP box via an IMAP client, I'd get a Bogus sequence in UID fetch error. So, now I've got Dovecot in place, and I'm getting the following error upon attempting to look at this same box: Error in IMAP command UID: Invalid UID messageset. Now, this user has 3 messages, each X-UID increments by one, starting at 1, so: X-UID: 1 X-UID: 2 X-UID: 3 None of those seem out of the ordinary size wise. I'm not sure what config information you'll need of me, as I'm new to dovecot, but any help would be appriciated. Thanks, Curt L.

3 8

[Dovecot] Quota and Trash
by Bernhard Schmidt 12 Mar '07

12 Mar '07

Hi, I finally got a grip on our mail guys to try out Dovecot after they started migrating a ~15k user mailsystem to Maildir+NFS (Netapp)+Courier and the performance was not as good as expected. So far the results are impressive, although there are of course a few small issues to be solved. One is the current Quota handling, which they use with Courier IMAP and (still) think it needs to be replicated 1:1 to dovecot. Currently they use maildir++ quota format. Mails moved to Trash get not included in the Quota calculation (standard "feature" of Courier IMAP) and get expunged after a certain period of days (IMAP_EMPTYTRASH). Is there any way we could replicate this behaviour with Dovecot? Not including mails in the Trash-folder into quota calculation seems to be a no-go to me according to the documentation, you can ignore the quota limit when copying messages into a certain folder with the "ignore" keyword but they are still included. This issue is directly related with the second one. Deleting old mails in Trash could be archieved with the expire-plugin, but that does not work with Dovecot v1.0, and I'd definitely want to run this. So I have to use "find", which deletes the mail from the folder. However, those mails are still included in the Quota calculation, so that will very likely become incorrect. Is there a generic recommendation for a tool that could be used to rebuild maildir quota calculations? Any other ideas how I could solve this problem and have dovecot behave like Courier here? Thanks, Bernhard

3 7

[Dovecot] Search not working?
by Marc Perkel 12 Mar '07

12 Mar '07

I switched for mbox to maildir last night and now searching folders isn't working. Getting a timeout. Is there something I might have forgot to configure?

2 3

[Dovecot] 1.0.rc26 released
by Timo Sirainen 12 Mar '07

12 Mar '07

http://dovecot.org/releases/dovecot-1.0.rc26.tar.gz http://dovecot.org/releases/dovecot-1.0.rc26.tar.gz.sig Most importantly this should fix mbox problems in recent RCs. * Changed --with-headers to --enable-header-install * If time moves backwards only max. 5 seconds, sleep until we're back in the original present instead of killing ourself. An error is still logged. - IMAP: With namespace prefixes LSUB prefix.* listed INBOX.INBOX. - deliver: Ignore mbox metadata headers from the message input. X-IMAP header crashed deliver. - deliver: If mail_debug=yes, drop out DEBUG environment before calling sendmail binary. Postfix's sendmail didn't really like it. - mbox: X-UID brokeness fixes broke rc25 even with valid X-UID headers. Now the code should finally work right. - Maildir: When syncing a huge maildir, touch dovecot-uidlist.lock file once in a while to make sure it doesn't get overwritten by another process. - Maildir++ quota: We didn't handle NUL bytes in maildirsize files very well. Now the file is rebuilt when they're seen (NFS problem). - Index/view handling fix should fix some crashes/errors - If index files were moved to a different endianess machine, Dovecot logged all sorts of errors instead of silently rebuilding them. - Convert plugin didn't change hierarchy separators in mailbox names. - PostgreSQL authentication could have lost requests once in a while with a heavily loaded server. - Login processes could have crashed in some situations - auth cache crashed with non-plaintext mechanisms

7 14

Re: [Dovecot] separate partition for index/uidlist - Thanks
by Daniel 12 Mar '07

12 Mar '07

Timo Sirainen: > > And what is exactly the use of the so called Quota reporting plugin? > > > It adds IMAP quota commands that can tell the client the current quota > usage and the quota limit. Just wanted to thank you for the kind support, and the great software, so.. thanks! Daniel

1 0

[Dovecot] MySQL database structure
by Erdenebat Gantomor 12 Mar '07

12 Mar '07

In Postfix+Postfixadmin+Dovecot+SASL+MySQL case what is the best and compact MySQL database structure for storing all configuration? What will you suggest me guys? I've already installed postfixadmin and I'm confusing (actually my experience is not enough) extending and organizing my database for postfix+dovecot. Please give me some quick tips. -- Best regards, Erdenebat Guntomor/ /mailto:RkLogin@gmail.com

2 1

[Dovecot] Dovecot Convert
by Marc Perkel 12 Mar '07

12 Mar '07

Trying to figure out how to convert an existing mbox system to maildir Below is my dovecot.conf file. Tried adding this at the bottom of the file and nothing happens. plugin { convert_mail = mbox:/vhome/%d/home/%n:INBOX=/vhome/%d/home/%n/INBOX convert_skip_broken_mailboxes=yes } What am I doing wrong? ## Dovecot 1.0 configuration file # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var # --with-ssldir=/etc/ssl # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s protocols = imap imaps pop3 pop3s # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. If you want to specify ports # for each service, you will need to configure these settings inside the # protocol imap/pop3 { ... } section, so you can specify different ports # for IMAP/POP3. #listen = * # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = # Disable SSL/TLS support. #ssl_disable = no # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf #ssl_cert_file = /etc/pki/dovecot/dovecot.pem #ssl_key_file = /etc/pki/dovecot/private/dovecot.pem ssl_cert_file = /usr/share/ssl/certs/imapd.pem ssl_key_file = /usr/share/ssl/certs/imapd.pem # File containing trusted SSL certificate authorities. Usually not needed. #ssl_ca_file = # Request client to send a certificate. #ssl_verify_client_cert = no # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 24 # SSL ciphers to use #ssl_cipher_list = all:!low # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. disable_plaintext_auth = no # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). log_path = /var/log/dovecot # For informational messages, use this logfile instead of the default info_log_path = /var/log/dovecot # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = /var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. # http://wiki.dovecot.org/Rootless #login_chroot = yes # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. # Note that this user is NOT used to access mails. # http://wiki.dovecot.org/UserIds #login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. login_process_size = 64 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. login_process_per_connection = no # Number of login processes to create. If login_process_per_user is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_user # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 # Greeting message for clients. #login_greeting = Dovecot ready. # Space-separated list of elements we want to log. The elements which have # a non-empty variable value are joined together to form a comma-separated # string. #login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c # Login log format. %$ contains login_log_format_elements string, %s contains # the data we want to log. #login_log_format = %$: %s ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. #mail_extra_groups = # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See doc/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden for # specific users in user database by giving /./ in user's home directory # (eg. /home/./user chroots into /home). Note that usually there is no real # need to do chrooting, Dovecot doesn't allow users to access files outside # their mail directory anyway. #mail_chroot = # Enable mail process debugging. This can help you figure out why Dovecot # isn't finding your mails. #mail_debug = no # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # doc/mail-storages.txt. There's a few special variables you can use, eg.: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if there's no domain # %h - home directory # # See doc/variables.txt for full list. Some examples: # # default_mail_env = maildir:/var/mail/%1u/%u/Maildir # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # default_mail_env = mbox:/vhome/%d/home/%n:INBOX=/vhome/%d/home/%n/INBOX:INDEX=/nobackup/imap-cache/%d-%n # If you need to set multiple mailbox locations or want to change default # namespace settings, you can do it by defining namespace sections: # # You can have private, shared and public namespaces. The only difference # between them is how Dovecot announces them to client via NAMESPACE # extension. Shared namespaces are meant for user-owned mailboxes which are # shared to other users, while public namespaces are for more globally # accessible mailboxes. # # REMEMBER: If you add any namespaces, the default namespace must be added # explicitly, ie. default_mail_env does nothing unless you have a namespace # without a location setting. Default namespace is simply done by having a # namespace with empty prefix. #namespace private { # Hierarchy separator to use. You should use the same separator for all # namespaces or some clients get confused. '/' is usually a good one. #separator = / # Prefix required to access this namespace. This needs to be different for # all namespaces. For example "Public/". #prefix = # Physical location of the mailbox. This is in same format as # default_mail_env, which is also the default for it. #location = # There can be only one INBOX, and this setting defines which namespace # has it. #inbox = yes # If namespace is hidden, it's not advertised to clients via NAMESPACE # extension or shown in LIST replies. This is mostly useful when converting # from another server with different namespaces which you want to depricate # but still keep working. For example you can create hidden namespaces with # prefixes "~/mail/", "~%u/mail/" and "mail/". #hidden = yes #} # Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # # flags, date.sent, date.received, size.virtual, size.physical # mime.parts, imap.body, imap.bodystructure # # Different IMAP clients work in different ways, so they benefit from # different cached fields. Some do not benefit from them at all. Caching more # than necessary generates useless disk I/O, so you don't want to do that # either. # # Dovecot attempts to automatically figure out what client wants and it keeps # only that. However the first few times a mailbox is opened, Dovecot hasn't # yet figured out what client needs, so it may not perform optimally. If you # know what fields the majority of your clients need, it may be useful to set # these fields by hand. If client doesn't actually use them, Dovecot will # eventually drop them. # # Usually you should just leave this field alone. The potential benefits are # typically unnoticeable. #mail_cache_fields = # Space-separated list of fields that Dovecot should never save to cache file. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Like mailbox_check_interval, but used for IDLE command. #mailbox_idle_check_interval = 30 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no # Maximum allowed length for mail keyword name. It's only forced when trying # to create new keywords. #mail_max_keyword_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. # Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes. #mail_read_mmaped = no # Don't use mmap() at all. This is required if you store indexes in remote # filesystems (NFS or clustered filesystem). #mmap_disable = no # Don't write() to mmaped files. This is required for some operating systems # which use separate caches for them, such as OpenBSD. #mmap_no_write = no # Locking method for index files. Alternatives are fcntl, flock and dotlock. # Dotlocking uses some tricks which may create more disk I/O than other locking # methods. #lock_method = fcntl # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Which locking methods to use for locking mbox. There's four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist in all systems. Doesn't work with NFS. # # You can use multiple locking methods; if you do the order they're declared # in is important to avoid deadlocks if other MTAs/MUAs are using multiple # locking methods as well. Some operating systems don't allow using some of # them simultaneously. #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # When mbox changes unexpectedly we have to fully read it to find out what # changed. If the mbox is large this can take a long time. Since the change # is usually just a newly appended mail, it'd be faster to simply read the # new mails. If this setting is enabled, Dovecot does this but still safely # fallbacks to re-reading the whole mbox file whenever something in mbox isn't # how it's expected to be. The only real downside to this setting is that if # some other MUA changes message flags, Dovecot doesn't notice it immediately. # Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK # commands. #mbox_dirty_syncs = yes # Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE, # EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored. #mbox_very_dirty_syncs = no # Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK # commands and when closing the mailbox). This is especially useful for POP3 # where clients often delete all mails. The downside is that our changes # aren't immediately visible to other MUAs. #mbox_lazy_writes = yes # umask to use for mail files and directories # umask = 077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. It could be a small # security risk if you use single UID for multiple users, as the users could # ptrace() each others processes then. #mail_drop_priv_before_exec = no # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #mail_process_size = 256 # Log prefix for mail processes. See doc/variables.txt for list of possible # variables you can use. #mail_log_prefix = "%Us(%u): " ## ## IMAP specific settings ## protocol imap { # Login executable location. #login_executable = /usr/libexec/dovecot/imap-login # IMAP executable location #mail_executable = /usr/libexec/dovecot/imap # This would write rawlogs into ~/dovecot.rawlog/ directory: #mail_executable = /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap # Maximum IMAP command line length in bytes. Some clients generate very long # command lines with huge mailboxes, so you may need to raise this if you get # "Too long argument" or "IMAP command line too large" errors often. #imap_max_line_length = 65536 # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/imap # Send IMAP capabilities in greeting message. This makes it unnecessary for # clients to request it with CAPABILITY command, so it saves one round-trip. # Many clients however don't understand it and ask the CAPABILITY anyway. #login_greeting_capability = no # Workarounds for various client bugs: # delay-newmail: # Send EXISTS/RECENT new mail notifications only when replying to NOOP # and CHECK commands. Some clients ignore them otherwise, for example # OSX Mail. Outlook Express breaks more badly though, without this it # may show user "Message no longer in server" errors. Note that OE6 still # breaks even with this workaround if synchronization is set to # "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. # netscape-eoh: # Netscape 4.x breaks if message headers don't end with the empty "end of # headers" line. Normally all messages have this, but setting this # workaround makes sure that Netscape never breaks by adding the line if # it doesn't exist. This is done only for FETCH BODY[HEADER.FIELDS..] # commands. Note that RFC says this shouldn't be done. #imap_client_workarounds = outlook-idle } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. #login_executable = /usr/libexec/dovecot/pop3-login # POP3 executable location #mail_executable = /usr/libexec/dovecot/pop3 # Don't try to set mails non-recent or seen with POP3 sessions. This is # mostly intended to reduce disk I/O. With maildir it doesn't move files # from new/ to cur/, with mbox it doesn't write Status-header. #pop3_no_flag_updates = no # Support LAST command which exists in old POP3 specs, but has been removed # from new ones. Some clients still wish to use this though. Enabling this # makes RSET command clear all \Seen flags from messages. #pop3_enable_last = no # POP3 UIDL format to use. You can use following variables: # # %v - Mailbox UIDVALIDITY # %u - Mail UID # %m - MD5 sum of the mailbox headers in hex (mbox only) # %f - filename (maildir only) # # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier version 0 : %f # Courier version 1 : %u # Courier version 2 : %v-%u # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # # Note that Outlook 2003 seems to have problems with %v.%u format which is # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. pop3_uidl_format = %v.%u # POP3 logout format string: # %t - number of TOP commands # %T - number of bytes sent to client as a result of TOP command # %r - number of RETR commands # %R - number of bytes sent to client as a result of RETR command # %d - number of deleted messages # %m - number of messages (before deletion) # %s - mailbox size in bytes (before deletion) #pop3_logout_format = top=%t/%T, retr=%r/%R, del=%d/%m, size=%s # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. # oe-ns-eoh: # Outlook Express and Netscape Mail breaks if end of headers-line is # missing. This option simply sends it if it's missing. # pop3_client_workarounds = outlook-no-nuls } ## ## Authentication processes ## # Executable location #auth_executable = /usr/libexec/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # Authentication cache size in kilobytes. #auth_cache_size = 0 # Time to live in seconds for cached data. After this many seconds a cached # record is forced out of cache. #auth_cache_ttl = 3600 # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username character translations before it's looked up from databases. The # value contains series of from -> to characters. For example "#@/@" means # that '#' and '/' characters are translated to '@'. auth_username_translation = #@/@ # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. # auth_verbose = yes # Even more verbose logging for debugging purposes. Shows for example SQL # queries. #auth_debug = no # Maximum number of dovecot-auth worker processes. They're used to execute # blocking passdb and userdb queries (eg. MySQL and PAM). They're # automatically created and destroyed as needed. #auth_worker_max_count = 30 auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous mechanisms = plain # # Password database is used to verify user's password (and nothing more). # You can have multiple passdbs and userdbs. This is useful if you want to # allow both system users (/etc/passwd) and virtual users to login without # duplicating the system users into virtual database. # # http://wiki.dovecot.org/Authentication # # PAM authentication. Preferred nowadays by most systems. # Note that PAM can only be used to verify if user's password is correct, # so it can't be used as userdb. If you don't want to use a separate user # database (passwd usually), you can use static userdb. # Linuxconf passwd-like file with specified location passdb passwd-file { args = /etc/vmail/shadow.%d } # Linuxconf passwd-like file with specified location userdb passwd-file { args = /etc/vmail/passwd.%d } # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by userdb above. user = root # Number of authentication processes to create #count = 1 } # It's possible to export the authentication interface to other programs, # for example SMTP server which supports talking to Dovecot. Client socket # handles the actual authentication - you give it a username and password # and it returns OK or failure. So it's pretty safe to allow anyone access to # it. Master socket is used to a) query if given client was successfully # authenticated, b) userdb lookups. # listener sockets will be created by Dovecot's master process using the # settings given inside the auth section auth_debug_passwords = yes #auth_master_user_separator=* auth default_with_listener { mechanisms = plain # passdb passwd-file { # Master users that can log in as anyone # args = /etc/dovecot.masterusers # master = yes #pass =yes # } passdb passwd-file { # Path for passwd-file args = /etc/vmail/shadow.%d } userdb passwd-file { # Path for passwd-file args = /etc/vmail/passwd.%d } socket listen { master { path = /var/run/dovecot/auth-master mode = 0666 } } } protocol lda { # UNIX socket path to master authentication server to find users. auth_socket_path = /var/run/dovecot/auth-master }

3 4

[Dovecot] Enable pop3 / pop3 and imap
by edwardspl＠ita.org.mo 12 Mar '07

12 Mar '07

Dear All, I'm new to use dovecot for the Mail service... So, how to enable the mail service ( pop3 / pop2 / imap ) ? Edward.

6 8

[Dovecot] Time moving backwards error
by Matthew Ward 12 Mar '07

12 Mar '07

I'm currently running a VPS which has the NTP daemon running on neither my CentOS installation nor on the hardware node itself, so as far as I am aware the server time shouldn't be being resynched by anything, and the time should be consistent. However, since r25 my Dovecot service is complaining that time is moving backwards (was being killed only a few moments after being started with r25, same problems as Emmett with r26) quite consistently, and always by one second. Could this simply be an error or something within Dovecot itself, as to have nothing physically updating the system time on my machine at all and to have Dovecot complaining that it's being resynched by one second all the time seems a bit odd?

4 4

Re: [Dovecot] separate partition for index/uidlist
by Daniel 11 Mar '07

11 Mar '07

> ... [...] Just one more question: is it wise to copy over the index files and the dovecot-uidlist files to the new locations, or dovecot will regenerate them? Daniel

2 3

[Dovecot] Upgrade from 0.99 to 1.0
by Láďa 11 Mar '07

11 Mar '07

Hi, I have just noticed that one our box is still running ancient 0.99 version (shame on me). Is there anything what I have to take care about during update? I am completely aware about changes in configuration files so my question is mainly about existing maildirs. Láďa

2 2

[Dovecot] separate partition for index/uidlist
by Daniel 11 Mar '07

11 Mar '07

Hi! What's a safe place for the separate index and uidlist files? I am planning to configure Quota/FS. Can they reside under dovecot's basedir? Is this a good idea? Does it have any significance where I put those files? Thanks, Daniel

2 6

[Dovecot] in memory indexes?
by Daniel 11 Mar '07

11 Mar '07

Hi! > RCS file: /home/cvs/dovecot/src/lib-index/mail-index.c,v > Working file: src/lib-index/mail-index.c > revision 1.268 > date: 2007-03-11 16:10:42 +0000; author: tss; state: Exp; lines: > > +8 -5; commitid: yo3GJUvm1yKgLG9s; > If we run out of disk space, move to in-memory indexes. I just saw the commit. Is this a "solution" for the Quota/FS problem, the problem which occurs when the quota is full, and dovecot can not update it's index files? Daniel -- LeVA

2 3

[Dovecot] (no subject)
by Erdenebat Gantomor 11 Mar '07

11 Mar '07

In Postfix+Postfixadmin+Dovecot+SASL+MySQL case what is the best and compact MySQL database structure for storing all configuration? What will you suggest me guys? I've already installed postfixadmin and I'm confusing (actually my experience is not enough) extending and organizing my database for postfix+dovecot. Please give me some quick tips. -- Best regards, Erdenebat Guntomor/ /mailto:RkLogin@gmail.com

1 0

[Dovecot] FreeBSD 6.1-RELEASE/kqueue high CPU load
by Taras Savchuk 11 Mar '07

11 Mar '07

Hi to ALL! I have dovecot-1.0r7 installed on FreeBSD 6.1, using kqueue and Maildir (<20 mailboxes, < 0,5 Gb size). Periodically CPU load of imap processes increasing up to 60-80%. Is it normall behavior or not? May be somebody had such kind of problems? -- С уважением, Савчук Тарас ООО "Элантек" : Аутсорсинг ИТ, WEB-разработка +7 (495) 589 68 81 +7 (926) 575 22 11 http://www.elantech.ru info(a)elantech.ru

8 32

[Dovecot] dovecot and pine tab-completion
by Kyle Wheeler 11 Mar '07

11 Mar '07

Hello, So, I'm migrating from Binc to Dovecot, and one of my users has run into an odd complaint/issue. I don't know that it's a Dovecot issue necessarily, but maybe the people here know a fix anyway... The problem is that pine tab-completion now appends a "." to the end of folders that have sub-folders. In other words, say the user has these folders: INBOX INBOX.foo INBOX.foo.bar When he types in INBOX.f and hits tab, for some reason Pine completes that to: INBOX.foo. Note the "." on the end. This is annoying, because then to get into foo he has to hit the delete key first. With the Binc server, the delimiter was /, and INBOX/foo/ was a perfectly legitimate folder name (so he could just hit return). Does anyone have any suggestions for how to fix this? ~Kyle -- There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -- Ed Howdershelt

2 3

Re: [Dovecot] Dovecot Stable Version
by Erdenebat Gantomor 10 Mar '07

10 Mar '07

First I'm not enough in English. Therefore sorry about that. I mean just asking about roadmap. I just don't wanna force anyone. Sorry again Timo if i was bugging you. Best regards, Erdenebat Guntomor/ /mailto:RkLogin@gmail.com Charles Marcus wrote: > Erdenebat Gantomor wrote: >> Dovecot is now in release candidate. When will release stable? Is it >> safe to use in production? I mean now the Dovecot is stable enough to >> use in production? > > <sigh> > > Please stop bugging Timo about this... he will release it when it is > ready. > > Seriously - if you want a release version, I'm sure Timo will gladly > accept your payment and provide one. >

2 1

[Dovecot] logging volumes
by Kyle Wheeler 10 Mar '07

10 Mar '07

Hello! I’m in the process of migrating from BincIMAP to Dovecot, and I have a minor question. One of the things that Binc does is logs how many bytes of data it has sent as part of logging the log-out. Is there a way to get Dovecot to do that, or to calculate something similar? ~Kyle -- Racism is man's greatest threat to man---the maximum of hatred for a minimum of reason. -- Abraham Joshua Heschel

2 2

[Dovecot] Warning: I/O leak
by Steffen Kaiser 10 Mar '07

10 Mar '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, there is message from Jim Horner (16 November 2006 17:02:44) about this issue, too. For testing I start dovecot with dovecot -F, when I kill it via ^C sometimes there are log entries like this: dovecot: Mar 07 10:10:13 Warning: I/O leak: 0x804d890 (15) dovecot: Mar 07 10:10:13 Warning: I/O leak: 0x804d890 (26) (gdb) x 0x804d890 0x804d890 <login_process_input>: 0x81e58955 I guess it's not important because Dovecot is interrupted. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEUAwUBRe6DsC9SORjhbDpvAQIqPAf3YHKm9L4IjUEx72yfdlV5P/aCfjrTDby/ HVWTBZeYjyld5I3thxfPNU/gV9eklZlozvHw03Z0LwKejcQsVWLc1g6jbJIYcnlC fNARkgtJj3Hy8Fn6QKhHr4keiAiedVTrf0gTq+NtcTmLGgVREhnJWBift8efx12s cnxH7YaL+Mj9+BwqdyQ5DcALCFwsHSI7IROHobP8ZnfqAkpgwAnCuo8140C31g+t XamPVuSVnsTnObXh6ki64TFuTk+FvhuyzH3NhroUXKS0Tl21l7E6+sMH2m39junI uS6p3Yweg193qtJwh4KmYutco9SBKp7V85gbpz6EpSDgYgG9rI5o =MgrB -----END PGP SIGNATURE-----

2 1

[Dovecot] Wish to improve logging
by Steffen Kaiser 10 Mar '07

10 Mar '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I had a problem in my test configuration, therefore I want to suggest to improvements for logging: 1) mail_log - add mailbox of operation dovecot: Mar 07 09:35:16 Info: IMAP(dvtest) [16829]: expunged: uid=886, msgid=<xxxxxxxxxxxxxx.xxxxxxxxxxx(a)xxxxxxxx.xx-xxxx-xxxxx-xxxx.xx> dovecot: Mar 07 09:35:16 Info: IMAP(dvtest) [16829]: expunged: uid=887, msgid=<xxxxxxxxxxxx.xxxxx.xxxxxxxxx.xxxxxxxx(a)xx-xxxx-xxxxx-xxxx.xx> Please add, from which folder the mail is deleted/expunged, because uid is no unique throughout the mail storage and I do not find no tracking in which mailbox the operation happens. 2) Login - add which passdb / userdb the data was gathered from dovecot: Mar 07 09:34:03 Info: auth(default): ldap(dvtest,10.20.10.63): bind search: base=dc=fh-bonn-rhein-sieg,dc=de filter=(&(objectClass=fhMailAlias)(uid=dvtest)) dovecot: Mar 07 09:34:03 Info: auth(default): ldap(dvtest,10.20.10.63): result: uidNumber(userdb_uid)=1012 gidNumber(userdb_gid)=102 homeDirectory(userdb_home)=/home/dvtest uid(userdb_user)=dvtest mailLocationDovecot(userdb_mail)=maildir:/home/dvtestMAIL/MailDir:INDEX=/var/cache/dovecot/1012/index:CONTROL=/var/cache/dovecot/1012/index/control dovecot: Mar 07 09:34:03 Info: auth(default): ldap(dvtest,10.20.10.63): bind: dn=uid=dvtest,ou=staff,dc=fb02,dc=fh-bonn-rhein-sieg,dc=de dovecot: Mar 07 09:34:03 Info: auth(default): ldap(dvtest,10.20.10.63): invalid credentials dovecot: Mar 07 09:34:03 Info: auth(default): client out: OK 1 user=dvtest dovecot: Mar 07 09:34:03 Info: auth(default): master in: REQUEST 1 16810 1 dovecot: Mar 07 09:34:03 Info: auth(default): prefetch(dvtest,10.20.10.63): passdb didn't return userdb entries dovecot: Mar 07 09:34:03 Info: auth(default): ldap(dvtest,10.20.10.63): user search: base=dc=fh-bonn-rhein-sieg,dc=de scope=subtree filter=(&(objectClass=fhMailAlias)(uid=dvtest)) fields=homeDirectory,uidNumber,gidNumber,mailLocationDovecot,uid dovecot: Mar 07 09:34:03 Info: auth(default): master out: USER 1 dvtest uid=1012 gid=102 home=/home/dvtest user=dvtest mail=maildir:/home/dvtestMAIL/MailDir:INDEX=/var/cache/dovecot/1012/index:CONTROL=/var/cache/dovecot/1012/index/control dovecot: Mar 07 09:34:03 Info: pop3-login: Login: 16810:, user=<dvtest>, method=PLAIN, rip=10.20.10.63, lip=10.20.10.166 First I didn't realized any problem at all ;) and assumed LDAP bind working. Dovecot successfully reads the LDAP attributes for the user dvtest, however, the LDAP bind fails with "invalid credentials", yet, dvtest was allowed to login. The reason is simple: When I was testing the LDAP bind stuff, I "commented out" the user dvtest in /etc/passwd, but not in "/etc/shadow" and intentionally used another password in LDAP. Dovecot is configured to consult userdb/passdb ldap, first, then pam. In my case, the LDAP bind failed, so Dovecot fall back to pam - just as configured. I would like suggest to log wich passdb / userdb Dovecot gathered the information from, because, at first, I interpreted the log file as if Dovecot allows an user to login, who is not authentificated. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRe6N+y9SORjhbDpvAQJITQf6AmueszP73MBoG5mPRzB0mEzKC9jmY+gb eepPjBZp7yqXnACt7hOjcI0ckLZpgmQd4TbwVmO1otJaaQa/UZvgy1pV7gXeMTVs RZnAT7qiT7j+RB54yg1nT65/W9VmP3ymp41pi+qlWfC3qaVwsFk9hgarQC1FzF/w tD92cT8vvLPzXXf22xO6bmeTW4xg6fsUWbC7BiL461qJTMXjHGZdMwU7jPbTrI3c iYAel2jKAMaspgTpz/sEg3Yjka2tafinItnah8Q9HIQGixzUlV750NULx/jR8Cop 1ufFZSigkVRY25XpxESgCAaKQg3LsB7rnZOVyG/hA3KDmyh2+nu9Yw== =WUyX -----END PGP SIGNATURE-----

2 1

[Dovecot] RV: deliver configuration
by Luis Venegas 10 Mar '07

10 Mar '07

Sorry, but I can't see a file named auth-master in any place... Luis Venegas wrote: > Hi., > > I am trying to configure Virtual Users. Whenever I use: > "virtual_transport = dovecot" I get: > > deliver(user_at_domain): > net_connect(/usr/local/var/run/dovecot/auth-master) failed: No such file > or directory > See: http://wiki.dovecot.org/LDA You probably didn't define the 'socket listen' or it's a different path. --Chris __________ Información de NOD32, revisión 2105 (20070309) __________ Este mensaje ha sido analizado con NOD32 antivirus system http://www.nod32.com

2 1

[Dovecot] deliver configuration
by Luis Venegas 09 Mar '07

09 Mar '07

Hi., I am trying to configure Virtual Users. Whenever I use: "virtual_transport = dovecot" I get: deliver(user_at_domain): net_connect(/usr/local/var/run/dovecot/auth-master) failed: No such file or directory But it works when I use: "virtual_transport = virtual" What am I doing wrong? Thank you !

2 1

[Dovecot] Vexim with LDA delivery
by Chris Wopat 09 Mar '07

09 Mar '07

No support help needed, just a success report having Dovecot integrate with Vexim (exim with web based frontend and sql db): http://silverwraith.com/vexim/ Just wanted to forward some configs to the list if anyone finds them useful. I just switched from vexim's normal "virtual_delivery" to "dovecot_virtual_delivery" so I could use sieve, which works nicely with Horde. This is mostly as described on the wiki: http://wiki.dovecot.org/LDA I'm using maildirsize in my case. There were a few things that had to be done to get it to work with quotas, I thought I would just spell it all out for anyone reading this list in the future: I can add stuff if anyone would like to the wiki, some of these items are elsewhere in the wiki, I wanted to ask before I put a full page up for integration with Vexim in particular. Should I do this, or just throw bits and peices where they seem relevant? This was on FreeBSD, hence the /usr/local/etc/ stuff. Exim's 'configure' file: ================================ virtual_domains: #file_transport = virtual_delivery file_transport = dovecot_virtual_delivery virtual_domains_catchall: #file_transport = virtual_delivery file_transport = dovecot_virtual_delivery dovecot_virtual_delivery: driver = pipe command = /usr/local/libexec/dovecot/deliver -d \ $local_part@$domain message_prefix = message_suffix = delivery_date_add envelope_to_add return_path_add log_output user = mailnull dovecot-sql.conf: ================================ driver = mysql connect = host=HOSTNAME dbname=vexim user=vexim password=PASSWORD default_pass_scheme = CRYPT password_query = SELECT crypt as password FROM users,domains \ WHERE users.username = '%u' AND users.enabled = '1' \ AND users.type='local' and domains.enabled='1' \ AND domains.domain_id = users.domain_id user_query = SELECT pop AS home, 26 AS uid, 26 AS gid, \ CONCAT('maildir:storage=', quota*1024) AS quota \ FROM users WHERE username = '%u' AND enabled = '1' Mostly complete dovecot.conf (much of this is obvious, but it's easier than piecing things together from various mailing lists posts/docs): ================================ mail_location = maildir:%h/Maildir first_valid_gid = 26 last_valid_gid = 26 protocol lda { mail_plugins = quota } auth default { mechanisms = plain passdb sql { args = /usr/local/etc/dovecot-sql.conf } userdb sql { args = /usr/local/etc/dovecot-sql.conf } user = root socket listen { master { path = /var/run/dovecot/auth-master mode = 0660 user = mailnull group = mail } } } plugin { quota = maildir } ================================ --Chris

1 0

[Dovecot] mail archive
by T. Horsnell 09 Mar '07

09 Mar '07

I'd like to download a complete mail archive so that I can browse for problems concerning Mulberry. Is this possible, or can I only get them in monthly gulps? Cheers, Terry. --

5 7

[Dovecot] Bug: mbox-sync-parse.c: line 228
by Dean Quanne 09 Mar '07

09 Mar '07

[root@mail postfix]# dovecot --version 1.0.rc25 [root@mail postfix]# dovecot -n # /usr/local/etc/dovecot.conf ssl_cert_file: /usr/share/ssl/certs/dovecot.pem ssl_key_file: /usr/share/ssl/private/dovecot.pem login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mbox_write_locks: fcntl auth default: passdb: driver: pam userdb: driver: passwd Attempting to delete an email yields ... (from Thunderbird, Becky and Squirrel WebMail) Mar 5 23:58:30 localhost dovecot: imap-login: Login: user=<dean>, method=PLAIN, rip=192.168.0.81, lip=81.235.169.182, TLS Mar 5 23:58:30 localhost dovecot: IMAP(dean): file mbox-sync-parse.c: line 228 (parse_x_imap_base): assertion failed: (ctx->sync_ctx->next_uid > ctx->sync_ctx->prev_msg_uid) Mar 5 23:58:30 localhost dovecot: IMAP(dean): Raw backtrace: imap [0x80a8265] -> imap [0x80a7de7] -> imap [0x8070a04] -> imap [0x8070a17] -> imap(mbox_sync_parse_next_mail+0x200) [0x807101c] -> imap(mbox_sync_rewrite+0x94f) [0x8077813] -> imap [0x80724bc] -> imap(mbox_sync+0x3e2) [0x807447a] -> imap [0x806cd9a] -> imap(cmd_copy+0x23d) [0x8057599] -> imap(cmd_uid+0x76) [0x805a60a] -> imap [0x805afb6] -> imap [0x805af4a] -> imap(_client_input+0x78) [0x805b0fc] -> imap(io_loop_handler_run+0x131) [0x80ad9e1] -> imap(io_loop_run+0x21) [0x80acf79] -> imap(main+0x458) [0x8061fc4] -> /lib/tls/libc.so.6(__libc_start_main+0xd3) [0x467e23] -> imap [0x8056799] Mar 5 23:58:30 localhost dovecot: child 4221 (imap) killed with signal 6 -- Dean Quanne

3 3

[Dovecot] Dovecot vs Couir-IMAP
by Erdenebat Gantomor 09 Mar '07

09 Mar '07

I'm the beginner for IMAP/POP3 servers. I'm starting to use Dovecot. But I'm confusing between Courier-IMAP and Dovecot. Anyone tell me some quick tips regarding this issue. What's the better and what's the worst thing comparing these two IMAP/POP3 servers? I think the Dovecot is good enough for security and performance issue over Courier. Is it right? And how about the feature comparision? -- Best regards, Erdenebat Guntomor/ /mailto:RkLogin@gmail.com

9 11

[Dovecot] Dovecot's Sieve Support
by Robb Beal 09 Mar '07

09 Mar '07

Hi Folks, I'm looking for details of Dovecot's Sieve support. Specifically, Support for Sieve scripts (RFC 3028) and the protocol for remotely managing Sieve scripts, including: -- draft-martin-managesieve-06.txt -- draft-ietf-sieve-imapflags-05.txt And the following Sieve actions: -- fileinto -- redirect -- imapflags Thanks, Robb Beal -- www.laszlosystems.com --

2 1

[Dovecot] Dovecot Stable Version
by Erdenebat Gantomor 09 Mar '07

09 Mar '07

Dovecot is now in release candidate. When will release stable? Is it safe to use in production? I mean now the Dovecot is stable enough to use in production? -- Best regards, Erdenebat Guntomor/ /mailto:RkLogin@gmail.com

4 3

[Dovecot] global_script_path and virtual users
by Joan 09 Mar '07

09 Mar '07

We have a big installation with postfix + dovecot + sieve. Now we would like to create a "junk" folder in every customer inbox so they can discard the spam by they own. We are planning to user global_script_path = /etc/dovecot/dovecot.sieve Where /etc/dovecot/dovecot.sieve is: require "fileinto"; if exists "X-Spam-Flag" { fileinto "Junk"; } My question is, will the script find the users in our database? And how, will it be using the lda configuration? I have been for weeks looking for this in the wiki and couldn't find it anywhere. I promise I'll put it in there if I find the clue :)

2 1

Re: [Dovecot] Problems with different mail clients
by Nuno Miguel Neves 09 Mar '07

09 Mar '07

Hello, all. I thing I solved my problem... I just changed dovecot.conf to include the default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u which is disabled by default. Now, apparently, I can access my inbox from both my pocket and my Vista Mail. Than you all and hope this helps someone else. :) ----- Original Message ----- From: Nuno Miguel da Cruz Neves To: dovecot(a)dovecot.org Sent: Thursday, March 08, 2007 7:23 PM Subject: Problems with different mail clients I use dovecot as my imap server, and everything is ok. I used an IMAP client from Windows XP (Outlook Express) as well as Pocket PC (Windows Mobile 5) and webmail. The problem is that I recently used Windows Vista and its imap client (Windows Mail), and problems began. From the Windows XP machine, all is ok, but from the Pocket PC a weird thing happens: When I first configure the client, in the Received Items, it shows all items correctly, but then, when starting to donwload, they simply disappear. All other folders are OK. Problem is just in inbox. I thing (although my tests were not exaustive) that deleting the .imap folder solves the problem, but I just can't understand why, because it is recreated again... Any help? Thank you, ------------------------------------------------------------- Tel +351 21 3182720 | Fax +351 213146114 Email Nuno.Miguel.Neves(a)pkf.pt | www.pkf.pt PKF | Av. António Augusto de Aguiar, 108, 4º | 1050-019 Lisboa | Portugal

1 0

[Dovecot] "ldap_result() failed: Can't contact LDAP server" log messages
by Mike Brudenell 09 Mar '07

09 Mar '07

Greetings - I', continuing to build a test system that, at present, only I have access to. It is running Dovecot 1.0rc24. Here's the output of a "dovecot-n"... # /usr/local/etc/dovecot.conf log_path: /logfiles/mail/live/dovecot protocols: imap ssl_cert_file: /usr/local/etc/ssl/certs/imapservice-bundle.crt ssl_key_file: /usr/local/etc/ssl/private/imapservice-private.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_process_per_connection: no login_greeting_capability: yes mail_location: maildir:/mailstore/%1u/%u/Maildir:INDEX=/var/dovecot/ index/%1u/%u:CONTROL=/var/dovecot/control/%1u/%u mail_debug: yes mmap_disable: yes maildir_copy_with_hardlinks: yes mail_log_prefix: %Us(%u)[%p]: imap_client_workarounds: delay-newmail outlook-idle namespace: type: private separator: / inbox: yes auth default: mechanisms: plain login cache_size: 1024 cache_ttl: 600 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890 username_format: %Lu passdb: driver: ldap args: /usr/local/etc/dovecot-ldap-passdb.conf userdb: driver: ldap args: /usr/local/etc/dovecot-ldap-userdb.conf We are using LDAP for the passdb and userdb. The oddity is that even on a quiescent system (Dovecot started from scratch, but no connections being made to it) we are seeing these messages being logged, apparently every 5 minutes: dovecot: Mar 09 11:09:44 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server dovecot: Mar 09 11:09:44 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server dovecot: Mar 09 11:14:45 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server dovecot: Mar 09 11:14:45 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server dovecot: Mar 09 11:19:45 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server dovecot: Mar 09 11:19:45 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server I'm guessing there are two log entries each time because of separate connections being used for the passdb and userdb. The LDAP server *is* available throughout. I'm wondering if Dovecot is trying to hold the connection open but, after a timeout of 5 minutes of inactivity, the LDAP server is closing it and causing Dovecot to log this message. If this is indeed the case then I guess on a production server these message will be rarely if ever seen. Obviously I'd prefer not to have such worrying-sounding log entries appearing. (And if my guess is right then they're slightly misleading: the LDAP server *can* be contacted!) Any thoughts? Cheers, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. *

3 3

[Dovecot] deliver(redacted): Mar 08 10:13:03 Fatal: postmaster_address setting not given
by Larry Vaden 09 Mar '07

09 Mar '07

Hi, We're new to dovecot and like what we see so far, but Google doesn't seem to have much on this error message. What are the likely causes? Kind regards, Larry Vaden, CoFounder and CEO Internet Texoma, Inc. We Care About Your Connection The Market Leader In Texomaland Since 1995

3 2

Re: [Dovecot] 1.0rc26: ssl_verify_client=yes ?
by Apostolis Papagiannakis 09 Mar '07

09 Mar '07

> > Date: Thu, 08 Mar 2007 18:13:48 +0200 > From: Timo Sirainen <tss(a)iki.fi> > Subject: Re: [Dovecot] 1.0rc26: ssl_verify_client=yes ? > > On Thu, 2007-03-08 at 16:40 +0100, Steffen Kaiser wrote: > >> >> > On Thu, 8 Mar 2007, Timo Sirainen wrote: >> > >> >>>> > >> Q2) >>>> > >> The next step, if dovecot blocks the client because >>>> > >> of the verify_client_cert, how to create certs for OE, >>>> > >> Evolution and Thunderbird? >>>> >>> > > >>> > > I don't think most clients support SSL client certificates at all, >>> > > although I know some people are using them with some clients.. Maybe >>> > > someone could add a list of the clients supporting them into wiki. >>> >> > >> > Er, a dummy question, I guess: >> > Can you use client certs to login into Dovecot? >> > Aka can use the certs as "passdb"? >> > > Yes. It will still need some passdb, but you could use null password and > ssl_username_from_cert=yes settings in which case it doesn't matter what > user/password is used to log in. > > But it circumvents Dovecot's login/auth process security model, so I > don't recommend it that much. Maybe some day I'll make login process > forward the client cert to dovecot-auth which does the actual > verification. > I have successfully tested ssl_username_from_cert and found no real problem, apart from the fact that dovecot "username" takes the value of the certificate "CN" attribute , instead of the email attribute (in my case "Apostolos Papayanakis" instead of apap/ at /ccf.auth.gr). Everything else works as expected (eg, further userdb lookups based on certificate CN). Our University has issued a few thousand certificates with subjects such as "/C=GR/O=Aristotle University of Thessaloniki/OU=Network Operations Center/CN=Apostolos Papayanakis/emailAddress=apap/ at /ccf.auth.gr", that are used for administrative purposes. We would be very happy to use them as an alternative method of IMAP/POP3 authentication. However certificate CNs are not unique (e.g. "John Smith") and we would like to avoid constantly patching dovecot to use the email (or other) attribute from the certificate. I think replacing NID_commonName with NID_pkcs9_emailAddress ( or NID_subject_key_identifier, or NID_subject_alt_name) in login-common/ssl-proxy-openssl.c, line 527 would suffice. (X509_NAME_get_text_by_NID(X509_get_subject_name(x509), NID_commonName, buf, sizeof(buf)) < 0). Maybe I should post a complete patch if Timo is interested. Apostolis

3 2

[Dovecot] Seen this behavior before?
by hadmut＠danisch.de 09 Mar '07

09 Mar '07

Hi, it's not yet a bug report, just a question: After I was successfully using dovecot-imap and Thunderbird for quite a while without any problem (debian unstable), I now sometimes experience that the IMAP-connection hangs and thunderbird waits forever when accessing a folder. I did not yet analyze the problem and I am not sure whether it is a thunderbird or a dovecot problem. Did anyone see this behavior before? regards Hadmut

4 4

[Dovecot] any way to find last login time?
by Aleksey Perov 09 Mar '07

09 Mar '07

Hi, For some reason I need to regularly check which mailboxes are in use and which are not. For POP3, I use my patched version of popa3d which updates mtime on ~/Maildir/cur/ every time user logs in, and I always have a reliable way to find active and inactive mailboxes. Is there any way to find a last login time without parsing logs with dovecot? -- Aleksey

2 1

[Dovecot] Unable to authenticate system users in Dovecot 1.0rc25
by Malaney J. Hill 09 Mar '07

09 Mar '07

Hello, I recently installed dovecot1.0rc25 on my RHEL4 system running postfix and wish to use both virtual and system users. Virtuals work fine, but I get authentication failures with system users. I've tried pam, passwd and shadow. Attempting to telnet as system user telnet localhost 143 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. * OK Dovecot ready. a login user passwd a NO Authentication failed. and corresponding log Mar 3 14:35:24 obvx dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AG1o******************* Mar 3 14:35:27 obvx dovecot: auth(default): pam(myuser,127.0.0.1): pam_authenticate() failed: Authentication failure Mar 3 14:35:27 obvx dovecot: auth(default): passwd(myuser,127.0.0.1): password mismatch Mar 3 14:35:27 obvx dovecot: auth(default): client out: FAIL 1 user=myuser Below is the output of dovecot -n ============ # /etc/dovecot.conf protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login first_valid_uid: 101 last_valid_uid: 101 mail_extra_groups: mail mail_location: maildir:~/Maildir mail_debug: yes maildir_copy_with_hardlinks: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/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/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): outlook-idle pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: user: nobody verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/sql.conf passdb: driver: pam args: * passdb: driver: passwd userdb: driver: sql args: /etc/dovecot/sql.conf userdb: driver: passwd userdb: driver: prefetch socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: mail master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: mail plugin: quota: maildir:storage=10240:messages=1000 trash: /etc/dovecot/trash.conf ============= Thanks, Malaney

2 4

[Dovecot] Auth mechanism variable expansion?
by Bill Green 09 Mar '07

09 Mar '07

Hi all, Timo wrote in a message to the list in February that "%m variable expands to the auth mechanism name.". Indeed, the Wiki "Variables" page states that this is the case. However if I use %m in my SQL password query it does not get expanded. I'm using rc 25. What am I doing wrong?

2 1

[Dovecot] Message mixing after switchover from mbox to maildir
by Andrey Falko 09 Mar '07

09 Mar '07

Hi everyone, Here is the story. We are running Redhat Enterprise Linux 4, and were using Dovecot .99.x . At one point, we chose to switch from mbox to maildir (and still use Dovecot). After the switchover our users reported a bug when using Thunderbird: "A new behavior that I have observed a couple of times is that the new IMAP server confuses email headers with content. E.g., I have an email from Person X, but when I go to view it, the contents is just a spam body from an adjacent header. With this specific bug, adjacent spams are also running into other bodies. This occurs I'd say once every hundred messages. Other appearances of this bug are with adjacent messages concatenated. I'm not sure how to explain this, maybe what happens is that the new IMAP server confuses requests and delivers the wrong message bodies to the client, which get cached. This could in some circumstances be more than an annoyance, e.g., with confidential emails inadvertently getting picked up in replies to people outside the company." We proceeded to update Dovecot to the latest available version (1.0.0-rc25). However, despite that, our users still report the same bug: "This bug still persists. In particular, I just (after the new version was applied) clicked on an email from Person X, and Thunderbird displayed an email from Person Y that I had just replied to. Note that the email from Y was not adjacent to the one from X (at least, in the temporal ordering)." I have not been able to reproduce the bug myself. Can anyone think of where we should start debugging? Best regards, Andrey Falko

2 1

[Dovecot] Problems with different mail clients
by Nuno Miguel da Cruz Neves 08 Mar '07

08 Mar '07

I use dovecot as my imap server, and everything is ok. I used an IMAP client from Windows XP (Outlook Express) as well as Pocket PC (Windows Mobile 5) and webmail. The problem is that I recently used Windows Vista and its imap client (Windows Mail), and problems began. >From the Windows XP machine, all is ok, but from the Pocket PC a weird thing happens: When I first configure the client, in the Received Items, it shows all items correctly, but then, when starting to donwload, they simply disappear. All other folders are OK. Problem is just in inbox. I thing (although my tests were not exaustive) that deleting the .imap folder solves the problem, but I just can't understand why, because it is recreated again... Any help? Thank you, ------------------------------------------------------------- Tel +351 21 3182720 | Fax +351 213146114 Email Nuno.Miguel.Neves(a)pkf.pt | www.pkf.pt PKF | Av. António Augusto de Aguiar, 108, 4º | 1050-019 Lisboa | Portugal

2 1

[Dovecot] dovecot sasl auth (pam) + postfix doesn't work...
by marco ghidinelli 08 Mar '07

08 Mar '07

hello, i tried to use the "dovecot sasl" with postfix using pam as backend (actually pam_krb5) but it doesn't work. dovecot runs well as pop3 server authenticating with the pam_krb5 module with the config below, but it doesn't even connect with the kerberos server (a remote AD 2003) when it's called from postfix. --------dovecot.conf--------- protocols = pop3 pop3s imap imaps disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/var/mail/vhosts/turboden.net/%Ln/ mail_extra_groups = mail protocol imap { } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } auth_default_realm = MYCORP.LOCAL auth_verbose = yes auth_debug = yes auth default { mechanisms = plain login passdb pam { args = dovecot } userdb static { args = uid=5000 gid=5000 } user = root socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } dict { } plugin { } -------------------------------- -----/etc/pam.d/dovecot------ auth required pam_krb5.so no_ccache ignore_root debug account required pam_permit.so ----------------------------- from syslog i only get: Mar 8 10:52:38 muletto dovecot: auth(default): client in: AUTH^I1^Iplain^Iservice=smtp^Iresp=<hidden> Mar 8 10:52:38 muletto dovecot: auth(default): passdb(username(a)MYCORP.LOCAL,master): Attempted master login with no master passdbs Mar 8 10:52:39 muletto dovecot: auth(default): client out: FAIL^I1^Iuser=username(a)MYCORP.LOCAL note that it doesn't care about the content of the /etc/pam.d/dovecot when dovecot is called by postfix. does the dovecot-sasl authentication works with the pam backend? maybe i should rename (or copy) the /etc/pam.d/dovecot to another name? let me know. bye.

2 1