- dovecot - dovecot.org

Re: [Dovecot] [dovecot] IMAP basics
by Paul Scott 30 May '07

30 May '07

Picking up a broken thread after gettin exim4 to send my mail out. version 1.0.0 on Debian sid: I now have fetchmail delivering three POP mailboxes to my Maildir. How do I tell Dovecot about this mail? TIA, Paul Scott

1 0

Re: [Dovecot] Dovecot] dovecot performance question
by Kenny Dail 30 May '07

30 May '07

> Hi, using the latest dovecot with pop3/imap. Using mostly outlook 2003 for > pop3 and squirrel mail imap. > > I have a lot of users reporting back that imap is very slow. We average > about 300 imap and another 700 pop session at any given time. reporting that imap is slow or that squirrelmail is slow? ;) How is the load average on the server? We found at our site to keep Apache/squirrelmail happy, we dedicated a server for our webmail users. Mostly being a RAM issue in that case. Just how beefy is the server you are using? > I am having a time issue on this server and im not sure if its affecting > dovecot. > > May 29 11:42:19 pop dovecot: POP3(xxx): Time just moved backwards by 1 > seconds. I'll sleep now until w > e're back in present. > May 29 11:42:19 pop dovecot: POP3(xxx): Time just moved backwards by 1 > seconds. I'll sleep now until w > e're back in present. > May 29 11:42:31 pop dovecot: POP3(xxx): Time just moved backwards by 1 > seconds. I'll sleep now until w > e're back in present. > May 29 11:42:42 pop dovecot: POP3(xxx): Time just moved backwards by 1 > seconds. I'll sleep now until w > e're back in present. It'll affect it in that you will be having 1 sec delays frequently it seems. You should definitely look into fixing that. That is bad behavior for a busy mail server. -- Kenny Dail <kend(a)amigo.net>

2 1

[Dovecot] namespace problem
by Rainer Sigl 29 May '07

29 May '07

Hi all, after an update from dovecot beta version to 1.0.0.-1 today morning I had different effects: thunderbird-, kmail-, Apple-clients, pine and squirrelmail could receive email correct with imaps. But not MSOutlook!!! Varying the namespace configurations in dovecot.conf I got different results with MSOutlook working but with thunderbird, squirrelmail etc. all folders are displayed but not the root Inbox etc. Its important to know that I migrated from courier-imap to dovecot. My well working namespace config BEFORE upgrade to 1.0.0-1: namespace private { #separator = / prefix = INBOX. # prefix = inbox = yes #hidden = yes } #the second namespace I need to work with Apple because they use / namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } Here my actual namespace configs: namespace private { separator = prefix = INBOX. inbox = no hidden = no } namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } namespace private { separator = . prefix = INBOX. inbox = yes hidden = yes } In varying inbox and hidden keywords I found this configuration. Most things are working with this but in squirrelmal I can't access inbox, the main folder. How do I have to configure that everythings works satisfying?? Many thanks Rainer Sigl [0]root@mpemail:/etc/dovecot# dovecot -n # /etc/dovecot/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps pop3s ssl_cert_file: /etc/ssl/certs/mpemail.pem ssl_key_file: /etc/ssl/private/mpemail-key.pem login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_chroot: no verbose_proctitle: yes mail_extra_groups: mail default_mail_env: maildir:/home/virtual_mail/%u mail_location: maildir:/home/virtual_mail/%u mail_debug: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): UID%u-%v namespace: type: private prefix: INBOX. namespace: type: private separator: / prefix: INBOX/ hidden: yes namespace: type: private separator: . prefix: INBOX. inbox: yes hidden: yes auth default: passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: static args: uid=1002 gid=1002 home=/home/virtual_mail/%u userdb: driver: passwd userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf -- ----------------- Rainer Sigl, | email: sigl(a)mpe.mpg.de MPI f. extraterrestrische Physik, | phone: +49 (89) 30000-3557 Postfach 1312, | fax: +49 (89) 30000-3569 D-85741 Garching, Germany | web: http://www.mpe.mpg.de/~sigl/

1 0

[Dovecot] Namespace Problems repost without attachment
by Rainer Sigl 29 May '07

29 May '07

Hi all, after an update from dovecot beta version to 1.0.0.-1 today morning I had different effects: thunderbird-, kmail-, Apple-clients, pine and squirrelmail could receive email correct with imaps. But not MSOutlook!!! Varying the namespace configurations in dovecot.conf I got different results with MSOutlook working but with thunderbird, squirrelmail etc. all folders are displayed but not the root Inbox etc. Its important to know that I migrated from courier-imap to dovecot. My well working namespace config BEFORE upgrade to 1.0.0-1: namespace private { #separator = / prefix = INBOX. # prefix = inbox = yes #hidden = yes } #the second namespace I need to work with Apple because they use / namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } Here my actual namespace configs: namespace private { separator = prefix = INBOX. inbox = no hidden = no } namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } namespace private { separator = . prefix = INBOX. inbox = yes hidden = yes } In varying inbox and hidden keywords I found this configuration. Most things are working with this but in squirrelmal I can't access inbox, the main folder. How do I have to configure that everythings works satisfying?? Many thanks Rainer Sigl -- ----------------- Rainer Sigl, | email: sigl(a)mpe.mpg.de MPI f. extraterrestrische Physik, | phone: +49 (89) 30000-3557 Postfach 1312, | fax: +49 (89) 30000-3569 D-85741 Garching, Germany | web: http://www.mpe.mpg.de/~sigl/

1 0

[Dovecot] Namespace Problems
by Rainer Sigl 29 May '07

29 May '07

Hi all, after an update from dovecot beta version to 1.0.0.-1 today morning I had different effects: thunderbird-, kmail-, Apple-clients, pine and squirrelmail could receive email correct with imaps. But not MSOutlook!!! Varying the namespace configurations in dovecot.conf I got different results with MSOutlook working but with thunderbird, squirrelmail etc. all folders are displayed but not the root Inbox etc. Its important to know that I migrated from courier-imap to dovecot. My well working namespace config BEFORE upgrade to 1.0.0-1: namespace private { #separator = / prefix = INBOX. # prefix = inbox = yes #hidden = yes } #the second namespace I need to work with Apple because they use / namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } Here my actual namespace configs: namespace private { separator = prefix = INBOX. inbox = no hidden = no } namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } namespace private { separator = . prefix = INBOX. inbox = yes hidden = yes } In varying inbox and hidden keywords I found this configuration. Most things are working with this but in squirrelmal I can't access inbox, the main folder. How do I have to configure that everythings works satisfying?? dovecot.conf and dovecot-sql.conf I send in the attachment. Many thanks Rainer Sigl -- ----------------- Rainer Sigl, | email: sigl(a)mpe.mpg.de MPI f. extraterrestrische Physik, | phone: +49 (89) 30000-3557 Postfach 1312, | fax: +49 (89) 30000-3569 D-85741 Garching, Germany | web: http://www.mpe.mpg.de/~sigl/ -- ----------------- Rainer Sigl, | email: sigl(a)mpe.mpg.de MPI f. extraterrestrische Physik, | phone: +49 (89) 30000-3557 Postfach 1312, | fax: +49 (89) 30000-3569 D-85741 Garching, Germany | web: http://www.mpe.mpg.de/~sigl/ ## Dovecot 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 protocols = 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. If you want to specify ports # for each service, you will need to configure these settings inside the # protocol imap/pop3 { ... } section, so you can specify different ports # for IMAP/POP3. #listen = * # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = # Disable SSL/TLS support. #ssl_disable = no # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. #ssl_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem #ssl_key_file = /etc/ssl/private/ssl-cert-snakeoil.key ssl_cert_file = /etc/ssl/certs/mpemail.pem ssl_key_file = /etc/ssl/private/mpemail-key.pem # If key file is password protected, give the password here. Alternatively # give it when starting dovecot with -p parameter. #ssl_key_password = # File containing trusted SSL certificate authorities. Usually not needed. #ssl_ca_file = # Request client to send a certificate. #ssl_verify_client_cert = no # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 168 # SSL ciphers to use #ssl_cipher_list = ALL:!LOW # 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 = /var/log/dovecot.log # For informational messages, use this logfile instead of the default info_log_path = /var/log/dovecot-info.log # Prefix for each line written to log file. % codes are in strftime(3) # format. log_timestamp = "%Y-%m-%d %H:%M:%S " # Syslog facility to use if you're logging to syslog. Usually if you don't # want to use "mail", you'll use local0..local7. Also other standard # facilities are supported. #syslog_facility = mail ## ## 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 = no # 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_connection 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_connection # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 # Greeting message for clients. #login_greeting = Dovecot ready. # Space-separated list of elements we want to log. The elements which have # a non-empty variable value are joined together to form a comma-separated # string. #login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c # Login log format. %$ contains login_log_format_elements string, %s contains # the data we want to log. #login_log_format = %$: %s ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). verbose_proctitle = yes # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. mail_extra_groups = mail # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See # /usr/share/doc/dovecot-common/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden 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 = 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 # /usr/share/doc/dovecot-common/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 /usr/share/doc/dovecot-common/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 = maildir:/home/virtual_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 { separator = prefix = INBOX. inbox = no hidden = no } namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } namespace private { separator = . prefix = INBOX. inbox = yes hidden = yes } #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 = INBOX/ # 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 = no # 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: # Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # # flags, date.sent, date.received, size.virtual, size.physical # mime.parts, imap.body, imap.bodystructure # # Different IMAP clients work in different ways, so they benefit from # different cached fields. Some do not benefit from them at all. Caching more # than necessary generates useless disk I/O, so you don't want to do that # either. # # Dovecot attempts to automatically figure out what client wants and it keeps # only that. However the first few times a mailbox is opened, Dovecot hasn't # yet figured out what client needs, so it may not perform optimally. If you # know what fields the majority of your clients need, it may be useful to set # these fields by hand. If client doesn't actually use them, Dovecot will # eventually drop them. # # Usually you should just leave this field alone. The potential benefits are # typically unnoticeable. #mail_cache_fields = # Space-separated list of fields that Dovecot should never save to cache file. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # The minimum number of mails in a mailbox before updates are done to cache # file. This allows optimizing Dovecot's behavior to do less disk writes at # the cost of more disk reads. #mail_cache_min_mail_count = 0 # When IDLE command is running, mailbox is checked once in a while to see if # there are any new mails or other changes. This setting defines the minimum # time to wait between those checks. Dovecot is however able to use dnotify # and inotify with Linux to reply immediately after the change occurs. #mailbox_idle_check_interval = 30 # 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. # Also note that if other software reads the mboxes/maildirs, they may handle # the extra CRs wrong and cause problems. #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. NOTE: If you use NFS, remember to change also mmap_disable setting! # Solaris doesn't support flock, so Solaris users need to change this to fcntl. #lock_method = flock # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Which locking methods to use for locking mbox. There's four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist in all systems. Doesn't work with NFS. # # You can use multiple locking methods; if you do the order they're declared # in is important to avoid deadlocks if other MTAs/MUAs are using multiple # locking methods as well. Some operating systems don't allow using some of # them simultaneously. #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # When mbox changes unexpectedly we have to fully read it to find out what # changed. If the mbox is large this can take a long time. Since the change # is usually just a newly appended mail, it'd be faster to simply read the # new mails. If this setting is enabled, Dovecot does this but still safely # fallbacks to re-reading the whole mbox file whenever something in mbox isn't # how it's expected to be. The only real downside to this setting is that if # some other MUA changes message flags, Dovecot doesn't notice it immediately. # Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK # commands. #mbox_dirty_syncs = yes # Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE, # EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored. #mbox_very_dirty_syncs = no # Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK # commands and when closing the mailbox). This is especially useful for POP3 # where clients often delete all mails. The downside is that our changes # aren't immediately visible to other MUAs. #mbox_lazy_writes = yes # If mbox size is smaller than this (in kilobytes), don't write index files. # If an index file already exists it's still read, just not updated. #mbox_min_index_size = 0 # Maximum dbox file size in kilobytes until it's rotated. #dbox_rotate_size = 2048 # Minimum dbox file size in kilobytes before it's rotated # (overrides dbox_rotate_days) #dbox_rotate_min_size = 16 # Maximum dbox file age in days until it's rotated. Day always begins from # midnight, so 1 = today, 2 = yesterday, etc. 0 = check disabled. #dbox_rotate_days = 0 # 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 # /usr/share/doc/dovecot-common/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/lib/dovecot/imap-login # IMAP executable location. Changing this allows you to execute other # binaries before the imap process is executed. # # This would write rawlogs into ~/dovecot.rawlog/ directory: # mail_executable = /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap # # This would attach gdb into the imap process and write backtraces into # /tmp/gdbhelper.* files: # mail_executable = /usr/lib/dovecot/gdbhelper /usr/lib/dovecot/imap # #mail_executable = /usr/lib/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/modules/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. # The list is space-separated. #imap_client_workarounds = outlook-idle } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. #login_executable = /usr/lib/dovecot/pop3-login # POP3 executable location #mail_executable = /usr/lib/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 # Older Dovecots : %v.%u # # Note that Outlook 2003 seems to have problems with %v.%u format which was # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. # # NOTE: Nowadays this is required to be set explicitly, since the old # default was bad but it couldn't be changed without breaking existing # installations. %08Xu%08Xv will be the new default, so use it for new # installations. # pop3_uidl_format = UID%u-%v # 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/modules/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. # oe-ns-eoh: # Outlook Express and Netscape Mail breaks if end of headers-line is # missing. This option simply sends it if it's missing. # The list is space-separated. #pop3_client_workarounds = } ## ## dovecot-lda specific settings ## # protocol lda { # If you wish to use plugins you need to specify plugin directory # For example quota enforcing is implemented by plugin #module_dir = /usr/local/lib/dovecot/lda # Address from LDA should send MDNs like out of quota # postmaster_address = postmaster(a)your.dom # If there is no user-specific Sieve-script, global Sieve script is # executed if set. #global_script_path = # UNIX socket path to master authentication server to find users. #auth_socket_path = /var/run/dovecot-auth-master # } ## ## Authentication processes ## # Executable location #auth_executable = /usr/lib/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # Authentication cache size in kilobytes. 0 means it's disabled. # Note that bsdauth, PAM and vpopmail require cache_key to be set for caching # to be used. Also note that currently auth cache doesn't work very well if # you're using multiple passdbs with same usernames in them. #auth_cache_size = 0 # Time to live in seconds for cached data. After this many seconds the cached # record is no longer used, *except* if the main database lookup returns # internal failure. #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 # In case of password mismatches, log the passwords and used scheme so the # problem can be debugged. Requires auth_debug=yes to be set. #auth_debug_passwords = 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 # Kerberos keytab to use for the GSSAPI mechanism. Will use the system # default (usually /etc/krb5.keytab) if not specified. #auth_krb5_keytab = auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous gssapi # mechanisms = plain userdb static { args = uid=1002 gid=1002 home=/home/virtual_mail/%u } # passdb passwd-file { # args = /etc/passwd # } ## ## dovecot-lda specific settings ## # socket listen { # master { # path = /var/run/dovecot-auth-master # mode = 0600 # user = vmail # User running Dovecot LDA # #group = mail # Or alternatively mode 0660 + LDA user in this group # } # } # # 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 # # Users can be temporarily disabled by adding a passdb with deny=yes. # If the user is found from that database, authentication will fail. # The deny passdb should always be specified before others, so it gets # checked first. Here's an example: #passdb passwd-file { # File contains a list of usernames, one per line #args = /etc/dovecot.deny #deny = yes #} # PAM authentication. Preferred nowadays by most systems. # Note that PAM can only be used to verify if user's password is correct, # so it can't be used as userdb. If you don't want to use a separate user # database (passwd usually), you can use static userdb. # passdb pam { # [session=yes] [cache_key=<key>] [<service name>] # # session=yes makes Dovecot open and immediately close PAM session. Some # PAM plugins need this to work, such as pam_mkhomedir. # # cache_key can be used to enable authentication caching for PAM # (auth_cache_size also needs to be set). It isn't enabled by default # because PAM modules can do all kinds of checks besides checking password, # such as checking IP address. Dovecot can't know about these checks # without some help. cache_key is simply a list of variables (see # /usr/share/doc/dovecot-common/variables.txt) which must match for the # cached data to be used. # Here are some examples: # %u - Username must match. Probably sufficient for most uses. # %u%r - Username and remote IP address must match. # %u%s - Username and service (ie. IMAP, POP3) must match. # # If service name is "*", it means the authenticating service name # is used, eg. pop3 or imap. # # Some examples: # args = session=yes * # args = cache_key=%u dovecot #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 { #} # BSD authentication. Used by at least OpenBSD. #passdb bsdauth { # [cache_key=<key>] - See cache_key in PAM for explanation. #args = #} # passwd-like file with specified location #passdb passwd-file { # Path for passwd-file #args = #} # checkpassword executable authentication # NOTE: You will probably want to use "userdb prefetch" with this. #passdb checkpassword { # Path for checkpassword binary #args = #} # SQL database passdb sql { # Path for SQL configuration file, see /etc/dovecot/dovecot-sql.conf for # example args = /etc/dovecot/dovecot-sql.conf } # LDAP database #passdb ldap { # Path for LDAP configuration file, see /etc/dovecot/dovecot-ldap.conf for # example #args = #} # vpopmail authentication #passdb vpopmail { # [cache_key=<key>] - See cache_key in PAM for explanation. #args = #} # # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # # http://wiki.dovecot.org/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:/home/%u/mail nice=10 # #args = #} # SQL database userdb sql { # Path for SQL configuration file, see /etc/dovecot/dovecot-sql.conf for # example args = /etc/dovecot/dovecot-sql.conf } # LDAP database #userdb ldap { # Path for LDAP configuration file, see /etc/dovecot/dovecot-ldap.conf for # example #args = #} # vpopmail #userdb vpopmail { #} # "prefetch" user database means that the passdb already provided the # needed information and there's no need to do a separate userdb lookup. # This can be made to work with SQL and LDAP databases, see their example # configuration files for more information how to do it. # http://wiki.dovecot.org/AuthSpecials #userdb prefetch { #} # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # 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 # Take the username from client's SSL certificate, using X509_NAME_oneline() # which typically uses subject's Distinguished Name. #ssl_username_from_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 pam { # } # userdb passwd { # } # socket listen { # master { # path = /var/run/dovecot-auth-master # # WARNING: Giving untrusted users access to master socket may be a # # security risk, don't give too wide permissions to it! # #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 # } # } #} plugin { # Here you can give some extra environment variables to mail processes. # This is mostly meant for passing parameters to plugins. %variable # expansion is done for all values. # Quota plugin #quota = dirsize:%h/mail # Convert plugin. If set, specifies the source storage path which is # converted to destination storage (default_mail_env). #convert_mail = mbox:%h/mail }

2 1

[Dovecot] Migration from tpop3d to dovecot - troubles galore!
by Odhiambo WASHINGTON 29 May '07

29 May '07

Hi people, I am trying to migrate some users from tpop3d (Maildir mailboxes) to dovecot. The most important aspect of this migration, and which I cannot seem to get right, is to first be able to make dovecot to authenticate against the current DB being used by tpop3d so that I can use imapsync to transfer the user mails. And I do believe that is what I am unable to get right!! So here goes what I have tried so far: Take a case of one username, eddie, who belongs to the domain, demo.wananchi.com. 1. This query is what I am using for password_query. I do suspect it is wrong, but well, this is what it yields from the current DB: mysql> SELECT CONCAT(domain.path, '/', popbox.mbox_name), popbox.password_hash FROM popbox, domain WHERE popbox.local_part = 'eddie' AND popbox. domain_name = 'demo.wananchi.com' AND popbox.domain_name = domain.domain_name; +--------------------------------------------+---------------------------------------+ | CONCAT(domain.path, '/', popbox.mbox_name) | password_hash | +--------------------------------------------+---------------------------------------+ | /var/spool/virtual/demo.wananchi.com/eddie | {md5}897fad9cbef974ff95254417234ff1df | +--------------------------------------------+---------------------------------------+ 2. This is what I use for user_query and the result: mysql> SELECT CONCAT(domain.path, '/', popbox.mbox_name) as home, 6 as uid, 6 as gid FROM popbox, domain WHERE popbox.local_part = 'eddie' AND popbox.domain_name = 'demo.wananchi.com' AND popbox.domain_name = domain.domain_name; +-------------------------------------------------+-----+-----+ | home | uid | gid | +-------------------------------------------------+-----+-----+ | /var/spool/virtual/nyerimunicipal.co.ke/eddie | 6 | 6 | +-------------------------------------------------+-----+-----+ 3. Getting a typical user would need this query, for example: mysql> select CONCAT(local_part,'\@',domain_name) as user from popbox limit 10; +-------------------------+ | user | +-------------------------+ | eddie(a)demo.wananchi.com | +-------------------------+ 4. My tables, and the data they contain: (a) mysql> desc popbox; +----------------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +----------------+--------------+------+-----+---------+-------+ | domain_name | varchar(255) | | PRI | | | | local_part | varchar(255) | | PRI | | | | password_hash | varchar(255) | YES | | NULL | | | mbox_name | varchar(255) | YES | | NULL | | | password_hash2 | varchar(255) | YES | | NULL | | +----------------+--------------+------+-----+---------+-------+ (b) mysql> select * from popbox limit 1; +-------------------+------------+---------------------------------------+-----------+----------------+ | domain_name | local_part | password_hash | mbox_name | password_hash2 | +-------------------+------------+---------------------------------------+-----------+----------------+ | demo.wananchi.com | eddie | {md5}7bb1be8a78498a9de40098a593199819 | eddie | 9IYjWHc4Cs9/w | +-------------------+------------+---------------------------------------+-----------+----------------+ PS: Not all users have password_hash2, which I think is Unix crypt!!! (c) mysql> desc domain; +---------------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +---------------+--------------+------+-----+---------+-------+ | domain_name | varchar(255) | | PRI | | | | unix_user | varchar(255) | YES | | NULL | | | password_hash | varchar(255) | YES | | NULL | | | path | varchar(255) | YES | | NULL | | | max_popbox | int(11) | YES | | NULL | | +---------------+--------------+------+-----+---------+-------+ (d) mysql> select * from domain limit 1; +--------------+-----------+---------------------------------------+--------------------------------------+-----------------+ | domain_name | unix_user | password_hash | path | max_popbox | +--------------+-----------+---------------------------------------+--------------------------------------+-----------------+ | dlsnovit.org | exim | {md5}d108219901e577db69c249645ae3a49f | /var/spool/virtual/demo.wananchi.com | 5 | +--------------+-----------+---------------------------------------+--------------------------------------+-----------------+ [root@ns2]#less /var/log/dovecot.log dovecot: May 29 17:42:57 Warning: Killed with signal 15 dovecot: May 29 17:42:59 Info: Dovecot v1.0.0 starting up dovecot: May 29 17:42:59 Info: auth-worker(default): mysql: Connected to localhost (virtualemail) dovecot: May 29 17:44:02 Info: auth(default): client in: AUTH 1 PLAIN service=POP3 secured lip=62.8.64.4 rip=62.8.64.4 resp=AGVk ZGllQGRlbW8ud2FuYW5jaGkuY29tAGJvZWluZzg= dovecot: May 29 17:44:02 Info: auth-worker(default): sql(eddie(a)demo.wananchi.com,62.8.64.4): query: SELECT CONCAT(domain.path, '/', popbox.mbox_n ame), popbox.password_hash FROM popbox, domain WHERE popbox.local_part = 'eddie' AND popbox.domain_name = 'demo.wananchi.com' AND popbox.domain_n ame = domain.domain_name dovecot: May 29 17:44:02 Error: child 40402 (auth-worker) killed with signal 11 dovecot: May 29 17:44:03 Info: auth(default): client out: FAIL 1 user=eddie(a)demo.wananchi.com temp dovecot: May 29 17:44:05 Info: pop3-login: Aborted login: user=<eddie(a)demo.wananchi.com>, method=PLAIN, rip=62.8.64.4, lip=62.8.64.4, secured o That password_hash - is it usable at all with dovecot? o Could password_hash2 be used? I could popolate the table with a known value and use it, just for imapsync to complete!! o What default_pass_scheme should I use in my userdb configuration? I'll very much appreciate help on this. I am currently testing with pop3, but once I get successful authentication, I will switch to imap for imapsync. Thanks for your time, and help, and advise:-) -Wash http://www.netmeister.org/news/learn2quote.html DISCLAIMER: See http://www.wananchi.com/bms/terms.php -- +======================================================================+ |\ _,,,---,,_ | Odhiambo Washington <wash(a)wananchi.com> Zzz /,`.-'`' -. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com |,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922 '---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121 +======================================================================+ One, with God, is always a majority, but many a martyr has been burned at the stake while the votes were being counted. -- Thomas B. Reed

1 0

[Dovecot] About create mailbox by dovecot
by gaoqiang.qian＠nokia.com 29 May '07

29 May '07

Hi, I am a beginner of Dovecot. Actually I have just used yum install dovecot in my red hat linux host server. Could anyone tell me how can I start to use the dovecot to create a mailbox in my domain name. It seems there are lots of documents in the homepage of dovecot, but I do not know which one is the one specifically start to create mailbox. Thanks Qiang

1 0

[Dovecot] Stop Maildir appending to path
by Henry 28 May '07

28 May '07

Dovecot is working perfectly except for one problem. I have local users and virtual users. Local users are ~/Maildir. And virtual users are /home/vmail/domain/user. The problem is, it keeps trying to fetch virtual mail at /home/vmail/domain/user/Maildir. It doesn't exist the user/ dir is the Maildir. To get around this, I have to make symlinks on each virtual email. What should I check? How do I make it stop appending Maildir to my virtual users path? If I set mail_location to the virtual user path, it works fine. But I won't be able to get local mail. So I... have mail_location pointing to local users ~/Maildir while UserDatabase/Extrafields feature will overwrite the path for virtual users. dovecat-sql.conf: password_query = SELECT email as user, password, CONCAT('/home/ vmail/', path) as userdb_mail, 5000 as userdb_uid, 5000 as userdb_gid FROM view_users WHERE email='%u';

2 1

[Dovecot] IMAP Bandwidth Monitoring
by Phillip T. George 28 May '07

28 May '07

Hello all, I'm wanting to set up IMAP bandwidth monitoring, but I don't see any IMAP size transfer entries in the log file. How would I turn this on? Please refer me to the manual if I've somehow missed it :) Thanks, Phillip

2 1

[Dovecot] IMAP basics
by Paul Scott 28 May '07

28 May '07

I have several POP mail accounts. I have installed and partially configured Dovecot 1.0.0 on Debian sid. I am having trouble understanding some of the basics. For starters do I need to fetch my POP mail (fetchmail, etc.) myself? TIA, Paul Scott

2 1

[Dovecot] Variable expansion in LDA vs POP/IMAP
by Stephane Enten 27 May '07

27 May '07

Hello all, I'm trying to understand when exactly the variable substitution happens in Dovecot, as I get different results in the LDA and in the POP/IMAP server. Here's my general setup: - Postfix MTA, delivers mail via Dovecot LDA - users list sits in a database - mail directory is stored in the database, but with Dovecot variables inside Delivery works perfectly fine, Dovecot's deliver get a "mail" column from the database (that looks like this: /mail/01/%2LMd/%2.2LMd/%LMd/mail/%Ln/ ) and expands variables, delivers the mail into the maildir's location. Now if I try to access the mailbox through Dovecot's POP/IMAP server, it looks like it gets the right field from the database, but won't expand the variables: May 24 18:31:14 mail1 dovecot: imap-login: Login: user=<XXXXX>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured May 24 18:31:14 mail1 dovecot: IMAP(XXXXX): Effective uid=1021, gid=304, home= May 24 18:31:14 mail1 dovecot: IMAP(XXXXX): maildir: data=/mail/01/%2LMd/%2.2LMd/%LMd/mail/%Ln/ May 24 18:31:14 mail1 dovecot: IMAP(XXXXX): maildir: root=/mail/01/%2LMd/%2.2LMd/%LMd/mail/%Ln, index=/srv/mail/01/%2LMd /%2.2LMd/%LMd/mail/%Ln, control=, inbox= May 24 18:31:14 wmail1-v dovecot: IMAP(XXXXX): Disconnected Am I missing something to get the pop/imap part expand those ? -- Stephane Enten

3 4

[Dovecot] UID confusion
by Kevin 27 May '07

27 May '07

I have just finished reading the info on the wiki on setting up virtual users with Dovecot and Postfix. http://wiki.dovecot.org/DovecotLDAPostfixAdminMySQL I'm confused about the UID and GID's. In the docs it shows a user, vmail being created with a UID of 101. Then it looks like GID 12 is used for Postfix or Mail. I'm not sure which it is and would like to know. Bulldozer

2 1

Re: [Dovecot] question mailbox format
by sc2＠gmx.at 27 May '07

27 May '07

ok after playing a while now it works , but i have one problem open.. a.) now he makes for pop3 index files in /var/indexes/%u/imap/index etc... you said that is correct too if i only use pop3 ? b.) i have as INBOX file /var/spool/mail/%u set, when somebody logs in, and the mailbox exist he gets the email (from mbox file), but when the mbox does not exist he makes a directory, instead of a file like /var/spool/mail/%u. The problem is when a new mail comes and the mbox file does not exist, the mail is saved to the directory as msg and not as mbox file any ideas? Btw im using version 1.0.0 thx

4 7

[Dovecot] locking question
by Paul Amaral 27 May '07

27 May '07

Hi, I'm using Maildir with dovecot .99, I'm getting some errors with fcntl locks. Do I still need to use a locking mechanism if I'm using maildir with pop3 access. For reasons I won't go into I cant upgrade from .99 to version one at the time. I'm getting this error with some users, I have tried to manually delete the .imap.index file but the error comes back, any thoughts? May 24 12:11:21 pop imap(generalg): Timeout while waiting for release of exclusive fcntl() lock for index file /home/g/generalg/Ma ildir/.INBOX/.imap.index TIA, Paul

3 2

[Dovecot] Address extensions with dovecot LDA
by Nick Kartsioukas 27 May '07

27 May '07

Greetings! I'm using Dovecot and Postfix with virtual mailboxes, the mailbox data is contained in a MySQL database. I'd like to use the Dovecot delivery agent so I can support Sieve filters. However, I'm not sure how to get the delivery agent to work with the Dovecot auth mechanism and MySQL to do proper lookups of email addresses with address extensions (such as test-blah(a)example.com) Does anyone have a similar setup that can tell me how I might get this to work? -- Nick Kartsioukas | KF6UZB change(a)nightwind.net | NK2694

1 1

[Dovecot] Quick question on multiple access to dovecot indexes
by Adam McDougall 26 May '07

26 May '07

I have up to 4 servers that will run dovecot behind a load balancer, which means the same user might be accessing the same mailbox from multiple servers, and it seems like dovecot doesn't like multiple access to the dovecot indexes for the one user since I currently have them stored in a nfs home directory. Is this a bad thing? Must I keep a seperate index location per server? Just today I started running dovecot on more than one server like this and started seeing things in the logs like: May 25 11:19:13 boomhauer dovecot: IMAP(mcdouga9): Corrupted transaction log file /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index.log: end_offset (1332) > current sync_offset (1244) May 25 11:19:13 boomhauer dovecot: IMAP(mcdouga9): broken sync positions in index file /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index May 25 11:19:13 boomhauer dovecot: IMAP(mcdouga9): fscking index file /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index May 25 11:19:13 boomhauer dovecot: IMAP(mcdouga9): Fixed index file /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index: log file sync pos 2,1332 -> 2, 1244 May 25 11:19:13 boomhauer dovecot: IMAP(mcdouga9): Unexpected transaction log desync with index /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index May 25 11:19:13 boomhauer dovecot: IMAP(mcdouga9): Disconnected: Mailbox is in inconsistent state, please relogin. May 25 11:19:17 dauterive dovecot: IMAP(mcdouga9): file mail-index.c: line 983 (mail_index_sync_from_transactions): assertion failed: (hdr.messages_count == (*map)->hdr.messages_count) May 25 11:19:17 dauterive dovecot: child 16386 (imap) killed with signal 6 ... May 25 11:19:53 dauterive in.imapproxyd[17211]: LOGIN: '"mcdouga9"' (127.0.0.1:53650) on existing sd [9] May 25 11:19:53 dauterive dovecot: IMAP(mcdouga9): Transaction log file /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index.log: marked corrupted May 25 11:19:53 dauterive dovecot: IMAP(mcdouga9): Transaction log file /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index.log.2: marked corrupted

2 2

[Dovecot] Dovecot crashes with malformed Qpopper's mbox
by 前田剛 26 May '07

26 May '07

I am testing migration from Qpopper 4.0.5 and have come across a problem. Dovecot dies while processing UIDL command when accessing malformed Qpopper's mbox which has duplicated "From " separator. Qpopper occasionally makes such header while rewriting mbox. In the attached file, unnecessary "From " at line 3. ---------------- * Dovecot 1.0.0 on Debian 4.0(x86) * ext3 filesystem(not NFS) * description Dovecot dies while processing UIDL command with malformed Qpopper's mbox which has duplicated "From " separator. This occurs when "pop3_reuse_xuidl" is "yes". conversation with Dovecot ~~~~~~~~~~~~~~~~~~~~~~~~~ $ telnet localhost 110 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. +OK Dovecot ready. user xxxxxxxx +OK pass xxxxxxxx +OK Logged in. uidl Connection closed by foreign host. * Dovecot configuration # /usr/local/etc/dovecot.conf protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login mail_extra_groups: mail mail_location: mbox:~/:INBOX=/var/mail/%u mail_full_filesystem_access: yes mbox_write_locks: fcntl mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 pop3_reuse_xuidl(default): no pop3_reuse_xuidl(imap): no pop3_reuse_xuidl(pop3): yes pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: * how to reproduce 1. set "pop3_reuse_xuidl = yes". 2. replace test user's mailbox with attached file. 3. pop3 login and exec "UIDL". POP3 process will die. -- // -------------------------------------------------------------- // MAEDA, Go <maeda-g(a)secom-sanin.co.jp> POP3(test01): file ../../../src/lib/array.h: line 157 (_array_idx): assertion failed: (idx * array->element_size < array->buffer->used) POP3(test01): Raw backtrace: pop3 [0x80a9fab] -> pop3 [0x80a99a9] -> pop3 [0x807ec2c] -> pop3(index_mail_get_headers+0x254) [0x807eeb4] -> pop3(index_mail_get_first_header+0x18) [0x807ef48] -> pop3(mail_get_first_header+0x16) [0x809b746] -> pop3 [0x8057ae9] -> pop3 [0x8057c7f] -> pop3 [0x805674e] -> pop3(io_loop_handler_run+0x128) [0x80b03e8] -> pop3(io_loop_run+0x28) [0x80af858] -> pop3(main+0x82) [0x8058792] -> /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7dffea8] -> pop3 [0x8055c21] child 4788 (pop3) killed with signal 6 From xxx(a)xx.xxxxxxx.xx.xx Sat Feb 17 19:27:47 2007 X-UIDL: i[f"!$h*!!S67!!/RW!! From xxx(a)xx.xxxxxxx.xx.xx Sat Feb 17 19:27:47 2007 Return-Path: <xxx(a)xx.xxxxxxx.xx.xx> X-Original-To: xxxxxxxx(a)xx.xxxxxxx.xx.xx Delivered-To: xxxxxxxx(a)xx.xxxxxxx.xx.xx Received: xxxx xxxx-xxxx-xxxxxx.xxxxxxx.xx.xx (xx [xxx.x.x.x]) xx xx-xxxxxxxx.xxxxxxx.xx.xx (xxxxxxx) xxxx xxxx xx xxxxxxxxxx xxx <xxxxxxxx(a)xx.xxxxxxx.xx.xx>; xxx, xx xxx xxxx xx:xx:xx +xxxx (xxx) Received: xx xx.xxxxxxx.xx.xx (xxxxxxx, xxxx xxxxxx xx) xx xxxxxxxxxx; xxx, xx xxx xxxx xx:xx:xx +xxxx (xxx) X-Mailer: xxxxxxx xx.x xx xxx.xxxxxx.xx.xx X-HTTP_REFERER: xxxx://xxx.xx-xxxxxxx.xx.xx/xxxx/xxxxx.xxxx Errors-To: xxxxxxxxx(a)xx-xxxxxxx.xx.xx To: xxxxxxxxx(a)xx-xxxxxxx.xx.xx From: x.xxxxxxxxx(a)xxxxxxx.xxx Subject: $x<xxx$x$?$$(xx-xxxx Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-2022-JP" Message-Id: <xxxxxxxxxxxxxx.xxxxxxxxxx(a)xx.xxxxxxx.xx.xx> Date: Sat, 17 Feb 2007 19:27:47 +0900 (JST) Status: RO xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx From xxx(a)xx.xxxxxxx.xx.xx Tue Feb 20 14:06:25 2007 X-UIDL: 7;j"!L;8"!b\%#!pH5!! Return-Path: <xxx(a)xx.xxxxxxx.xx.xx> X-Original-To: xxxxxxxx(a)xx.xxxxxxx.xx.xx Delivered-To: xxxxxxxx(a)xx.xxxxxxx.xx.xx Received: xxxx xxxx-xxxx-xxxxxx.xxxxxxx.xx.xx (xx [xxx.x.x.x]) xx xx-xxxxxxxx.xxxxxxx.xx.xx (xxxxxxx) xxxx xxxx xx xxxxxxxxxx xxx <xxxxxxxx(a)xx.xxxxxxx.xx.xx>; xxx, xx xxx xxxx xx:xx:xx +xxxx (xxx) Received: xx xx.xxxxxxx.xx.xx (xxxxxxx, xxxx xxxxxx xx) xx xxxxxxxxxx; xxx, xx xxx xxxx xx:xx:xx +xxxx (xxx) X-Mailer: xxxxxxx xx.x xx xxx.xxxxxx.xx.xx X-HTTP_REFERER: xxxx://xxx.xx-xxxxxxx.xx.xx/xxxx/xxxxx.xxxx Errors-To: xxxxxxxxx(a)xx-xxxxxxx.xx.xx To: xxxxxxxxx(a)xx-xxxxxxx.xx.xx From: xxxxx(a)xxxxx-xxx.xx.xx Subject: $x<xxx$x$?$$(xx-xxxx Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-2022-JP" Message-Id: <xxxxxxxxxxxxxx.xxxxxxxxxx(a)xx.xxxxxxx.xx.xx> Date: Tue, 20 Feb 2007 14:06:25 +0900 (JST) Status: RO xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

3 7

[Dovecot] Return error instead of dying on time back skip?
by Amon Ott 26 May '07

26 May '07

Hello everybody! Currently, dovecot just kills itself if it detects that time has moved backwards more than a hardcoded number of seconds. I accept the reasons, but I do not like to restart dovecot manually after waiting for time to move forward again. A cron job would not help, because time might still be wrong when it restarts dovecot. All our systems run ntpd, but they might be offline for a while before they get contact to a time server, e.g. because of DSL problems. When they do get contact and time is too far off, ntpd sets the new time directly (yes, it could gradually do that, but it might take ages). Now I wonder if Dovecot could return errors to the users instead of dying until time is fine again, e.g. "System time has moved backwards, please come back in n seconds". If the time skip is just a few seconds, it can of course delay and then go on as it does now. With this change, no admin would be needed to carefully restart Dovecot at the right time. I have not looked into Dovecot code myself yet, but could try a patch if necessary. Amon Ott -- Amon Ott - m-privacy GmbH Am Köllnischen Park 1, 10179 Berlin Tel: +49 30 24342334 Fax: +49 30 24342336 Web: http://www.m-privacy.de Handelsregister: Amtsgericht Charlottenburg HRB 84946 Geschäftsführer: Dipl.-Kfm. Holger Maczkowsky, Roman Maczkowsky GnuPG-Key-ID: EA898571

6 7

[Dovecot] dovecot.org DNS finally ok
by Timo Sirainen 26 May '07

26 May '07

All DNS caches that had the old dovecot.org IP should finally be expired by now. About 20 people were unsubscribed because of bounces. I've subscribed them back. I think I'm also going to set up a dovecot.org mirror which can be quickly brought up if the current dovecot.org happens to break for some reason. www.dovecot.org and wiki.dovecot.org at least needs to be up quickly. BTW. Anyone is free to set up their own dovecot.org mirror: rsync -qavz --delete dovecot.org::hg hg rsync -qavz --delete dovecot.org::dovecotweb www rsync -qavz --delete dovecot.org::dovecotwiki wiki rsync -qavz --delete dovecot.org::dovecotmail mail rsync -qavz --delete dovecot.org::dovecotnewsmail mail-news rsync -qavz --delete dovecot.org::dovecotcvsmail mail-cvs I don't want any official mirrors though. They're more trouble than worth. :)

1 0

[Dovecot] question mailbox format
by sc2＠gmx.at 26 May '07

26 May '07

i set mail_location = mbox:/var/spool/mail/%u and protocols = pop3s pop3 why he trys to create and use imap format?` in log are May 25 18:52:25 mail dovecot: pop3-login: Login: user=<richard>, method=PLAIN, rip=80.xx.xx.xx, lip=xx.xx.24.29, TLS May 25 18:52:26 mail dovecot: POP3(richard): open(/var/spool/mail/richard/inbo x, O_CREAT) failed: Not a directory May 25 18:52:26 mail dovecot: POP3(richard): mkdir_parents(/var/spool/mail/richard/.imap/INBOX) failed: Not a directory May 25 18:52:26 mail dovecot: POP3(richard): stat() failed with mbox file /var/ spool/mail/richard/inbox: Not a directory May 25 18:52:26 mail dovecot: POP3(richard): Couldn't init INBOX: Internal erro r occurred. Refer to server log for more information. [2007-05-25 18:52:25] May 25 18:52:26 mail dovecot: POP3(richard): Mailbox init failed top=0/0, retr= 0/0, del=0/0, size=0 friendly regards and thx

3 5

[Dovecot] Quota warning not generated
by Doug Council 26 May '07

26 May '07

I am testing out the unofficial quota warning patch with Dovecot 1.0.0, and no matter what values I use for the storage or messages values, the warning script is never executed. My plugin settings are: plugin { quota = maildir:storage=20480 quota_warning = storage=80%:messages=10 /usr/local/bin/quota-warning.sh } I've tried the following quota_warning lines without any luck: quota_warning = storage=80% /usr/local/bin/quota-warning.sh quota_warning = messages=10 /usr/local/bin/quota-warning.sh quota_warning = storage=80%:messages=10 /usr/local/bin/quota-warning.sh The quota-warning.sh script is set to 0755 and currently just syslogs a warning using logger(1). Run independently of Dovecot, it works fine. Here is a sample maildirsize file (if that is at all important) from when I tried the messages=10 setting: 10485760S 335322 12 14016 1 58058 1 46529 1 37623 1 55252 1 61901 1 53422 1 56228 1 There are more than 10 messages in the mailbox, but the quota-warning.sh script never gets executed. When using storage=80%, the maildirsize file has the correct values (not included in this message), but it never executes the script as well. Does anyone have any ideas? Thanks, -Doug

2 2

[Dovecot] How about a "pipe" plugin?
by Nicolas Boullis 25 May '07

25 May '07

Hi, I have written a plugin so that each time a message is added to a specific box, a program is run and the message is piped into it. Note that the message is also really added to the box. I've been using it for nearly 3 month, for spam/ham learning, and have not had any problem with it. I guess it could also be used to implement an out box (I remember seeing someone asking for such a feature on this list). Currently, I use it with a config like this: (...) namespace private { separator = . location = maildir:/var/mail/%u inbox = yes hidden = no } namespace public { separator = . prefix = learn. location = maildir:/var/learn/%u inbox = no hidden = no } (...) plugin { (...) pipe = /var/learn/%u/.spam:spamc -d some.host -L spam pipe2 = /var/learn/%u/.ham:spamc -d some.host -L ham (...) } Would people be interested by such a feature? If enough people show some interest, I can try to convince my boss to let me release this plugin GPL-licensed. Cheers, Nicolas Boullis

6 7

[Dovecot] Will pay $500 towards a Dovecot feature
by Marc Perkel 25 May '07

25 May '07

10 days ago I proposed this addition (see below) to Dovecot and got a lot of positive response. I would like to make it happen. I'm willing to contribute $500 to the development of this feature. It doesn't have to be implemented perfectly but needs to be workable to the extent that I can telnet into the Dovecot server and run it manually from the command line. I want to at least be able to run a simple script that I will write to add or remove someone from a black list text file. Timo has limited time but has indicated that he will allow it as a kind of undocumented feature (or wiki documented only). This is a sort of proof of concept feature and if it ever becomes a standard the standard will probably be different. However, we should implement it in a way that would be as close to a standard as possible. So - I'm looking for a programmer to make it happen. I'm also looking for others who might also kick in a few bucks as well if necessary. Here's the rough spec. ---------- Here's some thoughts I'd like to throw out there. I know it's not standard IMAP protocol but someone has to try new ideas first and I want to see what people (Timo) think of this. IMAP establishes a connection between the client and the server. Wouldn't it be great if it could be a conduit to let custom Thunderbird plugins talk to custom server application over the IMAP interface? For example, personalized server settings. Suppose for example I want Thunderbird to edit my server side white lists or black lists or any other setting? Wouldn't it be nice if IMAP supported these changes? The connection is made. It's a secure connection that's been authenticated. Lets use it! Here's my initial thoughts on this. Suppose we extended IMAP to include an EXECUTE command as follows: EXECUTE command parameter, parameter .... On the server side is a config file that has the commands that execute will allow and what programs they run. When the execute command is seen by Dovecot then Dovecot runs the program in the list with the parameters passed. For example, suppose there is a command to add a user to a server side blacklist. 100 execute blacklist add joe(a)smith.com 100 ok Dovecot would open a two way connection to the server application allowing the client to talk to any application that is configured and can send and receive text. The connection persists until the server end terminates or the client closes the connection. With a tool like this one can write generic applications easily that would greatly expand what email clients can do interacting with the server. Not only can setting be changes but you could interact with server side calendars, pick up voice messages from phone systems, run any sort of groupware, all over a generic IMAP connection with this simple extension. Example: 100 EXECUTE calendar 100 ok 100 list schedule today 8:00 10:00 100 8:00 make coffee 100 9:00 meeting with boss 100 9:30 Call Joe Blow at 415-555-1212 100 ok 100 quit 100 ok One thing I'd like to use it for is an outgoing SMTP connection to send outgoing email over IMAP. A session might look like this: 999 EXECUTE smtp 999 220 darwin.ctyme.com ESMTP Exim 4.67 Sun, 13 May 2007 06:52:26 -0700 999 helo ctyme.com 999 250 darwin.ctyme.com Hello localhost [127.0.0.1] 999 mail from:marc@perkel.com 999 250 OK 999 rcpt to:dovecot@dovecot.org 999 250 Accepted ...... 999 quit 999 OK Config File: There would have to be a config file that would be a table of what command run what. An example might look like this: calendar: /usr/bin/dovecot/calendar blacklist: /etc/exim/scripts/blacklist Probably might eventually want to add UID/GID and root directory restrictions for security. Login information and connection IP should be passed in the environment.

17 30

Re: [Dovecot] Converting mbox to Maildir, all prior read messages are downloaded as new
by Eric and Barbara Sammons 24 May '07

24 May '07

Can you elaborate on this convert plugin? I have not heard of it and am curious if it is available in 0.99. Thank you! Bruce Bodger wrote: > > On May 24, 2007, at 3:22 PM, Eric and Barbara Sammons wrote: > >> I am running dovecot 0.99. Everything works great; however, now I am >> looking at several different tools to convert mbox to Maildir. It >> seems the tools, mb2md.pl, perfect_maildir.pl, and others all do what >> they claim; however, when the messages are converted and they are >> stored in Maildir/cur, the email clients download these messages as new. > > Like you, I played with all the available scripts. Settled on using > ONLY Dovecot's convert plugin to convert a uw-imap mbox system to > Dovecot maildir. Believe it or not, it ran 100% perfectly and users > never even noticed the switch! > > Good luck. > B. Bodger > New York, NY >

3 2

[Dovecot] quota plugin
by maximatt 24 May '07

24 May '07

hi... i not undestand this plugin (quota) , because if i set a value 10240 (like in example) when i send a 4 messages with attaches sizes like 4MB they do not nothing, but if i want to send a message like 12MB the dont me do that, but in the first way the user inbox have like 20MB. ¿:(? i have these settings for this plugin: protocol imap { mail_plugins= quota imap_quota } plugin { quota= maildir:storage=10240 } ¿can anybody explain me that? :( thanks in advance!!! :)

1 0