- dovecot - dovecot.org

[Dovecot] Maildir and folders not under INBOX
by Oliver Schulze L. 24 Sep '05

24 Sep '05

Hi, I'm planning to migrate from dovecot/mbox to dovecot/maildir both using imap. I have read that when using the Maildir storage format, all folders are stored under the INBOX. Is this true in dovecot too? I want to have a configuration like the current: - new mail is delivered in /var/mail/USER - user folders are in /home/USER/mail I want to ask if this is posible in dovecot? Maybe using a config like this: default_mail_env = maildir:/home/%u/Maildir:INBOX=/var/mail/%u/Maildir Thanks Oliver -- Oliver Schulze L. <oliver(a)samera.com.py>

2 2

[Dovecot] Moving messages takes a longgggggg..... time. (Timeouts?) dovecot.conf help?
by Rob Frohne 23 Sep '05

23 Sep '05

Hi, I'm trying to get dovecot set up better. I am using 1.0alpha3. It takes a long long time to move messages for some reason. It seems it may be a timeout thing, because neither the client or server is using any cpu time or disk i/o or network to speak of. (To move maybe 400 messages, it seems to take maybe half an hour, maybe longer.) With alpha 2 I was getting messages from Thunderbird saying that the server was unable to move messages, would I like to continue. I haven't seen any of these lately, but when I updated to alpha3 I also made some dovecot.conf changes. I'm running this on OS X with a 450 MHz cube with 1.2 Gig of ram and a 7200 RPM hard drive. I have a lot of rules that move messages to various mailboxes and I get a lot of mail, so this is important to me. I have a very large Maildir set of mailboxes (about 40 of them with up to 70,000 messages in each mailbox). I have finally got it so that it will load the mailbox headers pretty quickly in Thunderbird. It takes about 15 to 30 seconds to load a message, but that is acceptable to me. Here is my dovecot.conf. Can anyone give me some tips? ## 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 # 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 = yes # 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/ssl/certs/dovecot.pem #ssl_key_file = /etc/ssl/private/dovecot.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 = # 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 # 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 = 4096 # 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 max_mail_processes = 4096 # 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 verbose_proctitle = yes # Show protocol level SSL errors. #verbose_ssl = no verbose_ssl = yes # 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_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 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 mail_debug=yes # 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:~/Library/Mail/Mailboxes:INBOX=/var/mail/%u default_mail_env = maildir:%h/Maildir # 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 mailbox_idle_check_interval = 15 # 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 mail_max_keyword_length = 250 # 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 maildir_copy_with_hardlinks = yes # 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 = 0077 # 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 mail_process_size = 4096 # 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 imap_max_line_length = 262144 # 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. # 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. #imap_client_workarounds = outlook-idle imap_client_workarounds = delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep } ## ## 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 = } ## ## 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. passdb pam { # [-session] [<service name>] # # -session makes Dovecot open and immediately close PAM session. Some # PAM plugins need this to work. # # If service name is "*", it means the authenticating service name # is used, eg. pop3 or imap. args = imap #args = dovecot } # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. #passdb passwd { #} # /etc/shadow or similiar, using getspnam(). Deprecated by PAM nowadays. #passdb shadow { #} # passwd-like file with specified location #passdb passwd-file { # Path for passwd-file #args = #} # checkpassword executable authentication #passdb checkpassword { # Path for checkpassword binary #args = #} # SQL database #passdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for example #args = #} # LDAP database #passdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example #args = #} # vpopmail authentication #passdb vpopmail { #} # # 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 # # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. userdb passwd { } # passwd-like file with specified location #userdb passwd-file { # Path for passwd-file #args = #} # static settings generated from template #userdb static { # Template for settings. Can return anything a userdb could normally # return, eg.: uid, gid, home, mail, nice # # A few examples: # # args = uid=500 gid=500 home=/var/mail/%u # args = uid=500 gid=500 home=/home/%u mail=mbox:%h/mail nice=10 # #args = #} # SQL database #userdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for example #args = #} # LDAP database #userdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example #args = #} # vpopmail #userdb vpopmail { #} # 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 # 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 } # 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 default_with_listener { # mechanisms = plain # passdb passwd { # } # userdb pam { # } # socket listen { # master { # path = /var/run/dovecot/auth-master # #mode = 0600 # # Default user/group is the one who started dovecot-auth (root) # #user = # #group = # } # client { # path = /var/run/dovecot-auth-client # mode = 0660 # } # } #} # connect sockets are assumed to be already running, Dovecot's master # process only tries to connect to them. They don't need any other settings # than path for the master socket, as the configuration is done elsewhere. # Note that the client sockets must exist in login_dir. #auth external { # socket connect { # master { # path = /var/run/dovecot/auth-master # } # } #} Thanks! Rob

1 0

[Dovecot] signing dovecot certs with own Cert. Auth.
by blaq b0x 23 Sep '05

23 Sep '05

Hi, I'm trying to get apache, sendmail , and dovecot to use SSL certs signed by my own CA. I've got the apache certs working fine. However, dovecot ( I haven't even tried sendmail yet) doesn't seem to accept any of the certificates that I create for it. There is a script that comes with dovecot that creates self-signed certificates for you but, I need certificates signed by my own CA. I found this tutorial http://homepage.mac.com/pauljlucas/personal/macmini/certs.html it shows you how to create a csr for dovecot that you can send to a CA. I signed it using CA.pl -sign. however, the certificate isn't accepted by dovecot. Unfortunately, dovecot doesn't log anything to maillog at failed startup. Just looking at the certificate contents I noticed that the self-signed certificates don't have all kinds of publisher information at the beginning of them like the apache certs. So I think what I'm missing is the difference between all the different cert types. I know that there are pem and cert ssl cert types, at least different extensions. Can anyone tell my what the difference is? are the certs suitable for apache and others for mail applications? is there a converter? Could it be the way that I'm signing the certificates? Any help would be appreciated. Thanks, Reply With Quote __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

6 8

[Dovecot] login_process_per_user referred to but not present in dovecot.conf?
by Rob Frohne 23 Sep '05

23 Sep '05

Hi, I find login_process_per_user referred to in the comments in dovecot.conf, but never set. Is this a typo and should it be login_process_per_connection or what? Thanks, Rob

2 1

[Dovecot] Lost transaction log file in alpha2
by James Berry 23 Sep '05

23 Sep '05

I had run alpha1 pretty uneventfully for several weeks. I upgraded to alpha2 a couple of days ago and have since suffered two incidents of "Lost transaction log", resulting in the client being unable to access the mailbox until I "rm dovecot.index.log*" Sep 14 10:48:35 caddy dovecot: imap(jberry): Lost transaction log file /Users/jberry/Maildir/dovecot.index.log seq 1 I should point out that this is a server with a single imap user (myself) and that I know only one imap client was trying to access the server at that point in time (though the client sw Mail.app may have had multiple connections to the server). Any suggestions/ideas/thoughts on whether something might have changed in alpha2 to start causing this? James.

2 4

[Dovecot] auth-master socket access
by Lieven Van Acker 23 Sep '05

23 Sep '05

Hey, I'm doing a setup of dovecot (cvs) + postfix + dovecot lda (cvs). Is there any solution to the /var/run/dovecot/auth-master access restrictions, prohibiting the user running dovecot-deliver from communicating with the master (aside from the dirty and unsafe hack to reset the permissions of the /var/run/dovecot dir after starting dovecot)? Thanks, Lieven

3 2

[Dovecot] Can't donwload mails with some attacchments
by Lethux 23 Sep '05

23 Sep '05

Hi. Does anyone find the same problem with attachments bigger than few Ks? The client (thunderbird) waits for the file to be downloaded. It can be waiting for several minuts and tryies before having it from dovecot. Can it be something against the lock of the file, the processes or something else? Any workaround or bugfix in the stable/alpha rel? thanks. L.

2 1

[Dovecot] Shared access to mail accounts.
by Rory Campbell-Lange 23 Sep '05

23 Sep '05

We are intending to have some project mail accounts which many people (up to 10) will share. Will this work? Our configuration uses imap only, with maildir format mail storage. Thanks Rory -- Rory Campbell-Lange <rory(a)campbell-lange.net> <www.campbell-lange.net>

3 4

[Dovecot] Is Alpha2 slower than Alpha1?
by Marc Perkel 23 Sep '05

23 Sep '05

I changed servers at the same time as changing from Alpha1 to Alpha2 but I'm on a faster server so it should be faster. But it seems slower especially deleting server side messages. Using mbox . Anyone else seeing tis?

2 1

[Dovecot] Basic namespaces question
by David King 23 Sep '05

23 Sep '05

I can't find a generalised "What the heck are namespaces all about?" anywhere, can anyone point me to a decent one? More directly, my question is this: if I set up two non-hidden private namespaces (one for mbox and one for maildir), will a well-written IMAP client automagically list folders from both as if they were part of (or below) the same hierarchy, or do I have to set up two accounts, one with a prefix of (say) #mbox and one of #maildir? One step further, I'd like to eventually get mail from /var/mail/%u in mbox format, and in "maildir:%h/.maildir" or "mbox:%h/.mail", whichever exists (I'm migrating from imap-uw, and would like the benefits of maildir without forcing users to change their mailstores in case they use pop3 or tools like mail(1)). I'm willing to do some coding for it, but I imagine that it would be non-trivial if namespaces aren't automatically integrated

2 1

[Dovecot] courier imap --> dovecot imap
by Paul 'Google' Smit 23 Sep '05

23 Sep '05

Dear Readers of tha list... Please help me out! I currenty have Dovecot Imap installed but I still have some old Courier Imap files from an old server which I want to use. Can I, in any way, import of convert them so I can use it? Regards, Millman ------------------------------- Linux: Fedora Core 4 Sendmail: 8.13.4-2 Dovecot: 0.99.14-4 Squirrelmail: 1.4.6-0 -------------------------------

3 3

[Dovecot] trying to see different files
by David Willoughby 23 Sep '05

23 Sep '05

i am wanting to sort my email into different files per the different email lists i use. i've posted this before but nobody responded. is it possible to use dovecot and sort my mail into /home/dlw/Mail/file1, file2 etc.... ? -- David Willoughby email: dlw(a)d1w.org icq: 1852393

7 8

[Dovecot] bug? Maildir ... sync: UID inserted in the middle of mailbox
by Peter Gervai 23 Sep '05

23 Sep '05

Version: 1.00alpha2 Error: imap(grin): Maildir /home/grin/Maildir sync: UID < next_uid (94 < 95, file = 1127311363.H977932P25148.gollum:2,) imap(grin): Maildir /home/grin/Maildir sync: UID inserted in the middle of mailbox (95 > 94, file = 1127311363.H977932P25148.gollum:2,) This error reappears frequently. Doesn't go away by restarting dovecot, but does go away when I delete all index and cache and whatnot (and restart dovecot). Appears in 10 minutes again... Could be sylpheed-claws-whatever-alpha imap problem, but whatever the client does dovecot shouldn't be fall apart I believe. Peter

3 2

[Dovecot] Another address-spec problem
by Chris Wakelin 23 Sep '05

23 Sep '05

I've had complaints from users about "MISSING_DOMAIN" in header fields and I've tracked it down to having "." in an unquoted display name. By my reading of RFC2822 (especially section 4.1) A N Other <a.n.other(a)somewhere.org> "A. N. Other" <a.n.other(a)somewhere.org> are legal, but A. N. Other <a.n.other(a)somewhere.org> is "obsolete", but should be supported by the server (no clients should do it). I think the relevant syntax is phrase = 1*word / obs-phrase word = atom / quoted-string obs-phrase = word *(word / "." / CFWS) and rfc822_parse_phrase() should be modified to cope with "obs-phrase". I'll have a go, but if Timo or anybody knows how to do it properly, that would be better! Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 2

[Dovecot] Debian packages of alpha2?
by Ben Beuchler 23 Sep '05

23 Sep '05

Is anyone maintaining Debian packages of alpha2? The official packages aren't even up to -stable yet. -Ben

2 1

[Dovecot] virtual passwords
by Michael Collins 22 Sep '05

22 Sep '05

I just set up postfix with some virtual domains and users. Dovecot made some dbs in /etc/dovecot. a passdb and userdb. the passdb file has passwords in there and I want to at least know what it is. I have tried to do 'echo -n mypassword | openssl md5 -hex' and insert that into them but it seems to not work. Probably something I am doing wrong. I looked at the archive and could not figure out how to search it. Anyway how do i change a password? Thanks. this is passdb: andreux@bla.com:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 andrew@bla.com:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 sikki@bla.com:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 amanda@bla.com:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 info@bla.com:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 help@bla.com:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 andrew@blu.biz:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 andreux@blu.biz:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 eric@blu.biz:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 jjenkins@blu.biz:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 -- -- Michael H. Collins It's us against them. Ride like you stole it. If you love some code, set it free. Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html

1 0

[Dovecot] problem with postgreSQL connect=
by octane indice 22 Sep '05

22 Sep '05

Hello I'm using dovecot with virtual accounts stored in a postgreSQL db. I use in the dovecot.conf: auth_userdb = pgsql /usr/local/etc/dovecot-pgsql-user.conf (and same for pass). In the file dovecot-pgsql-user.conf, I use: connect = host=127.0.0.1 dbname=vmail user=lecteur password=lire user_query = SELECT '/var/spool/vhosts/'||nom_domaine||'/'||nom_boite AS mail,5000 AS uid, 5000 AS gid FROM boites WHERE email = '%u' It doesn't work. If I write: connect = dbname=vmail user=lecteur user_query = SELECT '/var/spool/vhosts/'||nom_domaine||'/'||nom_boite AS mail,5000 AS uid, 5000 AS gid FROM boites WHERE email = '%u' It works. Of course the query with psql works: psql -U lecteur -h 127.0.0.1 vmail -c "SELECT '/var/spool/vhosts/'||nom_domaine||'/'||nom_boite AS mail,5000 AS uid, 5000 AS gid FROM boites WHERE email = '%u' " with the password 'lire' My question: do I make something wrong? I want to use the network, because in future, dovecot will not be on the same host than postgreSQL. Thanks --------------------------------------------- Etes vous un consom'Acteur ? Toutes les saveurs équitables sont sur http://www.epicerie-equitable.com

1 0

[Dovecot] Lost transaction log file /Users/frohro/Maildir/dovecot.index.log.2 seq 1
by Rob Frohne 22 Sep '05

22 Sep '05

Hi, I got a bunch of the following errors: Lost transaction log file /Users/frohro/Maildir/dovecot.index.log.2 seq 1 when I was trying to apply some rules to move messages from one mailbox to another. Things hadn't been working well and I had recently upgraded to alpha 2, so I moved all dovecot* files in my Maildir/. Things then seem to work better. Rob -- Rob Frohne, Ph.D., P.E. E.F. Cross School of Engineering Walla Walla College http://www.wwc.edu/~frohro/

1 0

[Dovecot] Weird series of errors with dovecot-stable
by Ben Beuchler 21 Sep '05

21 Sep '05

I'm using the dovecot-stable from 7/30, authenticating against an OpenLDAP server. From time to time, dovecot stops responding to new queries. It seems to be a self-correcting problem, lasting about 20 minutes. Here's how it starts: Aug 18 19:38:23 cliff dovecot: imap-login: Disconnected: Inactivity [150.253.42.12] Aug 18 19:38:36 cliff dovecot: pop3-login: Disconnected: Inactivity [68.46.174.217] Aug 18 19:39:35 cliff dovecot: imap-login: Disconnected: Inactivity [150.253.42.12] Normally I see almost no "Disconnected: Inactivity" messages, but when this problem shows up I get an almost non-stop barrage of them. In fact, over the 20 minutes or so, there's about 150 of those entries, so I filtered them out of the log snippets. I also filtered out any "normal" activity during the time period. Here's what's left: Aug 18 19:40:29 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:40:29 cliff dovecot: child 22347 (auth) killed with signal 6 Aug 18 19:42:04 cliff dovecot: auth(ldap): ldap(vmail,150.253.80.31): unknown user Aug 18 19:42:41 cliff dovecot: imap-login: SSL_read() syscall failed: EOF [24.26.184.219] Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:31 cliff dovecot: auth(ldap): Login process has too old (121s) requests, killing it. Aug 18 19:43:43 cliff dovecot: auth(ldap): Login process has too old (121s) requests, killing it. Aug 18 19:43:43 cliff dovecot: auth(ldap): Login process has too old (122s) requests, killing it. Aug 18 19:43:49 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:43:49 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:43:49 cliff dovecot: child 22557 (auth) killed with signal 6 Aug 18 19:43:49 cliff dovecot: child 22562 (login) returned error 89 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:32 cliff dovecot: child 22522 (login) returned error 89 Aug 18 19:45:32 cliff dovecot: child 22561 (login) returned error 89 Aug 18 19:45:32 cliff dovecot: child 22563 (login) returned error 89 Aug 18 19:45:32 cliff dovecot: child 22564 (login) returned error 89 Aug 18 19:45:32 cliff dovecot: child 22566 (login) returned error 89 Aug 18 19:47:54 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:47:54 cliff dovecot: child 22599 (auth) killed with signal 6 Aug 18 19:48:18 cliff dovecot: imap-login: SSL_read() syscall failed: EOF [69.81.39.120] Aug 18 19:48:18 cliff dovecot: imap-login: SSL_read() syscall failed: EOF [69.81.39.120] Aug 18 19:51:32 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:51:32 cliff dovecot: child 22628 (auth) killed with signal 6 Aug 18 19:54:14 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:54:14 cliff dovecot: child 22655 (login) returned error 89 Aug 18 19:54:14 cliff dovecot: child 22683 (login) returned error 89 Aug 18 19:54:14 cliff dovecot: child 22686 (auth) killed with signal 6 Aug 18 19:54:14 cliff dovecot: child 22689 (login) returned error 89 Aug 18 19:54:14 cliff dovecot: child 22690 (login) returned error 89 Aug 18 19:54:14 cliff dovecot: child 22699 (login) returned error 89 Then, magickally, it begins working again. Any thoughts? -Ben

2 1

[Dovecot] ldap: No password in reply
by Rudy Gevaert 21 Sep '05

21 Sep '05

Greetings, I'm trying to set up dovecot with ldap (and postfix) by following the page on the wiki. I configured everything, but something is wrong: dovecot: Sep 21 12:03:59 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=157.193.40.36 rip=157.193.44.68 dovecot: Sep 21 12:03:59 Info: auth(default): client out: CONT 1 dovecot: Sep 21 12:03:59 Info: auth(default): client in: CONT 1 b2xlX3dvYmJsZQBvbGVfd29iYmxlAHdvYmJsZQ== dovecot: Sep 21 12:03:59 Info: auth(default): ldap(ole_wobble,157.193.44.68): base=ou=accounts,dc=zalm,dc=UGent,dc=be scope=subtree filter=(&(objectClass=posixAccount)(uid=ole_wobble)) fields=uid,userPassword dovecot: Sep 21 12:03:59 Info: auth(default): ldap(ole_wobble,157.193.44.68): uid(user)=ole_wobble dovecot: Sep 21 12:03:59 Error: auth(default): ldap(ole_wobble,157.193.44.68): No password in reply dovecot: Sep 21 12:03:59 Info: auth(default): client out: FAIL 1 user=ole_wobble temp dovecot: Sep 21 12:04:01 Info: imap-login: Disconnected: user=<ole_wobble>, method=PLAIN, rip=157.193.44.68, lip=157.193.40.36, TLS This is my database: dn: dc=zalm,dc=UGent,dc=be objectClass: top objectClass: dcObject objectClass: organization o: Universiteit Gent dc: zalm dn: cn=admin,dc=zalm,dc=UGent,dc=be objectClass: simpleSecurityObject objectClass: organizationalRole cn: admin description: LDAP administrator userPassword:: e2NyeXB0fVpsbWpDb21kL3JSbkU= dn: ou=accounts,dc=zalm,dc=UGent,dc=be objectClass: top objectClass: organizationalUnit ou: accounts dn: cn=dovecot,ou=accounts,dc=zalm,dc=UGent,dc=be objectClass: top objectClass: person cn: dovecot sn: dovecot userPassword:: e0NSWVBUfXp6bGxQa1JoV1Nmb00= dn: uid=ole_wobble,ou=accounts,dc=zalm,dc=UGent,dc=be objectClass: top objectClass: person objectClass: posixAccount cn: Ole Wobble Olson sn: Olson uid: ole_wobble uidNumber: 3000 gidNumber: 8 homeDirectory: /home/postoffice userPassword:: e0NSWVBUfXBrOGN6SnlZVG5IL28= dn: uid=ole_wubble,ou=accounts,dc=zalm,dc=UGent,dc=be objectClass: top objectClass: person objectClass: posixAccount cn: Ole Wubble Olson sn: Olson uid: ole_wubble uidNumber: 3001 gidNumber: 8 homeDirectory: /home/postoffice What could be wrong? Thanks in advance, -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Rudy Gevaert e-mail: Rudy.Gevaert(a)UGent.be Directie ICT, Afdeling Infrastructuur Groep Systemen tel: +32 9 264 4734 Universiteit Gent fax: +32 9 264 4994 Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

1 1

[Dovecot] ALL TCP/IP connection REST when one mail contains format error
by Yi Xuan 20 Sep '05

20 Sep '05

Hi, I have setup a dovecot pop3 server on IP_A and using mbox format I have 6 users behind a NATed network, the public IP is IP_B. And one mail of one user seems contain format error. He always cannot receive the 5th mail from anywhere. Then when he receive mail in the intranet, all the TCP/IP connection REST between IP_A and IP_B. http/ssh/pop/smtp etc. all NG. After I delete the 5th mail from webmail, then the services work well. 1.It seems unreasonable, Can dovecot improve it and let it donot influence other users and other service? 2.What may cause mbox format error? and how can we avoid it? Best regards,

1 0

[Dovecot] Two strange behaviours with dovecot+postfix+squirrelmail
by Francisco Neira 20 Sep '05

20 Sep '05

Hi all, About a week ago I was forced to migrate my main (production) email server from RH9 to Centos4.1. The installation has dovecot-0.99.11 + postfix-2.1.5 and >600 mbox accessed email accounts. Number 1. Some users accessing thru squirremail (installed in my webserver) can read their INBOX at /var/spool/mail directory but when trying to delete a message they receive the following error message from squirrelmail: ERROR: Could not complete request. Consulta: COPY 1279 "mail/Trash" Reason Given: Internal error occured. Error report written to server log. [2005-09-16 15:08:04] and the error logged is the following: Sep 16 15:09:27 mail imap(username): mkdir_parents(/home/username//mail/.imap/Trash) failed: Permission denied I never stated that .imap/Trash when configuring dovecot and the strangest thing is that my account, as most of others, can delete messages moving from /var/spool/mail/my_name to /home/my_name/mail/Trash Number 2. Randomly, some users connecting from Mozilla Thunderbird via IMAP get an error message telling that there has been an error connecting to INBOX. Watching the maillog I found the following: Sep 16 13:07:43 mail imap(otheruser): File isn't in mbox format: /var/spool/mail/otheruser I accessed the user's inbox file with vi and found that there was a "--604" at the beginning of the file. In other case I found that the file was beginning with a truncated email message. Trying to "walk on the safer side", I changed the mbox_lock setting from "fcntl" to "dotlock" in the /etc/dovecot.conf file. Any suggestions and comments about his will be highly appreciated. Forgive me about my English, it is not my native lanaguage. Regards, -- Francisco Neira B. Administrador de Red Defensoria del Pueblo Lima, Peru, -05:00 UTC

2 1

[Dovecot] NO: Unsupported authentication mechanism
by Steve [Dovecot] 19 Sep '05

19 Sep '05

I'm happily using dovecot as my IMAP server and accessing mails using Thunderbird... but I want to use the Net::IMAP facilities in the Ruby standard library to write some scripts to automate various spam-related tasks & housekeeping. My Ruby script: require "net/imap" imap = Net::IMAP.new('localhost') imap.authenticate('LOGIN','myuser','mypassword') # More stuff using imap... From the documentation LOGIN uses plaintext authentication - which I understand is always acceptable for Dovecot when connecting from localhost. On the 3rd line I get a "NO response" exception raised (indicating that the IMAP server replied "NO") and the error message "Net::IMAP::NoResponseError: Unsupported authentication mechanism" If I change 'LOGIN' to 'CRAM-MD5' (the other value supported by Net::IMAP) then I get a similar (but not identical) error: "Net::IMAP::NoResponseError: Authentication failed: Unsupported authentication mechanism" If I use anything other than either 'LOGIN' or 'CRAM-MD5' I get an error from the Net::IMAP library saying "Unknown auth type" - which is reasonable. N.B. I've tried both where 'myuser' and 'mypassword' are valid - and not... this doesn't affect the error messages. There doesn't seem to be anything of interest in /var/log/messages... Can anyone tell me what is going wrong, and how to resolve this?

4 5

[Dovecot] FreeBSD port
by David King 19 Sep '05

19 Sep '05

FreeBSD users: I notice that the version of Dovecot in the FreeBSD ports system is back at .99. Are there any objections to my submitting an update to the FreeBSD ports for version 1.0a? Is it better to wait for 1.0 to be progressed a little or is it considered to be ready? 1.0a compiles and seems to run fine (on 5.3), so are there any obvious patches that would be needed for the FreeBSD build? -- Don't forget that 19 September is National Talk-Like-A-Pirate Day! http://www.talklikeapirate.com/piratehome.html

2 1

[Dovecot] 1.0alpha2: two asserts/cores
by Jeff A. Earickson 19 Sep '05

19 Sep '05

Hi, Two cores over the weekend, same assert message in syslog: imap(user): file message-body-search.c: line 393 (message_body_search_ctx): assertion failed: (input->v_offset <= part->physical_pos) Setup: Solaris 9, imap usage only, mbox format, dovecot compiled with gcc 4.0.1. gdb sessions of the two core files attached. Let me know if you need further analysis of the cores. Jeff Earickson Colby College

1 0

[Dovecot] vmailmgr user database
by Mij 19 Sep '05

19 Sep '05

hola guys Is a module for vmailmgr userdb being under work by someone? If not, i'd like to help out. Is there a standard API to implement or such? Is there some further documentation to avoid a full inspection of the sources? thank you

2 2

[Dovecot] Very minor feature request
by Steffen Kaiser 19 Sep '05

19 Sep '05

Hello, I'd suggest a way to get to know the "capabilities" of a compiled Dovecot. The background is that I've run the sequence ./configure --with-ldap && make && make install twice, all three commands tell me that all is fine (ldap is listed in the modules), but still dovecot told me that ldap is no Usedb module. A "make clean" before solved the problem -- well, something one should anyway. Besides, the "dovecot --capabilities" should also list all the defaults. Bye, -- Steffen Kaiser

3 4

[Dovecot] support multiple files.
by David Willoughby 19 Sep '05

19 Sep '05

i currently use procmail to sort my different mailing lists into differnet files for sanity puproses is there a way dovecot can find all these files? i have default_mail_env set to mbox:~/Mail/ could i use *:~/Mail/ as every file in /Mail is a mail file? -- David Willoughby email: dlw(a)d1w.org icq: 1852393

1 0

Re: [Dovecot] Misbehavior with Dovecot and Mulberry
by Jon Roma 18 Sep '05

18 Sep '05

Well, ironically after my tests succeeded, my reply to the Dovecot list just now failed to append to the Dovecot maildir folder. So I guess it works sometimes and not other times. :( The error message is the same "failed: Invalid argument". Jon Roma <roma(a)uiuc.edu> wrote: > > > Timo Sirainen <tss(a)iki.fi> wrote: > >> On Mon, 2005-09-05 at 23:57 -0500, Jon Roma wrote: >>> --> #6.3408 Mon Sep 5 23:25:13 2005 >>> A00092 APPEND Sent (\Seen) {610+} >>> A00092 NO >> >> That happens if some function returned -1 but didn't set any error. >> Shouldn't happen.. >> >>> I am running 1.0-test80 with Timo's patch to fix the "time off by >>> 200 minutes" error with mbox. All my folders are maildir at this >>> point -- I've converted them out of my UW mbx format store. My >>> client is Mulberry 3.1.6 for Windows and the OS is AIX 5.1. >> >> So, they are maildirs? Do these changes help: >> >> Index: src/imap/cmd-append.c >> =================================================================== >> RCS file: /var/lib/cvs/dovecot/src/imap/cmd-append.c,v >> retrieving revision 1.64 >> retrieving revision 1.65 >> diff -u -r1.64 -r1.65 >> --- src/imap/cmd-append.c 28 Jun 2005 11:15:57 -0000 1.64 >> +++ src/imap/cmd-append.c 18 Sep 2005 16:58:01 -0000 1.65 >> @@ -292,8 +292,7 @@ >> int failed; >> >> if (ctx->save_ctx != NULL) { >> - if (mailbox_save_continue(ctx->save_ctx) < 0 || >> - client->input->closed) { >> + if (mailbox_save_continue(ctx->save_ctx) < 0) { >> /* we still have to finish reading the message >> from client */ >> mailbox_save_cancel(ctx->save_ctx); >> Index: src/lib-storage/index/maildir/maildir-save.c >> =================================================================== >> RCS file: >> /var/lib/cvs/dovecot/src/lib-storage/index/maildir/maildir-save.c,v >> retrieving revision 1.57 >> retrieving revision 1.58 >> diff -u -r1.57 -r1.58 >> --- src/lib-storage/index/maildir/maildir-save.c 14 Aug 2005 19:02:54 >> -0000 1.57 +++ src/lib-storage/index/maildir/maildir-save.c 18 Sep 2005 >> 16:58:31 -0000 1.58 @@ -217,6 +217,10 @@ >> return -1; >> >> if (o_stream_send_istream(ctx->output, ctx->input) < 0) { >> + mail_storage_set_critical(STORAGE(ctx->mbox->storage), >> + "o_stream_send_istream(%s) failed: %m", >> + t_strconcat(ctx->tmpdir, "/", >> + ctx->files->basename, NULL)); >> ctx->failed = TRUE; >> return -1; >> } >> > > Timo: > > Yes, my mailboxes are maildirs. > > Your patch seems to have fixed the problem -- I can now append outgoing > mail to a Dovecot maildir 'Sent' mailbox as it gets sent. And I can now > also save a draft in my Dovecot maildir 'Drafts' mailbox when desired. > > What this means is that I no longer need UW (Yay!) -- I was saving my > outgoing mail and drafts in a skeletal UW tree pending resolution of > this problem. > > There is still an anomaly when using the Mulberry client to move mail > from the UW tree to Dovecot (which I now want to do in preparation for > getting rid of UW imapd. > > Using Mulberry to move mail from UW to Dovecot only works with some > messages and not others. Maybe this is not important -- I can slurp > my last two UW mboxes into a Dovecot namespace and then move them as > desired into the default namespace. > > But perhaps this behavior is something you are interested in -- here's > the transcript on the client side. > > First a copy/move that succeeded. I am in the source folder (under UW) > and have chosen a message that I want to move to the Dovecot 'Sent' > folder is the destination. > > --> #25.2768 Sun Sep 18 13:10:26 2005 > A00145 FETCH 170 (BODY[1]) > * 170 FETCH (BODY[1] {280} > ) > A00145 OK FETCH completed > > --> #1.2768 Sun Sep 18 13:10:34 2005 > A00010 APPEND Sent (\Seen) "15-Sep-2005 18:00:43 -0500" {813+} > --> #25.2768 Sun Sep 18 13:10:34 2005 > A00146 FETCH 170 (BODY.PEEK[]) > * 170 FETCH (BODY[] {813} > ) > A00146 OK FETCH completed > > A00010 OK Append completed. > > --> #1.2768 Sun Sep 18 13:10:35 2005 > A00011 STATUS Sent (MESSAGES RECENT UNSEEN UIDVALIDITY UIDNEXT) > * STATUS "Sent" (MESSAGES 5547 RECENT 1 UIDNEXT 5552 UIDVALIDITY > 1125869336 UNSEEN 0) > A00011 OK Status completed. > > --> #25.2768 Sun Sep 18 13:10:35 2005 > A00147 STORE 170 +FLAGS (\Deleted) > * 170 FETCH (FLAGS (\Seen \Deleted)) > A00147 OK STORE completed > > This move succeeded. > > Now I choose a different message in Mulberry and try to do the same > move operation. This one fails. > > --> #25.2768 Sun Sep 18 13:10:35 2005 > A00148 FETCH 171 (BODY[1]) > * 171 FETCH (BODY[1] {268} > ) > A00148 OK FETCH completed > > --> #1.2768 Sun Sep 18 13:10:44 2005 > A00012 APPEND Sent (\Seen) "15-Sep-2005 19:52:14 -0500" {832+} > --> #25.2768 Sun Sep 18 13:10:44 2005 > A00149 FETCH 171 (BODY.PEEK[]) > * 171 FETCH (BODY[] {832} > ) > A00149 OK FETCH completed > > A00012 NO Internal error occurred. Refer to server log for more > information. [2005-09-18 13:10:44] > > The corresponding syslog message is > > Sep 18 13:10:44 zippy dovecot: IMAP(roma): o_stream_send_istrea > (/var/imap/dovecot/roma/.Sent/tmp/1127067044.P44216Q3.zippy.cso.uiuc.edu) > failed: Invalid argument > > Maybe this isn't important, but I send it in case you think it's something > you want to look at. > > I'll leave the relevant mailbox around so I can try this again if > necessary. > > Thanks for the patch!

1 0

[Dovecot] "racing" error ???
by Andy Cravens 18 Sep '05

18 Sep '05

Anybody know what this racing error means? I've got hundreds of them in my Dovecot log file. I tried to search the archives but couldn't find a search link. Nothing on Google search either. dovecot: Aug 30 16:55:54 Error: IMAP(testuser): maildir_file_do(/export/home/testuser/mail) racing -- Andy Cravens

2 2

[Dovecot] Newbie question
by Andrés Rusconi 18 Sep '05

18 Sep '05

Hi, my name is Andrés Rusconi, from Tucumán, Argentina. Sorry my English, please. I am a very happy new user of Dovecot: I gained speed and simplicity with him. But I noticed that in clients who use Outlook, the deleted messages do not copy to the trash folder. This is not critical, but did not happen with Courier, and the users askme about this behavior. If some of you has somehow solved this small question, I will thank for their commentary. Saludos Andrés

2 1

[Dovecot] rawlog missing from 1.0a1?
by Gregory Bond 18 Sep '05

18 Sep '05

The code is in utils/rawlog.c but it never seems to be called anywhere?

4 3

[Dovecot] Master account
by Diego M. Vadell 18 Sep '05

18 Sep '05

Hi, Is there an administrator o master account in dovecot, which could be able too access all mailboxes? I need to periodically delete some emails (older than a number of days). I wanted to use imapfilter, a program that uses imap to access mailboxes to do that, but as the users can change their passwords, I can't do it. Is there a way to do that? Thanks in advance, -- Diego.

2 1

[Dovecot] Dovecot & SquirrelMail
by Mark Smith 18 Sep '05

18 Sep '05

At the moment SquirrelMail can only view the INBOX folder. Trash, Sent, Drafts and other folders i create are not listed. I remember there is a config in dovecot.conf to view where the default box is. I'm not sure how it should be set. My Inbox is in: /var/mail/$user/ The Other Dirs are in: /home/user/mail/ What should the config look like? Please Help Thanks! _________________________________________________________________ Be the first to hear what's new at MSN - sign up to our free newsletters! http://www.msn.co.uk/newsletters

3 3

[Dovecot] zombies in dovecot-auth processes
by jan 18 Sep '05

18 Sep '05

Hi all, I use dovecot-1.0-alpha2. Way can't auth process shutdown in a clean way. I allways discover lot of zombies for dovecot-auth, in a short time before shootingdown by linux. But everything work fine for client side. Example: dovecot 22931 0.0 0.0 3840 1104 ? S 12:12 0:00 pop3-login dovecot 22932 0.0 0.0 3844 1108 ? S 12:12 0:00 pop3-login root 22933 0.0 0.0 0 0 ? Z 12:12 0:00 [dovecot-auth] <defunct> root 22935 0.0 0.0 0 0 ? Z 12:12 0:00 [dovecot-auth] <defunct> dovecot 22938 0.0 0.0 3848 1116 ? S 12:12 0:00 imap-login root 22975 0.0 0.0 0 0 ? Z 12:12 0:00 [dovecot-auth] <defunct> dovecot 22977 0.0 0.0 3844 1112 ? S 12:12 0:00 imap-login root 22978 0.0 0.0 0 0 ? Z 12:12 0:00 [dovecot-auth] <defunct> Best Reg. //Jan Holmberg

2 1

[Dovecot] Local authentication without password
by Sebastjan Trepca 18 Sep '05

18 Sep '05

Hi, is it possible to configure dovecot so that users from a specific IP (let's say 127.0.0.1) don't have to send password? They would be authenticated no matter if passwords match or not. Thanks, Sebastjan

2 1

[Dovecot] Error indexing mbox file (LF error)
by Kevin Old 18 Sep '05

18 Sep '05

Hello everyone, I'm getting the error below for 2 different users on my system of 150+ users: Sep 12 09:32:49 uavco pop3-login: Login: cah [::ffff:172.16.3.107] Sep 12 09:32:49 uavco pop3(cah): Error indexing mbox file /var/mail/cah: LF not found where expected Sep 12 09:32:49 uavco pop3(cah): Error indexing mbox file /var/mail/cah: LF not found where expected Sep 12 09:32:49 uavco pop3(cah): Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-09-12 09:32:49] I've read in the archives that it's the blank line at the beginning of the mbox file, and once deleted everything works fine. The thing is, it keeps happening and I can't figure out why. Email clients that send mail to these accounts are the latest Outlook Express. As I said, I have 150+ users on the same system and they are fine. I'm not sure if protocol makes a difference, but we are using POP3 only. Any ideas what I can do to fix/prevent/correct this either programatically or with a patch of some sort? Is this actively being worked on? I'm running FC4 with dovecot-0.99.14-4.fc4. Any help is appreciated! Kevin -- Kevin Old kevinold(a)gmail.com

3 3

[Dovecot] Dual INBOX Locations
by Calum Power 18 Sep '05

18 Sep '05

G'day list, Just a quick question - I need to configure Dovecot to do the following: * check default_mail_env for the users' inbox in MBOX format * If the above fails, serve the user an inbox from a secondary location, in MAILDIR format. I have read up on Namespaces, however I can't seem to get this to work - login just fails when Dovecot cannot find the inbox in default_mail_env Any advice, anyone? :) Thanks, Calum -- Calum Power Systems Administrator Server101 Pty. Ltd. Fast, Reliable Web Hosting!

2 1

[Dovecot] Authentication Failure
by Dovecot 18 Sep '05

18 Sep '05

I installed Dovecot on our FC3 sendmail server and get this from our Dallas office ( out of state to me ). dovecot(pam_unix)[13823]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost Only one Dallas user can get mail (pop3 or imap). All local users work fine. I ended upgoing back to UW and all works fine. What should I look for? Thanks

2 1

[Dovecot] problems with Auth and Alpha 1a
by Søren Peter Skou 18 Sep '05

18 Sep '05

Hi all I'm not quite sure how to explain this problem, so I'll just go from the top ;-). System is setup on a FreeBSD with IMAP and POP3, both can use PAM and SQL (MySQL) as login methods, though only POP3 is accessible from "the world" - IMAP is restricted via firewall to only localhost. Simple eh? The problem is that dovecot apparently drops the SQL part from time to time. Though this can be fixed by HUPing the dovecotdaemon I'd rather that I didn't have to. I've narrowed the problem to something like this: Over time, Dovecot/POP3/SQL combination dies - I've yet to examine if the problem is on IMAP as well as this is only recently reported. I have never experienced this myself since I'm using Dovecot/IMAP/PAM and this seems to be rock solid. The configuration looks like this: OS: FreeBSD n/a 6.0-BETA3 FreeBSD 6.0-BETA3 #0: MySQL: 5.0.9-beta-log Dovecot: alpha 1 (I'll test Alpha 2 to see if the problem persists) Compilation options for dovecot: ./configure \ --enable-ipv6=no \ --with-ldap=no \ --with-vpopmail=no \ --with-mysql \ --with-ssl=no dovecot.conf: base_dir = /var/run/dovecot/ protocols = imap pop3 ssl_disable = yes disable_plaintext_auth = no login_user = dovecot login_process_per_connection = no login_greeting = Ready max_mail_processes = 1024 first_valid_uid = 1 first_valid_gid = 1 protocol imap { } protocol pop3 { } auth default { mechanisms = plain passdb pam { } userdb passwd { } passdb sql { args = /usr/local/etc/dovecot/mysql.conf } userdb sql { args = /usr/local/etc/dovecot/mysql.conf } user = root } -- END -- sql.conf: driver = mysql connect = host=localhost port=3306 dbname=N/A user=N/A password=N/A client_flags=0 default_pass_scheme = CRYPT password_query = SELECT password FROM mail WHERE username = '%n' and domain= '%d' user_query = SELECT concat('/VIRTUAL_MAIL/',domain,'/',username,'/') as home,concat('/VIRTUAL_MAIL/',domain,'/',username,'/') as mail, 1 as uid, 6 as gid FROM mail WHERE username = '%n' and domain = '%d' -- END -- I'm sort of at a loss here since everything "seems to be working" (tm) for one part, but not another Hope someone has an idea ;-) Søren P. Skou

2 1

[Dovecot] what does this mean: Warning: Error in custom flags file / Corrupted Indexes
by rick tait 18 Sep '05

18 Sep '05

Hi everyone: I am seeing a whole LOT of these messages in my dovecot logfile: imap(rickt): Sep 12 17:14:03 Warning: Error in custom flags file / home/rickt/mail/.imap/TRASH/.customflags: Duplicated ID 0 imap(rickt): Sep 12 17:14:03 Warning: Error in custom flags file / home/rickt/mail/.imap/TRASH/.customflags: Duplicated ID 1 and also these: imap(mbwnews): Sep 12 17:10:16 Error: Corrupted index file /home/ mbwnews/mail/.imap/INBOX/.imap.index: used_file_size larger than real file size (2016 vs 1608) imap(mbwnews): Sep 12 17:10:18 Error: Corrupted index file /home/ mbwnews/mail/.imap/INBOX/.imap.index: used_file_size larger than real file size (2016 vs 1608) And not just referring to my inbox, other users as well. I hava bog standard install of 0.99.10.8, on an openbsd 3.6 box. every now and then i get an error from my or my users' IMAP email client saying that it couldn't access a particular inbox. a few clicks of "OK" or "Cancel" etc and the problem seems to go away. all kinds of errors (similar to above) in the imapd logfile though, seem to correspond with the timing of the abovementioned IMAP mail client errors. one thing: my users DO use procmail, so there is a chance that their IMAP client might have a mailbox open that procmail may be trying to append to. i wonder if this is a locking issue? i guess what i'm asking is - 2 thing: 1) how can i get these pesky imap client errors to go away so my users mailboxes can be successfully selected? 2) what do the indexing errors mean? are the 2 things related? Thanks so very much in advance everyone! Best, Rick. rick tait | e: rickt(a)rickt.org | t: 323.829.5703

3 2

[Dovecot] Crashing error message
by Matt Juszczak 16 Sep '05

16 Sep '05

Sep 16 09:43:46 orion dovecot: imap(user): file mbox-sync-rewrite.c: line 375 (mbox_sync_read_and_move): assertion failed: (need_space == (uoff_t)-mails[idx].space) Got this message with all my signal 6 crashes.... Any ideas on interpretation? Thanks! -Matt

1 0

[Dovecot] Timeout while waiting for lock....
by Rob Frohne 16 Sep '05

16 Sep '05

Hi, I'm very new to administering mail, and this is surely a newbie question. I have my own IMAP mail server because I use my email as a way of filing important things, and I subscribe to a number of lists that I like to archive. I have about 40 mailboxes with up to 80,000 messages in some, and one with 40,000 messages is almost a Gigabyte in size. The total size is around 4 Gigabytes. Things were working quite well until I upgraded to OS X 10.4 and its new Mail.app mail client and then everything was too slow. I was using the UW IMAP server (2002d if I recall right) and Mail.app 1.3.9. I tried upgrading the server to the latest, but it didn't improve things noticeably. I swapped to dovecot 1.0alpha1, and used the mbox format, but that wasn't any better. I read that Maildir format was better, so I converted my mail to that format and tried that. It didn't seem much better. I tried to compile Cyrus on OS X and ran into all kinds of difficulty. I finally tried Cyrus on a Linux box, and turned off all my rules that move messages around. In comparing this to dovecot on my OS X box, Cyrus loads the messages significantly faster. I think there are some problems with my dovecot setup though. My mail.log is filled with this type of thing. Sep 15 16:43:51 cubex-wwc-edu dovecot: imap-login: Login: user=<frohro>, method=PLAIN, rip=172.17.128.191, lip=10.7.3.11 Sep 15 16:44:43 cubex-wwc-edu dovecot: imap(frohro): Timeout while waiting for lock for transaction log file /Users/frohro/Maildir/dovecot.index.log Sep 15 16:44:57 cubex-wwc-edu dovecot: imap-login: Login: user=<frohro>, method=PLAIN, rip=172.17.128.191, lip=10.7.3.11 Sep 15 16:45:51 cubex-wwc-edu dovecot: imap(frohro): Timeout while waiting for lock for transaction log file /Users/frohro/Maildir/dovecot.index.log I've tried mutt, evolution, kmail, and am now using Thunderbird, and am working on getting Mail.app to import an archive of my 4 Gigs of mail, thinking if nothing else works, I can have a copy of that on the clients I use, though I like having it on the server better. Can anyone suggest something to fix my problems, besides deleting all my email? Thanks, Rob

1 0

[Dovecot] SSL/TLS stopped working in 1.0 alpha2
by Andy Cravens 15 Sep '05

15 Sep '05

I have both 1.0 alpha1 and alpha2 installed on my test mail server. SSL/TLS does not work on alpha2. I'm using the same config file for both. No errrors in dovecot.log either. Is there a way to increase debugging info without recompiling?

2 3

[Dovecot] Dovecot Deliver Problem
by Marc Perkel 15 Sep '05

15 Sep '05

Trying to use the deliver utility and getting this error: error: net_connect(/var/run/dovecot/auth-master) failed: No such file or directory -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

4 9

[Dovecot] Re: mailbox corruption
by Yannick Majoros 14 Sep '05

14 Sep '05

Kelly Sauke wrote: >Wietse Venema wrote: > > > >>Yannick Majoros: >> >> >> >> >>>>What else is accessing the mailbox files? Any scripts running around >>>>that access mail without proper file locking, like scripts that >>>>replicate mail to another box? >>>> >>>>Whay file system is being used? >>>> >>>>If you can't figure out which is broken, then you'll have to use >>>>maildir files. >>>> >>>> >>>> >>>> >>>> >>>No scripts. If amavisd-new is safe, then nothing else should access >>>mailboxes. Only via dovecot POP3/IMAP. Do you think it is worth to go >>> >>> >>> >>> >>amavisd-new accesses mailboxe files, and what file locking >>mechanism would that be using? >> >> Wietse >> >> >> >> >> >For what its worth, I'm seeing the exact same corruption as Yannick is >talking about and the only two pieces of software installed on my >machine are postfix and dovecot. One of those two is the culprit, not >sure which one. > > > Yep, I would think the same. This is not an evidence, but a strong doubt: the same problem is still present after replacing MailScanner by amavisd-new. It could be that it happens less often, although, but I need some time to make real stats... -- ---------------------------------------------------------------------- Yannick Majoros http://www.inma.ucl.ac.be/~majoros Informaticien AUTO-INMA/FSA/UCL CSAM 4, avenue G. Lemaître B-1348 Louvain-la-Neuve Belgium Tel: +32-10-47.80.10 Fax: +32-10-47.21.80 #JAPH : http://www.inma.ucl.ac.be/~majoros/japh.txt Si vous avez des problèmes pour afficher ce message (accents qui ne passent pas, signature électronique, ...) votre système de mail n'est pas conforme aux standards, voir http://www.inma.ucl.ac.be/~majoros/email.html ----------------------------------------------------------------------

3 2

[Dovecot] web-based mail
by str tux 14 Sep '05

14 Sep '05

Hello List, I just installed dovecot and i love the simplicity of the default config; it simply works. Now I want to setup and web-based in addition to the default pop3 and imap client access - what u guys can recommend? Thanks. str

8 11

[Dovecot] Dovecot-LDA problems (CVS version) Signal 11 and empty 'mail' dir
by Steffen Kaiser 14 Sep '05

14 Sep '05

Hello, I'm trying dovecot-lda (deliver.c has CVS version 1.18). When I try to deliver a mail, an empty directory is created name $HOME/mail. This is neither the configured (via LDAP) nor the default "mail" setting in the /usr/local/etc/dovecot-deliver.conf. When the $HOME directory does not exist, but the user itself: Sep 1 11:47:12 localhost deliver: mbox: Can't create root IMAP folder /home/skaise2a/mail: Permission denied Sep 1 11:47:13 localhost sm-mta[4684]: j819lCgd004682: SYSERR(root): mailer local died with signal 11 Default mail: mail = maildir:%h/.mailboxes:INDEX=/usr/local/var/spool/dovecot/indexes/%Lu Configured via LDAP for user skaise2a: maildir:/mailcache/skaise2a:INDEX=/var/cache/dovecot/indexes/skaise2a:CONTROL=/var/cache/dovecot/control/skaise2a I have only found the error message in dovecot's src/lib-storage/index/mbox/mbox-storage.c function create_root_dir(). The Dovecot logs indicate that dovecot-lda is requesting the information from it and the message is - once the empty directory could be created - delivered into the configured IMAP root. Bye, -- Steffen Kaiser

2 2

[Dovecot] mailbox corruption
by Yannick Majoros 14 Sep '05

14 Sep '05

Hello, Here is the description of a problem we habe been having for some time. Originally posted on the postfix-users mailing list, but no solution found to date. >>>> We have been having problems with our mail system for a couple of >>>> months. Every now and then, some mailboxes get corrupted: a >>>> half-truncated message, usually without headers, is at the beginning >>>> of the mailbox, causing it to become unaccessible. >>>> >>>> For information, we use: >>>> >>>> - fedora core 4 >>>> - postfix-2.2.2-2 rpm >>>> - dovecot-0.99.14-4.fc4 rpm >>>> - mailscanner-4.36.4-1 rpm >>>> >>>> >>> >>> This ^^^^^^^^^^ is probably your problem. >>> >>> >> > > I wouldn't be so quick to blame mailscanner. I have fc4, postfix rpm > and dovecot. Nothing else and I get the same corruption he is talking > about. > > > Ok, I removed MailScanner and I still have the very same problem. Locking _does_ work for postfix and dovecot (discussed with Wietse, partly by mail). Any idea? As an alternative, is there a way of handling the problem better? Dovecot just locks on these corrupt mailboxes :-/ I didn't try Dovecot 1.0, as it is alpha and I don't have any package for that anyway (production system :-/ ). Thank you, -- ---------------------------------------------------------------------- Yannick Majoros http://www.inma.ucl.ac.be/~majoros Informaticien AUTO-INMA/FSA/UCL CSAM 4, avenue G. Lemaître B-1348 Louvain-la-Neuve Belgium Tel: +32-10-47.80.10 Fax: +32-10-47.21.80 #JAPH : http://www.inma.ucl.ac.be/~majoros/japh.txt Si vous avez des problèmes pour afficher ce message (accents qui ne passent pas, signature électronique, ...) votre système de mail n'est pas conforme aux standards, voir http://www.inma.ucl.ac.be/~majoros/email.html ----------------------------------------------------------------------

3 3

[Dovecot] Solaris build failed
by GARY GENDEL 14 Sep '05

14 Sep '05

dovecot-v1.0-alpha build failed for Solaris 11 (OpenSolaris Nevada). The problematic line is in socket.c line 228. The fix should be to change SOL_TCP to IPPROTO_TCP found in netinet/in.h. This change should work universally on all platforms. Gary

2 1