- dovecot - dovecot.org

[Dovecot] Re: separate SSL certificates for pop3s and imaps
by sean finney 11 Jul '05

11 Jul '05

On Thu, Jul 07, 2005 at 08:58:35PM +0300, dovecot-request(a)dovecot.org wrote: > Hi, > > I'm migrating a uw-imap installation to dovecot. With uw-imap I had > different SSL certificates and keys for ipop3d and imapd. How can I > configure dovecot to do the same with its pop3s and imaps services? i run dovecot in a multihomed server with three different names: mail.foo.edu smtp.foo.edu imap.foo.edu which, for ssl purposes, means we need three different certs to keep applications happy. my approach is to start a seperate dovecot process for each address, and manage the configuration in three seperate files, each one telling dovecot to specifically bind to only one address, and use a seperate runtime directory specific to that address. so for example, in my initscript, instead of just doing something like: start() { echo -n $"Starting $prog: " daemon $prog -c /etc/dovecot.conf RETVAL=$? echo [ $RETVAL -eq 0 ] && touch /var/lock/subsys/$prog return $RETVAL } i do something like: start() { echo -n $"Starting $prog: " for s in imap mail smtp; do mkdir -p /var/run/dovecot/${s}.foo.edu daemon $prog -c /etc/dovecot/${s}.foo.edu.conf done RETVAL=$? echo [ $RETVAL -eq 0 ] && touch /var/lock/subsys/$prog return $RETVAL } where the value of the ssl cert config is different in each of the files. you could extend this to also have one config file to only listen for pop and the other only for imap. hth, sean

4 5

[Dovecot] Creating encrypted passwords for new users /etc/imap.passwd
by John_R._McWade 09 Jul '05

09 Jul '05

Hello. I've been attempting to locate information on how to actually create the encrypted passwords for a new user in /etc/imap.passwd file. Im really going into this blindly, not having ever used dovecot before, and really just need to be pointed to any existing resources on this topic. This is a setup of dovecot (w/ sendmail,squirrelmail) on FC2. I've got one successful auth so far as a test user, with their info cut/pasted directly from /etc/passwd (it works) whereas using {PLAIN}password causes dovecot to drop the connection with an aborted login. So what I'm actually looking for is a resource or a quick response regarding the actual creation of the encrypted password in /etc/passwd style. Any clues on where I should look for this info? John

2 1

[Dovecot] io leak when dnotify is enabled but not available
by Johannes Berg 08 Jul '05

08 Jul '05

Hi, When dnotify is enabled, but not in the kernel, there's an io leak: $ /sbin/dovecot --exec-mail imap * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS] Logged in as johannes a select inbox * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 787 EXISTS * 0 RECENT * OK [UIDVALIDITY 1106061449] UIDs valid * OK [UIDNEXT 790] Predicted next UID a OK [READ-WRITE] Select completed. b IDLE imap(johannes): Error: fcntl(F_NOTIFY) failed: Invalid argument imap(johannes): Error: fcntl(F_NOTIFY) failed: Invalid argument + idling DONE b OK Idle completed. q logout * BYE Logging out q OK Logout completed. imap(johannes): Warning: I/O leak: 0x10068ff0 (8) Attached patch fixes it, I hope the patch is correct :) johannes

1 0

[Dovecot] stat() failed with mbox /var/mail/%u
by Jungshik Shin 08 Jul '05

08 Jul '05

Hello, Over the last 12 hours or so, I've been wrestling with a mysterious dovecot issue. After upgrading a mail server I'm helping my friend with maintaining from Fedora Core1 to Fedora Core4, I realized that I couldn't use UW-IMAP4 anymore (well, I can compile it myself, but it turned out that UW-IMAP was the main cause of the server's having load average as high as 30 from time to time so that I decided to move onto dovecot). Although I loved to migrate to maildir, I didn't dare to tackle the migration (I have a lot more important things to do :-)) to maildir. Instead, I thought that dovecot's indexing of mbox files should make the performance of the server a lot better than UW-IMAP. (in addition, we upgraded the HW from P3 800MHz single to P4 dual 3GHz). Last night, I experimented with several mboxes of one user's account (INBOX in /var/mail/<userid> and others in ~/mail/) and it worked perfectly well. So, I moved mboxes of other users and launched 'dovecot' informing users that the mail server is back up again. However, it didn't work with inbox (for IMAP) and POP3. There's no problem accessing mail folders in '~/mail', but accessing /var/mail/%u (inbox for IMAP) and using the same folder with POP3 didn't work. The error I got in the log file is: Jul 8 01:17:24 biosoft dovecot: pop3-login: Login: xyz123 [::ffff:1xx.2yy.zz.178] Jul 8 01:17:24 biosoft dovecot: POP3(xyz123): stat() failed with mbox file /var/mail/xyz123: Permission denied Jul 8 00:34:45 biosoft dovecot: imap-login: Login: xyz123 [::ffff:1xx.2yy.zz.178] Jul 8 00:34:45 biosoft dovecot: auth(default): Error sending status request (Operation not permitted) Jul 8 00:34:45 biosoft dovecot: imap-login: Login: xyz123 [::ffff:1xx.2yy.zz.178] Jul 8 00:34:45 biosoft dovecot: IMAP(xyz123): stat() failed with mbox file /var/mail/xyz123: Permission denied ls -ld / /var /var/mail/ /var/mail/xyz123 drwxr-xr-x 23 root root 4096 Jul 7 19:28 / drwxr-xr-x 26 root root 4096 Jul 7 23:35 /var drwxrwxrwt 2 root mail 4096 Jul 8 00:36 /var/mail/ -rw-rw---- 1 xyz123 mail 130751237 Jul 7 23:37 /var/mail/xyz123 I tried various combinations of permissions and ownerships for /var/mail (1777, 2775) and /var/mail/<userid>, but nothing made any difference. I also tweaked mbox locking methods ('dotlock fcntl' or 'fcntl' alone) When I came across this problem with the latest stable (2005-07-06), I went back to FC4's default package (0.99??), but with a slightly different error message in the log file, basically I had the same problem. I kept the default values for most configuration parameters. What I changed are listed below: mail_extra_groups = mail pop3_uidl_format = %08Xv%08Xu protocols = imap imaps pop3s default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u Also attached is the entire /etc/dovecot.conf I'm really desperate to get some enlightening answers on this problem, for which I'll really appreciate you. Thanks tons in advance, Jungshik ## 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=/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 imaps pop3s # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. You can specify ports with # "host:port", although with multiple protocols you probably want to move this # setting inside protocol imap/pop3 { ... } section, so you can specify # different ports for IMAP/POP3. listen = [::] # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = # Disable SSL/TLS support. #ssl_disable = no # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf #ssl_cert_file = /usr/share/ssl/certs/dovecot.pem #ssl_key_file = /usr/share/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 = yes # 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 = 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 # Greeting message for clients. #login_greeting = Dovecot ready. ## ## 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_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 = # 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 = default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # If you need to set multiple mailbox locations or want to change default # namespace settings, you can do it by defining namespace sections: # # You can have private, shared and public namespaces. The only difference # between them is how Dovecot announces them to client via NAMESPACE # extension. Shared namespaces are meant for user-owned mailboxes which are # shared to other users, while public namespaces are for more globally # accessible mailboxes. # # REMEMBER: If you add any namespaces, the default namespace must be added # explicitly, ie. default_mail_env does nothing unless you have a namespace # without a location setting. Default namespace is simply done by having a # namespace with empty prefix. #namespace private { # Hierarchy separator to use. You should use the same separator for all # namespaces or some clients get confused. '/' is usually a good one. #separator = / # Prefix required to access this namespace. This needs to be different for # all namespaces. For example "Public/". #prefix = # Physical location of the mailbox. This is in same format as # default_mail_env, which is also the default for it. #location = # There can be only one INBOX, and this setting defines which namespace # has it. #inbox = yes # If namespace is hidden, it's not advertised to clients via NAMESPACE # extension or shown in LIST replies. This is mostly useful when converting # from another server with different namespaces which you want to depricate # but still keep working. For example you can create hidden namespaces with # prefixes "~/mail/", "~%u/mail/" and "mail/". #hidden = yes #} # Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # # flags, date.sent, date.received, size.virtual, size.physical # mime.parts, imap.body, imap.bodystructure # # Different IMAP clients work in different ways, so they benefit from # different cached fields. Some do not benefit from them at all. Caching more # than necessary generates useless disk I/O, so you don't want to do that # either. # # Dovecot attempts to automatically figure out what client wants and it keeps # only that. However the first few times a mailbox is opened, Dovecot hasn't # yet figured out what client needs, so it may not perform optimally. If you # know what fields the majority of your clients need, it may be useful to set # these fields by hand. If client doesn't actually use them, Dovecot will # eventually drop them. # # Usually you should just leave this field alone. The potential benefits are # typically unnoticeable. #mail_cache_fields = # Space-separated list of fields that Dovecot should never save to cache file. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Like mailbox_check_interval, but used for IDLE command. #mailbox_idle_check_interval = 30 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no # Maximum allowed length for mail keyword name. It's only forced when trying # to create new keywords. #mail_max_keyword_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. # Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes. #mail_read_mmaped = no # Don't use mmap() at all. This is required if you store indexes in remote # filesystems (NFS or clustered filesystem). #mmap_disable = no # Don't write() to mmaped files. This is required for some operating systems # which use separate caches for them, such as OpenBSD. #mmap_no_write = no # Locking method for index files. Alternatives are fcntl, flock and dotlock. # Dotlocking uses some tricks which may create more disk I/O than other locking # methods. #lock_method = fcntl # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Which locking methods to use for locking mbox. There's four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist in all systems. Doesn't work with NFS. # # You can use multiple locking methods; if you do the order they're declared # in is important to avoid deadlocks if other MTAs/MUAs are using multiple # locking methods as well. Some operating systems don't allow using some of # them simultaneously. #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl mbox_read_locks = fcntl mbox_write_locks = fcntl # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 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 # Log prefix for mail processes. See doc/variables.txt for list of possible # variables you can use. #mail_log_prefix = "%Us(%u): " ## ## IMAP specific settings ## protocol imap { # Login executable location. login_executable = /usr/libexec/dovecot/imap-login # IMAP executable location #mail_executable = /usr/libexec/dovecot/imap # This would write rawlogs into ~/dovecot.rawlog/ directory: mail_executable = /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap # Maximum IMAP command line length in bytes. Some clients generate very long # command lines with huge mailboxes, so you may need to raise this if you get # "Too long argument" or "IMAP command line too large" errors often. #imap_max_line_length = 65536 # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/imap # Send IMAP capabilities in greeting message. This makes it unnecessary for # clients to request it with CAPABILITY command, so it saves one round-trip. # Many clients however don't understand it and ask the CAPABILITY anyway. #login_greeting_capability = no # Workarounds for various client bugs: # 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. # 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-negative-fetch: # Thunderbird sometimes messed up some calculations and wants to read # the message past it's end, giving negative size to FETCH BODY[]<..> # command. This workaround just hides the error message. #imap_client_workarounds = outlook-idle } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. #login_executable = /usr/libexec/dovecot/pop3-login # POP3 executable location #mail_executable = /usr/libexec/dovecot/pop3 # Don't try to set mails non-recent or seen with POP3 sessions. This is # mostly intended to reduce disk I/O. With maildir it doesn't move files # from new/ to cur/, with mbox it doesn't write Status-header. #pop3_no_flag_updates = no # Support LAST command which exists in old POP3 specs, but has been removed # from new ones. Some clients still wish to use this though. Enabling this # makes RSET command clear all \Seen flags from messages. #pop3_enable_last = no # POP3 UIDL format to use. You can use following variables: # # %v - Mailbox UIDVALIDITY # %u - Mail UID # %m - MD5 sum of the mailbox headers in hex (mbox only) # %f - filename (maildir only) # # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier version 0 : %f # Courier version 1 : %u # Courier version 2 : %v-%u # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # # Note that Outlook 2003 seems to have problems with %v.%u format which is # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. pop3_uidl_format = %08Xv%08Xu # 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 ## # You can have multiple authentication processes. With plaintext authentication # the password is checked against each process, the first one which succeeds is # used. 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. # 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 = no # Even more verbose logging for debugging purposes. Shows for example SQL # queries. #auth_debug = no auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous mechanisms = plain # 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 # checkpassword <path>: checkpassword executable authentication # passwd-file <path>: passwd-like file with specified location # vpopmail: vpopmail authentication # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # sql <config path>: SQL database, see doc/dovecot-sql.conf passdb = pam # 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 doc/dovecot-ldap.conf # sql <config path>: SQL database, see doc/dovecot-sql.conf userdb = passwd # 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. #chroot = # Number of authentication processes to create #count = 1 # Require a valid SSL client certificate or the authentication fails. #ssl_require_client_cert = no } # PAM doesn't provide a way to get uid, gid or home directory. If you don't # want to use a separate user database (passwd usually), you can use static # userdb. #auth onlypam { # mechanisms = plain # userdb = static uid=500 gid=500 home=/var/mail/%u # passdb = pam # user = dovecot-auth #} #auth ldap { # mechanisms = plain # userdb = ldap /etc/dovecot-ldap.conf # passdb = ldap /etc/dovecot-ldap.conf # user = dovecot-auth #} #auth virtualfile { # mechanisms = plain digest-md5 # userdb = passwd-file /etc/passwd.imap # passdb = passwd-file /etc/passwd.imap # user = dovecot-auth #} # 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 # } # } #}

2 2

[Dovecot] "Leave a copy on server" not marking messages as read...
by Matt Juszczak 07 Jul '05

07 Jul '05

Hi all, Our customers who have "Leave a copy on server" with POP3 continue to check their email, and each time they check it it re-downloads all emails (so it doesn't seem to be updating those messages already downloaded). Any ideas? Thanks! -Matt

1 0

[Dovecot] IMAP Folders
by Matt Juszczak 07 Jul '05

07 Jul '05

Hi all, We're using the mbox format and I tried setting up IMAP on my boss's computer tonight. He likes subfolders, and although they work, he can't seem to remove subfolders once he created them, nor create new folders without using something other than his mail client (like mkdir from the command line). Any ideas on this? Does dovecot just not officially support IMAP and subfolders with the mbox format? Or could it be a permissions issue? -Matt

2 1

[Dovecot] RE: dovecot not able to access sentmail folder in home directory(chdir)
by vineet 07 Jul '05

07 Jul '05

problem is solved the problem was with the access permissions to the folder having the users' folders make sure that dovecot has the permission to access the folders containg the users' folders vineet _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

1 0

[Dovecot] test76 segfaults?
by Johannes Berg 06 Jul '05

06 Jul '05

Hi, I was just trying to port my dspam plugin to the latest test release but ran into trouble so I decided to test the code itself first. I have the following maildir: johannes:~/.mail$ find . ./cur ./new ./new/test ./tmp ./.SPAM ./.SPAM/cur ./.SPAM/new ./.SPAM/tmp Now I run $ exec /usr/sbin/dovecot --exec-mail imap * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS] Logged in as johannes A SELECT INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 1 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1120680468] UIDs valid * OK [UIDNEXT 2] Predicted next UID A OK [READ-WRITE] Select completed. B COPY 1 SPAM imap(johannes): Error: Corrupted index file /home/johannes/.mail/.SPAM/dovecot.index: uid_validity = 0, next_uid = 2 Segmentation fault However, it actually did copy something: johannes:~/.mail$ find . ./cur ./cur/test:2, ./new ./tmp ./.SPAM ./.SPAM/cur ./.SPAM/new ./.SPAM/new/1120680473.P1535Q0M900310.johannes ./.SPAM/tmp ./.SPAM/dovecot.index ./.SPAM/dovecot-uidlist ./.SPAM/dovecot-uidlist.lock ./.SPAM/dovecot.index.log.2 ./.SPAM/dovecot.index.log ./dovecot.index.log ./dovecot.index ./dovecot.index.cache ./dovecot-uidlist The mail in that, for reference, is just this: --- A: xxx Subject: hallo! From: johannes X-DSPAM-Signature: asdf wow! --- johannes

1 1

[Dovecot] I need sleep (dovecot auth / postfix 2.3)
by /dev/rob0 06 Jul '05

06 Jul '05

I need the new sleep feature (smtpd_*_restrictions) of Postfix 2.3 snapshots, but I'm using the Dovecot auth patch. The 2.2.1 patch had problems in the snapshots I tried. Fortunately the problems were very simple. rob0@room101:~/src/mail/postfix-2.3-20050630$ patch -p1 < ~/dl/postfix-2.2.1-dovecot-auth.patch [snip] patching file src/smtpd/Makefile.in Hunk #1 FAILED at 1. Hunk #2 FAILED at 296. 2 out of 2 hunks FAILED -- saving rejects to file src/smtpd/Makefile.in.rej patching file src/smtpd/smtpd.c Hunk #1 FAILED at 854. Hunk #2 succeeded at 1006 (offset 16 lines). Hunk #3 succeeded at 1173 (offset 1 line). Hunk #4 succeeded at 1306 (offset 20 lines). Hunk #5 succeeded at 1562 (offset 33 lines). Hunk #6 succeeded at 1692 (offset 54 lines). Hunk #7 succeeded at 1834 (offset 72 lines). Hunk #8 succeeded at 2918 (offset 135 lines). Hunk #9 succeeded at 2952 (offset 73 lines). Hunk #10 succeeded at 3262 (offset 152 lines). Hunk #11 succeeded at 3301 (offset 73 lines). Hunk #12 succeeded at 3551 (offset 154 lines). 1 out of 12 hunks FAILED -- saving rejects to file src/smtpd/smtpd.c.rej [snip] I fixed the failures manually. Attached is a patch which only changes those two files ... it's a supplement to the existing patch as provided by Timo: http://dovecot.org/patches/postfix/postfix-2.2.1-dovecot-auth.patch I have not yet tested either sleep or AUTH, because I *do* need sleep for real. :) But it did compile with no errors nor [noted] warnings. I do have this running. -- mail to this address is discarded unless "/dev/rob0" or "not-spam" is in Subject: header

1 1

[Dovecot] Username mapping
by nodata 06 Jul '05

06 Jul '05

Hello. We're using dovecot with mysql for authentication, with postfixadmin for the admin web interface. We are moving users from passwd file usernames to email@domain style logins. Is there a better way to allow both sets of usernames (old and new) to work with dovecot than by adding extra copies of rows to the mailboxes table and changing the username? i.e. does dovecot support some kind of username mapping or aliasing? Thanks a lot

3 2

[Dovecot] dovecot not able to access sentmail folder in home directory(chdir)
by vineet 06 Jul '05

06 Jul '05

using dovecot version 0.99.11 while accessing through squirrelmail or even connecting manually(using openssl) to the server dovecot is not able to access the folder the mail.err log file has the following entry: dovecot: (/home/user) permission denied error no 89 returned by child process the squirrel mail error was connection dropped by imap server Query capability thanks vineet _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

1 0

[Dovecot] dovecot 1 for production? which one?
by Jeff A. Earickson 05 Jul '05

05 Jul '05

Hi, I've been lurking on the list since Spring, planning to replace UW-IMAP with dovecot 1.0 sometime this summer. The recent thread on "1.0" has not given me a good feeling about seeing it before summer's end. So I wonder if I should use dovecot-1.0-test-xx code or dovecot-stable-[date] code (which seems to change every day, how stable is that???). This is confusing, advice please. My setup: Solaris 9, mbox format. Jeff Earickson Colby College

2 1

[Dovecot] Root password or key access to pop3?
by Matt Juszczak 05 Jul '05

05 Jul '05

Hi all, We're an ISP, and are currently looking for a way for our tech support guys to access customer's email without having shell access to the server, or knowing the customer's password. We'd like to install a custom webmail client that would only show the user's inbox and the ability to delete the messages. The problem is, that we would have to know the user's password in order for my PHP pop3 code to go out and fetch the mail. Is there a way I can setup and/or patch dovecot so that any connection from <said IP address> can use the password "jq3erjq3535" for any account, and it will authenticate them? Or is this some kind of custom patch I would need to write? Thanks! -Matt

3 5

[Dovecot] error connecting dovecot from squirrelmail
by Srinivas 04 Jul '05

04 Jul '05

the problem is: 1. the error in the mailerr file is: Jul 4 19:42:26 obelix dovecot: chdir(/home/user) failed with uid 1229: Permission denied Jul 4 19:42:26 obelix dovecot: child 16385 (imap) returned error 89 2. the error msg given by Squirrelmail is: ERROR: connection dropped by imapserver QUERY: CAPABILITY the dovecot and squirrelmail settings are same on both the servers 3. the mailbox settings in dovecot.conf: default_mail_env = mbox:~/mail:INBOX=/var/spool/mail/%u OS: Debian Sarge stable thanks srinivas _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

1 0

[Dovecot] BOGUS files
by Obantec Support 04 Jul '05

04 Jul '05

Hi what does this mean BOGUS.watasiuk.8B8I (watasiuk is a username). FC3 Mark -- Obantec Support www.obantec.net 0845 458 3121 WebHosting and Domains Nominet UK Member & IPStag Holder CentralNic Accredited Reseller

4 6

[Dovecot] dovecot - outlook users keep getting locked out of imap
by Anthony Kolasny 03 Jul '05

03 Jul '05

Greetings: My outlook users accessing mail via dovecot's imaps have been consistantly getting locked out of their email. It happens about once a week per outlook user. It appears to happen when the are cliking on emails with attachments. When this happens, there are two imap deamons running for that user. I kill both deamons and things start working again. Squirrelmail, thunderbird and pine users haven't had this issue. I'm running a version of dovecot dated dovecot-stable-20050610. All user accounts have their mail on nfs mount points. The INBOX directory is local to the imap server but we have a smtp server that gets this data via nfs. Below is the dovecot.conf info: base_dir = /var/run/dovecot/ protocols = imap imaps ssl_disable = no ssl_cert_file = /usr/local/imaps/certs/dovecot_cert.pem ssl_key_file = /usr/local/imaps/certs/dovecot_key.pem disable_plaintext_auth = yes login_dir = /var/run/dovecot/login login_process_size = 128 login_processes_count = 9 login_max_processes_count = 256 login_max_logging_users = 512 verbose_proctitle = yes mail_extra_groups = mail default_mail_env = mbox:~/mail/:INBOX=/var/spool/mail/%u mmap_disable = no lock_method = fcntl mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl mbox_lock_timeout = 300 mbox_dotlock_change_timeout = 30 mbox_dirty_syncs = yes mbox_very_dirty_syncs = no protocol imap { imap_client_workarounds = outlook-idle } protocol pop3 { } auth default { mechanisms = plain passdb = pam userdb = passwd user = root } Your assistance is greatly appreciated. Thanks, Anthony

2 1

[Dovecot] dovecot restart bug?
by Andrew Hutchings 03 Jul '05

03 Jul '05

Using my initd script (no idea of the origin now) to do a restart I randomly get: Jun 28 13:56:05 svr24 dovecot: Killed with signal 15 Jun 28 13:56:05 svr24 dovecot: Dovecot v1.0-test74 starting up Jun 28 13:56:06 svr24 dovecot: Auth process died too early - shutting down Jun 28 13:56:06 svr24 dovecot: auth(default): net_connect_unix(/var/run/dovecot/auth-worker.23322) failed: No such file or directory Jun 28 13:56:06 svr24 dovecot: child 23322 (auth) returned error 89 It then suddenly starts working again, is this something to do with that new mysql timeout feature? This started happening when I migrated from test72 to test73. Regards Andrew -- Andrew Hutchings (A-Wing) - Linux Guru Netserve Consultants - http://www.domaincity.co.uk/ A-Wing Internet Services - http://www.a-wing.co.uk/ Random quote 111: "It's possible, you can never know, that the universe exists only for me." - BILL GATES

2 1

[Dovecot] dovecot problem or not ?
by Mircea Hutanu 03 Jul '05

03 Jul '05

Hi, I've setup a postfix mailserver with dovecot and postgres database for virtual domains with virtual users, but I have some problems getting the accounts to work. I've used instruction from this tutorial : http://wiki.dovecot.org/moin.cgi/DovecotPostgresql I want users to be able to get their email with imap or pop3, but I didn't manage to solve this problem. The server makes mbox style user accounts, I can send email to them but when I try to read emails from virtual accounts I get the following error : Jun 28 14:42:52 voodoo dovecot-auth: Login process 10 connected Jun 28 14:42:52 voodoo dovecot-auth: Login process 10 sent handshake: PID 10491 Jun 28 14:42:58 voodoo dovecot-auth: PGSQL: Performing query: SELECT password FROM users WHERE userid = 'user(a)foo.org' Jun 28 14:42:58 voodoo dovecot-auth: PGSQL: Performing query: SELECT '/home/'||home AS home, uid, gid FROM users WHERE userid = 'user(a)foo.org' Jun 28 14:42:58 voodoo pop3(user(a)foo.org): mbox: Can't create root IMAP folder /home/foo.org/mails/user/mail: Permission denied Jun 28 14:42:58 voodoo pop3(user(a)foo.org): Failed to create storage with data: mbox:/home/virtual/foo.org/mails/user Jun 28 14:42:58 voodoo pop3-login: Login: user(a)foo.org [127.0.0.1] Jun 28 14:42:58 voodoo dovecot-auth: Login process 8 disconnected Jun 28 14:42:58 voodoo dovecot: child 10492 (pop3) returned error 89 The error " mbox: Can't create root IMAP folder /home/foo.org/mails/user/mail: Permission denied" appears because, using mbox, the home for virtual accounts is /home/virtual/foo.org/mails/user, where user is allready the mbox file, to the sistem can't create the directory structure for IMAP settings. What I'm doing wrong ? Did someone else got this problem ? Thanks ! -- ------------------------------ Mircea Hutanu voodookid(a)gmail.com ------------------------------

2 1

[Dovecot] Automating message archiving
by Steffen Kaiser 03 Jul '05

03 Jul '05

Hallo, I recently stumple over some discussion about Sieve and what's the advantage to integrate it into the server rather than the LDA. Most of the filtering capabilites local users want to have performed are related to the INBOX or more preciesly the way to filter the message coming in. However, there are few tasks left: 1) Auto-archive old mail. 2) Drop old mail. 3) "Seen" mails are moved from INBOX to somewhere else. To 1) Several people love to store each single mail, but because the system becomes very slow when they open a mailbox with, day, 5000 messages (Mozilla even core dumps sometimes); they archive the mails by year or month, if they got elder than, say, 6 month. I do not want to discuss this habbit, it's like it is and I have the trouble with it. To 2) There is the doing of dropping all messages flagged as SPAM into a specific folder. It would be nice if the does messages are deleted, when they grew get elder. To 3) I don't grasp the idea, but it seems that notebook users want to look, what messages are new, flag and download selected ones; when they connect next time the "old, already seen" ones should be invisible, but still accessable on demand in another folder. Maybe it has to do with that the client sometimes reads the whole IMAP INBOX again, instead just the new ones. I've seen this behaviour with Mozilla myself in conjunction with a variaty of IMAP servers now and then. Those things must be user-configurable, of course ;-), I hoped Sieve would solve this problems, but it doesn't. The MVMF mentioned in the mailing list, doesn't as well. Does somebody has some solution for these tasks, besides to setup a cronjob and hack a webinterface? Is there some Dovecot tool that one can use to manipulate the mail storage? UW-IMAP ships such thing (mailutil), but it does not support Maildir and it would be nice, when the Dovecot extensions are created well. Bye, -- Steffen Kaiser

3 2

[Dovecot] Authenticate login failed: Unsupported authentication mechanism
by Orchun Kolcu 03 Jul '05

03 Jul '05

Hi, I just switched (or tried to) from UW-IMAP to dovecot. When I try to login through the telnet client I get: 1 NO Authentication failed and in the log I get: imap-login: Authenticate PLAIN failed: Unsupported authentication mechanism If I try to login through the IMAP client (Thunderbird), in the log I get the slightly different: imap-login: Authenticate login failed: Unsupported authentication mechanism Here's the auth setup from the conf: auth default { mechanisms = plain passdb = pam imap userdb = passwd user = root } And here's /etc/pam.d/imap for good measure: auth required pam_nologin.so auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth session required pam_stack.so service=system-auth The server is a fairly standard Redhat 8 setup. Any idea what's going on? Thanks! -- Orchun Kolcu orchunk(a)fastem.com -- http://www.fastmail.fm - The professional email service

3 3

Re: [Dovecot] error while connecting from squirrelmail
by Srinivas 02 Jul '05

02 Jul '05

dovecot and squirrelmail configuration successfull!! The problem was: There were many other options related to ssl,which were enabled, like ssl_cert_file,ssl_parameters_file and so on. i disabled them all, and it's working fine now. Now, only, ssl_disable = no is uncommented. Thank you all. Srinivas _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

1 0

[Dovecot] newbie - trying to set up pop3 access for multiple domains
by Andy Green - Green Consulting 01 Jul '05

01 Jul '05

I'm hosting multiple domains, and I'm having problems getting dovecot to play nicely. The only protocol I've got enabled in the conf file is pop3, yet the maillog shows the following entries when I try to authenticate: mbox: Can't create root IMAP folder /mail: Permission denied Failed to create storage with data: mbox:/var/mail/vhosts/<domain name here>/<user name here> returned error 89 Any ideas/suggestions would be greatly appreciated.

1 0

Re: [Dovecot] error while connecting from squirrelmail
by Srinivas 01 Jul '05

01 Jul '05

>Only two things I can think of: >1. Dovecot was not configured for imap with ssl (check that >ssl_disable is not set to yes). Also check the protocols statement >that it supports imaps. > >2. Check that you do not have access lists blocking off 993 to your >squirrelmail. This is often encountered if using tcp wrappers and >you're running dovecot through (x)inetd. > >Regards, Neil The ssl_disable is set to no and the protocols statement contains all the four protocols: imap pop3 imaps pop3s. But i couldn't make out the 2nd point, you suggested.Can you, please, describe it a little more ? Srinivas _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

3 2

[Dovecot] error while connecting from squirrelmail
by Srinivas 01 Jul '05

01 Jul '05

Hi all, I am new to dovecot and squirrelmail and I am trying to configure squirrelmail with dovecot as its imap server. When i disable "Secure Imap (TLS)" option (2-A-7) from squirrelmail configure menu, it's working fine. But when i try to enable tls support, squirrelmail is giving the following error: Warning: fsockopen(): unable to connect to 192.xx.xx.xx:993 in /usr/share/squirrelmail/functions/imap_general.php on line 445 ERROR Error connecting to IMAP server: tls://192.xx.xx.xx. 111 : Connection refused Go to the login page The port numbers of the imap server are as follows: imap_listen 143 pop3_listen 110 imaps_listen 993 pop3s_listen 995 Squirrelmail and the dovecot imap server are running on different machines, so it is essential to enable tls support. All the machines are running Debian Sarge. Can anyone suggest a solution for the above problem ? Thank you. Srinivas _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

2 1

[Dovecot] root login is refused, but....
by Roberto Tagliaferri 30 Jun '05

30 Jun '05

If i try to connect as root (dovecto 1.0) with wrong password doveco exit with an auth error robyt:~# telnet dns pop3 Trying x.x.x.x Connected to dns. Escape character is '^]'. +OK Dovecot ready. user root +OK pass [wrong] -ERR Authentication failed. but if the password is correct dovecot exit but with another error: user root +OK pass [correct] -ERR [IN-USE] Internal login failure. Refer to server log for more information. Connection closed by foreign host. robyt:~# Why dovecot don't close the connection at user root? With this system i may know the root password.. -- Roberto Tagliaferri Responsabile Progettazione & Produzione TosNet s.r.l. - Internet Service Provider r.tagliaferri(a)tosnet.it www.tosnet.it

3 3

[Dovecot] Dovecot doesn't use vchkpw properly :(
by Casey Allen Shobe 30 Jun '05

30 Jun '05

Hey all, It seems that dovecot does NOT call vchkpw properly when using vpopmail-style authentication, I can only guess that it reads the vpasswd{,.cdb} files directly. This is indicated by the syslog log for the mail facitily which reads: Jun 30 16:51:30 [vpopmail] vchkpw-smtp: (PLAIN) login success blah@blah.com:24.17.153.137 Jun 30 17:16:25 [pop3-login] Login: blah(a)blah.com [24.17.153.137] Jun 30 17:47:42 [imap-login] Login: blah(a)blah.com [216.57.201.58] pop3-login and imap-login are dovecot processes - vchkpw is never called or there would also be log entries for it. I've verified this with the vpopmail list, who agree that the problem lies within dovecot. This might not be quite so annoying, but we are using vpopmail compiled with the --enable-learn-passwords option, which will populate the password files with cleartext versions of the passwords where they are missing. Because of dovecot not calling vchkpw, this doesn't work for POP3/IMAP logins, only SMTP (using qmail-smtpd). People don't send mail from every account they poll, and we need to get all of the passwords in cleartext form so that we can complete migration to a PostgreSQL password database which multiple applications will use to authenticate. Are there plans to make dovecot use vchkpw in the normal checkpassword manner? If not, I'd like to request it. We will probably switch back to qmail-pop3d and bincimap for the time being to finish collecting passwords if we can't get a quick fix...I think we can do that without much impact. Cheers, -- Casey Allen Shobe | http://casey.shobe.info cshobe(a)seattleserver.com | cell 425-443-4653 AIM & Yahoo: SomeLinuxGuy | ICQ: 1494523 SeattleServer.com, Inc. | http://www.seattleserver.com

2 3

RE: [Dovecot] LF not found where expected
by Miles Mawyer 30 Jun '05

30 Jun '05

Thanks for the reply. I think I'd found the issue. It seems to be the empty line that is ending up at the top of mail file. I removed that blank line out of one of the mail box files, and it started working without an issue. I'm not sure what is causing the empty line in the mbox file however. Most of my clients use pop3 to download their messages through dovecot. Could this be happening if the client only downloads part of their messages? Pretty easy for me to straighten out, but I didn't know if this was a bug that needed to be addressed. ... Miles Mawyer -=- Webmaster . Centralva.net ... ... mmawyer(a)rosecomputers.com ... ... 434.385.5053 ... -----Original Message----- From: Timo Sirainen [mailto:tss@iki.fi] Sent: Tuesday, June 28, 2005 7:52 AM To: Miles Mawyer Cc: dovecot(a)dovecot.org Subject: Re: [Dovecot] LF not found where expected On 27.6.2005, at 18:45, Miles Mawyer wrote: > pop3(mjmurray): Jun 27 11:16:38 Error: Error indexing mbox file > /var/mail/mjmurray: LF not found where expected These usually happen because the mbox file has two adjacent From-line, ie: From foo ... From bar ... Message-headers: ... That shouldn't happen normally though. Sounds like something is wrong with how your mails are written. Are all the software that are writing to the mbox using same lock methods? Anyway, 1.0-test/stable versions of Dovecot can handle the adjacent From-lines too without failing.

2 1

[Dovecot] How to lock a user out?
by Kai Wang 29 Jun '05

29 Jun '05

Hi, We are considering to migrate to Dovecot. We can running uw-imap and have a local path which allow us to lock a user by creating a .lockdir directory in the user home directory and put our warning message to .lockdir/mbox. The locked user can still receive messages in ~/mbox. But can not access any messages except ~/.lockdir/mbox. I wonder if Dovecot has any similar feature which we can use to lock a user out without affecting the mail delivery? Kai Wang University of Calgary

2 4

[Dovecot] 1.0-test74
by Timo Sirainen 28 Jun '05

28 Jun '05

http://dovecot.org/test/ Not much has happened, but the APPEND bugfix is important since it was broken in test73 (at least). Summer makes me tired and lazy. :( I've been trying to get keywords implemented in maildir. Hopefully works soon.. After that I'll create 1.0-stable2 (ugh. any other naming ideas?) branch of the code before merging the new master/config code. - Fixed APPEND .. I hope? At least works much better than before - pop3_uidl_format = %m now doesn't return broken 0 MD5 sums when the MD5 sum wasn't written in indexes for some reason (eg. appended/copied to INBOX with IMAP and trying to access mail with POP3). - Authentication cache wasn't working when Dovecot was used for proxying - Index cache file wasn't keeping track of how much of the file was deleted, so it may not have ever shrinked - Maildir+NFS: Fixed skipping mails when moving files from new/ to cur/ - Maildir: We didn't notice if messages were directly deleted from new/

3 2

[Dovecot] imap corrupted indexes
by Emmett Pate 28 Jun '05

28 Jun '05

I've searched the archives and find a lot of references to corrupted indexes but can't seem to find any solutions. It seems like folks either have the problem or they don't. We recently migrated from a RedHat Linux server to an OpenBSD 3.7 server (both using dovecot). Imap was working flawlessly on the RedHat box but now gives numerous index errors. I then upgraded to dovecot-1.0-test66 compiled from ports - still no luck. Here's an example of the errors: Jun 27 12:02:23 mail dovecot: IMAP(epate): Corrupted transaction log file /home/epate/mail/.imap/INBOX/dovecot.index.log: Keyword record UIDs are broken Jun 27 12:02:24 mail dovecot: IMAP(epate): Lost transaction log file /home/epate/mail/.imap/INBOX/dovecot.index.log seq 7 I found references to "disabling indexing" but they don't say how. Would this be a reasonable temporary solution? Any other suggestions? Thanks for your help, Emmett Pate

3 3

[Dovecot] Sudden IMAP problem - UID Errors
by Jamie Heckford 28 Jun '05

28 Jun '05

Hi, We have quite happily been running dovecot with no issues at all for approx. two years now and have had no problem whatsoever. Great work :) BUT (there is always a but!).... yesterday one of our users started complaining that they were having issues with their mail. I checked and although they can still view their IMAP mailbox ok it constantly throws up error messages such as: "The UID of a message changed unexpectedly. This typically indicates a server bug. Your program may not function properly after this. MsgSeqNum 131: Previous UID: 21402, New UID: 21555 Protocol: IMAP" and "Your server has reported a UID which does not comply with the IMAP standard. This typically indicates a server bug. Your program may not function properly after this." This is using Outlook 2003 as the IMAP client, and is only affecting a single user. Server is dovecot-0.99.14 running on FreeBSD 4.9-RELEASE #1: Thu Apr 15 10:00:08 GMT 2004 Anybody seen this before or have any suggestions? Also is there a way I can make the logging more verbose as I only get info on date/user/ip when they login. I did see a --raw-log or similar compile flag, is this whats needed? I suspect this is Outlook being stupid and not dovecot though. Any help would be greatly received. Many thanks! -- Jamie Heckford Network Manager Trident Microsystems Ltd. t: +44(0)1737-780790 f: +44(0)1737-771908 w: http://www.trident-uk.co.uk/

2 2

[Dovecot] UID confusion
by Andrew Hutchings 28 Jun '05

28 Jun '05

Hi, 2 or 3 customers have reported that they are having problems downloading their mail via. POP3. I have attached the rawlogs of their transactions and the UID list at the time. Is this because I am using an incompatible UID format or is something else at fault? Deleting the UID list and indexes fixes the problem. I am using Test72. Regards Andrew -- Andrew Hutchings (A-Wing) - Linux Guru Netserve Consultants - http://www.domaincity.co.uk/ A-Wing Internet Services - http://www.a-wing.co.uk/ Random quote 148: "We had planned to integrate a Web browser with our operating system as far back as 1993" - Microsoft (27 Jul 1998, filing its first court responses to federal antitrust) STAT UIDL DELE 12 DELE 13 DELE 14 DELE 15 DELE 16 DELE 17 DELE 18 DELE 19 DELE 20 DELE 21 DELE 22 DELE 23 DELE 24 DELE 25 DELE 26 DELE 27 DELE 28 DELE 29 DELE 30 DELE 31 DELE 32 DELE 33 DELE 34 DELE 12 DELE 31 DELE 20 DELE 14 DELE 32 DELE 19 DELE 21 DELE 33 DELE 23 DELE 28 DELE 22 DELE 34 DELE 27 DELE 30 DELE 24 DELE 18 DELE 17 DELE 29 DELE 26 DELE 25 DELE 15 +OK 37 3133628 +OK 1 1102086912.6586 2 1102086912.6604 3 1102086912.6606 4 1102086912.6607 5 1102086912.6613 6 1102086912.6614 7 1102086912.6624 8 1102086912.6627 9 1102086912.6628 10 1102086912.6637 11 1102086912.6638 12 1102086912.6642 13 1102086912.6643 14 1102086912.6644 15 1102086912.6645 16 1102086912.6646 17 1102086912.6647 18 1102086912.6649 19 1102086912.6650 20 1102086912.6651 21 1102086912.6652 22 1102086912.6653 23 1102086912.6655 24 1102086912.6656 25 1102086912.6657 26 1102086912.6658 27 1102086912.6659 28 1102086912.6660 29 1102086912.6661 30 1102086912.6662 31 1102086912.6663 32 1102086912.6664 33 1102086912.6665 34 1102086912.6666 35 1102086912.6668 36 1102086912.6669 37 1102086912.6670 . +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Too many bad commands. 1 1102086912 6671 6586 1119365297.H428351P22768.svr34.nsnoc.com:2,S 6604 1119430792.H16069P15059.svr34.nsnoc.com:2,S 6606 1119435803.H269574P27211.svr34.nsnoc.com:2,S 6607 1119438782.H651475P11876.svr34.nsnoc.com:2,S 6613 1119444180.H435092P3752.svr34.nsnoc.com:2,S 6614 1119446623.H168979P14147.svr34.nsnoc.com:2,S 6624 1119519980.H840253P23730.svr34.nsnoc.com:2,S 6627 1119534126.H915877P9542.svr34.nsnoc.com:2,S 6628 1119534129.H58338P9545.svr34.nsnoc.com:2,S 6637 1119590807.H77202P16581.svr34.nsnoc.com:2,S 6638 1119594010.H314838P14558.svr34.nsnoc.com:2,S 6642 1119631309.H826676P15985.svr34.nsnoc.com:2,S 6643 1119634096.H108358P8422.svr34.nsnoc.com:2,S 6644 1119651249.H740483P15403.svr34.nsnoc.com:2,S 6645 1119652382.H85165P25444.svr34.nsnoc.com:2,S 6646 1119662861.H891233P15682.svr34.nsnoc.com:2,S 6647 1119666011.H343203P9515.svr34.nsnoc.com:2,S 6648 1119678421.H726408P9343.svr34.nsnoc.com:2,S 6649 1119682873.H656272P7774.svr34.nsnoc.com:2,S 6650 1119709610.H933163P23969.svr34.nsnoc.com:2,S 6651 1119711088.H95605P27225.svr34.nsnoc.com:2,S 6652 1119717756.H183955P3515.svr34.nsnoc.com:2,S 6653 1119726592.H247339P1807.svr34.nsnoc.com:2,S 6654 1119727779.H102401P8785.svr34.nsnoc.com:2,S 6655 1119749596.H731030P9216.svr34.nsnoc.com:2,S 6656 1119760115.H508676P14834.svr34.nsnoc.com:2,S 6657 1119761702.H762025P27895.svr34.nsnoc.com:2,S 6658 1119774991.H8003P28710.svr34.nsnoc.com:2,S 6659 1119780623.H432714P11671.svr34.nsnoc.com:2,S 6660 1119797027.H333204P330.svr34.nsnoc.com:2,S 6661 1119799332.H700308P15617.svr34.nsnoc.com:2,S 6662 1119800637.H600428P30602.svr34.nsnoc.com:2,S 6663 1119807991.H64209P14572.svr34.nsnoc.com:2,S 6664 1119808834.H473596P22065.svr34.nsnoc.com:2,S 6665 1119838893.H830072P23165.svr34.nsnoc.com:2,S 6666 1119838934.H873217P23186.svr34.nsnoc.com:2,S 6667 1119860409.H899984P26859.svr34.nsnoc.com:2, 6668 1119860596.H249033P27907.svr34.nsnoc.com 6669 1119867953.H904781P22645.svr34.nsnoc.com 6670 1119867978.H374439P22691.svr34.nsnoc.com

2 4

[Dovecot] getpeername() and SSL
by Andreas Goertz 28 Jun '05

28 Jun '05

Hi Timo, first of all: i'm using 0.99.14. You helped me to raw-log the client-IP using something like this in rawlog.c: if (net_getpeername(0, &ip, NULL) == 0) { str = t_strdup_printf("IP: %s\n", net_ip2addr(&ip)); write_full(log_out, str, strlen(str)); } Now i got the problem, that this doesn't work when the client is connected using SSL. After some testing i think, the problem is, that after calling net_getpeername() the ip-family is AF_UNIX, not AF_INET, so net_ip2addr() returns null, but i'm not sure ;-) And i have no clue, how to solve this and find out the ip... Do you have another hint for me? Thanks in advance. Regards, Andreas.

2 2

[Dovecot] Blank messages and problems starting Dovecot
by Lars Karset Grimsrud 28 Jun '05

28 Jun '05

When I use Evolution for viewing my e-mail and display full headers, no content is shown. The number of messages indicated in Evolution is however correct. Logging into webmail (Squirrelmail) doesn't work either, saying "Error connecting to IMAP server: localhost. 13 : Permission denied". I have verified that ~/Maildir/new actually contains valid e-mails. Does anyone have suggestions on how to debug this problem? A connection is established if I telnet. I use Fedora Core 4. Another problem I have, is changing log_path and info_log_path to something useful. If I change either to i.e. /tmp/dovecot.log, dovecot refuses to start (service dovcot restart) with noe error message. If it helps, my /etc/dovecot.conf is here: http://www.stud.ntnu.no/~grimsrud/info/dovecot.conf.txt -- Lars Karset Grimsrud <grimsrud(a)stud.ntnu.no>

2 1

[Dovecot] password scheme
by Nathalie Boulos 28 Jun '05

28 Jun '05

Hi, I have dovecot-0.99.11-1.FC3.4 running on fedora core 3, and authenticating with openLDAP on a remote server. When i try to authenticate, i get the error "Unknown password scheme SSHA". I read that earlier on this mailing list, SSHA was not suported by dovecot. Is it supported now? what should i do to make my password authentication work? The users in the openLDAP database have userPassword {SHA} already used by other services, so i cannot change them. Any suggestions? Regards, Nathalie ____________________________________________________ Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.yahoo.com

2 1

[Dovecot] LF not found where expected
by Miles Mawyer 28 Jun '05

28 Jun '05

I'm using Dovecot 0.99.13 on a fedora core 3 server. I keep getting these errors from time to time. There user ends up retrieving no mail (but no error in their client, be it web mail or pop3 client) What usually fixes it is this procedure: Cp mbox file to mbox_ Remove original mbox Send a test message to recreate mbox. Cat mbox_ >> mbox Problem solved! Can anybody tell me what causes this? pop3(mjmurray): Jun 27 11:16:38 Error: Error indexing mbox file /var/mail/mjmurray: LF not found where expected pop3(mjmurray): Jun 27 11:16:38 Error: Error indexing mbox file /var/mail/mjmurray: LF not found where expected pop3(mjmurray): Jun 27 11:16:38 Error: Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-06-27 11:16:38] pop3-login: Jun 27 11:17:06 Info: Login: mjmurray [64.203.167.125] pop3(mjmurray): Jun 27 11:17:06 Error: Error indexing mbox file /var/mail/mjmurray: LF not found where expected pop3(mjmurray): Jun 27 11:17:06 Error: Error indexing mbox file /var/mail/mjmurray: LF not found where expected pop3(mjmurray): Jun 27 11:17:06 Error: Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-06-27 11:17:06] imap-login: Jun 27 11:17:28 Info: Login: mjmurray [127.0.0.1] imap(mjmurray): Jun 27 11:17:28 Error: Error indexing mbox file /var/mail/mjmurray: LF not found where expected imap(mjmurray): Jun 27 11:17:28 Error: Error indexing mbox file /var/mail/mjmurray: LF not found where expected imap-login: Jun 27 11:19:12 Info: Login: mjmurray [127.0.0.1] imap(mjmurray): Jun 27 11:19:12 Error: Error indexing mbox file /var/mail/mjmurray: LF not found where expected imap(mjmurray): Jun 27 11:19:12 Error: Error indexing mbox file /var/mail/mjmurray: LF not found where expected ... Miles Mawyer -=- Webmaster . Centralva.net ... ... mmawyer(a)rosecomputers.com ... ... 434.385.5053 ...

2 1

[Dovecot] possible bug with incoming mail
by Luke Ehresman 28 Jun '05

28 Jun '05

I've been using Dovecot for a couple months now and am very impressed. Thanks for a great package. However, I have noticed a problem that I haven't been able to solve. When a new message comes into my inbox, the last message that was received is marked as new as well as the new one. I originally thought this was a bug in my client (mutt) but I have verified that the same thing happens with Thunderbird, Sylpheed, mutt, and pine. My configuration is as follows: ------------------------------- using mbox: default_mail_env = mbox:/var/spool/vfolders/%d/%n:INBOX=/var/spool/vmail/%d/%n using imaps Linux version 2.6.11-hardened-r1 (root@gondor) (gcc version 3.3.5 (Gentoo Linux 3.3.5-r1, ssp-3.3.2-3, pie-8.7.7.1)) #2 Thu May 5 13:14:52 EDT 2005 Thanks for any help you can give, Luke

3 3

[Dovecot] Dovecot + MySQL no auth
by Dylan Baxter 28 Jun '05

28 Jun '05

I haven't been able to login to my mail server using MySQL authentication and I believe I've found the issue. My POP log says: dovecot: Jun 07 09:58:56 Error: auth(default): sql(dylan(a)domain.com,127.0.0.1): Password query must return a field named "password" dovecot: Jun 07 09:58:56 Info: pop3-login: Disconnected [127.0.0.1] The password field in MySQL is called "passwd". Am I to understand that there is no way around this? I must rename the field to "password"? My config files all check out. I'm pretty sure I'm at a road block here. Any help would be greatly appreciated. Also, aren't there anough Dovecot users to warrant a forum and/or IRC channel? I cant seem to find either (but thank you for the mailing list!). Thanks all for any help! Dylan

4 4

[Dovecot] Restrictions on User Basis
by Net Cerebrum 28 Jun '05

28 Jun '05

Hi, I am running dovecot on Fedora Linux in our organization and use IMAP as well as POP3 protocols for mail retrieval. I want to impose the following user based restrictions: (a) I want to permit only selective users to access either POP3 or IMAP server or both. (b) The server can be accessed from LAN as well as WAN. However I want to allow only selective users to be able to access POP3 or IMAP server from the WAN side (or on the basis of IP addresses). What do I need to do to impose these restrictions ? Thanks,

3 2

[Dovecot] APPEND issue with Thunderbird
by Todd Burroughs 28 Jun '05

28 Jun '05

I'm getting a strange problem with APPEND and Thunderbird 0.8. This was working fine in the CVS version from June 8 and is not so fine as of June 20. It works fine using Pine. It appears that imap is hanging when trying to append to a folder. Right now, an imap process has the file open for about 1/2 hour. It wrote the headers out, but not the body. When Thunderbird disconnects from it, it closes the file, but does not finish writing the email. Here's the difference in the commands sent by Pine and Thunderbird from rawlogs. These are different accounts. (Thunderbird) (.in file) 2 append "Sent" (\Seen) {520+} Message-ID: <42BAC447.7050901(a)hostopia.com> (rest of headers and message follows) The .out file is empty --------------------------------------- (Pine) (.in file) 00000003 CAPABILITY 03000004 APPEND Sent {392} Date: Wed, 22 Jun 2005 19:35:42 -0400 (EDT) (rest of headers and message follows) 03000005 LOGOUT (.out file) * OK [RAWLOG TIMESTAMP] 2005-06-22 19:36:20 * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS 00000003 OK Capability completed. + OK 03000004 OK Append completed. * BYE Logging out 03000005 OK Logout completed. ----------------------------------------- Todd

3 2

[Dovecot] IP Based Access
by kasharif＠citech-bd.com 28 Jun '05

28 Jun '05

Hi, Can someone tell me how can I restrict 110 port access other than my IP block? if it through tcp-wrapper then how can i do that? Thanking Sharif

5 5

[Dovecot] FAM support?
by Michael Tibben 28 Jun '05

28 Jun '05

Hi, Is there any planned support for FAM http://oss.sgi.com/projects/fam/ in dovecot? One of my favourite features of Courier IMAP server is that it alerts my email client through IMAP when email has arrived. Regards, Mick

3 4

[Dovecot] pop3 retr error
by Marten Lehmann 28 Jun '05

28 Jun '05

Hello, I'm getting the following error while Mozilla Mail is downloading >4000 emails: The RETR command did not succeed. Error retrieving message. Mail server xxx responded: Message is deleted. So what's the error? Can't I retrieve a message, that has been marked as deleted before? If the Mesage-ID wouldn't exist, the error message would be different. I don't know what Mozilla Mail is doing and on which message id it is failing. Also, there's no output in the logfiles. Any ideas? Regards Marten

5 15

[Dovecot] quetion about duplicate messages
by Michiel van Es 28 Jun '05

28 Jun '05

Hi, we recently switched from Imap-Uw to Dovecot as a pop3 server. I was wondering why people who have the flag 'Leave messages on server' in their email client (Outlook, Outlook Expres) that they receive duplicates of their stored mail? Is it because Dovecot doesn't know that the messages has already been popped by Imap Uw or is the email client which thinks there are new messages on the server and if so..how can I avoid this behaviour? Thanks in advance for any help. -- Kind Regards, Michiel

2 1

[Dovecot] dovecot and solaris 9
by Sander 26 Jun '05

26 Jun '05

Hi, Does anyone know where to find a how-to to get dovecot working with Solaris. Specifically how to setup plain authentication? Thanks in advance, Sander

2 1

[Dovecot] Dovecot 1.0
by Jeff Graves 24 Jun '05

24 Jun '05

Either Timo's got most of the bugs worked out or everyone is on vacation this week (traffic on the list has been very light). Good Job! Jeff Graves, MCSA Customer Support Engineer Image Source, Inc. 10 Mill Street Bellingham, MA 02019 508.966.5200 - Phone 508.966.5170 - Fax jeff(a)image-src.com - Email www.image-src.com

1 0

[Dovecot] [newbie question]to receive mail
by neo anderson 23 Jun '05

23 Jun '05

sorry, i forget to attach the result that run by mail command. the "mail" command i use it shows the mail as follow: ========== mail command beg 12 mail-user(a)[xxx.xxx.xxx.xxx Thu Jun 23 11:21 48/1478 "this is a test mail" ========== mail command end ___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com

1 0

[Dovecot] [newbie question]to receive mail
by neo anderson 23 Jun '05

23 Jun '05

hi, i'm newbie to dovecot. lately i install postfix on a server for providing mail service. however, i encounter a problem in receiving mail, i.e., to get mail download to the remote client. (i'm able to send mail through mozilla client, but can't get the sent mail download to the client). what reasons may cause such problem? check several points that i suppose it may have problem, yet can't figure out where the problem may be resulted from. for instance, ========== telnet beg telnet target-server-ip 143 ... * OK dovecot ready. telnet target-server-ip 25 ... 220 host-name.domain.com ESMTP Postfix (ehlo localhost) <---------- hidden command i enter 250-host-name.domain.com 250-PIPELINING 250-SIZE 20971520 250-VRFY 250-ETRN 250-AUTH LOGIN GSSAPI DIGEST-MD5 CRAM-MD5 PLAIN 250-AUTH=LOGIN GSSAPI DIGEST-MD5 CRAM-MD5 PLAIN 250 8BITMIME (quit) <---------- hidden command i enter 221 Bye telnet target-server-ip 110 .... +OK dovecot ready ========== telnet end btw, i'm able to read and write mail through mail program in the target server; simply can't get the mail downloaded to the other client with mozilla mail client (out look also doesn't work). mozilla mail client is version 1.7 . target server using centos 4.0. postfix 2.1.5 dovecot-0.99.11-2.EL4.1 i appreciate any help, sincerely. ___________________________________________________________ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com

1 0

[Dovecot] miugrating mail to new server
by Gabe Granger 22 Jun '05

22 Jun '05

Hi All, I've just a new server to help with migration of our email, the old email server is using mbox and the new is using Maildir. I've managed to some user mail migrated fine. The new server is only a temp server as I have too many users to migrate easily in one go(Also I want to nuke the current mailserver, remove SuSE and install Debian on it). So what i'm doing it moving users one by one to temp server and converting to Maildir. My question is. I notice that all email files in maildir format end with .<host> when I go to migrate everything to back over to the original server is this going to cause me problem? Ie will the original server now have to be named the same as the temp server so that the maildir format files end with the same .<host> or does that not matter? Any help, advise would be great. Gabe

2 1

[Dovecot] question about
by Michiel van Es 22 Jun '05

22 Jun '05

Hi, I am running Dovecot (dovecot-0.99.11-2.EL4.1 on centos 4) and we are switching from newer machines. I copied all usernames from /etc/passwd,/etc/group and /etc/shadow to the new machine. I do not want that every user has it's own /home/$user directory.. When I test my dovecot installation with a telnet 'servername' 110 user test pass test I get this error: ################################################################################ Jun 20 13:22:47 mx01 pop3(aaptest): mbox: Can't create root IMAP folder /home/aaptest/mail: Permission denied Jun 20 13:22:47 mx01 pop3(aaptest): MAIL environment missing and autodetection failed (home /home/aaptest) Jun 20 13:22:47 mx01 dovecot: child 3393 (pop3) returned error 89 ############################################################################## So I changed the MAIL environment to /var/spool/mail (using Sendmail and mbox) Now I get this error: ###############################################################################3 Jun 20 13:27:37 mx01 pop3-login: Login: aaptest [::ffff:10.101.3.37] Jun 20 13:27:37 mx01 pop3(aaptest): open(/var/spool/mail//inbox, O_CREAT) failed: Permission denied Jun 20 13:27:37 mx01 pop3(aaptest): mkdir_parents(/var/spool/mail//.imap/INBOX) failed: Permission denied ################################################################################# Wht is Dovecot trying to AUTOcreate IMAP folders? I do not want Dovecot to do this hence I tell Dovecot to serve only pop3 and pop3s: # imap imaps pop3 pop3s protocols = pop3 pop3s # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. You can specify ports with # "host:port". #imap_listen = [::] pop3_listen = [::] Does anyone know how I can dissable this IMAP-AUTOcreate behaviour? Thanks in advance. Michiel

4 9