- dovecot - dovecot.org

[Dovecot] Problems to put dovecot-ldap.conf working
by Venilton Junior 14 Feb '07

14 Feb '07

Hi Folks, I'm having a little trouble to put dovecot authenticating in ldap. My postfix and saslauthd are authenticating fine. Here is what I have in my main.cf: # Accounts accounts_server_host = $ldap_server_host accounts_search_base = $ldap_search_base accounts_query_filter = (&(&(objectClass=VirtualMailAccount)(mail=%s))(forwardActive=FALSE)(acco untActive=TRUE)(delete=FALSE)) accounts_result_attribute = mailbox accounts_cache = no # aliases aliases_server_host = $ldap_server_host aliases_search_base = $ldap_search_base aliases_query_filter = (&(&(objectClass=VirtualMailAlias)(mail=%s))(accountActive=TRUE)) aliases_result_attribute = maildrop aliases_cache = no accountsmap_server_host = $ldap_server_host accountsmap_search_base = $ldap_search_base accountsmap_query_filter = (&(&(objectClass=VirtualMailAccount)(mail=%s))(forwardActive=FALSE)(acco untActive=TRUE)(delete=FALSE)) accountsmap_result_attribute = mail accountsmap_cache = no # VirtualForward virtualforward_server_host = $ldap_server_host virtualforward_search_base = $ldap_search_base virtualforward_query_filter = (&(&(objectClass=VirtualMailAccount)(mail=%s))(forwardActive=TRUE)(accou ntActive=TRUE)(delete=FALSE)) virtualforward_result_attribute = maildrop virtualforward_cache = no My saslauthd.conf follows as: ldap_servers: ldap://myldapserver/ ldap_version: 3 ldap_auth_method: bind ldap_bind_dn: uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot ldap_bind_pw: xxxx ldap_search_base: dc=domain,dc=com #ldap_filter: (|(mail=%u)(cn=%U)) ldap_filter: (&(|(mail=%u)(cn=%U)(mail=%U@%d))(accountActive=TRUE)(delete=FALSE)) PS: Removed my real server and search_base. Here is the test with saslauthd configuration: testsaslauthd -u novoemail01 -p teste123 0: OK "Success." And here is my dovecot-ldap.conf: hosts = myldapserver dn = uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot dnpass = xxxx ldap_version = 3 base = dc=domain,dc=com user_attrs = mail,,,,, user_filter = (&(objectClass=VirtualMailAccount)(mail=%u)(accountActive=TRUE)(delete=F ALSE)) pass_attrs = mail,userPassword pass_filter = (&(objectClass=VirtualMailAccount)(mail=%u)(accountActive=TRUE)(delete=F ALSE)) default_pass_scheme = SSHA When I try to authenticate, my mail.info get this: dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=200.155.34.10 rip=200.155.63.82 resp=AG5vdm9lbWFpbDAxAHRlc3RlMTIz dovecot: auth(default): ldap(novoemail01,200.155.63.82): pass search: base=dc=sercomtel,dc=com,dc=br scope=subtree filter=(&(objectClass=VirtualMailAccount)(mail=novoemail01)(accountActiv e=TRUE)(delete=FALSE)) fields=mail,userPassword dovecot: auth(default): ldap(novoemail01,200.155.63.82): unknown user dovecot: auth(default): client out: FAIL 1 user=novoemail01 Does anyone have an idea where I'm failing to configure this or find a misconfiguration? Tnx for any help. Best Regards, Venilton C. Junior

2 1

[Dovecot] resilience suggestion
by David Lee 14 Feb '07

14 Feb '07

On the whole we are pleased with our trials of dovecot to replace UW-IMAP. But (ah!) we have hit one particular problem, in which we think dovecot could probably benefit from a resilience improvement. We're running dovecot on Fedora Core 5 (FC5), with passwd map details supplied by NIS. We have found that "nscd" sometimes thinks that a username is invalid, even though it is valid. So when "deliver" attempts a delivery to the INBOX of that username, it receives "user unknown" from the name service, and then does a 5xx permanent failure of valid email. >From the user perspective "The System" has incorrectly rejected perfectly valid incoming email. It is rare, but it does occasionally happen on large, busy systems. Clearly it is fundamentally an "nscd" bug. But that bug is nevertheless out there, in the wild, on such systems, potentially affecting dovecot's delivery of valid user email. We have had a source code hack since October (in "deliver.c", simply replacing a "return ret" occurence with "return EX_TEMPFAIL") and it has worked nicely (ported forward from rc8 towards rc22). Mail re-queues and a later delivery attempt then succeeds. So it would be both helpful, and good for resilience against such real OS/nscd bugs (and similar), if there were a configuration option in dovecot to allow a site admin to tell deliver to use a temporary, 4xx, failure instead (if the circumstances were appropriate for the site). Could this be considered please, Timo? -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : : UNIX Team Leader Durham University : : South Road : : http://www.dur.ac.uk/t.d.lee/ Durham DH1 3LE : : Phone: +44 191 334 2752 U.K. :

9 15

[Dovecot] Ubuntu, Exim, deliver: permissions/setgid problem
by Sam Hathaway 14 Feb '07

14 Feb '07

Hello all, I have a little problem. I'm trying to set up Dovecot deliver (1.0 beta 3) as the LDA for Exim4 on Ubuntu 6.06 with MBOX, and I'm running into permissions problems. Exim typically wants to run pipes as the user to whom the mail is being delivered (as per the "check_local_user"). deliver needs access to the auth socket and needs to be able to create files in /var/mail. In Ubuntu, /var/mail is writeable by group mail, but not by others. So I thought I'd make deliver run as the user to whom the mail is being delivered (as per default) and with group "mail" (so it can create files in /var/mail). I also set the auth socket to be group-writeable and gave it the group mail. So theoretically, deliver should be able to: - connect to the socket - create dotfiles in /var/mail - write to the user's mailbox The problem I'm running into is that deliver tries to setgid to the primary group of the target user, and dies when it can't. I specifically do NOT want it to do this, because regular users don't have permission to write to /var/mail. I've also tried making deliver SUID root (as recommended on this list) or SGID mail (like procmail is) but I get the same error. If I also disable the "group = mail" line in the dovecot_deliver_user router in exim4.conf, I still get the same error. If I disable the "group = mail" line without making deliver SUID or SGID, then it can no longer connect to the auth socket. In this case it runs with the group of the user for whom the mail is being delivered, i.e. sam-adm (#10000). I've also tried adding "user = mail" to the transport, to no avail. The ONE way I've been able to make it work is to remove "group = mail" from exim4.conf and set the socket's mode to 0666, but I've seen warnings that allowing world-access to the socket is dangerous. I'm actually not sure why this works, since in this case it's running with both the UID and GID of the target user, and therefore shouldn't be able to create files in /var/mail. Can anyone untangle this for me? From what I've read, in Debian delivery agents should run with group "mail" (procmail is SGID mail). It seems to me that the way to go is to spawn it with group mail, allow group mail access to the auth socket, and be done with it. But this is prevented from working since it insists on resetting back to the user's primary group. Thanks, Sam Hathaway The relevent section of my dovecot.conf looks like this: protocol lda { postmaster_address = postmaster(a)uofr.net log_path = /var/log/dovecot-lda.log } auth default { mechanisms = plain socket listen { master { path = /var/run/dovecot-auth-master mode = 0660 group = mail } } # ... (other auth config directives here) } And the relevent parts of my exim4.conf are as follows: # in router section: local_user: debug_print = "R: local_user for $local_part@$domain" driver = accept domains = +local_domains check_local_user local_part_suffix = +* local_part_suffix_optional local_parts = ! root transport = dovecot_deliver_user # in transport section: dovecot_deliver_user: debug_print = "T: pipe for $local_part@$domain" driver = pipe command = /usr/lib/dovecot/deliver -d $local_part message_prefix = message_suffix = log_output delivery_date_add envelope_to_add return_path_add group = mail Here are the permissions on some interesting files/dirs: -rwxr-xr-x 1 root mail 551424 2006-11-22 21:59 /usr/lib/dovecot/deliver drwxrwsr-t 2 root mail 1024 2007-01-25 14:14 /var/mail -rw-rw---- 1 sam-adm mail 544 2007-01-25 15:58 /var/mail/sam-adm srw-rw---- 1 root mail 0 2007-01-25 15:39 /var/run/dovecot-auth-master And here's how I've been testing: echo "test" | mail -s "deliver test" sam-adm When I execute the above command, exim says: 2007-01-25 15:55:01 1HABcb-0006h4-N8 <= sam-adm(a)vps.uofr.net U=sam-adm P=local S=334 2007-01-25 15:55:02 1HABcb-0006h4-N8 ** sam-adm(a)vps.uofr.net R=local_user T=dovecot_deliver_user: Child process of dovecot_deliver_user transport returned 89 from command: /usr/lib/dovecot/deliver 2007-01-25 15:55:02 1HABcb-0006h4-N8 Completed And deliver says: deliver: "2007-01-25 15:55:02 "Fatal: setgid(10000) failed: Operation not permitted

3 6

[Dovecot] http://wiki.dovecot.org/VirtualhostingWithExim
by Marc Haber 14 Feb '07

14 Feb '07

Hi, Here is a new wording for the "Exim4 on Debian" part of the web page on http://wiki.dovecot.org/VirtualhostingWithExim. It's immutable, so I cannot directly change it. I e-mailed Florian, but he cannot log in to the wiki any more. Can somebody with appropriate privileges change the page? --------------------- If you are using the exim4 packages on Debian, you need to pay attention whether you are using the split or non-split configuration method that the packages offer. If you are using split-configuration, you need to apply the configuration changes to the router and transport directories inside /etc/exim4/conf.d; if you are using non-split configuration, you need to edit /etc/exim4/exim4.conf.template. A restart of the exim daemon with /etc/init.d/exim4 reload will activate your changes. You can find more information about the way Debian configures the exim4 packages in /usr/share/doc/exim4-base/README.Debian or at http://pkg-exim4.alioth.debian.org/README/README.Debian.html or at the Debian wiki (http://wiki.debian.org/PkgExim4) --------------------- Additionally, I would appreciate if the instructions for exim 3 could be removed. exim 3 is obsolete five years now, and new users of exim 4 are constantly finding old exim 3 documentation and fail in applying that docs to exim 4. Greetings Marc, Maintainer for Debian exim4 packages -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835

1 0

[Dovecot] .bz2 plugin?
by David McBride 14 Feb '07

14 Feb '07

Hello all, Is anyone working on a .bz2 plugin similar to the existing zlib plugin? Cheers, David -- David McBride <dwm(a)tastycake.net>

2 1

[Dovecot] dead bodies stacking up in Drafts folder
by Charles Bueche 14 Feb '07

14 Feb '07

Hi, Setup : Apple Mail 2.1.1 (752.3) on Intel MacBook Pro and Dovecot 1.0rc22 on Solaris 9/SPARC. I use IMAP/TLS. Problem : mails are stacking up in the Drafts folder. When I start writing a mail, it appears in the drafts folder, and usually disappear as desired when I hit "Send". It then appear in the "Sent" folder. Sometimes, a draft versions stays in "Drafts", I have 21 of them since 1.1.2007. In this period, I have written about 400 emails, so only about 5 % stick in "Drafts". I can of course periodically select and delete them, but I don't like such glitches. Never sure if emails are really sent. Advice welcome. I'm the Solaris packager and admin so I can test things if needed. Sorry if it's a known Apple Mail issue, I would be the one to beat for using closed-source stuff :-) Charles -- Charles Bueche <charles(a)bueche.ch> sand, snow, wave, wind and net -surfer A-Cat SUI 192

7 9

[Dovecot] [Fwd: Re: Is it 1.0 yet?]
by Gavin Henry 14 Feb '07

14 Feb '07

---------------------------- Original Message ---------------------------- Subject: Re: [Dovecot] Is it 1.0 yet? From: "Raymond Lillard" <ryl(a)plasmaequip.com> Date: Tue, February 13, 2007 11:16 pm To: "Gavin Henry" <ghenry(a)suretecsystems.com> -------------------------------------------------------------------------- -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gavin Henry wrote: > <quote who="Marc Perkel"> >> OK - my last main bug was fixed a few releases ago. I know that there's >> no end to getting things right but there comes a point when you need to >> call it done. No one trusts a 1.0 to be perfect but Dovecot is already >> better that most 2.0 versions of other software. >> >> I vote (as if my vote counted) to call it done, declare victory, and >> move on to 1.01, 1.02 etc. No one is going to trus it till it gets to >> 1.02 so I say lets bless it and move on. >> >> > > +1 > > +2 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF0kbLW6j0KQLSyTQRAhbZAJ0SAJDaNES4wV+UajiKJ0ByObbP5gCfXfdv CU2v+W+diqDAnarYRncXj2s= =XTcI -----END PGP SIGNATURE-----

1 0

[Dovecot] Chdir Permission Denied
by Jamie Heinzel 13 Feb '07

13 Feb '07

Here are the error messages I get when anyone tries to login. Feb 13 11:22:17 mail dovecot: chdir(/home/don150) failed with uid 776: Permission denied Feb 13 11:22:17 mail imap-login: Login: don150 [::ffff:192.168.146.10] Feb 13 11:22:17 mail dovecot: child 12101 (imap) returned error 89 I am not running SELinux so I'm not sure what is happening here. All was working fine this morning, then at about 9:30 am nobody could log in. Any help would be great. Thanks!

2 2

Re: [Dovecot] [Fwd: Disable a User's email account]
by Steffen Kaiser 13 Feb '07

13 Feb '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 13 Feb 2007, Michael Surette wrote: Hello, I'm not sure why you'd not mail this info the one, who had created the thread. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRdHa9y9SORjhbDpvAQLFoQf+PZUZZ6bHwhcKIh+8eTK3h4wEuF0lAqjE zuOjOC5D08bOgY86qt84vWqA+MYt9QTCXTPlTFxQYQESf5IgqgwKbPbl0PHxoc/1 GOddQ+Hd7I9lt42iWukqYtd6LGAV6CTIhZIFRm6uVnZYm1Or+3kiyFhiwMwkxSKF NfcsUYVenAhtfNSXOEALaBhvzdD/uUsZX/G/whq6y9A2xPOE25zdVxLPLP+F+mk3 enShwoGa1AMV6snOOEJIRkJ4QwuCacjuQjduyBKpn72rQukZBrHoJes8DOGdIKSx 3BrFz6ck+H+7hHt+vH6ukk2fRO7nkheltrMiCc22Uf97UIychHNrOA== =NWw9 -----END PGP SIGNATURE-----

1 0

[Dovecot] Apple mail
by Аркадий Володин 13 Feb '07

13 Feb '07

I have strange situation with Appe mail and latest (rc22) Dovecot. I using "mbox" POP3 (not IMAP) type of message box on server (exim: driver=appendfile) I also using MySQL authentification and SSL. Server - Linux Slackware 11.0 Linux/Thunderbird, WinXP/Thunderbird, WinXP/Outlook clients are working fine with their message boxes. But Apple mail doesn't delete messages in user's mbox, so client gets a lot of duplicate messages. As I see in such a mbox, there isn't system message like: >From MAILER_DAEMON Tue Feb 13 14:41:08 2007 Date: Tue, 13 Feb 2007 14:41:08 +0000 From: Mail System Internal Data <MAILER-DAEMON@mail> Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA Message-ID: <1171377668@mail> X-IMAP: 1169824263 0000000019 Status: RO But every message in such a box marked as "Status: RO" Please, help me to solve this trouble.

1 0

[Dovecot] error message after migration UW --> DOVECOT
by Frank Bonnet 13 Feb '07

13 Feb '07

Hello I get a lot of messages looking as above since I migrate from UW dovecot: Feb 13 10:27:44 Error: IMAP(xxxxxxxx): mbox sync: UID inserted in the middle of mailbox /user/xxxxxxxx/Trash (7 > 5, seq=2, idx_msgs=2) What would be the impact for my users ? Thanks a lot Frank

2 1

[Dovecot] [Fwd: Disable a User's email account]
by edwardspl＠ita.org.mo 13 Feb '07

13 Feb '07

Dear All, The System is FC6... So, how to disbale a User's mail service ? eg : Sendmail ( SMTP ) + Dovecot ( pop3 /imap ). Edward. -- fedora-list mailing list fedora-list(a)redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

6 12

[Dovecot] PAM, NSS, and a new blocking=yes setting
by Timo Sirainen 13 Feb '07

13 Feb '07

I wondered for a while if I should do this before v1.0, but since there seem to be problems with some PAM/NSS users and this was way easier to implement than I realized, here it is: passdb pam and userdb passwd now support blocking=yes setting in their args. For PAM the default has been to fork the dovecot-auth process and talk via a pipe to the main dovecot-auth. I've never really liked this approach, but didn't bother fixing it before. However it is also what has caused the bugs with nss_ldap, and maybe with other NSS backends too. NSS lookups then have been done all in the same dovecot-auth process without any forking. This meant that if it got stuck (or delayed a bit in LDAP queries and such), the whole dovecot-auth got stuck and all authentication attempts got stuck. With blocking=yes the lookups are handled in dovecot-auth worker processes. Earlier these workers have been used only with MySQL. Initially there is only a single worker process, but whenever dovecot-auth notices that there are no free workers while a new auth request comes, a new worker is created. auth_worker_max_count specifies the maximum number of those processes. This blocking=yes will probably work great with NSS. With PAM I'm not so sure. Mostly because the worker never exits, it just does one PAM auth after another. I think usually PAM is used only once in a process, so there might be memory leaks and maybe other bugs.. Then again, maybe not. I'll add some auth_worker_max_requests setting which can be set to 1 if this is a problem. Also for blocking=no case I added code to send KILL signal to PAM child processes which haven't replied for 2 minutes. With blocking=yes this condition can't be checked currently. http://dovecot.org/list/dovecot-cvs/2007-February/007639.html http://dovecot.org/list/dovecot-cvs/2007-February/007642.html http://dovecot.org/list/dovecot-cvs/2007-February/007646.html

2 2

[Dovecot] MD5-CRYPT passwords in a MySQL Database
by David Mills 13 Feb '07

13 Feb '07

First of all, hello to the list. I'm currently migrating from a /etc/passwd and /etc/shadow based configuration to a MySQL based one using dovecot 99.14 on debian sarge. The problem is that the /etc/shadow containes both DES encoded (Crypt) and md5 based passwords. I've set the default system to be Crypt, and have added {MD5-CRYPT} in front of the md5 passwords in place of the $1$ header found in /etc/shadow. But I can only log in on accounts that have DES based passwords. I've included my dovecot configuration, and below are 2 examples of encoded password, one crypt and one MD5: XalGYN3cy1crA {MD5-CRYPT}RL$Bvv.TF2XJkyVI6JOUO8tx/ If anyone has any ideas I'd really appreciate them since 80 odd accounts have this problem, so changing them one by one will be difficult. David -- David Mills Enki Technologies 01 76 00 71 20 *De nouvelles offres d'emploi...* *...pour bien démarrer 2007 !* Consulter la news <http://www.enki.fr/detail_actualite.htm?ACTU=13> - enki.fr <http://www.enki.fr> ## Dovecot 1.0 configuration file # 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 --sysconfdir=/etc/dovecot # --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 = imaps pop3 pop3s # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. You can specify ports with # "host:port". #imap_listen = * #pop3_listen = * # IP or host address where to listen in for SSL connections. Defaults # to above non-SSL equilevants if not specified. #imaps_listen = #pop3s_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. #ssl_cert_file = /etc/ssl/certs/dovecot.pem #ssl_key_file = /etc/ssl/private/dovecot.pem # 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 # 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 " ## ## 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 ## ## IMAP login process ## login = imap # Executable location. #login_executable = /usr/lib/dovecot/imap-login # 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 ## ## POP3 login process ## # Settings default to same as above, so you don't have to set anything # unless you want to override them. login = pop3 # Exception to above rule being the executable location. #login_executable = /usr/lib/dovecot/pop3-login ## ## 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 = 106 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # 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 # /usr/share/doc/dovecot-common/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden by # giving /./ in user's home directory (eg. /home/./user chroots into /home). #mail_chroot = # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # /usr/share/doc/dovecot-common/mail-storages.txt. There's a few special # variables you can use: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if user there's no domain # %h - home directory # # You can also limit a width of string by giving the number of max. characters # after the '%' character. For example %1u gives the first character of # username. 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:~/mail/:INBOX=/var/mail/%u # Space-separated list of fields to cache for all mails. Currently these # fields are allowed followed by a list of commands they speed up: # # Envelope - FETCH ENVELOPE and SEARCH FROM, TO, CC, BCC, SUBJECT, # SENTBEFORE, SENTON, SENTSINCE, HEADER MESSAGE-ID, # HEADER IN-REPLY-TO # Body - FETCH BODY # Bodystructure - FETCH BODY, BODYSTRUCTURE # MessagePart - FETCH BODY[1.2.3] (ie. body parts), RFC822.SIZE, # SEARCH SMALLER, LARGER, also speeds up BODY/BODYSTRUCTURE # generation. This is always set with mbox mailboxes, and # also default with Maildir. # # Different IMAP clients work in different ways, that's why Dovecot by default # only caches MessagePart which speeds up most operations. Whenever client # does something where caching could be used, the field is automatically marked # to be cached later. For example after FETCH BODY the BODY will be cached # for all new messages. Normally you should leave this alone, unless you know # what most of your IMAP clients are. Caching more fields than needed makes # the index files larger and generate useless I/O. # # With maildir there's one extra optimization - if nothing is cached, indexing # the maildir becomes much faster since it's not opening any of the mail files. # This could be useful if your IMAP clients access only new mails. #mail_cache_fields = MessagePart # Space-separated list of fields that Dovecot should never set to be cached. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Workarounds for various client bugs: # oe6-fetch-no-newmail: # Never send EXISTS/RECENT when replying to FETCH command. Outlook Express # seems to think they are FETCH replies and gives user "Message no longer # in server" error. 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. # outlook-pop3-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. #client_workarounds = # Dovecot can notify client of new mail in selected mailbox soon after it's # received. This setting specifies the minimum interval in seconds between # new mail notifications to client - internally they may be checked more or # less often. Setting this to 0 disables the checking. # NOTE: Evolution client breaks with this option when it's trying to APPEND. #mailbox_check_interval = 0 # 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 custom flag name. It's only forced when trying # to create new flags. #mail_max_flag_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. #mail_read_mmaped = no # 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 # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing messages are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's three 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. # # You can use both fcntl and flock too; if you do the order they're declared # with is important to avoid deadlocks if other MTAs/MUAs are using both fcntl # and flock. Some operating systems don't allow using both of them # simultaneously, eg. BSDs. If dotlock is used, it's always created first. #mbox_locks = dotlock fcntl # Should we create dotlock file even when we want only a read-lock? Setting # this to yes hurts the performance when the mailbox is accessed simultaneously # by multiple processes, but it's needed for reliable reading if no other # locking methods are available. #mbox_read_dotlock = no # 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 # 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. Note that setting # this to yes means that log file is opened as the logged in user, which # might not work. It could also 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 ## ## IMAP process ## # Executable location #imap_executable = /usr/lib/dovecot/imap # 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. #imap_process_size = 256 # Support for dynamically loadable modules. #imap_use_modules = no #imap_modules = /usr/lib/dovecot/imap ## ## POP3 process ## # Executable location #pop3_executable = /usr/lib/dovecot/pop3 # 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. #pop3_process_size = 256 # Support for dynamically loadable modules. #pop3_use_modules = no #pop3_modules = /usr/lib/dovecot/pop3 ## ## Authentication processes ## # An Authentication process is a child process used by Dovecot that # handles the authentication steps. The steps cover an authentication # mechanism (auth_mechanisms, how the client authenticates in the IMAP or # POP3 protocol), which password database should be queried (auth_passdb), # and which user database should be queried (auth_userdb, to obtain # UID, GID, and location of the user's mailbox/home directory). # # You can have multiple processes, though a typical configuration will # have only one. Each time "auth = xx" is seen, a new process # definition is started. The point of multiple processes is to be able # to set stricter permissions. (See auth_user below.) # # Just remember that only one Authentication process is asked for the # password, so you can't have different passwords accessible through # different process definitions (unless they have different # auth_mechanisms, and you're ok with having different password for # each mechanisms). # Authentication process name. auth = default # Specifies how the client authenticates in the IMAP protocol. # Space separated list of permitted authentication mechanisms: # anonymous plain digest-md5 cram-md5 # # anonymous - No authentication required. # plain - The password is sent as plain text. All IMAP/POP3 clients # support this, and the password can be encrypted by Dovecot to match # any of the encryption schemes used in password databases. # digest-md5 and cram-md5 - both encrypt the password so it is more # secure in transit, but are not well supported by clients, and # require that the password database use a matching encryption # scheme (or be in plaintext). # # See auth.txt for more details. # # If you are using SSL there is less benefit to digest-md5 and # cram-md5 as the communication is already encrypted. auth_mechanisms = plain # 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 = # 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 # passwd: /etc/passwd or similiar, using getpwnam() # passwd-file <path>: passwd-like file with specified location # static uid=<uid> gid=<gid> home=<dir template>: static settings # vpopmail: vpopmail library # ldap <config path>: LDAP, see /etc/dovecot/dovecot-ldap.conf # mysql <config path>: a MySQL database, see /etc/dovecot/dovecot-mysql.conf # pgsql <config path>: a PostgreSQL database, see # /etc/dovecot/dovecot-pgsql.conf auth_userdb = passwd #auth_userdb = static uid=139 gid=139 home=/home/users/%u/ # Password database specifies only the passwords for users. # http://wiki.dovecot.org/Authentication # passwd: /etc/passwd or similiar, using getpwnam() # shadow: /etc/shadow or similiar, using getspnam() # pam [<service> | *]: PAM authentication # passwd-file <path>: passwd-like file with specified location # vpopmail: vpopmail authentication # ldap <config path>: LDAP, see /etc/dovecot/dovecot-ldap.conf # mysql <config path>: a MySQL database, see /etc/dovecot/dovecot-mysql.conf # pgsql <config path>: a PostgreSQL database, see # /etc/dovecot/dovecot-pgsql.conf #auth_passdb = shadow auth_passdb = mysql /etc/dovecot/dovecot-mysql.conf #auth_executable = /usr/lib/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # 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 auth_userdb above. auth_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. #auth_chroot = # Number of authentication processes to create #auth_count = 1 # 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 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 # digest-md5 authentication process. It requires special MD5 passwords which # /etc/shadow and PAM doesn't support, so we never need roots to handle it. # Note that the passwd-file is opened before chrooting and dropping root # privileges, so it may be 0600-root owned file. #auth = digest_md5 #auth_mechanisms = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = # if you plan to use only passwd-file, you don't need the two auth processes, # simply set "auth_methods = plain digest-md5" # For the mysql passdb module, you'll need a database with a table that # contains fields for at least the userid and password. If you want to # use the user@domain syntax, you might want to have a separate domain # field as well. # # If your users all have the same uig/gid, and have predictable home # directories, you can use the static userdb module to generate the home # dir based on the userid and domain. In this case, you won't need fields # for home, uid, or gid in the database. # # If you prefer to use the mysql userdb module, you'll want to add fields # for home, uid, and gid. Here is an example table: # # CREATE TABLE users ( # userid VARCHAR(128) NOT NULL, # password VARCHAR(64) NOT NULL, # home VARCHAR(256) NOT NULL, # uid INTEGER NOT NULL, # gid INTEGER NOT NULL, # active CHAR(1) DEFAULT 'Y' NOT NULL # ); db_host = localhost db_port = 3306 db_unix_socket = /var/run/mysqld/mysqld.sock db = mail db_user = dovecot db_passwd = 3eDcVb db_client_flags = 0 # Default password scheme. # # Currently supported schemes include PLAIN, PLAIN-MD5, DIGEST-MD5, and CRYPT. # default_pass_scheme = CRYPT # Query to retrieve the password. # # The query should return one row, one column. If more than one row or column # is returned, authentication will automatically fail. # # Available substitutions: # %u = entire userid # %n = user part of user@domain # %d = domain part of user@domain # # Example: # password_query = SELECT password FROM users WHERE userid = '%n' AND domain = '%d' # password_query = SELECT password FROM users WHERE userid = '%u' AND active = 'Y' # password_query = SELECT password FROM enki_users WHERE username = '%u' # Query to retrieve the user information. # # The query must return only one row. The columns to return are: # home - Home directory # mail - MAIL environment # system_user - System user name (for initgroups()) # uid - System UID # gid - System GID # # Either home or mail is required. uid and gid are required. If more than one # row is returned or there's missing fields, login will automatically fail. # # Examples # user_query = SELECT home, uid, gid FROM users WHERE userid = '%n' AND domain = '%d' # user_query = SELECT dir AS home, user AS uid, group AS gid FROM users where userid = '%u' # user_query = SELECT home, 501 AS uid, 501 AS gid FROM users WHERE userid = '%u' # #user_query = SELECT home, uid, gid FROM users WHERE userid = '%u'

2 1

[Dovecot] pop3 via tls
by jepoy 13 Feb '07

13 Feb '07

hi guys, i want to try pop3 using tls, just like smtp. is it possible ? i want to first create a secure tunnel before donwloading the mails. tnx -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

2 1

[Dovecot] Problems with HUP'ing dovecot
by Javier Henderson 13 Feb '07

13 Feb '07

Hi, I'm running dovecot 1.0.rc7 on FreeBSD 6.1, so far with great success. Earlier today I tried to HUP the main process, the following was logged: dovecot: Feb 12 15:10:19 Warning: SIGHUP received - reloading configuration dovecot: Feb 12 15:10:19 Panic: file ioloop-poll.c: line 105 (io_loop_handle_remove): assertion failed: (index >= 0 && (unsigned int) index < ctx->fds_count) Of possible interest: just prior to issuing the HUP I had edited the / etc/resolv.conf file to take out the first entry since that particular DNS server went off line. I noticed that login attempts to the POP and IMAP services were timing out and that's when I sent the HUP to dovecot. Any ideas? Thanks, -jav

2 1

[Dovecot] mail_location and storage type
by Jürgen Herz 13 Feb '07

13 Feb '07

Hi, I was setting up a new system for testing Dovecot 1.0. My old one is using 0.99 and was set up quite a time ago, so I had to consult the documentation. I needed several attempts until it worked and that was because the designated maildir directory /server/mail/jrg/Maildir was completely empty. Upon login the server exited and wrote the following to the log: POP3(jrg): Ambiguous mail location setting, don't know what to do with it: /server/mail/jrg/Maildir (try prefixing it with mbox: or maildir:) POP3(jrg): Failed to create storage with data: /server/mail/jrg/Maildir That thing was the main cause of my confusion since the config wasn't ambiguous at all at already contained a prefix: mail_location = maildir:/server/mail/%u/Maildir The wiki article MailLocation doesn't contain any hint maildirs have to contain at least a cur subdirectory. That information I eventually got from mail-storages.txt - that file must be one for which the wiki isn't an alternative. So what is this mail about? 1. The log message is wrong or at least missleading. Would be fine if it could get improved. 2. Is there any reason at all to have a storage prefix but still require some special format for the directory in order to recognize it? 3. At least if the behaviour will stay, shouldn't the text from mail-storages.txt converted to a wiki article or incorporated into MailLocation? Regards, Juergen

2 3

[Dovecot] Compiler warnings
by Stephen Lee 12 Feb '07

12 Feb '07

Hi, I'm trying to install Dovecot 1.0RC22 on an old Trustix 1.5 box and am getting the compiler warnings: quota-storage.c:275: warning: pointer of type `void *' used in arithmetic convert-storage.c:50: warning: pointer of type `void *' used in arithmetic acl-backend-vfile.c:212: warning: pointer of type `void *' used in arithmetic There are many more of these pointer warnings in the various modules when compiling. Is this a problem? Thanks, Stephen

2 1

[Dovecot] Differences between IDLE when Maildir vs. wel the "mail" folder is used
by Philip Van Hoof 12 Feb '07

12 Feb '07

Are there any differences with how both IDLE and "UID FETCH n:n+x (FLAGS UID...)" are handled when Dovecot is using a "mail" vs. a "Maildir" user? I have recently implemented support for IDLE (Push E-mail) in a client infrastructure that I'm building. I haven't in depth checked out what the problem might be, but when Dovecot was using the "mail" dir in $HOME something about the implementation wasn't working. When I switched to "Maildir" everything worked. I only tested to the point of seeing the "* EXISTS n" response during the idle. I saw this response. It's for example possible that the n is wrong or that a bit later the "UID FETCH ..." ain't returning the right information. It's also possible that my implementation is wrong (of course) and I haven't yet had the time to really figure out what goes wrong. I did so far, however, test with Cyrus, Exchange, Courier and Isode's M-Box. All these tests where successful. SO if it indeed is a discrepancy in my implementation .. it's going to be something very specialised or specific I fear :-) I also setup testing infrastructure http://tinymail.org/trac/tinymail/wiki/TestImapServers Also take a careful look at this manual test. "tnytest" is a user on imap2.tinymail.org that uses Maildir. The "tnytest2" user doesn't have a Maildir configured. By that I mean that "Dovecot" has created the folder for E-mail using whatever it uses by default. Dovecot's IDLE (the EXISTS) responses also take a lot longer on tnytest2 than on tnytest. Another question. Why not simply "always" use the Maildir solution if that one works better? ;-) (really, honest question. Hehe). Take a look at the "UID FETCH" response: It's incorrect on tnytest2. The first attempt I asked for 1:1 and I got none. The second I asked for 1:4 and I got 3 of them, while IDLE clearly stated that there where 4 messages available. In reality 4 where indeed available (or copied in total). Well, I'm not saying something is or isn't wrong, just wondering and testing a little bit and seeing some strange results... Feel free to use imap2.tinymail.org for testing. And if you need root on that virtual machine, so that you can install a new version, go ahead. On http://imap2.tinymail.org you van find things like version information (it's a CVS snapshot). pvanhoof@lort:~$ telnet imap2.tinymail.org Trying 86.39.154.77... telnet: Unable to connect to remote host: Connection refused pvanhoof@lort:~$ telnet imap2.tinymail.org 143 Trying 86.39.154.77... Connected to imap2.tinymail.org. Escape character is '^]'. * OK Dovecot ready. ao1 login tnytest tnytest ao1 OK Logged in. a01 select INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 0 RECENT * OK [UIDVALIDITY 1171049606] UIDs valid * OK [UIDNEXT 2] Predicted next UID a01 OK [READ-WRITE] Select completed. a04 IDLE + idling * 2 EXISTS DONE a04 OK Idle completed. UID FETCH 1:2 (FLAGS UID) * 1 FETCH (FLAGS (\Seen) UID 1) * 2 FETCH (FLAGS (\Seen) UID 2) UID OK Fetch completed. ^] telnet> quit Connection closed. pvanhoof@lort:~$ telnet imap2.tinymail.org 143 Trying 86.39.154.77... Connected to imap2.tinymail.org. Escape character is '^]'. * OK Dovecot ready. a01 login tnytest2 tnytest a01 OK Logged in. a01 select INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1171107413] UIDs valid * OK [UIDNEXT 1] Predicted next UID a01 OK [READ-WRITE] Select completed. a04 IDLE + idling * 1 EXISTS DONE a04 OK Idle completed. a05 UID FETCH 1:1 (FLAGS UID) a05 OK Fetch completed. a04 IDLE + idling * 4 EXISTS DONE a04 OK Idle completed. a06 UID FETCH 1:4 (FLAGS UID) * 1 FETCH (FLAGS (\Seen) UID 2) * 2 FETCH (FLAGS (\Seen) UID 3) * 3 FETCH (FLAGS (\Seen) UID 4) a06 OK Fetch completed. -- Philip Van Hoof, software developer home: me at pvanhoof dot be gnome: pvanhoof at gnome dot org http://www.pvanhoof.be/blog

2 1

[Dovecot] PLAIN-MD5 password scheme with salt?
by Steffen Weber 12 Feb '07

12 Feb '07

Hello! I'm storing passwords as MD5 hashes in a MySQL database and have specified "default_pass_scheme = PLAIN-MD5" in dovecot-sql.conf. Can Dovecot append or prepend a salt to a password before hashing them? Because without salt the plaintext passwords can be restored from the MD5 hashes using rainbow tables. Greetings Steffen Weber

2 3

[Dovecot] mbox and dual-use folders?
by John Robinson 12 Feb '07

12 Feb '07

Feature request: please can we have support for messages stored in mbox files, but folders containing both messages and folders. I think this could be done for a folder called e.g. dovecot-list by having an mbox file called dovecot-list and a directory called dovecot-list.folder (or whatever, says he handwaving away name clashes which can be worked around like they are in maildirs). This may be a subset or variant of http://wiki.dovecot.org/FeatMboxMaildir Cheers, John.

2 1

[Dovecot] IMAP/POP3 server with proxy feature
by Jasper Bryant-Greene 12 Feb '07

12 Feb '07

We are currently evaluating the migration from a proprietary, legacy mail server onto Dovecot for 20,000+ virtual domains. This is a big job and we intend to do it by initially proxying connections through to the legacy server, and moving customers over in batches by turning off the proxy feature for them. In the manual it states "This model is still a bit unfinished in current code" [1]. What is needed to get this production-quality? I'm happy to help out with any work required. [1] http://wiki.dovecot.org/ImapProxy -- Jasper Bryant-Greene Director Album Limited jasper(a)albumltd.co.nz +64 21 708 334 / 0800 425 286 http://www.albumltd.co.nz/

5 4

Re: [Dovecot] Reproducible duplicate messages bug with Mail.app+Dovecot / may imap bug from mail apple
by Andrew Moran 12 Feb '07

12 Feb '07

On Feb 10, 2007, at 4:30 PM, Robert Schetterer wrote: > > Hi Andrew, > > i investigated the imap bugs from apple mail app with google > trough the years, and i saw there was no version without a bug with > imap, so i speculate its not dovecot what does something wrong here > Oh I have no doubt that Apple's Mail.app is very buggy, but I submit a bug to them which only happens with dovecot IMAP server, I'm sure they are going to be quick to blame dovecot rather than investigate it fully. This is why I was hoping that someone on this list who has Mail.app and Dovecot can (a) verify that it is happening for them (it's 100% reproducible to me) and (b) figure out exactly what's going on, at least to the point of knowing it's Mail.app's fault and not something Dovecot is doing, or a combination of both (such as dovecot doing something other IMAP servers don't and Mail.app misinterpreting it). --Andy

3 2

[Dovecot] Shared folders plans for the future
by Timo Sirainen 11 Feb '07

11 Feb '07

So while driving for several hours in my car recently and having nothing else to do, I started thinking how they could be done. I think the "public folders" configuration will stay as it is now. Does it really even need anything else? The problematic case is how the users can share their mailboxes to other users. There are two problems related to it: 1) How to get (quickly) a list of another user's mailboxes that I have access to? 2) How to get quickly a list of all users who have mailboxes that I have access to? The 1) problem is easier to solve. Create a directory listing all the mailboxes that are shared to at least someone (have ACLs set). It could be configured like: namespace shared { # IMAP namespace prefix, %u expands to shared user prefix = user/%u/ # Directory containing symlinks to user's all shared mailboxes share_dir = ~/Maildir/shared # Where to store indexes for other users' accessed mailboxes index_dir = ~/Maildir/others-indexes } The ~/Maildir/shared directory could then contain symlinks to all the shared mailboxes. The directory list could probably be in Maildir++ layout even though the symlinks would point to mboxes. This requires adding code that can handle mixed maildir/mbox directories, but it'll come anyway.. The 2) problem is more difficult. There are 3 choices: a) Use a shared database file. lib-dict could be used for this, so the database could be in SQL or in a berkeley db file. The downside to this is that the file needs to be readable and writable to everyone, so if users have shell access the users could break the file. They dictionary would contain data in format "<destination_user>/<sharing_user>" = 1 and "<destination_group>/<sharing_user>" = 1, ie. the value would be ignored and only the existence of the keys would be important. Then iterating through "<my_username>/*" and "<all_my_groups>/*" would list the users who probably have mailboxes where I have access to. b) Use a directories with sticky bit set. Well, basically the same idea as in a), except filesystem would be used. Actually perhaps this could be made another lib-dict backend.. c) Brute force: Just assume everyone potentially have shared mailboxes. Get the list of users by readdir()ing through /home (configurable). I guess each of these could be made an option.. So something like: namespace shared { .. # a) shared_dict = db:/var/lib/dovecot/shared-mailboxes.db # b) shared_dict = dir:/var/lib/dovecot/shared-mailboxes # c) shared_dict = bruteforce:/home } I'm currently also implementing a "mailbox list index", which contains a list of all the user's mailboxes and some useful metadata for them, such as number of messages and so on. So that STATUS command wouldn't need to open the mailbox index files if they haven't changed. The mailbox list index updating is normally done when directory's mtime has changed. For list of shared users that would also work in 2b) and 2c) cases, but for 2a) I'd either have to always sync everything or alternatively add some sequence/<dest_user/group>=# value which is grown for each update, and the syncing is done only when the sequence is updated.

6 17

[Dovecot] help needed - dovecot-ldap authentication
by Vidyasagar Warge 10 Feb '07

10 Feb '07

I am trying to set a up mail server on a ubuntu edgy machine. I followed the howto at http://wanderingbarque.com/howtos/mailserver/mailserver.html . I am able to configure everything except dovecot-ldap authentication :(. After struggling with it for a week I decided to seek help. The current version of dovecot is v1.0 RC21 and the version used for the howto is v0.99.10.9. I installed & tried to configure both versions but none of them was able to authenticate a user from ldap. I noted some differences in syntax of the dovecot.conf files of both the versions. It seems that the ldap documentation at dovecot site is from the old version of dovecot ( I might be wrong on this!). So if anyone can tell me how to configure the current version of dovecot with openldap? Please help me! I am eagerly waiting for your response. Regards, Vidyasagar

2 1

[Dovecot] where is the subfolders
by P Y Tan 10 Feb '07

10 Feb '07

I have just set up a dovecot IMAP + Maildir. Would any one tell me where Dovecot store the subfolders and how to delete invalid folders.

2 1

[Dovecot] 1.0.rc21 released
by Timo Sirainen 10 Feb '07

10 Feb '07

http://dovecot.org/releases/dovecot-1.0.rc21.tar.gz http://dovecot.org/releases/dovecot-1.0.rc21.tar.gz.sig Just one fix. Maybe the one big thing in Dovecot v2.0.* will be a test suite, which is run before any release. :) - Cache file handling could have crashed rc20

11 19

[Dovecot] Lda does not query pgsql
by Tognini Samuele 09 Feb '07

09 Feb '07

Hi, I don't know if it's a bug or my configuration fault, but LDA does not work as i expect. Dovecot auth connects to a pgsql database that mirrors Nis users infos, but it has also quota settings because i'd like to use a per-user quota environment. Mailserver and Postfix authenticates users with Nis (through PAM), while imap and local delivery (with the postfix mailbox_command setting) are left to dovecot mechanism. Imap works perfectly, dovecot retrieves authentication and quota setting from database, but dovecot LDA seems to not query any database (and nothing is logged) , so that quota is not retrived and message is not bounced when user is overquota. You can see it in the verbose log: deliver(tognini): 2007-02-08 12:25:02 Info: Loading modules from directory: /usr/lib/dovecot/modules/lda deliver(tognini): 2007-02-08 12:25:02 Info: Module loaded: /usr/lib/dovecot/modules/lda/lib10_quota_plugin.so deliver(tognini): 2007-02-08 12:25:02 Info: Module loaded: /usr/lib/dovecot/modules/lda/lib90_cmusieve_plugin. so deliver(tognini): 2007-02-08 12:25:02 Info: mbox: data=/home/t/tognini:INBOX=/var/spool/mail/tognini deliver(tognini): 2007-02-08 12:25:02 Info: mbox: root=/home/t/tognini, index=/home/t/tognini, inbox=/var/spool/mail/tognini deliver(tognini): 2007-02-08 12:25:02 Info: cmusieve: Using sieve path: /home/t/tognini/.dovecot.sieve deliver(tognini): 2007-02-08 12:25:02 Info: msgid=<20070208112502.7706B3273D6(a)arturo.cli.di.unipi.it>: saved mail to INBOX If i set quota variable in dovecot.conf, still no query but the global variable is used for all users: ... deliver(tognini): 2007-02-07 12:33:04 Info: dirsize quota limit = 1024kB ... My Debian server packages are: dovecot-common/unstable 1.0.rc22-1 postfix/testing 2.3.6-1 postgresql/testing 7.5.22 Dovecot.conf: protocols = imap imaps log_path = /var/log/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = Server ready. mail_location = mbox:%h:INBOX=/var/spool/mail/%u mail_extra_groups = mail mail_debug = yes mbox_read_locks = dotlock fcntl mbox_write_locks = dotlock fcntl protocol imap { mail_plugins = quota imap_quota imap_client_workarounds = outlook-idle tb-extra-mailbox-sep } auth_verbose = yes auth_debug = yes auth_debug_passwords = yes auth default { user = root mechanisms = plain passdb sql { args = /etc/dovecot/dovecot-sql.conf } userdb sql { args = /etc/dovecot/dovecot-sql.conf } userdb prefetch { } socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = mail # User running Dovecot LDA group = mail # Or alternatively mode 0660 + LDA user in this group } } } protocol lda { postmaster_address = samuele(a)example.org mail_plugins = quota cmusieve log_path = /var/log/dovecot-deliver.log info_log_path = /var/log/dovecot-deliver.log } plugin { #quota = dirsize:storage=1024 # every user gets this quota, but it's not what i want. } Dovecot-sql.conf: driver = pgsql connect = host=192.168.1.2 dbname=dovecot user=myuser password='mypasswd' default_pass_scheme = CRYPT password_query = SELECT password, home as userdb_home, uid as userdb_uid, gid as userdb_gid, 'dirsize:storage='||quota as userdb_quota FROM user_accounts WHERE username = '%u' AND active = '1' #user_query = SELECT home, uid, gid, quota FROM user_accounts WHERE username = '%u' user_query = SELECT home, uid, gid, 'dirsize:storage=' || quota AS quota FROM user_accounts WHERE username = '%u' Postfix main.cf: ... mailbox_size_limit = 0 recipient_delimiter = + mailbox_command = /usr/lib/dovecot/deliver .... Postgresql table: Table "public.user_accounts" Column | Type | Modifiers ----------+------------------------+------------------------------ username | character varying(12) | not null uid | integer | not null gid | integer | not null password | character varying(32) | home | character varying(255) | not null active | character(1) | not null default 'Y'::bpchar quota | integer | not null default 512 Thanks in advance for any help or suggestion, Samuele

1 1

[Dovecot] error on pop3
by jepoy 09 Feb '07

09 Feb '07

hi guys, just got this error after install quota. -ERR [IN-USE] Couldn't sync mailbox. tnx -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

3 4

[Dovecot] LSUB * error solved on rc22
by Gavin Henry 09 Feb '07

09 Feb '07

Hi All, Just a quickie to say ew are running the latest version now. Our LSUB error was due to: open(/var/mail/public/.Projects/dovecot-acl) failed: Permission denied Thanks. -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E ghenry(a)suretecsystems.com Open Source. Open Solutions(tm). http://www.suretecsystems.com/

1 0

[Dovecot] why is there email in my mbox file?
by Kendall Shaw 09 Feb '07

09 Feb '07

Hi, I've installed dovecot-imapd under ubuntu. My account and root are the only email accounts on my computer. I transitioned from using GNUS with fetchmail, exim and movemail, to gnus with exim, fetchmail and imap, so I've kept the mbox format email instead of changing to maildir. This works okay, except my mbox file is giant. I expected dovecot to take the mail out of the mbox file and put it somewhere. But, I see there's a big mbox file (/var/mail/me) that keeps growing. Is dovecot using that as the store of messages? If I were to move to using maildir instead of mbox, what is going to happen to my existing mail? Kendall

2 4

[Dovecot] Feature Request
by Jay Chandler 09 Feb '07

09 Feb '07

How much trouble would it be to have the name of the .subscriptions file set via the configuration file, or failing that, as a compile-time option? I find that editing the source directly is a bit of a harrowing experience, particularly when doing it as part of a package management system such as an RPM or the FreeBSD ports tree. -- Jay Chandler Network Administrator, Chapman University 714.628.7249 / chandler(a)chapman.edu Today's Excuse: Too many interrupts

2 1

[Dovecot] Folders compat. problem ?
by Frank Bonnet 08 Feb '07

08 Feb '07

Hi A user here has a strange problem when I moved my imap server from UW-IMAP to Dovecot. A folder created monthes ago with mozilla mail (windows client) became suddenly invisible when I stopped UW then started Dovecot. I really think that IMAP created folders a fully compatibles between UW and Dovecot but I'm curious to know from where does come this trouble ??? Anyone had experienced the same problem ? Thanks a lot.

2 2

[Dovecot] duplicate emails
by Alex 07 Feb '07

07 Feb '07

i'm working with dovecot-1.0.rc15 I have receive a lot of duplicate emails with microsoft outlook, i don't have this problem with outlook express This is in pop3

10 36

[Dovecot] POP3 UIDL
by FiL ＠ Kpoxa 07 Feb '07

07 Feb '07

I have installed rc22 and tried it with my mbox-based mail - fine. Then I converted that mbox to Maildir to see if new feature (saving state without QUIT) works - first run - I get time out. Second run - I get rest of the Maildir scanned and get into mailbox. Fine. but.... # telnet enders2 110 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. +OK Dovecot ready. user filonovd +OK pass ****** +OK Logged in. uidl +OK . where is the list of pop3 uids ? When I connect to mbox I get something like .......... 84904 d8f096c72c24719bd7d13d78a3694114 84905 9074b40ab4283ec38a151587f34690d9 84906 06a40afeaca43fc76bea2231b13b1a33 84907 cdae771ec2407df89a25321f3792d9e9 84908 9f84415625d77dd3cde7d9441847318e but with Maildir I get nothing. Doesn't look like proper behavior. P.S. mail_location = maildir:~/Maildir #mail_location = mbox:~/mail:INBOX=/var/mail/%u pop3_reuse_xuidl = no pop3_uidl_format = %m FiL

6 10

[Dovecot] negative quota usage causes over-quota messages with dictionary quota backend
by Marshal Newrock 07 Feb '07

07 Feb '07

Using dovecot 1.0.rc21, with quotas being stored in mysql, I have found that if the quota usage stored is negative, then when a message is given to dovecot deliver, the account is reports as being over quota. The squirrelmail quota usage plugin says that the quota is at around 40 million percent (I should have written down the exact number), though I don't know if that's squirrelmail or dovecot coming up with that number. At a guess, I'd say there's an unsigned int being used where the result can be signed. I'm using MySQL 5, so for an easy workaround, I added a trigger that sets the quota usage to 0 if it goes less than 0. I could probably also set the field to unsigned int, but I haven't tested what mysql does if you try to change an unsigned int field such that it would be negative. -- Marshal Newrock, Ideal Solution LLC http://www.idealso.com

1 0

[Dovecot] OTP?
by Micah Cowan 07 Feb '07

07 Feb '07

Hello, I was wondering where I might find more information about using OTP as an authentication protocol with dovecot. In searching, I found a thread from 2004, but not much information about how it has progressed from then. I also saw some promising patches from mid-last year, which if I had to guess are probably the addition of support for the SASL OTP mechanism. Is this available in a release yet? (And, also: does anyone know of Linux mail clients that support the OTP SASL mechanism? I'm hoping Thunderbird might...). If not, is it possible to make it work currently with PAM (or, if that's not possible, maybe Cyrus SASL)? It would be okay with me if it can work with PAM but not prompt with the seed/series number: I can scratch off keys no prob. I tried briefly to get it to work through PAM, and in fact opieinfo told me that the series was being decremented, but auth.log gives Feb 6 15:41:46 mabruk dovecot-auth: (pam_unix) authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=x.x.x.x user=micah ssh works fine with the same PAM settings (both include common-auth, which has:) auth sufficient pam_opie.so auth sufficient pam_unix.so nullok_secure auth required pam_deny.so -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/

4 7

[Dovecot] imap crashes on deleting an e-mail with no message-id.
by Tan Shao Yi 07 Feb '07

07 Feb '07

Hi, I'm on RC21 on a Solaris 10 SPARC box. Somehow I managed to receive an e-mail with no message-id and when dovecot tries to delete the e-mail. Viewing the e-mail is not a problem though. I attached truss to the imap process and this was what I received: pollsys(0x000B7A88, 3, 0xFFBFF870, 0x00000000) = 0 pollsys(0x000B7A88, 3, 0xFFBFF870, 0x00000000) = 0 pollsys(0x000B7A88, 3, 0xFFBFF870, 0x00000000) (sleeping...) pollsys(0x000B7A88, 3, 0xFFBFF870, 0x00000000) = 1 read(0, " g 1 b q U I D S T O".., 3747) = 52 alarm(120) = 0 fcntl(6, F_SETLKW64, 0xFFBFF1D0) = 0 alarm(0) = 120 close(8) = 0 open64("/maildirs/tansy/Maildir/maildirsize", O_RDWR|O_APPEND) = 8 read(8, " 1 0 7 3 7 4 1 8 2 4 0 S".., 5120) = 2223 read(8, 0xFFBFE8DF, 2897) = 0 Incurred fault #6, FLTBOUNDS %pc = 0x00086FF8 siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000 Received signal #11, SIGSEGV [default] siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000 I believe it's due to the mail_log plugin that is logging the message-ids being deleted. When I disabled the mail_log plugin, the e-mail gets deleted correctly. Timo, do you think we can have mail_log to handle such exceptions? :) Thanking in advance. Cheers, Tan Shao Yi

2 1

[Dovecot] Default domain name
by Nils Vogels 07 Feb '07

07 Feb '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I'm trying to setup a dovecot installation and at the same time i'm also moving from system to virtual users. In order for end-users to experience as little impact as possible, I'd like to add a default domainname to the login, if the login doesn't contain a full username. For instance: * User logging in as "user(a)mydomain.com" will get the mailbox for user(a)mydomain.com. * User logging in as "user" will also get the mailbox for user(a)mydomain.com Is there some way to do this, without using the pop3/imap proxy? I've searched the wiki and sample configuration file, but was only able to find entries about authentication rewrites so far, and I don't know if this could be done with auth_username_translation ? Greetings, Nils - -- Those who desire to give up freedom in order to gain security, will not have, nor do they deserve, either one. ~Benjamin Franklin (American Statesman, Scientist, Philosopher, Printer, Writer and Inventor. 1706-1790) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) iD8DBQFFyP+3MzNX/a06Wq0RAvQ4AJwNWr7ov8Fw6JhuoOQGiQte51FW9wCfaZ7x Y3VbqigfdqSFgnlA0Aukucg= =owku -----END PGP SIGNATURE-----

2 1

[Dovecot] Indexing Performance Question (was tpop3d vs dovecot)
by Nate 06 Feb '07

06 Feb '07

Since posting the previous thread we've setup a new system (Opteron 2.0ghz, 1gb ram, Fedora 6) for testing. I am hoping somebody very familiar with the indexing portion of dovecot can shed some light on this for me. After much testing, I've come to one primary conclusion that dovecot is possibly unnecessarily scanning or reading files within the maildir directories. Take a mailbox for instance (my test one has 71570 emails in the cur/ folder so the process runs long enough to get data of what it's doing). Follow these steps: 1. First pop3 connection. With no index files whatsoever, it takes nearly a full 10 minutes at 100% io load to scan the 71570 files (748M) directory and build the index files from scratch which look like this: -rw------- 1 postfix postdrop 839K Feb 1 00:43 dovecot.index -rw------- 1 postfix postdrop 1.9M Feb 1 00:57 dovecot.index.cache -rw------- 1 postfix postdrop 560K Feb 1 00:43 dovecot.index.log -rw------- 1 postfix postdrop 3.1M Feb 1 00:43 dovecot-uidlist While it's building index i see a lot of these fly by in lsof pop3 2023 postfix 8r REG 8,3 14425 285947 /var/spool/mail/test.visp.net/natetest/cur/1128488047.V902I7d42e.s3.visp.net:2, No problem here, the disk can only go as fast as the disk can go and thats a *lot* of mail. Although, one curious thing here, it appears that dovecot is reading or at least scanning the entire contents of the files within the cur/ directory to generate an index. I assume this by watching my disk cache go from 100MB to 600MB. Is it necessary to do that or only read the top X lines of each file, is that even possible? 2. Second connection. Near instantaneous results from a login and LIST. Cannot perform an lsof fast enough to see what files it's opening. This step can be repeated with nearly the same results. *rebooted machine to clear all cache* 3. Third connection. It takes ~40 seconds to display a LIST after login. The index files are untouched; however, during the 40 seconds I'm waiting, I can catch a few of these in lsof. pop3 1971 postfix 10r REG 8,3 4196 205963 /var/spool/mail/test.visp.net/natetest/cur/1157863512.V902I1f3867.s3.visp.net:2,S This tells me even though there is no new email, it is re-scanning the cur/ directory somewhat. It doesn't take near as long as the initial index build, but certainly takes longer than it would for the system to read any or all of the listed index files above. Why would dovecot need to even enter cur/ if the index file is up to date? Is it verifying that the index file is up to date by re-reading some or all of the many files in cur/? If so, could it not get the info it needs by simply doing the equivalent of a ls, which would take considerably less time? The disk cache is only filled up an additional 30meg vs an additional 500meg from connection 1, so it's certainly not reading as much data. (also makes me wonder why the initial scan/index build could not use this lesser time consuming function if thats what it's doing). Additional information: Running strace on the initial indexing looks like this... ------------------------------------------- open("/var/spool/mail/test.visp.net/natetest/cur/1115929738.V902I67c13.test.visp.net:2,", O_RDONLY) = 8 fstat(8, {st_mode=S_IFREG|0600, st_size=4667, ...}) = 0 pread(8, "Return-Path: <mehl8nl3n8osm3r83a"..., 4096, 0) = 4096 pread(8, "zdik8dyrnffv6bbrue.itownshipno12"..., 4095, 4096) = 571 pread(8, "", 3524, 4667) = 0 close(8) = 0 open("/var/spool/mail/test.visp.net/natetest/cur/1115931742.V902I67c42.test.visp.net:2,", O_RDONLY) = 8 fstat(8, {st_mode=S_IFREG|0600, st_size=3881, ...}) = 0 pread(8, "Return-Path: <sender-5-8759012-9"..., 4096, 0) = 3881 pread(8, "", 215, 3881) = 0 close(8) = 0 ------------------------------------------- Running strace on the 3rd connection looks like this... ------------------------------------------- open("/var/spool/mail/test.visp.net/natetest/cur/1114490671.V902I6011f.test.visp.net:2,", O_RDONLY) = 10 fstat(10, {st_mode=S_IFREG|0600, st_size=5367, ...}) = 0 pread(10, "Return-Path: <qflfmq82vz8zg-u6ci"..., 4096, 0) = 4096 pread(10, "gs/rpoc_District6Spauldings.php?"..., 4095, 4096) = 1271 pread(10, "", 2824, 5367) = 0 close(10) = 0 open("/var/spool/mail/test.visp.net/natetest/cur/1114496568.V902I60bf5.test.visp.net:2,", O_RDONLY) = 10 fstat(10, {st_mode=S_IFREG|0600, st_size=2047, ...}) = 0 pread(10, "Return-Path: <removed(a)aaa-calif.c"..., 4096, 0) = 2047 pread(10, "", 2049, 2047) = 0 close(10) = 0 Thank you for the help! - Nate

8 27

[Dovecot] Problem with vpopmail auth
by Fred Moyer 06 Feb '07

06 Feb '07

Hello, I've install 1.021 and am having some problems getting vpopmail authentication to work correctly (running 0.99 in production, upgrading to 1.021). I'm using vpopmail-5.4.16. Here are the authentication debug statements in the log, my dovecot.conf changes from default, and the schema of my vpopmail database. Any ideas / suggestions? I've commented out all authentication except for vpopmail. I took a look around the source but am not that familiar with the vpopmail api. Thanks dovecot: Feb 05 22:23:31 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=10.0.0.2 rip=10.0.0.1 resp=<hidden> dovecot: Feb 05 22:23:31 Info: auth(default): vpopmail(fred(a)redhotpenguin.com,10.0.0.1): crypted password=rightpasswd dovecot: Feb 05 22:23:31 Info: auth(default): client out: OK 1 user=fred(a)redhotpenguin.com dovecot: Feb 05 22:23:31 Info: auth(default): master in: REQUEST 1 13457 1 dovecot: Feb 05 22:23:31 Info: auth(default): vpopmail(fred(a)redhotpenguin.com,10.0.0.1): vget_assign(redhotpenguin.com) failed dovecot: Feb 05 22:23:31 Info: auth(default): master out: FAIL 1 dovecot: Feb 05 22:23:31 Info: imap-login: Internal login failure: user=<fred(a)redhotpenguin.com>, method=PLAIN, rip=10.0.0.1, lip=10.0.0.2 852 # vpopmail authentication 853 # http://wiki.dovecot.org/AuthDatabase/VPopMail 854 passdb vpopmail { 855 # args = cache_key=%u dovecot 856 # [cache_key=<key>] - See cache_key in PAM for explanation. 857 # args = cache_key=%u 858 } 907 # vpopmail 908 # http://wiki.dovecot.org/AuthDatabase/VPopMail 909 userdb vpopmail { 910 } +-----------+-----------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +-----------+-----------+------+-----+---------+-------+ | pw_name | char(32) | | PRI | | | | pw_domain | char(64) | | PRI | | | | pw_passwd | char(40) | YES | | NULL | | | pw_uid | int(11) | YES | | NULL | | | pw_gid | int(11) | YES | | NULL | | | pw_gecos | char(48) | YES | | NULL | | | pw_dir | char(160) | YES | | NULL | | | pw_shell | char(20) | YES | | NULL | | +-----------+-----------+------+-----+---------+-------+

1 1

[Dovecot] Big problems after upgrade from beta8 (FC5) to rc21
by Jim Garrison 06 Feb '07

06 Feb '07

After upgrading a working system from FC5's beta8 to rc21, one vhost is failing with: > dovecot: Feb 05 09:54:30 Error: POP3(user(a)mydomain.com): > open(/var/mail/vhosts/mydomain.com/david/user, O_CREAT) failed: Not a > directory > dovecot: Feb 05 09:54:30 Error: POP3(user(a)mydomain.com): > mkdir_parents(/var/mail/vhosts/mydomain.com/user/.imap/INBOX) failed: > Not a directory > dovecot: Feb 05 09:54:30 Error: POP3(user(a)mydomain.com): Couldn't open > INBOX: Internal error occurred. Refer to server log for more > information. [2007-02-05 09:54:30] > dovecot: Feb 05 09:54:30 Info: POP3(user(a)mydomain.com): No INBOX for > user top=0/0, retr=0/0, del=0/0, size=0 > dovecot: Feb 05 09:54:30 Info: pop3-login: Login: > user=<user(a)mydomain.com>, method=PLAIN, rip=::ffff:4.242.120.235, > lip=::ffff:216.75.55.45, TLS Here's the entire dovecot.conf: protocols = pop3s ssl_cert_file = /etc/pki/dovecot/certs/popcert.pem ssl_key_file = /etc/pki/dovecot/private/popkey.pem ssl_ca_file = /etc/pki/tls/certs/ca-bundle.crt ssl_parameters_regenerate = 48 disable_plaintext_auth = yes log_path = /var/log/dovecot.log mail_extra_groups = mail mbox_read_locks = fcntl mbox_write_locks = fcntl dotlock protocol imap { } protocol pop3 { } auth_verbose = no auth_debug = no auth_debug_passwords = no auth default { mechanisms = plain passdb passwd-file { args = /etc/dovecot/%d.passwd } passdb pam { } userdb passwd { } userdb static { args = uid=502 gid=502 home=/var/mail/vhosts/%d mail=mbox:/var/mail/vhosts/%d/%n } user = root } plugin { } Did something changed between beta8 and rc21 in the index format and/or mbox location? If so, how do I recover so users can retrieve mail again? Thx.

2 4

[Dovecot] LDAP auth_bind=yes in rc21 = goodness
by Adrian Close 06 Feb '07

06 Feb '07

Hi all, I finally got a chance to try out the fix for the LDAP auth_bind=yes issues in production (using rc21). It seems to be working just fine even after 24 hours of severe abuse. Incidentally, I had switched to bsdauth+login_ldap (on OpenBSD) which was often OK, but occasionally I would see Postfix smtpd throttled with SASL errors due to "connection refused" on the Dovecot authentication socket. This may just have been due to increased LDAP server load (Dovecot's internal LDAP generates much less). Thanks Timo! (And thanks Brad for updating the port) Adrian.

2 1

[Dovecot] minor kerberized dovecot build issue
by Dan Price 05 Feb '07

05 Feb '07

Hi all, again, I'm not knowledgeable about Kerberos, but we have a few users who use it to make sure that it works well on Solaris... so, they would like a Kerberized IMAPd. I tried compiling dovecot --with-gssapi on Solaris Nevada (the current development release), and the configure script choked for a couple of reasons. First, script uses 'grep -qv' in the case that you specify --with-gssapi to run some test. Unfortunately, Solaris doesn't have 'grep -q'. There's a note in GNU grep's manpage about this problem and a note that portable scripts should just redirect to /dev/null. Once I fixed this problem, I got: configure: WARNING: gssapi/gssapi.h: present but cannot be compiled configure: WARNING: gssapi/gssapi.h: check for missing prerequisite headers? configure: WARNING: gssapi/gssapi.h: see the Autoconf documentation configure: WARNING: gssapi/gssapi.h: section "Present But Cannot Be +Compiled" configure: WARNING: gssapi/gssapi.h: proceeding with the preprocessor's result configure: WARNING: gssapi/gssapi.h: in the future, the compiler will take +precedence configure: WARNING: ## ---------------------------------- ## configure: WARNING: ## Report this to dovecot(a)dovecot.org ## configure: WARNING: ## ---------------------------------- ## For whatever reason, on Solaris /usr/bin/krb5-config does not like the syntax 'krb5-config --cflags gssapi' (ditto with --libs). I found that removing the 'gssapi' part from the configure script fixed the problem, but I imagine this must break some other OS. If need be, I can follow up with the Kerberos team about this. Once I made these minor changes, I also had to add -lgss to the src/auth makefile's compile line. After that, I had no problem getting this to compile, although we have not yet tested it. -dp -- Daniel Price - Solaris Kernel Engineering - dp(a)eng.sun.com - blogs.sun.com/dp

2 3

[Dovecot] Nitpicking: rc21 startup banner says rc19
by Jim Garrison 05 Feb '07

05 Feb '07

> [jhg@helios RPMS]$ rpm -q dovecot > dovecot-1.0-1_42.rc21.fc5.at but: > dovecot: Feb 05 10:49:21 Info: Dovecot v1.0.rc19 starting up

4 5

[Dovecot] Problems enabling quota on MacOS X
by Lars Skovgaard 05 Feb '07

05 Feb '07

Hi, I'm trying to activate quotas for my users, preferably maildir++ quotas as all users are using maildir. I have compiled dovecot with quota-support, but when I try to enable quotas in the config, dovecot refuses to start up with a (to me, at least) strange message: Fopendir(/usr/local/lib/dovecot/imap) failed: No such file or directory Error: imap dump-capability process returned 89 In the logs I get the following: dovecot: read (imap dump-capability process) failed: Interrupted system call The directory "/usr/local/lib/dovecot/imap" is not missing, which would be the obvious explanation... Dovecot-version is 1.0rc21 (which by the way is running ***great*** without quotas). Thanks, /Lars

2 2

[Dovecot] Compile without GSSAPI disables SSL?
by Troy Engel 05 Feb '07

05 Feb '07

Perchance this is something unique to Red Hat -- I'm compiling/running 1.0rc?? on a CentOS 4 machine (i386), building RPMs and trimming down things I don't need (SQL e.g.). If I compile with the flag --with-gssapi, the resulting dovecot-auth binary links to libcrypto and libssl, the standard OpenSSL libs. Life is happy even though I don't need gssapi/krb5 support. If I remove --with-gssapi (but leave --with-ssl=openssl as before), the resulting dovecot-auth binary is no longer linked to the OpenSSL libraries (so I'm assuming no TLS/SSL support, but can't run the binary to test - I have SSL betatest users). So the question is, is this a ./configure problem in Dovecot, or some strangeness with Red Hat that you must link with gssapi/krb5 to get OpenSSL? Anyone care to hazard a guess? -te == details == The full configure line generated by the build is: + ./configure --build=i686-redhat-linux-gnu --host=i686-redhat-linux-gnu --target=i386-redhat-linux-gnu --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info 'INSTALL_DATA=install -c -p -m644' --with-doc --with-ssl=openssl --with-ssldir=/etc/pki/dovecot --with-ldap --with-gssapi --with-linux-quota=2 With gssapi: Install prefix ...................... : /usr File offsets ........................ : 64bit I/O loop method ..................... : poll File change notification method ..... : dnotify Building with SSL support ........... : yes (OpenSSL) Building with IPv6 support .......... : yes Building with pop3 server ........... : yes Building with mail delivery agent .. : yes Building with GSSAPI support ........ : yes Building with user database modules . : static prefetch passwd passwd-file checkpassword (modules) Building with password lookup modules : passwd passwd-file shadow pam checkpassword (modules) Building with SQL drivers ............: Without gssapi: Install prefix ...................... : /usr File offsets ........................ : 64bit I/O loop method ..................... : poll File change notification method ..... : dnotify Building with SSL support ........... : yes (OpenSSL) Building with IPv6 support .......... : yes Building with pop3 server ........... : yes Building with mail delivery agent .. : yes Building with GSSAPI support ........ : no Building with user database modules . : static prefetch passwd passwd-file checkpassword (modules) Building with password lookup modules : passwd passwd-file shadow pam checkpassword (modules) Building with SQL drivers ............: -- Troy Engel | Systems Engineer Fluid, Inc | http://www.fluid.com

2 2

[Dovecot] URGENT: specify mailboc location
by T. Horsnell 05 Feb '07

05 Feb '07

Is there a way I can tell dovecot to only use the .subscriptions file, if it exists, as the source of mailfolder paths, rather than have it look at every file in a user's directory to see if it's a mail folder? I'm on RHEL4, still on dovecot dovecot-0.99.11 Thanks, Terry.

2 1

[Dovecot] pop3 not working properly in 1.0.r19
by Charlie Root 05 Feb '07

05 Feb '07

Hi, I often see this message: Feb 1 14:42:44 vlk dovecot: POP3(obec(a)nizkov.cz): Mailbox init failed top=0/0, retr=0/0, del=0/0, size=0 Feb 1 14:42:44 vlk dovecot: POP3(obec(a)nizkov.cz): mbox sync: UID inserted in the middle of mailbox /var/mail/obec(a)nizkov.cz (68386 > 68346, seq=2, idx_msgs=3) this is on FreeBSD@i386 runnin 1.0.r19 (but I have seen this with all versions of 1.0.x), filesystem in use is UFS (ie. local filesystem). THe mailing client in question seems to be outlook express. I can provide the mbox in question. locking method is #lock_method = flock and the dovecot was compiled with kqueue thnx roman

2 1

[Dovecot] a namespace "mbox" without an INBOX
by David Bonnafous 05 Feb '07

05 Feb '07

hi, (dovecot 1.0r15) I try to setup up two namespaces: 1- the first one (and default one) a maildir namespace 2- the second one a mbox namespace I want only one "INBOX", in the maildir namespace, no INBOX in the mbox namespace. I get what I want with this configuration: ---------------------------------------- mail_location = maildir:~/Maildir namespace private { inbox = yes } namespace private { separator = . prefix = mbox. location = mbox:~/mbox:INBOX= inbox = no hidden = no } ---------------------------------------- My question is: is it a normal way to do what I want ? I mean, the line location = mbox:~/mbox:INBOX= looks odd. I try with just the line inbox=no (without INBOX=) but dovecot set a default INBOX that disturbs some mail client. yours, -- David Bonnafous Institut de Mathématiques Université Paul Sabatier Toulouse - France

2 1