- dovecot - dovecot.org

[Dovecot] UW-IMAP to Dovecot conversion - How to migrate the folders?
by Patrick - South Valley Internet 23 Aug '07

23 Aug '07

Hi all, I've read so much information on this that I'm a little confused as to what to follow. Here's what's going on: We just migrated away from our AIX machines which were running Postfix and UW-IMAP. We're now running Postfix with Dovecot. I already converted everyone's mbox file to maildir, but now I'm having a little troubles with how to exactly populate their IMAP folders. People are saying they cannot see their folders. These 'folders' they are talking about can be found in their /home directory. I have the following URLs I've been looking at: http://wiki.dovecot.org/Migration/MailFormat http://people.redhat.com/rkeech/maildir-migration.txt http://wiki.dovecot.org/Plugins/Convert http://www.dovecot.org/list/dovecot/2007-June/023757.html What would be the suggested method to convert them? So far I understand that I need to somehow populate the /home/USERNAME/Maildir/subscriptions file with the items located in /home/USERNAME/.mailboxlist and then I don't know what to do from there. I don't know if I need to incorporate a Dovecot plugin, or if there is a script I can run to do this for me. Since this is a live server, I would prefer to test on a single account before I run a plugin that would effect all users globally. Any help would be very appreciated - thanks in advance! Patrick

6 12

[Dovecot] Exim-dovecot-Horde/imp-Mysql
by Andre Eisvogel 22 Aug '07

22 Aug '07

Dear all, I'm running a linuxbox with ' Dovecot<->Exim<->horde/IMP<-> Mysql ', this is a very good combination and works excellent for the system users. Now I want to change the configuration and authenticate against the mysql database from horde. That way it is much easy for me to create (virtual) mail users. I also want to use the mail alias of the horde users for Exim and Dovecot. My questions are; is it possible to use the horde mysql database for this? And is it also possible for the mail alias of horde? If this is possible, is there a howto of this configuration? The packages i'm using are: Exim 4.67 Dovecot 1:1.0.3 Horde 3.1.4 Mysql 5.0.45 PHP 5.2.3 -- Met vriendelijke groet / Kind regards, André Eisvogel

2 2

[Dovecot] maildir question
by Tim Bates 22 Aug '07

22 Aug '07

If I copy message files (from a command prompt) will dovecot get upset or confused? Do I need to delete index files or anything like that? I ask because I need to restore some messages from a backup, but not restore the entire maildir. I tried some the other day as a test, but the user is saying that they didn't appear. TB ********************************************************************** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. **********************************************************************

3 3

[Dovecot] Subscriptions - delivering to different folders
by bichumo 21 Aug '07

21 Aug '07

Hi, I am using Postfix and Dovecot. I have set up backup_mailbox(a)domain.tld, which gets mail copies from user1(a)domain.tld user2(a)domain.tld user3(a)domain.tld, the copy option is set in postfix recipient_bcc_maps = path_to_file_recipient_bcc. In recipient_bcc file I have: user1(a)domain.tld backup_mailbox(a)domain.tld user2(a)domain.tld backup_mailbox(a)domain.tld user3(a)domain.tld backup_mailbox(a)domain.tld Postfix does the job and copies user1, user2, user3 emails to backup_mailbox. But I also want to filter mails in backup_mailbox and to put user1 mails to USER1 folder in backup_mailbox, user2 mails to USER2 folder in backup_mailbox and so on. How this is possible? I made an entry in subscriptions file of user1, user2, user3. Now I have folders .user1, .user2, user3 in backup_mailbox folder and I can also see these folders through webmail client (squirrelmail), but how do I put email copy which comes from user1(a)domain.tld to backup_mailbox(a)domain.tld to go not to main folder of backup_mailbox but to USER1 folder in backup_mailbox folder. Thanks for any suggestions.

2 1

[Dovecot] userdb override?
by Leroy van Logchem 21 Aug '07

21 Aug '07

Hi, I used to change the mailbox root for some users using a custom userdb file which contains lines like: doe::20000:200::/u/doe::userdb_mail=mbox:/u/doe/Mail:INBOX=/var/mail/%u The logfiles shows the mail location stays default ( rc15 worked ): --- dovecot: Aug 21 09:43:49 Info: auth(default): master out: USER 250 doe system_user=doe uid=20324 gid=200 home=/u/doe dovecot: Aug 21 09:43:49 Info: imap-login: Login: user=<doe> dovecot: Aug 21 09:43:49 Info: IMAP(doe): Effective uid=20000, gid=200, home=/u/doe dovecot: Aug 21 09:43:49 Info: IMAP(doe): mbox: data=/u/doe/:INBOX=/var/mail/doe dovecot: Aug 21 09:43:49 Info: IMAP(doe): mbox: root=/u/doe, index=/u/doe, inbox=/var/mail/doe --- Configuration: # 1.0.3: etc/dovecot.conf mail_location: mbox:~/:INBOX=/var/mail/%u auth default: mechanisms: plain login digest-md5 cram-md5 ntlm verbose: yes debug: yes passdb: driver: passwd-file args: /etc/userdb_extra passdb: driver: pam userdb: driver: passwd args: /etc/userdb_extra userdb: driver: passwd-file args: /etc/userdb_extra -- Leroy

2 2

Re: [Dovecot] imap memory footprint rather large
by Timo Sirainen 21 Aug '07

21 Aug '07

[back to list] On Tue, 2007-08-14 at 14:50 +0300, Timo Sirainen wrote: > On Tue, 2007-08-14 at 13:47 +0200, martin f krafft wrote: > > also sprach Timo Sirainen <tss(a)iki.fi> [2007.08.14.1250 +0200]: > > > mmap()ing a 200MB file doesn't mean that it immediately uses 200MB > > > of memory. It just reserves that much virtual space. Even if it > > > happens to read the whole 200MB, it shouldn't be much different > > > from simply reading the file in small parts, in which case kernel > > > places the same 200MB to page cache. > > > > I am aware of that. I just wonder why dovecot has to read the entire > > file into memory, via read() or mmap(). > > It doesn't. It mmaps it entirely so it doesn't waste CPU mmaping and > unmapping parts of it. It's then accessed only when and where needed. It probably does access the whole file though. This is because all the cached data for messages are stored next to each others. So now that your client fetches only INTERNALDATE it doesn't really need to read much, but because mmaped pages are read 4kB at a time, it practically reads the whole file. Perhaps this could use some work in future too, so that fields that are accessed together are stored in cache file close together. But then if multiple clients are used, there can be conflicting access patterns, and what's good for one client would be bad for another. Data could also be duplicated to reduce disk reads for different access patterns, but that comes at the cost of disk space..

4 4

[Dovecot] Dovecot fails almost every 20 minutes exactly
by Patrick - South Valley Internet 21 Aug '07

21 Aug '07

Hi all, We just set up our new mail servers using Postfix and Dovecot. We have implemented a load balanced solution to where our two mail servers have a common NFS share. Everything is working great. Everything but Dovecot for the most part. In testing, Dovecot was great. Now that we're in the production environment, we've noticed that every 20 minutes, Dovecot will stop running. But it gets even weirder - it appears that Machine A will stop, then 20 mins later after we issue a 'service dovecot restart', Machine B will stop. Then the whole process starts over when we restart Dovecot on Machine B. I can't see anything out of the ordinary in the log files either. I'm at a loss as to what's going on. Here's my dovecot -n: ################################ # 1.0.3: /etc/dovecot.conf listen: * ssl_cert_file: /usr/share/ssl/hermes.garlic.com/hermes.garlic.com.cert.pem ssl_key_file: /usr/share/ssl/hermes.garlic.com/hermes.garlic.com.privatekey.pem login_dir: /var/run/dovecot-login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login first_valid_uid: 200 mail_location: maildir:/home/%u/Maildir:INDEX=MEMORY maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: user: dovecot-auth username_format: %Lu passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix ################################ Any ideas what could be wrong? I don't think that setting up a cron to restart both dovecot servers is an idea solution - I'm hoping this is an easy fix. Thanks in advance. Patrick

2 2

[Dovecot] Dovecot IDLE bandwidth usage
by Fredrik Tolf 20 Aug '07

20 Aug '07

Hi list, I just recently discovered the IMAP IDLE command and tried it out with my Dovecot server. It seems to work fine and all, but it seems to be using quite a deal of bandwidth, because of the "* OK Still here" messages sent by the server at two minute intervals. I would argue that is a bit of a problem when using the IDLE command for "Push mail" on a mobile phone. I don't know exactly what parts of the packets that mobile carriers collect payment for, but the Ethernet bandwidth consumed by one such message is 149 bytes (83 bytes for the message itself, and 66 bytes for the TCP ACK from the client). At two minute intervals, that becomes over 100 KB per day, and over 3 MB per month. At GRPS rates typical here in Sweden, that becomes about 5-7 USD per month. That might not seem tremendously much, but seeing how it is what takes up the vast majority of the IMAP bandwidth, it is still quite annoying. Are those messages really necessary? I mean, Dovecot still times out after half an hour if the client doesn't "finish" the IDLE command and re-issues it, right? (Coincidentally, I would like to argue that it would be better not to time out at all during an IDLE command and just turn on TCP keepalives instead, but that is the minor issue here) I'll apologize in advance if this is already a tunable option, but I haven't found anything about it in the configuration file. Cheers, Fredrik Tolf

5 5

[Dovecot] MANAGESIEVE patch v6 for dovecot 1.0.3
by Stephan Bosch 18 Aug '07

18 Aug '07

Hello dovecot users, I have updated the MANAGESIEVE patch to (hopefully) fix the compilation issues reported by Robin Breathe. This is a patch against the latest stable release 1.0.3. It currently won't compile with 1.1 due to significant changes in the master code. Change Log V6 ------------- - Corked the client output stream while producing the capability greeting and on other some other occasions as well. Some naive client implementations expect to receive this as a single tcp frame and it is a good practice to do so anyway. Using this change the Thunderbird sieve extension (v0.1.1) seemed to work. However, scripts larger than a tcp frame still caused failures. All these issues are fixed in the latest version of the sieve add-on (currently v0.1.4). - Cleaned up the new proxy source. My editor made the indentation a complete mess in terms of TABs vs spaces. - Added TRYLATER response codes to BYE and NO messages where appropriate. - Recopied the libsieve library into this patch to incorporate any changes that were made (only sieve-cmu.c still needs to be compared to the old cmu-sieve.c). This also solves the __attribute__((unused)) GCC dependencies. These were fixed long ago by Timo.... the code duplication beast strikes again. (Will have to do this again for dovecot 1.1) - Removed spurious return value from void function in src/lib-sieve/sieve-implementation.c as reported by Robin Breathe. GCC fails to report these issues. The function involved is currently not used and serves only as an example on how dovecot could support multiple sieve back-ends... This patch still includes (yet another) instance of the CMU Sieve source, as explained in one of my previous e-mails (http://dovecot.org/list/dovecot/2006-July/015016.html) The patch can be downloaded at: http://sinas.rename-it.nl/~sirius/dovecot-1.0.3-MANAGESIEVE-v6.diff.gz The README.managesieve is located in the root of the dovecot source tree after applying the patch. Have fun testing the patch. Don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl IRC: Freenode, #dovecot, S[r]us

3 5

[Dovecot] Migrating from imapd to dovecot - how to keep user's Mail folders
by Patrick - South Valley Internet 17 Aug '07

17 Aug '07

Hi all, We're migrating off our current mail server with runs postfix and imapd on an AIX machine to Postfix and Dovecot running linux. Our customers have a lot of IMAP folders with folders they configured, which are currently located in their /home directory on the current mail server. The new mail server will have them at the same location. How do I configure Dovecot so that when a customer connects via IMAP using their favorite e-mail client, that the folders will be there? Thanks in advance. Patrick

1 0

[Dovecot] Dovecot 1.0.3: LDA + quota plugin
by Przemek Grądzki 17 Aug '07

17 Aug '07

I have problem with quota limit settings for "deliver" - global plugin settings overrides userdb quota setting !!! imap and pop3 works fine. Quota limit for user is set to "quota=maildir:ignore=Kosz:storage=512". And "maildirsize" file in user's mail_location contains "524288S" line - good. But when I set: ---------------- plugin { quota = maildir:ignore=Kosz:storage=102400 } ---------------- in "/etc/dovecot.conf", quota limit is set to "104857600S" in "maildirsize" file - BAD. Local delivery is configured as in http://wiki.dovecot.org/LDA, quota plugin is set in /etc/dovecot.conf: ---------------- protocol lda { ...... mail_plugins = cmusieve quota #mail_plugin_dir = /usr/lib/dovecot/lda ..... } ---------------- Per-user quota is configured like this (from LDAP): ---------------- user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,mailQuotaSize=quota=maildir:ignore=Kosz:storage pass_attrs = uid=user,userPassword=password,homeDirectory=userdb_home,uidNumber=userdb_uid,gidNumber=userdb_gid,mailQuotaSize =userdb_quota=maildir:ignore=Kosz:storage ---------------- "mailQuotaSize" attribute contains quota limit in kilobytes. /etc/dovecot.conf: ---------------------------- # 1.0.3: /etc/dovecot.conf log_path: /dev/stderr protocols: imap imaps pop3s managesieve login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_executable(managesieve): /usr/libexec/dovecot/managesieve-login first_valid_uid: 8 first_valid_gid: 12 mail_location: maildir:%h/Maildir mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_executable(managesieve): /usr/libexec/dovecot/managesieve mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/managesieve pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): auth default: mechanisms: plain login gssapi passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: prefetch userdb: driver: ldap args: /etc/dovecot-ldap.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 438 plugin: quota: maildir:ignore=Kosz:storage=102400 ----------------- PS. Sorry for my english.

1 0

[Dovecot] High CPU utilization on Solaris 10
by Jon Alessandrello 17 Aug '07

17 Aug '07

I've read similar post about such an issue, but have not seen any posted solutions. I have a clean install of Solaris 10 running a Sunfire v440 w/postfix. I am using dovecote solely for SMTP authentication, and it is working just fine except while running top I constantly see: 548 root 1 30 0 5240K 3416K run 522:51 49.45% dovecot-auth The process never crashes, nor are there any errors. I ran a test devel box with an almost identical setup of postfix and dovecot on Solaris 9 (V240) and the functionality is identical, but with no high CPU usage. The following are my configs and system info: dovecot --version 1.0.3 OS Solaris 10 Sparc (Patched) No NFS all local ufs dovecot -n # 1.0.3: /usr/local/etc/dovecot.conf log_path: /var/log/dovecot protocols: none ssl_disable: yes login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login auth default: mechanisms: plain login passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf socket: type: listen client: path: /opt/pmx/postfix/var/private/auth mode: 432 user: postfix group: postfix cat dovecot-ldap.conf: hosts = localhost dn = cn=priv-account,ou=container,dc=example,dc=com dnpass = mydnpasswd ldap_version = 3 base = ou=people,dc=example,dc=com scope = subtree pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = CRYPT Any help would be great!! -Jon

5 6

[Dovecot] dovecot notifying a database about total number of messages.
by Erland Nylend 17 Aug '07

17 Aug '07

Hello, in addition to our mail system, we have some other systems which needs to know how many messages, and how many unread messages, a user has in his/her inbox (maildir). Currently, we have a mod_perl script which takes a mail address as input, and then traverses the maildir, and outputs the number of unread messages. Our challenge is that the maildirs are located on a SAN, and traversing a maildir is slow. We currently have more than 100 requests pr. second, which we handle with caching, and spreading the load across different servers. I'm looking into the possibility of either using dovecots index files, or having dovecot update a database with total number of messages/number of unread messages. Question: 1) if I'm using perl, is there any way I can read in the information in the index files? Is the data formatted in some standarized way, so that I can parse it, or use a module which read in the data? (if I can read the indexes in wrapper scripts to imap/pop/deliver, then I could probably update a database with the information) 2) how would you proceed, if the aim is to end up with dovecot notifying a database regarding the number of messages, and unread messages? -- Erland Nylend

2 1

[Dovecot] ssh tunneling and maildir
by Joel Becker 17 Aug '07

17 Aug '07

Hello everyone, please keep my CC'd, I'm not on the list. I've been using dovecot happily via an ssh tunnel. My mutt is configured to use IMAP, and the tunnel is as follows in my muttrc: set tunnel="ssh -q mymailhost 'MBOX_LOCKS=fcntl MAIL=/home/jlbec/mail /usr/libexec/dovecot/imap'" It should be pretty obvious that this logs into mymailhost as me (via SSH keyauth) and runs /usr/libexec/dovecot/imap directly as a foreground process. Setting MAIL, it points dovecot imap to my mbox folders. dovecot imap speaks imap over stdin/out, this goes over the ssh to mutt. It works great. Really great. I don't need root access at all, the server isn't running dovecot globally, and I get IMAP through firewalls if I can ssh through a firewall/vpn. I'm using mbox and fcntl, so my MTA has no trouble working in concert. However, this doesn't appear to be documented anywhere. A friend showed it to me, and I don't even remember who that was. I'm now considering changing to maildir folders. I figure dovecot imap might figure out a folder is maildir when stat says S_IFDIR, but without documentation, I can't figure out how to tell dovecot imap to use maildir when I create a folder. I'm also unsure how this will interact with my MTA. For the latter, I'm thinking I just need to configure my MTA to use dovecot's deliver program. For the former, is there some magic environment variable I need to add to my tunnel command line? Thanks Joel -- "The first requisite of a good citizen in this republic of ours is that he shall be able and willing to pull his weight." - Theodore Roosevelt http://www.jlbec.org/ jlbec(a)evilplan.org

4 8

[Dovecot] Recover mailboxes
by Jordi Espasa Clofent 17 Aug '07

17 Aug '07

HI all, Some time ago I've user(a)domain.com in maildir mailbox with their own mails, their folders, subfolders, indexes files.. etc My server was missconfigured and I've rebuilded all SMTP; I've recreated all the mailboxes with same names that before. Of course, the problem is the content of these mailboxes it's not the same. So, the idea is: add all the contento from user(a)domain.com (old) mailbox to user(a)domain.com (new) mailbox. because I have got a complete copy of (old) mailboxes and their content. ¿How can I do it?

1 0

[Dovecot] High CPU utilization on Solaris 10
by Jon Alessandrello 17 Aug '07

17 Aug '07

Some people had this problem when giving some superoptimization flags with Sun Studio. Did you do that? -Timo No I did not use any optimization. And Dave, I took what you said and just tried both dovecot-1.0.2 dovecot-1.0.rc29 and have the same exact results :(

3 2

[Dovecot] index and control files not being created
by Luis Pablo Michelena Scaffo 16 Aug '07

16 Aug '07

Hello, I'm configurating dovecot 1.0.3 on debian etch. While trying to set public folders, y decided to have the index and control files on the users homes. those homes are mounted by nfs, with disabled access to root. In that scenario, I'm getting the errors i transcribe next: Aug 16 11:21:17 server dovecot: IMAP(user): fchown(/home/user/Maildir/shared-settings/control/.folder/dovecot-uidlis t) failed: Operation not permitted Aug 16 11:21:17 server dovecot: IMAP(user): fchown(/home/user/Maildir/shared-settings/control/.folder/dovecot-uidlis t) failed: Operation not permitted Aug 16 11:21:17 server dovecot: IMAP(user): rename(/inbox/shared/.folder/cur/mailfile, /inbox/shared/.folder/cur/mailfile :2,S) failed: Operation not permitted Aug 16 11:21:17 server dovecot: IMAP(user): fchown(/home/user/Maildir/shared-settings/control/.folder/dovecot-uidlis t) failed: Operation not permitted Aug 16 11:21:17 server dovecot: IMAP(user): rename(/inbox/shared/.folder/cur/mailfile, /inbox/shared/.folder/cur/mailfile :2,S) failed: Operation not permitted Aug 16 11:21:26 server dovecot: IMAP(user): Disconnected: Logged out Aug 16 11:21:27 server dovecot: IMAP(user): fchown(/home/user/Maildir/shared-settings/control/.folder/dovecot-uidlis t) failed: Operation not permitted Aug 16 11:21:27 server dovecot: IMAP(user): rename(/inbox/shared/.folder/cur/mailfile, /inbox/shared/.folder/cur/mailfile :2,S) failed: Operation not permitted Then I touched those files and the errors faded away. Beside that, I was testing the setup, and while trying to delete some files on the shared folder, I got another error: Aug 16 16:38:04 server dovecot: IMAP(user): rename(/inbox/shared/.folder/cur/1183976419.755_0.server:2,Sa, /inbox/shared/.folder/cur/1183976419.755_0.server:2,STa) failed: Operation not permitted Aug 16 16:38:11 server dovecot: IMAP(user): fchown(/home/user/Maildir/shared-settings/control/.folder/dovecot-uidlist) failed: Operation not permitted Aug 16 16:38:11 server dovecot: IMAP(user): rename(/inbox/shared/.folder/cur/1183976419.755_0.server:2,Sa, /inbox/shared/.folder/cur/1183976419.755_0.server:2,STa) failed: Operation not permitted Which seems odd, because I though that as a flag, the deleted flag should be marked on the index files and not directly on the shared folder (where the user hasn't any permission other than reading), ant the same goes to the "read" flag Am I wrong? Is there any workaround to make dovecot behave the way I'd liked? The config follows: login_executable: /usr/lib/dovecot/imap-login mail_extra_groups: mail mail_location: maildir:/home/%u/Maildir:INBOX=/inbox/mdir/%u mmap_disable: yes namespace: type: private separator: / location: maildir:~/Maildir:INBOX=/inbox/mdir/%u inbox: yes namespace: type: public separator: / prefix: Shared folders/ location: maildir:/inbox/shared:INDEX=/home/%u/Maildir/shared-settings/index:CONTROL=/home/%u/Maildir/shared-settings/control auth default: passdb: driver: passwd args: blocking=yes passdb: driver: shadow userdb: driver: passwd Cheers, Luis

1 0

[Dovecot] ANY password option
by Master Abi 16 Aug '07

16 Aug '07

Hi We sometimes migrate mailboxes over to one of our mail servers which has a very handy feature called 'ANY password'. This will allow access to a mailbox using the given username and disregard checking for the password. This is a useful feature for many reasons. Is there a possibility Dovecot could have such a a feature or is there a workaround already. Thanks Master

3 3

Re: [Dovecot] use of deliver from procmail advisable?
by Jerry Yeager 16 Aug '07

16 Aug '07

On Aug 15, 2007, at 5:00 AM, dovecot-request(a)dovecot.org wrote: > Message: 7 > Date: Wed, 15 Aug 2007 00:58:40 +0200 > From: martin f krafft <madduck(a)madduck.net> > Subject: Re: [Dovecot] use of deliver from procmail advisable? > To: dovecot(a)dovecot.org > Message-ID: <20070814225840.GA23721(a)piper.oerlikon.madduck.net> > Content-Type: text/plain; charset="us-ascii" > > also sprach Charles Marcus <CMarcus(a)Media-Brokers.com> > [2007.08.14.2028 +0200]: >>> Well, the whole point of sieve, I believe, is to make it >>> something that an >>> admin would want to let arbitrary users modify on their own >>> recognizance, >>> and the ability to specify arbitrary programs to run would be >>> just *asking* >>> to be hacked. >> >> Wouldn't a decent, secure alternative to procmail be sieve+amavisd- >> new? > > Except it's not really possible to make amavisd-new do per-user spam > filtering. And it's even more of a performance hog. > > -- > martin; (greetings from the heart of the sun.) > \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck > > "all language designers are arrogant. goes with the territory..." > -- larry wall > > spamtraps: madduck.bogus(a)madduck.net >

3 2

[Dovecot] Moving a mail between folders and post-processing ?
by Jerry Nicholls 16 Aug '07

16 Aug '07

Hi, Within Dovecot is there a way of spotting a change to a folder and running a post-processing script on the email that was moved ? I'm specifically after a way of seeing either an email entering or leaving a folder - preferably running a different post-process script depending on the direction. Essentially if an email enters or is moved out of a 'spam' folder I'd like to mark it as 'spam'/'ham' in the Bayesian filters respectively. Is there any such mechanism, or should I start looking at how to write a plugin to achieve this ? If it's the plugin route is there any good documentation on the plugin APIs etc ? Thanks, Jerry. -- Jerry Nicholls E: Jerry.Nicholls(a)zeninternet.co.uk Core Systems & Networks Manager W: http://www.zen.co.uk/ Zen Internet Ltd. T: 0845 058 9000 F: 0845 058 9005

3 2

Re: [Dovecot] deliver assertion failure
by Jerry Yeager 16 Aug '07

16 Aug '07

On Aug 15, 2007, at 5:00 PM, dovecot-request(a)dovecot.org wrote: > > > Message: 7 > Date: Thu, 16 Aug 2007 08:59:25 +1200 > From: Jasper Bryant-Greene <jbg(a)indy.net.nz> > Subject: [Dovecot] deliver assertion failure > To: dovecot(a)dovecot.org > Message-ID: <20070815205925.GA2808(a)port1.indy.net.nz> > Content-Type: text/plain; charset=us-ascii > > Deliver from latest 1.1 HG with sieve also from latest 1.1 HG is dying > with an assertion failure when it delivers to my mailbox. Other > mailboxes on the same system are unaffected, but I can read my mailbox > fine through IMAP. > > Dovecot and sieve were compiled with -march=nocona -pipe -ggdb > > I've commented out my entire sieve script and the problem still > occurs. > > file index-mail-headers.c: line 590 (index_mail_get_raw_headers): > assertion failed: (ret != -1) > - Last output repeated twice - > > Raw backtrace: > /usr/libexec/dovecot/deliver(i_syslog_panic_handler+0x2b) > [0x493125] > -> /usr/libexec/dovecot/deliver(i_fatal+0) [0x492b17] > -> /usr/libexec/dovecot/deliver [0x44f7cf] > -> /usr/libexec/dovecot/deliver(index_mail_get_first_header+0x30) > [0x44fb9b] > -> /usr/libexec/dovecot/deliver(mail_get_first_header+0x3a) > [0x47ca3d] > -> /usr/libexec/dovecot/deliver(deliver_get_return_address+0x21) > [0x41453b] > -> /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so(cmu_sieve_run > +0x14b) [0x2b3687f194a1] > -> /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so [0x2b3687f169ba] > -> /usr/libexec/dovecot/deliver(main+0x8dc) [0x415c4d] > -> /lib/libc.so.6(__libc_start_main+0xe3) [0x2b3687cf6533] > -> /usr/libexec/dovecot/deliver [0x4137a9] > > Jasper > > > ------------------------------ > > _______________________________________________ > dovecot mailing list > dovecot(a)dovecot.org > http://dovecot.org/cgi-bin/mailman/listinfo/dovecot > > End of dovecot Digest, Vol 52, Issue 56 > *************************************** I am getting the same error, the mail is still being delivered, but the system is generating an error message sent to the original sender The mail system <EMAIL ADDRESS HIDDEN>: Command died with signal 11: "/usr/local/libexec/dovecot/deliver" Reporting-MTA: dns; HIDDEN X-Postfix-Queue-ID: 7F344239D31 X-Postfix-Sender: rfc822; EMAIL ADDRESS HIDDEN Arrival-Date: Wed, 15 Aug 2007 15:53:32 -0400 (EDT) Final-Recipient: rfc822; EMAIL ADDRESS HIDDEN Action: failed Status: 5.3.0 Diagnostic-Code: x-unix; internal software error the mail logs show: to=<EMAIL ADDRESS HIDDEN>, relay=dovecot, delay=1.5, delays=0.01/0.02/0/1.5, dsn=5.3.0, status=bounced (Command died with signal 11: "/usr/local/libexec/dovecot/deliver") This did not happenr in v1.1 alpha 2, but is now appearing in 1.1 alpha 1.3 after a day or so of using the new version. Jerry Yeager

1 0

Re: [Dovecot] use of deliver from procmail advisable?
by Jerry Yeager 16 Aug '07

16 Aug '07

On Aug 15, 2007, at 5:00 PM, dovecot-request(a)dovecot.org wrote: > ------------------------------ > > Message: 3 > Date: Wed, 15 Aug 2007 18:08:58 +0200 > From: martin f krafft <madduck(a)madduck.net> > Subject: Re: [Dovecot] use of deliver from procmail advisable? > To: dovecot(a)dovecot.org > Message-ID: <20070815160858.GA22429(a)piper.oerlikon.madduck.net> > Content-Type: text/plain; charset="utf-8" > > also sprach Jerry Yeager <jerry(a)scene-naturally.dyndns.org> > [2007.08.15.1758 +0200]: >> a) Postfix milter to run ClamAv, eh something like this (for Linux >> fans) >> b) then use the regular Postfix <--> SpamAssassin <--> LDA (with >> sieve) >> setup (message routing via Postfix master.cf) so that individual >> users can >> set their own SA rules and vacation stuff. > > This is exactly how I used to have it but then the need for > a vacation autoresponse to the From: address (as opposed to > Return-Path) arose and I had to switch to procmail: > > http://dovecot.org/list/dovecot/2007-August/024766.html > > Before that, I was using spamc with --pipe-to, but always had a bad > feeling about that, since the manpage says: > > Note that there is a very slight chance mail will be lost here, > because if the fork-and-exec fails there?s no place to put the > mail message. > > and my message to SA-users on this was never answered[0]. > > 0. http://marc.info/?l=spamassassin-users&m=115185095923772&w=2 > > Now I am using procmail and at least now that failure will cause > postfix to defer a message. > > -- > martin; (greetings from the heart of the sun.) > \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck > > half a bee, philosophically, must ipso facto half not be. > but half the bee has got to be, vis-a-vis its entity. you see? > but can a bee be said to be or not to be an entire bee, > when half the bee is not a bee, due to some ancient injury? > -- monty python > > spamtraps: madduck.bogus(a)madduck.net >

1 0

[Dovecot] Errors from dovecot 1.1
by wenjie zheng 15 Aug '07

15 Aug '07

I downloaded and installed dovecot 1.1 nightly build yesterday. Here is a the errors I collected from the log file. dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=24 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 2 dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=52 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 2 dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=80 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension record updated without intro prefix dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=416 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 0 dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=444 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension header update without intro prefix dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=528 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 0 dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=556 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension header update without intro prefix dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=776 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 2 dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=804 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 3 dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=832 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 2 dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=876 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 3 dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Sending log messages too fast, throttling.. dovecot: Aug 15 14:19:29 Error: child 8898 (imap) killed with signal 6 dovecot: Aug 15 14:19:29 Info: IMAP(use@doamin): Disconnected: Logged out bytes=36/238 dovecot: Aug 15 14:19:30 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=920 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 2 dovecot: Aug 15 14:19:30 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=948 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 2 dovecot: Aug 15 14:19:30 Error: IMAP(use@doamin): file mail-index-sync-keywords.c: line 285 (mail_index_sync_keywords): assertion failed: (rec->modify_type == MODIFY_REMOVE) dovecot: Aug 15 14:19:30 Error: IMAP(use@doamin): Raw backtrace: imap [0x80badb6] -> imap [0x80ba903] -> imap(mail_index_sync_keywords+0xee) [0x80ac3e6] -> imap(mail_index_sync_record+0x393) [0x80a0437] -> imap(mail_index_sync_map+0x208) [0x80a075c] -> imap(mail_index_map+0x89) [0x809b059] -> imap [0x8098907] -> imap [0x8098b39] -> imap(mail_index_open+0x133) [0x8098c73] -> imap(index_storage_mailbox_open+0x75) [0x8092e71] -> imap [0x806de18] -> imap [0x806dfb6] -> /usr/lib/dovecot/imap/lib10_quota_plugin.so [0x119de8] -> imap(mailbox_open+0x50) [0x80ae1ec] -> imap(_cmd_select_full+0x76) [0x805da4e] -> imap(cmd_select+0x10) [0x805dcbc] -> imap [0x805fa22] -> imap [0x805f941] -> imap [0x805fab1] -> imap(_client_input+0x56) [0x805fb6e] -> imap(io_loop_handler_run+0x100) [0x80bff0c] -> imap(io_loop_run+0x2d) [0x8066b21] -> imap(main+0x64) [0x8066518] -> /lib/tls/libc.so.6(__libc_start_main+0xda) [0x6db78a] -> imap(__fxstat64+0x71) [0x8059605] Thanks, Wenjie

2 1

[Dovecot] MANAGESIEVE patch v5 for dovecot 1.0.2
by Stephan Bosch 15 Aug '07

15 Aug '07

Hello dovecot users, I have finally updated the MANAGESIEVE patch to fix the currently known small problems with the protocol implementation. Also, I included a proxy implementation based on imap-proxy.c. This patch is designed for dovecot release 1.0.2 and it will not apply cleanly to the 1.1 versions yet. Change Log V5 ------------- - Applied patch by Uldis Pakuls to fix master_dump_settings bug - Added some compilation/installation info to the README - Moved README to source tree's root as README.managesieve - Fixed minor error handling bug in sieve_storage.c with respect to a missing root directory. - Now sieve capabilities are reported as they are specified by the implementing library and not in forced upper case. The sieve RFC now explicitly states that sieve capability identifiers are case-sensitive. This broke compatibility with SquirrelMail/Avelsieve. - Disabled ANONYMOUS login entirely until proper support is implemented. V4 claimed to do so as well, but in fact it only stopped announcing it. - Implemented managesieve-proxy. It is not so much a clean copy of imap-proxy, since the managesieve greeting is much more complex and requires parsing. Configuration is identical to imap-proxy. This seems to be a little under-documented however (http://wiki.dovecot.org/PasswordDatabase/ExtraFields) This patch still includes (yet another) instance of the CMU Sieve source, as explained in one of my previous e-mails (http://dovecot.org/list/dovecot/2006-July/015016.html) Current plans include merging src/lib-managesieve with src/lib-imap, updating the patch for dovecot-1.1 and fixing any problems you might find. The patch can be downloaded at: http://sinas.rename-it.nl/~sirius/dovecot-1.0.2-MANAGESIEVE-v5.diff.gz The README.managesieve is located in the root of the dovecot source tree after applying the patch. Have fun testing the patch. Notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl IRC: Freenode, #dovecot, S[r]us

5 13

[Dovecot] Dovecot deliver + sieve + postfix virtual + mysql ?
by Radek Slavicinsky 15 Aug '07

15 Aug '07

Hey there guys. I have successful postfix + mysql + sagator + clamav + spamassassin + dovecot setup (it was a really crazy month full of tweaking :]) and the only thing i miss is some per maildir specific filtering. i decided to use sieve. everything is fine except that dovecot's deliver process doesn't see the actual .dovecot.sieve file with filtering rules in the root of a maildir. description of the situation follows: from /var/log/dovecot.log: deliver(support{the_at_symbol}support.etnetera.cz): "2007-08-15 13:32:11 "Error: userdb(support{the_at_symbol}support.etnetera.cz) didn't return a home directory or sieve script location, can't find it deliver(support{the_at_symbol}support.etnetera.cz): "2007-08-15 13:32:11 "Info: msgid=<200708151330.22021.radek.slavicinsky{the_at_symbol}etnetera.cz>: saved mail to INBOX /etc/dovecot/dovecot.conf: protocols = imap imaps pop3 pop3s listen = * disable_plaintext_auth = no shutdown_clients = yes log_path = /var/log/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " ssl_cert_file = /etc/certs/sponka.etnetera.cz.crt ssl_key_file = /etc/certs/sponka.etnetera.cz.key ssl_ca_file = /etc/certs/CA.crt login_process_size = 64 login_processes_count = 32 login_max_processes_count = 256 login_max_connections = 512 mail_location = maildir:/srv/vmail/domains/%d/%n/ #mail_location = maildir:/ namespace private { separator = . prefix = INBOX. inbox = yes } namespace private { separator = . prefix = inbox = yes hidden = yes } mail_extra_groups = vmail verbose_proctitle = yes mbox_read_locks = fcntl mbox_write_locks = fcntl protocol imap { } protocol pop3 { pop3_uidl_format = UID%u-%v } protocol lda { hostname = sponka.etnetera.cz postmaster_address = postmaster{the_at_symbol}etnetera.cz auth_socket_path = /var/run/dovecot/auth-master mail_plugins = cmusieve } auth default { mechanisms = plain login digest-md5 cram-md5 passdb sql { args = /etc/dovecot/dovecot-sql.conf } userdb sql { args = /etc/dovecot/dovecot-sql.conf } user = dovecot-auth socket listen { client { path = /var/spool/postfix/private/auth mode = 0666 user = postfix group = postfix } master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail group = vmail } } } dict { } plugin { } /etc/dovecot/dovecot-sql.conf: driver = mysql default_pass_scheme = PLAIN connect = host=127.0.0.1 dbname=postfix user=postfix password=averysecretpass password_query = SELECT password FROM mailbox WHERE username = '%u' AND active = '1' user_query = SELECT maildir, 65500 AS uid, 65500 AS gid FROM mailbox WHERE username = '%u' AND active = '1' the user_query gives: mysql> SELECT maildir, 65500 AS uid, 65500 AS gid FROM mailbox WHERE username = 'radek.slavicinsky(a)etnetera.cz' AND active = '1'; +--------------------------------+-------+-------+ | maildir | uid | gid | +--------------------------------+-------+-------+ | etnetera.cz/radek.slavicinsky/ | 65500 | 65500 | +--------------------------------+-------+-------+ 1 row in set (0.00 sec) the sieve rules file # ls /srv/vmail/domains/support.etnetera.cz/support/.dovecot.sieve -lha -rw-r--r-- 1 vmail vmail 957 Aug 15 13:30 /srv/vmail/domains/support.etnetera.cz/support/.dovecot.sieve i think there should be some specific settings for the cmusieve plugin, but i didnt find much docs about that thx for any help ;] blue4 :p

3 4

[Dovecot] Dovecot on OpenBSD stalls
by Bert Koelewijn 15 Aug '07

15 Aug '07

Hello list, I'm using dovecot 1.0.2 on OpenBSD 4.1. About every month, dovecot will just stall, without any error messages. The processes are still running, the network ports are open, but the login just hangs. The following error message does occur on a very regular basis: Aug 15 00:52:37 mail dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Aug 15 01:08:08 mail dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Aug 15 01:23:38 mail dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Aug 15 01:38:39 mail dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Aug 15 01:54:09 mail dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Aug 15 02:09:10 mail dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Aug 15 02:24:40 mail dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Aug 15 02:39:41 mail dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Aug 15 02:55:12 mail dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server (stalling from here) The LDAP directory is Active Directory and is not used as userdb, only as passdb. Thanks, Bert # 1.0.2: /etc/dovecot.conf base_dir: /var/dovecot/ ssl_cert_file: /etc/ssl/server.pem ssl_key_file: /etc/ssl/private/server.key login_dir: /var/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: _dovecot mail_location: maildir:~/Maildir mbox_write_locks: fcntl imap_client_workarounds: delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep auth default: mechanisms: plain login passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: _postfix group: _postfix /etc/dovecot-ldap.conf hosts = xxx.xxx.xxx.xxx:389 #uris = #dn = #dnpass = #sasl_bind = no #sasl_mech = #sasl_realm = #sasl_authz_id = #tls = no auth_bind = yes auth_bind_userdn = cn=%u,cn=Users,dc=koelewijn,dc=bz #ldap_version = 2 base = dc=bz #deref = never #scope = subtree #user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid #user_filter = (&(objectClass=posixAccount)(uid=%u)) #pass_attrs = uid=user,userPassword=password #pass_attrs = uid=user,userPassword=password,homeDirectory=userdb_home,uidNumber=userdb_uid,gidNumber=userdb_gid #pass_filter = (&(objectClass=posixAccount)(uid=%u)) #default_pass_scheme = CRYPT #user_global_uid = #user_global_gid =

1 0

[Dovecot] Sieve Vacation cause deliver to die
by M1 15 Aug '07

15 Aug '07

When a user enable vacation in sieve deliver die and the mail lost. I am using 1.0.3 Thanks ------------------------------------------------------------------------------------------------------------------------------------------- in syslog postfix/pipe[16060]: 8E33017D4: to=<vivi(a)abc.com.hk>, relay=dovecot, delay=0.17, delays=0.13/0.01/0/0.03, dsn=5.3.0, status=bounced (Command died with signal 11: "/usr/libexec/dovecot/deliver") ------------------------------------------------------------------------------------------------------------------------------------------- .dovecot.sieve # Sieve Filter # Generated by Ingo (http://www.horde.org/ingo/) (August 6, 2007, 9:56 am) require ["vacation", "fileinto"]; # Whitelisted Addresses if address :all :comparator "i;ascii-casemap" :is ["From", "Sender", "Resent-From"] "juscotsushin(a)juscocityhk.com" { keep; stop; } # Vacation if allof ( not exists ["list-help", "list-unsubscribe", "list-subscribe", "list-owner", "list-post", "list-archive", "list-id"], not header :comparator "i;ascii-casemap" :is "Precedence" "list,bulk" ) { vacation :days 7 :addresses "vivi(a)abc.com.hk" :subject "Autoreply : OUT OF OFFICE" "I will not be in Hong Kong from August 6-11. While I will check my mailbox from time to time, I may respond with some delay. Regards, Vivi"; } # Blacklisted Addresses if address :all :comparator "i;ascii-casemap" :is ["From", "Sender", "Resent-From"] ["store-news(a)amazon.com", "uschinaasset(a)aol.com", "janvqvogel(a)bible.org", "info(a)bichk.net", "anmhk(a)biznetvigator.com"] { discard; stop; } # dspam if header :comparator "i;ascii-casemap" :contains "X-DSPAM-Result" "Spam" { fileinto "INBOX.Spam"; } ------------------------------------------------------------------------------------------------------------------------------------------- mail / # dovecot -n # 1.0.3: /etc/dovecot/dovecot.conf protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/dovecot/server.pem ssl_key_file: /etc/ssl/dovecot/server.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login last_valid_uid: 500 first_valid_gid: 500 last_valid_gid: 500 mail_location: maildir:/home/mail/%d/%n mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota dspam mail_plugins(imap): quota imap_quota dspam mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: mechanisms: plain login passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 384 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: quota: maildir trash: /etc/dovecot/dovecot-trash.conf

3 2

[Dovecot] use of deliver from procmail advisable?
by martin f krafft 15 Aug '07

15 Aug '07

Hi list, I understand that dovecot's deliver does a little more than deliver: it also updates the dovecot metadata stored with each Maildir. Thus, if I use deliver as opposed to procmail's internal Maildir delivery, it seems that the IMAP server later has less work to do since the metadata is can use are up to date. Doing this, however, incurs an extra process for each mail delivered. I thus wonder whether the two balance each other out, or whether there is a strong difference. What do you think will be less resource-heavy: calling deliver for every mail received *in addition to* procmail, or letting the IMAP server update the metadata on access? -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck EARTH smog | bricks AIR -- mud -- FIRE soda water | tequila WATER spamtraps: madduck.bogus(a)madduck.net

4 8

[Dovecot] namespaces and creation of folders that contain folders...
by bhayden＠umn.edu 14 Aug '07

14 Aug '07

Hi Timo and all. imap/cmd-create.c contains the following bit of code: len = strlen(full_mailbox); if (len == 0 || full_mailbox[len-1] != ns->sep) directory = FALSE; else { /* name ends with hierarchy separator - client is just informing us that it wants to create children under this mailbox. */ directory = TRUE; mailbox = t_strndup(mailbox, len-1); full_mailbox = t_strndup(full_mailbox, strlen(full_mailbox)-1); i_info("Z CREATE NAME: YYY%sYYY", mailbox); } We've been having trouble with people not being able to create a mail folder that will contain other folders. Tried it both with users using mbox (where this would be a filesystem directory) and maildir. Failed everytime because of a test which rejects folder names that end with MAILDIR_FS_SEP. Looks like the above bit of code is supposed to catch these, make a note of the fact that the client wants a directory, and strip off that trailing separator. In fact, it does this in the case of 'full_mailbox'. However, for 'mailbox' (it seems to me) the code is incorrect as its using the len-1 which is the length of 'full_mailbox', not 'mailbox'. This means that when 'mailbox' and 'full_mailbox' are the same length--that is, for the default namespace (no prefix), it happens to work. However, in any other namespace, it won't, as 'full_mailbox' will always be longer then 'mailbox' if there is a ns prefix, and hence that trailing separator won't be trimmed. (As a matter of fact, in the unlikely instance that the prefix is a single character this will trim the null character from 'mailbox', which probably isn't a good thing.) So. Am I missing something, or crazy, or is this really a bug? Thanks, -Brian

2 2

[Dovecot] about index cache
by Joe Wong 14 Aug '07

14 Aug '07

Hi Timo, Is the dovecot index cache stored only standard header fields (from, to, cc, subject, content-type... )? What happen if there is non standard header, will it be cached? - Joe May the force be with you..

3 9

[Dovecot] Failed to compile dovecot 1.1 nightly build
by wenjie zheng 14 Aug '07

14 Aug '07

I downloaded the 1.1 night build from here: http://hg.dovecot.org/dovecot/archive/tip.tar.gz autogen.sh ./configure (with a long list of options) make I got this error information: ... rpcgen -c /usr/include/rpcsvc/rquota.x | \ -e 's/IXDR_PUT/(void)IXDR_PUT/g' \ -e 's/int32_t \*buf/int32_t *buf __attr_unused__/' > rquota_xdr.c /bin/sh: line 1: -e: command not found make[4]: *** [rquota_xdr.c] Error 127 make[4]: Leaving directory `/var/home/wzheng/code/vendor/src/plugins/quota' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/var/home/wzheng/code/vendor/src/plugins' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/home/wzheng/code/vendor/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/home/wzheng/code/vendor' make: *** [all] Error 2 Am I using the correct nightly build? Thanks, Wenjie

2 1

Re: [Dovecot] dovecot Digest, Vol 52, Issue 52
by Jerry Yeager 14 Aug '07

14 Aug '07

From the digest: On Aug 14, 2007, at 1:04 PM, dovecot-request(a)dovecot.org wrote: other messages cut out… > > > Message: 9 > Date: Tue, 14 Aug 2007 19:03:58 +0200 > From: martin f krafft <madduck(a)madduck.net> > Subject: Re: [Dovecot] use of deliver from procmail advisable? > To: dovecot(a)dovecot.org > Message-ID: <20070814170358.GA17390(a)piper.oerlikon.madduck.net> > Content-Type: text/plain; charset="us-ascii" > > also sprach Kyle Wheeler <kyle-dovecot(a)memoryhole.net> > [2007.08.14.1833 +0200]: >>> I understand that dovecot's deliver does a little more than >>> deliver: >> >> It also understands the 'seive' filter language (an alternative to >> procmail). > > I don't consider it an alternative to procmail because you cannot > pass mail to external programmes, like spamassassin or vacation. > Sure, sieve has its own vacation module, but I find that to be > rather limited. See this thread: > > http://dovecot.org/list/dovecot/2007-August/024686.html > >>> What do you think will be less resource-heavy: calling deliver >>> for every mail received *in addition to* procmail, or letting the >>> IMAP server update the metadata on access? >> >> Unless you're cutting it close to the limit on what your server >> can handle, that's probably the wrong question to ask. A better >> question is: which gives my users better performance? > > Good point. The users, however, as far as I know, all use tools like > offlineimap to synchronise in the background, so it hardly matters. > >> your users aren't paying attention. Dovecot will *seem* snappier >> if you do the indexing work on delivery rather than on access, >> even though it may spend more CPU cycles overall to do so. > > Does anyone have hard facts on how much the server process loses if > it encounters a folder with an index inconsistency? > > -- > martin; (greetings from the heart of the sun.) > \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck > > mulutlitithtrhreeaadededd s siigngnatatuurere > > spamtraps: madduck.bogus(a)madduck.net >

1 0

[Dovecot] status of APPENDUID: returning a UID in response to APPEND
by martin f krafft 14 Aug '07

14 Aug '07

# dovecot-related content below, this one for debian bug tracking # system: retitle 435959 Please support RFC4315 UIDPLUS extension in APPEND reply severity 435959 wishlist thanks [please keep 435959(a)bugs.debian.org on Cc.] Hi there, I am working on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435959, which is a performance problem that offlineimap has on large mailboxes. We think that a simple patch to dovecot could cure this problem. I am willing to write the patch but would really like to get your opinion first. In order to keep track of which IMAP message is stored in which local file, offlineimap uses the message UID, which is guaranteed to be unique in the directory, but constant across sessions. When uploading a new message to the IMAP server with APPEND, offlineimap then has to run a SEARCH to obtain said UID for the message it just uploaded. This takes ages on larger mailboxes, as the way offlineimap identifies the message is via a header that's not indexed by dovecot. The solution I found in RFC4315 ("UIDPLUS"; http://www1.tools.ietf.org/html/rfc4315) and then I saw http://www.dovecot.org/list/dovecot/2004-July/003993.html, and now I am wondering: is anyone else interested in APPENDUID? What's the status of an implementation, if any? Newer Courier IMAP server implementation support UIDPLUS and offlineimap will likely obtain this functionality soon. Cheers, [please keep 435959(a)bugs.debian.org on Cc.] -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck "by accepting this brick through your window, you accept it as is and agree to my disclaimer of all warranties, express or implied, as well as disclaimers of all liability, direct, indirect, consequential or incidental, that may arise from the installation of this brick into your building." -- seen on irc spamtraps: madduck.bogus(a)madduck.net

4 3

[Dovecot] dovecot-1.1 + dovecot-sieve-1.1 deliver backtraces
by Sergey 14 Aug '07

14 Aug '07

Hi, I am trying dovecot-1.1 with dovecot-sieve-1.1. First, dovecot -n do not report about deliver settings. They are: --- protocol lda { postmaster_address = postmaster(a)parkheights.dyndns.org hostname = parkheights.dyndns.org mail_plugins = cmusieve mail_plugin_dir = /usr/lib64/dovecot11/modules/lda sendmail_path = /usr/lib/sendmail auth_socket_path = /var/run/dovecot11/auth-master } --- Then, $ sudo /usr/sbin/dovecot11 -n # 1.1.alpha1: /etc/dovecot11/dovecot11.conf base_dir: /var/run/dovecot11/ log_path: /tmp/dovecot11.log info_log_path: /tmp/dovecot11.debug 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/ssl/parkheights.cert ssl_key_file: /etc/ssl/parkheights.key login_dir: /var/run/dovecot11/login login_executable(default): /usr/lib64/dovecot11/imap-login login_executable(imap): /usr/lib64/dovecot11/imap-login login_executable(pop3): /usr/lib64/dovecot11/pop3-login mail_extra_groups: mail mail_location: maildir:/var/spool/imap/%n/.imap mail_debug: yes mail_executable(default): /usr/lib64/dovecot11/imap mail_executable(imap): /usr/lib64/dovecot11/imap mail_executable(pop3): /usr/lib64/dovecot11/pop3 mail_plugin_dir(default): /usr/lib64/dovecot11/modules/imap mail_plugin_dir(imap): /usr/lib64/dovecot11/modules/imap mail_plugin_dir(pop3): /usr/lib64/dovecot11/modules/pop3 auth default: debug: yes debug_passwords: yes passdb: driver: passwd-file args: /etc/dovecot/dovecot.passwd userdb: driver: static args: uid=1927 gid=1927 home=/var/spool/imap/%n userdb: driver: passwd-file args: /etc/dovecot/dovecot.passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot11/auth-master mode: 384 user: vmail group: vmail --- Couple of backtraces from /tmp/dovecot11.log are here. I will try to attach them as a textfile to this message, so that lines will not be wrapped, but I'm not sure that attachements are not stripped. So, please excuse me for duplication in this case. --- dovecot: Jul 25 01:05:19 Error: IMAP(seriv): Corrupted index cache file /var/spool/imap/seriv/.imap/.community-lists-altlinux-org/dovecot.index.cache: Corrupted cach ed message_part data (physical_pos less than expected) deliver(seriv): Jul 25 04:17:26 Panic: seq = 1587, rec->uid = 0, first_new_seq = 1587, records = 1586 deliver(seriv): Jul 25 04:17:26 Error: Raw backtrace: /usr/lib64/dovecot11/deliver [0x46e045] -> /usr/lib64/dovecot11/deliver [0x46dd2c] -> /usr/lib64/dovecot11/deli ver [0x44de1e] -> /usr/lib64/dovecot11/deliver [0x44e687] -> /usr/lib64/dovecot11/deliver(index_transaction_finish_commit+0x28) [0x444488] -> /usr/lib64/dovecot11/de liver [0x41f53f] -> /usr/lib64/dovecot11/deliver(index_transaction_commit+0x38) [0x4442f8] -> /usr/lib64/dovecot11/deliver(mailbox_transaction_commit+0x11) [0x45f221 ] -> /usr/lib64/dovecot11/deliver(deliver_save+0x107) [0x414267] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so [0x2aaaab20987b] -> /usr/lib64/dovecot1 1/modules/lda/lib90_cmusieve_plugin.so(sieve_execute_bytecode+0x6b8) [0x2aaaab219dc8] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x30 b) [0x2aaaab20a35b] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so [0x2aaaab208806] -> /usr/lib64/dovecot11/deliver(main+0xc4e) [0x41505e] -> /lib64/li bc.so.6(__libc_start_main+0xf4) [0x2aaaaaee5c14] -> /usr/lib64/dovecot11/deliver [0x413739] deliver(seriv): Jul 25 04:17:26 Panic: seq = 1587, rec->uid = 0, first_new_seq = 1587, records = 1586 deliver(seriv): Jul 25 04:17:26 Error: Raw backtrace: /usr/lib64/dovecot11/deliver [0x46e045] -> /usr/lib64/dovecot11/deliver [0x46dd2c] -> /usr/lib64/dovecot11/deli ver [0x44de1e] -> /usr/lib64/dovecot11/deliver [0x44e687] -> /usr/lib64/dovecot11/deliver(index_transaction_finish_commit+0x28) [0x444488] -> /usr/lib64/dovecot11/de liver [0x41f53f] -> /usr/lib64/dovecot11/deliver(index_transaction_commit+0x38) [0x4442f8] -> /usr/lib64/dovecot11/deliver(mailbox_transaction_commit+0x11) [0x45f221 ] -> /usr/lib64/dovecot11/deliver(deliver_save+0x107) [0x414267] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so [0x2aaaab20987b] -> /usr/lib64/dovecot1 1/modules/lda/lib90_cmusieve_plugin.so(sieve_execute_bytecode+0x6b8) [0x2aaaab219dc8] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x30 b) [0x2aaaab20a35b] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so [0x2aaaab208806] -> /usr/lib64/dovecot11/deliver(main+0xc4e) [0x41505e] -> /lib64/li bc.so.6(__libc_start_main+0xf4) [0x2aaaaaee5c14] -> /usr/lib64/dovecot11/deliver [0x413739] dovecot: Jul 25 06:52:21 Error: IMAP(seriv): Corrupted index cache file /var/spool/imap/seriv/.imap/.sisyphus-lists-altlinux-org/dovecot.index.cache: Corrupted cache d message_part data (physical_pos less than expected) --- -- With best regards, Sergey. dovecot: Jul 25 01:05:19 Error: IMAP(seriv): Corrupted index cache file /var/spool/imap/seriv/.imap/.community-lists-altlinux-org/dovecot.index.cache: Corrupted cach ed message_part data (physical_pos less than expected) deliver(seriv): Jul 25 04:17:26 Panic: seq = 1587, rec->uid = 0, first_new_seq = 1587, records = 1586 deliver(seriv): Jul 25 04:17:26 Error: Raw backtrace: /usr/lib64/dovecot11/deliver [0x46e045] -> /usr/lib64/dovecot11/deliver [0x46dd2c] -> /usr/lib64/dovecot11/deli ver [0x44de1e] -> /usr/lib64/dovecot11/deliver [0x44e687] -> /usr/lib64/dovecot11/deliver(index_transaction_finish_commit+0x28) [0x444488] -> /usr/lib64/dovecot11/de liver [0x41f53f] -> /usr/lib64/dovecot11/deliver(index_transaction_commit+0x38) [0x4442f8] -> /usr/lib64/dovecot11/deliver(mailbox_transaction_commit+0x11) [0x45f221 ] -> /usr/lib64/dovecot11/deliver(deliver_save+0x107) [0x414267] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so [0x2aaaab20987b] -> /usr/lib64/dovecot1 1/modules/lda/lib90_cmusieve_plugin.so(sieve_execute_bytecode+0x6b8) [0x2aaaab219dc8] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x30 b) [0x2aaaab20a35b] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so [0x2aaaab208806] -> /usr/lib64/dovecot11/deliver(main+0xc4e) [0x41505e] -> /lib64/li bc.so.6(__libc_start_main+0xf4) [0x2aaaaaee5c14] -> /usr/lib64/dovecot11/deliver [0x413739] deliver(seriv): Jul 25 04:17:26 Panic: seq = 1587, rec->uid = 0, first_new_seq = 1587, records = 1586 deliver(seriv): Jul 25 04:17:26 Error: Raw backtrace: /usr/lib64/dovecot11/deliver [0x46e045] -> /usr/lib64/dovecot11/deliver [0x46dd2c] -> /usr/lib64/dovecot11/deli ver [0x44de1e] -> /usr/lib64/dovecot11/deliver [0x44e687] -> /usr/lib64/dovecot11/deliver(index_transaction_finish_commit+0x28) [0x444488] -> /usr/lib64/dovecot11/de liver [0x41f53f] -> /usr/lib64/dovecot11/deliver(index_transaction_commit+0x38) [0x4442f8] -> /usr/lib64/dovecot11/deliver(mailbox_transaction_commit+0x11) [0x45f221 ] -> /usr/lib64/dovecot11/deliver(deliver_save+0x107) [0x414267] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so [0x2aaaab20987b] -> /usr/lib64/dovecot1 1/modules/lda/lib90_cmusieve_plugin.so(sieve_execute_bytecode+0x6b8) [0x2aaaab219dc8] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x30 b) [0x2aaaab20a35b] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so [0x2aaaab208806] -> /usr/lib64/dovecot11/deliver(main+0xc4e) [0x41505e] -> /lib64/li bc.so.6(__libc_start_main+0xf4) [0x2aaaaaee5c14] -> /usr/lib64/dovecot11/deliver [0x413739] dovecot: Jul 25 06:52:21 Error: IMAP(seriv): Corrupted index cache file /var/spool/imap/seriv/.imap/.sisyphus-lists-altlinux-org/dovecot.index.cache: Corrupted cache d message_part data (physical_pos less than expected)

2 5

[Dovecot] v1.1.alpha3 released
by Timo Sirainen 13 Aug '07

13 Aug '07

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha3.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha3.tar.gz.sig All kinds of fixes and API changes. Previous alphas had some problems with index handling, now I didn't get any errors after almost 24h of stress testing. As a new feature userdb passwd now supports overriding some fields with templates. http://wiki.dovecot.org/AuthDatabase/Passwd

3 4

[Dovecot] logging dovecot-sieve vacation responses
by pod 13 Aug '07

13 Aug '07

I attach a patch that adds some informational logging for the vacation outcome in a similar style as the 'notify', 'redirect' and 'reject' cases. I considered adding logging for the not-willing-to-respond case since I think that would greatly assist testing/debugging vacation responses, but couldn't see where to put it that wasn't in the CMU code.

1 0

[Dovecot] plain authentication
by Roger D. Vargas 13 Aug '07

13 Aug '07

After upgrading my server I have found that Im not able to use plain auth for clients conecting from outside server. localhost clients (pine, webmail) works fine, but if I use Thunderbird I got an error saying that server requires TLS or SSL. But if I enable TLS or SSL I got more errors. I have tried sevral combinations, but havent found a working one. Here is my config, can somebody see what Im doing wrong? # /etc/dovecot/dovecot.conf protocols: imap pop3 ssl_disable: yes ssl_cert_file: /etc/ssl/dovecot/server.pem ssl_key_file: /etc/ssl/dovecot/server.key login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no mail_extra_groups: mail mail_location: mbox:~/mail/:INBOX=/var/spool/mail/%u mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: passdb: driver: shadow userdb: driver: passwd -- Roger D. Vargas http://dsgp.blogspot.com

1 0

[Dovecot] "pipe" plugin
by Nicolas Boullis 13 Aug '07

13 Aug '07

Hi, Long ago (more than 2 month ago), I told about a "pipe" plugin I had written to perform some spam/ham learning (see the attached message). I'm now proud to say that I can make it available for use by anyone. You can get it from http://nicolas.boullis.free.fr/pipe.tar.gz Note that this is a temporary location. If someone had a good place to host it, feel free to do (and tell). I think it would be great if the feature could be merged into dovecot. I don't care whether my plugin is used or a rewrite is performed... Cheers, Nicolas

2 2

[Dovecot] Inbox re-initialized
by Joshua, C.S. Chen 13 Aug '07

13 Aug '07

Hi folks, I just replaced my mail server's UW-imap with dovecot yesterday. I use the following folder setting default_mail_env = mbox:/asiaa/home/%u/:/asiaa/home/%u/mail/:INBOX=/var/mail/%u:INDEX=/asiaa/home/%u/mail/dovecot_indexes This is a Scientific linux 4.2 with dovecot 0.99.11-2 . Now today the server loading is highly reduced because of the pop3 session impact is low. But users have the following problems: For outlook express users, when they come in the office, the first time they launch outlook express, they found that the previous Inbox is re-transmitted. So they got double the number of all past e-mails (they setup OE setting to keep a copy on the server). And some users also use pine. After the pine session, they get another whole copy of the past e-mails (so some users got 3X or even 4X the past e-mails). Am I missing something for the dovecot.conf setting, here is the entire configurations: Thanks in advance protocols = pop3 pop3s imap_listen = [::] pop3_listen = [::] log_path = /var/log/dovecot login_dir = /var/run/dovecot-login login = imap login = pop3 default_mail_env = mbox:/asiaa/home/%u/:/asiaa/home/%u/mail/:INBOX=/var/m ail/%u:INDEX=/asiaa/home/%u/mail/dovecot_indexes mbox_locks = fcntl auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root Cheers Joshua

5 5

[Dovecot] using complete email address as username
by WJCarpenter 13 Aug '07

13 Aug '07

I've been poking around the dovecot wiki, and this idea looks plausible. I'm just double-checking with the assembled experts to see if there is some "gotcha" that will happen to me down the road. I have in mind a deployment of dovecot which will use serve several unrelated domains. My plan is to use the complete email address of the users as the unique userid. So, for example, a user with email address <foo(a)example.COM> is unrelated to a user with email address <foo(a)example.NET>. The "home" directories of such users will look something like: /some/path/foo(a)example.com/ /some/path/foo(a)example.net/ I do also plan to use ACLs for some things, so there could be ACL entries of the form: user:foo@example.com ... I will probably be using the quota plugin for individual users right away and group quotas later when that's officially available. So, is all this likely to work or will it collapse in a miasma of unmet expectations? Thanks in advance for any comments!

3 2

[Dovecot] Deleting deleted eMails
by Michael Weisgerber 11 Aug '07

11 Aug '07

Hello 2gether, I am using Dovecot 1.0.rc15 together with Outlook (I apologize) via IMAPS. Now I discovered, that all the old eMails, I marked for deleting, are still there, even the veeery old ones. Dovecot is marking the eMails (I am using maildir configuration) files with an "ST" extension. Is there any switch to turn on garbage collection and maybe a screw to tune the duration until deletion? Thanks for your help! Michael Weisgerber

5 5

[Dovecot] Dovecot shared mailbox folder problem
by Steffen Kaiser 10 Aug '07

10 Aug '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I've set up a namespace to share some mailboxes. When I try to select them, I get an internal error: Client-server chat: * OK Dovecot ready. 1 login dvtest2 x 1 OK Logged in. 2 list "" * * LIST (\HasNoChildren) "." "Trash" * LIST (\HasChildren) "." "test" * LIST (\HasNoChildren) "." "INBOX" * LIST (\HasNoChildren) "." "test.test2" * LIST (\Noselect \HasChildren) "." "Shared" * LIST (\HasNoChildren) "." "Shared.testAccess" * LIST (\HasNoChildren) "." "Shared.testNOaccess" 2 OK List completed. 3 select "Shared.testAccess" 3 NO Internal error occurred. Refer to server log for more information. [2007-07-04 16:45:31] dovecot: Jul 04 16:45:31 Error: IMAP(dvtest2) [3512]: stat(/mnt/mailcache/shared/.testAccess/cur) failed: Permission denied # l /mnt/mailcache/shared/.testAccess -n total 24 drwxrws--- 5 31045 30005 4096 2007-07-04 15:53 ./ drwxr-xr-x 6 0 0 4096 2007-07-04 16:08 ../ drwxrwsr-x 2 31045 30005 4096 2007-06-21 12:19 cur/ - -rw-r--r-- 1 31045 30005 17 2007-07-04 15:38 dovecot-acl - -rw-rw---- 1 31045 30005 0 2007-07-04 15:53 dovecot-shared drwxrws--- 2 31045 30005 4096 2007-06-21 13:57 new/ drwxrws--- 2 31045 30005 4096 2007-06-21 13:57 tmp/ I added chmod o+rx for testing purpose, just in case. stracing the situation results in: gettimeofday({1183560101, 339756}, {4294967176, 0}) = 0 read(0, "3 select \"Shared.testAccess\"\r\n", 3978) = 30 setsockopt(1, SOL_TCP, TCP_CORK, [1], 4) = 0 stat64("/mnt/mailcache/shared/.testAccess", {st_mode=S_IFDIR|S_ISGID|0770, st_size=4096, ...}) = 0 stat64("/mnt/mailcache/shared/.testAccess/cur", 0xbf8cb470) = -1 EACCES (Permission denied) write(2, "\1Estat(/mnt/mailcache/shared/.te"..., 72) = 72 stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=837, ...}) = 0 write(1, "3 NO Internal error occurred. Re"..., 95) = 95 setsockopt(1, SOL_TCP, TCP_CORK, [0], 4) = 0 gettimeofday({1183560101, 341458}, NULL) = 0 What do I wrong? # 1.0.1: /usr/local/dovecot/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/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/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 umask: 7 mail_drop_priv_before_exec: yes mail_executable(default): /usr/local/dovecot-1.0.1/libexec/dovecot/rawlog /usr/local/dovecot-1.0.1/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot-1.0.1/libexec/dovecot/rawlog /usr/local/dovecot-1.0.1/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_log zlib acl mail_plugins(imap): quota imap_quota mail_log zlib acl mail_plugins(pop3): quota mail_log mail_plugin_dir(default): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot/lib/dovecot/pop3 mail_log_prefix: %Us(%u) [%p]: mail_log_max_lines_per_sec: 0 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 namespace: type: public separator: . prefix: Shared. location: /mnt/mailcache/shared:CONTROL=/var/cache/dovecot/%i/sek/control:INDEX=/var/cache/dovecot/%i/sek/index auth default: mechanisms: plain login cache_size: 10 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890 verbose: yes debug: yes passdb: driver: ldap args: /usr/local/dovecot-1.0.1/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/dovecot-1.0.1/etc/dovecot-ldap.conf userdb: driver: passwd-file args: /etc/passwd socket: type: listen 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) iQEVAwUBRouzwS9SORjhbDpvAQLJwgf+NJ8bROXIRfoAjQy+eunNOtM+VoQB0I0A 6EUBG0XfTlgJ1hn63FxpQZPmKBMfLEl013DQQzm9Dw5GezrbgI815M+mZrP6BzYB 95ao1lCTo1hlyVGThG6LgE9JJS8BvE5ASaJOu4XD9u+d2LdV8I+MkcMC9o57XBQt nUV0RrNbxcQpuDq1Qpjf0tu9t0HCRoMzHD0p7cOHteSHiGvvrMeFD0JG7Ida7grQ Uzjbuw92qSNinwTE/89pVr3xrgJGmxdy7ix/y4UBeUx8I9YXOHheB7SOM3cQ6q6J KXKS89Fh9ZWZDsgQwmqaOfAhVgLQjyeAwyA6jqfNzg/Rx0J44m905w== =f+1y -----END PGP SIGNATURE-----

4 9

[Dovecot] Monitorize concurrent sessions
by Jordi Espasa Clofent 10 Aug '07

10 Aug '07

Hi all, ¿Is there some way/method to monitorize and see what users are working at same time? Thanks.

1 0

[Dovecot] dovecot: child 1690 (auth-worker) killed with signal 11
by Thomas Zajic 10 Aug '07

10 Aug '07

Hi there, I've been seeing this for quite a while now, but only today finally got off my lazy you-know-what and did a backtrace. Here's the requested info as per http://dovecot.org/bugreport.html: * Dovecot version [root@airframe]:~# dovecot --version 1.0.3 * Operating system or Linux distribution name Slackware 10.2, both kernel 2.6.21.3 and dovecot self-compiled * CPU architecture (x86 or something else?) x86 (AMD Athlon XP 3200+) * Filesystem you used (especially if you use NFS or not) ext3, local (no NFS) * Some kind of description of what you were doing and with what IMAP client. Thunderbird 2.0.0.4 (also happened with earlier versions) mail-notification-4.1 (" " " " " ) * If the problem can be reproduced, it helps a lot if you can tell how. Happens in almost regular intervals, not sure when exactly though. Usually when doing something in TB again (deleting or moving mails) after it has been sitting idling for a while. From the log files going back to July 22nd: [root@airframe]:~# grep "dovecot: child .* (auth-worker) killed with signal 11" /var/log/maillog* | wc -l 258 TB is configured to use TLS and secure authentication, use IDLE, and 5 cached server connections. Mail Notification is configured to use TLS, and to autodetect both the authentication mechanism and IDLE availability. * Dovecot configuration with dovecot -n [root@airframe]:~# dovecot -n # 1.0.3: /usr/local/etc/dovecot.conf login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_greeting_capability: yes verbose_proctitle: yes mail_location: maildir:/home/%u/Maildir:INBOX=/home/%u/Maildir/.INBOX mail_debug: yes fsync_disable: yes maildir_copy_with_hardlinks: yes mail_drop_priv_before_exec: yes auth default: mechanisms: plain digest-md5 cram-md5 debug: yes passdb: driver: shadow args: blocking=yes passdb: driver: passwd-file args: /usr/local/etc/dovecot-passwd userdb: driver: passwd args: blocking=yes * Backtrace [root@airframe]:~# gdb /usr/local/libexec/dovecot/dovecot-auth /usr/local/stow/dovecot-data/var/run/dovecot/core GNU gdb 6.3 [...] Core was generated by `dovecot-auth -w'. Program terminated with signal 11, Segmentation fault. [...] (gdb) bt full #0 0x00000000 in ?? () No symbol table info available. #1 0x08056954 in auth_worker_handle_passl (client=0x8089e18, id=3, args=0x808a082 "user=zlatko-mail\tservice=IMAP\tlip=192.168.1.3\trip=192.168.1.1\tsecured=1") at auth-worker-client.c:242 auth_request = (struct auth_request *) 0x808a3f0 credentials_str = 0x2 <Address 0x2 out of bounds> #2 0x08056c15 in auth_worker_handle_line (client=0x8089e18, line=0x808a078 "PASSL\t1\t2\tuser=zlatko-mail\tservice=IMAP\tlip=192.168.1.3\trip=192.168.1.1\tsecured=1") at auth-worker-client.c:326 id = 3 #3 0x08056ca7 in auth_worker_input (context=0x8085ac8) at auth-worker-client.c:359 client = (struct auth_worker_client *) 0x8089e18 line = 0x808a076 "3\tPASSL\t1\t2\tuser=zlatko-mail\tservice=IMAP\tlip=192.168.1.3\trip=192.168.1.1\tsecured=1" ret = 118 #4 0x0806b841 in io_loop_handler_run (ioloop=0x80851a8) at ioloop-poll.c:199 ctx = (struct ioloop_handler_context *) 0x80851d0 pollfd = (struct pollfd *) 0x80851f0 tv = {tv_sec = 1, tv_usec = 999620} io = (struct io *) 0x8089f88 t_id = 2 msecs = 134765256 ret = 0 call = true #5 0x0806ae89 in io_loop_run (ioloop=0x80851a8) at ioloop.c:329 No locals. #6 0x0805a04b in main (argc=2, argv=0xbfa36e98) at main.c:321 foreground = false (gdb) Please let me know if you need any additional info (log snippets, etc.). Thanks, Thomas -- =-------------------------------------------------------------------------= - Thomas "ZlatkO" Zajic <zlatko(a)gmx.at> Linux-2.6.21 & Thunderbird-2.0 - - "It is not easy to cut through a human head with a hacksaw." (M. C.) - =-------------------------------------------------------------------------=

2 3

[Dovecot] Version 1.1 Alpha 2 Various Stuff
by Jerry Yeager 09 Aug '07

09 Aug '07

Some preamble information… OS X 10.4.10 (all updates) Power Mac Dual G5, 2.0 Postfix with Dovecot SASL, Dovecot LDA, Dovecot imaps (openssl) Mail clients Apple Mail v 2.1 SquirrelMail v 1.4.10a Thunderbird v 2.0.0.6 Mulberry v 4.06 For various versions of Dovecot, from 0.9m up through 1.0.3 things went well, no memorable big problems, with one exception: Mulberry v 4.0.8 would/will not work; i.e. it refuse(d) to connect saying it could not start SSL to begin the connection. Dropped back to version 4.0.6. I switched to version 1.1 alpha 2 (compile and configuration information is attached at the end of this message) 1) Started up Apple mail. Mail boxes disappeared in Apple Mail's list, except for the main Inbox mail box. Fixed by setting mailbox_list_index_disable = yes in the Dovecot.conf file, restarted both Dovecot and Mail, all the mailboxes reappeared and worked correctly. 2) Started up Squirrel Mail using several different browsers. No problems. 3) Started up Thunderbird. No problems. 4) Started up Mulberry. It partially connected, but stopped with the error saying that it had hit the limit for maximum connections. Mail logs show: dovecot: imap-login: Maximum number of connections exceeded: user=<username>, method=PLAIN, rip=192.168.1.1, lip=192.168.1.50, TLS I tried increasing the various limits in the Dovecot.conf file up through a maximum limit of 2048 connections, to no avail. Mulberry will initially connect to several of the mailboxes, but will stop without getting all of them and will throw up the 'over the connection limit' error and will then show you a dialog box that asks you to log-in. Attempting to doing so returns a fatal error 54. I have not tried Mulberry's version 4.0.8. 5) Mail logs had this message suddenly begin appearing: auth-worker(default): pam(username,192.168.1.1): pam_authenticate() failed: Authentication failure Fixed by completely commenting PAM authentication section out; It was: passdb pam { # [blocking=yes] [session=yes] [setcred=yes] # [cache_key=<key>] [<service name>] # ... essentially a placeholder section, since everything inside is commented out # # } now is: #passdb pam { # # ... even the outer block is commented out # #} The error has now disappeared from the logs. Dovecot was build using: CPPFLAGS=-I/usr/local/include/openssl LDFLAGS='-L/usr/local/lib -R/ usr/local/lib' \ ./configure \ --with-ssl=openssl \ --with-libiconv-prefix=/usr/local Dovecot.conf: # 1.1.alpha2: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imaps ssl_listen: *:993 ssl_parameters_regenerate: 24 ssl_cipher_list: ALL:!LOW:!SSLv2 verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: Dovecot login_greeting: Hello, Dovecot is ready. valid_chroot_dirs: /var/mail/vmail/ mail_extra_groups: mail mail_location: maildir:/var/spool/vmail/%d/%n:INDEX=/var/spool/vmail/% d/%n:INBOX=/var/spool/vmail/%d/%n mail_debug: yes mailbox_list_index_disable: yes lock_method: flock imap_client_workarounds: delay-newmail auth default: mechanisms: plain login passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd-file args: /etc/dovecot/users socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /usr/local/var/run/dovecot/auth-master mode: 384 user: virtual group: virtual

2 2

[Dovecot] Crash with 1.1alpha2 when lazy_expunge is enabled?
by Rich at Whidbey Telecom 09 Aug '07

09 Aug '07

I'm seeing a crash in 1.1alpha2 when trying to expunge a folder when "lazy_expunge" is enabled: namespace private { separator = . prefix = .EXPUNGED/ location = maildir:/mailstore/%u/Expunged hidden = yes } ... lazy_expunge = .EXPUNGED/ .EXPUNGED/ .EXPUNGED/ Commenting out "lazy_expunge" prevents the crash and mail is expunged. It happens with and without ACL's. Attached is the log output. The messages never actually get moved to the "Expunged" directory, but there is a "temp" file created each time: /mailstore/testuser/Expunged/ drwx------ 6 testuser users 4096 Aug 9 11:39 . drwxr-xr-x 4 testuser users 4096 Aug 9 10:59 .. drwx------ 2 testuser users 4096 Aug 9 10:59 cur -rw------- 1 testuser users 24 Aug 9 11:39 dovecot.list.index.log -rw------- 1 testuser users 28 Aug 9 11:39 dovecot.list.index.uidmap drwx------ 5 testuser users 4096 Aug 9 11:02 .Junk -rw------- 1 testuser users 0 Aug 9 10:59 maildirfolder drwx------ 2 testuser users 4096 Aug 9 10:59 new -rw------- 1 testuser users 0 Aug 9 11:04 temp.mail4.whidbey.net.8596.7b344a891b2c6691 -rw------- 1 testuser users 0 Aug 9 11:32 temp.mail4.whidbey.net.8761.bfe04f5457e4ba7e -rw------- 1 testuser users 0 Aug 9 11:33 temp.mail4.whidbey.net.8765.44e803d87275348a -rw------- 1 testuser users 0 Aug 9 11:37 temp.mail4.whidbey.net.9031.f4a972591af59e05 -rw------- 1 testuser users 0 Aug 9 11:39 temp.mail4.whidbey.net.9125.d67b160254a01631 drwx------ 2 testuser users 4096 Aug 9 10:59 tmp Lazy expunge works on our production 1.0.0 systems. Anyone else seen this? Rich dovecot: Aug 09 11:04:25 Info: imap-login: Login: user=<testuser>, method=PLAIN, rip=209.166.64.35, lip=172.16.125.4 dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Loading modules from directory: /usr/local/lib/dovecot/imap dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Module loaded: /usr/local/lib/dovecot/imap/lib01_acl_plugin.so dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Module loaded: /usr/local/lib/dovecot/imap/lib02_lazy_expunge_plugin.so dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Module loaded: /usr/local/lib/dovecot/imap/lib10_quota_plugin.so dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Module loaded: /usr/local/lib/dovecot/imap/lib11_imap_quota_plugin.so dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Effective uid=40308, gid=100, home=/var/mail/testuser dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Quota rule: root=storage=102400 mailbox= storage=256000kB messages=0 dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Namespace: type=private, prefix=, sep=., inbox=yes, hidden=no, list=yes dovecot: Aug 09 11:04:25 Info: IMAP(testuser): maildir: data=/mailstore/testuser/Maildir:INDEX=MEMORY dovecot: Aug 09 11:04:25 Info: IMAP(testuser): maildir++: root=/mailstore/testuser/Maildir, index=, control=, inbox=/mailstore/testuser/Maildir dovecot: Aug 09 11:04:25 Info: IMAP(testuser): acl: initializing backend with data: vfile:/adminstore/configs/dovecot-acls:cache_secs=600 dovecot: Aug 09 11:04:25 Error: IMAP(testuser): Sending log messages too fast, throttling.. dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl: acl username = testuser dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl: owner = 1 dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl vfile: Global ACL directory: /adminstore/configs/dovecot-acls dovecot: Aug 09 11:04:26 Info: IMAP(testuser): Namespace: type=private, prefix=.EXPUNGED/, sep=., inbox=no, hidden=yes, list=no dovecot: Aug 09 11:04:26 Info: IMAP(testuser): maildir: data=/mailstore/testuser/Expunged:INDEX=MEMORY dovecot: Aug 09 11:04:26 Info: IMAP(testuser): maildir++: root=/mailstore/testuser/Expunged, index=, control=, inbox=/mailstore/testuser/Expunged dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl: initializing backend with data: vfile:/adminstore/configs/dovecot-acls:cache_secs=600 dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl: acl username = testuser dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl: owner = 1 dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl vfile: Global ACL directory: /adminstore/configs/dovecot-acls dovecot: Aug 09 11:04:28 Info: IMAP(testuser): acl vfile: reading file /adminstore/configs/dovecot-acls/Junk dovecot: Aug 09 11:04:28 Info: IMAP(testuser): acl vfile: file /mailstore/testuser/Maildir/.Junk/dovecot-acl not found dovecot: Aug 09 11:04:41 Info: IMAP(testuser): acl vfile: reading file /adminstore/configs/dovecot-acls/Junk dovecot: Aug 09 11:04:41 Info: IMAP(testuser): acl vfile: file /mailstore/testuser/Expunged/.Junk/dovecot-acl not found dovecot: Aug 09 11:04:41 Error: IMAP(testuser): file mailbox-list-maildir.c: line 161 (maildir_list_get_path): assertion failed: (mailbox_list_is_valid_existing_name(_list, name)) dovecot: Aug 09 11:04:41 Error: IMAP(testuser): Raw backtrace: imap [0x80c5df1] -> imap [0x80c5d0c] -> imap [0x806ba2d] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so [0x46cfab] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_object_init_from_name+0x1d) [0x46b93d] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_backend_vfile_acllist_rebuild+0x1c7) [0x46d627] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_backend_vfile_acllist_refresh+0x1fd) [0x46db5d] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_backend_vfile_acllist_verify+0x1f) [0x46dcdf] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so [0x46cf13] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_object_have_right+0x2d) [0x46bc6d] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_storage_rights_ctx_have_right+0x5a) [0x4703aa] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so [0x470466] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so [0x4707d8] -> /usr/local/lib/dovecot/imap/lib02_lazy_expunge_plugin.so [0xf5ad3a] -> /usr/local/lib/dovecot/imap/lib10_q dovecot: Aug 09 11:04:41 Error: IMAP(testuser): uota_plugin.so [0x51b92a] -> imap(mailbox_open+0x46) [0x80b6ff6] -> /usr/local/lib/dovecot/imap/lib02_lazy_expunge_plugin.so [0xf5b092] -> /usr/local/lib/dovecot/imap/lib10_quota_plugin.so [0x51b0e8] -> imap(imap_expunge+0xb4) [0x8060034] -> imap(cmd_expunge+0x43) [0x805a4d3] -> imap [0x805e649] -> imap [0x805e6e3] -> imap(_client_input+0x65) [0x805ecb5] -> imap(io_loop_handler_run+0x10f) [0x80cba3f] -> imap(io_loop_run+0x28) [0x80cb3a8] -> imap(main+0x4ec) [0x806637c] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x707dec] -> imap [0x8058e41] dovecot: Aug 09 11:04:41 Error: child 8596 (imap) killed with signal 6

1 0

[Dovecot] UW-IMAP style mbox snarfing from /var/mail/ to ~/mbox
by Timo Sirainen 09 Aug '07

09 Aug '07

http://dovecot.org/patches/mbox-snarf-plugin.c Also committed to CVS HEAD. Usage: mail_location = mbox:~/mail:INBOX=/var/mail/%u protocol imap { mail_plugins = mbox_snarf } protocol pop3 { mail_plugins = mbox_snarf } plugin { mbox_snarf = ~/mbox } If ~/mbox doesn't exist, nothing special is done. If ~/mbox exists, it's treated as INBOX and mails are moved from /var/mail/%u whenever the mailbox is synchronized. If all the messages couldn't be copied, for example because of out of quota, then none of the messages are copied. I suppose that could be a problem. It might be possible to fix that by changing: if (mailbox_copy(dest_trans, mail, 0, NULL, NULL) < 0) { if (!mail->expunged) { ret = -1; break; } } to just: if (mailbox_copy(dest_trans, mail, 0, NULL, NULL) < 0) { if (!mail->expunged) break; } But I'm not sure about that. Try and tell me. :)

2 18

Re: [Dovecot] assertion failed with KMail 3.5.6 and dovecot 1.0.0
by Timo Sirainen 09 Aug '07

09 Aug '07

On Mon, 2007-07-30 at 15:07 +0200, Sylvain Joyeux wrote: > > > IMAP(doudou): file ostream-crlf.c: line 339 (_send_istream): assertion > > > failed: ((size_t)ret <= iov.iov_len) > > Hmm. Can you get Dovecot to dump a core file? > > Probably easiest way to get this fixed would be then if you sent me > > the core file and also the imap binary and I'll debug it further. Or > > I could also send you several gdb commands you could run. > > Here are the imap executable and core dump files (compressed). They are > generated on a powerpc machine, so I'm not sure it will be useful to you. > Moreover, Debian strips its executables, so no line numbers ... Debugging information would have been really useful, but I did fix one bug and added some more asserts: http://hg.dovecot.org/dovecot-1.0/rev/bd113e9fe67b If it still wasn't fixed, maybe with this change it gives another assert.

1 0

[Dovecot] Outlook 2000/2003 frequent disconnect issue
by Jeff Ramsey 09 Aug '07

09 Aug '07

I have been using Dovecot for an IMAP server for a few years now, with no hitch. Even using Outlook 2K/2K3 as a client. Yesterday, I had a user experience the 'Negative UIDs' issue spoken of here: http://wiki.dovecot.org/Clients/NegativeUIDs I performed all of the steps mentioned in this article, and it seemed like it would work properly the first time the user checked their email, and then after that, they would get this error again. I checked to see what the latest stable version of Dovecot was, and decided to upgrade. I was at 0.99.11-8 and the latest stable rpm for my distro was 1.0.2-2. The upgrade went fine. Or so I thought. I am now getting the following message on all Outlook Clients: "Your IMAP Server closed the connection....this can occur if the connection is idle for too long" I have scoured the Internet for this error and have come up with many suggestions, none of which have worked. I have increased Outlook's timeout period to the full 10 minutes, and I have disabled SELinux. None of this seems to have worked. Is there anyone out there who has actually had this issue and resolved it? Can you please help? Thanks, Jeff Ramsey MIS Administrator TMI Forest Products, Inc. jefframsey(a)tubafor.com 360.477.0738 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

4 12

[Dovecot] Database server failure causes endless loop
by Andy Shellam 09 Aug '07

09 Aug '07

Hi, I've just started setting up Dovecot 1.0.1, and made an error in my configuration, which I think has found a potential problem in Dovecot. I'm using PostgreSQL authentication, and set the database host to "localhost", which PostgreSQL doesn't listen on, so libpq is throwing the standard "is the server running?" message. The problem, however, is Dovecot isn't seeming to understand this, and is endlessly looping, trying to query it every 5 seconds. My client (telnet during testing) is simply sitting there waiting for a response, which it's never going to get. After about 5 minutes, Dovecot killed the connection, saying "* BYE Disconnected for inactivity." If this was from an IMAP client, I'm guessing the client would time-out after so long when it doesn't get a response back. Wouldn't it be more sensible for Dovecot to try PostgreSQL, say, 3 times. If unsuccessful, send the client an "internal server error" or something similar? Otherwise if the database server failed, and the client tries to connect, it'd be waiting for at least a minute (or whatever the standard time-out interval is) before failing, whereas it'd be better to see almost instantly if the server's down. Regards, Andy. Log output: dovecot: Jul 01 11:31:03 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:03 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:03 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:08 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:08 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:08 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:13 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:13 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:13 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:18 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:18 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:18 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:23 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:23 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:23 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:28 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:28 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:28 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:33 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:33 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:33 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:38 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:38 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:38 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:43 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:43 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:43 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:48 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:48 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:48 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:53 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:53 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:53 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:58 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:58 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:58 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:32:03 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:32:03 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:32:03 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:32:08 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:32:08 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:32:08 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:32:13 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:32:13 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:32:13 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:32:18 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:32:18 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:32:18 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:32:23 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:32:23 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:32:23 Error: auth(default): TCP/IP connections on port 5432?

2 1