- dovecot - dovecot.org

[Dovecot] UID inserted in the middle of mailbox
by Nicolas STRANSKY 28 Feb '05

28 Feb '05

I'm seeing these with latest 1.0-stable : Feb 27 16:48:12 zamok dovecot: POP3(****): mbox sync: UID inserted in the middle of mailbox /var/mail/**** (176 > 150) Feb 27 16:49:58 zamok dovecot: POP3(****): mbox sync: UID inserted in the middle of mailbox /var/mail/**** (4409 > 4237) Feb 27 16:50:04 zamok dovecot: IMAP(****): mbox sync: UID inserted in the middle of mailbox /var/mail/**** (7122 > 5116) Feb 27 16:50:16 zamok dovecot: IMAP(****): mbox sync: UID inserted in the middle of mailbox /home/****/Mail/trash (15571 > 14535) Feb 27 16:50:16 zamok dovecot: IMAP(****): mbox sync: UID inserted in the middle of mailbox /home/****/Mail/trash (16578 > 14535) Feb 27 16:50:19 zamok dovecot: IMAP(****): mbox sync: UID inserted in the middle of mailbox /var/mail/**** (23318 > 13713) -- Nico L'étude approfondie de la nature est la source la plus féconde des découvertes mathématiques. -+- Joseph Fourier -+-

2 1

[Dovecot] Protect some mailbox to remove
by FireFly 25 Feb '05

25 Feb '05

I've installed dovecot 0.99.14 (maildir, postfix, RHEL3) and I would like to create , for every user, 4 mailbox (in skel): mail-sent, spam, virus-alert and sysadm. Procmail, parsing header mail, will move mails into a specific mailbox. Every users could move, delete, read these mails but they must not delete mailbox folder (such as INBOX mail). Thanks in advance, Francesco __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

[Dovecot] APOP
by Steven Stern 25 Feb '05

25 Feb '05

I want to turn off POP3 and use POP3S in its place. So far, it's working well for Outlook and Thunderbird. But I'm running into problems with Agent: It supports APOP but not POP3S. Is there a way to have Dovecot support APOP authentication on a normal POP3 connection? I'm running 0.99.13 on Fedora Core 3. -- Steve

2 1

[Dovecot] A few words about NFS please?
by Jeff A. Earickson 25 Feb '05

25 Feb '05

Hi, Could you say a few words about Dovecot and POP/IMAP to an NFS mounted filesystem? I thought I saw on the dovecot webpage that NFS is "no way" with 0.99 and "maybe" with 1.x. I was looking for the FAQ and couldn't find it. My setup is like so: My mail server is a Solaris 9 system, running sendmail/procmail, and qpopper POP. Mail is stored in mbox format. The /var/mail filesystem is NFS exported to another Solaris 9 system that runs UW-IMAP. The user community also has login access to this second system, so there are also local email clients like Pine and emacs using the NFS /var/mail. So, POP and sendmail/procmail accesses /var/mail locally, while UW-IMAP accesses it via NFS. The user community has been warned to do either POP or IMAP, but not both. There are very few problems with this setup. I would like to use Dovecot for both POP and IMAP on the two machines. I know NFS is frowned upon, but this has worked for me. Comments and suggestions, please? Jeff Earickson Colby College

4 3

[Dovecot] Inotify
by Nicolas STRANSKY 25 Feb '05

25 Feb '05

Hi, Is there any plans to use the Linux inotify, which is a major improvement over dnotify ? (Linux mechanism for communicating filesystem events to user space) Regards, -- Nico Écrivez dans l'ivresse, mais relisez-vous à jeun. -+- André Gide (1869-1951) -+-

2 1

[Dovecot] Authentication woes
by woollettg 25 Feb '05

25 Feb '05

I having a hard time working this out, I've looked in the wiki and various other places but am still cueless (stupid me) mercury:/etc/dovecot# imtest -a graeme 203.96.154.204 S: * OK dovecot ready. C: C01 CAPABILITY S: * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE STARTTLS AUTH=PLAIN S: C01 OK Capability completed. Authentication failed. no mechanism available Security strength factor: 0 mercury:/etc/dovecot# Below is my configuration file for version 0.99-14.1 on a Debian Sarge box I'm quite happy with plaintext auth for now. Any help or suggestions much appreciated. Graeme ## Dovecot 1.0 configuration file # 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/dovecot # --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 # 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. You can specify ports with # "host:port". #imap_listen = * #pop3_listen = * # IP or host address where to listen in for SSL connections. Defaults # to above non-SSL equilevants if not specified. #imaps_listen = #pop3s_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. #ssl_cert_file = /etc/ssl/certs/dovecot.pem #ssl_key_file = /etc/ssl/private/dovecot.pem # 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 # 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 = # 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 " ## ## 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 ## ## IMAP login process ## login = imap # Executable location. login_executable = /usr/lib/dovecot/imap-login # 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 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 ## ## POP3 login process ## # Settings default to same as above, so you don't have to set anything # unless you want to override them. login = pop3 # Exception to above rule being the executable location. #login_executable = /usr/lib/dovecot/pop3-login ## ## 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 = mail # ':' 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 # /usr/share/doc/dovecot-common/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden by # giving /./ in user's home directory (eg. /home/./user chroots into /home). #mail_chroot = # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # /usr/share/doc/dovecot-common/mail-storages.txt. There's a few special # variables you can use: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if user there's no domain # %h - home directory # # You can also limit a width of string by giving the number of max. characters # after the '%' character. For example %1u gives the first character of # username. 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 = # Space-separated list of fields to cache for all mails. Currently these # fields are allowed followed by a list of commands they speed up: # # Envelope - FETCH ENVELOPE and SEARCH FROM, TO, CC, BCC, SUBJECT, # SENTBEFORE, SENTON, SENTSINCE, HEADER MESSAGE-ID, # HEADER IN-REPLY-TO # Body - FETCH BODY # Bodystructure - FETCH BODY, BODYSTRUCTURE # MessagePart - FETCH BODY[1.2.3] (ie. body parts), RFC822.SIZE, # SEARCH SMALLER, LARGER, also speeds up BODY/BODYSTRUCTURE # generation. This is always set with mbox mailboxes, and # also default with Maildir. # # Different IMAP clients work in different ways, that's why Dovecot by default # only caches MessagePart which speeds up most operations. Whenever client # does something where caching could be used, the field is automatically marked # to be cached later. For example after FETCH BODY the BODY will be cached # for all new messages. Normally you should leave this alone, unless you know # what most of your IMAP clients are. Caching more fields than needed makes # the index files larger and generate useless I/O. # # With maildir there's one extra optimization - if nothing is cached, indexing # the maildir becomes much faster since it's not opening any of the mail files. # This could be useful if your IMAP clients access only new mails. #mail_cache_fields = MessagePart # Space-separated list of fields that Dovecot should never set to be cached. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Workarounds for various client bugs: # oe6-fetch-no-newmail: # Never send EXISTS/RECENT when replying to FETCH command. Outlook Express # seems to think they are FETCH replies and gives user "Message no longer # in server" error. 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. # outlook-pop3-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. #client_workarounds = # Dovecot can notify client of new mail in selected mailbox soon after it's # received. This setting specifies the minimum interval in seconds between # new mail notifications to client - internally they may be checked more or # less often. Setting this to 0 disables the checking. # NOTE: Evolution client breaks with this option when it's trying to APPEND. #mailbox_check_interval = 0 # 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 custom flag name. It's only forced when trying # to create new flags. #mail_max_flag_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. #mail_read_mmaped = no # 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 # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing messages are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's three 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. # # You can use both fcntl and flock too; if you do the order they're declared # with is important to avoid deadlocks if other MTAs/MUAs are using both fcntl # and flock. Some operating systems don't allow using both of them # simultaneously, eg. BSDs. If dotlock is used, it's always created first. #mbox_locks = dotlock fcntl # Should we create dotlock file even when we want only a read-lock? Setting # this to yes hurts the performance when the mailbox is accessed simultaneously # by multiple processes, but it's needed for reliable reading if no other # locking methods are available. #mbox_read_dotlock = no # 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 # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. Note that setting # this to yes means that log file is opened as the logged in user, which # might not work. It could also 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 ## ## IMAP process ## # Executable location imap_executable = /usr/lib/dovecot/imap # 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. #imap_process_size = 256 # Support for dynamically loadable modules. #imap_use_modules = no imap_modules = /usr/lib/dovecot/imap ## ## POP3 process ## # Executable location #pop3_executable = /usr/lib/dovecot/pop3 # 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. #pop3_process_size = 256 # Support for dynamically loadable modules. #pop3_use_modules = no #pop3_modules = /usr/lib/dovecot/pop3 ## ## Authentication processes ## # An Authentication process is a child process used by Dovecot that # handles the authentication steps. The steps cover an authentication # mechanism (auth_mechanisms, how the client authenticates in the IMAP or # POP3 protocol), which password database should be queried (auth_passdb), # and which user database should be queried (auth_userdb, to obtain # UID, GID, and location of the user's mailbox/home directory). # # You can have multiple processes, though a typical configuration will # have only one. Each time "auth = xx" is seen, a new process # definition is started. The point of multiple processes is to be able # to set stricter permissions. (See auth_user below.) # # Just remember that only one Authentication process is asked for the # password, so you can't have different passwords accessible through # different process definitions (unless they have different # auth_mechanisms, and you're ok with having different password for # each mechanisms). # Authentication process name. auth = default # Specifies how the client authenticates in the IMAP protocol. # Space separated list of permitted authentication mechanisms: # anonymous plain digest-md5 cram-md5 # # anonymous - No authentication required. # plain - The password is sent as plain text. All IMAP/POP3 clients # support this, and the password can be encrypted by Dovecot to match # any of the encryption schemes used in password databases. # digest-md5 and cram-md5 - both encrypt the password so it is more # secure in transit, but are not well supported by clients, and # require that the password database use a matching encryption # scheme (or be in plaintext). # # See auth.txt for more details. # # If you are using SSL there is less benefit to digest-md5 and # cram-md5 as the communication is already encrypted. auth_mechanisms = plain # 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 = # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # http://wiki.dovecot.org/Authentication # http://wiki.dovecot.org/VirtualUsers # passwd: /etc/passwd or similiar, using getpwnam() # passwd-file <path>: passwd-like file with specified location # static uid=<uid> gid=<gid> home=<dir template>: static settings # vpopmail: vpopmail library # ldap <config path>: LDAP, see /etc/dovecot/dovecot-ldap.conf # mysql <config path>: a MySQL database, see /etc/dovecot/dovecot-mysql.conf # pgsql <config path>: a PostgreSQL database, see # /etc/dovecot/dovecot-pgsql.conf auth_userdb = passwd # Password database specifies only the passwords for users. # http://wiki.dovecot.org/Authentication # passwd: /etc/passwd or similiar, using getpwnam() # shadow: /etc/shadow or similiar, using getspnam() # pam [<service> | *]: PAM authentication # passwd-file <path>: passwd-like file with specified location # vpopmail: vpopmail authentication # ldap <config path>: LDAP, see /etc/dovecot/dovecot-ldap.conf # mysql <config path>: a MySQL database, see /etc/dovecot/dovecot-mysql.conf # pgsql <config path>: a PostgreSQL database, see # /etc/dovecot/dovecot-pgsql.conf auth_passdb = passwd #auth_executable = /usr/lib/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # 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 auth_userdb above. auth_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. #auth_chroot = # Number of authentication processes to create #auth_count = 1 # 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 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 # digest-md5 authentication process. It requires special MD5 passwords which # /etc/shadow and PAM doesn't support, so we never need roots to handle it. # Note that the passwd-file is opened before chrooting and dropping root # privileges, so it may be 0600-root owned file. #auth = digest_md5 #auth_mechanisms = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = # if you plan to use only passwd-file, you don't need the two auth processes, # simply set "auth_methods = plain digest-md5"

3 2

[Dovecot] Re: Problems with MySQL/PAM authentication
by KATOH Yasufumi 25 Feb '05

25 Feb '05

> I'm using (or trying to at least) a combination of PAM/passwd and MySQL > authentication: : (snip) > MySQL authentication works without problems but authentication real > (system) users dosn't: : I have similar problem using Multiple Auth Database: auth virtual { mechanisms = plain userdb = passwd-file /etc/dovecot/passwd passdb = passwd-file /etc/dovecot/passwd user = root } auth local { mechanisms = plain userdb = passwd passdb = shadow user = root } I tested: | % telnet localhost 143 | Trying 127.0.0.1... | Connected to localhost. | Escape character is '^]'. | * OK Dovecot ready. | 1 login kato(a)harp.gr.jp password | 1 NO Authentication failed. | 1 login kato(a)harp.gr.jp password | 1 OK Logged in. | 1 logout | * BYE Logging out | 1 OK Logout completed. | Connection closed by foreign host. "kato(a)harp.gr.jp" is registered in /etc/dovecot/passwd. First time it failed, but success at second time. "auth local" works without problem. | Feb 24 11:19:24 tara dovecot: auth(local): shadow(kato(a)harp.gr.jp,127.0.0.1): unknown user | Feb 24 11:19:33 tara dovecot: auth(local): shadow(kato(a)harp.gr.jp,127.0.0.1): unknown user | Feb 24 11:19:33 tara dovecot: auth(virtual): userdb(kato(a)harp.gr.jp,127.0.0.1): uid=1000 gid=100 home=/home/kato mail= | Feb 24 11:19:33 tara dovecot: IMAP(kato(a)harp.gr.jp): mkdir(/home/kato(a)harp.gr.jp/Maildir/cur) failed: Permission denied | Feb 24 11:19:33 tara dovecot: imap-login: Login: kato(a)harp.gr.jp [127.0.0.1] | Feb 24 11:19:35 tara dovecot: auth(local): file auth-client-connection.c: line 31 (auth_client_send): assertion failed: (conn->refcount > 1) | Feb 24 11:19:35 tara dovecot: child 14884 (auth) killed with signal 6 I rewritten dovecot.conf and tested. The result is different. auth local { mechanisms = plain userdb = passwd passdb = shadow user = root } auth virtual { mechanisms = plain userdb = passwd-file /etc/dovecot/passwd passdb = passwd-file /etc/dovecot/passwd user = root } At this time, "auth virtual" work, and "auth local" doesn't work. | * OK Dovecot ready. | 1 login kato(a)harp.gr.jp password | 1 OK Logged in. | 1 logout | * BYE Logging out | 1 OK Logout completed. | * OK Dovecot ready. | 1 login kato password | 1 NO Authentication failed. | 1 login kato password | 1 OK Logged in. | 1 logout | * BYE Logging out | 1 OK Logout completed. (kato is system user) | Feb 24 11:28:52 tara dovecot: auth(virtual): passwd-file(kato,127.0.0.1): unknown user | Feb 24 11:28:59 tara dovecot: auth(virtual): passwd-file(kato,127.0.0.1): unknown user | Feb 24 11:28:59 tara dovecot: auth(local): userdb(kato,127.0.0.1): uid=1000 gid=100 home=/home/kato mail= | Feb 24 11:28:59 tara dovecot: imap-login: Login: kato [127.0.0.1] | Feb 24 11:28:59 tara dovecot: auth(virtual): file auth-client-connection.c: line 31 (auth_client_send): assertion failed: (conn->refcount > 1) | Feb 24 11:28:59 tara dovecot: child 14924 (auth) killed with signal 6 It is not worked well to write configuration previously, but worked well to write after. I tested with ldap auth instead of paswd-file auth. I got same result. Env: Plamo Linux 4.01 (kernel 2.6.10, glibc 2.3.2) dovcot-1.0-test62, dovecot-stable-20050222 -- karma @ jazz.email.ne.jp / Y.KATOH Sorry for my poor English.

2 2

[Dovecot] Limit Number of Postgres Database Connections
by Dan Fitzpatrick 25 Feb '05

25 Feb '05

I have dovecot running with postgres backend. I am exceeding my maximum database connections (currently 40) with dovecot 0.99.10.9 and postfix and was wondering if dovecot has a parameter to limit the total number of database connections that it will create. Dan

2 1

[Dovecot] mozilla, error in imap command uid
by Nicolas Kowalski 24 Feb '05

24 Feb '05

Hello. Mozilla (1.7.3) gives me the following error message when trying to view some messages: the mail server responded: Error in IMAP command UID: Invalid BODY[..] parameter: Missing '>' in '<10240.-7730>'. What's wrong ? Thanks. -- Nicolas

5 9

[Dovecot] Nightly stable & SSL-problems
by Jani Karlsson 23 Feb '05

23 Feb '05

Getting it otherwise to work, but I still can't get it to listen any SSL-ports. been testing: protocols = imap imaps pop3 pop3s listen = 193.65.59.150 ssl_listen = 193.65.59.150 doesn't help. with: ssl_disable = no of course. protocol imap { # Login executable location. login_executable = /usr/local/libexec/dovecot/imap-login # IMAP executable location mail_executable = /usr/local/libexec/dovecot/imap ssl_listen = 193.65.59.150 .... } tried it there also.. yet: tcp 0 0 193.65.59.150:110 0.0.0.0:* LISTEN 29030/dovecot tcp 0 0 193.65.59.150:143 0.0.0.0:* LISTEN 29030/dovecot is the result I get. Anyone succeeded in this? Platform is Debian/Linux, running 2.4 series kernel, compiled with openssl-support. Version is dovecot-stable-20050221. All help appreciated. Jani Karlsson

2 1

[Dovecot] Build error in stable branch
by Andrew Hutchings 23 Feb '05

23 Feb '05

Hi guys, Just tested yesterday's stable build, when including SQL into the build I am getting an error on like 86 of passdb-sql.c (passdb_result = PASSDB_RESULT_OK;) It rightly says passdb_result is undeclared. Commenting out this line fixes it and build appears to work fine after that. Regards Andrew -- Andrew Hutchings Linux Guru Netserve Consultants Ltd. http://www.domaincity.co.uk/

1 0

[Dovecot] Problems with Dovecot and self-signed cert
by Seth Bokelman 22 Feb '05

22 Feb '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've recently set up a Red Hat Enterprise Linux 4 WS server, and decided to try using Dovecot as my IMAP server, as I was impressed with the dedication to security that seems to be the core development goal. I'm really happy with it, but I can't get it to work with a self-signed cert. Normally, on a RHEL system, you just go into /user/share/ssl/certs/ and type: make whatever.pem Then you fill out the various address fields, and you've got a cert. However, when I rename/delete the existing dovecot.pem and generate a new one using this method, Dovecot won't start and I'm unable to connect to the box. The cert that it's currently using is called "localhost.localdomain", and while that works, mail clients gripe every time about the domain name not matching the certificate. I've looked through the RHEL documentation, and it appears I'm doing everything correct. Anyone have any suggestions? - -- Seth H. Bokelman (Seth.Bokelman(a)UNI.edu) Systems Administrator ITS-Network Services, University of Northern Iowa 15 Curris Business Building, Cedar Falls, Iowa 50614 Phone: (319) 273-7423 http://www.sethb.com/ ICQ#: 6497760 MSN Messenger: seth.bokelman(a)uni.edu AOL/AIM: sethb2 Yahoo Messenger: sethbokelman -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCG3QhOiUz+Af5BIIRAv0VAKCm9JlKio9Z9Dzdr+WnZVtoYBNVqACdHNQH TuiLbT6yIXmeJLFg9ggibcM= =yPVK -----END PGP SIGNATURE-----

2 2

Re: [Dovecot] apple mail, and mails marked as deleted
by Joerg Lentsch 22 Feb '05

22 Feb '05

On 22.02.2005, at 03:17, Jim Tittsler wrote: > On Feb 22, 2005, at 04:36, Joerg Lentsch wrote: > >> is this a feature or a bug in conjunction with apple mail. i usually >> use the feature in imap to not delete the emails, but only mark them >> as deleted, which is a very usefull feature if you use a emailbox >> with more people accessing it. Im now trying an SME server >> installation with dovecot 0.99.10, and when i delete a message, it >> gets marked as deletet, but as soon as i change the mailbox the mail >> gets also expunged from it. is this a bug fixed in the newer dovecot >> releases ? or is this a feature that i can configure ? > > Do you have Mail.app set to "Compact mailboxes automatically" (on the > Advanced tab of the preferences for the account you are using)? When > that is checked, Mail.app issues an IMAP CLOSE command when you leave > a mailbox, which removes messages with the \Deleted flag set. > Hi there! thank you all for the answer. Yes indeed, after trying all the various options on the mail client, i discovered that it was this "Compact" switch. Thanks again for your help. /Maximus -- W.E.L.T. - Joerg Lentsch Mitterweg 16 Via di mezzo ai piani Tel: +39 0471 973020 I-39100 Bozen Bolzano Fax:+39 0471 974131 Suedtirol - Italien - Italia

1 0

[Dovecot] uw-imap and gnu-pop3d to dovecot transition/replacement
by Jani Karlsson 22 Feb '05

22 Feb '05

Hi I am trying directly to replace old uw-imap + GNU pop3d with Dovecot. Problems I am having with new (1.0-stable 22.02.2005) are: - How to get SSL working with new config? imaps_listen doesn't exist anymore. cannot add protocol imaps for some reason. - need to get Dovecot run on another port the test-phase, ie 144 for imap, 994 for IMAPs - need to use .mailboxlist (modified the source already, this maybe works - due SSL problem not tested?) - no symlinks etc can't be done (simply too many mailboxes) so how to make dovecot read IMAP-directories from user's homedir.. Anything else I should know before trying this transition? All help truely appreciated. Jani. (Mailbox count is high which why transition to faster postclient-server software is necessary - or adding few more dual CPU-servers.. and doing anything but editing config/such by hand is not a option.)

2 2

[Dovecot] apple mail, and mails marked as deleted
by Joerg Lentsch 22 Feb '05

22 Feb '05

hi, is this a feature or a bug in conjunction with apple mail. i usually use the feature in imap to not delete the emails, but only mark them as deleted, which is a very usefull feature if you use a emailbox with more people accessing it. Im now trying an SME server installation with dovecot 0.99.10, and when i delete a message, it gets marked as deletet, but as soon as i change the mailbox the mail gets also expunged from it. is this a bug fixed in the newer dovecot releases ? or is this a feature that i can configure ? TIA /Maximus -- W.E.L.T. - Joerg Lentsch Mitterweg 16 Via di mezzo ai piani Tel: +39 0471 973020 I-39100 Bozen Bolzano Fax:+39 0471 974131 Suedtirol - Italien - Italia

3 2

[Dovecot] Bug?: Authentication still doesn't work with imap-login
by Peter Franck 21 Feb '05

21 Feb '05

I tried digging it all through. I can't find a solution. The problem pops up in auth-master-connection.c in function master_input_request. It does a auth_client_connection_lookup with the "client_pid" (which behaves as a counter, where i would expect a constant process-id...) Something is very wrong with this PID. Maybe someone can explain the Master <--> Auth IPC to me so I can understand and fix it myself? Where does Master take this client number from? Hints are highly appreciated, Peter --- LOG --- Feb 21 21:04:36 office dovecot: Dovecot v1.0-test62 starting up Feb 21 21:04:48 office dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=192.168.23.1 rip=192.168.23.42 resp=AHZpYwBzeXNpbnQyMQ== Feb 21 21:04:48 office dovecot: auth(default): client out: OK 1 user=vic Feb 21 21:04:48 office dovecot: auth(default): master in: REQUEST 1 2 1 Feb 21 21:04:48 office dovecot: auth(default): Master requested auth for nonexisting client 2 --- my configuration: --- base_dir = /var/run/dovecot/ protocols = imap imaps ssl_cert_file = /etc/ssl/certs/imapd-192.168.23.1.pem ssl_key_file = /etc/ssl/certs/imapd-192.168.23.1.pem protocol imap { } protocol pop3 { } auth_verbose = yes auth_debug = yes auth default { mechanisms = plain passdb = pam imap userdb = passwd user = root }

1 1

[Dovecot] index corruption with test62 on openbsd 3.6
by Ben Lovett 21 Feb '05

21 Feb '05

i noticed this while browsing through my maillog.. Feb 21 11:27:43 selenium dovecot: IMAP(ben): Corrupted index cache file /u/home/ben/Maildir/.INBOX.ML-SunHELP.rescue/dovecot.index.cache: field index too large (3337 >= 22) i have no problems reading that box after this, and see no other messages about corrupt index files from today, or the past 14 days. --ben

1 0

[Dovecot] Dovecot SSL-Certificate
by Adam Pordzik 21 Feb '05

21 Feb '05

Hello, I've a not really dovecot specific problem with my certificate. Since the OpenSSL documentation isn't what I expect to be at least good, I hope someone here can give me a hint how/where fo fix it; I've created a root-Certificate with almost untouched openssl.cnf and issued a server-certificate for dovecot. This cert and it's key I placed in somewhat like /var/dovecot. To state explicitly, away from it's superior root-cert. So, a: openssl s_client -connect server.tektoform.lan:993 -showcerts ends up in: unable to get local issuer certificate. Althougt connections from clients are working, I prefer to set it up cleanly. Does openssl-clientlib looks up for openssl.cnf, where the place of root-CA-cert is denoted, or do I have to put all cert together in a single directory, or, or, or ...? Or to be more verbose for "openssl s_client": CONNECTED(00000003) depth=0 /C=DE/ST=Hamburg/L=Hamburg/O=d-dt/OU=lan/CN=server.tektoform.lan/emailAddress=hostmaster(a)tektoform.lan verify error:num=20:unable to get local issuer certificate verify return:1 depth=0 /C=DE/ST=Hamburg/L=Hamburg/O=d-dt/OU=lan/CN=server.tektoform.lan/emailAddress=hostmaster(a)tektoform.lan verify error:num=27:certificate not trusted verify return:1 depth=0 /C=DE/ST=Hamburg/L=Hamburg/O=d-dt/OU=lan/CN=server.tektoform.lan/emailAddress=hostmaster(a)tektoform.lan verify error:num=21:unable to verify the first certificate verify return:1 --- Thanks for your comments. A --

2 1

[Dovecot] login: Missing protocol from server name 'imap'
by Peter Franck 20 Feb '05

20 Feb '05

I also tried the 0.99 and hacking login-process.c, with no success. It seems to expect a slash delimited string like 'name/protocol' and it just gets "imap" there, but I didn't figure out where this string comes from or what it ought to be. So I would be grateful if someone could enlighten me. Thanks, Peter --- Some blafa: Feb 17 21:45:44 office dovecot: Dovecot v1.0-test59 starting up Feb 17 21:45:44 office dovecot: login: Missing protocol from server name 'imap' Linux office 2.4.20-64GB-SMP #1 SMP Fri Jan 14 15:08:48 UTC 2005 i686 unknown unknown GNU/Linux Client: Mozilla Thunderbird 1.0 (20041206) IMAPS port 993 Dovecot Started by xinetd: # # imaps - imap mail daemon over ssl # service imaps { disable = no socket_type = stream protocol = tcp wait = no user = root server = /usr/libexec/dovecot/imap-login server_args = --ssl flags = IPv4 }

3 6

[Dovecot] Re: Need 2 additional folders like INBOX for JUNK and INFECTED mails
by Mirko Schulze 17 Feb '05

17 Feb '05

Hi there. I've solved now the problem, but it's not really fine yet. The "special-folders" are undeletable in the filesystem, but the Mailclient displays different errormessages for the same action. I've modified following source files. The new additional lines are similar to the INBOX "lines" /src/imap/cmd-list.c: 63 /src/imap/cmd-delete.c :20 /src/lib-storage/index/maildir/maildir-storage: 294,308,437,601 Notice that the linenumbers are not really correct, because of the deferrals by inserting new sourcecode. The new problem is, that the mailclient displays incorrect error messages. When i use another folder caching method i'll get no errors. Perhaps someone has a better solution, than i? Thanks Mirko

1 0

[Dovecot] Problems with MySQL/PAM authentication
by Allan Joergensen 17 Feb '05

17 Feb '05

Hi, I'm using (or trying to at least) a combination of PAM/passwd and MySQL authentication: auth vmail { mechanisms = plain userdb = sql /etc/dovecot/dovecot-sql.conf passdb = sql /etc/dovecot/dovecot-sql.conf user = root } auth system { mechanisms = plain userdb = passwd passdb = pam imap user = root } MySQL authentication works without problems but authentication real (system) users dosn't: Feb 13 02:05:57 coredump dovecot: auth(vmail): sql(alj,127.0.0.1): query: SELECT crypt AS password FROM passwd WHERE id = 'al j' Feb 13 02:05:57 coredump dovecot: auth(vmail): sql(alj,127.0.0.1): unknown user Feb 13 02:05:57 coredump dovecot: auth(system): userdb(alj,127.0.0.1): uid=10000 gid=1000 home=/home/alj mail= Feb 13 02:05:57 coredump dovecot: imap-login: Login: alj [127.0.0.1] Feb 13 02:05:57 coredump dovecot: auth(system): userdb(alj,127.0.0.1): uid=10000 gid=1000 home=/home/alj mail= Feb 13 02:05:57 coredump dovecot: imap-login: Login: alj [127.0.0.1] Feb 13 02:05:57 coredump dovecot: auth(system): userdb(alj,127.0.0.1): uid=10000 gid=1000 home=/home/alj mail= Feb 13 02:05:57 coredump dovecot: imap-login: Login: alj [127.0.0.1] Feb 13 02:05:57 coredump dovecot: auth(system): userdb(alj,127.0.0.1): uid=10000 gid=1000 home=/home/alj mail= Feb 13 02:05:57 coredump dovecot: imap-login: Login: alj [127.0.0.1] Feb 13 02:05:57 coredump dovecot: auth(vmail): file auth-client-connection.c: line 31 (auth_client_send): assertion failed: (conn->refcount > 1) Feb 13 02:05:57 coredump dovecot: auth(system): userdb(alj,127.0.0.1): uid=10000 gid=1000 home=/home/alj mail= Feb 13 02:05:57 coredump dovecot: imap-login: Login: alj [127.0.0.1] Feb 13 02:05:57 coredump dovecot: child 22359 (auth) killed with signal 6 Feb 13 02:05:58 coredump dovecot: auth(vmail): mysql: Connected to (null) (vmail) After a few logins authentication stops working and dovecot needs to be restarted. It seems that the mysql dovecot-auth crashes if the MySQL query does not return anything but only if it is combined with the PAM authentication. -- Allan Joergensen - http://nowhere.dk/ "I believe my plan has a fatal flaw." -- The Brain

1 1

[Dovecot] dovecot-stable: NIL from in envelope request
by Michael P. Cosby 16 Feb '05

16 Feb '05

Using the latest dovecot-stable (20050213) with pine, I get an empty "from" header in my e-mails. This doesn't happen with 1.0.59-test, nor did it happen with the first dovecot-stable (20050131). A partial connection log is below: 1.0-test59: IMAP DEBUG 15:23:32 2/13: 00000007 FETCH 1:41 (UID ENVELOPE BODY.PEEK[HEADER.FIELDS (Newsgroups Content-MD5 Content-Disposition Content-Language Content-Location resent-to resent-date resent-from resent-cc resent-subject List-Help List-Unsubscribe List-Subscribe List-Post List-Owner List-Archive Followup-To References)] INTERNALDATE RFC822.SIZE FLAGS) IMAP DEBUG 15:23:32 2/13: * 1 FETCH (ENVELOPE ("Wed, 03 Mar 2004 18:54:05 -0000" "[rowingdockmembers] Next Wed." (("Charles Barksdale" NIL "cbarksdale" "austin.rr.com")) (("Charles Barksdale" NIL "cbarksdale" "austin.rr.com")) (("Charles Barksdale" NIL "cbarksdale" "austin.rr.com")) ((NIL NIL "rowingdockmembers" "yahoogroups.com")) NIL NIL NIL "<c259kd+rqe4(a)eGroups.com>") BODY[HEADER.FIELDS (NEWSGROUPS CONTENT-MD5 CONTENT-DISPOSITION CONTENT-LANGUAGE CONTENT-LOCATION RESENT-TO RESENT-DATE RESENT-FROM RESENT-CC RESENT-SUBJECT LIST-HELP LIST-UNSUBSCRIBE LIST-SUBSCRIBE LIST-POST LIST-OWNER LIST-ARCHIVE FOLLOWUP-TO REFERENCES)] {76} IMAP DEBUG 15:23:32 2/13: UID 1 INTERNALDATE "03-Mar-2004 13:56:55 -0500" RFC822.SIZE 2722 FLAGS (\Seen)) dovecot-stable 20050213: IMAP DEBUG 15:18:30 2/13: 00000007 FETCH 1:41 (UID ENVELOPE BODY.PEEK[HEADER.FIELDS (Newsgroups Content-MD5 Content-Disposition Content-Language Content-Location resent-to resent-date resent-from resent-cc resent-subject List-Help List-Unsubscribe List-Subscribe List-Post List-Owner List-Archive Followup-To References)] INTERNALDATE RFC822.SIZE FLAGS) IMAP DEBUG 15:18:30 2/13: * 1 FETCH (ENVELOPE ("Wed, 03 Mar 2004 18:54:05 -0000" "[rowingdockmembers] Next Wed." NIL NIL NIL NIL NIL NIL NIL "<c259kd+rqe4(a)eGroups.com>") BODY[HEADER.FIELDS (NEWSGROUPS CONTENT-MD5 CONTENT-DISPOSITION CONTENT-LANGUAGE CONTENT-LOCATION RESENT-TO RESENT-DATE RESENT-FROM RESENT-CC RESENT-SUBJECT LIST-HELP LIST-UNSUBSCRIBE LIST-SUBSCRIBE LIST-POST LIST-OWNER LIST-ARCHIVE FOLLOWUP-TO REFERENCES)] {76} IMAP DEBUG 15:18:30 2/13: UID 1 INTERNALDATE "03-Mar-2004 13:56:55 -0500" RFC822.SIZE 2722 FLAGS (\Seen)) Any help would be appreciated..... Thanks - Michael

5 4

[Dovecot] Messages keep getting resent.
by poohba＠blkpoohba.dyndns.org 16 Feb '05

16 Feb '05

I have IMAP and POP running and when I log in thru pop from my blackberry which is the only way it pulls all the new emails. When I log into my computer and check email via PINE i guess something is refreshed because very soon there after if not immediately all the emails in the INBOX are sent/pulled from my blackberry again. Why is this happening?

2 1

[Dovecot] Speed up large maildirs
by Leen Besselink 16 Feb '05

16 Feb '05

Hi, I'm very fond of maildirs, they are simple, I like that. But I've never really understood the significance of maildir/new/. The only use I can see is that (for example in the case of dovecot), you'd move a message from new to cur and then update the index-file, that's it. So to make put it more direct, you'd know when and with what to update the index-file, based on where the file resides. I've never been bothered by them, until I found that that is the last hurdle for fast access to a large (and receiving a lot of mail) Maildir. I've been thinking long and hard about what to do to make them work even better. My idea at this point is the following, use maildir/new as little as possible, just use it for what it was intented and spread the time of updates. If someone would make a wrapper-program around the delivery-program (like qmail-local, vpopmaildeliver, procmail or local and virtual from postfix) and the delivery program would print to standard output the path+filename it saved a (or more) message(s) to, the wrapper would be able to send an update-message to a dovecot-daemon. That mean, updates are small, and opening a large maildir would be sped up. How does that sound ? I hope this is a helpfull suggestion. _____________________________________ New things are always on the horizon.

6 11

[Dovecot] Why am I getting more imap folders?
by poohba＠blkpoohba.dyndns.org 16 Feb '05

16 Feb '05

At one point I was just using what was under ~/mail now I have: ~/mail ~/mail/fedora ~/mail/trash ~/mail/mplayer ~/mail/yahoo ~/mail/Scott ~/mail/.imap/fedora ~/mail/.imap/fedora/.imap.index ~/mail/.imap/fedora/.imap.index.tree ~/mail/.imap/trash ~/mail/.imap/trash/.imap.index ~/mail/.imap/mplayer ~/mail/.imap/mplayer/.imap.index ~/mail/.imap/yahoo ~/mail/.imap/yahoo/.imap.index ~/mail/.imap/yahoo/.imap.index.data ~/mail/.imap/yahoo/.imap.index.tree ~/mail/.imap/Scott ~/mail/.imap/Scott/.imap.index ~/mail/.imap/INBOX ~/mail/.imap/INBOX/.imap.index ~/mail/.imap/old_subscriptions/.imap.index ~/mail/.imap/old_subscriptions/.imap.index.data ~/mail/.imap/ffmpeg ~/mail/.imap/ffmpeg/.imap.index ~/mail/.imap/apache ~/mail/.imap/apache/.imap.index ~/mail/.imap/dovecot ~/mail/.imap/dovecot/.imap.index ~/mail/ffmpeg ~/mail/apache ~/mail/dovecot These are not all the files but just the most recently touched files. Can I not just have imap view and use the ~/mail files? Is this normal? Can I have it set up to use the maildir files that are already there? It used to work that way but I guess that is with the other imap server that came with fc1.

3 3

[Dovecot] changing user mail folders
by Jason M. Wilde 15 Feb '05

15 Feb '05

I have a working dovecot server with user mail in Maildir:~/Maildir What is the proper way to change the location of user mail to /var/mail/username to take advantage of a large /var drive space? Would you recommend adding the creation of new user directories in /var/mail to my Redhat "adduser" script to get the permissions correct? Or via some other method? Also, any idea how to make Postfix deliver mail to the the new user directories? Thank you for any help and for a great product. Jason

1 0

[Dovecot] assertion failed in mail-transaction-log-view.c
by Alan Schmitt 15 Feb '05

15 Feb '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, After having moved to using Apple mail.app for offline imap reading (served by a dovecot 1.0-test59 server), I noticed the following in the logs: Feb 14 13:52:48 top dovecot: 3102(schmitta): file mail-transaction-log-view.c: line 86 (mail_transaction_log_view_set): assertion failed: (min_file_seq <= max_file_seq) Is this bad? Would upgrading to a newer version of dovecot help in this case? Thanks, Alan Schmitt -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFCEKDFNIAqM4hFUWgRAjfeAKCRpPafj/Pfhbi4wh1YFHnRxbPx3QCfSMqY S3nnORob3OXAfkDre1o7x5s= =iBoA -----END PGP SIGNATURE-----

2 1

[Dovecot] Need 2 additional folders like INBOX for JUNK and INFECTED mails
by Mirko Schulze 15 Feb '05

15 Feb '05

Hi there, i need for JUNK & INFECTED mail two folders like INBOX. The folders must be fixed in naming, permissions and so on. I've adjusted some commands in the ./src/imap folder. But it's work not really fine: Creating a folder works, but deleting too. *smile* Moving a "special-name-folder" (f.e. from Trash) to its correct place, Dovecot says, that the folder is currently there. subsribing / unsubscribing doesn't work, too. ... ... ... I think that this is a "standard" problem for much people, who don't want, that the users will delete files through the imap protocol. Are there any solutions? Thanx Mirko

1 0

[Dovecot] 0.99.14 released
by Timo Sirainen 15 Feb '05

15 Feb '05

One more change since -rc3 (the last one in list). v0.99.14 2005-02-11 Timo Sirainen <tss(a)iki.fi> - Message address fields are now parsed differently, fixing some issues with spaces. Affects only clients which use FETCH ENVELOPE command. - Message MIME parser was somewhat broken with missing MIME boundaries - mbox: Don't allow X-UID headers in mails to override the UIDs we would otherwise set. Too large values can break some clients and cause other trouble. - passwd-file userdb wasn't working - PAM crashed with 64bit systems - non-SSL inetd startup wasn't working - If UID FETCH notices and skips an expunged message, don't return a NO reply. It's not needed and only makes clients give error messages.

2 1

[Dovecot] Help, problems with permissions
by Simon Windsor 14 Feb '05

14 Feb '05

Hi I am replacing my current mail system, using Exim/Postgres/WU-IMAP to another host using Dovecot. Everything has gone well, until I have tried to access some test mails via POP. The error message I am getting is Feb 14 03:03:57 wpc1273 pop3(simonw(a)orion-w-t.co.uk): lstat (/home/dovecot/users/orion-w-t.co.uk/simonw/cur) failed: Permission denied Feb 14 03:03:57 wpc1273 pop3(simonw(a)orion-w-t.co.uk): Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-02-14 03:03:57] The file permissions are drwx------ 2 dovecot dovecot 4096 Feb 13 23:24 cur drwx------ 2 dovecot dovecot 4096 Feb 14 02:53 new drwx------ 2 dovecot dovecot 4096 Feb 14 02:53 tmp The UID/GID I am using is 1001, and the orion-w-t.co.uk/simonw directories are owned by that uid/gid. Can anyone provide advice on what I have to do to get POP, and eventually IMAP working? Many thanks Simon -- Simon Windsor Eml: simon.windsor(a)cornfield.org.uk Tel: 01454 617689 Mob: 07960 321599

3 4

Re: [Dovecot] Help, problems with permissions
by Simon Windsor 14 Feb '05

14 Feb '05

Hi Thank you for the reply. The documentation on the wiki/dovecot site clearly provides an example exim transport statements showing mail writes as dovecot/dovecot with permisions of 600. The mail system uses virtual users, and I have provided mail/group ids of 1001/1001. The current directory tree is /home - owned by root /home/dovecot - owned by root /home/dovecot/users - owned by root, 777 /home/dovecot/users/DOMAIN - owned by 1001:1001, 777 /home/dovecot/users/DOMAIN/USER - owned by 1001:1001, 777 /home/dovecot/users/DOMAIN/USER/cur - owned by dovecot:dovecot, 600 /home/dovecot/users/DOMAIN/USER/new - owned by dovecot:dovecot, 600 /home/dovecot/users/DOMAIN/USER/tmp - owned by dovecot:dovecot, 600 Can you confirm that all files should be owned by 1001/1001? What permissions should should exist on these directories/files? Thanks, once again Simon Amelia A Lewis (amyzing(a)talsever.com) wrote: > >It looks as though cur/new/tmp are owned by user dovecot, rather than >the user whose mail it is. In my (similar, prolly) setup, maildirs are >owned by their owners. Dovecot is executed as the user reading the >mail. > >Amy! >On Mon, 14 Feb 2005 02:19:09 +0000 >Simon Windsor <simon.windsor(a)cornfield.org.uk> wrote: > >> Hi >> >> I am replacing my current mail system, using Exim/Postgres/WU-IMAP to >> another host using Dovecot. >> >> Everything has gone well, until I have tried to access some test mails >> via POP. >> >> The error message I am getting is >> >> Feb 14 03:03:57 wpc1273 pop3(simonw(a)orion-w-t.co.uk): lstat >> (/home/dovecot/users/orion-w-t.co.uk/simonw/cur) failed: Permission >> denied >> Feb 14 03:03:57 wpc1273 pop3(simonw(a)orion-w-t.co.uk): Couldn't open >> INBOX: Internal error occured. Refer to server log for more >> information. [2005-02-14 03:03:57] >> >> The file permissions are >> >> >> drwx------ 2 dovecot dovecot 4096 Feb 13 23:24 cur >> drwx------ 2 dovecot dovecot 4096 Feb 14 02:53 new >> drwx------ 2 dovecot dovecot 4096 Feb 14 02:53 tmp >> >> The UID/GID I am using is 1001, and the orion-w-t.co.uk/simonw >> directories are owned by that uid/gid. >> >> Can anyone provide advice on what I have to do to get POP, and >> eventually IMAP working? >> >> Many thanks >> >> Simon >> >> >> >> -- >> Simon Windsor >> >> Eml: simon.windsor(a)cornfield.org.uk >> Tel: 01454 617689 >> Mob: 07960 321599 >> > > > -- The Last Song of Sirit Byar > -- Simon Windsor Eml: simon.windsor(a)cornfield.org.uk Tel: 01454 617689 Mob: 07960 321599

1 0

[Dovecot] Bug?
by Adam Pordzik 13 Feb '05

13 Feb '05

Hello, I noticed with different MUA (at least Thunberdird and OutlookExpress) endmost characters beeing sometimes cut-off my mails, so I assume dovecot is affected in this. Is this a known bug? Is it mayby already fixed? dovecot-0.99.10.6 on FreeBSD 5.2.1-RELEASE #1: Fri Mar 12 20:05:38 CET 2004 root@MONSTER.tektoform.lan:/usr/src/sys/i386/compile/SERVER A --

3 2

[Dovecot] Problems with dovecot using Maildir on JFS.
by Jacob Robert Wilkins 12 Feb '05

12 Feb '05

Howdy, I have dovecot installed on CentOS (rhel3 clone), and I'm using Dag's dovecot package. I have postfix setup to deliver to Maildir, in /home. The /home volume was formatted with JFS. In this setup, both Outlook and Thunderbird would not show any new mail unless they were completely shutdown and restarted. I have moved /home to an ext3 formatted and all is well. Anyone have any insight on this? Thanks, jrw

4 6

[Dovecot] can i get a list about the describtion of all sources of dovecot?
by bigbox＠mails.de 12 Feb '05

12 Feb '05

I want to control, which user, when and what modify in their mailbox done. which sourcecode must i modify? Please

2 1

[Dovecot] Trouble with Dovecot
by Paul A. Novojeeloff 11 Feb '05

11 Feb '05

Hello! I'm trying the Dovecot as IMAP server, so I have one problem: I can log in to server, but nothing appears in mailclient and following message appears in log: imap(user): Feb 08 20:36:34 Fatal: We couldn't drop root group privileges dovecot: Feb 08 20:36:34 Error: child 21356 (imap) returned error 89 What could be wrong? Thanks for your answer. WBR, Paul.

4 8

[Dovecot] PoP3 AutoDeletion
by Cheema, Ravi 10 Feb '05

10 Feb '05

Qpopper has a compile time option '--enable-auto-delete Automatically delete downloaded msgs' Is there anything similar in dovecot. I'm trying to migrate from qpopper to dovecot any help is appreciated.

4 3

Re: [Dovecot] Corrupted index file
by Tero Ripattila 10 Feb '05

10 Feb '05

Hello guys, --On 9. helmikuuta 2005 15:25 -0300 Edgardo Pezoa <epezoa(a)safp.cl> wrote: > We have almost same problem: both using Postfix, Dovecot and Procmail > in different OS and with different MUA. For me, the key is > Dovecot+Procmail. I I've seen this too on OpenBSD 3.6-current. I' running Postfix w/ Dovecot. My users uses Mulberry, Mutt, Pine, Thunderbird, Outlook, Outlook Express, The Bat! as their MUA. > The question is: someone have a real fix? I'd love to hear about this too :-) Thanks, Tero -- Tero Ripattila -- Tero Ripattila Leenankuja 2 G 67 FI-02230 Espoo, Finland Telephone: +358-45-638 0242 Fax: +358-45-689 0743 E-mail: tero(a)ripattila.com WWW: http://www.ripattila.com

2 2

[Dovecot] outstanding issues with 0.99.13
by sean finney 10 Feb '05

10 Feb '05

hi list, i'm in the process of testing dovecot before a hopeful switchover from uw-imap/qpopper to dovecot, primarily to get off of the uw-imap/mbox combo and moved to Maildir. i think we've worked out the logistics to avoid any service downtime, with only a short window of a few minutes per user for when we convert from mbox to maildir format. however, during testing a few issues have come up, some of which i've been able to work around, others which i haven't. for those that i have been able to work around, i'll include my solution so that fellow googlers may profit, and for those that i haven't i'd really appreciate your feedback. logistical problems: 1 - automagic detection and uw-imap inbox in ~/mbox. i'm not sure if this is a default characteristic or if it's specific to us, but our spool is in /var/mail/foo and inbox in ~/mbox. the automagic Maildir/mbox detection doesn't find the "mbox", and i can't tell it where it is because then it doesn't look for the Maildir. solution: i wrote a small patch to dovecot's autodetect code to help it find the location of our mailboxes. if anyone would like a copy of said patch i can send it off list. 2 - uw-imap's spool/inbox message moving. i read from the wiki that this isn't a feature currently being worked on. solution: deliver all mail to the same place. since we use procmail as our MDA, this isn't too hard of a problem. basically we redirect mail to the inbox and redeliver everything in the spool. 3 - supporting multi-homed services + ssl. for historical reasons we provide services from multiple hostnames (mail.foo, imap.foo, etc). with ssl, that means a different cert for each, otherwise some clients will break. solution: we're spawning off three seperate dovecot instances, each using a different config file. not the most graceful, but it works... application problems: 4 - dovecot imap + ms lookout 2002 + deleting messages. i'm not sure if this is an app or server side problem. basically, a user will delete a message, only to have it reappear in the mailbox a short time (few minutes) later. if i monitor the state of the mbox file, no changes are made to it until the user selects "empty trash", after which point they are expunged. looking at a protocol dump, i see the client setting the deleted flag on the message when they originally delete it. here's an excerpt: <snip> tg7i OK Idle completed. 6gzd UID STORE 30021 +FLAGS (\Deleted \Seen) * 51 FETCH (FLAGS (\Deleted \Seen \Recent) UID 30021) 6gzd OK Store completed. stpw IDLE <snip> i'm not too familiar with imap, but it looks like the server is caching the deletion request and then forgetting later forgetting about it? i have all the "client workarounds" enabled, fwiw. solution: ??? 5 - mac os x + eudora + deleting mail. a different problem alltogether. in eudora deleting a mail seems to immediately move it to the "trash" mailbox, so the above problem does not occur. what *does* happen is that if a user rapidly deletes messages one-by-one, an error message pops up about UID's not existing. i haven't gotten a full description of this problem, but here's an excerpt from what i think is the symptom: <snip> A00109 UID COPY 30002 Trash A00109 OK Copy completed. A00110 UID STORE 30002 +Flags.silent (\Deleted) A00110 OK Store completed. A00111 EXPUNGE * 31 EXPUNGE A00111 OK Expunge completed. <snip> and later: <snip> A00040 UID FETCH 30002 (UID BODYSTRUCTURE) A00040 NO Some of the requested messages no longer exist. A00041 UID FETCH 30002 RFC822.SIZE A00041 NO Some of the requested messages no longer exist. A00042 UID FETCH 30002 (BODY.PEEK[]) A00042 NO Some of the requested messages no longer exist. <snip> which i suppose is correct that it doesn't exist (since it was moved out of the inbox). however, eudora does not have this problem with uw-imap, and i'm wondering what might be causing it? solution: ??? okay, i think that's everything that i've ran into. we're still pushing ahead with this because we need to get the hell off of uw-imap/mbox, but i don't think we'll be able to stick with dovecot if these are unresolvable issues. in that case, we'll probably use dovecot with these minor nuisances while we transition, and then perhaps use courier in the long run. hopefully that won't have to be the case though :) if anyone has any experience specifically with "5" and "5", i'd really, really like to hear about it. in the meantime, i'll continue to test other things, and also see if the problem also persists when mail is stored in Maildir format. anyway, thanks for your time! sean

4 4

[Dovecot] oh, and status of 1.0?
by sean finney 09 Feb '05

09 Feb '05

sorry for splitting this off into a second message :) is there a roadmap/schedule for the release of 1.0? ever curious, sean

2 1

[Dovecot] Dovecot Maildir to read /var/spool/mail
by Ben Halicki 09 Feb '05

09 Feb '05

Hi all, Does anyone know how to configure dovecot to read /var/spool/mail as the inbox using maildir format? Thanks in advance, Ben Halicki

2 2

Re: [Dovecot] Corrupted index file
by Frank Hart 09 Feb '05

09 Feb '05

On Wed, Feb 09, 2005 at 02:55:51PM -0500, Michael Baird wrote: > Frank, exactly the same thing happened to me. Last week I tried to > migrate over to dovecot, from courier-imap for all the reasons you > mentioned, I ran into the Corrupted index file issue and had to cut back > to courier-imap. I am using dovecot for maildir as it appears you are, > however I specified an outside directory for index files (/var/indexes). > I have a few thousand people using my webmail/imap system so this issue > quickly became a big issue after the cutover. > > Regards > Michale Baird It was probably my own fault. Timo Sirainen noticed Edgardo Pezoa was using MH style filenames. And I did the same thing. My main inbox configured in procmail was $HOME/Maildir/new and it should be $HOME/Maildir/ (notice the slash at the end). Now, new mails have filenames such as 1107960126.14681_2.hive:2, instead of msg.uC:2,S. I never had this problem with courier so I didn't thought it could be a configuration error. Thanks everyone for the help. Timo's mail: http://dovecot.org/list/dovecot/2005-February/006215.html -- make install, not war

1 0

[Dovecot] Corrupted index file w/Procmail in FC2
by Edgardo Pezoa 09 Feb '05

09 Feb '05

Hello: We have a Fedora Core 2 (FC2) server with Dovecot and Procmail. Versions are: dovecot-0.99.13-4.FC2 procmail-3.22-13 We use "maildir" below home directory like: /users/operaciones/epezoa/maildir, where "epezoa" is my account. If I receive an e-mail, is stored at "new" folder. When I try to get e-mail from server, message is transfered from "new" folder to "cur" folder, but I can't see my e-mail and Dovecot generates a "Corrupted index file" in log file: Feb 8 14:02:34 dlp1 pop3(epezoa): Corrupted index file /users/operaciones/epezoa/maildir/.INBOX/.imap.index: index.next_uid (14836) > uid_rec.uid (14825) But, If I receive another e-mail (at "new" folder) and I try to get messages, I get both. My clients are Mozilla (with "pop3") and Squirrel (from another server with "imaps"). Both have same behavior, so I think client is not involved in this problem. MTA is Postfix, but all accounts works well, except who use Procmail. I read about locking in Procmail and Dovecot and I think locking may produce this problem, but I can't find what's wrong. I upgraded dovecot from dovecot-0.99.10-5 to try fix this. Thanks in advance, -- Edgardo Pezoa

2 4

[Dovecot] 0.99.14-rc2
by Timo Sirainen 09 Feb '05

09 Feb '05

http://dovecot.org/rc/ I should have released 0.99.14 already, but I've been way too busy lately. Among other things I started working half-time at Movial (www.movial.fi) I had forgotten 8 hour work days at office could take so much time :) Anyway.. There has been a few changes since RC1 so I'll still make RC2 before the final. Changes since RC1: - passwd-file userdb wasn't working - PAM crashed with 64bit systems - non-SSL inetd startup wasn't working - upgraded setuid/setgid initialization code from 1.0-tests

1 0

[Dovecot] New user Q: dovecot-0.99-13 / UnixWare 7.1.0
by Steven Palm 09 Feb '05

09 Feb '05

Trying to get dovecot up and running. I managed to get everything compiled and linked correctly, but there seems to be some problem with either the auth process or communication between the main process and the auth process. When I try to login, I get: * OK dovecot ready. 1 login n9yty testing * OK Waiting for authentication process to respond.. And I keep getting the same message over and over until eventually it dies if I let it sit: * BYE Disconnected for inactivity. In the log, all I see is: dovecot: Feb 05 02:24:46 Info: Dovecot starting up imap-login: Feb 05 02:32:46 Info: Disconnected: Inactivity [127.0.0.1] I have this in my config, but yet that is all the logging I see: auth_userdb = passwd auth_passdb = shadow auth_verbose = yes auth_debug = yes I then tried to do ./configure with --enable-debug, but if I do that I get this in the log when trying to run dovecot: dovecot: Feb 05 02:08:01 Info: Dovecot starting up dovecot: Feb 05 02:08:03 Error: Auth process died too early - shutting down dovecot: Feb 05 02:08:03 Error: child 8441 (login) killed with signal 6 dovecot: Feb 05 02:08:03 Error: child 8440 (auth) killed with signal 6 (sometimes the (login) line is not send, but always (auth)) Any thoughts on where to next start tracking this down? I tried to use test62, but get this (haven't dug much further into this one since I'd like a stable release for this application): main.c: In function `listen_protocols': main.c:284: error: structure has no member named `_listen' main.c: At top level:

2 2

[Dovecot] possible bug in 1.0-test62
by Dominik 'Rathann' Mierzejewski 09 Feb '05

09 Feb '05

When connecting with mutt via IMAPS, I get "connection to server closed" and this appears in logs: dovecot: Feb 04 12:48:30 Error: IMAP(rathann): file mail-index-sync-ext.c: line 118: assertion failed: (size <= synch_size) The problem goes away after deleting the index from ~/Mail/.imap/INBOX. We're running 1.0-test62 on Solaris 9. -- Dominik 'Rathann' Mierzejewski <rathann*at*icm.edu.pl> Interdisciplinary Centre for Mathematical and Computational Modelling Warsaw University | http://www.icm.edu.pl | tel. +48 (22) 5540810

2 1

[Dovecot] File isn't in mbox format - Couldn't open INBOX
by Girish Patangay 09 Feb '05

09 Feb '05

I cannot reproduce this error everytime, but it seems to happen when Outlook tries to delete the first message (the first message in the file, message on top) in the /var/mail/user file. I tried looking through the mailing list but came up blank. Is this a known problem? I can fix this problem by editing the file manually and fixing the file. If I delete the first 2 lines (in the example below) and make sure the Inbox file starts at "From ..." it works fine again. Here is the log: ---------------------------------------------- Feb 2 09:23:45 angel pop3-login: Login: sathyan [127.0.0.1] Feb 2 09:23:45 angel pop3(sathyan): File isn't in mbox format: /var/mail/sathyan Feb 2 09:23:45 angel pop3(sathyan): File isn't in mbox format: /var/mail/sathyan Feb 2 09:23:45 angel pop3(sathyan): Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-02-02 09:23:45] ---------------------------------------------- The inbox file for this user looks like this: ---------------------------------------------- [root@angel mail]# head sathyan zenxoI6Jdi_xPyRoBhrhf-- >From caecelius(a)payaway.every1.net Wed Feb 2 07:03:36 2005 Return-Path: <caecelius(a)payaway.every1.net> ---------------------------------------------- -- ------------------------- Girish Patangay <girish(a)intoto.com> Intoto Inc <www.intoto.com> Phone: 408.844.0480x304 Fax: 408.844.0488 PG ID: 0x74D3A118

2 1

[Dovecot] assertion failed in imap-bodystructure.c
by Martin Preen 09 Feb '05

09 Feb '05

Hello, I'm currently testing dovecot/imap (Version 0.99.13). I found this in the log: imap(xxxxx): [ID 265587 mail.crit] file imap-bodystructure.c: line 278 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) dovecot: [ID 684838 mail.error] child 7376 (imap) killed with signal 6 The user tried to setup a new folder (with Thunderbird) and that seemed to cause this error. What does that mean ? Should I worry about ? Martin ----------------------------------------------------------------- Martin Preen, Universitaet Freiburg, Institut fuer Informatik Georges-Koehler-Allee, Geb.52, Zi.00-006, 79110 Freiburg, Germany phone: ++49 761 203-8250 preen(a)informatik.uni-freiburg.de fax: ++49 761 203-8242 www.informatik.uni-freiburg.de

2 1

[Dovecot] TROUBLES WITH dovecot configuration
by Alexey S. Kuznetsov 09 Feb '05

09 Feb '05

Hello! I'm new in this list and new to dovecot, so I have some troubles with its configuration. I have an Linux OS installed and Postfix what supports virtual domains and places mail to: /var/spool/mail/vhosts/DOMAIN_NAME/ I've installed dovecot, configured it to use only pop3 proto. Configuration like this (most important lines from config) # cat /usr/local/dovecot/etc/dovecot.conf login_user = dovecot default_mail_env = mbox:/var/spool/mail/vhosts/%d/%n auth = default auth_mechanisms = plain auth_userdb = passwd-file /usr/local/dovecot/ps/pop.users auth_passdb = passwd-file /usr/local/dovecot/ps/pop.users auth_user = root cat /usr/local/dovecot/ps/pop.users testemail@mydomain.org:1a1dc91c907325c69271ddf0c944bc72[34]:1000:7266::/var/spool/mail/vhosts/mydomain.org/::: My system uid is 508, when I set it in pop.users file it works nice: accepts password, lists mail, everything. But when I want to create uniq. id for my domain: useradd -d /dev/null -s /bin/date -u 1000 mydomainorg telnet localhost 110 Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'. +OK dovecot ready. user testemail(a)mydomain.org +OK pass pass +OK Logged in. -ERR No INBOX for user. Connection closed by foreign host. And in logs: # cat /var/log/dovecot.log Jan 28 22:11:02 Error: mkdir_parents(/var/spool/mail/vhosts/mydomain.org//mail/.imap/INBOX) failed: Permission denied pop3(testemail(a)mydomain.org): Jan 28 22:11:02 Error: Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-01-28 22:11:02] If I set uid 508 everything will be cool! I don't understand why it works like this? I logged in to my account and via sudo su - I became root user. Root has uid 0, and why it works with uid 508 I can't even imagine :( Please help me with this problem. Thanx! -- Sincerely, Alexey S. Kuznetsov AK2351-RIPE

2 1

[Dovecot] can't login in pop3 accounts
by Sebastian Alduncin Pisanty 09 Feb '05

09 Feb '05

hi there... i HAVE practically searched in ALL messages from 2004 year, and haven't any luck with this problem, so I'm inserting here "dovecot.conf" content: ## Dovecot 1.0 configuration file # 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=/usr/share/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 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. You can specify ports with # "host:port". imap_listen = * pop3_listen = * # IP or host address where to listen in for SSL connections. Defaults # to above non-SSL equilevants if not specified. #imaps_listen = #pop3s_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 = /usr/share/ssl/certs/dovecot.pem #ssl_key_file = /usr/share/ssl/private/dovecot.pem # 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 = 0 # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability) #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 = # 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. Note the extra space at the end of line. 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. 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. #login_chroot = yes ## ## IMAP login process ## login = imap # Executable location. #login_executable = /usr/libexec/dovecot/imap-login # 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. #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 = 16 # 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 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 ## ## POP3 login process ## # Settings default to same as above, so you don't have to set anything # unless you want to override them. login = pop3 # Exception to above rule being the executable location. #login_executable = /usr/libexec/dovecot/pop3-login ## ## 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 # ':' 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 by # giving /./ in user's home directory (eg. /home/./user chroots into /home). #mail_chroot = # 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: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if user there's no domain # %h - home directory # # You can also limit a width of string by giving the number of max. characters # after the '%' character. For example %1u gives the first character of # username. Some examples: # # maildir:/var/mail/%1u/%u/Maildir # mbox:~/mail/:INBOX=/var/mail/%u # mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # #default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # Space-separated list of fields to cache for all mails. Currently these # fields are allowed followed by a list of commands they speed up: # # Envelope - FETCH ENVELOPE and SEARCH FROM, TO, CC, BCC, SUBJECT, # SENTBEFORE, SENTON, SENTSINCE, HEADER MESSAGE-ID, # HEADER IN-REPLY-TO # Body - FETCH BODY # Bodystructure - FETCH BODY, BODYSTRUCTURE # MessagePart - FETCH BODY[1.2.3] (ie. body parts), RFC822.SIZE, # SEARCH SMALLER, LARGER, also speeds up BODY/BODYSTRUCTURE # generation. This is always set with mbox mailboxes, and # also default with Maildir. # # Different IMAP clients work in different ways, that's why Dovecot by default # only caches MessagePart which speeds up most operations. Whenever client # does something where caching could be used, the field is automatically marked # to be cached later. For example after FETCH BODY the BODY will be cached # for all new messages. Normally you should leave this alone, unless you know # what most of your IMAP clients are. Caching more fields than needed makes # the index files larger and generate useless I/O. # # With maildir there's one extra optimization - if nothing is cached, indexing # the maildir becomes much faster since it's not opening any of the mail files. # This could be useful if your IMAP clients access only new mails. #mail_cache_fields = MessagePart # Space-separated list of fields that Dovecot should never set to be cached. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Workarounds for various client bugs: # oe6-fetch-no-newmail: # Never send EXISTS/RECENT when replying to FETCH command. Outlook Express # seems to think they are FETCH replies and gives user "Message no longer # in server" error. 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. #client_workarounds = outlook-idle # Dovecot can notify client of new mail in selected mailbox soon after it's # received. This setting specifies the minimum interval in seconds between # new mail notifications to client - internally they may be checked more or # less often. Setting this to 0 disables the checking. # NOTE: Evolution client breaks with this option when it's trying to APPEND. #mailbox_check_interval = 30 # 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 custom flag name. It's only forced when trying # to create new flags. #mail_max_flag_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. #mail_read_mmaped = 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 # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing message are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's three 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. # # You can use both fcntl and flock too; if you do the order they're declared # with is important to avoid deadlocks if other MTAs/MUAs are using both fcntl # and flock. Some operating systems don't allow using both of them # simultaneously, eg. BSDs. If dotlock is used, it's always created first. mbox_locks = fcntl # Should we create dotlock file even when we want only a read-lock? Setting # this to yes hurts the performance when the mailbox is accessed simultaneously # by multiple processes, but it's needed for reliable reading if no other # locking methods are available. #mbox_read_dotlock = no # 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 # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. Note that setting # this to yes means that log file is opened as the logged in user, which # might not work. It could also 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 ## ## IMAP process ## # Executable location #imap_executable = /usr/libexec/dovecot/imap # 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. #imap_process_size = 256 # Support for dynamically loadable modules. #imap_use_modules = no #imap_modules = /usr/lib/dovecot/imap ## ## POP3 process ## # Executable location #pop3_executable = /usr/libexec/dovecot/pop3 # 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. #pop3_process_size = 256 # Support for dynamically loadable modules. #pop3_use_modules =yes #pop3_modules = /usr/lib/dovecot/pop3 ## ## Authentication processes ## # You can have multiple processes; each time "auth = xx" is seen, a new # process definition is started. The point of multiple processes is to be # able to set stricter permissions to others. For example, plain/PAM # authentication requires roots, but if you also use digest-md5 authentication # for some users, you can authenticate them without any privileges in a # separate auth process. Just remember that only one auth process is asked # for the password, so you can't have different passwords with different # processes (unless they have different auth methods, and you're ok with # having different password for each method). # Authentication process name. auth = default # Space separated list of wanted authentication mechanisms: # plain digest-md5 anonymous # EBRAIN changed #auth_mechanisms = plain digest-md5 auth_mechanisms = plain # 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 to use if none was specified. #auth_default_realm = # Where user database is kept: # passwd: /etc/passwd or similiar, using getpwnam() # passwd-file <path>: passwd-like file with specified location # static uid=<uid> gid=<gid> home=<dir template>: static settings # vpopmail: vpopmail library # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # pgsql <config path>: a PostgreSQL database, see doc/dovecot-pgsql.conf auth_userdb = passwd # auth_userdb = pgsql /usr/local/etc/dovecot-pgsql.conf # Where password database is kept: # passwd: /etc/passwd or similiar, using getpwnam() # shadow: /etc/shadow or similiar, using getspnam() # pam [<service> | *]: PAM authentication # passwd-file <path>: passwd-like file with specified location # vpopmail: vpopmail authentication # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # pgsql <config path>: a PostgreSQL database, see doc/dovecot-pgsql.conf # auth_passdb = pgsql /usr/local/etc/dovecot-pgsql.conf auth_passdb = pam #auth_executable = /usr/libexec/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # 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. auth_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. #auth_chroot = # Number of authentication processes to create #auth_count = 1 # 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 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 = no # digest-md5 authentication process. It requires special MD5 passwords which # /etc/shadow and PAM doesn't support, so we never need roots to handle it. # Note that the passwd-file is opened before chrooting and dropping root # privileges, so it may be 0600-root owned file. #auth = digest_md5 #auth_methods = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = # if you plan to use only passwd-file, you don't need the two auth processes, # simply set "auth_methods = plain digest-md5" =================================================== OK sorry about pasting all .conf, but didn't know what to do... so here is the deal, I have configured IMAP to use in SquirrelMail, and it's working flawless, and before that i went putting up POP3 access, and in that time went flawless, but dunno what is going on that I can't login from neither Outlook 2003 or Outlook Express 6, when i turn ON Verbose, in "maillog" appears this message (i don't think trying to login from other prog would help, but right now starting to download Thunderbird): Jan 29 14:37:33 cddserver dovecot: Dovecot starting up Jan 29 15:15:41 cddserver dovecot: Killed with signal 15 any clue what could it BE??? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

[Dovecot] Corrupted index file
by Frank Hart 09 Feb '05

09 Feb '05

I've recently switched from Courier-imap to dovecot and I'm impressed with it's speed and reliability. However, my index file gets regularly corrupted: Feb 8 21:23:16 hive imap(hart): Corrupted index file /home/hart/Maildir/.INBOX/.imap.index: index.next_uid (129) > uid_rec.uid (128) dovecot version: 0.99.13-3 Debian sid) I use dovecot in combination with mutt, procmail and postfix. If I rename the last received mail I can use my inbox folder again (until the next time the index gets corrupted). Debian bug# 294284 -- make install, not war

2 2