- dovecot - dovecot.org

[Dovecot] ldap auth with test66
by Thomas Hummel 04 Apr '05

04 Apr '05

Hello, The installation of 1.0-test66 (still on FreeBSD 5.3-RELEASE-p1 with openldap-2.1.27) solved the SIGSEV problem I posted here on March 30 but I still cannot authenticate correctly with ldap. logs report "ldap(dovetest,127.0.0.1): No password in reply" and my client gets a "NO Temporary authentication failure." Obviously the attr_names array of the passdb_ldap_connection struct is valid until the preinit function but has been corrupted when we're at the passdb_init function. For instance, here's what I get in the log file for the 'fields' value : --- dovecot: Apr 04 11:43:19 Info: Dovecot v1.0-test66 starting up dovecot: Apr 04 11:44:58 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AGRvdmV0ZXN0AHBhc3M = dovecot: Apr 04 11:44:58 Info: auth(default): ldap(dovetest,127.0.0.1): base=ou= personnes, dc=pasteur, dc=fr scope=subtree filter=(&(objectClass=posixAccount)(u id=dovetest)) fields=0^S^<^S^d^S^°^S^ð^S^^T^T^Ð^T^Ø^T^^C -- Beside, I could notice, by adding some logging info, that the attr_names seem to hold the USER attrs instead of the PASS attrs. I'm trying now to investigate further through gdb (I added a sleep in the main of dovecot-auth to be able to attach the running process in gdb) but without success for now. Do you have any clue of where I should look ? -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

1 0

RE: [Dovecot] LDA Wishlist idea
by Mark Lidstone 04 Apr '05

04 Apr '05

But then in theory I should be able to get Fetchmail to figure that out by itself. Thanks for your reply too, Jakob. I think I'll have to have a good think about this one. Many thanks, Mark Lidstone IT and Network Support Administrator BMT SeaTech Ltd Grove House, Meridians Cross, 7 Ocean Way Ocean Village, Southampton. SO14 3TJ. UK Tel: +44 (0)23 8063 5122 Fax: +44 (0)23 8063 5144 E-Mail: mailto:mark.lidstone@bmtseatech.co.uk Website: www.bmtseatech.co.uk ======================================================================== == Confidentiality Notice and Disclaimer: The contents of this e-mail and any attachments are intended only for the use of the e-mail addressee(s) shown. If you are not that person, or one of those persons, you are not allowed to take any action based upon it or to copy it, forward, distribute or disclose the contents of it and you should please delete it from your system. BMT SeaTech Limited does not accept liability for any errors or omissions in the context of this e-mail or its attachments which arise as a result of Internet transmission, nor accept liability for statements which are those of the author and not clearly made on behalf of BMT SeaTech Limited. ======================================================================== == -----Original Message----- From: Timo Sirainen [mailto:tss@iki.fi] Sent: 02 April 2005 23:23 To: Mark Lidstone Cc: dovecot(a)dovecot.org Subject: RE: [Dovecot] LDA Wishlist idea On Sat, 2005-04-02 at 10:12 +0100, Mark Lidstone wrote: > I know that's how Demon do it, but surely it's not the only way of > doing it. > > As for putting the correct headers in, I've had no end of trouble with > fetchmail ignoring those headers and picking something it found in the > latest "Received:" header (which obviously names the drop-box). But fetchmail supports SDPS? You could write POP3 plugin which implements SDPS by eg. looking at those Return-Path and Envelope-To headers and returning them..

1 0

[Dovecot] Nested folders
by Michael Irons 03 Apr '05

03 Apr '05

I would like to have nested folders that users could create from their MUA. The problem is that I cannot create sub folders either through the MUA or by hand on the server side. I can make folders that are not the subfolder of anything. I have an Inbox, Mailing Lists, Spam, Trash, etc. But I cannot create subfolders of these. For example, I would like a subfolder under Mailing Lists for each Mailing list that I have subscribed. I am using Postfix that delivers directly to procmail which puts mails into Maildir style mail boxes in each users home directory. I am using the dovecot-0.99.13-4.FC2 rpm if that helps. I am sure that there would be some information about this somewhere, but I haven't found it in the mailing lists or googling around. The only information I have been able to find is that dovecot reportedly supports this. Thanks, Mike

2 2

[Dovecot] We couldn't drop root group privileges
by J. Erik Heinz 03 Apr '05

03 Apr '05

Hi, I just installed dovecot. The installation went well and i configured dovecot to user ~/Maildir. When I tested imap via telnet the login work, but right after that the connection is cutted: Trying 192.168.0.14... Connected to op. Escape character is '^]'. * OK dovecot ready. . login jerik password . OK Logged in. Connection closed by foreign host. And the log says: dovecot: Apr 02 19:37:18 Info: Dovecot starting up imap-login: Apr 02 19:38:03 Info: Login: jerik [192.168.0.23] imap(jerik): Apr 02 19:38:03 Fatal: We couldn't drop root group privileges dovecot: Apr 02 19:38:04 Error: child 15194 (imap) returned error 89 So the problem is that dovecot "could't drop root group". I started dovecot with /usr/local/etc/rc.d/dovecot.sh through the user root. The privilegs of the file are: ls -l dovecot.sh -r-xr-xr-x 1 root wheel 459 2 Apr 19:03 dovecot.sh the /usr/local/etc/dovecot.conf has the following entries. protocols = imap ssl_disable = yes disable_plaintext_auth = no log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot.log login = imap login_user = dovecot login = pop3 verbose_proctitle = yes first_valid_gid = 0 valid_chroot_dirs = /var/mail default_mail_env = maildir:~/Maildir client_workarounds = oe6-fetch-no-newmail outlook-idle outlook-pop3-no-nuls maildir_copy_with_hardlinks = yes auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = passwd auth_user = root auth_verbose = yes If I understand the dovecot.conf wright, the is the user root required for running dovecot "auth_user = root". That's why I don't understand the erros message. By the way, through the installation there was the user and group dovecot created, should this user start dovecot at boottime? Or should he be used for other tasks? Regards Erik -- J. Erik Heinz Koblenzer Str. 11 60327 Frankfurt am Main Handy: 0163 337 37 45 Mail: jheinz(a)wiwi.uni-frankfurt.de

2 2

[Dovecot] Multiple auth method problem
by Timshel Knoll-Miller 03 Apr '05

03 Apr '05

Hi, I'm having issues getting the multiple authentication methods of dovecot 1.0-test65 to work correctly on NetBSD. I am combining a MySQL database of virtual host accounts with the system password database of local machine accounts. Both work correctly when enabled on their own, but when enabled together only the one listed first in the "auth default" section of dovecot.conf works - the other logs the following error (line 5 below): Mar 29 21:56:50 rivendell dovecot: Dovecot v1.0-test65 starting up Mar 29 21:56:51 rivendell dovecot: auth(default): mysql: Connected to 127.0.0.1 (maildomains) Mar 29 21:56:51 rivendell dovecot: auth-worker(default): mysql: Connected to 127 .0.0.1 (maildomains) Mar 29 21:57:05 rivendell dovecot: auth-worker(default): BUG: PASSV had invalid passdb num Mar 29 21:57:38 rivendell dovecot: Killed with signal 2 To the client, dovecot locks up when a LOGIN command is issued for a user which can't be authenticated using the first method available (in my case, passwd). So for me, /etc/passwd users can still log in ok, but dovecot will lock up whenever a login with any other username is attempted. Script started on Tue Mar 29 22:07:59 2005 [root@rivendell ttyp3 ~]# telnet localhost 143 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. . LOGIN timshel secret . OK Logged in. . LOGOUT * BYE Logging out . OK Logout completed. Connection closed by foreign host. [root@rivendell ttyp3 ~]# telnet localhost 143 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. . LOGIN timshel(a)shels.net secret <dovecot locks up> . LOGOUT ^] telnet> quit Connection closed. [root@rivendell ttyp3 ~]# telnet localhost 143 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. . LOGIN dummyuser dummypass <dovecot locks up again> ^] telnet> quit Connection closed. [root@rivendell ttyp3 ~]# Script done on Tue Mar 29 22:09:03 2005 My dovecot.conf file is attached - can anyone shed any light on this and help me get going? Cheers, Timshel ## 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. # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s protocols = imap imaps pop3 pop3s #protocols = imap imaps #protocols = imaps # 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 = * #listen = [::] listen = 127.0.0.1 # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = #ssl_listen = [::] ssl_listen = * # Disable SSL/TLS support. #ssl_disable = no # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf #ssl_cert_file = /usr/pkg/etc/ssl/certs/imap.pem #ssl_key_file = /usr/pkg/etc/ssl/private/imap.pem ssl_cert_file = /etc/openssl/certs/mail.shels.net.crt ssl_key_file = /etc/openssl/private/mail.shels.net.key # File containing trusted SSL certificate authorities. Usually not needed. #ssl_ca_file = ssl_ca_file = /etc/openssl/ShelsCA/cacert.pem # Request client to send a certificate. #ssl_verify_client_cert = no # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 24 # SSL ciphers to use #ssl_cipher_list = all:!low # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. #disable_plaintext_auth = yes disable_plaintext_auth = yes # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). #log_path = # For informational messages, use this logfile instead of the default #info_log_path = # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = /var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. # http://wiki.dovecot.org/Rootless #login_chroot = yes # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. # Note that this user is NOT used to access mails. # http://wiki.dovecot.org/UserIds #login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 32 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to create. If login_process_per_user is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_user # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 # Greeting message for clients. #login_greeting = Dovecot ready. ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. first_valid_uid = 100 #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 = 100 #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 = # ':' 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 = no # 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 = maildir:/home/%u/Maildir #default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u default_mail_env = maildir:~/.mail # If you need to set multiple mailbox locations or want to change default # namespace settings, you can do it by defining namespace sections: # # You can have private, shared and public namespaces. The only difference # between them is how Dovecot announces them to client via NAMESPACE # extension. Shared namespaces are meant for user-owned mailboxes which are # shared to other users, while public namespaces are for more globally # accessible mailboxes. # # REMEMBER: If you add any namespaces, the default namespace must be added # explicitly, ie. default_mail_env does nothing unless you have a namespace # without a location setting. Default namespace is simply done by having a # namespace with empty prefix. #namespace private { # Hierarchy separator to use. You should use the same separator for all # namespaces or some clients get confused. '/' is usually a good one. #separator = / # Prefix required to access this namespace. This needs to be different for # all namespaces. For example "Public/". #prefix = # Physical location of the mailbox. This is in same format as # default_mail_env, which is also the default for it. #location = # There can be only one INBOX, and this setting defines which namespace # has it. #inbox = yes # If namespace is hidden, it's not advertised to clients via NAMESPACE # extension or shown in LIST replies. This is mostly useful when converting # from another server with different namespaces which you want to depricate # but still keep working. For example you can create hidden namespaces with # prefixes "~/mail/", "~%u/mail/" and "mail/". #hidden = yes #} # Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # # flags, date.sent, date.received, size.virtual, size.physical # mime.parts, imap.body, imap.bodystructure # # Different IMAP clients work in different ways, so they benefit from # different cached fields. Some do not benefit from them at all. Caching more # than necessary generates useless disk I/O, so you don't want to do that # either. # # Dovecot attempts to automatically figure out what client wants and it keeps # only that. However the first few times a mailbox is opened, Dovecot hasn't # yet figured out what client needs, so it may not perform optimally. If you # know what fields the majority of your clients need, it may be useful to set # these fields by hand. If client doesn't actually use them, Dovecot will # eventually drop them. # # Usually you should just leave this field alone. The potential benefits are # typically unnoticeable. #mail_cache_fields = # Space-separated list of fields that Dovecot should never save to cache file. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Like mailbox_check_interval, but used for IDLE command. #mailbox_idle_check_interval = 30 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no # Maximum allowed length for mail keyword name. It's only forced when trying # to create new keywords. #mail_max_keyword_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. # Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes. #mail_read_mmaped = no # Don't use mmap() at all. This is required if you store indexes in remote # filesystems (NFS or clustered filesystem). #mmap_disable = no # Don't write() to mmaped files. This is required for some operating systems # which use separate caches for them, such as OpenBSD. #mmap_no_write = no # Locking method for index files. Alternatives are fcntl, flock and dotlock. # Dotlocking uses some tricks which may create more disk I/O than other locking # methods. #lock_method = fcntl # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. maildir_copy_with_hardlinks = yes # 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 = 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/pkg/libexec/dovecot/imap-login # IMAP executable location #mail_executable = /usr/pkg/libexec/dovecot/imap # This would write rawlogs into ~/dovecot.rawlog/ directory: #mail_executable = /usr/pkg/libexec/dovecot/rawlog /usr/pkg/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/pkg/lib/dovecot/imap # Send IMAP capabilities in greeting message. This makes it unnecessary for # clients to request it with CAPABILITY command, so it saves one round-trip. # Many clients however don't understand it and ask the CAPABILITY anyway. #login_greeting_capability = no # Workarounds for various client bugs: # 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-negative-fetch: # Thunderbird sometimes messed up some calculations and wants to read # the message past it's end, giving negative size to FETCH BODY[]<..> # command. This workaround just hides the error message. #imap_client_workarounds = outlook-idle } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. #login_executable = /usr/pkg/libexec/dovecot/pop3-login # POP3 executable location #mail_executable = /usr/pkg/libexec/dovecot/pop3 # Don't try to set mails non-recent or seen with POP3 sessions. This is # mostly intended to reduce disk I/O. With maildir it doesn't move files # from new/ to cur/, with mbox it doesn't write Status-header. #pop3_no_flag_updates = no # Support LAST command which exists in old POP3 specs, but has been removed # from new ones. Some clients still wish to use this though. Enabling this # makes RSET command clear all \Seen flags from messages. #pop3_enable_last = no # POP3 UIDL format to use. You can use following variables: # # %v - Mailbox UIDVALIDITY # %u - Mail UID # %m - MD5 sum of the mailbox headers in hex (mbox only) # %f - filename (maildir only) # # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier version 0 : %f # Courier version 1 : %u # Courier version 2 : %v-%u # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # # Note that Outlook 2003 seems to have problems with %v.%u format which is # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. #pop3_uidl_format = %v.%u pop3_uidl_format = %08Xu%08Xv # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/pkg/lib/dovecot/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. # oe-ns-eoh: # Outlook Express and Netscape Mail breaks if end of headers-line is # missing. This option simply sends it if it's missing. #pop3_client_workarounds = } ## ## Authentication processes ## # Executable location #auth_executable = /usr/pkg/libexec/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # Authentication cache size in kilobytes. #auth_cache_size = 0 # Time to live in seconds for cached data. After this many seconds a cached # record is forced out of cache. #auth_cache_ttl = 3600 # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username character translations before it's looked up from databases. The # value contains series of from -> to characters. For example "#@/@" means # that '#' and '/' characters are translated to '@'. #auth_username_translation = # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. auth_verbose = no # Even more verbose logging for debugging purposes. Shows for example SQL # queries. auth_debug = no # 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 auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous #mechanisms = plain digest-md5 cram-md5 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 # # 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 { # Service name or * as parameter. * 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 { #} # passwd-like file with specified location #passdb passwd-file { # Path for passwd-file #args = #} # checkpassword executable authentication #passdb checkpassword { # Path for checkpassword binary #args = #} # SQL database passdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for example args = /usr/pkg/etc/dovecot-sql.conf } # LDAP database #passdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example #args = #} # vpopmail authentication #passdb vpopmail { #} # # 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:%h/mail nice=10 # #args = #} # SQL database userdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for example args = /usr/pkg/etc/dovecot-sql.conf } # LDAP database #userdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example #args = #} # vpopmail #userdb vpopmail { #} # 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 } # It's possible to export the authentication interface to other programs, # for example SMTP server which supports talking to Dovecot. Client socket # handles the actual authentication - you give it a username and password # and it returns OK or failure. So it's pretty safe to allow anyone access to # it. Master socket is used to a) query if given client was successfully # authenticated, b) userdb lookups. # listener sockets will be created by Dovecot's master process using the # settings given inside the auth section #auth default_with_listener { # mechanisms = plain # passdb passwd { # } # userdb pam { # } # socket listen { # master { # path = /var/run/dovecot/auth-master # #mode = 0600 # # Default user/group is the one who started dovecot-auth (root) # #user = # #group = # } # client { # path = /var/run/dovecot-auth-client # mode = 0660 # } # } #} # connect sockets are assumed to be already running, Dovecot's master # process only tries to connect to them. They don't need any other settings # than path for the master socket, as the configuration is done elsewhere. # Note that the client sockets must exist in login_dir. #auth external { # socket connect { # master { # path = /var/run/dovecot/auth-master # } # } #}

2 2

[Dovecot] Trouble with basic Dovecot setup
by paul wisehart 03 Apr '05

03 Apr '05

Hi, I have compiled dovecot-1.0_stable. (http://dovecot.org/nightly/stable/dovecot-stable-20050328.tar.gz) I have it set to "userdb = passwd" & "passdb = passwd" I have a user "wise" with an maildir type mailbox at ~/Mail The actual maildirs are all subfolders with the INBOX "inbox" being one of them. I also have setup the ssl certificates with the script from the source doc directory. I start dovecot, and try to login from a seperate machine running thunderbird. I tell it to use ssl ( 993 ). (I specified both dovecot logs in the config file.) This is what I get from the dovecot logs: "info_log_path = /etc/dovecot/info.log": dovecot: Mar 29 08:30:15 Info: Dovecot v1.0-stable starting up dovecot: Mar 29 08:37:44 Info: Dovecot v1.0-stable starting up dovecot: Mar 29 08:39:04 Info: imap-login: Aborted login [###.###.###.###] I get that last line every time I try to connect from thunderbird. Any ideas? I can give more detailed info as well. thanks! -- paul \ / wisehart >/ <//////$> |\|\|\ -- paul \ / wisehart >/ <//////$> |\|\|\

1 1

[Dovecot] QUOTA support timeframe? (also -- folders in folders?)
by Gerald V. Livingston II 02 Apr '05

02 Apr '05

I see it's been in the wishlist a while. Any possible timeframe for getting it working, or maybe a patch (or is it too big a change) to support it? I'm building a new server to move an existing userbase to. So far I have working: Postfix (with Maildir quota patches that work fine) Amavis-new with ClamAV scanning for viruses (will add SpamAssassin soon) SquirrelMail IMP (Horde) (Yes, 2 webmails to allow customers a choice of interface) Right now my test accounts have quotas, but they have no way to see where they stand without IMAP++ QUOTA support. Also, a question. Does Dovecot support folders within folders other than INBOX? I hadn't even thought about that question until I tried to create a test folder from within Squirrelmail and checked the "Let this folder contain subfolders" box and the creation failed ---- nevermind, that must be a Squirrelmail oddity. I created another folder inside the test folder and it worked OK -- just have to NOT check that box. Thanks all, Gerald

3 3

[Dovecot] pop3 storage problems
by Obantec Support 02 Apr '05

02 Apr '05

Hi Having updated the conf file and done a restart i now see 3 account with problems. Mar 30 12:10:37 proteus2a pop3(campusuk): Failed to create storage with data: mbox:/var/spool/mail/campusuk Mar 30 13:08:20 proteus2a pop3(tlccoco_003): Failed to create storage with data: mbox:/var/spool/mail/tlccoco_003 Mar 30 13:16:44 proteus2a pop3(tlccoco_001): Failed to create storage with data: mbox:/var/spool/mail/tlccoco_001 Mark

2 1

RE: [Dovecot] LDA Wishlist idea
by Mark Lidstone 02 Apr '05

02 Apr '05

Hi, I know that's how Demon do it, but surely it's not the only way of doing it. As for putting the correct headers in, I've had no end of trouble with fetchmail ignoring those headers and picking something it found in the latest "Received:" header (which obviously names the drop-box). Thanks, Mark Lidstone IT and Network Support Administrator BMT SeaTech Ltd Grove House, Meridians Cross, 7 Ocean Way Ocean Village, Southampton. SO14 3TJ. UK Tel: +44 (0)23 8063 5122 Fax: +44 (0)23 8063 5144 E-Mail: mailto:mark.lidstone@bmtseatech.co.uk Website: www.bmtseatech.co.uk ======================================================================== == Confidentiality Notice and Disclaimer: The contents of this e-mail and any attachments are intended only for the use of the e-mail addressee(s) shown. If you are not that person, or one of those persons, you are not allowed to take any action based upon it or to copy it, forward, distribute or disclose the contents of it and you should please delete it from your system. BMT SeaTech Limited does not accept liability for any errors or omissions in the context of this e-mail or its attachments which arise as a result of Internet transmission, nor accept liability for statements which are those of the author and not clearly made on behalf of BMT SeaTech Limited. ======================================================================== == -----Original Message----- From: Jakob Hirsch [mailto:jh@plonk.de] Sent: 01 April 2005 19:52 To: dovecot(a)dovecot.org Subject: Re: [Dovecot] LDA Wishlist idea Mark Lidstone wrote: > Demon (an ISP) have extensions to POP3 they call "SDPS" - there's > basically an extra command that can be called for an email and it > gives the envelope rcpt and from addresses. I was wondering if there > was any chance of future versions of Dovecot allowing something > similar? As demon says, SDPS works by accessing "the same mail spools as are used by SMTP". Dovecot does not do this. And I don't see a need for that. Configure your MTA to put the envelope data into the mail header (e.g. Return-path and Envelope-to). I used this several times for multidrop-mailboxes (which also seems to be the main use of SDPS).

2 1

[Dovecot] virtual user question
by Steve Hoffman 02 Apr '05

02 Apr '05

I'm sorry if this has been asked already, but I'm new to the list and to dovecot. I'm trying to add imap to our existing setup where we host many virtual domains and would like to use dovecot to do it as I find it's one of the most configurable I've seen so far. The problem is that our virtual users passwd files are kept in seperate directories so /etc/virtual/%d/passwd, but I can't use the variable substitution in the dovecot.conf file as it results in a load error because it won't translate the %d. I'm using the latest development release, test65. I read in the config file that you can use many passdb's but do I have to put them all in there or is there a way to use some sort of substitution? The other issue I'm having is when I try to test the connection (with a hard coded path to passwd) it fails auth if I pass the username "user(a)domain.com" but passes if I pass just "user". Any help or places you can point me for these issues? Thanks, Steve

2 1