- dovecot - dovecot.org

[Dovecot] Keep getting this
by Brent Clark 29 Nov '06

29 Nov '06

Hey all I just installed logcheck and with the result im seeing quiet a few of these. Nov 28 16:59:11 mail dovecot: IMAP(user): file ioloop.c: line 22 (io_add): assertion failed: (fd >= 0) My question is, is it something I need to be concerned about, and also is there something I can do to help dovecot. Kind Regards Brent Clark

3 2

[Dovecot] Extra_fields / first check userdb?
by Leroy van Logchem 29 Nov '06

29 Nov '06

Hi, I would like to supply a few users with extra_fields. All users are found by PAM first so the userdb passwd-file doesnt seem to be used. How to alter the lookup sequence? We can't remove the accounts from the central passwd, just for Dovecot. Thanks, Leroy

2 2

[Dovecot] Authentication
by eric 29 Nov '06

29 Nov '06

Try as I may, I cannot get Dovecot to allow anything but blank passwords listed in a custom file I made for the purpose. It will not recognise anybody in passwd. Only using POP3 on an internal network so little danger of incursions. Once I created a password file with user names and no password, one user could login (from Outlook 2003) but another could not. Telnet test also fails to authenticate. I have allowed the group to write to the /var/spool/folder Syslog simply showed authentication failed. Relevant bits of my config: disable plain text = no mail extra group = users pop3 uidl format %08Xu%08Xv pasted direct from the help I have un commented auth user name characteres mechanisms = plain and I have set auth debug passwords = yes user = root System: Suse 9.3 Dovecot 1.0 rc13 Any ideas? -- John McC

1 0

Re: [Dovecot] considering dovecot
by Rick Hazey 29 Nov '06

29 Nov '06

On Nov 28, 2006, at 3:43 PM, Ejay Hire wrote: > Hello. What email client do you use? Most of the one's I've used (on > Windows) choke at 5k. Our users tend to use one of the following: Apple Mail Entourage (basically Outlook for Mac) Outlook Outlook Express Thunderbird and then there's the webmail system we provide. Apple Mail has virtually no limit on messages it will handle. I currently have over 500,000 emails in my Apple Mail. It stores email much like Dovecot; each email is in a separate file. This makes backups a breeze, which a reason to switch to a server that uses maildir. Entourage, Outlook Express and Outlook have problems if the data file exceeds 2GB. This is an ongoing problem and I'm hoping by keeping email on the server, the support headaches will be reduced. I'm not sure what limits Thunderbird has. I use Thunderbird to connect to the main directory for all email and it doesn't seem to have any trouble handling it. Currently, everyone is using POP3 but I want to move to IMAP. (Thunderbird is the only client that connects via IMAP on our systems) The motivation for moving to IMAP is primarily for spam handling. Instead of users contacting us for emails that might be caught as spam, the spam will be moved to a "junk mail" folder. Then the user can peruse the folder themselves to find any legit email improperly categorized as junk. Vacation messages is the other item that is prompting a change. Everyone is screaming for that feature.

1 0

[Dovecot] Can't drop root group privileges
by Jackie Hunt 28 Nov '06

28 Nov '06

Hi all, I need your insight. I've been testing Dovecot on an AIX 5.2 system. Compiled and running fine. We have some users on an AIX 5.1 system, so I'm working on installing it there, so we can do further testing. I'm using Dovecot 1.0 RC15 with OpenSSL 9.0.7e, configured to use port 10143 (imap) and 10993 (imaps). The error I'm seeing in the log is: dovecot: Nov 28 09:23:54 Info: imap-login: Login: user=<jackie>, method=PLAIN, r ip=xx.x.xxx.xxx, lip=xxx.xx.xxx.xx, TLS dovecot: Nov 28 09:23:54 Error: IMAP(jackie): We couldn't drop root group privil eges (wanted=200, gid=200, egid=0) dovecot: Nov 28 09:23:54 Error: child 860274 (imap) returned error 89 I've seen this error reported on the list, with the suggested resolution being to set the first_valid_gid = 0 in dovecot.conf. I've tried that, and nothing changes. Any help would be greatly appreciated! Jackie --- Jackie Hunt ACNS Voice: (970) 663-3789 Colorado State University FAX: (970) 491-1958 Fort Collins, CO 80523 Email: jackie.hunt(a)colostate.edu

1 0

[Dovecot] POP3 && Folders
by Timothy White 28 Nov '06

28 Nov '06

I'm sure this has come up on the list before... I have a number of accounts normally only accessed via IMAP, and for this reason, there is a global sieve script for all users (also required for the spam filtering). What this means though, is that ever users has 3-4 set folders, that are forced on. I now have a few users that want to use POP3. Is there a way to make it download all messages, in all folders, rather than just the inbox? I'm using Maildir's Thanks Tim -- Linux Counter user #273956 Don't email joeblogs(a)scouts.org.au

2 1

[Dovecot] dovecot-1.0.rc13 LDA
by Peter Bauer 26 Nov '06

26 Nov '06

Hello, I've installed dovecot-1.0.rc13 on FreeBSD-6.1 with LDA support. But I didn't found the /var/run/dovecot/auth-master file on my system. I need this file for the protocol lda { ... auth_socket_path = /var/run/dovecot-auth-master ... } settings in the /usr/local/etc/dovecot.conf. Does anyone has an idea? PS: On a older installation (dovecot-1.0.rc7) the file exists and works very well. Thanks. -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

3 4

[Dovecot] Dovecot, Postfix, Mysql and Virtual Users
by Justin Sung Kim 25 Nov '06

25 Nov '06

Hi, I am looking for a guide or manual to implement Dovecot, Postfix, Mysql and postfixadmin to manage virtual users. Can I get a help from someone? The main issue for me is the SMTP authentication with Mysql. postfixadmin stores the password in md5. How can you make that so it works on both smtp and dovecot? Please help me out. I am stuck with installing and re-installing. Thank you in advance. Justin.

2 1

[Dovecot] Thanks! Migration UWimap -> Dovecot report
by Leroy van Logchem 25 Nov '06

25 Nov '06

Best Dovecot devs, We moved from UW-imap&pop3 to Dovecot this morning (~500 accounts) and reduced our traffic from the home directory server to the imap server bigtime: | 22 Nov| 0.1 0.8| 0.0 0.0| 0.4 0.5| 1550.6 42.9| 1557.3 67.9| | 23 Nov| 0.3 1.0| 0.0 0.1| 0.4 0.6| 1331.8 37.3| 1337.2 46.3| | 24 Nov| 0.0 0.4| 0.0 0.0| 0.2 0.2| 186.8 8.8| 188.9 9.2| Yesterday and the day before we averaged 1.35 TB of NFS traffic for all the remote imap folders (mbox format) while today we only use 1/10th :) Also the lazy purge and writes are absolutly fast now, thanks! One question: Our pop3 users recieved all mail while 'leave mail on server' was enabled -it didnt delete it-. After one such run it's fine. Any idea to improve a uw/ipop3d migration for the next time? <dovecot.conf of rc15> pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = outlook-no-nuls oe-ns-eoh -- Leroy

2 1

Re: [Dovecot] dovecont.conf and "Evolution Mail" configuration
by maria.freixes_graells＠alcatel.es 24 Nov '06

24 Nov '06

> Please....I am lost completly!! Could anyone help me to solve the > question of how can I configure the mail in my linux machine.... > The scenarious is that this linux machine with red had enterprise > linux 4 receives mail from another machine via sendmail. This mail is > saved into /var/spool/mail/ directori, the user is webmaster. > But I want that the mails into /var/spool/mail/webmaster are sended to > the "evolution mail" via pop protocol. > Any idea? > If you could weaste some time with me, I be very gratefully for it!! > Thanks a lot, > Maria > > maria.freixes_graells(a)alcatel.es escribió: >> Hello people!! >> >> First, thanks very much to Ejay Hire and to John Peacock for your >> quickly answer!! >> >> Now, I've dovecot installed, I downloaded the source and I compiled >> them. It's running ok now. >> >> But.....as I am new in all these issues I have some problems with the >> configuration. >> >> I have a user called "webmaster" that have a mail into >> /var/spool/mail, I want to redirect these mails to the "Evolution >> Mail" program from my Linux Desktop. >> I have doubts in two ways: >> >> 1.- Is the dovecot.conf file correct? >> 2.- Are the "Evolution Mail" setting correct? >> >> Evolution Account Settings: >> Name: webmaster(a)bar.ses.alcatel.es >> Full Name: webmaster >> Email Address: webmaster(a)bar.ses.alcatel.es >> Server Type: POP >> Host: 159.23.98.66 >> Username: webmaster >> Server Type: SMTP >> Server Configuration: 159.23.98.66 >> >> >>

4 7

Re: [Dovecot] Question regarding bounce messages on quota full. [solved]
by Mustafa A. Hashmi 24 Nov '06

24 Nov '06

On 11/14/06, Mustafa A. Hashmi <mahashmi(a)gmail.com> wrote: In the following section: > auth default { > mechanisms = plain > > 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 > } > } > > passdb pam { > > } > > # LDAP database > userdb ldap { > args = /etc/dovecot/dovecot-ldap.conf > } > user = root # <<-- wrong > } user = vmail fixes the issue. Apologies about the noise. Thanks all. Regards, -- Mustafa A. Hashmi mahashmi(a)gmail.com mh(a)stderr.net

2 2

[Dovecot] mailadm? authentication vs. authorization?
by David Lee 24 Nov '06

24 Nov '06

Does "dovecot" have anything similar to the UW IMAP "mailadm" group operation? From near the end of: http://www.washington.edu/imap/documentation/RELNOTES.html 'Support for SASL authentication identity vs. authorization identity in the IMAP and POP3 servers. If the user indicated by the authentication identity is in the "mailadm" group, he may specify any authorization identity and get logged in as the authorization identity user.' This allows an email administrator (member of group "mailadm") to sort out problems in a user's mailbox as that user identifier. (We try to train our users not to reveal their password to anyone, not even to our own staff. But sometimes, as staff, it is very useful to be able to do operations as a particular user to diagnose a problem.) -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : : Durham University : : http://www.dur.ac.uk/t.d.lee/ South Road : : Durham DH1 3LE : : Phone: +44 191 334 2752 U.K. :

2 1

[Dovecot] LDAP authentication windows 2003
by Matheus Antonio Oliveira 24 Nov '06

24 Nov '06

1 0

[Dovecot] Two email accounts writing to one nfs shared home directory
by John McDonald 23 Nov '06

23 Nov '06

I use dovecot as a local imap server on my desktop machine due to the fact that my workplace only support POP3. I use fetchmail to pop, postfix to deliver, and dovecot for client access. At present I have a single email account which is the same as my system login and have postfix and dovecot setup to use ~/Maildir. The home directories on our system are served from a central file system, using nfs, which has full backup/disaster recovery policy implemented. I now need to setup a second separate email account for a specific task. Our sysadmins have setup this account for me on the POP3 server. The problem is that this account does not have a home directory on our system and therefore I can't write to ~/Maildir. What I would like to do is setup the same type of system for this second account without necessitating the creation of a home directory. That is, I would like a second Maildir folder in my own user account to which this second email account's messages are delivered. This way I will have full backup of the messages. What is the most straightforward way of achieving this? (or can it be done at all?) Thanks for the help. Regards, John McDonald.

3 2

[Dovecot] dovecont.conf and "Evolution Mail" configuration
by maria.freixes_graells＠alcatel.es 23 Nov '06

23 Nov '06

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

1 0

[Dovecot] Which version of dovecat I must use quit mysql 14.12 5.0.24a?
by maria.freixes_graells＠alcatel.es 22 Nov '06

22 Nov '06

Hello everybody!! I'm new on linux machine configuration, and I have a question related to product versions. We've Linux seweb1 2.6.9-5.EL installed, but instead of install the mysql product from "Red Hat Interprise Linux 4" CD what is mysql-0:4.1.7-4.RHEL4.1.i386, we installed: *mysql 14.12 5.0.24a *So, now, when we tried to install dovecot, it needs mysql-0:4.1.7-4.RHEL4.1.i386, perl-DBD-MySQL-0:2.9004-3.1.i386 and postgresql-libs-0:74.6-1.RHEL4.2.i386. I don't want to install these packets from mysql because I'm afraid to crash the mysql that we've now working...... So, my question is, what I need to do in this case? Can I install the mysql CD version without interferring to our actual BD working: *mysql 14.12 5.0.24a? *Or....Which version of dovecot we must install in order to work with *mysql 14.12 5.0.24a. *I would be very gratefully if you could help me, beacause we afraid to crash the BD that is working now, and we don't know how to install dovecot in this case. Best regards, Maria

2 1

[Dovecot] assertion failed: (need_space == (uoff_t)-mails[idx].space)
by David King 21 Nov '06

21 Nov '06

I'm running Dovecot dovecot-1.0.r13 on FreeBSD (FreeBSD 6.1-RELEASE- p10). Mail is stored in mbox format (dovecot.conf after the msg). Procmail delivers mail to subfolders under ~/.mail, locking using dotfiles. One folder in particular for one user has an mbox file ~/.mail/Cron. Quite often, I'll see that procmail processes are stacking up because ~/.mail/Cron.lock exists, and they (rightly) refuse to deliver to a locked mailbox. It seems that dovecot is creating these lock files and then dying. The .lock file's contents refer to a PID that, by the time I see the lockfile, doesn't exist. It appears that dovecot is leaving behind the lock files, after exiting with a signal 6 (sometimes 11) and leaving behind messages in /var/log/maillog (and the end of this message). In dovecot.conf I have mail_drop_priv_before_exec = no, but I can't find the core file that I would expect it to dump, so I can't give you a backtrace. Hopefully the assertion in /var/log/maillog is enough. With ~/.mail/Cron perpetually locked, I'm not able to receive mail in this folder, and with any IMAP client that tries to access that folder having the IMAP server shut down, it keeps me from getting mail. Any ideas? # tail /var/log/maillog Nov 11 23:05:32 melchoir dovecot: imap-login: Login: user=<ketralnis>, method=PLAIN, rip=10.0.1.239, lip=10.0.0.1, TLS Nov 11 23:05:32 melchoir dovecot: IMAP(ketralnis): Disconnected: Logged out Nov 11 23:06:52 melchoir dovecot: IMAP(ketralnis): file mbox-sync- rewrite.c: line 405 (mbox_sync_read_and_move): assertion failed: (need_space == (uoff_t)-mails[idx].space) Nov 11 23:06:52 melchoir dovecot: child 16929 (imap) killed with signal 6 Here is dovecot.conf: # cat /usr/local/etc/dovecot.conf | sed -E 's/^(.*)#.*$/\1/' | grep - Ev '(^#|^[ ]*$' protocols = imap pop3 imaps pop3s ssl_cert_file = /etc/ssl/mail-cert.pem ssl_key_file = /etc/ssl/private/mail-key.pem disable_plaintext_auth = no login_user = dovecot verbose_proctitle = yes first_valid_gid = 0 mail_extra_groups = mail default_mail_env = mbox:%h/.mail:INBOX=/var/mail/%u mmap_disable = no lock_method = fcntl mbox_read_locks = dotlock mbox_write_locks = dotlock fcntl mail_drop_priv_before_exec = no protocol imap { login_greeting_capability = yes imap_client_workarounds = delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep } protocol pop3 { pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } auth default { mechanisms = plain login passdb pam { } userdb passwd { } userdb prefetch { } user = root }

2 3

[Dovecot] Dovecot on Solaris
by Steven F Siirila 21 Nov '06

21 Nov '06

For those running Dovecot on Solaris, what are your positive/negative experiences with building the software with CC vs. GCC? We are currently letting ./configure find our gcc and build with it, but wondered if anyone has any experience with Sun CC (does it even compile, for example). -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

6 5

[Dovecot] RAID benchmarks
by Ethan Sommer 21 Nov '06

21 Nov '06

We (a small college with about 3000 active accounts) are currently in the process of moving from UW IMAP running on linux to dovecot running on a cluster of 3 or 4 new faster Linux machines. (Initially using perdition to split the load.) As we are building and designing the system, I'm attempting to take (or find) benchmarks everywhere I can in order to make informed decisions and so that when we need something faster we have something to compare it to. I've looked all over the Internet and I haven't seen very many good benchmarks running on recent hardware for things like this. Even simple things like how different raid levels perform with fast CPUs and really fast disks. We recently got the first of the cluster machines (which has the following specs: (from penguin computing) 2x 1.6ghz woodcrest (so 4 cores total) 2g ram (we may upgrade to more, depending on what we seem to need) 6x 15k SAS 73G hard drives. I've always read that RAID 10 is the RAID of choice for mail, because the checksums take time and whatnot, but on a system that fast I'm sure that's not an issue (which I could see from the cpu usage during benchmarks.) We were also wondering whether RAID6 would be a good option since it would give more redundancy. (raid6 allows 2 drive failures) All tests were run on ext3 with all 6 disks in the raid. Everything is using Linux software raid. I used bonnie++ to run the benchmarks, and here are the initial results we got: Output Input RAID "Per Chr" "Block" "Per Chr" "Block" RAID6 34628, 97983, 23316, 39077 RAID5 39559, 32715, 32036, 52231 RAID10 38816, 229062, 40645, 267418 I assume that mail running maildir (as we intend to do) is somewhere between writing one char at a time and writing huge blocks to fill 4g files. Since the Per Chr values seemed to have maxed out the CPU and we'll have 4 cores available, I tried the same thing running 4 copies of bonnie at once and adding the results. (I worked backwards and didn't bother with raid 6 for obvious reasons) Output Input RAID "Per Chr" "Block" "Per Chr" "Block" RAID5 37465, 37095, 102828, 174263 RAID10 111239, 128287, 93400, 230320 So, if our system is ever running full out, basically disk bound, it should be able to handle about 4X as many writes and at least as many reads using RAID10 than raid 5, and since raid 6 was pretty similar to raid 5 in the first tests, I assume it will be here too. I have the full bonnie results if anyone's interested. I also plan to come up with some basic benchmarks as we start to actually have dovecot working as we want it to. (Possibly using the macs in our labs and XGrid as a "client".. finally a use for that thing :) ) Do people have suggestions as to what to test for a primarily IMAP (+ a little POP) server? I was thinking of doing something similar to http://www.courier-mta.org/mbox-vs-maildir/ which selects a mail box, deletes and expunges a message, fetches a few messages, and then does some searches. Also, while I have the opportunity, are there any other benchmarks I should run? I suppose I could compare dovecot with mbox vs maildir, with indexing and without. Dovecot with indexing but the indexes deleted, etc. I could compare dovecot to uw imap. Anything else? I probably can't justify the time to get cyrus up and running. (I did that a few months ago when deciding which server to use...) Ethan Sommer -- -- Ethan Sommer Systems Administrator Gustavus Adolphus College 507-933-7042 sommere(a)gac.edu

3 5

[Dovecot] rc14 and rc15 performance issues
by Jeff A. Earickson 21 Nov '06

21 Nov '06

Hi, I am stuck at rc13 because rc14 and rc15 have both failed to keep up with imap connections on my (slow old) system. I have the problem where if a lot of people check their email at once (like at the top of the hour) then my load goes way up and things slow to a crawl. My setup: Solaris 10 on an E220R, mbox format, imap and imaps only. I also use "login_process_per_connection = no". Any suggestions? Jeff Earickson Colby College

5 6

[Dovecot] how to configure dovecot
by Hein Celliers 21 Nov '06

21 Nov '06

Hi all! I need some help....changing passwords....... Dovecot server, appears to cache the old credentials. It only discovers the change upon a restart. I need to know how to configure dovecot (dovecot-1.0-0.beta2.7) as not to cache the passwords. (Using fedora core 5) Thanks Hein Celliers

1 0

Re: [Dovecot] Dovecot on Solaris
by Joseph Tam 21 Nov '06

21 Nov '06

> For those running Dovecot on Solaris, what are your positive/negative > experiences with building the software with CC vs. GCC? We are currently > letting ./configure find our gcc and build with it, but wondered if anyone > has any experience with Sun CC (does it even compile, for example). I once used StudioCC to compile dovecot to see if the problem I had was a compiler bug, but in general, I use gcc since a lot of software is tested against it. I don't use Studio unless performance is critical. >From what I know, IMAP performance is basically disk-memory bounded, so it might not be worth sweating over: use whatever gives you the least grief. Joseph Tam <tam(a)math.ubc.ca>

1 0

[Dovecot] manageSIEVE implementation
by Brian G. Peterson 20 Nov '06

20 Nov '06

I found a thread from last year that suggested that a manageSIEVE (port 2000) implementation for dovecot-sieve doesn't exist yet. I assume that this is still true. Could somebody please provide a status on this? Thanks, - Brian

3 3

Re: [Dovecot] Auth checking also the service
by Andrey Panin 20 Nov '06

20 Nov '06

On 322, 11 18, 2006 at 12:56:41 +0100, Alessandro Astarita wrote: > Alle 12:14, sabato 18 novembre 2006, Johannes Berg ha scritto: > > I don't see why it wouldn't be possible but haven't looked at the code. > > > > I wonder why you even need to distinguish between these though. Are we > > still in the days where encryption is a value-added service? :) > > I have to distinguish pop3/pop3s and imap/imaps because I need mailboxes with > ssl access only. It's a way to force users to do secure connection. :-) Please try attached patch. It adds %c variable which expands to "TLS" if connection is secure. > -- > Alessandro 'Asterix' Astarita <aleast(a)capri.it> > Capri Online S.r.l. http://www.caprionline.it/ > "Unix IS user friendly. It's just selective about who its friend are" > -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

3 2

[Dovecot] BUG: passdb checkpassword {} and lastauth file
by Max A 20 Nov '06

20 Nov '06

(Repeat, because on the first message there was no reaction) Hi. If checkpassword interface is used for working with vpopmail, function vpopmail "Record time and ip of last auth attempt" (--enable-auth-logging option for configure) won't work - the file "lastauth" is created in Maildir, but does not contain ip-address. If I had correctly understood, dovecot woldn't have set a enviroment variable TCPREMOTEIP for vchkpw. If changes are made in auth/passdb-checkpassword.c (a patch in attachment), everything will work. Probably, the patch is incorrect and does not solve all problems, however the request is to pay attention to existence of the problem. Also it is possible, that a similar problem exists with other variables TCP UCSPI protocol (http://cr.yp.to/proto/ucspi-tcp.txt) P.S. If use the interface vpopmail instead of checkpassword, the file "lastauth" will not be created at all, that is a little bit inconvenient. ********************************** System: dovecot-1.0.rc10 vpopmail-5.4.17 ASP Linux Server II (RHEL3 clone) kernel 2.4.21-47.EL.aspsmp CPU architecture: x86 (IBM xSeries 336) Filesystem: ext3 ********************************** dovecot configuration: base_dir = /var/run/dovecot/ protocols = imap pop3 disable_plaintext_auth = no ssl_disable = yes login_greeting = Ready. first_valid_uid = 89 last_valid_uid = 89 first_valid_gid = 89 last_valid_gid = 89 protocol imap { listen = 81.26.136.8:144 mail_executable = /usr/local/libexec/dovecot/imap mail_plugins = quota imap_quota mail_plugin_dir = /usr/local/lib/dovecot/imap imap_client_workarounds = delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep } protocol pop3 { listen = 81.26.136.8:112 login_executable = /usr/local/libexec/dovecot/pop3-login mail_executable = /usr/local/libexec/dovecot/pop3 pop3_uidl_format = %f mail_plugins = quota mail_plugin_dir = /usr/local/lib/dovecot/pop3 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } auth default { mechanisms = plain login passdb checkpassword { args = /var/qmail/vpopmail/bin/vchkpw } userdb prefetch { } user = root } dict { } plugin { quota = maildir } *************************************** dovecot configure options: ./configure \ --disable-ipv6 \ --prefix=/usr/local \ --sysconfdir=/etc/dovecot \ --without-passwd \ --without-passwd-file \ --without-shadow \ --without-pam \ --without-bsdauth \ --with-checkpassword \ --with-vpopmail \ --without-static-userdb \ --with-prefetch-userdb \ --without-sql \ --without-pgsql \ --without-mysql \ --without-sqlite \ --with-ssl=openssl \ --with-pop3d \ --without-deliver \ --with-storages=maildir \ --with-docs ***************************************** vpopmail configure options: ./configure \ --enable-auth-module=cdb \ --enable-logging=p \ --enable-md5-passwords \ --enable-make-seekable \ --enable-file-sync \ --enable-ip-alias-domains \ --enable-clear-passwd \ --disable-roaming-users \ --disable-learn-passwords \ --disable-passwd \ --enable-auth-logging diff -ur dovecot-1.0.rc10.orig/src/auth/passdb-checkpassword.c dovecot-1.0.rc10/src/auth/passdb-checkpassword.c --- dovecot-1.0.rc10.orig/src/auth/passdb-checkpassword.c 2006-08-22 06:37:56.000000000 +0400 +++ dovecot-1.0.rc10/src/auth/passdb-checkpassword.c 2006-10-17 16:47:09.000000000 +0400 @@ -226,6 +226,10 @@ env_put(t_strconcat("REMOTE_IP=", net_ip2addr(&request->remote_ip), NULL)); + env_put(t_strconcat("TCPREMOTEIP=", + net_ip2addr(&request->remote_ip), + NULL)); + } if (request->master_user != NULL) { env_put(t_strconcat("MASTER_USER=",

2 5

[Dovecot] dovecot and ldap passwords.
by Mauro Sanna 20 Nov '06

20 Nov '06

Hallo. First of all I'm sorry for my bad english. I have a question about how dovecot use passwords. I have all my mail accounts in a ldap database. The user password are stored in form: {crypt}mypasswd. In dovecot-ldap.conf I have default_pass_scheme = CRYPT. All is working fine. The problem in the crypt scheme is that I can't have passwords more than 8 characters long. So I've tried to change the type of the ldap passwords in SSHA or SMD5, but in this way the users can't authenticate yourselfs. Dovecot doesn't understand SSHA or SMD5?

3 3

[Dovecot] Problem with rc10
by Steven F Siirila 20 Nov '06

20 Nov '06

I just upgraded our test server from rc6 to rc10... ISSUE #1 I noticed that we no longer are getting two "From_" lines. However, the one that was good (had the original sender e-mail address) is now gone. The one with "dovecot.deliver" remains. I attempted to add "-d test" to the mailbox_command line in main.cf as follows: mailbox_command = /opt/dovecot/libexec/dovecot/deliver -d test and things turned ugly and caused Postfix to defer messages: Oct 17 16:31:50 hostname postfix/local[7230]: D14632C9C: to=<someuser@somehost>, relay=local, delay=3.6, delays=3/0.02/0/0.62, dsn=4.3.0, status=deferred (temporary failure) I removed the "-d test" from the Postfix main.cf and the problem went away. So, how do I fix the "From_" lines? ISSUE #2 After upgrading, messages cannot be moved from the INBOX to a folder. Thunderbird claims there was an internal error and to consule the server logs, but I see nothing in the dovecot logs that would indicate what's going on. For example, I attempted to move a message into my Trash folder which did not currently have any index files. Here is a Solaris truss output of that attempt: poll(0x000B4C98, 2, 999) = 0 poll(0x000B4C98, 2, 0) = 0 poll(0x000B4C98, 2, 999) = 1 read(0, " D O N E\r\n", 3323) = 6 write(1, " 2 8 O K I d l e c".., 23) = 23 read(0, 0x000BC5BB, 3317) Err#11 EAGAIN poll(0x000B4C98, 2, 675) = 1 read(0, " 3 0 u i d c o p y ".., 3317) = 27 stat64("/home/sfs/Trash", 0xFFBFF5C8) = 0 alarm(120) = 0 fcntl(6, F_SETLKW64, 0xFFBFF308) = 0 alarm(0) = 120 stat64("/home/sfs/Trash", 0xFFBFF640) = 0 mkdir("/home/sfs/.imap/Trash", 0770) Err#17 EEXIST stat64("/home/sfs/.imap/Trash", 0xFFBFF4C0) = 0 stat64("/home/sfs/Trash", 0xFFBFF4C0) = 0 time() = 1161122396 open64("/home/sfs/.imap/Trash/dovecot.index", O_RDWR) Err#2 ENOENT open64("/home/sfs/.imap/Trash/dovecot.index", O_RDWR) Err#2 ENOENT write(1, " 3 0 N O I n t e r n".., 96) = 96 poll(0x000B4C98, 2, 588) = 0 poll(0x000B4C98, 2, 0) = 0 poll(0x000B4C98, 2, 410) = 0 Someone else using a different IMAP client caused these errors to occur (this is even after I wiped all of their dovecot index files): Oct 17 16:43:11 earth.tc.umn.edu dovecot: IMAP(kor): Corrupted transaction log file /home/kor/.imap/INBOX/dovecot.index.log: invalid indexid (1161121145 != 1156185395) Oct 17 16:43:11 earth.tc.umn.edu dovecot: IMAP(kor): Corrupted transaction log file /home/kor/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (6 >= 6) Oct 17 16:47:09 earth.tc.umn.edu dovecot: IMAP(kor): Corrupted transaction log file /home/kor/.imap/INBOX/dovecot.index.log: invalid indexid (1161121145 != 1161120959) Oct 17 16:47:09 earth.tc.umn.edu dovecot: IMAP(kor): Corrupted transaction log file /home/kor/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (2 >= 2) Oct 17 17:05:59 earth.tc.umn.edu dovecot: IMAP(kor): Corrupted transaction log file /home/kor/.imap/INBOX/dovecot.index.log: invalid indexid (1161121145 != 1161120959) Oct 17 17:05:59 earth.tc.umn.edu dovecot: IMAP(kor): Corrupted transaction log file /home/kor/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (4 >= 4) Here are our non-standard dovecot.conf items: protocols = imap imaps pop3 pop3s shutdown_clients = no syslog_facility = local6 ssl_cert_file = /etc/opt/openssl/certs/dovecot.pem ssl_key_file = /etc/opt/openssl/private/dovecot.pem default_mail_env = mbox:~/:INBOX=/var/mail/%u # Default namespace namespace private { separator = / prefix = location = mbox:~/:INBOX=/var/mail/%u inbox = yes hidden = yes } mail_full_filesystem_access = yes first_valid_uid = 100 max_mail_processes = 8192 mbox_min_index_size = 128 imap_client_workarounds = delay-newmail outlook-idle tb-extra-mailbox-sep pop3_uidl_format = %08Xu%08Xv protocol lda { postmaster_address = postmaster(a)umn.edu mail_plugins = cmusieve } auth_verbose = yes auth_debug = yes auth default { passdb pam { args = session=yes * } } I am now backing out to rc6 for now... we never saw this behavior on rc6. -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

2 4

[Dovecot] Problems Creating Core Dumps
by Joseph D. Wagner 20 Nov '06

20 Nov '06

Dovecot 1.0.rc15 crashed on my FC4 server, but it didn't create a core dump. Upon further research, I found these lines tucked away in the /etc/rc.d/init.d/functions file: # make sure it doesn't core dump anywhere unless requested ulimit -S -c ${DAEMON_COREFILE_LIMIT:-0} >/dev/null 2>&1 The /etc/rc.d/init.d/functions file is a master file that is referenced by all of the init scripts, so I didn't want to change it. Instead, I created a file /etc/sysconfig/dovecot with the following line: DAEMON_COREFILE_LIMIT=unlimited If I'm reading the /etc/rc.d/init.d/functions file correctly, this should work, but my bash is rusty. I was hoping someone else could check my work. Joseph D. Wagner

2 1

[Dovecot] Backtraces without core dumps
by Timo Sirainen 19 Nov '06

19 Nov '06

Since getting core dumps seems to be difficult sometimes, especially with login processes, I've now added code to log the backtrace when Dovecot crashes in some assert check (or some other reason why it decides to abort()). This code works with Linux and Solaris, but I don't know about BSDs. Apparently there exists libexecinfo library which could be used. I think this code could be used to log backtraces also for segfaults, but that's more risky so I didn't do it yet. Maybe it should be done only optionally. If you're interested in trying, the code is now in CVS and in the latest nightly snapshot. When it crashes, it prints something like: Panic: file client.c: line 55 (client_create): assertion failed: (my_client != NULL) Error: Backtrace: ./imap [0x80b2ffa] -> ./imap [0x80b2ecc] -> ./imap [0x805bbb3] -> ./imap(main+0x426) [0x80634a6] -> /lib/tls/libc.so.6 (__libc_start_main+0xc8) [0xb7e53ea8] -> ./imap [0x80566a1] Looks like the symbol name resolving doesn't work all that great. But here gdb will help you: gdb ./imap (gdb) b *0x80b2ffa Breakpoint 1 at 0x80b2ffa: file failures.c, line 126. (gdb) b *0x80b2ecc Breakpoint 2 at 0x80b2ecc: file failures.c, line 185. (gdb) b *0x805bbb3 Breakpoint 3 at 0x805bbb3 (gdb) b *0x80634a6 Breakpoint 4 at 0x80634a6: file main.c, line 223. That went pretty well, except for some reason it couldn't figure out where 0x805bbb3 was. To get some kind of an idea about that, you can do: (gdb) x 0x805bbb3 0x805bbb3 <client_create+467>: 0x90909090 If someone knows better ways to do all of this, please tell me too :)

1 0

[Dovecot] Dovecot (unofficial) patches
by Egbert Jan 19 Nov '06

19 Nov '06

Dear list, As a recent dovecot addict, I'm a bit puzzled by the sheer amount of patches available. I have not seen the history of these patches and I could not find a README explainng the patches. Are all these personal wishes/nice to have things or are they (to be) incorporated in dovecot-final? I use rpmbuild to create new rpms from the latest tarball but in that process still several patches are included during the build. I wonder if they are still needed in rc15. I use the orignal spec file (the latest I could find) was created for rc7 and in there I see: Patch2 dovecot-0.99.10-mbox-patch Seems to be to change the order of ./Mail before ./mail Patch3 dovecot-CVE-2006-2414 Overview from CVE db:Directory traversal vulnerability in Dovecot 1.0 beta and 1.0 allows remote attackers to list files and directories under the mbox parent directory and obtain mailbox names via ".." sequences in the (1) LIST or (2) DELETE IMAP command. I'm not a spec file wizard, so I change as less as possible. Unfortunately the maintainer (Jerome Soyer) has never responded to my emails. My server runs Mandriva Official 2007.0 and Postfix 2.3.3 and dovecot rc14 (will move to rc15 soon). TNX EgbertJan (NL)

2 1

[Dovecot] TLS timeout with Thunderbird
by Jason Dixon 19 Nov '06

19 Nov '06

I'm trying to get dovecot working with various clients on my new mailserver. I installed the base rc2 that comes with OpenBSD 4.0, then upgraded to rc14 when I ran into problems with TLS and Thunderbird. The server has no problems with Mail.app on my laptop, but any connection attempts from Thunderbird timeout after the TCP handshake. 13:53:41.074438 66.x.x.2.50483 > 38.x.x.248.993: S 3787736038:3787736038(0) win 65535 <mss 1460,nop,wscale 0,nop,nop,timestamp 2064284084 0,sackOK,eol> (DF) 13:53:41.074554 38.x.x.248.993 > 66.x.x.2.50483: S 1565942120:1565942120(0) ack 3787736039 win 16384 <mss 1460,nop,nop,sackOK,nop,wscale 0,nop,nop,timestamp 2681405076 2064284084> (DF) 13:53:41.459434 66.x.x.2.50483 > 38.x.x.248.993: . ack 1 win 65535 <nop,nop,timestamp 2064284084 2681405076> (DF) 13:53:47.028621 66.x.x.2.50483 > 38.x.x.248.993: F 1:1(0) ack 1 win 65535 <nop,nop,timestamp 2064284096 2681405076> (DF) The only thing logged by dovecot is a disconnection event. There is nothing else logged, even with ssl_verbose enabled. Nov 17 14:23:05 colo2 dovecot: imap-login: Disconnected: rip=66.x.x. 2, lip=38.x.x.248, TLS handshake This happens with Thunderbird 1.5.0.4 and 1.5.0.8 on Mac OS X, and Thunderbird 1.5.0.7 on Windows 2000. Any ideas would be greatly appreciated. Thanks, -- Jason Dixon DixonGroup Consulting http://www.dixongroup.net

7 11

[Dovecot] 1.0.rc15 released
by Timo Sirainen 19 Nov '06

19 Nov '06

http://dovecot.org/releases/dovecot-1.0.rc15.tar.gz http://dovecot.org/releases/dovecot-1.0.rc15.tar.gz.sig * Fixed an off-by-one buffer overflow in cache file handling. The code is executed only with mmap_disable=yes and only if index files are used (ie. INDEX=MEMORY is safe). * passdb checkpassword: Handle vpopmail's non-standard exit codes. - rc14 sometimes assert-crashed if .log.2 file existed in a mailbox (earlier versions leaked memory and file descriptors) - io_add() assert-crashfixes - Potential SSL hang fix at the beginning of the connection

1 0

[Dovecot] Security hole #2: Off-by-one buffer overflow with mmap_disable=yes
by Timo Sirainen 19 Nov '06

19 Nov '06

Version: 1.0test53 .. 1.0.rc14 (ie. all 1.0alpha, 1.0beta and 1.0rc versions so far). 0.99.x versions are safe (they don't even have mmap_disable setting). Problem: When mmap_disable=yes setting is used, dovecot.index.cache file is read to memory using "file cache" code. It contains a "mapped pages" bitmask buffer. In some conditions when updating the buffer it allocates one byte too little. Exploitability: I think it's going to be pretty difficult to cause anything else than a crash, but I wouldn't say impossible. Only logged in IMAP/POP3 users can exploit this. In theory you might be able to exploit this for other users as well by sending them a lot of specially crafted emails, but this requires knowing what dovecot.index.cache file contains. Normally its contents can't be predicted, although perhaps with POP3 users it gets empty often enough that the exploit could be tried. Then again, the exploit requires having at least 4MB cache file, which won't happen with POP3 users before the mailbox has about 170k mails (if I counted right). With IMAP the cache file is used more, so it's easier to fill the 4MB with for example a lot of To-headers. Workaround: Use INDEX=MEMORY so the cache files aren't used at all. Fix: 1.0.rc15 fixes this. You can also use this patch: http://dovecot.org/patches/1.0/file-cache-buffer-overflow-fix.diff

1 0

[Dovecot] I/O leak
by Jim Horner 19 Nov '06

19 Nov '06

I upgraded from rc12 to rc14 last night... sifting through the logs I noticed the following. I point this out since it appears dovecot is in high gear bug-fix mode. This issue is not big for me; I rarely stop dovecot. My init.d script for dovecot is basically stop) killall dovecot imap-login I am guessing there might be a more graceful way to stop dovecot? Or rc14 fixed this? I see in rc14 changelog: - rc13 crashed if client disconnected while IDLEing but only user1 was IDLE. Nov 15 21:53:23 myserver dovecot: IMAP(user1(a)arinbe.com): Disconnected in IDLE Nov 15 21:53:23 myserver dovecot: imap-login: Killed with signal 15 Nov 15 21:53:23 myserver dovecot: IMAP(user2(a)arinbe.com): Disconnected Nov 15 21:53:23 myserver dovecot: imap-login: Killed with signal 15 Nov 15 21:53:23 myserver dovecot: IMAP(user3(a)arinbe.com): Disconnected Nov 15 21:53:23 myserver dovecot: imap-login: Killed with signal 15 Nov 15 21:53:23 myserver dovecot: I/O leak: 0x804d7a0 (17) Nov 15 21:53:23 myserver dovecot: I/O leak: 0x804d7a0 (15) Nov 15 21:53:23 myserver dovecot: I/O leak: 0x804d7a0 (19) Nov 15 21:53:30 myserver postfix/master[31974]: terminating on signal 15 Nov 15 21:54:02 myserver dovecot: Dovecot v1.0.rc14 starting up Jim

2 2

[Dovecot] 1.0.rc14 released
by Timo Sirainen 19 Nov '06

19 Nov '06

http://dovecot.org/releases/dovecot-1.0.rc14.tar.gz http://dovecot.org/releases/dovecot-1.0.rc14.tar.gz.sig More fixes. "Duplicate header extension keywords" is the only known problem (or if I forgot something, remind me). I'll try to figure out a way to reproduce it easily and then get it fixed. * LDAP: Don't try to use ldap_bind() with empty passwords, since Windows 2003 AD skips password checking with them and just returns success. * verbose_ssl=yes: Don't bother logging "syscall failed: EOF" messages. No-one cares about them. + Dovecot sources should now compile without any warnings with gcc 3.2+ - rc13 crashed if client disconnected while IDLEing - LDAP: auth_bind=yes fixes - %variables: Fixed zero padding handling and documented it. %0.1n shouldn't enable it, and it really shouldn't stay for the next %variable. -sign also shouldn't stay for the next variable. - Don't leak opened .log.2 transaction logs. - Fixed a potential hang in IDLE command (probably really rare). - Fixed potential problems with client disconnecting while master was handling the login. - quota plugin didn't work in Mac OS X

4 7

[Dovecot] quota plugin enhancement request
by Michael Tibben 19 Nov '06

19 Nov '06

Hi am having a small issue with the quota plugin In Squirrelmail when a message is deleted, it seems to be copied to the Trash folder *before* it is deleted from the current folder. However if it is a large message being deleted and the mailbox is close to its quota limit, it means dovecot will deny the copy operation as the quota will be exceeded if the message is copied Because of this, I am wondering if it is possible to have an option for the quota plugin to track, but not enforce the quota. This is because I don't require quota enforcement on IMAP, as Postfix will enforce quota on incoming mail anyway. I hope this makes sense... Michael

5 6

[Dovecot] Is "Resource temporarily unavailable" an old problem?
by Ricardo Dias Campos 19 Nov '06

19 Nov '06

Hi. I've installed dovecot recently in a Fedora 5 Linux. It seemed to be OK but I begun to get the message "Can't connect to auth server at default: Resource temporarily unavailable". When I get the message, dovecot hangs. The problem is that "temporarily" is not quite true since the only way to get dovecot running again is to restart it. As a matter of fact, I cannot say that it never recovers. What I know is that it is out for a long, long time. Then a new problem arose: the time between hang-ups begun to diminish. Trying to find why I discovered that the number or dovecot-auth processes was too high (last time I got 169 processes, a lot of them <defuncts>). It seems that, if I kill all these processes, it takes more time before it hangs again. I looked up for messages in the Internet and I found a mail exchange between people from this list. The first hint I got was to upgrade dovecot. As I said, I'm using Fedora 5 and the version distributed with it was dovecot-1.0-0.beta2.7.i386. I upgraded it to dovecot-1.0-0.beta8.2.fc5.i386. I couldn't make any direct relantionship between this versions and the ones in dovecot site so I cannot tell what dovecot version I'm using in terms of dovecot site versioning. Any help is welcome. Thanks, Ricardo

3 3

[Dovecot] CHANGE REQUEST: Move config files out of main $sysconfdir
by Brian G. Peterson 19 Nov '06

19 Nov '06

Currently, dovecot places it's config files in $sysconfdir In Makefile.am, this is defines as: confdir = $(sysconfdir) It would be far more friendly to an already overloaded /etc/ directory, and easier to locate the files, to follow the now-common convention and place files in $sysconfdir / dovecot / ... on most systems this would mean: /etc/dovecot/ If there is only a dovecot.conf, it doesn't really matter, but when additional config files get added for ldap, sql, sieve, it starts to add up. Some distributions already make this change, but placing this change in the dovecot core would make it unnecessary for downstream packagers to make a change to the core dovecot distribution files. Regards, - Brian

3 2

Re: [Dovecot] NTLM authentication from Outlook
by Lars Skovgaard 19 Nov '06

19 Nov '06

> Hi all > > I've enabled ntlm authentication in dovecot, and use dovecot sasl in > postfix as well. > > Authentication with ntlm works well from Mac OS X Mail.app, as well > as from Outlook Express, but fails with Outlook. Strangely enough, > ntml authentication works in Outlook when using smtp (via postfix), > but neither from imap or pop3 (both dovecot). As dovecot sasl handles > all authentication against a mysql userdb, this strikes me as very > strange. > > I've instructed my clients with Outlook to fetch mail using a ssl- > encrypted connection, and to send using ntlm-authentication. This > works, but I would like to have ntlm available as an option to all my > clients, without forcing them to change mail-clients. > > I've turned on auth_verbose, auth_debug and auth_debug_passwords, and > compared the passwordstring with the one calculated using dovecotpw, > and they match. The only odd thing is that the username is returned > from Outlook as an all-caps string, so user(a)domain.tld becomes > USER(a)DOMAIN.TLD. I don't know if it matters, but I don't think so, as > changing the user-login to an all-caps version doesn't solve the > problem. > > Any hints will be most welcome. > > /Lars Greetings, everyone I'm sorry, but I seem to have made a mistake regarding the passwordstring from Outlook – seems like the string I looked at was from MS Entourage... (that's what you get from trying to debug something when you're too tired to think straight). I've now enabled debugging again, and have tried logging in from Outlook with ntlm-authentication. The log-entries are as follows: Nov 16 23:29:09 SD-Server dovecot: auth(default): client in: AUTH 1 NTLM service=IMAP lip=192.168.2.2 rip=192.168.2.13 Nov 16 23:29:09 SD-Server dovecot: auth(default): client out: CONT 1 Nov 16 23:29:09 SD-Server dovecot: auth(default): client in: CONT 1 TlRM7IIog0ADQAuAAAFASgKAAAAD0AABgATVNTUAABYUEFSQkVKRFNHUlVQUAAAABGACgAAA lNQUNEU= Nov 16 23:29:09 SD-Server dovecot: auth(default): client out: CONT 1 TlRMTVNAAAAFAHgAeAAAAAAAADAA +H1XooTUAACAAAAyZ9yMNkAAdgBlAHIALgBsAG8AACYAJgBOAAAAUwBEAC0AUwBlAHIAYwBh AGwAAwAeAFMAyAC4AbABvsAAAAAGMAYRAAtAFMAZQByAHYAZQBQBAAA= Nov 16 23:29:09 SD-Server dovecot: auth(default): client in: CONT 1 TlRMAYAHwAAAAYABgAlAAAAAwADTVNTUAFQAAAAMAAAAAAAAEAH3ZyprYRPWIAAAAAAcgBkA EkATQBBAEMAWABQAAAAACsAAADAAAAGAABIAqMx1XpiwbAAAHAAcwAcABQNAEEAQwBYAFAAT ABpAHMAYQAgAFMAawBvAHYAZwBhAGAAAAAKIAgUBKAoAAAAPSQBAAAAAAAAAAAJILBz4x4RA Ixsp2rhFi8VB6g== Nov 16 23:29:09 SD-Server dovecot: auth(default): ntlm(?, 192.168.2.13): Username contains disallowed characters Nov 16 23:29:10 SD-Server dovecot: auth(default): client out: FAIL 1 The same account logs in without problems if I use a plaintext password (SSL-encrypted, since plaintext-login is disabled). in dovecot.conf I have the following: auth default { mechanisms = plain digest-md5 cram-md5 ntlm rpa } The authentication is done against a mysql-db, which until now has worked with every client I've tested (except Outlook). I have set up postfix to use dovecot-sasl, and use the same userdb for smtp-authentication. Strangely enough the exact same data is accepted when using ntml-authentication with smtp, though a warning is added to my logs. This is an example of a log-entry from an Outlook-user sending a mail: Nov 14 16:40:49 SD-Server postfix/smtpd[8354]: connect from unknown [hid.den.ip.adr] Nov 14 16:40:49 SD-Server dovecot: auth-worker(default): mysql: Connected to localhost (dovecot_auth) Nov 14 16:40:51 SD-Server postfix/smtpd[8354]: warning: unknown [hid.den.ip.adr]: SASL NTLM authentication failed: TlRMTVNTUAACAAMAZYAAQByAHAFAooAOINYZ// +97QAAAAAAAAUwBEAC0AUwBlAHIAdgBlAHIALgBsAG8AYwBhAGwAAwAeAFMARAAtAFAbABvA GMAYAAAAHgAeADAQAAAAAACYAJgBOBZQByAC4sAAAAAAA= Nov 14 16:40:51 SD-Server postfix/smtpd[8354]: AC6402D668E: client=unknown[hid.den.ip.adr], sasl_method=NTLM, sasl_username=user(a)domain.dk Nov 14 16:40:51 SD-Server postfix/cleanup[8358]: AC6402D668E: message- id=<006a01c70803$4dcd1b00$0200a8c0@acerce5220052b> Nov 14 16:41:13 SD-Server postfix/qmgr[8494]: AC6402D668E: from=<user(a)domain.dk>, size=819330, nrcpt=1 (queue active) Nov 14 16:41:16 SD-Server postfix/smtpd[8354]: disconnect from unknown [hid.den.ip.adr] Nov 14 16:41:29 SD-Server postfix/smtp[8361]: AC6402D668E: to=<user(a)otherdomain.dk>, relay=smtp.domain.dk[hid.den.ip.adr]:25, delay=37, delays=22/0.08/0.06/15, dsn=2.0.0, status=sent (250 156794624 mailfe12 Message accepted for delivery) Nov 14 16:41:29 SD-Server postfix/qmgr[8494]: AC6402D668E: removed The same warning is issued from postfix when a user sends mail from Outlook Express, but not when the same user sends from Thunderbird or Mail.app. In fact, I've only seen these problems when the users are using MS products. I really hope someone can shed some light on what is going on. Best regards Lars

2 1

[Dovecot] dovecot:IMAP(user) killed with signal 6
by Spil Oss 18 Nov '06

18 Nov '06

Hi all, After rc10 I have problems with imap and imaps Hi all, After rc10 I have problems with imap and imaps Nov 16 15:42:39 beastie dovecot: IMAP(user1): open(/home/user1/Maildir/.MeldWelSpam/dovecot-keywords) failed: Permission denied Nov 16 15:44:09 beastie dovecot: IMAP(user2): open(/home/user2/Maildir/.MeldWelSpam/dovecot-keywords) failed: Permission denied Nov 16 15:44:09 beastie dovecot: IMAP(user2): file maildir-keywords.c: line 222 (maildir_keywords_lookup_or_create): assertion failed: (mk->synced) Nov 16 15:44:09 beastie dovecot: child 98798 (imap) killed with signal 6 Nov 16 15:46:10 beastie dovecot: IMAP(user2): open(/home/user2/Maildir/.MeldWelSpam/dovecot-keywords) failed: Permission denied Nov 16 15:46:10 beastie dovecot: IMAP(user2): file maildir-keywords.c: line 222 (maildir_keywords_lookup_or_create): assertion failed: (mk->synced) Nov 16 15:46:10 beastie dovecot: child 98819 (imap) killed with signal 6 The Permission denied messages where there in rc10 as well, but that was not causing problems. These folders are symlinks to shared spam and ham folders for spamassassin learning. Any clue on how to fix this? FreeBSD-i386 6.1-RELEASE-p10 dovecot-1.0.r13 from ports Kind regards, Spil.

3 3

[Dovecot] updated gentoo ebuild provides dovecot-sieve
by Brian G. Peterson 18 Nov '06

18 Nov '06

I'm hoping that there are some Gentoo users on this list who will chime in on a bug that is near and dear to my heart. We've created an updated Gentoo ebuild that adds a sieve USE flag and builds dovecot-sieve if the use flag is enabled. The gentoo bug is here: https://bugs.gentoo.org/show_bug.cgi?id=141743 and the ebuild is available as an attachment to that bug, or as a patch attachment (in case you're not running rc14, or just prefer the look of a unified diff) Any gentoo users on this list are urged to install from the ebuild/patch on the bug, and *report back* on the bug or this list, so that the Gentoo dev will know that it's safe to add this to portage CVS. Thank You. Regards, - Brian

2 1

[Dovecot] Dovecot LDA, LDAP, Postfix and Spawning programs..
by Jorgen Lundman 18 Nov '06

18 Nov '06

Qmail, when using LDAP, a user can specify delvieryProgramPath, or a .qmail file, to launch something like procmail. Qmail correctly setuid() to the uids set for the user in LDAP, as well as set up the common env vars (HOME, USER, MAILDIR). We moved to Postfix but found that it is quite lacking in the features supported when it comes to "virtual" users. No .forward, and if you set up an alternate transport, they are run as "any user but root, nor postfix, nor the virtual-user's uid". And worse, does not even supply the HOME/MAILDIR values to transport delivery plugin. (Forcing it to getpwnam() or similar). I have an option to make my own setuid program to query LDAP (postmap -q would work), setuid() and call, say, procmail. It has been suggested I can use "maildrop" as it can talk to LDAP. However, I picked "Dovecot" as my pop3/imap program due to an irrational dislike of Courier imap. So, if I tried Dovecot-LDA, would it support the user optionally having a ".forward" file, or perhaps the LDAP attribute deliveryProgramPath, or some other way to filter based on subject/body to sort, and/or forward, mail? If it can use LDAP, will it setuid() to the users uid (as set in LDAP, assuming I cook the LDAP conf entries correctly) when delivering(I'd hope so!) and running external filters? I am still running rc10, which works well but flips out regularly. (Previously mentioned 'too many files open' bug, some leaks in locks) I will upgrade when the LDAP changes are deemed stable. Lund -- Jorgen Lundman | <lundman(a)lundman.net> Unix Administrator | +81 (0)3 -5456-2687 ext 1017 (work) Shibuya-ku, Tokyo | +81 (0)90-5578-8500 (cell) Japan | +81 (0)3 -3375-1767 (home)

2 1

[Dovecot] Failed Assert in RC13 on FC4
by Joseph D. Wagner 18 Nov '06

18 Nov '06

I received the following notices from logwatch: dovecot: IMAP(userid): file ioloop.c: line 22 (io_add): assertion failed: (fd >= 0): 1 Time(s) dovecot: child 16976 (imap) killed with signal 6: 1 Time(s) Please let me know if you need any further information from me. Joseph D. Wagner

2 1

[Dovecot] two assertion failures
by Mikhail Teterin 18 Nov '06

18 Nov '06

Hello! I was able to overcome the earlier-reported problems (of dovecot treating the standard mailboxes in /var/mail/ as directories) by specifying mail_location (continuing to use the 0.99-era dovecot.conf did not work). Then I started seeing assertion-failures like: file istream-raw-mbox.c: line 499 (istream_raw_mbox_get_body_size): assertion failed: (rstream->mail_size != (uoff_t)-1) these disappeared, when I disabled mmap-access (mmap is limited to 1Gb on FreeBSD/i386), although dovecot-0.99 worked... I can now get to my mail again, but every once in a while the following assertion kills the connection: file mail-transaction-log.c: line 273 (mail_transaction_log_close): assertion failed: (log->files == NULL) Please, advise... Thanks! -mi

2 1

[Dovecot] Auth checking also the service
by Alex 18 Nov '06

18 Nov '06

Hello everyone. I'm switching to dovecot from courier-imap and after some problems with Apple Mail client, now everything seems to be fine. The only problem that I have not solved yet is to check also the service (pop3, pop3s, imap, imaps) in the authentication phase. In courier-authlib I do this: MYSQL_SELECT_CLAUSE SELECT username, \ password, \ "", \ 1002, \ 1003, \ '/vmail', \ maildir, \ quota, \ name, \ "" \ FROM mailbox \ WHERE username="$(local_part)@$(domain)" \ AND active=1 \ AND $(service)=1 where $(service) can be pop3, pop3s, imap or imaps. Is it possible to do a similar thing in dovecot? Thank you in advance, Alex

3 4

[Dovecot] sieve newbie question
by matteo＠progettomio.net 17 Nov '06

17 Nov '06

Hi all, can you clarify my doubts about sieve? I understand what is it, but what's the different between use exim with rules + dovecot and use exim + dovecot-lda + sieve rules? i can create many kind of rules on exim, then i don't get the difference. if someone is so kind to explain me the main points i'll appreciate it! Regards, Matteo

3 3

[Dovecot] Help needed
by Ricardo Dias Campos 17 Nov '06

17 Nov '06

Hi. Days ago I sent a message to this list asking for help on a problem that seemed to me to be old: dovecot hangs and dovecot-auth posts log messages like: Nov 16 17:04:39 netuno dovecot: imap-login: Can't connect to auth server at default: Resource temporarily unavailable Nov 16 17:04:42 netuno dovecot: pop3-login: Can't connect to auth server at default: Resource temporarily unavailable Unfortunatelly when this happens the only way to recover is to restart dovecot. After I while I begun to clean the dovecot-auth processes (defunct or not) that remain in the process list and the cycle of running/hunging restart from 1 hang a day until it reaches 1 hang each 10 minutes, when I kill dovecot-auth again. I've seen some days ago some messages related to this problem but they were inconclusive, meaning that they didn't point to a solution. Any help is welcome. Thanks. Ricardo

1 0

[Dovecot] LDA Question
by Jeff 17 Nov '06

17 Nov '06

I need some advice about replacing maildrop with the Dovecot LDA. I need to replicate a setup that uses postfix+maildrop+spamassassin. We'll be using Dovecot 1rc13. In the current setup, maildrop reads a file called .mailfilter in each user's folder, then call spamassassin according to the user's preferences. The file is simple, and looks like this -- if ( $SIZE > 20971520 ) { EXITCODE=77 echo "Your email was rejected because it exceeded limit of 20 MB" exit } if ( $SIZE < 26144 ) { exception { xfilter "/usr/local/bin/spamc -u user(a)domain.com" } } exception { to "$DEFAULT/Maildir/" } What is the most straightforward way to have 'Deliver' do the same thing, without changing the way that SA gets called? Apologies in advance if this is a boneheaded question. I've been sorting through Sieve documentation and HOWTOs and I see everything but what I need.

2 1

[Dovecot] maildirsize update error?
by Maykel Moya 16 Nov '06

16 Nov '06

According to [1], Trash is a reserverd folder name. When moving a message to it, maildirsize should be update with a negative byte count. If I move a message from any folder to Trash, maildirsize gets two lines, one positive and one negative. The problem is that a user can't move messages to Trash while being overquota because the positive entry goes before the negative. I'm using dovecot-1.0rc14. Regards maykel [1] http://www.inter7.com/courierimap/README.maildirquota.html

1 0

[Dovecot] Dovecot tries to create bogus files in /var/mail
by Mikhail Teterin 16 Nov '06

16 Nov '06

After upgrading from 0.99.2 to 1.0rc14, I started seeing log-entries like: Nov 16 12:56:22 corbulon dovecot: IMAP(mksarch): mkdir_parents(/var/mail/mksarch/.imap/INBOX) failed: Not a directory Nov 16 12:56:51 corbulon dovecot: IMAP(anat): open(/var/mail/anat/inbox, O_CREAT) failed: Not a directory Nov 16 12:56:51 corbulon dovecot: IMAP(anat): mkdir_parents(/var/mail/anat/.imap/INBOX) failed: Not a directory And my IMAP client (KMail) shows up error message with "Internal server error". The files in /var/mail/ are just that -- files (in the bad old Unix mbox format), and not directories, why is dovecot treating them as directories? Please advise... Thanks! -mi

1 0