- dovecot - dovecot.org

[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

[Dovecot] virtual users with winbind
by Paul Matthews 17 Jan '06

17 Jan '06

hi there, i'm trying to setup virtual users with winbind, i have everything setup in dovecot other than 'Data source for users, homes and IDs'. i have 'Password authentication source' set to auth_passdb = pam my pam module is using winbind with the mkhomedir.so i have 'Mail file location' set to default_mail_env = mbox:/home/%u/mail:INBOX=/var/spool/mail/%u i have 'Data source for users, homes and IDs' set tp auth_userdb = passwd at the moment my local users can sign in, but my winbind users can't, i'm looking for a way to make auth_userdb look up a pam module, or something ... i don't know what i'm looking for, can someone help me with virtual users with winbind?

1 0

[Dovecot] in a major jam...
by Tom Allison 16 Jan '06

16 Jan '06

I upgraded my dovecot installation from something <<1.0 to 0.99.14 today. I wasn't exactly planning to but it just came along for the ride when I upgraded the rest of my system. I was using postgresql for the authentication. Nothing works. the debug logs show that I'm able to make a connection to the database table well enough: auth(default): pgsql: Connected to dbmail (that's my database name) When I attempt to login I get (briefly) password mismatch. I haven't changed the password in well over a year. My old configuration file for dovecot.conf went to the tune of: login = imap auth_mechanisms = plain auth_passdb = pgsql:/etc/dovecot/dovecot-pgsql.conf auth_user = root (probably not the best, but it worked) I now have a config file something like this: dovecot-pgsql.conf -- added the 'driver = pgsql' statement. Because it's able to connect to the database I don't think this is much of a problem here. dovecot.conf (these are all the non-empty lines, except for some logging stuff) protocols = imap disable_plaintext_auth = no protocol imap { } protocol pop3 { } auth_verbose = yes auth_debug = yes auth default { mechanisms = plain passdb pam { } passdb sql { args = /etc/dovecot/dovecot-pgsql.conf } userdb passwd { } user = root } It's fairly obvious that there has been a lot of work done on getting more authentication mechanisms in place for dovecot. That's great, and some day I want to play with it, but this is not the day for it. help.... help.... oh help!

2 2

[Re: [Dovecot] in a major jam...]
by Tom Allison 16 Jan '06

16 Jan '06

Marcus Rueckert wrote: > On 2006-01-16 14:46:36 -0500, Tom Allison wrote: > >>I upgraded my dovecot installation from something <<1.0 to 0.99.14 >>today. I wasn't exactly planning to but it just came along for the ride >>when I upgraded the rest of my system. > > > do you mind to upgrade to the release mentioned in this mail > http://www.dovecot.org/list/dovecot/2006-January/010832.html ? > > the 0.99.14 code base is 2y old and no longer actively maintained. > I upgraded from 0.99.14. It reports 1.0alpha5 now. This is the transistion that broke me. And I just realized I posted this twice to the mailing list. My rather hastily set up connection to another mail server wasn't telling me I actually sent anything.

1 0

[Dovecot] Plain password not authenticating
by Anne Wilson 16 Jan '06

16 Jan '06

I'm trying to set up a temporary mailserver using Debian Sarge and Dovecot 1.0 with maildir format. My only previous experience has been on a simple imap server. I have read the wiki documentation and searched the archives, but can't tie down my problem. The log tells me Info: passwd-file(anne) : unknown user. I have set auth_userdb = passwd-file /etc/imap.passwd auth_passdb = passwd-file /etc/imap.passwd and created the /etc/imap.passwd file as anne:{plain}mypassword:1000:1000::/home/anne What have I missed? Anne -- Registered Linux User No.293302 (http://counter.li.org/)

4 23

[Dovecot] Re: Dovecot memory use and settings
by Roger Weeks 16 Jan '06

16 Jan '06

We're continuing to have dovecot auth-worker failures once or more times per day. The symptoms are these in the log: pop1 dovecot: auth-worker(default): Out of memory (Needed 8164 bytes) or auth-worker(default): sql(lewis1,12.43.59.134): Password query failed: MySQL client ran out of memory Timo suggested that we need to up the auth_process_size = 256 However, we've tried increasing this to 512 and then 768. The comment on the entry says # Set max. process size in megabytes. These changes don't seem to make any difference. On both of our servers (RH ES4, 1MB RAM), we never seem to have more than 300MB of RAM used. However, the auth-worker process continues to fail occasionally. It does respawn itself after a couple of minutes, but in that time all authentication for dovecot fails. Am I missing something else in the config? -- Roger J. Weeks Systems & Network Administrator Mendocino Community Network On Jan 11, 2006, at 12:51 PM, Timo Sirainen wrote: > On Wed, 2006-01-11 at 12:40 -0800, Roger Weeks wrote: >> pop1 dovecot: auth-worker(default): Out of memory (Needed 8164 bytes) >> >> or >> >> auth-worker(default): sql(lewis1,12.43.59.134): Password query >> failed: MySQL client ran out of memory > > These are different from the system running out of memory. It's about > authentication process size hitting its configured limit. Default is: > > # Set max. process size in megabytes. > #auth_process_size = 256 > > So it appears that it's trying to grow above 256MB at which point it > gets killed. This could mean that something is leaking memory, but I > don't remember other people having this problem, so it might be > somehow > specific to your configuration. > > In any case those auth-workers are restarted automatically whenever > they > die so it shouldn't be that big of a problem? > > There are also ways to debug this if you want to.. >

3 5

[Dovecot] Imap working, but not Pop3
by Cyril Spiro 16 Jan '06

16 Jan '06

I'm running Redhat Linux 4.1 and I have dovecot loaded and imap is working. Users can get their mail via squirrelmail. But everytime I try to 'chkconfig ipop3 on' I get the error 'error reading information on service pop3: no such file or directory'. Any ideas?

2 1

[Dovecot] passdb-pam: PAM_RHOST on FreeBSD >= 5.0 (where PAM != Linux-PAM)
by Tom Alsberg 16 Jan '06

16 Jan '06

This is actually something I had on my mind to write about in the past few -stable and alpha releases, but did not get to and instead always patched myself. Now having updated to the latest snapshot (which may be released as beta1), I stumbled on it again: In src/auth/passdb-pam.c, where the client host is passed to PAM, the code looks like this: #ifdef PAM_RHOST const char *host = net_ip2addr(&request->remote_ip); if (host != NULL) pam_set_item(pamh, PAM_RHOST, host); #endif For some reason there is a preprocessor/compile-time check whethere there exists such a preprocessor symbol as the PAM item PAM_RHOST (why check that? IIRC PAM_RHOST is standard and in all PAM implementations). However, PAM_RHOST (or other PAM items, for that matter), are not preprocessor symbols in all PAM implementations. For example, in OpenPAM (the PAM implementation used on FreeBSD >= 5.0, among others; FreeBSD 4 used Linux-PAM), PAM items are elements of an enum, and thus this check fails, and the client host is not passed to PAM. Since it can be defined in several ways, I do not see how to check for it other than using a compilation test (in autoconf) and then defining something like HAVE_PAM_RHOST in config.h. However I do not see why check for it at all, so I propose to remove that #ifdef. Tiny patch attached for that. 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.

1 0

[Dovecot] Looking to upgrade from .99.14 to 1.0alpha5
by Erik Dasque 15 Jan '06

15 Jan '06

Hi all, I was looking to upgrade my dovecot .99.14 installation to 1.0alpha5 today and bumped into an issue. My setup is on Mac OS X 10.4 and I am using After reading http://wiki.dovecot.org/UpgradingDovecot , I created a default dovecot.conf file with the following information grabbed from my prior installation: Snow:~ ed$ grep -v '^ *#' /usr/local/etc/dovecot.conf|grep -v ^$ ssl_disable = yes login = imap login = pop3 auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam login auth_user = root auth_verbose = yes So as you can see, I use passwd and pam as my authentication db. So I copied over the dovecot-example.conf and as far as I know the only modifications I needed to make to the default file were to disable ssl and set the verbose and debug auth. Keep in mind that passwd/pam db methods work with .99.14 but with 1.0alpha5, I get the following: Jan 14 15:55:16 Snow dovecot: Dovecot v1.0.alpha5 starting up Jan 14 15:58:15 Snow dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AGVkAGFic2ludGhlMzM= Jan 14 15:58:15 Snow dovecot: auth(default): pam(ed,127.0.0.1): pam_authenticate() failed: Authentication failure Jan 14 15:58:15 Snow dovecot: auth(default): client out: FAIL 1 user=ed Jan 14 15:58:21 Snow dovecot: auth(default): client in: AUTH 2 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AGVkAGFic2ludGhlMzM= Jan 14 15:58:21 Snow dovecot: auth(default): pam(ed,127.0.0.1): pam_authenticate() failed: Authentication failure Jan 14 15:58:21 Snow dovecot: auth(default): client out: FAIL 2 user=ed and so on and so forth. Any idea what could be causing this or how to debug this further ? Thanks in advance, Erik PS: my pam setup for dovecot is: Snow:~ ed$ more /etc/pam.d/dovecot auth required pam_unix.so nullok account required pam_unix.so

3 2

[Dovecot] Occasional errors opening email folder in SquirrelMail
by Jonathan 15 Jan '06

15 Jan '06

Every once in a while I get this [1] error when trying to open a mail folder in SquirrelMail. I don't know enough about IMAP to tell if it is a SquirrelMail or a Dovecot issue. I also get this [2] error message every time I try to send an email. The email goes through but there is no copy in the Sent folder. If there is some kind of logging I can enable that would help with this please let me know. [1] ERROR: Bad or malformed request. Query: FETCH (FLAGS UID RFC822.SIZE BODY.PEEK[HEADER.FIELDS (Date To Cc >From Subject X-Priority Importance Priority Content-Type)]) Server responded: Error in IMAP command UID: Invalid arguments. [2] ERROR: Bad or malformed request. Server responded: Error in IMAP command APPEND: Thank you, Jonathan

2 2

[Dovecot] How long to 1.0?
by Fredrik Tolf 15 Jan '06

15 Jan '06

Hi! I'm wondering how close Dovecot can be said to be to 1.0 "Final". How stable can the alpha branch be said to be? I was browsing around the Dovecot homepage, but I couldn't find any answer to this question. I hope it hasn't been asked (too many times) before. Fredrik Tolf

15 29

[Dovecot] Corrupted index files
by Andy Cravens 15 Jan '06

15 Jan '06

I'm using alpha 5 and I'm getting "Corrupted index cache files" errors on one user's account. I found several posts in the mail archives on this subject and concluded from the responses that it's not a serious problem because Dovecot can deal with it. I deleted the index files and they were recreated but the error persists. The end user did not notice any problem but it makes me nervous. Is this something I should be concerned about? dovecot: Jan 12 10:22:06 Error: imap(username): Corrupted index cache file /export/home/username/mail/dovecot.index.cache: Duplicated field in header: hdr.CONTENT-TYPE dovecot: Jan 12 14:31:08 Error: imap(username): Corrupted index cache file /export/home/username/mail/.syslog_analyzer/dovecot.index.cache: Duplicated field in header: hdr.CONTENT-TYPE dovecot: Jan 12 14:43:56 Error: imap(username): Corrupted index cache file /export/home/username/mail/.gl3_ip_allocation/dovecot.index.cache: Duplicated field in header: hdr.CONTENT-TYPE By the way... is there a search function somewhere for searching the mailing list archives? I ended up selecting one month at a time and searching through the thread titles with my browser's "find" button. -- Andy

3 3

[Dovecot] 20060114 snapshot compilation warnings
by Chris Wakelin 15 Jan '06

15 Jan '06

Timo, I've noticed a couple of extra compilation errors in last night's snapshot compared to the snapshot I downloaded on Tuesday, probably due to the int -> bool change :- (gcc 3.3.2 on Solaris 8) mbox-sync.c: In function `mbox_sync': mbox-sync.c:1568: warning: comparison is always false due to limited range of data type index-search.c: In function `search_index_arg': index-search.c:131: warning: comparison is always false due to limited range of data type quota-storage.c: In function `quota_check': quota-storage.c:114: warning: passing arg 3 of `quota_try_alloc' from incompatible pointer type together with a few "unused parameter/variable" errors which were there before. I also needed to rewrite half my internal patches :) but that shouldn't have made any difference (they certainly don't involve those files). 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

3 5

[Dovecot] How can I archive maildir?
by Neal Becker 15 Jan '06

15 Jan '06

Does anyone have a suggestion how to archive old maildir format mail?

2 3

Fwd: Re: [Dovecot] Compile problem on FreeBSD 6.0-STABLE
by Peter Losher 15 Jan '06

15 Jan '06

On Friday 30 December 2005 12:54 pm, Brad wrote: > Why would you install a port of something that comes with > the base OS, especially MIT Kerb5? While Krb5 is included in FreeBSD, it's Heimdal implementation, not MIT's, and some of us have valid reasons for running MIT Krb5 instead and the API's are different between the two. Best Wishes - Peter -- [ http://www.plosh.net/ ] - "Earth Halted: Please reboot to continue"

1 0

[Dovecot] Password changing?
by john 14 Jan '06

14 Jan '06

Hey all, new user to the dovecot mailing list but I promise, this is a neat question. Is it possible to request users change their email password through their email client? I'm currently authenticating email logins to my dovecot server through SSL, with each users password checked against their /etc/passwd password. So far, thunderbird will ask for the users new password (forced change at first logon,) but it fails to change the users password through the encrypted email connection. Any assistance would be gladly appreciated. Getting past this hurdle means i can eliminate one more bill gates server/money hole with a power button. P.S. If anyone isnt using this "feature" to get users to set their email password, how might i ask are you getting users to change their email password to dovecot? --John

2 1

[Dovecot] [BUG] Thread command
by Sebastjan Trepca 14 Jan '06

14 Jan '06

Hi, while implementing thread support in our mail application I found a bug which kills IMAP(alpha5, SUSE 10) process... These are the commands: x OK Logged in. x select INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk Junk $Forwarded Spam) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk Junk $Forwarded Spam \*)] Flags permitted. * 2280 EXISTS * 1 RECENT * OK [UNSEEN 473] First unseen. * OK [UIDVALIDITY 1136386397] UIDs valid * OK [UIDNEXT 2319] Predicted next UID x OK [READ-WRITE] Select completed. x uid thread references utf8 (SUBJECT "locking") * THREAD (2289 2307) * 2281 EXISTS * 1 RECENT x OK Thread completed. x UID THREAD REFERENCES UTF8 (SUBJECT 'locking') Connection closed by foreign host. This is the code dump: (gdb) bt full #0 0xdededede in ?? () No symbol table info available. #1 0x08060127 in mail_thread_deinit (ctx=0x80c0120) at imap-thread.c:100 No locals. #2 0x080611e2 in imap_thread (cmd=0x80c5c34, charset=0x80c5f48 "UTF8", args=0x80ea980, type=MAIL_THREAD_REFERENCES) at imap-thread.c:156 wanted_headers = {0x80b6645 "message-id", 0x80b2947 "in-reply-to", 0x80b2953 "references", 0x80b1978 "subject", 0x0} client = (struct client *) 0x80c5bf0 headers_ctx = (struct mailbox_header_lookup_ctx *) 0x80eb188 ctx = (struct thread_context *) 0x80c0120 mail = (struct mail *) 0x80ced28 ret = 0 #3 0x080598b5 in cmd_thread (cmd=0x80c5c34) at cmd-thread.c:66 client = (struct client *) 0x80c5bf0 sargs = <value optimized out> args = (struct imap_arg *) 0x80c5ea0 args_count = <value optimized out> pool = 0x80ea930 error = <value optimized out> charset = 0x80c5f48 "UTF8" str = 0x80c5f38 "REFERENCES" #4 0x0805a271 in _client_input (context=0x80c5bf0) at client.c:338 cmd = (struct client_command_context *) 0x80c5c34 ret = <value optimized out> #5 0x080a91c8 in io_loop_handler_run (ioloop=0x80c49b0) at ioloop-epoll.c :250 ctx = <value optimized out> event = (struct epoll_event *) 0x80c4a00 io = (struct io *) 0x80c5da8 tv = {tv_sec = 0, tv_usec = 999991} t_id = 2 msecs = <value optimized out> ret = 0 i = 0 call = <value optimized out> #6 0x080a881b in io_loop_run (ioloop=0x80c49b0) at ioloop.c:230 No locals. #7 0x080617e4 in main (argc=3, argv=0xbfa6e7d4, envp=0xbfa6e7e4) at main.c :235 No locals. Hope this is enough. Sebastjan

2 1

[Dovecot] Errors in /var/log/maillog and /var/log/dovecot.log
by Li Cai 14 Jan '06

14 Jan '06

I am trying to migrate from UW imap to dovecot. OS: RHEL 3 X86 MTA: Postfix Auth: PAM (NIS server) Most of the users are fine, but I have some users have problems: " Jan 14 09:18:42 Info: imap-login: Internal login failure: user=<user1>, method=PLAIN, rip=X.X.X.X, lip=X.X.X.X, TLS " This happens on dovecot version dovecot-1.0.alpha5-1 and dovecot-0.99.11-1 If anyone else has met such problem? Thanks Li

2 3

[Dovecot] "Discarding bogus continuation" message in pine
by Jesse Chan-Norris 14 Jan '06

14 Jan '06

Running 1.0alpha5 (though I've been having this problem for the past couple of versions), and using mbox for the mailboxes. After I've read my mail using Apple's Mail.app (or Thunderbird) and take it offline, when I try to open the INBOX (or any mailbox) with pine, I get the following message (in pine): [Discarding bogus continuation in msg 1: $Forwarded NonJunk] Quitting and re-running pine does not bring up this message again, and it looks like it's getting confused by the internal mbox message's X-IMAP line: X-IMAP: 1076598957 0000257269 NotJunk JunkRecorded $NotJunk $Junk Junk \ Forwarded $Forwarded NonJunk The "$Forwarded NonJunk" part is the only part of that line that is on a new line, and it gets written out like that after I've read mail using an IMAP client, leading me to believe that pine doesn't know how to handle the newline in the X-IMAP line. I don't know if this is a Dovecot, Mail.app, or pine problem, but I never saw this error in UW-IMAP. Any help would be appreciated. Thanks! jcn

2 2

[Dovecot] Upgrade question
by Anne Wilson 14 Jan '06

14 Jan '06

I have 0.99.14 installed. I've downloaded the latest version. Does it install over the old one, in parallel, or need an uninstall of the old one? Anne

2 2

[Dovecot] compiling Dovecot CVS version, 1 problem, 1 wish, 3 questions
by Steffen Kaiser 14 Jan '06

14 Jan '06

Hello, today I checked out a new copy of Dovecot (and LDA) from CVS: File: ChangeLog Status: Up-to-date Working revision: 1.2765 Repository revision: 1.2765 /home/cvs/dovecot/ChangeLog,v I could compile them, but my findings follow: - the problem: I copied dovecot-lda below CVS_ROOT/dovecot, the first make attempt failed with this fatal error: make[3]: Entering directory `/var/autofs/fb02/prgdist/dovecot/dovecot/dovecot-lda/src/libsieve' /bin/sh ../../ylwrap `test -f 'addr.y' || echo './'`addr.y y.tab.c addr.c y.tab.h addr.h y.output addr.output -- bison -y -d -p addr ../../ylwrap: ../../ylwrap: No such file or directory the "ylwrap" is actually located in the Dovecot directory, hence, one directory up, so running ln -s ../ylwrap . in CVS_ROOT/dovecot/dovecot-lda fixed the problem. - the wish: It would be nice, if one could compile dovecot-lda right in the CVS locations without the need to give any option, e.g. the default "dovecot" path could be "../dovecot". - the questions: running ./autogen.sh results in: configure.in:1562: required file `./config.h.in' not found SUBDIRS: variable `DELIVER' is used but `DELIVER' is undefined ^^ Maybe the 2nd error results in that I passed "--without-deliver" to ./configure? running ./configure results in: checking for shared library run path origin... ./config.rpath: ./config.rpath: No such file or directory done running dovecot-lda/autogen.sh results in: configure.in:4: required file `./lda-config.h.in' not found Neither of these error messages prevent to built Dovecot, but they does not look "correct". Bye, -- Steffen Kaiser

3 4

[Dovecot] dovecot+ldap no auth...
by Joaquim Petiz 14 Jan '06

14 Jan '06

Dear sirs, In the configuration of Dovecot I can´t get autentication of the users. My work environment is: OpenBSD 3.8 Postfix 2.2.5 (instaled thru ports with ldap and sasl support) Opendap 2.2.27 (instaled thru ports with sasl support) Dovecot 0.99.14 (instaled thru source with ldap support) I have two domains in ldap, the postfix is just autenticating in ldap (sending e-mails to users of 2 ldap domains), I have one vmail user and one vmail group with uid e gid 800 to e-mail delivery and one dovecot user for dovecot itself. The Dovecot is not autenticating: # telnet localhost 143 * OK dovecot ready 0 login user(a)domain.com password 0 NO Authentication failed. ldap´s LOGS: Jan 11 13:48:56 ldap slapd[6397]: conn=6 op=4 SRCH base="cn=dovecot,o=organization,c=com" scope=2 deref=0 filter="(&(objectClass=qmailUser)(mail=user(a)domain.com))" Jan 11 13:48:56 ldap slapd[6397]: conn=6 op=4 SRCH attr=uid userPassword Jan 11 13:48:56 ldap slapd[6397]: conn=6 op=4 SEARCH RESULT tag=101 err=32 nentries=0 text= my slapd.conf: include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/nis.schema include /etc/openldap/schema/qmail.schema include /etc/openldap/schema/openldap.schema pidfile /var/run/slapd/slapd.pid argsfile /var/run/slapd/slapd.args access to dn.base="" by * read access to attr=userPassword by dn="uid=vmail,o=organization,c=com" read by dn="cn=dovecot,o=organization,c=com" read by anonymous auth by self write by * none database ldbm checkpoint 1024 5 cachesize 10000 suffix "o=organization,c=com" rootdn "cn=administrator,o=organization,c=com" rootpw {CRYPT}xxxxxxxxxxx directory /var/openldap-data index objectClass eq my user.ldif dn: cn=user,ou=domain1.com,o=organization,c=com cn: user ou: domain1.com sn: user objectClass: top objectClass: person objectClass: inetOrgPerson objectClass: posixAccount objectClass: qmailUser homeDirectory: /var/vmail/domains/domain1.com/user mail: user(a)domain1.com mailHost: mail.domains.com mailQuotaSize: 0 mailQuotaCount: 0 deliveryMode: normal uid: user uidNumber: 2000 gidNumber: 2000 accountStatus: active userPassword: {CRYPT}xxxxxxxxxxxx mailMessageStore: domain1.com/user mailAlternateAddress: user(a)domain1.com my dovecot.conf protocols = imap imap_listen = *:143 ssl_disable = yes login_dir = /var/dovecot/login login_executable = /usr/local/libexec/dovecot/imap-login login_user = dovecot first_valid_uid = 800 last_valid_uid = 800 first_valid_gid = 800 last_valid_gid = 800 valid_chroot_dirs = /var/vmail/domains/ default_mail_env = mbox:/var/vmail/domains/%d/%u/Maildir auth = default auth_mechanisms = plain auth_userdb = ldap /etc/dovecot-ldap.conf auth_passdb = ldap /etc/dovecot-ldap.conf My dovecot-ldap.conf hosts = localhost dn = uid=dovecot,o=organization,c=com dnpass = password ldap_version = 3 base = o=organization,c=com deref = never scope = subtree user_attrs = uid,homeDirectory,,uid,uidNumber,gidNumber user_filter = (&(objectClass=qmailUser)(mail=%u)) pass_attrs = uid,userPassword pass_filter = (&(objectClass=qmailUser)(mail=%u)) default_pass_scheme = CRYPT user_global_uid = 800 user_global_gid = 800 []'s

2 1

[Dovecot] New Dovecot installation and OE not POPing problems
by techlist06 14 Jan '06

14 Jan '06

Greetings: Recently I converted my mailserver to Postfix with some local accounts being accessed via Dovecot and POP3S. The clients are OE. The users are reporting that they aren't getting their messages. In the past with my old (IW?) POP server, I just used mail -f /var/spool/user and deleted the "DO NOT DELETE THIS MESSAGE...." message #1 and this cleared any problems with messages being out of sync on what had and had not been downloaded, etc. With Dovecot, I don't know how to "bump" the mailbox to get it "reset" so that OE will download the messages again, and/or get them if it hasn't already. Is this possible? Thanks very much for the time to help, Scott

2 1

[Dovecot] Auth protocol and Perl
by Allan Joergensen 14 Jan '06

14 Jan '06

Hi, does anyone have at working Perl example of how to use the auth protocol with Perl (I'm planing on making a dovecot auth plugin for qpsmtpd but it would a lot easier to reuse somebody elses code :)) tia, -- Allan Joergensen - http://nowhere.dk/ "All right, so it's impossible. How long will it take?"

3 3

[Dovecot] ERROR : Connection dropped by imap-server.
by Paul Matthews 14 Jan '06

14 Jan '06

hi there, i'm trying to setup dovecot with squirrel mail at the moment and i'm getting this error message ERROR: ERROR : Could not complete request. Query: CREATE "Sent" Reason Given: Permission denied ERROR: ERROR : Connection dropped by imap-server. Query: SELECT "INBOX" can someone tell me what this means? and what folders i have to change the permissions on? this is out of my /etc/dovecot.conf file if it helps default_mail_env = mbox:/var/mail/%u:mbox:~/mail/

3 2

[Dovecot] Patch: More of kqueue() support.
by Vaclav Haisman 14 Jan '06

14 Jan '06

Hi, the attached patch contains these changes: 2005-12-15 22:18 Vaclav Haisman <v.haisman(a)sh.cvut.cz> * src/lib/ioloop-kqueue.c: Fix IO_ERROR behaviour. * src/lib/ioloop-notify-kqueue.c: New file. * configure.in: Improve kqueue detection and handling. Cleanup. The configure.in changes that are not related to kqueue are there to make autoconf 2.59, automake 1.9.6 and libtool 1.5.20 are happy. The directory change notification is not really well tested because Dovecot doesn't seem to use it that much. As per Brad's request I have changed all occurrences of FreeBSD to just BSD. Vaclav Haisman

4 3

Re: [Dovecot] Message read not sticking with Apple Mail / dovecot 1.0alpha5
by Andy Cravens 13 Jan '06

13 Jan '06

Yes... I'm seeing this with the Apple mail client on Tiger. Our server is alpha 5/maildir/solaris 9/75 users. The apple user with the problem typically has more that one client open. He tends to leave his home PC connected when he comes in to work. He was able to resolve the last occurrence by closing all clients and resynching his mailboxes. We've also seen this problem on Solaris 9 running Mozilla 1.7.2 and Windows XP running outlook and evolution. These other clients have not seen a problem in over a month. The Apple user has problem every week. One interesting observation on this problem is that it will go away by itself given enough time. It seems that after a few hours to a full day it will go away. -- Andy Michael Stevens wrote: > Hi. > > I'm getting very weird behaviour with Apple Mail on Tiger and > 1.0alpha5 (with Timo's patch for the bug I saw). > > I can read a mail, see Apple Mail flag it as read, quit, come back > later, and find the mail is marked unread again. It seems to also > happen sometimes when I switch folders or get new mail. > > I've not worked out what's triggering it yet. Anyone seen anything > like this? > > Michael > >

1 0

[Dovecot] reply-to address of the list
by Udo Rader 13 Jan '06

13 Jan '06

Hi, is there a chance to alter the list behaviour to not use the sender address of a posting in the reply-to field but dovecot(a)dovecot.org instead? That way one has to either use "reply to all" in the MUA or manually enter dovecot(a)dovecot.org in any replies. And a "reply to all" duplicates postings because the posting once goes to the list and once to the original poster, that get's the reply twice then. Or maybe I am missing something ... :-) Udo BestSolution.at GmbH http://www.bestsolution.at

9 11

[Dovecot] removing folders doesn't always work
by William Astle 13 Jan '06

13 Jan '06

I've been running dovecot for a while now. I've got 1.0alpha5 running on a Slackware linux 10.2 system (i386). My system is using mbox format which means you can't have folders that contain both folders and messages. What I'm seeing is that removing folders doesn't always work. From what I can tell, it only affects folders that contain folders. Dovecot doesn't remove the directory from the server when the folder is removed which means it just keeps coming back. It's easy to duplicate this. Just create a folder that is allowed to contain folders only. You will see a directory created on the server. Then remove the folder. The directory will still be on the server, even if it is empty (i.e. no dovecot index files in it). Of course, most people create folders and never delete them, but occasionally it's useful to do so. For the record, removing folders that contain messages (mbox files) works. -- William Astle Lexicom Ltd. Phone: +1-403-262-6610 Long Distance: 1-877-426-6277 Email: astle(a)lexi.net

1 0

Re: [Dovecot] Message read not sticking with Apple Mail / dovecot 1.0alpha5
by Hauke Fath 13 Jan '06

13 Jan '06

Am 13.01.2006 um 11:17 Uhr +0000 schrieb Michael Stevens: >I can read a mail, see Apple Mail flag it as read, quit, come back >later, and find the mail is marked unread again. It seems to also >happen sometimes when I switch folders or get new mail. > >I've not worked out what's triggering it yet. Anyone seen anything >like this? Same here - Eudora on MacOS 10.4, and Mozilla on NetBSD 3. It is not strictly repeatable, but happens frequently. hauke -- /~\ The ASCII Ribbon Campaign Hauke Fath \ / No HTML/RTF in email Institut für Nachrichtentechnik X No Word docs in email TU Darmstadt / \ Respect for open standards Ruf +49-6151-16-3281

1 0

[Dovecot] dovecot-ldap.conf for usernames/homes/UID/GID
by Paul Matthews 13 Jan '06

13 Jan '06

hi there, Im getting such a headache today, Ive added myself to three mailing lists trying to figure this out, okay here it goes. Ive got a Fedora Core 4 box running dovecot imap, squirrel mail, postfix, samba/winbind. Im running winbind to authenticate against Active Directory, Ive edited my /etc/pam.d/dovecot pam module so to let my users login with there Active directory password, but squirrel mail wont let them I think, let me stress the term, think is has something to do with there home directories, because I have some local users as well, they can login no issues & my users with the same usernames on unix and ADS can login with there ADS passwords Now Im looking at the dovecot webmin module and I see that Data source for users, homes and Ids is set to use Standard unix username database. There is now option of PAM like in Password authentication source. Although I do see LDAP, using config file. Can I set that to query Active directory ldap database and go there Data source for users, homes and Ids? If I can can someone tell me how to, if not can someone tell me what I need to do? Here is what I have so far with my /etc/dovecot-ldap.conf hosts = senior-server.school.cathedral.qld.edu.au:389 dn = cn=administrator,cn=users,dc=school,dc=cathedral,dc=qld,dc=edu,dc=au dnpass = wwvH@cs ldap_version = 3 base = dc=school,dc=cathedral,dc=qld,dc=edu,dc=au deref = never scope = subtree user_attrs = uid,homeDirectory,,uid,uidNumber,gidNumber user_filter = (&(objectClass=posixAccount)(cn=%u)) pass_attrs = uid,userPassword pass_filter = (&(objectClass=posixAccount)(uid=%u)) CRYPT default_pass_scheme = CRYPT user_global_uid = 100 user_global_gid = 100

2 3

[Dovecot] QUOTA Imap Extension
by Brady Wetherington 13 Jan '06

13 Jan '06

Hi - long time lurker, very rare poster I understand Dovecot's support for mbox quotas is - well, not quite there yet. But I actually am not asking about that. I use vpopmail and qmail and Maildirs and was wondering about the QUOTA imap extension, which allows IMAP clients to query their quota settings. The reason I need to know about this is that I have a mailserver with a chunk of clients and their mail stores are getting large. And starting to exhaust my storage. I could just throw more storage at it - but they're not paying me for that level of storage, so I need to quota them. And my main source of business is one particular consulting company, so I pretty much have to do what they say, within reason, and they said, "Okay, you can quota everyone, so long as they can at least find out what their quota is in Webmail..." Which is pretty reasonable - quota'ing people and then not letting them know how close to their quota they are seems cruel, especially with the meager IQ's of my particular set of clients. Some research on my part has determined that there's an RFC for a QUOTA extension to IMAP, and there are plugins for my webmail program (Squirrelmail) which can display the user's quota usage there. Also, some mail clients are smart enough to also query the QUOTA extensions and let the user know how close they are to their max quota usage. I'm also planning a pretty decent-sized technology transition in the near future (switching to a shared-storage system with two servers, etc, etc), and I could be convinced to perhaps try and change my quotaing system at the same time - for instance, switching to filesystem quotas instead of vpopmail quotas, if that will help. The scary possibility that I guess I have to prepare myself for is that dovecot Just Doesn't Do It, and I need to figure out some other way of informing the clients of their quota usage - possibly a script that goes and recurses through maildirs and sends little emails if users are at a certain percentage of their actual usage, or something...I'm certainly not looking forward to writing that, but it's not a fate worse than death...

2 1

[Dovecot] were are my e-mails?
by Paul Matthews 13 Jan '06

13 Jan '06

hi there, i seam to have pretty much everything under control at the moment other than the ability to recieve email's ... i can send them though and i know they get there because i can login into webmin and look in my user's mail boxes and see the e-mails, but for some reason i can retrive them using squirrel mail, can someone tell me why?

1 0

[Dovecot] pop3 CAPA STLS and stupid clients
by Marten Lehmann 13 Jan '06

13 Jan '06

Hello, is it possible to disable the announcment of STLS in the CAPA-command for the pop3-daemon? I want to support pop3s, but only at port 995, not through the STLS on port 110. The reason for this is that some clients have problems with this and strange errors appear (e.g. older imap-libs) although they don't seem to have a problem with pop3s through port 995. Regards Marten

1 0

Re: [Dovecot] PAM Authentication issues with Dovecot
by david.kolts＠entouch.net 13 Jan '06

13 Jan '06

1 0