- dovecot - dovecot.org

[Dovecot] update quota
by Alex 30 Nov '06

30 Nov '06

I'm working with last dovecot r15 and exim 4.63 When I download my emails, pop3, dovecot not upadtes the maildirsize file

2 1

[Dovecot] lmtp: help needed
by Leonardo Lanzi 30 Nov '06

30 Nov '06

Hi all, parsing the mailing list archive, it seems that the lmtp-server will not be developed soon, so I'm looking for someone that could help me in writing one, even if not the best one. That's why: I've just started to study dovecot, as I was recruited, just about forced, to help The System Manager of our University in the global e-mail migration - more than 37'000 users, 440 mailing lists, everything synchronized with administrative databases and so on - from open-vms (yes... you have not sight problems: OpenVMS ... please don't blame us). In particular, we have (we'd like so much) to directly deliver from a front-end load-balanced anti-spam&virus all "good" messages into maildirs, updating at the same time the indexes for dovecot. Our idea is to write an lmtp, possibly not from scratch; we have already a threaded server, recently born as a raw smtp server to test the antivirus and antispam system under heavy load (before to start the migration), that can be converted to lmtp protocol, but we lack of information on the dovecot API for delivering in a "dovecot-way". As often occurs, we have not months to get it done, therefore _any_ kind of suggestion will be very much appreciated. Thank you all for the help, and patience! -- Leonardo Lanzi Department of Physics - University of Florence - Italy -- PS - Examples of help: 1. "The code is self-explaining, but obviously you're too old to learn: accept to be in the mist, and switch to cyrus" 2. "the following n-functions ... of deliver can accept your data from memory and do all the job" 3. "I've already done everything, download it at the following url..." 3a. "I've already done everything, but you must send me, _before_, your smtp stressing server, or all your tests on latency of irq handlers with 2.6 kernel, or at least one 18-year-old scottish-malt-whisky bottle!"

3 3

[Dovecot] Subfolders with Thunderbird and maildir?
by Andrew Z 30 Nov '06

30 Nov '06

I setup a test dovecot-1.0-0.beta8.2.fc5 and left most of the settings as the defaults. In Thunderbird 1.5.0.8 Windows, when I tried to create a subfolder named "subfolder" under INBOX, it showed up as the same level a INBOX and with the name "INBOX^subfolder". I was able to manually create a subfolder using "mkdir ~/mail/test_manual_subfolder; touch ~/mail_test_subfolder/blah" and then subscribing to it. That's too much work. :) Now when I try to create a subfolder of a non-inbox folder, nothing happens (not even an error). Screen shot: http://img452.imageshack.us/my.php?image=subfoldersthunderbird15ao6.png The Dovecot system is Fedora Core 5 x86 and an NFS client for /home. I'm considering switching from Trustix, UW-IMAP, and mbox. I'm also considering changing INBOX to a Maildir (not /var/spool/mail/%u). Andrew

2 2

[Dovecot] MAILDIR environment
by adcx＠server101.com 29 Nov '06

29 Nov '06

from docs/mail-storages.txt: "Also as a special case, if MAILDIR environment exists, maildir storage is used with the directory specified in it." Forgive me if this seems obvious, but is this talking about setting MAILDIR as an enivornment variable? I have it set on my system in both /etc/profile and ~/.bash_profile: MAILDIR=/path/to/maildir/ export MAILDIR and have confirmed this worked by running 'echo $MAILDIR'. I've logged the user in question out and then in again, as well as restarting dovecot but it still defaults to checking ~/Maildir when the user logs in. Setting the location using default_mail_env is not an option here as I need the fallback behaviour that occurs when default_mail_env is not set. Any advice appreciated.

2 1

[Dovecot] Redundant shared mail store?
by Jasper Bryant-Greene 29 Nov '06

29 Nov '06

Hi guys I'm about to embark on a project replacing a legacy single mail server running proprietary software with a cluster of Dovecot servers. We clearly need a shared mail store for these servers, but we are not happy with simply using a server running NFS as this becomes a single point of failure. What have other people used? AFAICT our options are: * A shared block device (Fibre Channel, iSCSI, ATAoE etc) running GFS or similar to allow multiple servers to access it concurrently * Two or more NFS units, either with built-in support for replication of FS changes and failover, or with scripts for achieving this functionality I prefer option 1, although it's expensive. What have other people used? Do we have other options? TIA -- Jasper Bryant-Greene Director Album Limited jasper(a)albumltd.co.nz +64 21 708 334 / 0800 425 286 http://www.albumltd.co.nz/

4 3

[Dovecot] Quota problems on uidlist files
by James Nunnerley 29 Nov '06

29 Nov '06

Hi All, Please excuse me for this somewhat a slightly uneducated explanation of a problem we are experiencing. I'm more a web developer rather than a sysadmin, and have only recently been looking at how exactly dovecot works. We're having a problem when users/groups quotas are reached on our server platform. Our platform bases quotas on groups - i.e. domains, so a single user has a user username and group of their domain; and the domain has a set amount of space available. This means that if they then try and access their email, via either imap or in most cases webmail, it would seem that dovecot is unable to create the dovecot-uidlist file - which makes complete sense, because it's running as that user and under the group as detailed above.. We've tried changing a pre-existing file to have group ownership of nobody, but from what we can gather, this file is not actually updated, but deleted and recreated when changes occur. One solution would be to take the dovecot-uidlist file out of the mail directory structure, on which the quotas are enforced, but this is not configurable in dovecot. Alternatively, having someway of changing to ownership of the file would also get around this problem. Does anyone have any experience of either a work around for this, or something which we can change in dovecot that will allow users to create a dovecot file, even if they are over quotas? Many thanks James James Nunnerley Applications Developer Namesco Limited

2 1

[Dovecot] [Fwd: Re: Authentication]
by "M. Tolga Özses" 29 Nov '06

29 Nov '06

Sorry, I forgot to Reply all -------- Original Message -------- Subject: Re: [Dovecot] Authentication Date: Wed, 29 Nov 2006 09:49:42 +0200 From: "M. Tolga Özses" <mtozses(a)sabanciuniv.edu> To: eric <eric(a)ccat.co.nz> References: <456D3221.2030900(a)ccat.co.nz> eric wrote: > 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 It is disable_plaintext_auth = no for me, and it works well > mail extra group = users It should be mail_extra_groups = mail, same > 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? > > -- M. Tolga Özses Bilgi Teknolojisi Sabanci Üniversitesi Orhanli 34956 Tuzla Istanbul Tel: (216) 483 91 98 Web: http://people.sabanciuniv.edu/mtozses -- M. Tolga Özses Bilgi Teknolojisi Sabanci Üniversitesi Orhanli 34956 Tuzla Istanbul Tel: (216) 483 91 98 Web: http://people.sabanciuniv.edu/mtozses

3 2

[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