- dovecot - dovecot.org

[Dovecot] gssapi auth issue...
by Dan Price 28 Mar '07

28 Mar '07

Hi all-- been away from the list for a few weeks so forgive me if this problem has been reported-- with the help of some of our Kerberos engineers, we tracked down why we can't authenticate our Solaris kerberos clients to Dovecot. Here's the deal: Our IT organization issued us kerberos tickets of the form imap(a)foobar.sfbay.sun.com Which I presume is their standard-- and probably not negotiable. However, the hostname of the machine is: "foobar", not foobar.sfbay.sun.com (as reported by gethostname(3c)). So when dovecot does this: mech-gssapi.c: principal_name = t_str_new(128); str_append(principal_name, service_name); str_append_c(principal_name, '@'); ---> str_append(principal_name, my_hostname); We wind up asking kerberos to look for a ticket for imap@foobar, instead of imap(a)foobar.sfbay.sun.com. Obviously we can patch the source, but I was wondering if we could have a gssapi_hostname setting in the config file? Or perhaps we could have a knob letting us globally override my_hostname? Although I don't know what side effects that could have. We have some new cores I also need to report-- I'll get on that. Thanks in advance, -dp -- Daniel Price - Solaris Kernel Engineering - dp(a)eng.sun.com - blogs.sun.com/dp

3 2

[Dovecot] Custom Mail Directory for some users
by Patrick Kranz 27 Mar '07

27 Mar '07

Hi list, I'm new on this mailing list and I'm kind of stucked at the moment. I managed to get Postfix and Dovecot working together with Amavis, OpenLDAP und SASL on Ubuntu Linux Release "Dapper Drake". The Dovecot version shipped with Dapper is 1.0-beta3 (at least, that's what the package database tells me), I also tried this with a Debian Backport of version 1.0-rc15. And here is my problem: A customer of mine needs usernames different from the mail address for his third party software to work. In other words, I need the ability to login with the username foo to get access to the mailbox bar(a)example.com. So I tried to override the mail_location property for this user with a separate mailDirectory attribute in my LDAP tree. Speaking in dovecot.conf words: mail_location = maildir:/var/spool/dovecot/mail/%d/%n auth default { machanisms = plain passdb ldap { args = /etc/dovecot/dovecot-ldap.com } userdb ldap { args = /etc/dovecot/dovecot-ldap.com } userdb static { args = uid=vmail gid=vmail user = dovecot } and dovecot-ldap.conf: hosts = localhost dn = cn=admin,dc=ekits,dc=de dnpass = secret auth_bind = yes ldap_version = 3 base = ou=mailsystem,dc=ekits,dc=de scope = subtree user_attrs = mailDirectory=mail user_filter = (&(objectClass=ekitsMailAccount)(uid=%u)) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=ekitsMailAccount)(uid=%u)) user_global_uid = vmail user_global_gid = vmail a typical ldap entry looks something like this: dn: cn=Patrick Kranz,o=EK IT-Solutions,ou=mailsystem,dc=ekits,dc=de ekitsMailDestination: patrick(a)ekits.de objectClass: ekitsMailAccount objectClass: top cn: Patrick Kranz structuralObjectClass: ekitsMailAccount entryUUID: b4ebb9e8-6d8d-102b-9dc9-9edb870845a4 creatorsName: cn=admin,dc=ekits,dc=de createTimestamp: 20070323132526Z userPassword:: YVBhc3M= mailDirectory: maildir:/var/spool/dovecot/mail/ekits.de/blubb uid: patrick As far as I can interpret the log of slapd, dovecot doesn't even ask for the attribute "mailDirectory". I also tried this with userdb prefetch. With this it did actually ask for the attribute but it still had no effect. With this configuration dovecot creates the directory /var/spool/spool/dovecot/mail/patrick if I login with the uid patrick but I wanted access to /var/spool/dovecot/mail/ekits.de/blubb If anybody has any clue what I did wrong or if I have a conceptional misunderstanding, I would appreciate every help. Thanks in advance. Greetings, Patrick

3 4

[Dovecot] recent master-settings.c and main.c changes breaks dovecot on my system
by Daniel 27 Mar '07

27 Mar '07

Hi! Compiled the latest cvs today, and noticed the changes in src/master/main.c and master-settings.c. With the versions 1.80.2.19 and 1.125.2.28 (respectively) I can not start dovecot, because it says: Fatal: dup2(stdin) failed: Bad file descriptor Error: imap dump-capability process returned 89 After reverting the patch: http://www.dovecot.org/list/dovecot-cvs/2007-March/008371.html everything is back to normal. My system is OpenBSD 4.0 and dovecot is recent cvs. Daniel

2 1

[Dovecot] Coredump in dovecot-auth on gss auth
by Dan Price 27 Mar '07

27 Mar '07

I've enabled the GSS code in dovecot, but our Kerberos nerds are complaining that it doesn't work :) I probably have the thing totally misconfigured (so don't worry about that part for now), but I do have a crash: Info: imap-login: Disconnected: rip=XXX.YYY.229.8, lip= XXX.YYY.17.59, TLS handshake Error: auth(default): gssapi(?,XXX.YYY.229.8): While acquiring service credentials: No credentials were supplied, or the credentials were unavailable or inaccessible Error: auth(default): gssapi(?,XXX.YYY.229.8): While acquiring service credentials: No principal in keytab matches desired name Info: imap-login: Disconnected: method=GSSAPI, rip=129.146.229.8, lip=XXX.YYY.17.59 Error: child 188558 (auth) killed with signal 11 Info: imap-login: Disconnected: method=PLAIN, rip=129.146.229.8, lip=XXX.YYY.17.59 The dovecot auth process SIGSEGV's and dies at login time (I think). Here's the backtrace: (gdb) bt full #0 0xfef25e1a in gss_release_name () from /usr/lib/libgss.so.1 No symbol table info available. #1 0x08064ccf in mech_gssapi_auth_free (request=0xfef3c000) at mech-gssapi.c:394 minor_status = 0 #2 0x08060551 in auth_request_handler_flush_failures () at auth-request-handler.c:493 auth_request = (struct auth_request **) 0x8047b5c i = 1 size = 1 __PRETTY_FUNCTION__ = "auth_request_handler_flush_failures" #3 0x0806f54a in io_loop_handle_timeouts (ioloop=0x8096f78) at ioloop.c:276 t = (struct timeout *) 0x8098048 called_timeouts = (struct timeout *) 0x8098048 tv = {tv_sec = 134852200, tv_usec = 0} t_id = 2 #4 0x0806fb42 in io_loop_handler_run (ioloop=0x8096f78) at ioloop-poll.c:159 ctx = (struct ioloop_handler_context *) 0x8096fb0 pollfd = (struct pollfd *) 0x8096f78 tv = {tv_sec = 0, tv_usec = 0} io = (struct io *) 0x8047f99 t_id = 134836088 msecs = 134894204 ret = 0 call = true #5 0x0806f65d in io_loop_run (ioloop=0x8096f78) at ioloop.c:311 No locals. #6 0x08062bb2 in main (argc=1, argv=0x809ae68) at main.c:321 foreground = false Thanks, -dp -- Daniel Price - Solaris Kernel Engineering - dp(a)eng.sun.com - blogs.sun.com/dp

3 2

[Dovecot] Sync of read message status between squirrelmail and outlook express
by Mohd Ikhwan Abdullah 27 Mar '07

27 Mar '07

Hi, We have a Linux email server running CentOS 4.4. I have a scenario here. The users here use a mixture of outlook express and squirrel mail as their email client. The users download their mail into outlook express via pop3 but the have configured outlook express to leave a copy on the server for 7 days. 1. After downloading the mail into outlook express the users would read the mail and the mail would be set as 'READ' in outlook express. 2. Is there a way to configure dovecot so that the 'READ' status in outlook express is reflected on the message still stored on the server as well. Cause when they access via squirrel mail the message is still mark as 'UNREAD'. Any suggestions is very much appreciated. Thanks in advance.

3 3

[Dovecot] compiling dovecot on aix gcc 3.3.2
by funkypunky drunky 27 Mar '07

27 Mar '07

I try to compile the dovecot with gcc version 3.3.2 on aix. It seemed it was okay. It was working but when i try to use quota dynamic modules i get error. Edlopen(/usr/local/lib/dovecot/imap/lib10_quota_plugin.so) failed: Could not load module /usr/local/lib/dovecot/imap/lib10_quota_plugin.so. System error: No such file or directory Error: imap dump-capability process returned 89 When i check the /usr/local/lib/dovecot/imap/lib10_quota_plugin.so i see that it is a link which is pointing /usr/local/lib/dovecot/lib10_quota_plugin.so . But there is no lib10_quota_plugin.so . I try compiling it on linux debian. I see that lib10_quota_plugin.so in it is proper place. I dont know what to do. Did i something wrong? I need help Best regards

4 9

[Dovecot] LDA bouncing mails after upgrade
by Milan Holzäpfel 27 Mar '07

27 Mar '07

Hello, on my system, I have a copy of /usr/libexec/dovecot/deliver located in /usr/libexec/dovecot/postfix-deliver/deliver (only accessible to postfix and with SUID root permissions). If I happen to forget to update this copy after an upgrade of dovecot, the deliver LDA bounces mails: | Mar 22 20:29:20 host.example.org deliver(user(a)example.org): Module is for different version 1.0.rc27: /usr/lib/dovecot/lda/lib10_quota_plugin.so | Mar 22 20:29:20 host.example.org postfix/pipe[17344]: <ID>: to=<user(a)example.org>, relay=dovecot, delay=1.9, delays=1.5/0/0/0.35, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/postfix-deliver/deliver") Should I just set version_ignore=yes and remember myself to upgrade it, or could deliver return a code signaling "temporary failure", or should I rather make postfix interpret 89 as temporary failure? (don't know by heart whether that's possible). Regards, Milan -- Milan Holzaepfel <mail(a)mjh(d)name> <URL:http://mjh.name/> pub 4096R/C790FC23 EB8E 5E81 81E3 53A9 9B74 B895 5179 54C0 C790 FC23

4 3

[Dovecot] Odd error message
by Steven F Siirila 27 Mar '07

27 Mar '07

We are running Dovecot 1.0-rc27 and have run across what seems to be a fatal error (SIGSEGV) in the past few days (4 times total in past 6 days). It appears to have been 5 separate users, 5 separate remote IP addresses. Two of these have this format: Mar 26 15:13:10 myhostname dovecot: imap-login: Authenticate PLAIN failed: Don't send unrequested data: user=<rmtuser>, method=PLAIN, rip=10.9.9.9, lip=10.1.1.1, TLS The other three have this format: Mar 26 09:41:45 myhostname dovecot: imap-login: Authenticate PLAIN failed: Don't send unrequested data: method=PLAIN, rip=10.9.9.9, lip=10.1.1.1, TLS Here's the first one a bit more expanded, showing the SIGSEGV (signal 11): Mar 26 15:13:10 myhostname dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=10.1.1.1 rip=10.9.9.9 Mar 26 15:13:10 myhostname dovecot: auth(default): client out: CONT 1 Mar 26 15:13:10 myhostname dovecot: auth(default): client in: CONT<hidden> Mar 26 15:13:10 myhostname dovecot: auth(default): pam(rmtuser,10.9.9.9): lookup service=IMAP Mar 26 15:13:10 myhostname dovecot: auth(default): client out: OK 1 user=rmtuser Mar 26 15:13:10 myhostname dovecot: auth(default): master in: REQUEST 675645 3333 1 Mar 26 15:13:10 myhostname dovecot: auth(default): passwd(rmtuser,10.9.9.9): lookup Mar 26 15:13:10 myhostname dovecot: auth(default): master out: USER 675645 rmtuser system_user=rmtuser uid=99999 gid=9999 home=/home/r/rmtuser Mar 26 15:13:10 myhostname dovecot: imap-login: Authenticate PLAIN failed: Don't send unrequested data: user=<rmtuser>, method=PLAIN, rip=10.9.9.9, lip=10.1.1.1, TLS Mar 26 15:13:10 myhostname dovecot: imap-login: Disconnected: user=<rmtuser>, method=PLAIN, rip=10.9.9.9, lip=10.1.1.1, TLS Mar 26 15:13:10 myhostname dovecot: child 3333 (login) killed with signal 11 What can I do to further diagnose this problem? -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

2 1

[Dovecot] imaps listen only at localhost
by Dirk Schleicher 26 Mar '07

26 Mar '07

Hello list, I try to get dovecot listen only at localhost. I try listen localhost:993 and it did not work. The installation I made from http://holl.co.at/howto-email/ How it is possible that dovecot with imaps only work on localhost? Thanks for the help. Best regards Dirk

2 2

[Dovecot] netapp/maildir/dovecot performance
by bofh list 26 Mar '07

26 Mar '07

We are seeing some poor performance recently that is focused around users with large mailboxes (100,000 message /INBOX, 80,000 message subfolders, etc). The performance problem manifests as very high system% utilization - basically iowait for NFS. There are two imap servers with plenty of horsepower/memory/etc. They are connected to a 3050c cluster via gig-e. Here are the mount options: rw,tcp,nfsvers=3,rsize=8192,wsize=8192,nosuid,nodev,soft,intr,noac,actimeo=0 I need to get this system% utilization brought down because it is starting to slowdown imap performance for other users (it goes up to 95% on a regular basis, with users that have folders with many messages). My thought is to try removing the noac option and bump up the actimeo value from 0 to 30. Unfortunately I don't have access to use a SLB to direct traffic to individual servers. My understanding is that the worst that can happen is index corruption (which will result in rebuilding them when it happens). Any thoughts? I'm running RC24.

3 5

[Dovecot] authentication process fails when starting 2nd dovecot
by Cipriano Groenendal - TransIP 26 Mar '07

26 Mar '07

Hello, With dovecot running already, (accidently) starting another dovecot seems to break the authentication process of the first dovecot. Login will be impossible untill dovecot is restarted. # dovecot Fatal: listen(143) failed: Address already in use ## Wait several seconds. # telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. 0: logout * OK Waiting for authentication process to respond.. 0: logout * OK Waiting for authentication process to respond.. -- Also, in the logfiles the following entries will appear: -- Mar 26 12:11:21 virt6 dovecot: pop3-login: No authentication sockets found Mar 26 12:11:21 virt6 dovecot: child 38054 (login) returned error 89 Mar 26 12:11:23 virt6 dovecot: imap-login: No authentication sockets found Mar 26 12:11:23 virt6 dovecot: child 38058 (login) returned error 89 -- Running dovecot-1.0.r22 on FreeBSD 6.2-STABLE, amd64 architecture. Standaard FreeBSD UFS fs. -- dovecot config -- # /usr/local/etc/dovecot.conf protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login verbose_proctitle: yes first_valid_gid: 0 mail_extra_groups: mail mail_location: mbox:~/mail:INBOX=/var/mail/%u mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private separator: / prefix: #mbox/ location: mbox:~/mail:INBOX=/var/mail/%u inbox: yes hidden: yes namespace: type: private separator: / location: maildir:~/Maildir auth default: passdb: driver: pam userdb: driver: passwd ------ Met vriendelijke groet, Cipriano Groenendal -- Transip BV | http://www.transip.nl/ Hoogwaardige Innovatie | Aangename Zekerheid

2 1

[Dovecot] Unwanted INBOX. prefix issues
by Kevin Bowling 26 Mar '07

26 Mar '07

I have a strange problem. I installed Dovecot and had my trash folder and such in the root of my maildir, and everything was working great. I then installed SquirrelMail which created folders in with the INBOX. prefix. I manually removed these from the maildir, but the INBOX.Trash is still shown in the folder listing of Thunderbird. This leads to some strange behavior, such as the delete button not working. Is there a way I can reset the folder list, and take the INBOX.* items out? Any help would be appreciated. Regards, Kevin

2 4

[Dovecot] Rpm builders: Dovecot spec file
by Egbert Jan 26 Mar '07

26 Mar '07

Maybe best asked to Axel... I'm re-building my server from scratch (the old one was MDK 10.1 -> Mandriva 2006.0 with Postfix/Courier) and I want to install the latest versions postfix/mysql/postfixadmin/dovecot/squirrelmail. I've been building Dovecot (and postfix) from tarballs/srpm in the past so I know more or less how it all fits together. But I wonder if 'old' patches still need to be included/applied in the building of the latest rc's. I still see references to those patches in the spec file. Unfortunately the latest 'official' rpm for Mandriva (I'm running 2007.0) is rc7 and I never succeeded getting in contact with the Mandriva maintainer to ask the same question. In the Axel's AT rpm I still see some patches included but others than in the Mandriva rc7 spec file. Are those patches not already applied to the latest sources by Timo? Tnx Egbert Jan NL

2 2

[Dovecot] assertion failure with nopassword
by Johannes Berg 26 Mar '07

26 Mar '07

Hm, so my mailing list archive is up, but when I add nopassword to the list of settings in my passdb passwd-file I get: file auth-request.c: line 924 (auth_request_set_field): assertion failed: (request->passdb_password == NULL) Raw backtrace: dovecot-auth [0x806be11] -> dovecot-auth [0x806bd8c] -> dovecot-auth(auth_request_set_field+0x277) [0x80547d7] -> dovecot-auth [0x8060418] -> dovecot-auth [0x8060509] -> dovecot-auth(auth_request_verify_plain+0xb3) [0x80559b3] -> dovecot-auth [0x8055ac2] -> dovecot-auth(auth_request_verify_plain_callback+0x30) [0x8055b50] -> dovecot-auth [0x8060dbe] -> dovecot-auth(io_loop_handler_run+0x152) [0x806f1c2] -> dovecot-auth(io_loop_run+0x28) [0x806e508] -> dovecot-auth(main+0x2fb) [0x805aaab] -> /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7a3fea8] -> dovecot-auth [0x8050ff1] This is with rc27. I don't seem to be able to get the passdb_password to NULL with passwd-file. johannes

2 2

[Dovecot] Bug tracking system
by Timo Sirainen 26 Mar '07

26 Mar '07

There are three reasons why I haven't really bothered setting up a bug tracking system for Dovecot: 1) They're all kind of annoying to use. 2) They all require a lot of stuff like PHP, SQL server, etc. which I don't really want to put into dovecot.org. 3) Probably most importantly: If people start reporing bugs in there, I'm pretty much the only person who will ever read them and reply to them. Currently when people report bugs in here, it's quite useful to have other people read them too. They may already know the bug and say they've reported it, they may have an idea what's causing it, they may know a workaround, etc. All in all, moving things to BTS would most likely cause my life to be harder and it might be more difficult to get some bugs fixed. A couple of days ago I started thinking about this and then I figured out a way to solve all of this nicely with a new and great Dovecot based bug tracking system. :) Just so I won't forget it, here's the plan: Dovecot BTS ----------- The preferred way to report bugs is to send them to dovecot-bugs(a)dovecot.org. The only thing it does is prefix the subject line with [BUG #nnn] and forward it to dovecot(a)dovecot.org. Now everyone can reply to it just as it was a normal mailing list mail. As long the subject contains the "[BUG #nnn]" prefix, it's part of the bug. Existing mailing list threads can also be turned into bugs by replying to the thread's root message with To: dovecot-bugs(a)dovecot.org. This again causes the new reply to contain [BUG #nnn] prefix. Then comes the web part. There's no SQL database or anything, everything is stored in a mailbox in the IMAP server. The mailbox contains the whole dovecot(a)dovecot.org archive. Bug metadata such as priority, status, etc. is stored using IMAP ANNOTATE extension, which allows setting key=value pairs to messages. Unfortunately Dovecot doesn't yet support that extension. Bugs' root messages contain the annotations for the whole bug thread. So to get a list of all bugs, the BTS issues an IMAP SEARCH ANNOTATE command to list all messages with some specific "bug=yes" type of annotation. For those messages then it can fetch the subject and whatever else metadata it wants. Newly created bugs don't have annotations though. To fix that, the BTS also uses ANNOTATEMORE (or is it METADATA nowadays?) extension to keep "last seen message in BTS" state in the mailbox's annotations. It then issues a SEARCH SUBJECT "[bug #" command for the new messages and does THREAD command for them to see if they're the bug root, or if they were replies to another message which should be treated as the bug root. When viewing a bug, the bug metadata comes from the annotations. Annotation history could also be kept, possibly as messages in another history mailbox. The messages for a bug can be viewed by issuing a THREAD (REFERENCES) command and showing all the mails that exist under the bug root. So, any volunteers to implement the web part, if I implement the ANNOTATE extension? :) It would actually even be possible to implement multiple frontends. All I need to do is give you access (read-only, or read-write for some) to the bug tracking mailbox, and you can use whatever frontend you wish, even a non-web one!

17 39

[Dovecot] Dovecot LDA issues
by Steven F Siirila 26 Mar '07

26 Mar '07

We've seen two issues come up with Dovecot LDA, both of which have caused us problems: 1) If the user's home directory does not exist, or is not owned by them, deliver fails and causes the mail message to bounce back to the originator. In our environment this happens when our user is moved to another server (where we move their files, but for up to 24 hours afterwards, continue to re-mail their /var/mail INBOX). This no longer works because the user has no home directory, causing deliver to fail with "Permission denied" when attempting to create their home directory for the purposes of creating INBOX index files. 2) If the user is over quota (in their home directory), deliver fails with a temporary error, causing requeues until the user is back under quota (which in our environment could be a long time, days). Since we've never had quotas on the user's INBOX (in /var/mail), this is a problem for us. I'd propose for both of these cases that deliver issue WARNING messages to its logs, and simply not create index files for the INBOX. If the INBOX index files already exist, and the user is over quota in /home, neither deliver nor any other Dovecot process should attempt to update them, and instead issue WARNING messages. This allows the e-mail to be delivered instead of requeued, or worse yet, rejected. Index files are supposed to make things perform better, not worse, in ALL cases. :) -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

2 3

[Dovecot] deliver: -m, sieve and -n
by Jim Horner 26 Mar '07

26 Mar '07

Hi, I took a stab at editing the wiki ... the changes disappeared? I guess I was overruled. The wiki (http://wiki.dovecot.org/LDA) states -m <mailbox>: Destination mailbox (default is INBOX). If the mailbox doesn't exist, it's created (unless -n is used). If message couldn't be saved to the mailbox for any reason, it's delivered to INBOX instead. I tried to add a little note that the sieve plugin takes precedence. For example if at the end of the a .dovecot.sieve there is a line like: fileinto "CompanyFolders.general"; then the -m <mailbox> is ignored. I am not sure about the use of 'stop'. -n: If the destination mailbox doesn't exist, don't create it. This affects both -m parameter and fileinfo action in Sieve scripts. The fallback is to deliver mail to INBOX. (typo: fileinto not fileinfo) My testing shows that if the mailbox does not exist then the mail is rejected like so: === Your message was automatically rejected by Dovecot Mail Delivery Agent. The following reason was given: Mailbox doesn't exist: mail-lists.debian === I like the wiki's solution better. Jim

2 3

[Dovecot] dovecot authentication & exim in rc27
by Richard P. Welty 26 Mar '07

26 Mar '07

[introduction: new to the list, used dovecot w/exim as MTA in simple ways for 2 years, blah blah blah] i'm trying to get exim to use dovecot auth with a copy of rc27 and am missing something that's probably quite simple. specifically, how does one configure the authenticators in dovecot.conf for rc27? the auth section of the default config file installed in rc27 doesn't entirely look like what i'm seeing in other documentation; instead of auth default { } i'm seeing auth = default followed by lots of standard flags prefixed by auth_, but i don't see how to set up the socket. i have the following; dovecot starts and doesn't complain but it doesn't create the socket either: auth_socket listen { client { path = /var/run/dovecot/auth-client mode = 0660 user = exim group = exim } } any suggestions? thanks, richard

2 1

[Dovecot] anonymous mailing list archive configuration?
by Johannes Berg 25 Mar '07

25 Mar '07

Hi, I'd like to run a mailing list archive via IMAP like for this list but my mails are in maildir and not mbox. It's easy to add a new user that has access to the maildir that mails get stored in, and I can simply link that up to that user's inbox. It's also easy to prevent putting mail into that folder. However, one thing I'm not clear on is how to prevent that user from creating new folders. I don't think I can do that with permissions to the ~/Maildir since that user needs to be able to create files there for indizes etc. Is that possible? Should/can I write a plugin that prevents things? johannes

2 3

[Dovecot] Design docs in wiki
by Timo Sirainen 25 Mar '07

25 Mar '07

If you've ever wondered how Dovecot works internally, I've now written something about it to the wiki. It's probably a bit confusing and there are a lot of things missing, but it's better than nothing. :) http://wiki.dovecot.org/Design

2 1

[Dovecot] 1.0.rc28 / v1.0 plans
by Timo Sirainen 24 Mar '07

24 Mar '07

I'll probably release 1.0.rc28 in a few days. Would be nice to get some testing for it first. http://dovecot.org/nightly/dovecot-latest.tar.gz contains pretty much what it's supposed to be. I've now replied to all the mails I was planning on replying, excluding the few patches that are v1.1 material. If you think I forgot to reply to some mail, please resend it. I think the documentation in Wiki is finally beginning to look pretty good. All the important things are done. The only things in my "would be nice TODO" list are: - Add a new page about index files and their configuration. I'll probably do this before rc28. - PasswordSchemes and Authentication/Mechanisms are pretty heavy reading. Could be made easier to understand. Possibly also create some mechanism-specific pages describing how to configure them in Dovecot and in clients. - Design documents would also be nice, but not very useful for non-programmers and pretty big job to write them I'm planning on adding the Wiki pages to doc/wiki/ in the tarball and changing: - http://wiki.dovecot.org/* links to doc/wiki/*.txt in dovecot-example.conf - doc/variables.txt could be removed and links to it updated to doc/wiki/Variables.txt - doc/auth-protocol.txt is also already in wiki. Maybe create doc/design/ and put the AuthProtocol.txt there and other design wiki pages there as well. As for v1.0, it looks like there aren't many bug reports anymore about rc27. If there are as few for rc28, I'll release v1.0 in about a month. So unless something special happens, I'll fix only the simplest bugs after rc28 and leave the rest to v1.1/v1.0.1. Hmm. Looks like 13.4. is Friday. Perhaps that's a good day for a release. :) Looks like I ended up adding a few more new features to rc28: * deliver + userdb static: Verify the user's existence from passdb, unless allow_all_users=yes * dovecot --exec-mail: Log to configured log files instead of stderr + When copying/syncing a lot of mails, send "* OK Hang in there" replies to client every 15 seconds so it doesn't just timeout the connection. + Added idxview and logview utilities to examine Dovecot's index files + passdb passwd and shadow support blocking=yes setting now also + mbox: If mbox file changes unexpectedly while we're writing to it, log an error. + deliver: Ignore -m "" parameter to make calling it easier. + deliver: Added new -n parameter to disable autocreating mailboxes. It affects both -m parameter and Sieve plugin's fileinto action - auth cache: If unknown user was found from cache, we didn't properly return "unknown user" status, which could have caused problems in deliver. - Index view syncing fixes - rc27 didn't compile with some non-GCC compilers - vpopmail support didn't compile in rc27 - NFS check with chrooting broke home direcotry for the first login - deliver: If user lookup returned "unknown user", it logged "BUG: Unexpected input" - convert plugin didn't convert INBOX

5 11

[Dovecot] idxview: Fatal: file hdr read() 41984 != 1170103198
by Troy Engel 24 Mar '07

24 Mar '07

Playing with the new idxview I got this error running against my INBOX dovecot.index.cache file. What exactly does it mean? Full output: # /usr/libexec/dovecot/idxview dovecot.index.cache -- INDEX: dovecot.index.cache version = 1.8 base header size = 0 header size = 1170103198 record size = 1170103283 compat flags = 7 index id = 0 flags = 26512 uid validity = 0 next uid = 2460778624 messages count = 0 recent messages count = 632 seen messages count = 1 deleted messages count = 1140057508 first recent uid lowwater = 4294966816 first unseen uid lowwater = 3 first deleted uid lowwater = 1836 log file seq = 0 log file int offset = 2 log file ext offset = 1140057513 sync size = 266287972361 sync stamp = 21 day stamp = 0 day first uid[0] = 1378709065 day first uid[1] = 2037149797 day first uid[2] = 980374573 day first uid[3] = 826620960 day first uid[4] = 2019113286 day first uid[5] = 808463731 day first uid[6] = 1279801136 day first uid[7] = 1078085165 Fatal: file hdr read() 41984 != 1170103198 ('idxview dovecot.index' and 'logview dovecot.index.log' come back without any Fatal type errors, just gobs of information) -te -- Troy Engel | Systems Engineer Fluid, Inc | http://www.fluid.com

2 2

[Dovecot] Dovecot LDA Logging
by Jonathan Stewart 23 Mar '07

23 Mar '07

I have Dovecot LDA logging fine right now but I really don't like having my log files world writable because I have users with shell access. Is there a way to have Dovecot LDA log to syslog or would it be possible to write a mini-daemon that could log to syslog on behalf of Deliver or something else altogether? Jonathan

2 2

[Dovecot] Stalled imaptest10 process
by Steffen Kaiser 23 Mar '07

23 Mar '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, in order to stress my Dovecot test installation a bit, I compiled imaptest10.c. Now and then I see: Logi List Stat Sele Fetc Fet2 Copy Stor Dele Expu Appe Logo 100% 50% 50% 100% 100% 100% 33% 50% 100% 100% 100% 100% 30% 5% 5% 0 0 0 0 0 0 0 0 0 0 0 0 1/ 1 0 0 0 0 0 0 0 0 0 0 0 0 1/ 1 0 0 0 0 0 0 0 0 0 0 0 0 1/ 1 0 0 0 0 0 0 0 0 0 0 0 0 1/ 1 - 46. stalled for 1784 secs in APPEND - 46. stalled for 1785 secs in APPEND - 46. stalled for 1786 secs in APPEND - 46. stalled for 1787 secs in APPEND - 46. stalled for 1788 secs in APPEND - 46. stalled for 1789 secs in APPEND - 46. stalled for 1790 secs in APPEND (Sometimes SELECT or COPY) The maximum stalled time in APPEND is 1790s; in SELECT and COPY the maximum time is less than 20s until now. The only IMAP process loops around a poll(): poll([{fd=4, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=2, events=POLLERR|POLLHUP|POLLNVAL}, {fd=0, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 3, 0) = 0 gettimeofday({1174389105, 882286}, {4294967236, 0}) = 0 gettimeofday({1174389105, 882339}, NULL) = 0 poll([{fd=4, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=2, events=POLLERR|POLLHUP|POLLNVAL}, {fd=0, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 3, 999) = 0 gettimeofday({1174389106, 882011}, {4294967236, 0}) = 0 gettimeofday({1174389106, 882123}, NULL) = 0 poll([{fd=4, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=2, events=POLLERR|POLLHUP|POLLNVAL}, {fd=0, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 3, 0) = 0 So does imaptest itself: poll([{fd=3, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=52, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 2, 0) = 0 gettimeofday({1174389079, 93585}, {4294967236, 0}) = 0 write(1, " 0 0 0 0 0 0 "..., 68) = 68 write(2, " - 46. stalled for 1698 secs in "..., 39) = 39 gettimeofday({1174389079, 93814}, NULL) = 0 poll([{fd=3, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=52, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 2, 999) = 0 gettimeofday({1174389080, 93445}, {4294967236, 0}) = 0 gettimeofday({1174389080, 93497}, NULL) = 0 poll([{fd=3, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=52, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 2, 0) = 0 gettimeofday({1174389080, 93607}, {4294967236, 0}) = 0 There are no crashes, nothing. The server is idle then. I first assumed that it is related to an out-of-quota condition, but this time there is no fs quota set for the user. When I played with the quota, I ran imaptest with standard settings and without copybox=. I used this command: /usr/local/src/imaptest user=dvtest pass=pass clients=115 mbox=test.mbox box=box0 copybox=box1 msgs=200 ./configure summary: Install prefix ...................... : /usr/local/dovecot.rc27 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 ldap sql (modules) Building with password lookup modules : passwd passwd-file shadow pam checkpassword ldap sql (modules) Building with SQL drivers ............: pgsql # /usr/local/dovecot.rc27/sbin/dovecot -n # /usr/local/dovecot.rc27/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/dovecot.log protocols: imap imaps pop3 pop3s ssl_ca_file: /etc/ssl/certs/ca.crt ssl_cert_file(default): /etc/ssl/certs/imap.pem ssl_cert_file(imap): /etc/ssl/certs/imap.pem ssl_cert_file(pop3): /etc/ssl/certs/pop3.pem ssl_key_file(default): /etc/ssl/private/imap.key ssl_key_file(imap): /etc/ssl/private/imap.key ssl_key_file(pop3): /etc/ssl/private/pop3.key disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot//login login_executable(default): /usr/local/dovecot.rc27/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot.rc27/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot.rc27/libexec/dovecot/pop3-login login_log_format_elements: %p: user=<%u> method=%m rip=%r lip=%l %c verbose_proctitle: yes first_valid_uid: 1000 mail_location: maildir:%h/MailDir:CONTROL=/var/cache/dovecot/%i/control:INDEX=/var/cache/dovecot/%i/index mail_debug: yes dotlock_use_excl: yes maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_drop_priv_before_exec: yes mail_executable(default): /usr/local/dovecot.rc27/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot.rc27/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot.rc27/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_log zlib mail_plugins(imap): quota imap_quota mail_log zlib mail_plugins(pop3): quota mail_log mail_plugin_dir(default): /usr/local/dovecot.rc27/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot.rc27/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot.rc27/lib/dovecot/pop3 mail_log_prefix: %Us(%u) [%p]: mail_log_max_lines_per_sec: 30 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %u pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): oe-ns-eoh namespace: type: private separator: . inbox: yes hidden: yes auth default: mechanisms: plain login cache_size: 10 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890 verbose: yes debug: yes passdb: driver: ldap args: /usr/local/dovecot.rc26/etc/dovecot-ldap.conf passdb: driver: shadow userdb: driver: prefetch userdb: driver: ldap args: /usr/local/dovecot.rc26/etc/dovecot-ldap.conf userdb: driver: passwd-file args: /etc/passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 432 group: mail plugin: quota: fs Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRf/E3i9SORjhbDpvAQI5oQgAhOYKF9Rw0Ezz8Fn22xLjm/EtXdsRgpPx 6kcBkT+v4gLc15ORtcCrWLmU0bG+an//2wQ33cAiH2X/veZXEdXtwNultq+HPM3/ MYnjvNhL+OkkN9wAGOLTaRFJUDofEiXQzeNiVhYelmUsT4NaLzVQT4tRiYrbIAvK sHlkZJayE3gTIc5SzAviWxPPEkcJO+0HpMrym9USYbFtWNMVEMSYl9pGTVp9YTa0 oMUGpge1H8Qw75VMuf9jHC2SU8Xe889pv9CiButE0cpkQSsQj7Gf4+rX5V3ts3xv vw8oAZdsc3Rzms3JrWRiAsQHomXeAW0VPZSi/DjIOXT/AshXvnLDQw== =FLRG -----END PGP SIGNATURE-----

2 9

[Dovecot] ssl on embedded device
by burolib 23 Mar '07

23 Mar '07

Hi. I'm still facing troubles on my way. This time concerning ssl encryption. only dovecot-auth starts... imap and pop3 go down with this log dovecot: Mar 23 18:34:19 Info: Dovecot v1.0.rc27 starting up dovecot: Mar 23 18:34:20 Error: Temporary failure in creating login processes, slowing down for now dovecot: Mar 23 18:34:20 Error: imap-login: Can't load certificate file /etc/ssl/certs/server.pem: error:2507006C:lib(37):func(112):reason(108) dovecot: Mar 23 18:34:20 Error: child 849 (login) returned error 89 dovecot: Mar 23 18:34:20 Error: imap-login: Can't load certificate file /etc/ssl/certs/server.pem: error:2507006C:lib(37):func(112):reason(108) dovecot: Mar 23 18:34:20 Error: imap-login: Can't load certificate file /etc/ssl/certs/server.pem: error:2507006C:lib(37):func(112):reason(108) dovecot: Mar 23 18:34:20 Error: child 847 (login) returned error 89 dovecot: Mar 23 18:34:20 Error: child 848 (login) returned error 89 I attemped with makecert.sh, myown certificate which works with qmail-pop3d/stunnel, and cacert.org. All the times i get the same error. my dovecot.conf says: ## ## SSL settings ## #ssl_listen = #ssl_disable = no ssl_cert_file = /etc/ssl/certs/server.pem ssl_key_file = /etc/ssl/private/private.key #ssl_key_password = #ssl_ca_file = #ssl_verify_client_cert = no ssl_parameters_regenerate = 128 ssl_cipher_list = ALL:!LOW verbose_ssl = yes I spent a week trying to solve this out. Any ideas? ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://click.libero.it/imode

1 0

[Dovecot] lock file on embedded device
by burolib 23 Mar '07

23 Mar '07

thanks for the suggest. That's just an attempt.I will install everything on a device with usb support, therefore i will be able to use an hard disk or something like that. ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://click.libero.it/imode

1 0

[Dovecot] multiple instances of dovecot on one machine
by Marshal Newrock 23 Mar '07

23 Mar '07

I was trying to run two instances of dovecot on the same machine, each listening on a single IP. The problem I ran into was that each time one was started or restarted, the other stopped responding. I saw the following in the logs: Mar 23 00:02:27 sentinel dovecot: Dovecot v1.0.rc27 starting up Mar 23 00:02:27 sentinel dovecot: Socket already exists: /var/run/dovecot/dict-server After I saw that, I commented out the dict section and quota from the plugins. The second line disappeared, but I could still only get one dovecot listening at a time. In the end, I went back to a single dovecot listening on all IP's, and found another way to do what I was trying to do, so all is still working for me. I'm guessing I'm the first person to try to run two dovecots on one machine. Actually, I should clarify: there was also a third, listening to none on localhost, but there only for the lda process. The auth socket was set to /var/run/dovecot/auth-master. And this also was not accepting connections while the others were running. -- Marshal Newrock Ideal Solution, LLC - http://www.idealso.com

2 2

[Dovecot] Possible bug with removing e-mail when user over fs quota
by Qweb - Yavuz Aydin 23 Mar '07

23 Mar '07

Dear list, I don't know if this is by design or possibly a bug, but there is a difference when removing e-mail when a user is over filesystem quota when indexing is on or off. All is working fine on our servers when indexing is on, users can remove then purge e-mail when over quota, but when we turn off indexing (by setting INDEX=MEMORY) it doesn't work. Users can remove, but not purge. And after a reload of the page the e-mail is there again. We are using Dovecot 1.0.rc15 on Debian Sarge (through backports.org) with mboxes. We have set up the configuration of dovecot regarding quota's according to http://wiki.dovecot.org/Quota/FS Unfortunately I don't have time to try this on the latest version, but is there anyone out there willing to try? -- Best regards, Yavuz Aydin Qweb Internet Services

2 1

[Dovecot] changing the separator
by Marten Lehmann 23 Mar '07

23 Mar '07

Hello, is it possible the change the folder separator from "." to "/"? Users shall be able to have folders like "Junk/aol.com/*". Regards Marten

5 7

[Dovecot] maildirsize problem?
by Alan Mosca [Aluminati] 23 Mar '07

23 Mar '07

Hello all, Recently I have received a few complaints from users that their quota was being reported wrong. This seems to have started when I switched to quota=maildir and ignore=Trash (did both at the same time). The main reported problem is that maildirsize is not correctly updated when they delete messages. My personal hypothesis is something like this: - User moves to Trash - Trash is ignored so it is not marked on the maildirsize (?) - User purges trash - Trash is still ignored so it is still not marked (?) Resulting in a buildup of errors in the maildirsize file. Would it be a good idea to mark the maildirsize file when a file is moved to an ignored folder? That could though potentially lead to people just moving to trash instead of deleting. Thank you guys and keep up the good work! -- Alan Mosca Systems Administrator Aluminati Network Group

2 1

[Dovecot] Timeout while logging in
by Kevin Richter 23 Mar '07

23 Mar '07

Hi, sometimes there is a timeout, while logging in. Dovecot-rc24 Dovecot uses PAM, PAM uses a LDAP server. Solaris 10 The log, if everything is ok: auth(default): client in: AUTH 1 PLAIN service=POP3 secured lip=x.x.x.x rip=x.x.x.x resp= auth(default): client out: CONT 1 auth(default): client in: CONT<hidden> auth(default): client out: OK 1 user=ssal0041 auth(default): master in: REQUEST 453 4779 1 auth(default): master out: USER 453 ssal0041 system_user=ssal0041 uid=3092 gid=1100 home=/home/ss pop3-login: Login: user=<ssal0041>, method=PLAIN, rip=x.x.x.x, lip=x.x.x.x, TLS POP3(ssal0041): Effective uid=3092, gid=1100 POP3(ssal0041): mbox: data=/home/ssal0041/mail/:INBOX=/var/mail/ssal0041 POP3(ssal0041): mbox: root=/home/ssal0041/mail, index=/home/ssal0041/mail, inbox=/var/mail/ssal0041 POP3(ssal0041): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 The log, if a timeout occures: auth(default): client in: AUTH 1 PLAIN service=POP3 secured lip=x.x.x.x rip=x.x.x.x resp= auth(default): client out: CONT 1 auth(default): client in: CONT<hidden> auth(default): client out: OK 1 user=ssal0041 auth(default): master in: REQUEST 454 4770 1 auth(default): master out: USER 454 ssal0041 system_user=ssal0041 uid=3092 gid=1100 home=/home/ss pop3-login: Login: user=<ssal0041>, method=PLAIN, rip=x.x.x.x, lip=x.x.x.x, TLS The rest is missing. Any ideas, how I can debug this issue? Regards, Kevin

2 8

Re: [Dovecot] deliver to subfolder with dovecot's LDA
by Bill Boebel 23 Mar '07

23 Mar '07

On Fri, March 16, 2007 8:12 pm, Tom Bombadil <grlists(a)gmail.com> said: > How can deliver messages to a subfolder using the LDA? > For example, I want a message to joe+spam(a)abc.com to be placed inside > the 'spam' subfolder. $ deliver --help Usage: deliver [-c <config file>] [-d <destination user>] [-m <mailbox>] [-f <envelope sender>] So for the example above, you can call it like this: $ deliver -d joe(a)abc.com -m spam To do this from Postfix, /etc/postfix/master.cf: dovecot unix - n n - - pipe flags=DRhu user=virtual argv=/usr/libexec/dovecot/deliver -d ${recipient} -f ${sender} -m ${extension} However, I think LDA freaks out if you pass -m "". So this might not work when there is no "+folder". Timo: Should -m treat empty string as if -m was not passed at all? Bill

4 14

[Dovecot] I wrote a managesieve server for Dovecot
by Neale Pickett 22 Mar '07

22 Mar '07

I have written a managesieve server from scratch in Python. I did just enough work to get it working with avelsieve (the squirrelmail plugin), smartsieve, and KDE's sieve kioplugin. It supports the entire Internet draft. Since I didn't have a working sieve server to compare against, I'm not sure if it's 100% compatible with timsieved. Client applications seem to work okay anyway. I wrote it in such a way as to decouple how authentication is carried out and how sieve scripts are actually stored, so you could for instance modify this to work with SASL and Exim. Currently it only has code for PAM and Dovecot's LDA, because I run Postfix :). TLS support is in the code but disabled because I had problems writing a unit test for it. All my connections are from localhost anyway. http://woozle.org/~neale/repos/pysieved if anyone is interested. I haven't looked closely at Stephan Bosch's managesieve server in C but I do want to acknowledge that he has written a C managesieve server that currently exists as a patch to the Dovecot source code. People looking for a managesieve implementation in C are encouraged to try his patch out: http://sinas.rename-it.nl/~sirius/ Neale

3 5

[Dovecot] tilde in mbox:, when used in non-system user db
by Michal Soltys 22 Mar '07

22 Mar '07

Originally I've thought that this is related to INBOX field, but it turned out it happens only when you specify mbox. Consider following passwd-file: testms::10000:10000:imap,,,:/home/vmail/ppgk.com.pl/testms/./::userdb_mail=mbox:~/Mail:INBOX=/home/vmail/ppgk.com.pl/%u/inbox or following line from userdb static: args = uid=10000 gid=10000 home=/home/vmail/ppgk.com.pl/%u/./ mail=mbox:~/Mail:INBOX=/home/vmail/ppgk.com.pl/%u/inbox In both cases, in user's directory, there will be an empty ~/Mail directory created, in addition to Mail and inbox. No idea about how sql or ldap would behave here, but global mail_location from dovecot.conf doesn't suffer from this issue (~ was expanded properly in ktrace dump). Chroot specification (/./) doesn't matter here. If I change mbox:~/Mail:INBOX=..... to mbox:/home/vmail/ppgk.com.pl/%u/Mail:INBOX=~/inbox then everything will be fine - no extra '~' dir. Thus my assumption it's not INBOX field related. Looking at ktrace, it seems that imap process is checking for the existence of ~/Mail, without expanding tilde. Then quite a bit later, it creates Mail as a "side effect" of creating Trash subdirectory. Relevant fragments: 1853 imap CALL mkdir(0x8a79b100,0x1f8) 1853 imap NAMI "~/Mail" 1853 imap RET mkdir -1 errno 2 No such file or directory 1853 imap CALL sigprocmask(0x1,0xffffffff) 1853 imap RET sigprocmask 0 1853 imap CALL mprotect(0x3c0ec000,0x1000,0x3) 1853 imap RET mprotect 0 1853 imap CALL mprotect(0x3c0ec000,0x1000,0x1) 1853 imap RET mprotect 0 1853 imap CALL sigprocmask(0x3,0) 1853 imap RET sigprocmask -65793/0xfffefeff 1853 imap CALL mkdir(0x8a79b108,0x1f8) 1853 imap NAMI "~" 1853 imap RET mkdir 0 1853 imap CALL mkdir(0x8a79b100,0x1f8) 1853 imap NAMI "~/Mail" 1853 imap RET mkdir 0 and 1853 imap CALL stat(0x8a79b180,0xcfbeb5c0) 1853 imap NAMI "/home/vmail/ppgk.com.pl/testms/Mail/Trash" 1853 imap RET stat -1 errno 2 No such file or directory 1853 imap CALL stat(0x8a79b1b0,0xcfbeb600) 1853 imap NAMI "/home/vmail/ppgk.com.pl/testms/Mail/Trash" 1853 imap RET stat -1 errno 2 No such file or directory 1853 imap CALL mkdir(0x8a79b1e0,0x1f8) 1853 imap NAMI "/home/vmail/ppgk.com.pl/testms/Mail" 1853 imap RET mkdir 0 1853 imap CALL open(0x8a79b1b0,0xa02,0x1b0) 1853 imap NAMI "/home/vmail/ppgk.com.pl/testms/Mail/Trash" 1853 imap RET open 7 My configuration is prtty much the same as previously: openbsd 3.9, i386, dovecot 1.0-rc27 (latest nightly, but the same happened in stock 1.0rc27) dovecot.userdb: testms::10000:10000:imap,,,:/home/vmail/ppgk.com.pl/testms/./::userdb_mail=mbox:~/Mail:INBOX=/home/vmail/ppgk.com.pl/%u/inbox dovecot.passdb: testms:{PLAIN}test: base_dir: /var/dovecot/ protocols: imap imaps pop3 pop3s ssl_listen: * ssl_ca_file: /etc/ssl/cert_bundle.pem ssl_cert_file: /etc/ssl/ca_ppgk/certs/fetch_crt.pem ssl_key_file: /etc/ssl/ca_ppgk/private/fetch_key.pem verbose_ssl: yes login_dir: /var/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting: Dovecot IMAP server ready. login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no valid_chroot_dirs: /var/mail:/home/regular:/home/vmail verbose_proctitle: yes first_valid_uid: 1999 first_valid_gid: 10 mail_location: mbox:~/Mail:INBOX=/var/mail/%u mail_debug: yes fsync_disable: yes lock_method: fcntl maildir_copy_with_hardlinks: yes mbox_read_locks: fcntl mbox_write_locks: fcntl mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login verbose: yes debug: yes passdb: driver: passwd-file args: /etc/dovecot.passdb passdb: driver: bsdauth userdb: driver: passwd-file args: /etc/dovecot.userdb userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master:

2 1

[Dovecot] Getting more spam
by postmaster＠webisp.co.uk 22 Mar '07

22 Mar '07

Hi I am taking part in writing an anti spam filter for my uni project. However at the moment I am not getting much spam to my mail server - running dovecot and postfix :) Do you have any suggestions for getting more? Thanks Tom

5 7

Re: [Dovecot] Replacing qmail + vpopmail with: sendmail + dovecot.
by David Robillard 22 Mar '07

22 Mar '07

> Hi, > I wonder if it posible to replace qmail + vpopmail with sendmail + dovecot? > > The idea is like this: > - use sendmail + milter API to filter spam/virus and deliver the email to > the dovevot MDA (LDA) > - dovecot should save the email to the directory as specified in the > vpopmail DB > - maintain the vpopmail BD (users + passwd) > - use dovecot pop3/imap for the clients > - use sendmail again to receive the email from the pop3/imap users and > deliver the email to the internet as usual. > > Anyone has done this? It is posible in the paper, in the real world? Hi Oliver, We run sendmail + dovecot on FreeBSD for around 3500 users. It runs smooth. We also run two other FreeBSD machines with Sophos PureMessage for Anti-SPAM and Anti-Virus cleanup which is linked via sendmail's milter. You're going to need Procmail to link sendmail and dovecot for local mail delivery to the user's mbox or Maildir, which ever you prefer. We're using Maildir here to serve both IMAP over SSL and POP3 over SSL. If you need any help in the setup of sendmail + procmail + dovecot, just tell me. Of course, if you're more experienced with Postfix, then use it. IMHO it's not as flexible as sendmail. But YMMV. Have fun, David -- David Robillard UNIX systems administrator & Oracle DBA CISSP, RHCE & Sun Certified Security Administrator Montreal: +1 514 966 0122

2 2

[Dovecot] GSSAPI authentication behind HA servers
by Mustafa A. Hashmi 22 Mar '07

22 Mar '07

Hi all, We have 2 mail servers sitting behind linux-HA machines.The mail servers are currently running dovecot 1.0rc2. Looking to enable GSSAPI authentication, I exported krb keytabs for imap/node01.domain@REALM and imap/node02.domain@REALM for both mail servers. However, clients are connecting to mail.domain.com, which results in a mismatch as far as the keytab is concerned (and rightly so). Connections directly to node01 and node02 work fine for gssapi auth. I proceeded to export a key for mail.domain.com into the same keytab for both the nodes, however, I don't think more than a single key is checked for the imap service, and authentication errors continued. Is anybody running something similar? Could you please explain how you have this working on your end? Appreciate any help. Regards, -- Mustafa A. Hashmi mahashmi(a)gmail.com

1 1

[Dovecot] Preparing for sharing with ACLs
by Mike Brudenell 22 Mar '07

22 Mar '07

Greetings - I'm finalising the layout of our new mailstore ready for a trial service using Dovecot (switching from the UW IMAP server). This is using Maildir mailboxes, changing from our current mix of MBX and traditional Berkeley. One of the things we are often asked for is how someone can grant another access to their mailbox: eg, a Head of Department wants the Departmental Secretary to review and reply to e-mails, but not tell her the password. I understand that Dovecot doesn't provide a user-interface for setting up or manipulating these, nor the IMAP ACL extension at this time, so... Q1. Are there plans to add support for ACLs in the future, along with an end-user accessible means of setting these up and manipulating them? I also understand that it is currently possible for the Mail Admin to set up ACLs (globally and/or per-mailbox) and shared folders (I admit I'm having trouble getting my head around the latter in the Wiki a bit). I' hoping to avoid using the current "has to be done by the Administrator" setup, and instead want to plan for any future end- user interface. We are using filestore quotas for the Maildirs, so at present a user's Maildir directories and files are owned by their username (UNIX uid) and group (UNIX gid). * Naturally for filestore quotas to continue to work items need to continue to be owned by the person's username (UNIX uid). When end-user support for shared mailboxes and ACLs comes along one day (hopefully!) I assume two levels of access control are needed: 1. At the filestore level the other authorised users will need read and/or write access to the directories and files comprising the Maildir, and 2. Suitable ACLs will be needed to grant access via Dovecot to authorised persons, but not to other random people. So looking to the future, I'm therefore thinking that instead of having each user's Maildir directories and files owned by their UNIX uid and gid I should instead have them owned by their UNIX uid and a common-to-everyone UNIX gid. Eg, drwxrwx--- user1:mail directoryname -rw-rw---- user1:mail filename I realise there is an element of risk here, as we would be relying on Dovecot's security to limit access so that only authorised users can access a given person's mailbox. Is this the right approach to adopt? Or is there a better way of (one day) enabling Person A to share their mailbox to Person B but not Person C? (We need a solution that is general and based on ACLs, not one that relies on our creating custom UNIX groups and assigning people's usernames to these.) I've read the Wiki pages on ACLs and Shared Folders, but am having trouble putting the information together in my mind to (one day) solve this particular requirement. Can anyone shed any light, please? Cheers, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. *

2 1

[Dovecot] home_location or smth like that
by razor 22 Mar '07

22 Mar '07

hi dovecot list help me please dovecot-1.0.r27 exim lda virtual users in ldap base i decided to start using the sieve pluging so i have to make the homes (now my homeDirectory in ldapbase is /nonexistent). there is a lot of users, so i dont wonna to make changes in every ldap record + imho the hard link to userhome in ldap - its a not good idea. so is there any way to make it easy? may be like home_location = bla-bla-bla/%n/home in dovecot.conf (or in dovecot-ldap.conf ) sorry for my english -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

2 3

[Dovecot] corrupted transaction log error resulting in multiple deliveries
by Justin McAleer 22 Mar '07

22 Mar '07

I'm finally picking my dovecot project back up now, and after upgrading rc19 to rc27, I sent a test message to an existing account which resulted in log entries like these: Mar 16 08:45:37 node7 deliver(user(a)example.com): Corrupted transaction log file /var/indexes/example/com/u/us/user/.INBOX/dovecot.index.log: Append with UID 3, but next_uid = 15368 Mar 16 08:45:37 node7 deliver(user(a)example.com): msgid=<20070316124031.8F089D39A5(a)node7.neonova.net>: save failed to INBOX Mar 16 08:45:37 node7 postfix/pipe[29267]: 8F089D39A5: to=<user(a)example.com>, relay=dovecot, delay=306, delays=306/0.01/0/0.02, dsn=4.3.0, status=deferred (temporary failure) So, as you can see deliver has the problem and defers delivery. Is dovecot supposed to be able to recover from a corrupted log file on its own? It repeated this until I manually wiped out the index directory (didn't try just removing the log files first, sorry). The kicker is that deliver actually did save the message to the inbox every time, so multiple copies were delivered (every time I flushed the queue until it was actually fixed, a copy was delivered). I have my mail directories on an NFS mount, and indexes on localdisk, FYI.

2 10

[Dovecot] Throttling Logins
by Sean Kamath 22 Mar '07

22 Mar '07

Hi. Earlier today I was hit with 612 login attempts in 7 minutes. They ramped up slowly, too. :-) They quickly hit the file descriptor limit. And then a login server spawned and died so quickly that dovecot just died. My question is, is there a way to throttle the number of login connections? I'm doing it in my firewall now, but it would be nice to be able to say something like "max-login-attempts: X" before we blacklist the IP (for some configurable time). yeah, I know V4.2 :-) By the way, I *really* appreciate all the effort that's gone into Dovecot. Great work, everyone. Sean

2 2

[Dovecot] mail looping
by Steven F Siirila 22 Mar '07

22 Mar '07

We are running Postfix 2.3.3 and Dovecot 1.0-RC27 on a Solaris 10 server. We use the Dovecot LDA for local delivery. Problems arise with looping mail whenever a user's .forward contains a reference to themselves. This most frequently occurs when a user sets up a vacation since it then puts this in their .forward file: \username, "|/usr/bin/vacation username" The vacation program runs fine, and sends a notice back to the message originator, but when an attempt is made to deliver the message locally, it fails with: Mar 21 13:02:16 myhost.mydomain postfix/local[13373]: 3DF5A2C63: to=<systest(a)myhost.mydomain>, relay=local, delay=0.15, delays=0.12/0/0/0.03, dsn=5.4.6, status=bounced (mail forwarding loop for systest(a)myhost.mydomain) Any ideas? I hope it's something stupid I've overlooked... Noteworthy line in postfix/main.cf: mailbox_command = /opt/dovecot/libexec/dovecot/deliver -f "$SENDER" and finally, dovecot -n: # /etc/opt/dovecot/dovecot.conf syslog_facility: local6 protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_cert_file: /etc/opt/openssl/certs/dovecot.pem ssl_key_file: /etc/opt/openssl/private/dovecot.pem shutdown_clients: no login_dir: /var/opt/dovecot/run/dovecot/login login_executable(default): /opt/dovecot/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot/libexec/dovecot/imap-login login_executable(pop3): /opt/dovecot/libexec/dovecot/pop3-login login_processes_count: 32 login_max_processes_count: 4096 max_mail_processes: 8192 first_valid_uid: 100 default_mail_env: mbox:~/:INBOX=/var/mail/%u mail_location: mbox:~/:INBOX=/var/mail/%u mail_full_filesystem_access: yes mbox_lazy_writes: no mail_executable(default): /opt/dovecot/libexec/dovecot/imap mail_executable(imap): /opt/dovecot/libexec/dovecot/imap mail_executable(pop3): /opt/dovecot/libexec/dovecot/pop3 mail_plugin_dir(default): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /opt/dovecot/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv namespace: type: private separator: / location: mbox:~/:INBOX=/var/mail/%u inbox: yes hidden: yes auth default: username_format: %Lu verbose: yes debug: yes passdb: driver: pam args: session=yes * userdb: driver: passwd -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

1 1

[Dovecot] Timeouts connecting via POP3
by Don O'Neil 22 Mar '07

22 Mar '07

I'm experiencing timeouts from time to time from both Mac Mail and Outlook when connecting to my server. I originally suspected that it might be process # related, so I increased the auth & login process counts but that hasn't seemed to make a difference. I'm running 1.0rc10 which came with my DirectAdmin control panel. I'm wondering if this problem is known and was fixed in a later release? I'm waiting for instructions from the DirectAdmin folks on building a new version in case they do something special. Any ideas? Thanks!

2 6

[Dovecot] Solaris Dovecot dovecot dovecot-1.0.rc27
by Randall Svancara 22 Mar '07

22 Mar '07

To all, I am using Dovecot on solaris 10. Home directories are mounted using NFS. However, they are not readable by root. I compiled Dovecot from the source. I set the following environment variables: export LDFLAGS='-L/local/software/openssl/lib -R/local/software/openssl/lib' export CPPFLAGS=-I/local/software/openssl/include Then I ran gmake and the gmake install. In the server logs, when I attempt to connect to port 993 using imap over SSL, i receive the following error: dovecot: Mar 21 15:34:25 Info: imap-login: Login: user=<someusername>, method=PLAIN, rip=134.121.92.228, lip=134.121.5.141, TLS dovecot: Mar 21 15:34:25 Error: IMAP(someusername): ld.so.1: imap: fatal: libgcc_s.so.1: open failed: No such file or directory dovecot: Mar 21 15:34:25 Error: child 13085 (imap) killed with signal 9 Has anyone seen similar issues? Randall

6 6

[Dovecot] Comments about LDA wiki page
by Magnus Holmgren 22 Mar '07

22 Mar '07

I've just tried out Dovecot LDA. The reason I didn't want to use it before was that I found it unnecessary together with Exim, plus I wanted to use Exim's filtering. But now I wanted to see if can notice any improvement when the indexes are updated on delivery, and I saw that it's possible to use Exim filters and pass the resulting folder with -m. Now, correct me if I'm wrong, but IIUC some corrections, improvements, and comments could be made on http://wiki.dovecot.org/LDA. In the "Site-wide setup" section (and in dovecot.conf) it's suggested that access be restricted to the master socket somehow. The first Exim example ("System-users"), however, requires a world-writable socket. Uncomment "group = mail" and deliver will complain that setgid() fails. In this situation, the "-d $local_part@$domain" is unnecessary because then deliver will use the name of the user it's running as (it should probably have been just "-d $local_part" anyway). However, if deliver is run by root (which is by default impossible under Exim) or setuid root, then a destination user is mandatory. Oh wait, without -d the auth socket isn't used at all, only the HOME environment variable and default_mail_env are. Well, it shouldn't matter much if you're running a standard pam/passwd setup, but with a more complicated non-virtual setup I see only four solutions: Make deliver setuid root, remove root from the compiled-in FIXED_NEVER_USERS list, run deliver as a user/group that has write access to all mailboxes, or make the master socket world-writable. -- Magnus Holmgren holmgren(a)lysator.liu.se (No Cc of list mail needed, thanks)

2 1

[Dovecot] How does vpopmail support works?
by Oliver Schulze L. 22 Mar '07

22 Mar '07

Hi, I'm still trying to migrate a running qmail + vpopmail to sendmail + dovecot. I need the milter stuff from sendmail. I got sendmail + dovecot running using the migrated tables from the vpopmail DB, but I'm facing the UID problem in pop3. So, now I'm following the vpopmail authdb path. My questions are: - what do I need, a running vpopmail server (lib + binary, etc)? - or only the DB? This is on Centos 4.4 Many thanks Oliver -- Oliver Schulze L. | Get my e-mail after a captcha in: Asuncion - Paraguay | http://tinymailto.com/oliver

1 0

[Dovecot] Wiki needs updating: Dovecot LDA + Dovecot Sieve + Exim
by Stephen Usher 22 Mar '07

22 Mar '07

So as to make sure that Dovecot Sieve's vacation system works Exim has to be forced to generate a "Reply-To:" header in the message (which it doesn't do by default). The current example for using the Dovecot LDA with Exim doesn't do this. Here is a replacement example for the local_delivery transport:- local_delivery: driver = pipe command = /usr/local/libexec/dovecot/deliver -d $local_part message_prefix = message_suffix = log_output delivery_date_add envelope_to_add return_path_add headers_add = Reply-To: ${if def:header_reply-to:{$h_reply-to:}{$h_from:}} #group = mail #mode = 0660 Basically, if the Reply-To: header exists than it merely gets overwritten with itself. If it doesn't then the header is created and the contents of the From header is put into it. If this is not done then the libsieve over restrictive rules (requiring a "Reply-To:" header even though the RFC doesn't require it) will not allow the vacation system to work. Steve -- --------------------------------------------------------------------------- Computer Systems Administrator, E-Mail:-steve@earth.ox.ac.uk Department of Earth Sciences, Tel:- +44 (0)1865 282110 University of Oxford, Parks Road, Oxford, UK. Fax:- +44 (0)1865 272072

3 2

[Dovecot] Doubled mails and UIDs
by Adam Lackorzynski 22 Mar '07

22 Mar '07

Hi, I'm still seeing mails being downloaded twice via POP3 in my setup, running rc27. The log file shows: dovecot: Mar 18 22:08:05 Error: POP3(joe): mbox sync: UID inserted in the middle of mailbox /home/joe/Mail/INBOX (442671 > 80, seq=10, idx_msgs=153) dovecot: Mar 18 22:08:05 Info: POP3(joe): Disconnected: Logged out top=0/0, retr=153/1069109, del=153/153, size=1066449 The next POP3 connect will fetch most of the messages again. dovecot: Mar 18 22:18:48 Info: POP3(joe): Disconnected: Logged out top=0/0, retr=147/1006204, del=147/147, size=1003647 Is there a problem if an incoming message already contains an X-UID header? Might it be worthwhile to remove this header when mails are being delivered (e.g. with procmail)? Thanks, Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

2 4

[Dovecot] rc27 assert, mbox format
by Jeff A. Earickson 22 Mar '07

22 Mar '07

Timo, After several days of flawless work, rc27 gave an assert/core yesterday: Mar 19 00:10:46 karst dovecot: [ID 107833 mail.error] IMAP(user): file mbox-sync-rewrite.c: line 423: assertion failed: (need_space == (uoff_t)-mails[idx].space) Mar 19 00:10:46 karst dovecot: [ID 107833 mail.error] IMAP(user): Raw backtrace: 0x8a51c -> 0x473f4 -> 0x479b0 -> 0x41c50 -> 0x42430 -> 0x431d4 -> 0x43dac -> 0x44040 -> 0x2aa70 -> 0x2afec -> 0x2337c -> 0x23508 -> 0x235f0 -> 0x90c18 -> 0x9043c -> 0x2cfac -> 0x1dbe8 I could see nothing wrong with the user's mailbox, it was not corrupted. My setup: Solaris 10 sparc, mbox format, INBOX NFSv4 mounted from another S10 sparc system, no disk quotas, ZFS filesystem for both the INBOX filesystem and the user's home directory. Unfortunately, I compiled dovecot with Sun's cc compiler, so the gdb traceback is fairly useless. I need to go back to gcc. Jeff Earickson Colby College

2 2

Re: [Dovecot] Dovecot 'suicide'
by John Andrea 21 Mar '07

21 Mar '07

>dovecot: Time just moved backwards by 6 seconds So this will show up when systems move from daylight savings time to standard time ? >As others mentioned, using ntpd avoids this problem entirely. Not entirely. If you need to restart ntpd, the time can jump when catching up with 'step-tickers'.

3 2