- dovecot - dovecot.org

[Dovecot] can I hide or delete the message "don't delete this message -- folder internal data" ?
by Felipe Stuardo 22 Jan '06

22 Jan '06

sorry for my english... is possible that i can hide or delete the message "don't delete this message -- folder internal data" ? this message is see from all accounts of my mail server. i have a system with: Fedora Core 4 dovecot-0.99.14-4.fc4 sendmail-8.13.4-2 thanks _______________________________________________________________________ Advertencia: Este mensaje contiene la opinion personal del remitente y la Universidad Catolica Nuestra Senora de la Asuncion no asume responsabilidad alguna con relacion al contenido del presente mensaje. Cualquier consulta realizar por favor a sysadmin(a)uca.edu.py . Protected by LED

3 2

[Dovecot] in a major jam... authentication
by tallison1 22 Jan '06

22 Jan '06

I was upgrading my debian box and managed to upgrade my dovecot installation at the same time. I wasn't planning on it, but it came along just the same. I took some notes on what I thought I needed to change, but apparently it wasn't enough. I've been running this for quite some time now with pgsql authentication and it's been one of those nice applications that always behave themselves. Until now. I can connect to the database. But I always fail the authentication. From the logs I'm coming in on a PLAIN authentication and failing on "password mismatch" The database hasn't changed the password in years. The database stores the password as (I believe) an md5 encryption of the real password. Whatever it is, it is definitely encrypted in the table. What I had in my configuration file was something like this: disable_plaintext_auth = no (this was marked as the default and I enforced it in the new file) auth_mechanisms = plain auth_passdb = pgsql:/etc/dovecot/dovecot-pgsql.conf auth_user = root login = imap I have updated the configuration as follows: dovecot-pgsql.conf 'driver = pgsql' 'default_pass_scheme = PLAIN-MD5' ( I tried changing this to PLAIN but it didn't help ) dovecot.conf protocols = imap disable_plaintext_auth = no protocol imap { } protocol pop3 { } auth default { mechanisms = plain passdb pam { } passdb sql { args = /etc/dovecot/dovecot-pgsql.conf } userdb passwd { } user = root } I'm not sure what to try now, all I know is that my IMAP server is just dead and I'm unable to get the authentication working again. I can't find much that says how to set this up again and am reluctant to just start trying stuff.

3 2

[Dovecot] plain text auth
by ohp＠pyrenet.fr 22 Jan '06

22 Jan '06

Hi everyone, This is my second try with dovecot, and still no luck. What I want is twig to work with dovecot on the localhost address . I need to authenticate through pam for real accounts and through pgsql for virtual ones. I just cant autenticate: logs are : imap-:login: Authenticate PLAIN failed: Unsupported authentication mechanism or: Aborted login: method = PLAIN Could someone please share a working config file that does what I want? I'm struggling for weeks now both on tyhe alpha5 and beta1 versions. TIA -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) 15, Chemin des Monges +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: ohp(a)pyrenet.fr ------------------------------------------------------------------------------ Make your life a dream, make your dream a reality. (St Exupery)

5 8

[Dovecot] INBOX as either mbox or Maildir
by Tom Alsberg 22 Jan '06

22 Jan '06

In Dovecot 0.99, I recall somewhere I read it was possible for INBOX to be both a Maildir and an mbox in the same configuration (either automatically detected, or depending on the existence in a different location). Perhaps I was wrong, I'm not sure. Any way, I now became interested in this sort of setup: Most users have their spool an mbox in /var/mail/<username>, and then they (or their MUA) have to move read mail from there to ~/mbox or something like that (a state in which users use the spool as a long-time storage space is unacceptable, and we have measures to avoid it). However, for those that will access their mail only via IMAP, it will be easier to set in .forward or something like that automatic delivery directly to their mailbox - some Maildir in their home directory (there can then be a link from /var/mail or /var/maildir or whatever to there), which will contain both read and new messages. In such a case one would want INBOX to be that main mailbox. Would it be possible to set Dovecot to either automatically detect whether /var/mail/<username> is a Maildir or mbox (which relates to my interest in mixing maildirs and mboxes in one namespace which I have written about several months ago) or to configure several options for INBOX with the first one found used? Cheers, -- Tom -- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.

2 1

Re: [Dovecot] Login user doesn't exist: dovecot
by Anne Wilson 21 Jan '06

21 Jan '06

On Thursday 19 Jan 2006 22:37, Willem Riede wrote: > On 01/19/2006 05:11:30 PM, Anne Wilson wrote: > > I think that maybe I should uninstall it and start again. > > Now that you're running Fedora you should use a RPM to install > dovecot. I can help you with that by getting you my working beta1 > src.rpm to rebuild, if you like. > Hi, William. Thanks for the offer. I'm a bit puzzled at the moment as to where I've actually got to. This is what's happened: I had original made an rpm with checkinstall, so I removed the dovecot user, so that a new install would set it up with the expected UID and GID, and removed the rpm. My 'bright' idea was that I would install the official Fedora 0.99.14, then install 1.0bet1 over it. I had been assured earlier that it would install over the executables, so it seemed reasonable. I got 0.99.14 on, but could not find the dovecot.conf.example or dovecot.conf to check paths, which worried me a bit, so I thought that if I attempted a login it would give me errors that would define a path. For the first time ever, it logged in! What's more, I can see my imap directories on another box. The only dovecot.conf that I know about is the copy that was in /home/anne. What do you think is happening? If all is working I will leave well alone. This is to be a temporary mail server while I do an upgrade. I don't want to do any more work on it than I need to, because I will be doing it over again, for a permanent install, on the upgraded box in a week or so. Anne -- Registered Linux User No.293302 (http://counter.li.org/)

5 5

[Dovecot] beta1: assert due to hard fs quota
by Jeff A. Earickson 20 Jan '06

20 Jan '06

Hi, In the "for what it is worth" category... The following assert popped up in beta1 on Solaris 9 this morning: imap(user): file mail-index-view-sync.c: line 155 (view_sync_get_expunges): assertion failed: (ret == 0) The user had hit a hard disk quota on their home directory, ie where the indexes go. Dovecot cored with a zero-byte core file in the user's home directory, naturally. Jeff Earickson Colby College

1 0

[Dovecot] Login user doesn't exist: dovecot
by Anne Wilson 20 Jan '06

20 Jan '06

After completely trashing my system a few days ago, I now have FC4 running, and have compiled dovecot-1.-beta1. Everything is placed in a different place from the debian install, so it's possible that I have a path problem. Attempting to start dovecot in a root console brings up the line Login user doesn't exist: dovecot Advice, please? Anne

5 11

[Dovecot] Major CPU spike for SSL parameters?
by Todd Vierling 20 Jan '06

20 Jan '06

I went from a nightly of about 20051117 or so (about alpha4 generation) to 1.0beta1 yesterday, and dovecot is now spinning the CPU furiously apparently every ~10 minutes per: Jan 18 13:04:36 server dovecot: SSL parameters regeneration completed Jan 18 13:14:14 server dovecot: SSL parameters regeneration completed Jan 18 13:24:00 server dovecot: SSL parameters regeneration completed Jan 18 13:37:09 server dovecot: SSL parameters regeneration completed Jan 18 13:44:21 server dovecot: SSL parameters regeneration completed Jan 18 13:54:37 server dovecot: SSL parameters regeneration completed Jan 18 14:04:03 server dovecot: SSL parameters regeneration completed Jan 18 14:14:58 server dovecot: SSL parameters regeneration completed Jan 18 14:24:03 server dovecot: SSL parameters regeneration completed Jan 18 14:34:18 server dovecot: SSL parameters regeneration completed Jan 18 14:44:11 server dovecot: SSL parameters regeneration completed Jan 18 14:53:44 server dovecot: SSL parameters regeneration completed Jan 18 15:04:16 server dovecot: SSL parameters regeneration completed Jan 18 15:13:59 server dovecot: SSL parameters regeneration completed Jan 18 15:25:22 server dovecot: SSL parameters regeneration completed Jan 18 15:33:58 server dovecot: SSL parameters regeneration completed Jan 18 15:44:03 server dovecot: SSL parameters regeneration completed Jan 18 15:54:13 server dovecot: SSL parameters regeneration completed Note that this is not the DH parameter generation; that completed on the first run, as documented. This is impacting other processes on the machine, and it seems a bit of a radical change. Is the internal default meant to be this short...? I'm going to attempt to set "ssl_parameters_regenerate" explicitly, but I'd like to stick with builtin defaults wherever possible. (Perhaps this regeneration could also be made a little friendlier on the machine, by forking and using setpriority() to lower the CPU demand of this work from the default nice level of the main daemon.) -- -- Todd Vierling <tv(a)duh.org> <tv(a)pobox.com> <todd(a)vierling.name>

3 5

[Dovecot] beta1: how to use quota plugin???
by Jeff A. Earickson 20 Jan '06

20 Jan '06

Hi, After searching gmane.mail.imap.dovecot on the topic, and wiki.dovecot.org, I'm still clueless on how to use RFC 2087 quotas in dovecot with the quota plugin. How come no wiki doc? My setup: Solaris 9, mbox format. Both the filesystem for INBOXes (/var/mail) and the user's home directories have filesystem-based quotas imposed. For example: % quota -v joeblow Disk quotas for joeblow (uid 20737): Filesystem usage quota limit /export/home 955 298000 302400 (where indices and mail folders go) /var/mail 530 151200 204800 (where joeblow's INBOX lives) If joeblow connects via dovecot IMAP, I want our webmail code (horde/imp) to tell him his disk quotas to keep him out of trouble. Horde/Imp (2.2.5) has quota code that says it works with Courier imap. Dovecot is supposed to be Courier compatible. How do I get the quota info out of Dovecot and down to Horde/IMP? Jeff Earickson Colby College

3 3

[Dovecot] Migrating from UW IMAP - pine - Thunderbird - squirrelmail
by Gerhard Wiesinger 19 Jan '06

19 Jan '06

Hello! In this email you can find a configuration primer for a Migration from UW IMAP with pine, Thunderbird and squirrelmail as client. For compatibility the mbox format is used. A description for pine with imap acces without entering any password is also discussed. Please use dovecot 1.0beta1 or later for correct handling with pine. Short overview of Mail folders: =============================== | Used | elm | pine | Thunderbird | squirrelmail | UW imapd | dovecot | Base directoy | ~/Mail | ~/Mail | ~/mail | as configured | mail | | | Sent Folder | ~/Mail/sent | ~/Mail/sent | ~/mail/sent-mail | Sent | Sent | | | Trash Folder | ~/Mail/Trash | | - | Trash | Trash | | | Drafts Folder | ~/Mail/Drafts | | saved-messages | Drafts | Drafts | | | Templates | ~/Mail/Templates | | | Templates | | | | Unsent Folder | wie Thunderbird | | | Local Folders/Unsent Messages | | | | Postponed | | | postponed-msgs | | | | | Canceled Mail | | ~/Canceled.mail | ~/dead.letter | | | | | Personal namespace | | | | | | | | Public namespace | | | | | | #news | | Other Users | | | | | | | | pine setup: =========== SETUP(S)/collectionLists(L)/Mail Just add the following to Server: localhost/notls Before: Nickname : Mail Server : Path : Mail/ View : After: Nickname : Mail Server : localhost/notls Path : Mail/ View : In ~/.pinerc modify the following configuration parameters: mail-check-interval=15 rsh-open-timeout=30000 rsh-path= rsh-command=/usr/sbin/dovecot --exec-mail imap # For large Mailboxes tcp-read-warning-timeout=180 For details have a look at: http://www.unix.org.ua/orelly/networking_2ndEd/ssh/ch11_03.htm http://www.cs.unc.edu/cgi-bin/howto?howto=pine-imap http://www.ii.com/internet/messaging/pine/ http://www.umanitoba.ca/acn/docs/pine/pine-imap.html Migration from UW Imapd to dovecot: =================================== Disable UW Imapd in xinetd http://wiki.dovecot.org/Migration Migrate Mailboxes: http://wiki.dovecot.org/uw2dovecot.sh or cd $USER cp .mailboxlist .subscriptions dovecot configuration: Config (/etc/dovecot.conf): UW Imapd compatible protocols = imaps default_mail_env = mbox:~:INBOX=/var/mail/%u mail_full_filesystem_access = yes mbox_read_locks = fcntl mbox_write_locks = fcntl mbox_lazy_writes=no Self signed Certificate for SSL: cd /etc/pki/dovecot/private openssl genrsa -out dovecot.pem 2048 openssl req -new -x509 -nodes -sha1 -days 3650 -key dovecot.pem >../dovecot.pem Enter the data for the certificate http://sial.org/howto/openssl/self-signed/ dovecot debugging: ================== Config (/etc/dovecot.conf): #GW: mail_executable = /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap Directory ~/dovecot.rawlog must exist and the input/output will be logged there For ethereal debugging use the following dovecot configuration: Sniffing: #GW: protocols = imap imaps #GW: disable_plaintext_auth = no maildir/mbox documentation: =========================== http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi?coll=fw&db=man&fname… http://people.redhat.com/rkeech/maildir-migration.txt squirrelmail: ============= $use_imap_tls = true; $imapPort = 993; $imap_server_type ='dovecot'; $optional_delimiter = 'detect'; $force_username_lowercase = true; $default_folder_prefix = '~/Mail/'; $sent_folder = 'sent'; $show_prefix_option = false; $show_contain_subfolders_option = false; Thunderbird Plugins =================== With imap Folder the Xpunge plugin is very usefull to have consitent mailboxes. Xpunge https://addons.mozilla.org/extensions/moreinfo.php?application=thunderbird&… http://www.cs.ualberta.ca/~tegos/mozilla/tb/ Hope is helps. Feedback is welcome. Ciao, Gerhard

1 0

[Dovecot] no inbox error?
by John Woodell 19 Jan '06

19 Jan '06

When a new user has no inbox (has not received a message), the box client shows an error dialog. Is there any way to surpress this... besides touching an empty inbox for all valid accounts?

1 0

[Dovecot] Dovecot + mysql on CentOs 4.2 64-bit...
by Anders Kongsted 19 Jan '06

19 Jan '06

Hi, I'm in trouble. Is there any how-to'es to set up a server as described in the subject? Regards Anders

1 0

[Dovecot] Donating
by Timo Sirainen 19 Jan '06

19 Jan '06

I've never really liked all these donation buttons in web pages, or receiving donations at all, but as some extra money could make my life easier in the next few months, I thought I'd give it a try. http://dovecot.org/donate.html (And if you're wondering how I could still promise those 1000 euros for a security hole, I've a credit card but I'd rather not use it :) Also I'm not really expecting for anyone to find holes at least anytime soon.)

9 10

[Dovecot] problems compiling
by Imre Gergely 19 Jan '06

19 Jan '06

hi i downloaded dovecot-1.0.beta1.tar.gz, did a rpmbuild -ta dovecot-1.0.beta1.tar.gz (which uses the dovecot.spec from the tar.gz), and got the following: Making install in quota make[3]: Entering directory `/usr/src/gimre/rpm2/BUILD/dovecot-1.0.beta1/src/plugins/quota' make[4]: Entering directory `/usr/src/gimre/rpm2/BUILD/dovecot-1.0.beta1/src/plugins/quota' mkdir -p -- /usr/lib/dovecot/imap /usr/lib/dovecot/lda mkdir: cannot create directory `/usr/lib/dovecot': Permission denied mkdir: cannot create directory `/usr/lib/dovecot': Permission denied make[4]: *** [install-exec-local] Error 1 make[4]: Leaving directory `/usr/src/gimre/rpm2/BUILD/dovecot-1.0.beta1/src/plugins/quota' make[3]: *** [install-am] Error 2 so everything did compile alright, but it has some problems with installing the plugins. and i dunno why it tries to create those directories in the root directory. of course i'm compiling it as a non-root users, so it doesn't have any write permissions. and it normally shouldn't have to do an install in directories other then buildroot. so what's the catch? if i disable from the src/Makefile.in to not compile the plugins, everything works fine, i got a nice rpm file. i'm on Fedora Core 4. any help would be appreciated. thx.

5 7

[Dovecot] dovecot lda with sendmail
by Michael Surette 18 Jan '06

18 Jan '06

I'm trying to set up dovecot's deliver program as the lda for sendmail. I seem to need a config file for it '/etc/dovecot-deliver.conf'. Is there any documentation for this configuration file and it's contents? sendmail will call it under the recipient's uid, and all it has to do is drop the message into the proper maildir as defined in /etc/dovecot.conf and update the indexes. Mike

2 2

[Dovecot] still strugling
by ohp＠pyrenet.fr 18 Jan '06

18 Jan '06

Hi all, After I posted yesterday, I'm still struggling with dovecot 1.0beta1 I installed it on openbsd with no problem. But I can't get it to authenticate plaintext on Unixware. I had to add two include files <sys/types.h> and <sys/mkdev.h> in compat.h because minor and major where undefined on unixware. I doubt that could fail... What's wrong with that conf: ## Dovecot 1.0 configuration file # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr/local --sysconfdir=/usr/local/etc --localstatedir=/var # --with-ssldir=/etc/ssl # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s protocols = imap pop3 # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. If you want to specify ports # for each service, you will need to configure these settings inside the # protocol imap/pop3 { ... } section, so you can specify different ports # for IMAP/POP3. #listen = * # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = # Disable SSL/TLS support. ssl_disable = yes # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf #ssl_cert_file = /etc/ssl/certs/dovecot.pem #ssl_key_file = /etc/ssl/private/dovecot.pem # File containing trusted SSL certificate authorities. Usually not needed. #ssl_ca_file = # Request client to send a certificate. #ssl_verify_client_cert = no # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 24 # SSL ciphers to use #ssl_cipher_list = ALL:!LOW # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. disable_plaintext_auth = no # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). #log_path = # For informational messages, use this logfile instead of the default #info_log_path = # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " # Syslog facility to use if you're logging to syslog. Usually if you don't # want to use "mail", you'll use local0..local7. Also other standard # facilities are supported. #syslog_facility = mail ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = /var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. # http://wiki.dovecot.org/Rootless #login_chroot = yes # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. # Note that this user is NOT used to access mails. # http://wiki.dovecot.org/UserIds login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 32 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. login_process_per_connection = no # Number of login processes to create. If login_process_per_connection is # yes, this is the number of extra processes waiting for users to log in. login_processes_count = 1 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_connection # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 # Greeting message for clients. #login_greeting = Dovecot ready. # Space-separated list of elements we want to log. The elements which have # a non-empty variable value are joined together to form a comma-separated # string. #login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c # Login log format. %$ contains login_log_format_elements string, %s contains # the data we want to log. #login_log_format = %$: %s ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). verbose_proctitle = yes # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. first_valid_gid = 0 #last_valid_gid = 0 # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. mail_extra_groups = mail # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See doc/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden for # specific users in user database by giving /./ in user's home directory # (eg. /home/./user chroots into /home). Note that usually there is no real # need to do chrooting, Dovecot doesn't allow users to access files outside # their mail directory anyway. #mail_chroot = # Enable mail process debugging. This can help you figure out why Dovecot # isn't finding your mails. mail_debug = yes # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # doc/mail-storages.txt. There's a few special variables you can use, eg.: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if there's no domain # %h - home directory # # See doc/variables.txt for full list. Some examples: # # default_mail_env = maildir:/var/mail/%1u/%u/Maildir # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # default_mail_env = mbox:/var/spool/mail/%u # If you need to set multiple mailbox locations or want to change default # namespace settings, you can do it by defining namespace sections: # # You can have private, shared and public namespaces. The only difference # between them is how Dovecot announces them to client via NAMESPACE # extension. Shared namespaces are meant for user-owned mailboxes which are # shared to other users, while public namespaces are for more globally # accessible mailboxes. # # REMEMBER: If you add any namespaces, the default namespace must be added # explicitly, ie. default_mail_env does nothing unless you have a namespace # without a location setting. Default namespace is simply done by having a # namespace with empty prefix. #namespace private { # Hierarchy separator to use. You should use the same separator for all # namespaces or some clients get confused. '/' is usually a good one. #separator = / # Prefix required to access this namespace. This needs to be different for # all namespaces. For example "Public/". #prefix = # Physical location of the mailbox. This is in same format as # default_mail_env, which is also the default for it. #location = # There can be only one INBOX, and this setting defines which namespace # has it. #inbox = yes # If namespace is hidden, it's not advertised to clients via NAMESPACE # extension or shown in LIST replies. This is mostly useful when converting # from another server with different namespaces which you want to depricate # but still keep working. For example you can create hidden namespaces with # prefixes "~/mail/", "~%u/mail/" and "mail/". #hidden = yes #} # Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # # flags, date.sent, date.received, size.virtual, size.physical # mime.parts, imap.body, imap.bodystructure # # Different IMAP clients work in different ways, so they benefit from # different cached fields. Some do not benefit from them at all. Caching more # than necessary generates useless disk I/O, so you don't want to do that # either. # # Dovecot attempts to automatically figure out what client wants and it keeps # only that. However the first few times a mailbox is opened, Dovecot hasn't # yet figured out what client needs, so it may not perform optimally. If you # know what fields the majority of your clients need, it may be useful to set # these fields by hand. If client doesn't actually use them, Dovecot will # eventually drop them. # # Usually you should just leave this field alone. The potential benefits are # typically unnoticeable. #mail_cache_fields = # Space-separated list of fields that Dovecot should never save to cache file. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # When IDLE command is running, mailbox is checked once in a while to see if # there are any new mails or other changes. This setting defines the minimum # time to wait between those checks. Dovecot is however able to use dnotify # and inotify with Linux to reply immediately after the change occurs. #mailbox_idle_check_interval = 30 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no # Maximum allowed length for mail keyword name. It's only forced when trying # to create new keywords. #mail_max_keyword_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. # Also note that if other software reads the mboxes/maildirs, they may handle # the extra CRs wrong and cause problems. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. # Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes. #mail_read_mmaped = no # Don't use mmap() at all. This is required if you store indexes in remote # filesystems (NFS or clustered filesystem). #mmap_disable = no # Don't write() to mmaped files. This is required for some operating systems # which use separate caches for them, such as OpenBSD. #mmap_no_write = no # Locking method for index files. Alternatives are fcntl, flock and dotlock. # Dotlocking uses some tricks which may create more disk I/O than other locking # methods. NOTE: If you use NFS, remember to change also mmap_disable setting! # Solaris doesn't support flock, so Solaris users need to change this to fcntl. #lock_method = flock # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Which locking methods to use for locking mbox. There's four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist in all systems. Doesn't work with NFS. # # You can use multiple locking methods; if you do the order they're declared # in is important to avoid deadlocks if other MTAs/MUAs are using multiple # locking methods as well. Some operating systems don't allow using some of # them simultaneously. #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # When mbox changes unexpectedly we have to fully read it to find out what # changed. If the mbox is large this can take a long time. Since the change # is usually just a newly appended mail, it'd be faster to simply read the # new mails. If this setting is enabled, Dovecot does this but still safely # fallbacks to re-reading the whole mbox file whenever something in mbox isn't # how it's expected to be. The only real downside to this setting is that if # some other MUA changes message flags, Dovecot doesn't notice it immediately. # Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK # commands. #mbox_dirty_syncs = yes # Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE, # EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored. #mbox_very_dirty_syncs = no # Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK # commands and when closing the mailbox). This is especially useful for POP3 # where clients often delete all mails. The downside is that our changes # aren't immediately visible to other MUAs. #mbox_lazy_writes = yes # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. It could be a small # security risk if you use single UID for multiple users, as the users could # ptrace() each others processes then. #mail_drop_priv_before_exec = no # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #mail_process_size = 256 # Log prefix for mail processes. See doc/variables.txt for list of possible # variables you can use. #mail_log_prefix = "%Us(%u): " ## ## IMAP specific settings ## protocol imap { # Login executable location. #login_executable = /usr/local/libexec/dovecot/imap-login # IMAP executable location #mail_executable = /usr/local/libexec/dovecot/imap # This would write rawlogs into ~/dovecot.rawlog/ directory: #mail_executable = /usr/local/libexec/dovecot/rawlog /usr/local/libexec/dovecot/imap # Maximum IMAP command line length in bytes. Some clients generate very long # command lines with huge mailboxes, so you may need to raise this if you get # "Too long argument" or "IMAP command line too large" errors often. #imap_max_line_length = 65536 # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/local/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 = yes # Workarounds for various client bugs: # delay-newmail: # Send EXISTS/RECENT new mail notifications only when replying to NOOP # and CHECK commands. Some clients ignore them otherwise, for example # OSX Mail. Outlook Express breaks more badly though, without this it # may show user "Message no longer in server" errors. Note that OE6 still # breaks even with this workaround if synchronization is set to # "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. # netscape-eoh: # Netscape 4.x breaks if message headers don't end with the empty "end of # headers" line. Normally all messages have this, but setting this # workaround makes sure that Netscape never breaks by adding the line if # it doesn't exist. This is done only for FETCH BODY[HEADER.FIELDS..] # commands. Note that RFC says this shouldn't be done. # tb-extra-mailbox-sep: # With mbox storage a mailbox can contain either mails or submailboxes, # but not both. Thunderbird separates these two by forcing server to # accept '/' suffix in mailbox names in subscriptions list. imap_client_workarounds = delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. #login_executable = /usr/local/libexec/dovecot/pop3-login # POP3 executable location #mail_executable = /usr/local/libexec/dovecot/pop3 # Don't try to set mails non-recent or seen with POP3 sessions. This is # mostly intended to reduce disk I/O. With maildir it doesn't move files # from new/ to cur/, with mbox it doesn't write Status-header. #pop3_no_flag_updates = no # Support LAST command which exists in old POP3 specs, but has been removed # from new ones. Some clients still wish to use this though. Enabling this # makes RSET command clear all \Seen flags from messages. #pop3_enable_last = no # POP3 UIDL format to use. You can use following variables: # # %v - Mailbox UIDVALIDITY # %u - Mail UID # %m - MD5 sum of the mailbox headers in hex (mbox only) # %f - filename (maildir only) # # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier version 0 : %f # Courier version 1 : %u # Courier version 2 : %v-%u # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # Older Dovecots : %v.%u # # Note that Outlook 2003 seems to have problems with %v.%u format which was # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. # # NOTE: Nowadays this is required to be set explicitly, since the old # default was bad but it couldn't be changed without breaking existing # installations. %08Xu%08Xv will be the new default, so use it for new # installations. # pop3_uidl_format = %08Xu%08Xv # POP3 logout format string: # %t - number of TOP commands # %T - number of bytes sent to client as a result of TOP command # %r - number of RETR commands # %R - number of bytes sent to client as a result of RETR command # %d - number of deleted messages # %m - number of messages (before deletion) # %s - mailbox size in bytes (before deletion) #pop3_logout_format = top=%t/%T, retr=%r/%R, del=%d/%m, size=%s # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/local/lib/dovecot/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. # oe-ns-eoh: # Outlook Express and Netscape Mail breaks if end of headers-line is # missing. This option simply sends it if it's missing. pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } ## ## Authentication processes ## # Executable location #auth_executable = /usr/local/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. #auth_cache_ttl = 3600 # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username character translations before it's looked up from databases. The # value contains series of from -> to characters. For example "#@/@" means # that '#' and '/' characters are translated to '@'. #auth_username_translation = # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. auth_verbose = yes # Even more verbose logging for debugging purposes. Shows for example SQL # queries. auth_debug = yes # Maximum number of dovecot-auth worker processes. They're used to execute # blocking passdb and userdb queries (eg. MySQL and PAM). They're # automatically created and destroyed as needed. #auth_worker_max_count = 30 # Kerberos keytab to use for the GSSAPI mechanism. Will use the system # default (usually /etc/krb5.keytab) if not specified. #auth_krb5_keytab = auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous gssapi mechanisms = plain # # Password database is used to verify user's password (and nothing more). # You can have multiple passdbs and userdbs. This is useful if you want to # allow both system users (/etc/passwd) and virtual users to login without # duplicating the system users into virtual database. # # http://wiki.dovecot.org/Authentication # # Users can be temporarily disabled by adding a passdb with deny=yes. # If the user is found from that database, authentication will fail. # The deny passdb should always be specified before others, so it gets # checked first. Here's an example: #passdb passwd-file { # File contains a list of usernames, one per line #args = /etc/dovecot.deny #deny = yes #} # PAM authentication. Preferred nowadays by most systems. # Note that PAM can only be used to verify if user's password is correct, # so it can't be used as userdb. If you don't want to use a separate user # database (passwd usually), you can use static userdb. passdb pam { # [-session] [cache_key=<key>] [<service name>] # # -session makes Dovecot open and immediately close PAM session. Some # PAM plugins need this to work. # # 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. #args = dovecot } # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. #passdb passwd { #} # /etc/shadow or similiar, using getspnam(). Deprecated by PAM nowadays. #passdb shadow { #} # BSD authentication. Used by at least OpenBSD. #passdb bsdauth { # [cache_key=<key>] - See cache_key in PAM for explanation. #args = #} # passwd-like file with specified location #passdb passwd-file { # Path for passwd-file #args = #} # checkpassword executable authentication # NOTE: You will probably want to use "userdb prefetch" with this. #passdb checkpassword { # Path for checkpassword binary #args = #} # SQL database #passdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for example #args = #} # LDAP database #passdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example #args = #} # vpopmail authentication #passdb vpopmail { # [cache_key=<key>] - See cache_key in PAM for explanation. #args = #} # # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # # http://wiki.dovecot.org/Authentication # http://wiki.dovecot.org/VirtualUsers # # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. userdb passwd { } # passwd-like file with specified location #userdb passwd-file { # Path for passwd-file #args = #} # static settings generated from template #userdb static { # Template for settings. Can return anything a userdb could normally # return, eg.: uid, gid, home, mail, nice # # A few examples: # # args = uid=500 gid=500 home=/var/mail/%u # args = uid=500 gid=500 home=/home/%u mail=mbox:/home/%u/mail nice=10 # #args = #} # SQL database #userdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for example #args = #} # LDAP database #userdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example #args = #} # vpopmail #userdb vpopmail { #} # "prefetch" user database means that the passdb already provided the # needed information and there's no need to do a separate userdb lookup. # This can be made to work with SQL and LDAP databases, see their example # configuration files for more information how to do it. # http://wiki.dovecot.org/AuthSpecials #userdb prefetch { #} # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by userdb above. user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. # Note that valid_chroot_dirs isn't needed to use this setting. #chroot = # Number of authentication processes to create #count = 1 # Require a valid SSL client certificate or the authentication fails. #ssl_require_client_cert = no # Take the username from client's SSL certificate, using X509_NAME_oneline() # which typically uses subject's Distinguished Name. #ssl_username_from_cert = no } # It's possible to export the authentication interface to other programs, # for example SMTP server which supports talking to Dovecot. Client socket # handles the actual authentication - you give it a username and password # and it returns OK or failure. So it's pretty safe to allow anyone access to # it. Master socket is used to a) query if given client was successfully # authenticated, b) userdb lookups. # listener sockets will be created by Dovecot's master process using the # settings given inside the auth section #auth default_with_listener { # mechanisms = plain # passdb passwd { # } # userdb pam { # } # socket listen { # master { # path = /var/run/dovecot-auth-master # # WARNING: Giving untrusted users access to master socket may be a # # security risk, don't give too wide permissions to it! # #mode = 0600 # # Default user/group is the one who started dovecot-auth (root) # #user = # #group = # } # client { # path = /var/run/dovecot-auth-client # mode = 0660 # } # } #} # connect sockets are assumed to be already running, Dovecot's master # process only tries to connect to them. They don't need any other settings # than path for the master socket, as the configuration is done elsewhere. # Note that the client sockets must exist in login_dir. #auth external { # socket connect { # master { # path = /var/run/dovecot-auth-master # } # } #} Where can I start to debug? Can someone help? -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) 15, Chemin des Monges +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: ohp(a)pyrenet.fr ------------------------------------------------------------------------------ Make your life a dream, make your dream a reality. (St Exupery)

1 0

[Dovecot] Re: Error on login when running dovecot on RH9
by Ismail M. Settenda 18 Jan '06

18 Jan '06

Error on login when running dovecot on RH9 and I get an error msg when I login thru squirrel mail that the user name or password incorrect.. BTW ..installed squirmail from rpm and dovecot from tar file , I had a bit of a problem getting dovecot to run as I had to copy to file from a running copy on Fedora, the two file where - /usr/share/ssl/private/dovecot.pem - /usr/share/ssl/certs/dovecot.pem But it is runnig now...I just cant login!! Can anyone help? Below is the output form maillogs below from login as user : ismail Jan 17 10:45:40 elct dovecot: imap-login: Aborted login: user=<ismail>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jan 17 10:49:17 elct dovecot: imap-login: Aborted login: user=<ismail>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jan 17 11:02:57 elct dovecot: imap-login: Aborted login: user=<ismail>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jan 17 11:03:03 elct dovecot: imap-login: Aborted login: user=<ismail>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jan 17 11:10:08 elct dovecot: imap-login: Aborted login: user=<ismail>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jan 17 11:10:14 elct dovecot: imap-login: Aborted login: user=<ismail>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured -- Ismail

1 0

[Dovecot] Auth wit multiple ldap configfiles
by Dominik Saar 18 Jan '06

18 Jan '06

Hi, trying to deliver local mails with exim over dovecot. The problem is, that i logged in with a username from ldap to imap For this i created in dovecot.conf auth imap { args = /path/to/dovecot-ldap.conf ...... } And for delivery i use command = /path/to/dovecot/deliver -d $local_part@$domain in the exim.conf $local_part is diferent to the loginname in the ldaptree So i create in dovecot.conf auth deliver { args = /path/to/dovecot-ldap_deliver.conf } Sometime dovecot check the "auth deliver" section and sometimes the "auth imap" section i created. I don´t understand why dovecot doesn´t check allways both sections?!? P.S.: Sorry my english :)

1 0

[Dovecot] gdbhelper.c concerns
by Jeff A. Earickson 17 Jan '06

17 Jan '06

Timo, I was surprised to find both an execvp() and a system() call in gdbhelper.c. While gdbhelper should be running as an ordinary user (the person running imap), I find it a bit scary. I realize that the code is getting ready to run gdb, which is god-knows-where in the user's path. But still... Maybe the code should do a getuid() and/or geteuid() and refuse to run if the uid is zero. Also, the code does the fork() *before* checking the argc count. Maybe do it the other way around so the i_fatal is killing one process instead of two. Jeff Earickson Colby College

1 0

[Dovecot] 1.0 beta1 -- kevent() for notify failed: Invalid argument
by John Wong 17 Jan '06

17 Jan '06

after upgrade to 1.0 beta1 i see the warning/error message in mail log like this: kevent() for notify failed: invalid argument I/O leak: 0x1c05b6cc (5) is it normal?

2 1

[Dovecot] 1.0 beta1 plugin-loading
by Jan-Piet Mens 17 Jan '06

17 Jan '06

When a user logs on, the following messages appear in the log: dovecot: imap 21360 : Loading modules from directory: /usr/local/lib/dovecot/imap dovecot: imap 21360 : dlopen(/usr/local/lib/dovecot/imap/lib02_trash_plugin.so) failed: /usr/local/lib/dovecot/imap/lib02_trash_plugin.so: undefined symbol: quota dovecot: imap 21360 : Module loaded: /usr/local/lib/dovecot/imap/lib01_quota_plugin.so dovecot: imap 21360 : dirsize quota path = /shared/homes/rscweb.net/jpm/Maildir/ dovecot: imap 21360 : dirsize quota limit = 512000kB dovecot: imap 21360 : Module loaded: /usr/local/lib/dovecot/imap/lib02_imap_quota_plugin.so dovecot: imap 21360 : dlopen(/usr/local/lib/dovecot/imap/lib01_zlib_plugin.so) failed: /usr/local/lib/dovecot/imap/lib01_zlib_plugin.so: undefined symbol: gzseek Removing those files with rm -f lib01_zlib_plugin.* lib02_trash_plugin.so solves the problem. Platform Centos 4.2 , Linux 2.6.9-22.0.1.ELsmp Regards, -JP

1 0

[Dovecot] 1.0beta1: bullet-proofing dovecot-example.conf
by Jeff A. Earickson 17 Jan '06

17 Jan '06

Timo, I got bit last night during my upgrade to beta1 by uncommenting the following part of dovecot.conf for my site: #passdb passwd-file { # File contains a list of usernames, one per line #args = /etc/dovecot.deny #deny = yes #} I did a "s/#//" over this block of code, thereby uncommenting the comment too. Then I wondered why beta1 wouldn't start for me, until I found the conf syntax error. I suggest "bullet-proofing" some of the comments in dovecot-example.conf against this error, like so: #passdb passwd-file { ### File contains a list of usernames, one per line #args = /etc/dovecot.deny #deny = yes #} Attached is a diff against beta1 dovecot-example.conf to fix this kind of dumb mistake. Jeff Earickson Colby College

1 0

[Dovecot] SSL and login_process_per_connection = no
by Chris Wakelin 17 Jan '06

17 Jan '06

Just thought I'd check, but is the combination of SSL and "login_process_per_connection = no" expected? I'm wondering, because imap_login is doing the SSL-proxying, and in our live Dovecot instance we have "login_process_per_connection = no" (we had problems with authentication and running out of file descriptors early on, now fixed by using userdb = passwd-file rather than NIS). This combination seems to work OK in 1.0-beta1, except I just got disconnected with a log entry: Warning: imap-login: SSL_write() syscall failed: Bad file number [<IP address>] which I've never seen before (though I've been testing this with alpha5 for weeks). Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

1 0

[Dovecot] 1.0 beta1 testing
by Timo Sirainen 17 Jan '06

17 Jan '06

If you have time, please test http://dovecot.org/nightly/dovecot-latest.tar.gz If nothing big comes up, I'll release it as 1.0beta1 tomorrow evening.

8 10

[Dovecot] Duplicate suppression
by Greg Trounson 17 Jan '06

17 Jan '06

Hi there, Does the Dovecot project have plans to implement duplicate suppression at some stage? I have a situation where several people belong to more than one mailing list. One alias ('staff') incorporates several lists. These staff are receiving duplicate messages (one copy for every list they're on) when a message is sent to this staff alias. There is no reason they need to receive more than one copy. There seems to be no way I can turn that feature off in my MTA so I thought I'd try a bit further down the chain. thanks, Greg

6 6