- dovecot - dovecot.org

[Dovecot] IMAP EXPUNGE disconnect/box hang - Fedora Core 2, Squirrelmail and Evolution
by Schettino, John Charles 22 Apr '05

22 Apr '05

I'm a bit befuddled by this behavior. I've been using dovecot for close to a year, and recently the Fedora Core 2 Update: dovecot-0.99.13-4.FC2 build came in via yum. Since then I occasionally get this EXPUNGE disconnect error. When the error hits, the box does not crash but I can no longer log in*, nor start any new processes. I happen to have gkrellm running and I see a slow but steady climb in the # of processess. The only way to recover the box is to do a hard reset, as I cannot log in, nor su - to do a shutdown. In one case I happened to have a root shell open, and I still could not do a shutdown. Any ideas as to what I should do with this? As long as I don't expung everything is fine, but when I do expunge (move something or a filter runs in squirrelmail, or Action/Expunge in Evolution) sometimes it works fine, sometimes I get this error and a weird zombie state. It was all rock solid before this new version. Suggestions welcome - I don't seem to be getting any logging when it goes bad, perhaps I can up the log level? I'm more then happy to build the current dovecot from source, and if I should post this to some Fedora list, point me at it :D

1 0

[Dovecot] IMAP EXPUNGE disconnect/box hang - Fedora Core 2, Squirrelmail and Evolution
by Schettino, John Charles 22 Apr '05

22 Apr '05

Correction: I'm running yum.log:03/07/05 05:48:28 Updated: dovecot 0.99.14-1.1.fc2.rf.i386 - Sorry about that. I'm a bit befuddled by this behavior. I've been using dovecot for close to a year, and recently the Fedora Core 2 Update: dovecot-0.99.13-4.FC2 build came in via yum. Since then I occasionally get this EXPUNGE disconnect error. When the error hits, the box does not crash but I can no longer log in*, nor start any new processes. I happen to have gkrellm running and I see a slow but steady climb in the # of processess. The only way to recover the box is to do a hard reset, as I cannot log in, nor su - to do a shutdown. In one case I happened to have a root shell open, and I still could not do a shutdown. Any ideas as to what I should do with this? As long as I don't expung everything is fine, but when I do expunge (move something or a filter runs in squirrelmail, or Action/Expunge in Evolution) sometimes it works fine, sometimes I get this error and a weird zombie state. It was all rock solid before this new version. Suggestions welcome - I don't seem to be getting any logging when it goes bad, perhaps I can up the log level? I'm more then happy to build the current dovecot from source, and if I should post this to some Fedora list, point me at it :D

1 0

Re: [Dovecot] 1.0 release
by Roger Marquis 22 Apr '05

22 Apr '05

> See http://www.dovecot.org/list/dovecot/2005-January/006144.html If anyone on this list is running 1.0 under FreeBSD inetd I'd really like to know if the syslog/ip address bug has been fixed. We're hoping to use dovecot with pop before smtp but 0.99's dovecot-auth + dovecot--inetd logs the local server's ip address instead of the remote client ip. -- Roger Marquis Roble Systems Consulting http://www.roble.com/

1 0

[Dovecot] How to setup dovecot under MACOSX?
by CHENG Gao 22 Apr '05

22 Apr '05

I have built Dovecot 1.0 test 67 under MACOSX. But I can not find any tutorial on how to setup it. Please allow me to explain my need. I want to setup a local imap server, and then import all my email from Mail.app and Gnus into it. Thus I can choose to read emails with any client. It's only a single user environment. Could anyone instruct me if there is any tutorial for Dovecot MACOSX setting? Thanks in advance.

2 1

[Dovecot] maildir creation
by Renzetti Federico 22 Apr '05

22 Apr '05

Hi all, this is my first post to the list and sorry for my english. I have a mail server based on qmail+dovecot+ldap with virtualdomains and maildir stored in /var/vmail/<DOMAIN>/<USERNAME>/Maildir. When I create a user on LDAP I don't create maildir too. So if I log-in with dovecot (143,110) I hope dovecot creates maildir for users but this is not I get: maildir are not created... dovecot.conf .... default_mail_env = maildir:/var/vmail/%d/%n/Maildir .... There is a way to create automatically maildir for users? Thanks all. -- Renzetti Federico System/Network Administrator RedHat Certified Engineer Fabaris S.r.l. Tel. +39 0765 22181 - Fax +39 0765 410100 Via G. Mameli, 90 02047 Poggio Mirteto (RI) Filiale: Viale dell'Università, 25 00185 Roma (RM) www.fabaris.it

4 3

[Dovecot] 1.0 release
by Patrick Avery 22 Apr '05

22 Apr '05

I'm dying to use the 1.0 capability to use more than one mysql user pasword database. However, I'm too chicken to use 1.0-test in a production environment. Does anyone know if there is a planned release date for 1.0? Or can anyone say how risky it is to use 1.0-test?

6 9

[Dovecot] Disable multiple POP3 logins
by Jesus Salvo Jr. 21 Apr '05

21 Apr '05

Hi, With some POP3 servers, when you login more than once, the POP3 server says "Err: multiple login". How can I achieve that with dovecot ? For example: I login to my POP account that is hosted by the ISP: $ telnet pop.x.com 110 Trying x.x.x.x... Connected to pop.x.com (x.x.x.x). Escape character is '^]'. +OK <25628.1113981451@bne022mfe> USER mb13536d +OK PASS testcase +OK LIST +OK 1 4608 . STAT +OK 1 4608 While that pop3 login is still active, I run another telnet session to login again to the same account. $ telnet pop.x.com 110 Trying x.x.x.x... Connected to pop.x.com (x.x.x.x). Escape character is '^]'. +OK <11709.1113981546@bne021mfe> USER mb13536d +OK PASS testcase -ERR multiple login Connection closed by foreign host. Thanks, John

3 2

[Dovecot] assertion failed in 1.0-stable
by Martin Preen 21 Apr '05

21 Apr '05

Hello everybody, I get the following assertion error with dovecot 1.0-stable when accessing a large folder: file istream-raw-mbox.c: line 383 (istream_raw_mbox_get_body_size): assertion failed: (rstream->body_offset != (uoff_t)-1) There is no error when using dovecot 0.99.14. Any ideas ? Martin ----------------------------------------------------------------- Martin Preen, Universitaet Freiburg, Institut fuer Informatik Georges-Koehler-Allee, Geb.52, Zi.00-006, 79110 Freiburg, Germany phone: ++49 761 203-8250 preen(a)informatik.uni-freiburg.de fax: ++49 761 203-8242 www.informatik.uni-freiburg.de

2 2

[Dovecot] message status changed from new to old on read
by Andrew Pimlott 21 Apr '05

21 Apr '05

Hi. I'm new to IMAP, but just tried uw-imapd and then dovecot in conjuction with offlineimap. I'm using Debian package version 0.99.14-1 and have my mail in mbox format. One of the first things that annoys me about both programs is that as soon as you read a mailbox over imap, the imapd changes all "new" messages to "old". It seems to have the assumption that the IMAP client is "reading" the messages, but particularly in the case of offlineimap, this assumption is not justified: I might not read the message on the client on which I've just synced, I might read it on the server or another client. So I would like dovecot to leave the mailbox alone, and leave it up to the client to write any changes to message status. Is there any option to dovecot that would accomplish this? While experimenting, I noticed that dovecot sometimes doesn't notice changes to the status made directly on the server. For example, if I create new mbox mailbox with one message (initially "new"), and access it with imap (using mutt in this example), it shows up "new" in the client. When I next access it with imap, it shows up "old", because dovecot modified the status as described above. If I then run mutt directly on the mailbox and change the status back to "new", then access it with imap, it still shows up "old". If I then remove the .imap directory containing the caches, it is back to "new". I assume that dovecot is supposed to pick up changes made directly on the server, right? Thanks for your help, Andrew

2 2

[Dovecot] minimial maildir++ quota for dovecot-0.99
by David Harris 21 Apr '05

21 Apr '05

Hello, I'm using dovecot-0.99.14, and I wonder if anyone has created patch for *minimal* Maildir++ support. By minimal Maildir++ support, I mean the following: (1) New messages created by dovecot will include the ,S=nnnnn string in the unique identifier so that Maildir++ clients don't have to stat the file to know the size. (2) Dovecot will append to the maildirsize file when a message is deleted or added. If maildirsize gets larger than the 5120 limit, then just delete it and let someone else recalculate the quota. My goal isn't full Maildir++ support in dovecot, but just to make it play nicely with my Maildir++ aware delivery agent. (If someone has full Maildir++ support, I'd be glad for that too!) If what I describe above doesn't exist, I am interested in paying someone to make this quick patch. E-mail me off list if you are interested. Thanks, David

1 0

[Dovecot] dovecot ssl problem
by Alexander Heuer 20 Apr '05

20 Apr '05

Hi there, I am having a weird problem with dovecot and ssl. If I am accessing the dovecot imap server with for example sylpheed-claws or evolution, everything works fine. If it is accessed via windows either by outlook or thunderbird, we get occassional timeouts. It's working fine for a few hours, then for 5 to 20 minutes, every attempt to connect from the outside results in "Connection to server timed out". Added to that, the problem only arises, if a direct SSL connection to Port 993 is used. Using Sylpheed with STARTTLS to Port 143 from the outside works fine as well. It's not a firewall Problem, since port 993 and 143 are open, the config files have been checked over and over for 2 weeks and are good as well. Dovecot log says: imap-login: Apr 20 13:26:05 Warning: SSL_read() syscall failed: Connection timed out [83.104.224.142] Doing uber verbose output doesn't bring up any extended information, syslog stays clean as well. The Problem is not directly reproducable by a certain action, it just arises from time to time. There can be 3 working days without problems, or 6 timeouts > 20 minutes within one day. System is Debian Sarge unstable with a custom 2.6.10 Kernel. During the timeouts, mail is still received and put into the users mailboxes by exim, it's just that you cannot access the imap server for approx 20 minutes. Dovecot version is 0.99.14 Regards Alexander Heuer

1 0

[Dovecot] MySQL and dovecot
by Anders Kongsted 20 Apr '05

20 Apr '05

Hi, I have some problems with my connection from outside to POP3/IMAP... As far as I can see every should be set corret. Currently I use version 0.99.11-1.FC3.4 installed from an RPM-file. I tried to debug the signin process. It's always saying bad password... What encryption can DoveCot read? Currently my password is encrypted with md5crypt... Regards Anders

2 1

[Dovecot] dovecot-sasl license
by Marcus Rueckert 19 Apr '05

19 Apr '05

hi, i talked to timo about re-licensing the sasl part of dovecot under a more liberal license (bsd/lgpl e.g.). it would allow the integration of it in bsd base systems. another reason i would be interested is adding sasl support to svnserve [1]. so here is my question: what is your oppinion about this issue? any objections from contributors? darix [1] http://subversion.tigris.org/ -- irssi - the client of the smart and beautiful people http://www.irssi.de/

3 2

[Dovecot] Fetching POP3 Mail with Dovecot
by Eurig Jones 18 Apr '05

18 Apr '05

Hi, I have a small personal server here which I've managed to successfuly install the dovecot server onto. What i'm hoping to do is download POP3 mail from 1 or 2 accounts using the dovecot server so I'll be able to read all from the dovecot server... Is this possible? thanks! Eurig

2 1

[Dovecot] attr_names in test67
by Thomas Hummel 18 Apr '05

18 Apr '05

Hello, I'm wondering if the following situation is valid (though I think it isn't since I still cannot authenticate with ldap pass/userdb on test67 running on FreeBSD-5.3). Is it normal that the passdb_ldap_conn->attr_names second element (for instance) "turns to" "homeDirectory" as the following step by step gdb run sample shows ? : -- Breakpoint 1, userdb_ldap_preinit (args=0x80796d0 "/usr/local/dovecot/etc/dovecot-ldap.conf") at userdb-ldap.c:201 201 userdb_ldap_conn = db_ldap_init(args); (gdb) p passdb_ldap_conn->attr_names[1] $1 = 0x8079990 "userPassword" (gdb) cont Continuing. Breakpoint 2, userdb_ldap_init (args=0x80796d0 "/usr/local/dovecot/etc/dovecot-ldap.conf") at userdb-ldap.c:208 208 (void)db_ldap_connect(userdb_ldap_conn); (gdb) p passdb_ldap_conn->attr_names[1] $2 = 0x80799e0 "homeDirectory" (gdb) cont Continuing. Breakpoint 3, ldap_lookup_pass (auth_request=0x5, ldap_request=0x14) at passdb-ldap.c:157 157 struct ldap_connection *conn = passdb_ldap_conn; (gdb) p passdb_ldap_conn->attr_names[1] $3 = 0x80799e0 "homeDirectory" (gdb) cont Continuing. -- Could it explain why I get - in the error log : -- dovecot: Apr 08 18:08:15 Error: auth(default): ldap(dovetest,127.0.0.1): No password in reply dovecot: Apr 08 18:08:15 Error: auth(default): file passdb-ldap.c: line 122 (handle_request): assertion failed: (scheme != NULL) -- - in the info log : dovecot: Apr 08 18:08:15 Info: auth(default): ldap(dovetest,127.0.0.1): base=ou=personnes, dc=pasteur, dc=fr scope=subtree filter=(&(objectClass=posixAccount)(uid=dovetest)) fields=uid,homeDirectory,,,uidNumber,gidNumber ? Thanks for your help. -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

2 2

[Dovecot] no password reply
by Askar 18 Apr '05

18 Apr '05

"dovecot-auth: ldap(branch): No password in reply" Is this Freebsd error , or active directory is not configured correctly or dovecot bug? regards Askar

5 5

[Dovecot] SORT using cached filesystem modtimes
by Emmett Lazich 18 Apr '05

18 Apr '05

Timo or anyone, This may be a bug or maybe a design decision. Either way I am curious to hear comments. Why do the dovecot-0.99.14 server's .imap.index files contain a cached copy of each message's date and time as supplied by the filesystem, as opposed to the date and time found in each message header? When testing various imap clients (eg. tbird-1.0.2, evolution-2.0, outlook2003, squirrelmail-1.4.4) I was intrigued by the behaviour of message date sorting. I toggled on/off the use of server side SORTing in some imap clients, then started forcing rebuilds of .map.index files, and eventually came to the above conclusion. For normal dovecot server side processing, this condition (if I am correct) may not be a problem, but if someone was to deposit a bunch of maildir files firstly into an imap account (bypassing dovecot), and if this person (eg. me) did not preserve the filesystem/inode file attributes. Then dovecot appears to cache the "wrong" data. What happens then is that some imap clients can display wrong date+times in the message lists, and some imap clients find that server side SORTing does not work. Keen to hear thoughts/opinions. -Emmett

3 3

[Dovecot] LSUB matches prefix bug?
by Chris Wakelin 17 Apr '05

17 Apr '05

I think I've found a minor bug in the LSUB command: . LSUB "" "*" gives ... * LIST (\Noselect) "/" "#maildir" ^^^^ * LSUB () "/" "#maildir/test4" where I have a namespace with prefix "#maildir/". Here's a patch to make it not list the namespace prefix in an LSUB command (or should it list it as 'LSUB (\Noselect) "/" "#maildir"'?) :- --- dovecot-1.0-stable.orig/src/imap/cmd-list.c Fri Mar 18 20:00:44 2005 +++ dovecot-1.0-stable/src/imap/cmd-list.c Mon Apr 11 18:29:33 2005 @@ -218,7 +218,7 @@ match = ns->hidden ? IMAP_MATCH_NO : imap_match(ctx->glob, cur_prefix); - if (match == IMAP_MATCH_YES) { + if ((match == IMAP_MATCH_YES) && !ctx->lsub) { /* The prefix itself matches */ enum mailbox_flags flags; string_t *str = t_str_new(128); Best Wishes, Chris --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 1

[Dovecot] Dovecot causing hanging on random folders...
by Rick Flower 17 Apr '05

17 Apr '05

I've been using the 1.0 test series (currently 1.0test 67 and before that 1.0-test59) and both exhibited this issue.. I use Thunderbird and will open one or two of my nested Maildir folders via imap and find that it goes out there trying to open the folder (according to the messages that Thunderbird claims) and it never comes back.. I've attached to the various dovecot processes to see what their doing and they appear to be waiting for things to do -- e.g. not working on anything in particular.. The only way to fix this is to quit Thunderbird and restart it.. I see this about 2-3 times a day.. I'd love to track it down.. I've seen this on Fedora Core 1 (i386 server) and also on a PPC Linux system running an older kernel (on a Buffalo Linkstation if you know what that is).. Below is the current set of dovecot processes running on my FC1 box : [rickf@srv1 dovecot-1.0-test67]# ps aux | grep dove root 748 0.0 0.0 3380 720 ? S 11:30 0:00 dovecot-auth dovecot 749 0.0 0.0 2440 668 ? S 11:30 0:01 imap-login dovecot 760 0.0 0.0 2788 700 ? S 11:30 0:01 imap-login root 709 0.0 0.0 2312 688 ? S 11:30 0:13 /usr/dovecot/sbin/dovecot I'd be happy to track this down if someone can point me in the right direction.. -- Rick

2 1

[Dovecot] Multiple auth mechinisms
by Micha Silver 17 Apr '05

17 Apr '05

From the WIki features page, ( http://wiki.dovecot.org/moin.cgi/CoreFeatures ) it's not clear to me if the dovecot-stable release supports multiple authentications mechanisms (like in 1.0-testxx). I need both virtual domains and system users. Can I use the stable release for this? Thanks, --Micha

2 1

[Dovecot] Failed to create storage with data:
by Matthieu Imbert 17 Apr '05

17 Apr '05

Hi, i'm using dovecot-1.0-stable. All my mail accounts are virtual accounts that come from pam with the following configuration in auth_default: passdb = pam userdb = static uid=5000 gid=5000 home=/var/mail/vhost/example.com/%n mail=/var/mail/vhost/example.com/%n for a user foo, if the directory /var/mail/vhost/example.com/foo already exists, then all is ok, but if the directory doesn't exists, it seems dovecot is unable to create it "on the fly". I get the following error message: Failed to create storage with data: /var/mail/vhost/example.com/foo i'm quite sure it is not a permission related problem (i made /var/mail/vhost/example.com world writable to be sure). I'm currently trying to understand the maildir code... But could someone tell me if the maildir directory should exist for dovecot to work ? In the case that the answer is yes, i would say in advance that it's a problem for sites hosting a lot of virtual users, since it means that these users must receive at least one mail for their mail account to work correctly (i use postfix as MTA, and if the user's maildir doesn't exist, postfix takes care of creating it). I'm not very fond of solutions with scripts taking care of creating users. Thanks in advance for your answers :) -- \|||/ (o o) Matthieu Imbert ooO-(_)-Ooo------------------------------------------ équipe administration réseau et systèmes Ecole normale superieure lettres et sciences humaines 15, Parvis René Descartes BP 7000 69342 LYON cedex 07 tél 0437376127, secrétariat 0437376122 fax 0437376123 contact équipe réseau et systèmes <reseau(a)ens-lsh.fr> contact personnel <matthieu.imbert(a)ens-lsh.fr> -----------------------------------------------------

5 8

[Dovecot] test-67 index issues.
by Dan Sully 17 Apr '05

17 Apr '05

I've been seeing a lot of these in my logs: dovecot: Apr 11 17:48:24 Error: IMAP(fenner): Lost transaction log file /home/f/fenner/Maildir/dovecot.index.log seq 3 dovecot: Apr 11 17:48:24 Error: IMAP(fenner): Lost transaction log file /home/f/fenner/Maildir/dovecot.index.log seq 3 dovecot: Apr 11 17:48:24 Error: IMAP(fenner): Lost transaction log file /home/f/fenner/Maildir/dovecot.index.log seq 3 dovecot: Apr 11 17:48:24 Error: IMAP(fenner): Lost transaction log file /home/f/fenner/Maildir/dovecot.index.log seq 3 dovecot: Apr 11 17:48:24 Error: IMAP(fenner): Lost transaction log file /home/f/fenner/Maildir/dovecot.index.log seq 3 dovecot: Apr 11 17:48:24 Error: IMAP(fenner): Lost transaction log file /home/f/fenner/Maildir/dovecot.index.log seq 3 dovecot: Apr 11 17:48:24 Error: IMAP(fenner): Lost transaction log file /home/f/fenner/Maildir/dovecot.index.log seq 3 dovecot: Apr 11 17:48:25 Error: IMAP(fenner): Lost transaction log file /home/f/fenner/Maildir/dovecot.index.log seq 3 dovecot: Apr 11 17:48:25 Error: IMAP(fenner): Lost transaction log file /home/f/fenner/Maildir/dovecot.index.log seq 3 dovecot: Apr 11 17:48:25 Error: IMAP(fenner): Lost transaction log file /home/f/fenner/Maildir/dovecot.index.log seq 3 dovecot: Apr 11 17:48:25 Error: IMAP(fenner): Lost transaction log file /home/f/fenner/Maildir/dovecot.index.log seq 3 Agent is Apple Mail. Previously removing the indexes and letting them rebuild fixed the issue. Now I've had to restart the server and remove the indexes. Linux, 2.6.x, glibc 2.3.3 -D -- It's the wrong trousers Gromit, and they've gone wrong!

2 1

[Dovecot] Invalid mbox file /var/spool/mail/username: No such file or directory
by Obantec Support 17 Apr '05

17 Apr '05

Hi dovecot-0.99.11-1.FC3.4.i386.rpm on FC3 when i create a user account with pop3 email i find that if i don't send and email to the account (so that sendmail creates the file under /var/spool/mail/testuser) where "testuser" is the users username. If the user logs in with Outlook or Outlook express they get an error and maillog shows. Apr 11 14:18:58 proteus2a pop3(testuser): Invalid mbox file /var/spool/mail/testuser: No such file or directory Apr 11 14:18:58 proteus2a pop3(testuser): Failed to create storage with data: mbox:/var/spool/mail/testuser if "testuser" file does not exist it would be better if Dovecot created an empty file IMHO. as a temp fix i now fire off emails to new accounts to avoid this. Mark

2 1

[Dovecot] Trying to allocate 0 bytes in index-mail-headers.c
by Todd Burroughs 17 Apr '05

17 Apr '05

Here's a new one. It just started with the latest (April 8) CVS version. In index-mail-headers.c, line 622: fields = t_new(struct mail_cache_field, count); count is 0 I'm seeing this with several mailboxes. We're using mbox. Here's the error message and backtrace. dovecot: Apr 09 10:53:18 Error: 3348 IMAP(chairman): Trying to allocate 0 bytes dovecot: Apr 09 10:53:18 Error: child 3348 (imap) killed with signal 6 Core was generated by `imap'. Program terminated with signal 6, Aborted. (gdb) bt #1 0xbffff5c8 in ?? () #2 0x00000006 in ?? () #3 0x00000d14 in ?? () #4 0xb7ef1d41 in raise () from /lib/tls/libc.so.6 #5 0xb7ef3529 in abort () from /lib/tls/libc.so.6 #6 0x080985ba in i_internal_panic_handler ( fmt=0x6 <Address 0x6 out of bounds>, args=0xd14 <Address 0xd14 out of bounds>) at failures.c:374 #7 0x080989d4 in i_panic (format=0x80add1b "Trying to allocate %u bytes") at failures.c:173 #8 0x08097e37 in t_malloc_real (size=Variable "size" is not available. ) at data-stack.c:214 #9 0x08097f54 in t_malloc0 (size=0) at data-stack.c:282 #10 0x08074d34 in index_header_lookup_init (box=0x80c2990, headers=0xbffff840) at index-mail-headers.c:622 #11 0x0808c6f1 in mailbox_header_lookup_init (box=0x0, headers=0xbffff840) at mail-storage.c:376 #12 0x0805e095 in imap_sort (cmd=0x80bb9a8, charset=0x80bbd38 "US-ASCII", args=0x80d72a0, sort_program=0x80b2098) at imap-sort.c:228 #13 0x08058363 in cmd_sort (cmd=0x80bb9a8) at cmd-sort.c:123 #14 0x080595e5 in _client_input (context=0x80bb968) at client.c:334 #15 0x0809d74a in io_loop_handler_run (ioloop=0x80ba5b0) at ioloop-poll.c:184 #16 0x0809ce69 in io_loop_run (ioloop=0x80ba5b0) at ioloop.c:218 #17 0x080604a7 in main (argc=1, argv=0xbffffa74, envp=0xbffffa7c) at main.c:228 (gdb) bt full #0 0xffffe410 in ?? () No symbol table info available. #1 0xbffff5c8 in ?? () No symbol table info available. #2 0x00000006 in ?? () No symbol table info available. #3 0x00000d14 in ?? () No symbol table info available. #4 0xb7ef1d41 in raise () from /lib/tls/libc.so.6 No symbol table info available. #5 0xb7ef3529 in abort () from /lib/tls/libc.so.6 No symbol table info available. #6 0x080985ba in i_internal_panic_handler ( fmt=0x6 <Address 0x6 out of bounds>, args=0xd14 <Address 0xd14 out of bounds>) at failures.c:374 No locals. #7 0x080989d4 in i_panic (format=0x80add1b "Trying to allocate %u bytes") at failures.c:173 No locals. #8 0x08097e37 in t_malloc_real (size=Variable "size" is not available. ) at data-stack.c:214 block = Variable "block" is not available.

2 2

[Dovecot] dovecot and evolution
by Dennis Lambe 17 Apr '05

17 Apr '05

I am using dovecot 0.99.13 and Evolution 2.0.2 on Fedora Core 3. Recently, Ximian stopped being able to access my local INBOX via IMAP, failing with the following error: Error while Opening folder imap://malsyned@localhost/INBOX. Incomplete server response: no information provided for message 1. I got a transcript of the conversation between Evolution and dovecot. The relavent section follows: ========================== [>>] Reading from client A00015 SELECT INBOX [<<] Reading from server * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 7668 EXISTS * 0 RECENT * OK [UNSEEN 7660] First unseen. * OK [UIDVALIDITY 1101063317] UIDs valid * OK [UIDNEXT 334080] Predicted next UID A00015 OK [READ-WRITE] Select completed. [>>] Reading from client A00016 UID FETCH 1:* (FLAGS RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS.NOT (RECEIVED)]) [<<] Reading from server * 2 FETCH (UID 326401 FLAGS (\Seen) INTERNALDATE "09-Apr-2005 13:40:44 -0400" RFC822.SIZE 698 BODY[HEADER.FIELDS.NOT (RECEIVED)] {335} Date: 09 Apr 2005 13:40:44 -0400 From: Mail System Internal Data <MAILER-DAEMON(a)malsyned.dyndns.org> Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA Message-ID: <1113068444(a)malsyned.dyndns.org> X-IMAP: 1113068168 0000078081 Status: RO X-IMAPbase: 1101063317 334079 X-UID: 326401 Content-Length: 260 X-Keywords: ) * 3 FETCH (UID 326402 FLAGS (\Seen) INTERNALDATE "24-Mar-2003 01:45:45 -0500" RFC822.SIZE 1794 BODY[HEADER.FIELDS.NOT (RECEIVED)] {680} Return-Path: <mindless(a)cif.rochester.edu> X-Original-To: malsyned@localhost Delivered-To: malsyned(a)localhost.cif.rochester.edu Delivered-To: malsyned(a)cif.rochester.edu Date: Fri, 19 Apr 2002 09:36:25 -0400 Subject: Re: I can't login Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v481) From: Michael Maskalans <mindless(a)cif.rochester.edu> To: <problem(a)cif.rochester.edu> Content-Transfer-Encoding: 7bit In-Reply-To: <003501c1e6f0$d4859bb0$ef441842@yi0b4plk53mjqz> Message-Id: <71B00250-539A-11D6-A72E-00039303ECDC(a)cif.rochester.edu> X-Mailer: Apple Mail (2.481) Content-Length: 301 Status: RO X-UID: 326402 ) ========================== It looks like dovecot really isn't sending any information for message #1, starting right off at message #2. The headers it gives for message #2 are the same as the first message in my mailspool, and the headers for message #3 are those of the second message in my mailspool. It goes on from there. This doesn't happen to other folders I try to access via IMAP, only my INBOX. Since this only seems to affect Evolution and not pine, I don't know whether this is technically a bug in dovecot or Evolution. I guess that's up to the RFC, which I haven't read all the way through. Anybody got an idea about how to fix this or what's causing it? (Please CC me directly on any replies, I'm not subscribed to this mailing list) Thanks, --Dennis Lambe, <malsyned(a)gmail.com> P.S. Is there a way to get a session transcript out of dovecot? It would save me a fair bit of perl hackery.

2 1

[Dovecot] Upcoming configuration file changes
by Timo Sirainen 17 Apr '05

17 Apr '05

For those who might be interested. Comments welcome. A few weeks ago I had started redesigning how Dovecot handles configuration files. I wrote a new parser and converted dovecot-auth to use the new way. Today I finally managed to convert imap process as well, which wasn't that easy because I didn't want mbox/maildir-specific settings to be hardcoded in any common code. So, the changes will be: - Dovecot master process will need a new completely different configuration file which tells what processes to run and their uids/chroots/memory limits. Very much like Postfix's master.cf. I'm not sure about its format yet (suggestions welcome), but maybe something like it's already: process imap-login { executable = /usr/lib/dovecot/imap-login chroot = /var/run/dovecot/login uid = dovecot vsz_limit = 32M } ... Hopefully after these changes the master process will become very small and simple. - One of the processes will be a configuration process, which is the one that reads and parses the configuration for non-master processes. The default configuration file format will be pretty similar to what we have now, but it can of course be replaced with SQL backends and whatever. Config process will listen in some unix socket waiting for requests from other processes, which connect to it just after they start up and maybe also sometimes later (eg. to get user/IP-specific settings when a new client connects). - The data that config process sends and what other processes parse is based on simple key=value pairs, so it's possible to still store and parse them from environment if needed. Also it makes it possible to override settings from command line (eg. imap -o mail_debug=yes) or give user-specific settings in userdb. Here's an example: # config process reads something like: mmap_disable = yes namespace foo { type = private separator = / mbox { dir = ~/mail mbox_read_locks = dotlock } } # sends out: mmap_disable = yes namespaces = foo namespaces_foo_type = private namespaces_foo_separator = / namespaces_foo_mbox = 1 namespaces_foo_mbox_1_dir = ~/mail namespaces_foo_mbox_1_mbox_read_locks = dotlock - Config process should verify that all given settings are valid so that typos are noticed. This may not be that easy because the setting definitions are distributed all around the source code. I think there needs to be at least a (Perl) script that finds out all the setting definitions and writes them to some all-settings.c for config process so it knows them. Settings for plugins are more difficult though.. Should they somehow be marked in config file that they're plugins (plugin foo { .. })? Or maybe config process could dynamically load all the plugins itself and request their setting definitions?

3 4

[Dovecot] Logwatch
by Rich West 16 Apr '05

16 Apr '05

Having FC3 systems and utilizing Dovecot, I have come to rely on some of the information I get from the daily logwatch run. Logwatch, by default, doesn't properly recognize dovecot's information in the messages file, but it is easy to tweak. The patch below will give you some statistics regarding POP3 and IMAP usage. I believe I grabbed all of the differences in the unified diff below. If I missed anything, please post. :) -Rich --- /etc/log.d/conf/services/imapd.conf 2005-04-15 14:24:52.000000000 -0400 +++ /etc/log.d/conf/services/imapd.conf 2005-04-15 14:51:52.073609243 -0400 @@ -20,7 +20,7 @@ # Only give lines pertaining to courier... # I'm not sure if this is complete, especially for the new webmail daemon in 0.44.1 #but you will get at least all currently supported logs -*OnlyService = (imapd|imapd-ssl) +*OnlyService = (imap-login|imapd|imapd-ssl) *RemoveHeaders = --- /etc/log.d/conf/services/pop3.conf 2005-04-15 14:51:22.795813799 -0400 +++ /etc/log.d/conf/services/pop3.conf 2005-04-15 15:07:00.837019392 -0400 @@ -15,12 +15,12 @@ Title = "POP-3" # Which logfile group... -LogFile = messages +LogFile = maillog # Only give lines pertaining to courier... # I'm not sure if this is complete, especially for the new webmail daemon in 0.44.1 #but you will get at least all currently supported logs -*OnlyService = (pop3d-ssl|pop3d|spop3d) +*OnlyService = (pop3-login|pop3d-ssl|pop3d|spop3d) *RemoveHeaders = --- /etc/log.d/scripts/services/pop3 2005-04-15 15:15:28.727123168 -0400 +++ /etc/log.d/scripts/services/pop3 2005-04-15 15:03:47.402606350 -0400 @@ -58,6 +58,8 @@ # Don't care about these... } elsif ( ($User, $Host) = ( $ThisLine =~ /^user (.*?) authenticated - (.*)$/ ) ) { $Login{$User}{$Host}++; + } elsif ( ($User, $Host) = ( $ThisLine =~ /Login: (.*?) (\[.*\])/ ) ) { + $Login{$User}{$Host}++; } elsif ( ($User,$Downloaded,$DownloadSize,$Left,$LeftSize) = ( $ThisLine =~ /^Stats: (.*?) (.*?) (.*?) (.*?) (.*?)$/) ) { $DownloadedMessages{$User} += $Downloaded; $DownloadedMessagesSize{$User} += $DownloadSize; --- /etc/log.d/scripts/services/imapd 2005-04-15 15:15:20.742084824 -0400 +++ /etc/log.d/scripts/services/imapd 2005-04-15 15:04:39.868698875 -0400 @@ -43,6 +43,9 @@ # Don't care about these... } elsif ( ($User, $Host) = ( $ThisLine =~ /^Login user=(.*?) host=(.* \[.*\])$/ ) ) { $Login{$User}{$Host}++; + } elsif ( ($User, $Host) = ( $ThisLine =~ /Login: (.*?) (\[.*\])/ ) ) { + $ConnectionNonSSL{$Host}++; + $Connection{$Host}++; } elsif ( ($User,$Host) = ( $ThisLine =~ /^Authenticated user=(.*) host=(.* \[.*\])$/ ) ) { $Login{$User}{$Host}++; } elsif ( ($User,$Host) = ( $ThisLine =~ /^Preauthenticated user=(.*) host=(.*)$/ ) ) {

3 3

Re: [Dovecot] maildir in NFS
by Lev Butyrev 15 Apr '05

15 Apr '05

>I think it might be replaced with "mmap_disable=yes" (see the >dovecot-example.conf). I guess the nfs.txt file is a little out of date. > >Chris I try to use option "mmap_disable=yes", but in dovecot logs same messages: "mail_index_lock_fd() failed with file /var/mail/sam-butyrev.lk/dovecot.index.log: No locks available\ ..." In syslog such messages: kernel: lockd: cannot monitor ip_address_nfs_server kernel: lockd: failed to monitor ip_address_nfs_server nfs server Solaris 9 nfs client linux slackware 10.1 with kernel 2.4.29 Sory for my english.

2 1

[Dovecot] comparision with other imap servers and folder sharing
by Emmett Lazich 15 Apr '05

15 Apr '05

Some praise: Timo, I must say I am super impressed with this product. I do free support a few good friends with small businesses running Linux servers (a mix of RH9, Suse9.2 and gentoo) that I dropped as email and samba servers. I found UW-IMAP to be terrible in every way except that using mbox is sometimes nice for old s/w tools. No need for details re UW-IMAP problems. In early 2004 I found courier-imap to be vastly better behaved than UW-IMAP and also much faster once large folders were open. DJB's Maildirs seemed cool, and postfix likes them too, and mb2md-3.20.pl worked great . So everything seemed good and certainly was better. But courier cannot cope with large imap accounts (eg. millions of messages and a few GBytes) where courier-imap grinds to a halt on the initial folder scanning. Cyrus just looks like a big evil beast that needs too much time to learn. Four days ago, this lead me to dovecot. The performance, reliability, configurability of dovecot is amazing. Timo, I think you could give yourself more credit on something important when selling Dovecot. You write that Dovecot "does not support shared folders". This might turn away some people considering Dovecot. People whom like me do not have/want a good understanding of the imap protocol. I believe you mean that Dovecot does not support shared folders in the technical imap sense of shared namespaces between separate imap accounts. Since Dovecot works beautifully when sharing folders via logging in with the same username more than once. Plus your documentation and config notes imply that this is no problem. IDLE and fcntl locking works great for me. Thank you and good luck! -Emmett

1 0

[Dovecot] maildir in NFS
by Lev Butyrev 14 Apr '05

14 Apr '05

How can I configure the dovecot for working with maildir's through NFS? If I add option "index_mmap_invalidate = yes" (as in doc/nfs.t) then in log I have this message: "Error: Error in configuration file /etc/dovecot.conf line 296: Unknown setting: index_mmap_invalidate" If I try to get the mail without option "index_mmap_invalidate" then I have in log this message: "Error: POP3(butyrev.lk): mail_index_lock_fd() failed with file /var/mail/sam-butyrev.lk/dovecot.index.log: No locks available dovecot: Error: POP3(butyrev.lk): mail_index_wait_lock_fd() failed with file /var/mail/sam-butyrev.lk/dovecot.index.log: No locks available dovecot: Error: POP3(butyrev.lk): Couldn't open INBOX: Internal error occured. Refer to server log for more information." dovecot-stable-20050414

2 1

[Dovecot] dovecot + pam + krb5 + nsswitch
by Askar 14 Apr '05

14 Apr '05

hi, anyone of you pls guide me what entries to put in nsswitch.conf for pam to work with krberse, i'm trying to authenticate users from AD, I thinks (my findings) pam.d/dovecot looks into /etc/nsswitch.conf for which passwd databases to use while authenticating a users. my krb setup is working fine I tested with "kinit username" and it authenticat to AD server. Atm i'm trying with these setttings in /etc/nsswitch.conf with no success. #group: compat #group_compat: nis passwd: files krb group: files krb hosts: files dns #networks: files #passwd: compat #passwd_compat: nis #shells: files ~ My plateform is freebsd 5.3 regards Askar

1 0

[Dovecot] test67 ldap_connection
by Thomas Hummel 13 Apr '05

13 Apr '05

Hello, I've been trying to figure out what's wrong with authentication against an ldap pass/user db with test67 as test62 was working fine. [ The problem is the same as previously described in this list : - FreeBSD-5.3 - dovecot-1.0-test67 - openldap-2.1.27 --> "ldap(dovetest,127.0.0.1): No password in reply" --> "NO Temporary authentication failure." or -- dovecot: Apr 12 18:22:41 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=157.99.64.42 rip=157.99.64.42 dovecot: Apr 12 18:22:41 Info: auth(default): client out: CONT 1 dovecot: Apr 12 18:22:41 Info: auth(default): client in: CONT 1 AGRvdmV0ZXN0AGZvbw== dovecot: Apr 12 18:22:41 Info: auth(default): ldap(dovetest,157.99.64.42): base=ou=personnes, dc=pasteur, dc=fr scope=subtree filter=(&(objectClass=posixAccount)(uid=dovetest)) fields=uid,homeDirectory,,,uidNumber,gidNumber dovecot: Apr 12 18:22:42 Info: auth(default): client in: AUTH 2 PLAIN service=IMAP lip=157.99.64.42 rip=157.99.64.42 resp=AGRvdmV0ZXN0AGZvbw== dovecot: Apr 12 18:22:42 Info: auth(default): ldap(dovetest,157.99.64.42): base=ou=personnes, dc=pasteur, dc=fr scope=subtree filter=(&(objectClass=posixAccount)(uid=dovetest)) fields=uid,homeDirectory,,,uidNumber,gidNumber dovecot: Apr 12 18:22:42 Error: auth(default): ldap(dovetest,157.99.64.42): No password in reply dovecot: Apr 12 18:22:42 Error: auth(default): file passdb-ldap.c: line 122 (handle_request): assertion failed: (scheme != NULL) dovecot: Apr 12 18:22:42 Error: child 43147 (auth) killed with signal 6 -- ] I've noticed the following changes in the source code, and my understanding (which may be wrong) of my problem goes as follows : - In test62, the 'attr_names' attribute array was defined outside the 'ldap_connection' struct, thus allowing 'passdb_ldap_conn' and 'userdb_ldap_conn' structs to have different array of such type. - At the opposite, in test67, the 'attr_names' array is inside the 'ldap_connection'. As 'passdb_ldap_conn' and 'userdb_ldap_conn' are of the 'ldap_connection' type and since the 'db_ldap_init' function returns the existing ldap connection if it exists, the 'passdb_ldap_preinit' and 'usedb_ldap_preinit' will call the 'db_ldap_set_attrs' function on _the same_ 'ldap_connection' object. - So when the 'db_ldap_search' function is called from the 'passdb-ldap.c:ldap_lookup_pass function, the 5th argument (passdb_ldap_conn->attr_names) will point to the 'user_attrs' instead of the 'pass_attrs', since userdb_preinit will have already been called. - I've also noticed the use of the 'attr_map' hash to store the attribute/value pairs, but since it doesn't seems to be used when calling 'ldap_lookup_pass', I guess the problem is somewhere else. Can someone give me a clue ? Has someone successfully set up dovecot-1.0-test67 on a similar configuration ? thanks -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

2 2

[Dovecot] dovecot 0.99.14 assertion failed
by Ivan Pesin 13 Apr '05

13 Apr '05

Hello. Recently I've got following assertion on my server with dovecot 0.99.14 when searching: file message-body-search.c: line 391 (message_body_search_ctx): assertion failed: (input->v_offset <= part->physical_pos) -- Ivan Pesin N-iX Newcomp GmbH

1 0

[Dovecot] dovecot + postfix + active directory
by Askar 12 Apr '05

12 Apr '05

hi list, I'm just curious if someone succesfully done dovecot authentication of Active directory and I will appreciage any link in this regards Thanks Askar

3 6

[Dovecot] Syslog, Dovecot, and LogWatch
by Rich West 12 Apr '05

12 Apr '05

At what level does Dovecot log to syslog? UW-IMAP uses local6.debug to log to syslog, but it doesn't seem that dovecot does the same.. (the file I defined for UW-IMAP's output hasn't received anything since I moved over to Dovecot? Also, has anyone managed to get LogWatch and Dovecot to play nicely together? I noticed that LogWatch no longer gives any statistics on the imap usage since I shut down UW and went full blast with Dovecot.. -Rich

4 4

[Dovecot] Index(?) problem under OpenBSD
by Gaby vanhegan 12 Apr '05

12 Apr '05

Hi, My apologies if this has been mentioned before, I haven't pulled up a google search yet. I run Dovecot from the package under OpenBSD 3.6 (dovecot-0.99.10.8). The problem I have is that occasionally dovecot corrupts an index file (I think), which causes the process to gradually creep up in usage, until it hits 99%, where it stays, without quitting. If I then fire up my mail client later on, it does the same thing. Doing this two or three times results in 3 processes, all at 33%, and a load of 100 on the server. The problem is resolved by deleting all the index files in my Maildir. If this doesn't solve the problem, then duplicating my Maildir and using the new copy, after deleting all the index files, fixes the problem. But these only work for a while, and the problem rears it's head with other users as well, so I need a fix. Has anybody else suffered this problem? Is there a fix in a more recent version? Is it OpenBSD specific? What can I do to help diagnose the problem? Should I turn of indexes? Upgrade to the latest version? Some example errors from my logfile: imap(gaby): Apr 11 15:32:37 Error: Corrupted index file /home/gaby/Maildir/.INBOX/.imap.index: Wrong messages_count in header (261 != 382) imap(gaby): Apr 11 15:32:37 Error: Corrupted index data file /home/gaby/Maildir/.INBOX/.imap.index.data: used_file_size larger than real file size (142368 vs 10264) imap(gaby): Apr 11 15:32:44 Error: Corrupted index file (in-memory index for /home/gaby/Maildir): UIDVALIDITY changed in uidlist imap(gaby): Apr 11 15:36:12 Error: Timeout while waiting for release of shared fcntl() lock for index file /home/gaby/Maildir/.Work.LTSN/.imap.index imap(gaby): Apr 11 16:21:27 Error: Timeout while waiting for release of shared fcntl() lock for index file /home/gaby/Maildir/.Archive.Trash-20050308/.ima imap(gaby): Apr 11 16:25:02 Error: Timeout while waiting for release of shared fcntl() lock for index file /home/gaby/Maildir/.Archive.Trash-20050407/.ima Gaby -- Uganda Maximum - Enemy of the English Thrust gaby(a)vanhegan.net http://weblog.vanhegan.net

3 5

[Dovecot] Namespace prefix not ending with separator
by Chris Wakelin 11 Apr '05

11 Apr '05

I'm still battling my way through using hidden namespaces to hide the change from UW-IMAP to Dovecot 1.0-stable from my users. The latest problem is that some (probably many) users have their IMAP folder prefix set to "~/mail" rather than "~/mail/". I have hidden namespaces with prefixes "~/mail/", "~%u/mail/" and "mail/". LIST "~/mail" "*" returns nothing, so I've tried adding another namespace for "~/mail". Now LIST "~/mail" "*" returns * LIST (\NoInferiors \UnMarked) "/" "~/mailtest1/test1-2" * LIST (\NoInferiors \UnMarked) "/" "~/mailtest2" * LIST (\NoInferiors \UnMarked) "/" "~/mailtest3" whereas UW-IMAP returns * LIST (\NoInferiors \UnMarked) "/" ~/mail/test1/test1-2 * LIST (\NoInferiors \UnMarked) "/" ~/mail/test2 * LIST (\NoInferiors \UnMarked) "/" ~/mail/test3 I wonder whether LIST should insert an extra namespace separator in such cases? Having said that, it seems to work, except it may cause problems with folder subscriptions, which I've had to hack in order for them to be compatible with UW-IMAP (i.e. to store them as "~/mail/test1" etc.) Best Wishes, Chris --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

1 0

[Dovecot] imap segfault in mail-index-sync.c
by Todd Burroughs 10 Apr '05

10 Apr '05

Our support team seems to have caused another crash. They treat this mailbox like a shared one, so there may be a few people accessing it at once. They are mostly using dovecot, but some could be using uw-imap. These are the only two ways that this box is accessed. I know that this doesn't really work with mbox, but it doesn't appear to corrupt the mailbox. It seems to be a good stress test... In this case, it looks like several of them are logged in at once. Here's the log entry and backtrace of the imap process which segfaulted. I'll put a section of logs covering this time at the end, in case it helps. The problem appears to be here in mail-index-sync.c: #define MAIL_INDEX_IS_SYNCS_SAME(index) \ ((index)->sync_log_file_seq == (index)->hdr->log_file_seq && \ (index)->sync_log_file_offset == (index)->hdr->log_file_ext_offset) index->hdr is NULL dovecot: Apr 09 20:52:07 Error: 27413 IMAP(support): Fixed index file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index: recent_messages_count 12 -> 0 dovecot: Apr 09 20:52:11 Error: 27413 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: Extension introduction for unknown id 1 dovecot: Apr 09 20:52:11 Error: 27413 IMAP(support): Corrupted index file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index: File too small dovecot: Apr 09 20:52:12 Error: child 27413 (imap) killed with signal 11 Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. (gdb) bt #0 0x08082836 in mail_index_sync_begin (index=0x80c1dc8, ctx_r=0x1, view_r=0x1, log_file_seq=4294967295, log_file_offset=Unhandled dwarf expression opcode 0x93 ) at mail-index-sync.c:322 #1 0x0806e7f3 in mbox_sync (mbox=0x80c29a8, flags=Variable "flags" is not available. ) at mbox-sync.c:1459 #2 0x080683f6 in mbox_storage_close (box=0x80c29a8) at mbox-storage.c:955 #3 0x0808c59d in mailbox_close (box=0x1) at mail-storage.c:300 #4 0x080593da in client_destroy (client=0x80bb968) at client.c:72 #5 0x080596d6 in _client_input (context=0x80bb968) at client.c:387 #6 0x0809d74a in io_loop_handler_run (ioloop=0x80ba5b0) at ioloop-poll.c:184 #7 0x0809ce69 in io_loop_run (ioloop=0x80ba5b0) at ioloop.c:218 #8 0x080604a7 in main (argc=1, argv=0xbffffa44, envp=0xbffffa4c) at main.c:228 (gdb) p index->hdr $11 = (const struct mail_index_header *) 0x0 Here's the rest of the logs: dovecot: Apr 09 20:51:59 Error: 27337 IMAP(support): Fixed index file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index: recent_messages_count 12 -> 0 dovecot: Apr 09 20:52:01 Error: 27337 IMAP(support): Cached message offset lost for seq 11 in mbox file /mailhome/new/m/2/support/mbox dovecot: Apr 09 20:52:07 Error: 27413 IMAP(support): Fixed index file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index: recent_messages_count 12 -> 0 dovecot: Apr 09 20:52:11 Error: 25454 IMAP(support): mbox sync: Expunged message reappeared in mailbox /mailhome/new/m/2/support/mbox (UID 323634 < 324043) dovecot: Apr 09 20:52:11 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: Append with UID 323479, but next_uid = 324043 dovecot: Apr 09 20:52:11 Error: 27413 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: Extension introduction for unknown id 1 dovecot: Apr 09 20:52:11 Error: 27413 IMAP(support): Corrupted index file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index: File too small dovecot: Apr 09 20:52:12 Error: child 27413 (imap) killed with signal 11 dovecot: Apr 09 20:52:13 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 1 dovecot: Apr 09 20:52:15 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 1 dovecot: Apr 09 20:52:17 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 1 dovecot: Apr 09 20:52:18 Error: 27467 IMAP(support): Corrupted index file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index: File too small dovecot: Apr 09 20:52:18 Error: 27467 IMAP(support): Corrupted index file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index: File too small dovecot: Apr 09 20:52:19 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:19 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 1 dovecot: Apr 09 20:52:19 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (2 >= 2) dovecot: Apr 09 20:52:21 Error: 25454 IMAP(support): Corrupted index cache file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.cache: indexid changed dovecot: Apr 09 20:52:21 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:21 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 1 dovecot: Apr 09 20:52:21 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (96) > file size (24) dovecot: Apr 09 20:52:21 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (3 >= 3) dovecot: Apr 09 20:52:23 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:23 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 2 dovecot: Apr 09 20:52:23 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (96) > file size (24) dovecot: Apr 09 20:52:23 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (4 >= 4) dovecot: Apr 09 20:52:25 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 3 dovecot: Apr 09 20:52:27 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:27 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 3 dovecot: Apr 09 20:52:27 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (44) > file size (24) dovecot: Apr 09 20:52:27 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (5 >= 5) dovecot: Apr 09 20:52:29 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:29 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 4 dovecot: Apr 09 20:52:29 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (44) > file size (24) dovecot: Apr 09 20:52:29 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (6 >= 6) dovecot: Apr 09 20:52:31 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:31 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 5 dovecot: Apr 09 20:52:31 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (44) > file size (24) dovecot: Apr 09 20:52:31 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (7 >= 7) dovecot: Apr 09 20:52:33 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:33 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 6 dovecot: Apr 09 20:52:33 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (44) > file size (24) dovecot: Apr 09 20:52:33 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (8 >= 8) dovecot: Apr 09 20:52:35 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:35 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 7 dovecot: Apr 09 20:52:35 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (84) > file size (24) dovecot: Apr 09 20:52:35 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (9 >= 9) dovecot: Apr 09 20:52:38 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:38 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 8 dovecot: Apr 09 20:52:38 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (140) > file size (24) dovecot: Apr 09 20:52:38 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (10 >= 10) dovecot: Apr 09 20:52:39 Error: 27552 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 10 dovecot: Apr 09 20:52:40 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:40 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 9 dovecot: Apr 09 20:52:40 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (44) > file size (24) dovecot: Apr 09 20:52:40 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (11 >= 11) dovecot: Apr 09 20:52:42 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:42 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 10 dovecot: Apr 09 20:52:42 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (44) > file size (24) dovecot: Apr 09 20:52:42 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (12 >= 12) dovecot: Apr 09 20:52:42 Error: 27552 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 11 dovecot: Apr 09 20:53:12 Error: 27552 IMAP(support): file_dotlock_open() failed with file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: Resource temporarily unavailable dovecot: Apr 09 20:53:12 Error: 27552 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 11 dovecot: Apr 09 20:53:12 Error: 27552 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 11 dovecot: Apr 09 20:53:12 Error: 27552 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 11 dovecot: Apr 09 20:53:12 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:53:12 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 11 dovecot: Apr 09 20:53:12 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (13 >= 13) dovecot: Apr 09 20:53:14 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 11 dovecot: Apr 09 20:53:16 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:53:16 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 11 dovecot: Apr 09 20:53:16 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 12 dovecot: Apr 09 20:53:16 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (14 >= 14) dovecot: Apr 09 20:53:18 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:53:18 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 12 dovecot: Apr 09 20:53:18 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 13 dovecot: Apr 09 20:53:18 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (15 >= 15)

1 0

[Dovecot] Authentication and the wrong mailbox?
by Rich West 10 Apr '05

10 Apr '05

I just migrated from UW-imap to dovecot last night. After some tweaking of the dovecot.conf file, disabling xinetd's entries, firing up the dovecot daemon, and copying the .mailboxlist to .subscriptions for all users, things looked to be going just fine! I received a call this morning from a user stating that they had all of *my* emails in *their* inbox! They don't know when it happened as their machine POP's email off every 5-10 minutes or so, but we were able to isolate it to a 8hr period last night. Further investigation showed that at some time through the evening, dovecot freaked out during the authentication phase and for some bizzare reason, when the user connected via POP3, they were able to download all of my inbox! Additionally, by the time I was looking in to it, NO users could authenticate via dovecot, and, hence, no one had access to email. Restarting dovecot resolved the issue, but I have my doubts about it being truly resolved. I'm going to run some tests (what little I can think of), but this is the first time I have ever experienced a situation such as this. One thing for UW is that this situation never happened, and I've only had dovecot running for about 13hrs. Any ideas as to how or why this may have happened, and how it can be prevented, would be wonderful. -Rich -- Richard West $14.95 Registrations mailto:rwest@wesmo.com Wesmo Computer Services .com .net .org .tv .cc http://www.wesmo.com Full Domain & Web Hosting .BIZ .INFO & MORE!!

4 8

[Dovecot] Failed to create storage with data
by Christopher Cheng 09 Apr '05

09 Apr '05

I was trying to configure postfix, mysql with dovecot. The postfix part is fine, but dovecot seems cannot cannot read the mail directory dovecot: Apr 09 16:22:37 Info: Dovecot starting up dovecot-auth: Apr 09 16:22:38 Info: MySQL: connected to localhost dovecot-auth: Apr 09 16:22:38 Info: Login process 7 connected dovecot-auth: Apr 09 16:22:38 Info: Login process 8 connected dovecot-auth: Apr 09 16:22:38 Info: Login process 7 sent handshake: PID 13875 dovecot-auth: Apr 09 16:22:38 Info: Login process 8 sent handshake: PID 13878 dovecot-auth: Apr 09 16:22:38 Info: Login process 9 connected dovecot-auth: Apr 09 16:22:38 Info: Login process 9 sent handshake: PID 13876 dovecot-auth: Apr 09 16:23:11 Info: MySQL: Performing query: SELECT clear FROM postfix_users WHERE user='chris' dovecot-auth: Apr 09 16:23:11 Info: MySQL: Performing query: SELECT concat('/var/spool/mail/', maildir) AS mail, uid, gid FROM postfix_users WHERE user='chris' imap(chris): Apr 09 16:23:11 Error: mbox: Can't create root IMAP folder /mail: Permission denied imap(chris): Apr 09 16:23:11 Fatal: Failed to create storage with data: /var/spool/mail/mydomain.com/chris/Maildir imap-login: Apr 09 16:23:11 Info: Login: chris [::ffff:192.168.1.2] dovecot-auth: Apr 09 16:23:11 Info: Login process 9 disconnected dovecot: Apr 09 16:23:11 Error: child 13879 (imap) returned error 89 dovecot-auth: Apr 09 16:23:11 Info: Login process 9 connected dovecot-auth: Apr 09 16:23:11 Info: Login process 9 sent handshake: PID 13880 The file status in the mail folder. The uid and gid of vmail is 1004 [root@bluemountain chris]# ls /var/spool/mail/mydomain.com/chris/ -l total 16 -rwx------ 1 vmail vmail 11382 Apr 9 00:51 Maildir Here's my mysql data mysql> select * from postfix_users; +----+----------------------+-------+-------+------+------+------+---------- ----------------------+------------------------------+-------+--------+----- ----+-------+ | id | email | clear | crypt | name | uid | gid | homedir | maildir | quota | access | postfix | user | +----+----------------------+-------+-------+------+------+------+---------- ----------------------+------------------------------+-------+--------+----- ----+-------+ | 1 | chris(a)mydomain.com | pass | | | 1004 | 1004 | /var/spool/mail/mydomain.com | mydomain.com/chris/Maildir | | Y | Y | chris | +----+----------------------+-------+-------+------+------+------+---------- ----------------------+------------------------------+-------+--------+----- ----+-------+ 1 row in set (0.00 sec)

1 1

[Dovecot] Outlook express confusion
by Andrew Hutchings 08 Apr '05

08 Apr '05

Hi, This may be a problem with my config file but I am finding that customers (and more importantly my boss) that are using outlook express when using test66/67 (upgraded from test60 + from address patch) are having message reappear after being fully deleted (not just marked) but are unreadable, sometimes blank headers appear too but again no message. Since it is affecting my boss he has told me to go back to test60 or lower, and won't let me find the problem. Regards Andrew -- Andrew Hutchings (A-Wing) Linux Guru - Netserve Consultants Ltd. - www.domaincity.co.uk Random BOFH excuse: Cosmic ray particles crashed through the hard disk platter

2 10

[Dovecot] maildir quota management
by Wayne Lovely 08 Apr '05

08 Apr '05

Hi everyone, my name is Wayne Lovely and this is my first post. My company has a need for dovecot to decrement the portion of quota used. The used portion and hard limit will be stored in a central database. Initially I'll just hack in what we need as a proof of concept, but I would like to get some input into what people would really like, such that I can make a good contribution. regards, Wayne Lovely

2 3

[Dovecot] 1.0-test67
by Timo Sirainen 08 Apr '05

08 Apr '05

http://dovecot.org/test/ Hopefully better release than last one. Fixes several problems test66 had and also some older problems reported in this list. It also contains a pretty large mbox code cleanup, fixing several problems (especially related to X-IMAP/X-IMAPbase headers) and making it a bit faster. Maybe I'll backport it to 1.0-stable too when it looks like it's stable.. BTW. mbox code is slower than necessary when updating message flags and mbox_lazy_writes=yes, because it reads message headers for each message whose flag is to be changed (in index). Should fix that one soon too..

2 4

Re: [Dovecot] Delimiter of mailbox changes in response to STATUS command...
by Lawrence Katz 08 Apr '05

08 Apr '05

Hi Chris - Thank you for the reply. > I can't reproduce this in our setup in either 1.0-stable or > 1.0-test66. What's your namespace definition and MAIL= environment? > What does > > 1 LIST "Misc/" "*" > > give you? The LIST command returns what I expect to see (for readability): 2 list "Misc/" "*" * LIST (\HasNoChildren) "/" "Misc/Spam" > Can you 1 SELECT "Misc/Spam" OK? I can select that mailbox as well as others without a problem. Here's what NAMESPACE returns: 3 NAMESPACE * NAMESPACE (("" "/")) NIL NIL My namespace definition in dovecot.conf is as follows: namespace private { separator = / # prefix = # location = inbox = yes # hidden = yes } I didn't have default_mail_env set to anything, but I just tried the following without a change in the STATUS command's behavior: default_mail_env = maildir:/home/%u/Maildir Is there any other information that might help? Thanks, Lawrence

3 6

[Dovecot] Linux, Maildir over NFS, Locking problems
by Terrence Martin 08 Apr '05

08 Apr '05

Hi, I am having problems with file locks with my NFS mounted Maildir setup. NFS Client/IMAP Server is RHEL3 clone whitebox and NFS server is a Fedora Core 2 system. Both are running lockd as far as I can tell. dovecot is installed with Dag's latest dovecot RPMs for RHEL3. Time is synced between the two systems. Here is the pertinent log file entry dovecot: Dovecot starting up Apr 7 11:17:42 sentry imap(tmartin): /home/tmartin/Maildir/.subscriptions failed with subscription file file_wait_lock(): No locks available Now what I can find in nfs.txt is that I need to use fnctl is this ".customflags and .subscriptions files require fcntl() locking currently. Many NFS servers don't support it, at least without a separate lockd daemon. These will be fixed later to be NFS-safe by default." My question is am I using fcntl? The only reference I can find in the config refers to mbox formats, but I am using maildir. Setting the one reference to fcntl does not seem to have any effect. Is there a configuration setting to tell the server to use fcntl locks or a way to tell if it is trying to use fcntl locks? Thanks for any tips, Terrence

2 4

[Dovecot] MySQL-Auth Problem
by Felix Jirka 08 Apr '05

08 Apr '05

Hi, i would use Dovecot-test66 with MySQL-Auth for virtual users. MySQLd version: 4.1.10a I compliled dovecot with: CPPFLAGS=-I/usr/include/mysql LDFLAGS=-L/usr/lib ./configure --prefix=/usr --sysconfdir=/etc/dovecot --without-passwd --without-shadow --without-pam --without-checkpassword --without-bsdauth --without-vpopmail --with-mysql --with-ssl=openssl --with-storages=maildir --with-moduledir=/etc/dovecot/modules but if i start Dovecot i get: Apr 3 12:44:28 l2 dovecot: auth-worker(default): mysql: Connect failed to 127.0.0.1 (mail): Benutzer 'mail'@'localhost' hat keine Zugriffsberechtigung (verwendetes Passwort: Ja) - waiting for 75 seconds before retry but password and user are correct and worked with dovecot 0.99.14 cu Felix

2 1

[Dovecot] 1.0-test66
by Timo Sirainen 08 Apr '05

08 Apr '05

http://dovecot.org/test/ I've still lots of mails in my INBOX and in this list that I should be looking into.. But here's a release that fixes at least some things. Maybe I'll make another one tomorrow.. Most importantly keyword code was changed a lot. It's now faster and less buggy. The keywords are also finally written into mbox, and keyword changes in the mbox are picked up. So upgrading from Dovecot 0.99.x or UW-IMAP (or reverting back to them) doesn't anymore lose the keywords. Maildir still needs 0.99.x-compatible customflags-file and storing the keywords as a..z flags in maildir filename. Hopefully I'll get that done soon, and then we should be nearing 1.0-alpha1 release :) The new keyword code hasn't been tested much, so this might be less stable than earlier versions. - Renamed oe6-fetch-no-newmail workaround to delay-newmail and changed it to work more like the name says: only newmail notifications are skipped and not only for FETCH command. - LDAP crashfixes - Changed FETCH to return smaller items first. Should fix all kmail and Thunderbird problems. Removed tb-negative-fetch workaround as it shouldn't be needed anymore. - Cache file was breaking constantly with test65 - Blocking passdb fixes and proper RPA realm support patches from Andrey - in-memory indexes should be working again if someone wants to use them for some reason (:INDEX=MEMORY) - gzipped mbox plugin http://dovecot.org/patches/1.0/zlib-plugin.tar.gz - SORT crashfix - Some mbox rewriting fixes (should fix some asserts) - etc.

6 6

[Dovecot] Question about "reply from worker without password scheme"
by Zoong PHAM 08 Apr '05

08 Apr '05

I have dovecot-1.0-test64 installed on OpenBSD-3.6. It works fine with local password. Now I fail to get dovecot to use MySQL to query for user details. Any help would be very appreciated. Here are the details: from /var/log/maillog: 1) with "default_pass_scheme = PLAIN" Apr 3 07:20:22 www dovecot: Dovecot v1.0-test64 starting up Apr 3 07:20:23 www dovecot: auth(default): mysql: Connected to (null) (dovecot) Apr 3 07:20:23 www dovecot: auth-worker(default): mysql: Connected to (null) (dovecot) Apr 3 07:20:50 www dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=1.2.3.4 rip=5.6.7.8 resp=AGhhemVsQGhhemVscGhhbS5jb20AemhAMTlTQXZl Apr 3 07:20:50 www dovecot: auth-worker(default): sql(client(a)clientdomain.com,5.6.7.8): query: SELECT pass AS password FROM user WHERE user = 'client(a)clientdomain.com' Apr 3 07:20:50 www dovecot: auth(default): blocking(client(a)clientdomain.com,5.6.7.8): Received reply from worker without password scheme Apr 3 07:20:51 www dovecot: auth(default): client out: FAIL 1 user=client(a)clientdomain.com temp Apr 3 07:21:50 www dovecot: imap-login: Disconnected: Inactivity [5.6.7.8] 2) with "default_pass_scheme = PLAIN-MD5" Apr 3 07:07:13 www dovecot: Dovecot v1.0-test64 starting up Apr 3 07:07:14 www dovecot: auth(default): mysql: Connected to (null) (dovecot) Apr 3 07:07:14 www dovecot: auth-worker(default): mysql: Connected to (null) (dovecot) Apr 3 07:07:47 www dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP se cured lip=1.2.3.4 rip=5.6.7.8 resp=AGhhemVsQGhhemVscGhhbS5jb20AemhAMTlTQXZl Apr 3 07:07:47 www dovecot: auth-worker(default): sql(client(a)clientdomain.com,5.6.7.8): query: SELECT pass AS password FROM user WHERE user = 'client(a)clientdomain.com' Apr 3 07:07:48 www dovecot: auth(default): client out: FAIL 1 user=client(a)clientdomain.com Command to start dovecot: /usr/local/dovecot/sbin/dovecot -c /usr/local/dovecot/etc/dovecot.conf Part of /usr/local/dovecot/etc/dovecot.conf: .... disable_plaintext_auth = no .... # SQL database passdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for # example args = /usr/local/dovecot/etc/dovecot-mysql.conf } .... # SQL database userdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for # example args = /usr/local/dovecot/etc/dovecot-mysql.conf } .... I also tried with "disable_plaintext_auth = yes" without any luck. /usr/local/dovecot-1.0-test64/etc/dovecot-mysql.conf: driver = mysql connect = host=/var/www/dovecot/mysql.sock dbname=dovecot user=dovecot password=secretpwDB default_pass_scheme = PLAIN password_query = SELECT pass AS password FROM user WHERE user = '%u' user_query = SELECT maildir AS mail, sysuid AS uid, sysgid AS gid FROM user WHERE user = '%n' Manually query MySQL with username and passwd as specified in /usr/local/dovecot-1.0-test64/etc/dovecot-mysql.conf: mysql> SELECT pass AS password FROM user WHERE user ='client(a)clientdomain.com'; +-----------+ | password | +-----------+ | secretpw | +-----------+ 1 row in set (0.00 sec) mysql> Thanks, Zoong

3 10

[Dovecot] imap segfault in mail-cache.c
by Todd Burroughs 08 Apr '05

08 Apr '05

Found an imap crash. I'm using the CVS copy from March 23. This is running under Linux, kernel 2.6.11.something. We use mbox over NFS, everything is on the NFS server. There is currently only one dovecot server accessing the mailbox. Here's the log messages: dovecot: Apr 05 13:11:20 Error: 27911 IMAP(support): UIDVALIDITY changed (1112720886 -> 1112721068) in mbox file /mailhome/new/m/support/mbox dovecot: Apr 05 13:11:20 Error: 27911 IMAP(support): mbox sync: UID inserted in the middle of mailbox /mailhome/new/m/support/mbox (316790 > 316789) dovecot: Apr 05 13:11:20 Error: 27911 IMAP(support): Corrupted index cache file /mailhome/new/m/support/.imap/INBOX/dovecot.index.cache: indexid changed dovecot: Apr 05 13:11:20 Error: child 27911 (imap) killed with signal 11 Here's a backtrace. Note that cache->hdr is NULL. Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. #0 0x080777f9 in mail_cache_lock (cache=0x80c4e20) at mail-cache.c:404 404 cache->hdr_copy = *cache->hdr; (gdb) bt #0 0x080777f9 in mail_cache_lock (cache=0x80c4e20) at mail-cache.c:404 #1 0x0807a1e9 in mail_cache_handler_init (ctx_r=0xbffff3d8, cache=0x80c4e20) at mail-cache-sync-update.c:40 #2 0x0807a3a0 in mail_cache_expunge_handler (sync_ctx=0xbffff520, seq=32, data=0x80cc964, context=0x80c8ce0) at mail-cache-sync-update.c:85 #3 0x08081ba3 in mail_index_sync_record (ctx=0xbffff520, hdr=0x80c5e34, data=0x80cb590) at mail-index-sync-update.c:135 #4 0x080826b9 in mail_index_sync_update_index (sync_ctx=0x80c5d98, sync_only_external=0) at mail-index-sync-update.c:648 #5 0x08080913 in mail_index_sync_commit (ctx=0x80c5d98) at mail-index-sync.c:595 #6 0x0806e432 in mbox_sync (ibox=0x80c3fe0, flags=MBOX_SYNC_REWRITE) at mbox-sync.c:1418 #7 0x08067eb9 in mbox_storage_close (box=0x80c3fe0) at mbox-storage.c:914 #8 0x0808a72d in mailbox_close (box=0xffffff02) at mail-storage.c:299 #9 0x08057efc in _cmd_select_full (cmd=0x80b9050, readonly=0) at cmd-select.c:50 #10 0x08057f31 in cmd_select (cmd=0x80b9050) at cmd-select.c:99 #11 0x080593f5 in _client_input (context=0x80b9010) at client.c:334 #12 0x0809b28a in io_loop_handler_run (ioloop=0x80b79e8) at ioloop-poll.c:184 #13 0x0809a9a9 in io_loop_run (ioloop=0x80b79e8) at ioloop.c:218 #14 0x080602a7 in main (argc=1, argv=0xbffffa34, envp=0xbffffa3c) at main.c:229 (gdb) bt full #0 0x080777f9 in mail_cache_lock (cache=0x80c4e20) at mail-cache.c:404 view = (struct mail_index_view *) 0x80c4748 ext = (const struct mail_index_ext *) 0x80c62c8 i = 0 ret = -1 #1 0x0807a1e9 in mail_cache_handler_init (ctx_r=0xbffff3d8, cache=0x80c4e20) at mail-cache-sync-update.c:40 ctx = (struct mail_cache_sync_context *) 0x80c6958 ret = Variable "ret" is not available. (gdb) p cache->hdr $1 = (const struct mail_cache_header *) 0x0 Todd Burroughs

2 1

[Dovecot] Archiving Dovecot format maildir
by Leslie Viljoen 08 Apr '05

08 Apr '05

Hi! It seems that the Maildir format used by Dovecot is a standard, right? Has anyone written something to archive mail in Dovecot format maildirs? I have a script that seems to be for Cyrus IMAP but it doesn't seem to work. I'll write a Perl program if there is nothing available but I am concerned about dovecot's index files - do I need to do anything to get dovecot to rebuild them? Leslie Viljoen

2 1

[Dovecot] headers don't match message
by Kevin 08 Apr '05

08 Apr '05

the other day i moved all mail functions to a different machine. i copied over my existing maildir's and installed dovecot-stable-20050405. once i had everything moved and dovecot running i checked my mail via imap. all the messages appeared however when i try to read a message the message body doesn't match the header info that's showed in the message list. is this an index problem? or did i corrupt my maildir when i moved it over to another host?

3 4

[Dovecot] public or shared folders
by Richard Stegman 08 Apr '05

08 Apr '05

Hello I would like to setup a public namespace with folders under it that are accessiable by certain users. Something like this: Projects---- | |-----03060 | |-----04579 Users should be able to move emails from their inbox to the shared folders, and all user can see the moved email. Here is what I have done so far: 1. I installed dovecot-1.0-0 4 stable20050221.rhf3.at.i386.rpm to a Fedora core 3 machine with Postfix and procmail. 2. Tested mail server - both pop and imap work. 3. Modified dovecot conf. file with the following entry: namespace private { separator = / prefix = inbox = yes hidden = no } namespace public { separator = . prefix = Projects. location = maildir:/var/mail/Projects inbox = no hidden = no } 4. Restart dovecot. Test - imap and pop work. 5. Create group imapu. Add email users to group imapu 6. Create (as root) /var/mail/Projects. Change group to imapu. Change mode 770 7. Touch file dovecot-shared to /var/mail/Projects. Change group to imapu. Change mode 770 8. Make directory /var/mail/Projects/.03060. Change group to imapu. Change mode 770 9. Touch file dovecot-shared to /var/mail/Projects/.03060. Change group to imapu. Change mode to 770 10. Restart dovecot. I start up thunderbird and the Project namespace shows up. I then subscribe to 03060 and get this error: The current command did not succeed. The mail server responded: Error in IMAP command UID: Invalid BODY[..] parameter: Missing '>' <10240.-1357>'. I click ok and I can move email from the inbox to 03060. The mail shows up in 03060. No other user can then subscribe to 03060. What am I doing wrong? Thanks Rick

2 1

[Dovecot] pam problems
by Matthieu Imbert 07 Apr '05

07 Apr '05

Hi, i'm quite new to dovecot. i built it from the stable-1.0 sources. i have the following error messages in syslog when trying to launch dovecot: dovecot: Dovecot v1.0-stable starting up dovecot: auth(default): Unknown passdb type 'pam' dovecot: Auth process died too early - shutting down dovecot: child 373 (auth) returned error 89 i googled a bit, and found some posts on this mailing list describing the same problem, and the answer is that pam support is not compiled in. So i tried to ensure pam support would be compiled: i made sure that i have the proper libs. I work on debian so i did: apt-get install libpam-runtime libpam-modules apt-show-version tells me the version numbers installed: ... libpam-modules/testing uptodate 0.76-22 libpam0g/testing uptodate 0.76-22 libpam-runtime/testing uptodate 0.76-22 libpam-ldap/stable uptodate 140-1 ... my configure line is as follows: ./configure --sysconfdir=/etc --localstatedir=/var --with-ssl=openssl --with-pam when running configure, the only line related to pam is the following: checking for pam_start in -lpam... no and at the end of the configure script i get the following summary: Building with user database modules : static passwd passwd-file checkpassword (modules) Building with password lookup modules : passwd passwd-file shadow checkpassword (modules) So it seems that pam support is not built in. What is the lib i am missing ? Any help appreciated, thanks -- \|||/ (o o) Matthieu Imbert ooO-(_)-Ooo------------------------------------------ équipe administration réseau et systèmes Ecole normale superieure lettres et sciences humaines 15, Parvis René Descartes BP 7000 69342 LYON cedex 07 tél 0437376127, secrétariat 0437376122 fax 0437376123 contact équipe réseau et systèmes <reseau(a)ens-lsh.fr> contact personnel <matthieu.imbert(a)ens-lsh.fr> -----------------------------------------------------

1 1

Re: [Dovecot] Dovecot 1.0 POP3 login but no mail
by david＠stpenable.com 06 Apr '05

06 Apr '05

I followed Geralds' instructions and dovecot returns "0 0" to stat cmd and "0 messages:" to list. So it thinks there are zero when there are over 40 in "%h/.maildir". I had not changed my config file before reboot so how can this happen? It worked prior to reboot and not after. I get no maillog errors, what next? Thx. David "David Wynter" <david(a)stpenable.com> wrote .. > Dovecot is installed on the hosted FC1 server I have, it was working fine > until yesterday when they had to bounce the server. I can login fine from > Outlook or connect telnet <hostname> 110. But even though I can see sendmail > has received mail into my %h/.maildir (via webmail's user mail facility) > when I log into dovecot via Outlook it does not retrieve any of it. > > I tried from W2K "telnet <hostname> 110", it connects "+OK dovecot ready.", > then I typed "LOGIN <username> <password>" and i get "-ERR Unknown > command.". However with Outlook it logs in fine I see in maillog the result, > no other errors in maillog. Cannot see what is wrong. Here are the important > bits of my dovecot.conf, everything else is std. i.e. commented out > > protocols = pop3 > login = imap > login = pop3 > default_mail_env = maildir:%h/.maildir > client_workarounds = outlook-idle > mbox_locks = fcntl > auth = default > auth_userdb = passwd > auth_passdb = pam > auth_user = root > auth_verbose = yes > > Ideas on where to look next? > > Thx > > David

1 0

[Dovecot] Delimiter of mailbox changes in response to STATUS command...
by Lawrence Katz 06 Apr '05

06 Apr '05

Hi - I've been using Hastymail with my Dovecot server for awhile now. However, I have noticed that at some point Hastymail stopped showing the number of unseen messages in its folder drop down list, it just shows 0 for the folders that I have it checking for unseen messages. I'm not sure when it broke, but I think it's when I went to one of the testing builds several months ago. I just upgraded to Hastymail 1.3 and Dovecot testing66 today just to see if the issue would go away and it hasn't. So I did some digging and I think I found the cause of the issue... If I send a STATUS command, like the one shown below, Dovecot changes the mailbox delimiter in the result from a "/" to a "."... 2 STATUS "Misc/Spam" (UNSEEN) * STATUS "Misc.Spam" (UNSEEN 3) 2 OK Status completed. I was able to work around this in Hastymail by substituting a "/" for a "." when the result comes back, but it's not that elegant. Any thoughts on why this might be happening in Dovecot? Is it a configuration issue on my part, or a bug? The private namespace in my dovecot.conf has the following: separator = / Thanks, Lawrence

1 0

[Dovecot] dovecot crashes
by Geo Carncross 06 Apr '05

06 Apr '05

I'm getting these over and over again in my dovecot [CVS] logs. I'm using PAM for authentication- something that worked a few weeks ago. Apr 6 15:22:11 [PAM-env] Unknown PAM_ITEM: <XAUTHORITY> Apr 6 15:22:11 [dovecot-auth] PAM pam_putenv: delete non-existent entry; XAUTHORITY dovecot: Apr 06 15:22:16 Warning: Killed with signal 2 dovecot: Apr 06 15:22:16 Error: child 25731 (imap) killed with signal 2 dovecot: Apr 06 15:22:16 Error: child 27545 (login) killed with signal 2 dovecot: Apr 06 15:22:16 Error: child 20320 (login) killed with signal 2 -- Internet Connection High Quality Web Hosting http://www.internetconnection.net/

2 3

[Dovecot] Dovecot 1.0 POP3 login but no mail
by David Wynter 06 Apr '05

06 Apr '05

Dovecot is installed on the hosted FC1 server I have, it was working fine until yesterday when they had to bounce the server. I can login fine from Outlook or connect telnet <hostname> 110. But even though I can see sendmail has received mail into my %h/.maildir (via webmail's user mail facility) when I log into dovecot via Outlook it does not retrieve any of it. I tried from W2K "telnet <hostname> 110", it connects "+OK dovecot ready.", then I typed "LOGIN <username> <password>" and i get "-ERR Unknown command.". However with Outlook it logs in fine I see in maillog the result, no other errors in maillog. Cannot see what is wrong. Here are the important bits of my dovecot.conf, everything else is std. i.e. commented out protocols = pop3 login = imap login = pop3 default_mail_env = maildir:%h/.maildir client_workarounds = outlook-idle mbox_locks = fcntl auth = default auth_userdb = passwd auth_passdb = pam auth_user = root auth_verbose = yes Ideas on where to look next? Thx David

3 2

[Dovecot] change POP3 default prompt
by Ing. Alejandro Rodriguez 06 Apr '05

06 Apr '05

ppl for security reasons I'dont want that the default prompt for the POP3 be +OK Dovecot ready. don't want an attacker can guess my POP3 server easily, any idea?? want something like +OK mydomain.com ready. regards A

2 1

[Dovecot] dovecot and vpopmail
by Kris Northern 05 Apr '05

05 Apr '05

Hello Im using dovecot .99.14 with vpopmail 5.4.2 on debian sarge I changed the settings in dovecot.conf default_mail_env = maildir:/home/vpopmail/domains/%d/%u/Maildir (my mail is in /home/vpopmail/domains/phidelity.com/kris/Maildir) auth = vpopmail auth_mechanisms = plain auth_userdb = vpopmail auth_passdb = vpopmail auth_executable = /home/vpopmail/bin/vchkpw auth_user = vpopmail and when I start up dovecot I get these errors Apr 4 22:43:01 mail dovecot: Dovecot starting up Apr 4 22:43:02 mail dovecot: Auth process died too early - shutting down Apr 4 22:43:02 mail dovecot: child 25759 (auth) returned error 11 can someone help me make sense of this? I couldnt find anything useful on google. -kris

2 1

[Dovecot] FETCH order fix backport to stable from test66
by Chris Wakelin 05 Apr '05

05 Apr '05

I've had a go at back-porting Timo's recent fixes to the IMAP fetch command from 1.0-test66 to 1.0-stable. This seems to fix the problem with kmail, and Thunderbird seems to work fine without its RFC822.SIZE fix. It's a bit big for the body of this message, so it's attached. The bit I'm most concerned about in my port is whether I got the buffer_insert call right (back-ported from an array_insert call) in imap-fetch.c :- @@ -119,8 +129,14 @@ memset(&h, 0, sizeof(h)); h.handler = handler; h.context = context; + h.buffered = buffered; - buffer_append(ctx->handlers, &h, sizeof(h)); + if (!buffered) + buffer_append(ctx->handlers, &h, sizeof(h)); + else { + buffer_insert(ctx->handlers, ctx->buffered_handlers_count * size of(h), &h, sizeof(h)); + ctx->buffered_handlers_count++; + } } Best Wishes, Chris --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

1 0

[Dovecot] Running POP3 with two different ports?
by Andres U 05 Apr '05

05 Apr '05

Hi everyone! I need to run Dovecot with two ports (eg 110 and 2110). Any ideas? Regards, Andres Argentina

2 1

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

04 Apr '05

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

1 0

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

04 Apr '05

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

1 0

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

03 Apr '05

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

2 2

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

03 Apr '05

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

2 2

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

03 Apr '05

Hi, I'm having issues getting the multiple authentication methods of dovecot 1.0-test65 to work correctly on NetBSD. I am combining a MySQL database of virtual host accounts with the system password database of local machine accounts. Both work correctly when enabled on their own, but when enabled together only the one listed first in the "auth default" section of dovecot.conf works - the other logs the following error (line 5 below): Mar 29 21:56:50 rivendell dovecot: Dovecot v1.0-test65 starting up Mar 29 21:56:51 rivendell dovecot: auth(default): mysql: Connected to 127.0.0.1 (maildomains) Mar 29 21:56:51 rivendell dovecot: auth-worker(default): mysql: Connected to 127 .0.0.1 (maildomains) Mar 29 21:57:05 rivendell dovecot: auth-worker(default): BUG: PASSV had invalid passdb num Mar 29 21:57:38 rivendell dovecot: Killed with signal 2 To the client, dovecot locks up when a LOGIN command is issued for a user which can't be authenticated using the first method available (in my case, passwd). So for me, /etc/passwd users can still log in ok, but dovecot will lock up whenever a login with any other username is attempted. Script started on Tue Mar 29 22:07:59 2005 [root@rivendell ttyp3 ~]# telnet localhost 143 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. . LOGIN timshel secret . OK Logged in. . LOGOUT * BYE Logging out . OK Logout completed. Connection closed by foreign host. [root@rivendell ttyp3 ~]# telnet localhost 143 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. . LOGIN timshel(a)shels.net secret <dovecot locks up> . LOGOUT ^] telnet> quit Connection closed. [root@rivendell ttyp3 ~]# telnet localhost 143 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. . LOGIN dummyuser dummypass <dovecot locks up again> ^] telnet> quit Connection closed. [root@rivendell ttyp3 ~]# Script done on Tue Mar 29 22:09:03 2005 My dovecot.conf file is attached - can anyone shed any light on this and help me get going? Cheers, Timshel ## Dovecot 1.0 configuration file # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples with # real defaults being based on configure options. # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s protocols = imap imaps pop3 pop3s #protocols = imap imaps #protocols = imaps # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. If you want to specify ports # for each service, you will need to configure these settings inside the # protocol imap/pop3 { ... } section, so you can specify different ports # for IMAP/POP3. #listen = * #listen = [::] listen = 127.0.0.1 # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = #ssl_listen = [::] ssl_listen = * # Disable SSL/TLS support. #ssl_disable = no # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf #ssl_cert_file = /usr/pkg/etc/ssl/certs/imap.pem #ssl_key_file = /usr/pkg/etc/ssl/private/imap.pem ssl_cert_file = /etc/openssl/certs/mail.shels.net.crt ssl_key_file = /etc/openssl/private/mail.shels.net.key # File containing trusted SSL certificate authorities. Usually not needed. #ssl_ca_file = ssl_ca_file = /etc/openssl/ShelsCA/cacert.pem # Request client to send a certificate. #ssl_verify_client_cert = no # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 24 # SSL ciphers to use #ssl_cipher_list = all:!low # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. #disable_plaintext_auth = yes disable_plaintext_auth = yes # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). #log_path = # For informational messages, use this logfile instead of the default #info_log_path = # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = /var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. # http://wiki.dovecot.org/Rootless #login_chroot = yes # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. # Note that this user is NOT used to access mails. # http://wiki.dovecot.org/UserIds #login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 32 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to create. If login_process_per_user is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_user # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 # Greeting message for clients. #login_greeting = Dovecot ready. ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. first_valid_uid = 100 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. first_valid_gid = 100 #last_valid_gid = 0 # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. #mail_extra_groups = # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See doc/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden for # specific users in user database by giving /./ in user's home directory # (eg. /home/./user chroots into /home). Note that usually there is no real # need to do chrooting, Dovecot doesn't allow users to access files outside # their mail directory anyway. #mail_chroot = # Enable mail process debugging. This can help you figure out why Dovecot # isn't finding your mails. #mail_debug = no # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # doc/mail-storages.txt. There's a few special variables you can use, eg.: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if there's no domain # %h - home directory # # See doc/variables.txt for full list. Some examples: # # default_mail_env = maildir:/var/mail/%1u/%u/Maildir # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # #default_mail_env = maildir:/home/%u/Maildir #default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u default_mail_env = maildir:~/.mail # If you need to set multiple mailbox locations or want to change default # namespace settings, you can do it by defining namespace sections: # # You can have private, shared and public namespaces. The only difference # between them is how Dovecot announces them to client via NAMESPACE # extension. Shared namespaces are meant for user-owned mailboxes which are # shared to other users, while public namespaces are for more globally # accessible mailboxes. # # REMEMBER: If you add any namespaces, the default namespace must be added # explicitly, ie. default_mail_env does nothing unless you have a namespace # without a location setting. Default namespace is simply done by having a # namespace with empty prefix. #namespace private { # Hierarchy separator to use. You should use the same separator for all # namespaces or some clients get confused. '/' is usually a good one. #separator = / # Prefix required to access this namespace. This needs to be different for # all namespaces. For example "Public/". #prefix = # Physical location of the mailbox. This is in same format as # default_mail_env, which is also the default for it. #location = # There can be only one INBOX, and this setting defines which namespace # has it. #inbox = yes # If namespace is hidden, it's not advertised to clients via NAMESPACE # extension or shown in LIST replies. This is mostly useful when converting # from another server with different namespaces which you want to depricate # but still keep working. For example you can create hidden namespaces with # prefixes "~/mail/", "~%u/mail/" and "mail/". #hidden = yes #} # Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # # flags, date.sent, date.received, size.virtual, size.physical # mime.parts, imap.body, imap.bodystructure # # Different IMAP clients work in different ways, so they benefit from # different cached fields. Some do not benefit from them at all. Caching more # than necessary generates useless disk I/O, so you don't want to do that # either. # # Dovecot attempts to automatically figure out what client wants and it keeps # only that. However the first few times a mailbox is opened, Dovecot hasn't # yet figured out what client needs, so it may not perform optimally. If you # know what fields the majority of your clients need, it may be useful to set # these fields by hand. If client doesn't actually use them, Dovecot will # eventually drop them. # # Usually you should just leave this field alone. The potential benefits are # typically unnoticeable. #mail_cache_fields = # Space-separated list of fields that Dovecot should never save to cache file. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Like mailbox_check_interval, but used for IDLE command. #mailbox_idle_check_interval = 30 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no # Maximum allowed length for mail keyword name. It's only forced when trying # to create new keywords. #mail_max_keyword_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. # Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes. #mail_read_mmaped = no # Don't use mmap() at all. This is required if you store indexes in remote # filesystems (NFS or clustered filesystem). #mmap_disable = no # Don't write() to mmaped files. This is required for some operating systems # which use separate caches for them, such as OpenBSD. #mmap_no_write = no # Locking method for index files. Alternatives are fcntl, flock and dotlock. # Dotlocking uses some tricks which may create more disk I/O than other locking # methods. #lock_method = fcntl # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. maildir_copy_with_hardlinks = yes # Which locking methods to use for locking mbox. There's four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist in all systems. Doesn't work with NFS. # # You can use multiple locking methods; if you do the order they're declared # in is important to avoid deadlocks if other MTAs/MUAs are using multiple # locking methods as well. Some operating systems don't allow using some of # them simultaneously. mbox_read_locks = fcntl mbox_write_locks = fcntl # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # When mbox changes unexpectedly we have to fully read it to find out what # changed. If the mbox is large this can take a long time. Since the change # is usually just a newly appended mail, it'd be faster to simply read the # new mails. If this setting is enabled, Dovecot does this but still safely # fallbacks to re-reading the whole mbox file whenever something in mbox isn't # how it's expected to be. The only real downside to this setting is that if # some other MUA changes message flags, Dovecot doesn't notice it immediately. # Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK # commands. #mbox_dirty_syncs = yes # Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE, # EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored. #mbox_very_dirty_syncs = no # Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK # commands and when closing the mailbox). This is especially useful for POP3 # where clients often delete all mails. The downside is that our changes # aren't immediately visible to other MUAs. #mbox_lazy_writes = yes # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. It could be a small # security risk if you use single UID for multiple users, as the users could # ptrace() each others processes then. #mail_drop_priv_before_exec = no # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #mail_process_size = 256 # Log prefix for mail processes. See doc/variables.txt for list of possible # variables you can use. #mail_log_prefix = "%Us(%u): " ## ## IMAP specific settings ## protocol imap { # Login executable location. #login_executable = /usr/pkg/libexec/dovecot/imap-login # IMAP executable location #mail_executable = /usr/pkg/libexec/dovecot/imap # This would write rawlogs into ~/dovecot.rawlog/ directory: #mail_executable = /usr/pkg/libexec/dovecot/rawlog /usr/pkg/libexec/dovecot/imap # Maximum IMAP command line length in bytes. Some clients generate very long # command lines with huge mailboxes, so you may need to raise this if you get # "Too long argument" or "IMAP command line too large" errors often. #imap_max_line_length = 65536 # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/pkg/lib/dovecot/imap # Send IMAP capabilities in greeting message. This makes it unnecessary for # clients to request it with CAPABILITY command, so it saves one round-trip. # Many clients however don't understand it and ask the CAPABILITY anyway. #login_greeting_capability = no # Workarounds for various client bugs: # delay-newmail: # Send EXISTS/RECENT new mail notifications only when replying to NOOP # and CHECK commands. Some clients ignore them otherwise, for example # OSX Mail. Outlook Express breaks more badly though, without this it # may show user "Message no longer in server" errors. Note that OE6 still # breaks even with this workaround if synchronization is set to # "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. # netscape-eoh: # Netscape 4.x breaks if message headers don't end with the empty "end of # headers" line. Normally all messages have this, but setting this # workaround makes sure that Netscape never breaks by adding the line if # it doesn't exist. This is done only for FETCH BODY[HEADER.FIELDS..] # commands. Note that RFC says this shouldn't be done. # tb-negative-fetch: # Thunderbird sometimes messed up some calculations and wants to read # the message past it's end, giving negative size to FETCH BODY[]<..> # command. This workaround just hides the error message. #imap_client_workarounds = outlook-idle } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. #login_executable = /usr/pkg/libexec/dovecot/pop3-login # POP3 executable location #mail_executable = /usr/pkg/libexec/dovecot/pop3 # Don't try to set mails non-recent or seen with POP3 sessions. This is # mostly intended to reduce disk I/O. With maildir it doesn't move files # from new/ to cur/, with mbox it doesn't write Status-header. #pop3_no_flag_updates = no # Support LAST command which exists in old POP3 specs, but has been removed # from new ones. Some clients still wish to use this though. Enabling this # makes RSET command clear all \Seen flags from messages. #pop3_enable_last = no # POP3 UIDL format to use. You can use following variables: # # %v - Mailbox UIDVALIDITY # %u - Mail UID # %m - MD5 sum of the mailbox headers in hex (mbox only) # %f - filename (maildir only) # # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier version 0 : %f # Courier version 1 : %u # Courier version 2 : %v-%u # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # # Note that Outlook 2003 seems to have problems with %v.%u format which is # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. #pop3_uidl_format = %v.%u pop3_uidl_format = %08Xu%08Xv # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/pkg/lib/dovecot/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. # oe-ns-eoh: # Outlook Express and Netscape Mail breaks if end of headers-line is # missing. This option simply sends it if it's missing. #pop3_client_workarounds = } ## ## Authentication processes ## # Executable location #auth_executable = /usr/pkg/libexec/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # Authentication cache size in kilobytes. #auth_cache_size = 0 # Time to live in seconds for cached data. After this many seconds a cached # record is forced out of cache. #auth_cache_ttl = 3600 # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username character translations before it's looked up from databases. The # value contains series of from -> to characters. For example "#@/@" means # that '#' and '/' characters are translated to '@'. #auth_username_translation = # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. auth_verbose = no # Even more verbose logging for debugging purposes. Shows for example SQL # queries. auth_debug = no # Maximum number of dovecot-auth worker processes. They're used to execute # blocking passdb and userdb queries (eg. MySQL and PAM). They're # automatically created and destroyed as needed. #auth_worker_max_count = 30 auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous #mechanisms = plain digest-md5 cram-md5 mechanisms = plain # # Password database is used to verify user's password (and nothing more). # You can have multiple passdbs and userdbs. This is useful if you want to # allow both system users (/etc/passwd) and virtual users to login without # duplicating the system users into virtual database. # # http://wiki.dovecot.org/Authentication # # PAM authentication. Preferred nowadays by most systems. # Note that PAM can only be used to verify if user's password is correct, # so it can't be used as userdb. If you don't want to use a separate user # database (passwd usually), you can use static userdb. #passdb pam { # Service name or * as parameter. * means the authenticating service name # is used, eg. pop3 or imap. #args = dovecot #} # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. passdb passwd { } # /etc/shadow or similiar, using getspnam(). Deprecated by PAM nowadays. #passdb shadow { #} # passwd-like file with specified location #passdb passwd-file { # Path for passwd-file #args = #} # checkpassword executable authentication #passdb checkpassword { # Path for checkpassword binary #args = #} # SQL database passdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for example args = /usr/pkg/etc/dovecot-sql.conf } # LDAP database #passdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example #args = #} # vpopmail authentication #passdb vpopmail { #} # # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # # http://wiki.dovecot.org/Authentication # http://wiki.dovecot.org/VirtualUsers # # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. userdb passwd { } # passwd-like file with specified location #userdb passwd-file { # Path for passwd-file #args = #} # static settings generated from template #userdb static { # Template for settings. Can return anything a userdb could normally # return, eg.: uid, gid, home, mail, nice # # A few examples: # # args = uid=500 gid=500 home=/var/mail/%u # args = uid=500 gid=500 home=/home/%u mail=mbox:%h/mail nice=10 # #args = #} # SQL database userdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for example args = /usr/pkg/etc/dovecot-sql.conf } # LDAP database #userdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example #args = #} # vpopmail #userdb vpopmail { #} # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by userdb above. user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. # Note that valid_chroot_dirs isn't needed to use this setting. #chroot = # Number of authentication processes to create #count = 1 # Require a valid SSL client certificate or the authentication fails. #ssl_require_client_cert = no } # It's possible to export the authentication interface to other programs, # for example SMTP server which supports talking to Dovecot. Client socket # handles the actual authentication - you give it a username and password # and it returns OK or failure. So it's pretty safe to allow anyone access to # it. Master socket is used to a) query if given client was successfully # authenticated, b) userdb lookups. # listener sockets will be created by Dovecot's master process using the # settings given inside the auth section #auth default_with_listener { # mechanisms = plain # passdb passwd { # } # userdb pam { # } # socket listen { # master { # path = /var/run/dovecot/auth-master # #mode = 0600 # # Default user/group is the one who started dovecot-auth (root) # #user = # #group = # } # client { # path = /var/run/dovecot-auth-client # mode = 0660 # } # } #} # connect sockets are assumed to be already running, Dovecot's master # process only tries to connect to them. They don't need any other settings # than path for the master socket, as the configuration is done elsewhere. # Note that the client sockets must exist in login_dir. #auth external { # socket connect { # master { # path = /var/run/dovecot/auth-master # } # } #}

2 2

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

03 Apr '05

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

1 1

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

03 Apr '05

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

3 3

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

03 Apr '05

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

2 1

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

03 Apr '05

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

2 1

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

03 Apr '05

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

2 1

[Dovecot] dovecot don't start
by Luca Stancapiano 03 Apr '05

03 Apr '05

hi...I've a problem with dovecot 0.99.13-3 for fedora core 3. When I start dovecot with "service dovecot start" it seems to start succesful but it is a false message. It don't start and in /var/log/maillog I've this errors: Apr 1 15:37:00 edim dovecot: Dovecot starting up Apr 1 15:37:03 edim dovecot: Auth process died too early - shutting down Apr 1 15:37:03 edim dovecot: child 9593 (auth) returned error 127 Apr 1 15:37:03 edim pop3-login: fd_send(-1) failed: Broken pipe my configuration is : protocols = imap imaps pop3 pop3s imap_listen = [::] pop3_listen = [::] imaps_listen = [::] pop3s_listen = [::] ssl_cert_file = /usr/share/ssl/certs/dovecot.pem ssl_key_file = /usr/share/ssl/private/dovecot.pem login_dir = /var/run/dovecot-login login = imap login = pop3 mbox_locks = fcntl auth = default auth_mechanisms = plain auth_userdb = passwd auth_user = root what does it?

2 1

[Dovecot] new to dovecot, dealing with MH foders
by jerry scharf 03 Apr '05

03 Apr '05

Hello, I'm sorry if this is a repeat, a few choice searches into google didn't help and I found no search for the archives. I can no longer put of moving away from UW-IMAP. Dovecot certainly seems to be the right choice, but I am having problems getting it to do what I need it to for all my mail. The machine is running the dist version, 0.99.12. I have a system mailbox and a large MH mail tree (~25K messages.) I saw that dovecot didn't support mh trees like UW did. It looked like maildir would be a good common target. So I found a script that would convert the mbox to maildir and have adjusted postfix, and that all works fine. Then I found mh2maildir, and ran it over my entire mh tree. Then I tried just for a test copying one of the small top level directories under ~/Maildir, but my MUA (mulberry) doesn't see it. So how do I get dovecot to see things other than the inbox in maildir format? How can I easily test to see if it's dovecot's problem or the MUA? thanks for any help, jerry Jerry Scharf laguna way consulting

3 2

[Dovecot] dovecot-1.0-test65 + mysql build problem (sha1_result)
by Michael Goth 03 Apr '05

03 Apr '05

Hello all! When trying to build dovecot-1.0-test65 with mysql support I get the following error: ... /usr/local/mysql/lib/libmysqlclient.a(sha1.o)(.text+0x5c): In function `sha1_result': : multiple definition of `sha1_result' ../lib/liblib.a(sha1.o)(.text+0x830):/usr/local/src/dovecot/dovecot-1.0-test65/src/lib/sha1.c:242: first defined here /usr/lib/gcc-lib/i586-suse-linux/3.3.1/../../../../i586-suse-linux/bin/ld: Warning: size of symbol `sha1_result' changed from 158 in ../lib/liblib.a(sha1.o) to 126 in ../lib/liblib.a(sha1.o) collect2: ld returned 1 exit status make[3]: *** [dovecot-auth] Error 1 make[3]: Leaving directory `/usr/local/src/dovecot/dovecot-1.0-test65/src/auth' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/dovecot/dovecot-1.0-test65/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/dovecot/dovecot-1.0-test65' make: *** [all] Error 2 The version of mysql I'm using is 4.1.10a. Could this mean that dovecot uses a function ('sha1_result') that already exists in libmysqlclient.a? If not, can someone perhaps point me into the right direction where to look for the error? I can provide more details about my setup, if needed, of course. Regards, Michael

2 1

Re: [Dovecot] [ #14832]: Capital letters in POP3 logins
by Timo Sirainen 03 Apr '05

03 Apr '05

In CVS pass_query can now return "user" column to replace the username that was used to log in. Besides fixing character casing problems, it also allows login aliases.

1 0

[Dovecot] FC2 POP3/SMTP Configuration
by Linux Stuff 03 Apr '05

03 Apr '05

OK, let me try this again. . . . I'm a newbie to dovecot and a little bit less of a newbie to linux. I am in the process of moving my server from RH9 to FC2. The only obstacle remaining is my email. I run dovecot (v0.99.14) POP3 and sendmail (8.12.11-4.6) with Mozilla (1.4.2 and others), Thunderbird (1.0.2) and Netscape (7.1 on PC's, etc) mail clients - mostly PC's (W2K, WXP). They all can read their mail but none of the users can send any mail. I have also tested with Outlook and it works!? Ximian Evolution (1.4.6) also works!??? Depending on the state of the dovecot.conf file, I get the following: Mar 28 16:04:14 corvette sendmail[5810]: unable to open Berkeley db /etc/sasldb2: Invalid argument Mar 28 16:04:14 corvette sendmail[5810]: unable to open Berkeley db /etc/sasldb2: Invalid argument Mar 28 16:04:14 corvette sendmail[5810]: no secret in database Why do Outlook and Ximian work and the others do not? I know I must be missing something in my config file. Ideas?? Thanks

2 1

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

02 Apr '05

Hi all, Sorry if this is out of place, but I've seen people suggesting future functionality for Dovecot on here before. TBH I'm not completely sure if this would be possible in a LDA. Demon (an ISP) have extensions to POP3 they call "SDPS" - there's basically an extra command that can be called for an email and it gives the envelope rcpt and from addresses. I was wondering if there was any chance of future versions of Dovecot allowing something similar? Many thanks, Mark Lidstone IT and Network Support Administrator BMT SeaTech Ltd Grove House, Meridians Cross, 7 Ocean Way Ocean Village, Southampton. SO14 3TJ. UK Tel: +44 (0)23 8063 5122 Fax: +44 (0)23 8063 5144 E-Mail: mailto:mark.lidstone@bmtseatech.co.uk Website: www.bmtseatech.co.uk ======================================================================== == Confidentiality Notice and Disclaimer: The contents of this e-mail and any attachments are intended only for the use of the e-mail addressee(s) shown. If you are not that person, or one of those persons, you are not allowed to take any action based upon it or to copy it, forward, distribute or disclose the contents of it and you should please delete it from your system. BMT SeaTech Limited does not accept liability for any errors or omissions in the context of this e-mail or its attachments which arise as a result of Internet transmission, nor accept liability for statements which are those of the author and not clearly made on behalf of BMT SeaTech Limited. ======================================================================== ==

3 2

Re: [Dovecot] [ #14832]: Capital letters in POP3 logins
by Gerald V. Livingston II 02 Apr '05

02 Apr '05

I just tested and IMAP doesn't ignore case either. Remove the UPPER CASE maildir created by your POP3 login then do the same thing with an IMAP client. Set up the IMAP client to use an UPPER CASE username and when you log-in/refresh folders it creates the new UPPERCASE empty Maildir all over again. Crap, between this and the missing QUOTA feature I guess I'm gonna have to rip out Dovecot and use Courier. I really wanted to use Dovecot for it's speed with the indexing. What I don't understand is -- all usernames in my test database are stored in lower case -- shouldn't it simply fail to match and cause the login to fail? Can anyone point out how to force the match to be case sensitive? I'll investigate and get back to the list. It would be "nicer" though if Dovecot converted all username input to lower case before authenticating to maintain uniqueness of email addresses. Gerald On Wed, 30 Mar 2005 21:16:12 +0400 "support(a)majordomo.ru" <support(a)majordomo.ru> wrote: > Using dovecot (version 1.0-test59, with mysql-auth) I saw strange problem: > after authentication by POP3 in case that username given has capital letters, for example SupportTeam(a)majordomo.ru, > dovecot creates new maildir 'SupportTeam' for this username instead reading mails from existing maildir 'supportteam'. > Then dovecot scans created maildir 'SupportTeam' and returns 0 messages (sure:). > IMAP4 works fine in the same time. > Can I solve this problem or it is virtually "bug" of dovecot?

4 5

[Dovecot] dovecot authentication problem on OSX
by Mac Shabba 01 Apr '05

01 Apr '05

after reading good comments on dovecot i'm trying to get it going I've got an apple g4, with osx 10.3.8 Compile and install went fine. I can also start dovecot, and telnet to it...but I can't login Even before I try to auth i get this in the log: >>localhost dovecot: Dovecot starting up >>localhost imap-login: opendir(".") failed when trying to get list of authentication servers: Permission denied I can't find any reference to this error message, and I'm completely puzzled about it I just need to know how to figure out what is causing this...is it related to pam, folder permissions, server config, .... MacShabba

2 1

[Dovecot] Anybody tracking the GSSAPI patch?
by David B Harris 01 Apr '05

01 Apr '05

Hey all, I'm doing some Kerberos stuff at work, and I'm thinking it'd be nice if dovecot had GSSAPI support. I found http://dovecot.org/list/dovecot/2004-July/004039.html (thanks Colin :), but it's a long ways away from applying to the current stable tree. I'm wondering - has anybody else been keeping a local copy of this patch up to date? Thanks, Dave -- Arguing with an engineer is like wrestling with a pig in mud. After a while, you realise the pig is enjoying it. OpenPGP v4 key ID: 4096R/59DDCB9F Fingerprint: CC53 F124 35C0 7BC2 58FE 7A3C 157D DFD9 59DD CB9F Retreive from subkeys.pgp.net or risk key corruption

1 0

[Dovecot] test65 killed by SIGSEV
by Thomas Hummel 31 Mar '05

31 Mar '05

Hi, I had successfully set up dovecot-1.0-test62 + ldap pass/user db, but now I'm encoutering a SIGSEV problem with a similar set up of a brand new dovecot-1.0-test65 installation. The auth process is killed by a SIGSEV as reported in the error log file : dovecot: Mar 30 17:06:59 Error: child 28291 (auth) killed with signal 11 To be precise, the problem occurs in the "ldap_lookup_pass" function (auth/passdb-ldap.c) just before loging the ldap request parameters (auth_request_log_debug) and to actually perform the search (db_ldap_search). The signal occurs on the call of t_strarray_join(attr_names, ",") What I'm observing is that the "attr_names" array of the "passdb_ldap_conn" ldap connection doesn't seem to hold the right attributes : while in the test62 version it holded 'uid' and 'userPassword', it holds now 'uid' and 'homeDirectory'. As a matter of fact, the content of this array seem to change between the "preinit" and "init" passdb function and I'm not quite sure this is legal. So my client (actually just a test through telnet) gets a 'NO Temporary authentication failure'. Here's a gdb backtrace of the process : ------- Program received signal SIGSEGV, Segmentation fault. 0x08065bf6 in t_strarray_join (arr=0x807aa20, separator=0x8067b1a ",") at strfuncs.c:571 571 len = strlen(*arr); (gdb) bt full #0 0x08065bf6 in t_strarray_join (arr=0x807aa20, separator=0x8067b1a ",") at strfuncs.c:571 alloc_len = 8 sep_len = 1 len = 9 pos = 39 needed_space = 0 str = 0x806e488 "uid,homeDirectory,,,uidNumber,gidNumber" #1 0x080578a1 in ldap_lookup_pass (auth_request=0x8077a10, ldap_request=0x8077ab0) at passdb-ldap.c:181 conn = (struct ldap_connection *) 0x807a810 vars = (const struct var_expand_table *) 0x807a9a0 attr_names = (const char **) 0x807aa08 filter = 0x806e268 "(&(objectClass=posixAccount)(uid=dovetest))" base = 0x806e468 "ou=personnes, dc=pasteur, dc=fr" str = (string_t *) 0x806e268 #2 0x08050947 in auth_request_verify_plain (request=0x8077a10, password=0x806e198 "pass", callback=0x8054790 <verify_callback>) at auth-request.c:261 passdb = (struct passdb_module *) 0x806b9e0 result = -1077941592 cache_key = 0x646975 <Error reading address 0x646975: Bad address> __PRETTY_FUNCTION__ = "auth_request_verify_plain" ---Type <return> to continue, or q <return> to quit--- #3 0x0805486e in mech_plain_auth_continue (request=0x8077a10, data=0xffffffff <Error reading address 0xffffffff: Bad address>, data_size=6580597) at mech-plain.c:62 authenid = 0x806e181 "dovetest" error = 0xbfbfeaf8 "(ë¿¿²ø\004\b\020@\b\b\034\020\b\b(ë¿¿dø\004\b\002" pass = 0x806e198 "pass" i = 0 count = 2 #4 0x08051a80 in auth_request_handler_auth_begin (handler=0x8084010, args=0x808101c "1\tPLAIN\tservice=IMAP\tsecured\tlip=127.0.0.1\trip=127.0.0.1\tresp=AGRvdmV0ZXN0AHBhc3M=") at auth-request-handler.c:327 len = 20 mech = (struct mech_module *) 0x0 request = (struct auth_request *) 0x8077a10 list = (const char * const *) 0x806e114 name = 0x806e130 "resp" arg = 0x806e160 "\200á\006\b\016" initial_resp = 0x806e0de "AGRvdmV0ZXN0AHBhc3M=" initial_resp_data = (const void *) 0x646975 initial_resp_len = 0 id = 1 buf = (buffer_t *) 0x806e160 valid_client_cert = 0 ---Type <return> to continue, or q <return> to quit--- #5 0x0804f8b2 in auth_client_input (context=0x80785c0) at auth-client-connection.c:144 conn = (struct auth_client_connection *) 0x80785c0 line = 0x8081017 "AUTH\t1\tPLAIN\tservice=IMAP\tsecured\tlip=127.0.0.1\trip=127.0.0.1\tresp=AGRvdmV0ZXN0AHBhc3M=" #6 0x0805f8dc in io_loop_handler_run (ioloop=0x8078000) at ioloop-poll.c:184 data = (struct ioloop_handler_data *) 0x806d080 pollfd = (struct pollfd *) 0x2 tv = {tv_sec = 1, tv_usec = 999555} io = (struct io *) 0x806d5c0 t_id = 2 msecs = 0 ret = 0 call = 1 #7 0x0805f319 in io_loop_run (ioloop=0x8078000) at ioloop.c:218 No locals. #8 0x080541dd in main (argc=1, argv=0x1) at main.c:311 foreground = 0 (gdb) ------- Thanks -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

1 2

[Dovecot] Pine and prefix - LIST command bug?
by Chris Wakelin 31 Mar '05

31 Mar '05

I've been having problems with Pine 4.62 talking to Dovecot 1.0 stable. It's fine when the folder collection path is empty, but if I have "~/mail/" or "mail/" it gives access errors (I'm using the "~/mail/", "mail/" etc. hidden namespaces for backwards compatability). It seems to me that Dovecot is not replying correctly to a "LIST" command with empty mailbox name: - Dovecot: xyz LIST "" "" * LIST (\NoSelect) "/" "" xyz LIST "~/mail/" "" * LIST (\NoSelect) "/" "" xyz LIST "mail/" "" * LIST (\NoSelect) "/" "" UW-IMAP; xyz LIST "" "" * LIST (\NoSelect) "/" "" xyz LIST "~/mail/" "" * LIST (\NoSelect) "/" ~/ xyz LIST "mail/" "" * LIST (\NoSelect) "/" mail/ RFC 2060 says: An empty ("" string) mailbox name argument is a special request to return the hierarchy delimiter and the root name of the name given in the reference. The value returned as the root MAY be null if the reference is non-rooted or is null. In all cases, the hierarchy delimiter is returned. This permits a client to get the hierarchy delimiter even when no mailboxes by that name currently exist. Mind you, it looks like at least our UW-IMAP also gets it wrong for "~/mail/". Of course, I may be misunderstanding something! Best Wishes, Chris --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 8

Re: [Dovecot] [ #14832]: Capital letters in POP3 logins
by Jakob Hirsch 31 Mar '05

31 Mar '05

support(a)majordomo.ru wrote: > Can I solve this problem or it is virtually "bug" of dovecot? No bug, just the "garbage in, garbage out" principle. Mysql's string matches are case-insensisitive by default, so when dovecot asks mysql for the user information of UsEr1, it will get the information of user1 and therefore assumes that UsEr1 is a valid login. It's not dovecot's fault. If you want the match case-insensitive (so UsEr1 will be rejected), add the BINARY attribute to the userid field or change your query to '... WHERE BINARY userid = "%u"' in password_query and user_query. If you want to allow logins as UsEr1 (and let him access user1's mail), you have to change your dovecot.conf, I think. Use %h instead of %u there, and let user_query return the home directory with something like 'SELECT CONCAT('/var/spool/vmail/',LOWER(userid)) AS home, ...'.

3 5

[Dovecot] [ #14832]: Capital letters in POP3 logins
by support＠majordomo.ru 30 Mar '05

30 Mar '05

Здравствуйте, Это автоматически созданное сообщение, просьба не отвечать на него. Ваше письмо, отправленное на support(a)majordomo.ru с темой "Capital letters in POP3 logins", получено почтовой системой хостинг-провайдера Majordomo.ru. Вам ответят в ближайшее время. Вашему письму присвоен номер 14832 , если в дальнейшем Вы будете связываться с нами по данному вопросу, просьба его указать. С уважением, служба техподдержки Majordomo.ru. =========================================== URL http://www.majordomo.ru phone +7 812 3200732 phone +7 095 7272278 e-mail support(a)majordomo.ru

1 0

[Dovecot] [ #14832]: Capital letters in POP3 logins
by support＠majordomo.ru 30 Mar '05

30 Mar '05

Hello all! I'm newbie here :) Using dovecot (version 1.0-test59, with mysql-auth) I saw strange problem: after authentication by POP3 in case that username given has capital letters, for example SupportTeam(a)majordomo.ru, dovecot creates new maildir 'SupportTeam' for this username instead reading mails from existing maildir 'supportteam'. Then dovecot scans created maildir 'SupportTeam' and returns 0 messages (sure:). IMAP4 works fine in the same time. Can I solve this problem or it is virtually "bug" of dovecot? Thanks in advance! Vladimir

1 0

[Dovecot] Chrooting dovecot.
by BSD Mail 30 Mar '05

30 Mar '05

Greetings, I have installed Dovecot under FreeBSD 5_3 It is pretty impressive. I got SSL working with no problem for both imap and pop3. Besides that I do still want to chroot Dovecot. I noticed that there are some options in the dovecot.conf that are intended for this. Unfortunately online resources on how to do that can't be found on google. Although I'm running the server as user dovecot. I still do have this: dovecot pop3-login 491 1 tcp4 10.0.1.4:995 *:* dovecot pop3-login 490 1 tcp4 10.0.1.4:995 *:* dovecot pop3-login 489 1 tcp4 10.0.1.4:995 *:* dovecot imap-login 488 1 tcp4 10.0.1.4:993 *:* dovecot imap-login 487 1 tcp4 10.0.1.4:993 *:* dovecot imap-login 486 1 tcp4 10.0.1.4:993 *:* root dovecot 481 5 tcp4 10.0.1.4:993 *:* root dovecot 481 6 tcp4 10.0.1.4:995 *:* Fine for the first six lines it's doing what it's doing. But the last two lines are running as root. That is why I want to chroot the server. I would like if anyone can point me to some howto or notes on how to do so. If there is none I will have to configure a jail just for this purpose. Thanks in advance. -- Regards,

4 3

[Dovecot] Abort error in current CVS version
by Todd Burroughs 30 Mar '05

30 Mar '05

I just tried the latest version from CVS and got this error: dovecot: Mar 29 18:11:33 Error: 27526 IMAP(todd.bluegenesis.com): Corrupted index cache file /mailhome/new/t/b/todd.bluegenesis.com/.imap/INBOX/dovecot.index.cache: Duplicated field in header: hdr.RESENT-TO dovecot: Mar 29 18:11:33 Error: 27526 IMAP(todd.bluegenesis.com): file index-mail-headers.c: line 68 (index_mail_parse_header_finish): assertion failed: (match[match_idx] != mail->header_match_value + 1) dovecot: Mar 29 18:11:34 Error: child 27526 (imap) killed with signal 6 I deleted the index files, didn't help. I checked my mailbox and there aren't any mails with a duplicate "Resent-To" header. With older versions of dovecot, I still get this error, but it does not abort. (Using mbox, if it matters) Here's a backtrace: Core was generated by `imap'. Program terminated with signal 6, Aborted. #0 0xffffe410 in ?? () (gdb) bt #0 0xffffe410 in ?? () #1 0xbffff528 in ?? () #2 0x00000006 in ?? () #3 0x00006b86 in ?? () #4 0xb7ef1d41 in raise () from /lib/tls/libc.so.6 #5 0xb7ef3529 in abort () from /lib/tls/libc.so.6 #6 0x0809744a in i_internal_panic_handler ( fmt=0x6 <Address 0x6 out of bounds>, args=0x6b86 <Address 0x6b86 out of bounds>) at failures.c:374 #7 0x08097864 in i_panic ( format=0x80a3bcc "file %s: line %d (%s): assertion failed: (%s)") at failures.c:173 #8 0x080748cf in index_mail_parse_header (part=0x0, hdr=0x0, mail=0x80c2f20) at index-mail-headers.c:210 #9 0x08090963 in _read (stream=0x80c3be8) at istream-header-filter.c:170 #10 0x0809a293 in i_stream_read (stream=0x80c3c0c) at istream.c:51 #11 0x0809a4d1 in i_stream_read_data (stream=0x80c3c0c, data=0xbffff7c4, size=0xbffff7c8, threshold=58) at istream.c:229 #12 0x08092f5f in message_parse_header_next (ctx=0x80c1920, hdr_r=0xbffff7f8) at message-parser.c:735 #13 0x0809363e in message_parse_header (part=0x0, input=0x80c3c0c, hdr_size=0x0, callback=0x80757c0 <search_header>, context=0xbffff880) at message-parser.c:655 ---Type <return> to continue, or q <return> to quit--- #14 0x08075640 in index_storage_search_next (_ctx=0x80c5568, mail=0x80c2f20) at index-search.c:502 #15 0x0808b705 in mailbox_search_next (ctx=0x6, mail=0x80c2f20) at mail-storage.c:405 #16 0x08057bee in cmd_search (cmd=0x80ba980) at cmd-search.c:33 #17 0x080594f5 in _client_input (context=0x80ba940) at client.c:334 #18 0x0809c5da in io_loop_handler_run (ioloop=0x80b95b0) at ioloop-poll.c:184 #19 0x0809bcf9 in io_loop_run (ioloop=0x80b95b0) at ioloop.c:218 #20 0x080603a7 in main (argc=1, argv=0xbffffa74, envp=0xbffffa7c) at main.c:229 (gdb)

1 0

[Dovecot] Compile Error in current CVS
by Todd Burroughs 30 Mar '05

30 Mar '05

Had a small error with the current CVS version. It was in deliver.c. Here's a fix. I'm assuming that adding NULL is correct ;-) dovecot.2005-03-29/src # diff deliver/deliver.c.orig deliver/deliver.c 86c86 < box = mailbox_open(storage, mailbox, MAILBOX_OPEN_FAST | --- > box = mailbox_open(storage, mailbox, NULL, MAILBOX_OPEN_FAST | Here's the symptoms: deliver.c: In function `save_mail': deliver.c:87: warning: passing arg 3 of `mailbox_open' makes pointer from integer without a cast deliver.c:87: error: too few arguments to function `mailbox_open' make[3]: *** [deliver.o] Error 1 make[3]: Leaving directory `/services/src/9.2/dovecot/dovecot.2005-03-29/src/deliver' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/services/src/9.2/dovecot/dovecot.2005-03-29/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/services/src/9.2/dovecot/dovecot.2005-03-29' make: *** [all] Error 2

1 0

[Dovecot] Checkin 1.37 of src/lib-storage/mail-storage.c
by Geo Carncross 29 Mar '05

29 Mar '05

Checkin 1.37 of src/lib-storage/mail-storage.c added a parameter to mailbox_open() but this broke building src/deliver/deliver.c as revision 1.2 doesn't use the new parameter. It looks like save_mail() of src/deliver/deliver.c calls mailbox_open() and it looks like it might work fine if it were to use a (struct istream *)0 as the third parameter (instead of the flags) -- but I don't use deliver [yet], so I don't have any adequate way to test this. -- Internet Connection High Quality Web Hosting http://www.internetconnection.net/

1 0

[Dovecot] mbox zlib compression plugin
by Timo Sirainen 29 Mar '05

29 Mar '05

Some people have been asking this forever, but because it wasn't possible to implement it as a plugin, I hadn't done it. Now, due to some API changes for other purposes, it was suddenly easy. So, if you want to try it, grab the latest CVS code / nightly CVS snapshot and http://dovecot.org/patches/1.0/zlib-plugin.tar.gz Compilation instructions inside zlib-plugin.c file. What it does is check if mbox name ends with ".gz", if so it opens it as read-only using zlib. If the file isn't actually zlib compressed, zlib seems to be able to still access it as a normal file (but it's still read-only). It should be possible to implement it for maildir files as well by hooking into mail_get_stream().

1 0

[Dovecot] FC2 POP Configurtion
by Linux Stuff 29 Mar '05

29 Mar '05

I'm a newbie to dovecot and a little bit less of a newbit to linux. I am in the process of moving my server from RH9 to FC2. The only obstacle remaining is my email. I run sendmail with netscape mail clients - mostly PC's. They all can read their mail but none of the users can send. Depending on the state of the dovecot.conf file, I get the following: Mar 28 16:04:14 corvette sendmail[5810]: unable to open Berkeley db /etc/sasldb2: Invalid argument Mar 28 16:04:14 corvette sendmail[5810]: unable to open Berkeley db /etc/sasldb2: Invalid argument Mar 28 16:04:14 corvette sendmail[5810]: no secret in database I know I must be missing something, probably trivial. Does someone have a simple, easy-to-read, config file for dovecot pop running with sendmail? Thanks

1 0

[Dovecot] error creating storage
by Alex 28 Mar '05

28 Mar '05

Hello, I have some problems. I am getting the error: Mar 28 21:24:01 APOLLO imap(alex(a)mydomain.nl): Failed to create storage with data: mydomain.nl/alex What is wrong with it? I think it has something to do with the rights or something. Can anyone tell me what to do? Thank you, Alex

1 0

[Dovecot] Re: telnet to pop3 problem
by Obantec Support 28 Mar '05

28 Mar '05

Hi Yes i was :( did the change you suggested and that bit works now. Off to look at using syslog to how dovecot logging works. Mark ----- Original Message ----- From: "Herbert" <herbert(a)oslo.ath.cx> To: "Obantec Support" <support(a)obantec.net> Sent: Monday, March 28, 2005 4:31 PM Subject: Re: telnet to pop3 problem > Obantec Support <support(a)obantec.net> wrote: > > Hi > > > > default_mail_env was commented out. when i set it to > > > > default_mail_env = maildir:/var/spool/mail/%u > ^^^^^^^ > You are not using maildir, are you? > > > it fails to deliver maillog shows. > > Mar 28 15:34:31 proteus2a pop3(obantec): > > lstat(/var/spool/mail/obantec/cur) failed: Not a directory > > > > /var/spool/mail exists what is /cur ??? all i want is > > /var/spool/mail/obantec where obantec is the mail file. > > Maybe you should use: > > default_mail_env = mbox:/var/spool/mail/%u > > - Herbert > > > -- > No virus found in this incoming message. > Checked by AVG Anti-Virus. > Version: 7.0.308 / Virus Database: 266.8.4 - Release Date: 27/03/2005 > >

1 0

[Dovecot] telnet to pop3 problem
by Obantec Support 28 Mar '05

28 Mar '05

Hi I have 1 customer who is having issues with pop3 on FC3 telnet mail.hisdomain.com 110 +OK dovecot ready. user beachy -ERR Unknown command. user beachy +OK pass letmein +OK Logged in. list -ERR No INBOX for user. pass & username fake for this example! Mark

2 2

[Dovecot] Wiki upgrade
by Timo Sirainen 28 Mar '05

28 Mar '05

Upgraded Moin wiki from 1.2.x -> 1.3.4 which required migrating old data using several scripts and reconfiguring the whole thing. If you see any problems, please mail me.

1 0

[Dovecot] Address with whitespace shows as ""@MISSING_DOMAIN
by Chris Wakelin 28 Mar '05

28 Mar '05

It seems that Dovecot gets confused when presented with a header like: From: someone(a)somewhere.org i.e. with leading whitespace and no "friendly name" This shows up as ""@MISSING_DOMAIN in clients, such as Pine, that believe what Dovecot tells them rather than parsing the headers themselves (e.g. Thunderbird). Here's a sample IMAP session: xyz FETCH 728 ENVELOPE * 728 FETCH (ENVELOPE ("Tue, 22 Mar 2005 10:10:50 +0100 (BST)" "Test" ((NIL NIL "" "MISSING_DOMAIN")) ((NIL NIL "c.d.wakelin" "reading.ac.uk")) ((NIL NIL "" "MISSING_DOMAIN")) ((NIL NIL "" "MISSING_DOMAIN")) NIL NIL NIL "<Pine.GSO.3.96.1010704101043.17798B-100000@suma3>")) xyz OK Fetch completed. Here's UW-IMAP on the same mailbox: . FETCH 729 ENVELOPE * 729 FETCH (ENVELOPE ("Tue, 22 Mar 2005 10:10:50 +0100 (BST)" "Test" ((NIL NIL "c.d.wakelin" "reading.ac.uk")) ((NIL NIL "c.d.wakelin" "reading.ac.uk")) ((NIL NIL "c.d.wakelin" "reading.ac.uk")) ((NIL NIL "c.d.wakelin" "reading.ac.uk")) NIL NIL NIL "<Pine.GSO.3.96.1010704101043.17798B-100000@suma3>")) . OK FETCH completed I'm not sure I read the RFC correctly, but it looks like whitespace is allowed (and if it wasn't, I'd expect our MTA, Exim to fix it on delivery). There's a particular member of one of the UK academic computing mailing lists who always seems to do this, but I'm not sure how common a problem it is! Best Wishes, Chris --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 2

[Dovecot] Troubleshooting help
by Paul Michael Reilly 28 Mar '05

28 Mar '05

Somehow, hopefully to be determined, I got my Thunderbird/dovecot Fedora Core 3 configuration into a real snit, such that I can no longer access my INBOX. When Thunderbird tries to get the INBOX content (or get new mail) it reports "The current command did not succeed. The mail server responded: Invalid messageset: -2147483648:*." Scouring logs and googling has come up empty. Now I'm flailing at trying to get to a state that this problem does not exist. I'd like to understand how this situation arose and how to deal with it better if it happens to any other users on my mail server. Thanks, -pmr

3 3

[Dovecot] cannot select
by juri vrljicak 28 Mar '05

28 Mar '05

hi everybody, Found many many answers in here but...not this one. My imap client displays all of the folders but not the inbox one (cannot select inbox). Paths in imap.passwd seem to be fine. using mbox format and error log says "fail with mbox file..is a directory" which i already know. do i have to create a file? and what about valid uids and gids, i had some trouble with that too. well defined and nevertheless dropped. (using netbsd dove sqmail) regards _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

2 1

[Dovecot] test65 "deliver" LDA bug
by "Branko F. Gračnar" 28 Mar '05

28 Mar '05

Hello. I've tried to implement dovecot's deliver LDA to my home mailserver. I've run into troubles :) dovecot-deliver.conf: -- snip -- mail = maildir:%h/Maildir:INBOX=maildir:%h/Maildir mbox_read_locks = flock mbox_write_locks = flock -- snip -- when i run: deliver -d bfg < email.txt dovecot delivers message to ~/Maildir/maildir/new It acctually creates "maildir" folder inside real maildir folder. If i try to list messages via Outlook express mail client, OE reports entire folder list, but also lists one message "which no longer exists on server". If i remove ~/Maildir/maildir folder this message dissaperas from OE imap folder listing. Test scenario: 1. start dovecot 2. try to deliver message using "deliver" program (succeedes) 3. try to open INBOX via imap: Outlook Express: - reports INBOX message listing with one message, which "doesn't exist on server anymore" - the next delivery test with "deliver" LDA fails (lots of nanosleep() calls) Thunderbird: - reports that there are NO messages in INBOX - still can delivery messages with "deliver" LDA deliver strace output (search for EVIL CODE string): --- snip --- execve("/opt/dovecot/libexec/dovecot/deliver", ["/opt/dovecot/libexec/dovecot/deliver", "-d", "bfg"], [/* 42 vars */]) = 0 uname({sys="Linux", node="frost", ...}) = 0 brk(0) = 0x80af7cc mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb28ee000 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=29220, ...}) = 0 mmap2(NULL, 29220, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb28e6000 close(3) = 0 open("/lib/libdl.so.2", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0 \r\0\000"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=9604, ...}) = 0 mmap2(NULL, 11364, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x5837000 mmap2(0x5839000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1) = 0x5839000 close(3) = 0 open("/lib/libc.so.6", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220T\1"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=1207404, ...}) = 0 mmap2(NULL, 1132300, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x583a000 mmap2(0x5949000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x10f) = 0x5949000 mmap2(0x594c000, 9996, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x594c000 close(3) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb28e5000 set_thread_area({entry_number:-1 -> 6, base_addr:0xb28e56b0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0 munmap(0xb28e6000, 29220) = 0 open("/dev/urandom", O_RDONLY) = 3 read(3, "\362yOO", 4) = 4 close(3) = 0 time(NULL) = 1111840485 brk(0) = 0x80af7cc brk(0x80d87cc) = 0x80d87cc brk(0x80d9000) = 0x80d9000 uname({sys="Linux", node="frost", ...}) = 0 cat: 1111836380.P11693Q0M524017.frost:2,S: No such file or directory getpid() = 23206 rt_sigaction(SIGHUP, {0x8093a90, [], SA_RESTORER, 0x58625b8}, NULL, 8) = 0 rt_sigaction(SIGUSR1, {0x8093a90, [], SA_RESTORER, 0x58625b8}, NULL, 8) = 0 rt_sigaction(SIGUSR2, {0x8093a90, [], SA_RESTORER, 0x58625b8}, NULL, 8) = 0 rt_sigaction(SIGINT, {0x8093ad0, [INT], SA_RESTORER|SA_RESTART, 0x58625b8}, {SIG_DFL}, 8) = 0 rt_sigaction(SIGTERM, {0x8093ad0, [TERM], SA_RESTORER|SA_RESTART, 0x58625b8}, {SIG_DFL}, 8) = 0 rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_DFL}, 8) = 0 rt_sigaction(SIGALRM, {SIG_IGN}, {SIG_DFL}, 8) = 0 gettimeofday({1111840485, 349252}, {4294967236, 0}) = 0 open("/opt/dovecot/etc/dovecot-deliver.conf", O_RDONLY|O_LARGEFILE) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=111, ...}) = 0 pread(3, "#\n#\n# \n\nmail = maildir:%h/Maildi"..., 1024, 0) = 111 pread(3, "", 913, 111) = 0 close(3) = 0 socket(PF_UNIX, SOCK_STREAM, 0) = 3 fcntl64(3, F_GETFL) = 0x2 (flags O_RDWR) fcntl64(3, F_SETFL, O_RDWR|O_NONBLOCK) = 0 connect(3, {sa_family=AF_UNIX, path="/var/run/dovecot/auth-master"}, 110) = 0 fstat64(3, {st_mode=S_IFSOCK|0777, st_size=0, ...}) = 0 _llseek(3, 0, 0xb71716b0, SEEK_CUR) = -1 ESPIPE (Illegal seek) getsockname(3, {sa_family=AF_UNIX, path=L '"}, [2]) = 0 write(3, "VERSION\t1\t0\nUSER\t1\tbfg\n", 23) = 23 poll([{fd=3, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL, revents=POLLIN}], 1, 2147483647) = 1 gettimeofday({1111840485, 361824}, {4294967236, 0}) = 0 read(3, "VERSION\t1\t0\nSPID\t29143\n", 4096) = 23 poll([{fd=3, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL, revents=POLLIN}], 1, 2147483647) = 1 gettimeofday({1111840485, 364325}, {4294967236, 0}) = 0 read(3, "USER\t1\tbfg\tsystem_user=bfg\tuid=1"..., 4073) = 66 getgid32() = 0 setgid32(100) = 0 setgroups32(1, [100]) = 0 setuid32(1000) = 0 setuid32(0) = -1 EPERM (Operation not permitted) getgid32() = 100 getegid32() = 100 setgid32(0) = -1 EPERM (Operation not permitted) lstat64("maildir/cur", 0xb7171640) = -1 ENOENT (No such file or directory) mkdir("maildir/cur", 0770) = -1 ENOENT (No such file or directory) ********* EVIL CODE ********* mkdir("maildir", 0770) = 0 mkdir("maildir/cur", 0770) = 0 lstat64("maildir/new", 0xb7171640) = -1 ENOENT (No such file or directory) mkdir("maildir/new", 0770) = 0 lstat64("maildir/tmp", 0xb7171640) = -1 ENOENT (No such file or directory) mkdir("maildir/tmp", 0770) = 0 ********* EVIL CODE ********* fcntl64(0, F_GETFL) = 0 (flags O_RDONLY) fcntl64(0, F_SETFL, O_RDONLY|O_NONBLOCK) = 0 fstat64(0, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0 lstat64("maildir/cur", {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0 lstat64("maildir/new", {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0 lstat64("maildir/tmp", {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0 stat64("/export/home/bfg/Maildir", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0 stat64("maildir/dovecot-shared", 0xb7171620) = -1 ENOENT (No such file or directory) time(NULL) = 1111840485 open("/export/home/bfg/Maildir/dovecot.index", O_RDWR|O_LARGEFILE) = 4 alarm(120) = 0 fcntl64(4, F_SETLKW64, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}, 0xb7171410) = 0 alarm(0) = 120 fstat64(4, {st_mode=S_IFREG|0600, st_size=144, ...}) = 0 mmap2(NULL, 144, PROT_READ|PROT_WRITE, MAP_SHARED, 4, 0) = 0xb28ed000 open("/export/home/bfg/Maildir/dovecot.index.log", O_RDWR|O_LARGEFILE) = 5 fstat64(5, {st_mode=S_IFREG|0600, st_size=16504, ...}) = 0 pread(5, "\1\0\30\0\223LEB\1\0\0\0\0\0\0\0\0\0\0\0\223LEB", 24, 0) = 24 open("/export/home/bfg/Maildir/dovecot.index.cache", O_RDWR|O_LARGEFILE) = 6 fstat64(6, {st_mode=S_IFREG|0600, st_size=1202176, ...}) = 0 mmap2(NULL, 1202176, PROT_READ, MAP_SHARED, 6, 0) = 0xb27bf000 fcntl64(4, F_SETLK64, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}, 0xb7171470) = 0 alarm(120) = 0 fcntl64(5, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xb71714b0) = 0 alarm(0) = 120 stat64("/export/home/bfg/Maildir/dovecot.index.log", {st_mode=S_IFREG|0600, st_size=16504, ...}) = 0 fstat64(5, {st_mode=S_IFREG|0600, st_size=16504, ...}) = 0 mmap2(NULL, 16504, PROT_READ, MAP_SHARED, 5, 0) = 0xb27ba000 madvise(0xb27ba000, 16504, MADV_SEQUENTIAL) = 0 fstat64(4, {st_mode=S_IFREG|0600, st_size=144, ...}) = 0 stat64("/export/home/bfg/Maildir/dovecot.index", {st_mode=S_IFREG|0600, st_size=144, ...}) = 0 fcntl64(4, F_SETLK64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xb71714b0) = 0 write(2, "Error: ", 7Error: ) = 7 write(2, "Fixed index file /export/home/bf"..., 89Fixed index file /export/home/bfg/Maildir/dovecot.index: first_recent_uid_lowwater 3 -> 1) = 89 write(2, "\n", 1 ) = 1 msync(0xb28ed000, 120, MS_SYNC) = 0 fcntl64(4, F_SETLK64, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}, 0xb71714f0) = 0 fcntl64(5, F_SETLK64, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}, 0xb71714f0) = 0 stat64("maildir/new", {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0 stat64("maildir/cur", {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0 fstat64(4, {st_mode=S_IFREG|0600, st_size=144, ...}) = 0 stat64("/export/home/bfg/Maildir/dovecot.index", {st_mode=S_IFREG|0600, st_size=144, ...}) = 0 alarm(120) = 0 fcntl64(5, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xb7171560) = 0 alarm(0) = 120 stat64("/export/home/bfg/Maildir/dovecot.index.log", {st_mode=S_IFREG|0600, st_size=16504, ...}) = 0 fstat64(5, {st_mode=S_IFREG|0600, st_size=16504, ...}) = 0 fstat64(4, {st_mode=S_IFREG|0600, st_size=144, ...}) = 0 stat64("/export/home/bfg/Maildir/dovecot.index", {st_mode=S_IFREG|0600, st_size=144, ...}) = 0 alarm(120) = 0 fcntl64(4, F_SETLKW64, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}, 0xb7171570) = 0 alarm(0) = 120 fstat64(4, {st_mode=S_IFREG|0600, st_size=144, ...}) = 0 stat64("/export/home/bfg/Maildir/dovecot.index", {st_mode=S_IFREG|0600, st_size=144, ...}) = 0 fcntl64(4, F_SETLK64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xb7171470) = 0 _llseek(4, 0, [144], SEEK_END) = 0 write(4, "\0\0\0\0\0\0\0\0\0\0\0\0", 12) = 12 fstat64(4, {st_mode=S_IFREG|0600, st_size=156, ...}) = 0 mmap2(NULL, 156, PROT_READ|PROT_WRITE, MAP_SHARED, 4, 0) = 0xb27b9000 open("/etc/localtime", O_RDONLY) = 7 fstat64(7, {st_mode=S_IFREG|0644, st_size=696, ...}) = 0 fstat64(7, {st_mode=S_IFREG|0644, st_size=696, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb27b8000 read(7, "TZif\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\6\0\0\0\6\0"..., 4096) = 696 close(7) = 0 munmap(0xb27b8000, 4096) = 0 open("/etc/localtime", O_RDONLY) = 7 fstat64(7, {st_mode=S_IFREG|0644, st_size=696, ...}) = 0 close(7) = 0 msync(0xb27b9000, 156, MS_SYNC) = 0 fcntl64(4, F_SETLK64, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}, 0xb7171470) = 0 umask(0177) = 022 time(NULL) = 1111840485 lstat64("maildir/dovecot-uidlist.lock", 0xb71714c0) = -1 ENOENT (No such file or directory) stat64("maildir/temp.frost.23206.19bb83d2a70b22b7", 0xb7171490) = -1 ENOENT (No such file or directory) open("maildir/temp.frost.23206.19bb83d2a70b22b7", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0666) = 7 link("maildir/temp.frost.23206.19bb83d2a70b22b7", "maildir/dovecot-uidlist.lock") = 0 unlink("maildir/temp.frost.23206.19bb83d2a70b22b7") = 0 fstat64(7, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0 umask(022) = 0177 open("maildir/dovecot-uidlist", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("maildir/new", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 8 fstat64(8, {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0 fcntl64(8, F_SETFD, FD_CLOEXEC) = 0 getdents64(8, /* 2 entries */, 4096) = 48 getdents64(8, /* 0 entries */, 4096) = 0 close(8) = 0 open("maildir/cur", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 8 fstat64(8, {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0 fcntl64(8, F_SETFD, FD_CLOEXEC) = 0 getdents64(8, /* 2 entries */, 4096) = 48 getdents64(8, /* 0 entries */, 4096) = 0 close(8) = 0 fstat64(4, {st_mode=S_IFREG|0600, st_size=156, ...}) = 0 mmap2(NULL, 156, PROT_READ|PROT_WRITE, MAP_SHARED, 4, 0) = 0xb27b8000 pwrite(5, "\0\0\0\0\221\315\0\20", 8, 16504) = 8 pwrite(5, "\1\0\0\0\1\0\0\0", 8, 16512) = 8 pwrite(5, "\200\200\200\204 \0\0\20", 8, 16520) = 8 pwrite(5, "\34\0\4\0\1\0\0\0", 8, 16528) = 8 fsync(5) = 0 pwrite(5, "\200\200\200\204", 4, 16504) = 4 fstat64(5, {st_mode=S_IFREG|0600, st_size=16536, ...}) = 0 munmap(0xb27ba000, 16504) = 0 mmap2(NULL, 16536, PROT_READ, MAP_SHARED, 5, 0) = 0xb27ba000 madvise(0xb27ba000, 16536, MADV_SEQUENTIAL) = 0 fstat64(4, {st_mode=S_IFREG|0600, st_size=156, ...}) = 0 stat64("/export/home/bfg/Maildir/dovecot.index", {st_mode=S_IFREG|0600, st_size=156, ...}) = 0 fcntl64(4, F_SETLK64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xb7171460) = 0 munmap(0xb27b9000, 156) = 0 munmap(0xb27b8000, 156) = 0 umask(0) = 022 open("/export/home/bfg/Maildir/dovecot.index.tmp", O_RDWR|O_CREAT|O_TRUNC|O_LARGEFILE, 0600) = 8 umask(022) = 0 write(8, "\7\0x\0\220\0\0\0\f\0\0\0\1\10\4\0\223LEB\0\0\0\0\223L"..., 120) = 120 write(8, "\0\0\0\0\224LEB\10\0\4\0\4\0\5\0cache\0\0\0", 24) = 24 close(8) = 0 fcntl64(4, F_SETLK64, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}, 0xb7171460) = 0 fsync(4) = 0 rename("/export/home/bfg/Maildir/dovecot.index.tmp", "/export/home/bfg/Maildir/dovecot.index") = 0 fcntl64(4, F_SETLK64, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}, 0xb7171530) = 0 fcntl64(5, F_SETLK64, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}, 0xb7171530) = 0 lstat64("maildir/dovecot-uidlist.lock", {st_mode=S_IFREG|0600, st_size=0, ...}) = 0 unlink("maildir/dovecot-uidlist.lock") = 0 close(7) = 0 munmap(0xb28ed000, 144) = 0 stat64("maildir/tmp/1111840485.P23206Q0M364325.frost", 0xb7171660) = -1 ENOENT (No such file or directory) umask(0) = 022 open("maildir/tmp/1111840485.P23206Q0M364325.frost", O_WRONLY|O_CREAT|O_EXCL|O_LARGEFILE, 0600) = 7 umask(022) = 0 _llseek(7, 0, [0], SEEK_CUR) = 0 fstat64(7, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0 poll([{fd=0, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL, revents=POLLHUP}], 1, 2147483647) = 1 gettimeofday({1111840485, 393090}, {4294967236, 0}) = 0 read(0, "", 4096) = 0 fsync(7) = 0 close(7) = 0 alarm(120) = 0 fcntl64(5, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xb7171590) = 0 alarm(0) = 120 stat64("/export/home/bfg/Maildir/dovecot.index.log", {st_mode=S_IFREG|0600, st_size=16536, ...}) = 0 fstat64(5, {st_mode=S_IFREG|0600, st_size=16536, ...}) = 0 fstat64(4, {st_mode=S_IFREG|0600, st_size=156, ...}) = 0 stat64("/export/home/bfg/Maildir/dovecot.index", {st_mode=S_IFREG|0600, st_size=144, ...}) = 0 open("/export/home/bfg/Maildir/dovecot.index", O_RDWR|O_LARGEFILE) = 7 alarm(120) = 0 fcntl64(7, F_SETLKW64, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}, 0xb7171410) = 0 alarm(0) = 120 fstat64(7, {st_mode=S_IFREG|0600, st_size=144, ...}) = 0 mmap2(NULL, 144, PROT_READ|PROT_WRITE, MAP_SHARED, 7, 0) = 0xb28ed000 fcntl64(7, F_SETLK64, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}, 0xb7171440) = 0 close(4) = 0 alarm(120) = 0 fcntl64(7, F_SETLKW64, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}, 0xb71715a0) = 0 alarm(0) = 120 umask(0177) = 022 time(NULL) = 1111840485 lstat64("maildir/dovecot-uidlist.lock", 0xb71714f0) = -1 ENOENT (No such file or directory) stat64("maildir/temp.frost.23206.187e2a44c13cb5c3", 0xb71714c0) = -1 ENOENT (No such file or directory) open("maildir/temp.frost.23206.187e2a44c13cb5c3", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0666) = 4 link("maildir/temp.frost.23206.187e2a44c13cb5c3", "maildir/dovecot-uidlist.lock") = 0 unlink("maildir/temp.frost.23206.187e2a44c13cb5c3") = 0 fstat64(4, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0 umask(022) = 0177 open("maildir/dovecot-uidlist", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) fcntl64(5, F_SETLK64, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}, 0xb7171560) = 0 fcntl64(7, F_SETLK64, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}, 0xb7171510) = 0 link("maildir/tmp/1111840485.P23206Q0M364325.frost", "maildir/new/1111840485.P23206Q0M364325.frost") = 0 unlink("maildir/tmp/1111840485.P23206Q0M364325.frost") = 0 alarm(120) = 0 fcntl64(7, F_SETLKW64, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}, 0xb71715b0) = 0 alarm(0) = 120 alarm(120) = 0 fcntl64(5, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xb7171530) = 0 alarm(0) = 120 stat64("/export/home/bfg/Maildir/dovecot.index.log", {st_mode=S_IFREG|0600, st_size=16536, ...}) = 0 fstat64(5, {st_mode=S_IFREG|0600, st_size=16536, ...}) = 0 pwrite(5, "\0\0\0\0\2\0\0\20", 8, 16536) = 8 pwrite(5, "\1\0\0\0 \0\0\0", 8, 16544) = 8 fsync(5) = 0 pwrite(5, "\200\200\200\204", 4, 16536) = 4 fcntl64(5, F_SETLK64, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}, 0xb7171550) = 0 fcntl64(7, F_SETLK64, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}, 0xb7171650) = 0 write(4, "1 1111837843 2\n1 1111840485.P232"..., 50) = 50 utime("maildir/dovecot-uidlist.lock", [2005/03/26-13:34:45, 2005/03/26-13:34:45]) = 0 fsync(4) = 0 rename("maildir/dovecot-uidlist.lock", "maildir/dovecot-uidlist") = 0 close(4) = 0 exit_group(75) SHELL EXIT CODE: 0 --- snip --- Best regards, Brane

2 1

[Dovecot] Another imap crash...
by Todd Burroughs 26 Mar '05

26 Mar '05

The segfault problem that was happening seems to be fixed. I'm still getting some "(imap) killed with signal 6" errors. I just noticed that it did get one segfault. Unfortunately, I don't have a core file. I'll try to get one if this happens again. Here's the error messages, not sure if it will help. I'm using the CVS copy from March 24. dovecot: Mar 26 05:28:20 Error: 4282 IMAP(support): Corrupted index cache file /mailhome/new/s/support/.imap/INBOX/dovecot.index.cache: indexid changed dovecot: Mar 26 05:28:20 Error: 4282 IMAP(support): Corrupted transaction log file /mailhome/new/s/support/.imap/INBOX/dovecot.index.log: invalid indexid (1111832898 != 1111831599) dovecot: Mar 26 05:28:20 Error: 4282 IMAP(support): Corrupted index file /mailhome/new/s/support/.imap/INBOX/dovecot.index: Record UIDs are not ordered dovecot: Mar 26 05:28:20 Error: 4282 IMAP(support): Corrupted transaction log file /mailhome/new/s/support/.imap/INBOX/dovecot.index.log: invalid indexid (1111831599 != 0) dovecot: Mar 26 05:28:20 Error: 4282 IMAP(support): Corrupted index file /mailhome/new/s/support/.imap/INBOX/dovecot.index: Record UIDs are not ordered dovecot: Mar 26 05:28:20 Error: child 4282 (imap) killed with signal 11 Todd Burroughs

1 0

[Dovecot] quota issue POP3
by Obantec Support 26 Mar '05

26 Mar '05

Hi Just u/g to RH FC3 from RH8.0 which seemed to work fine with quotas. I have quotas for usernames set up as /home/domain/domainX/username/ for web space 50MB say 48MB used so 2MB free and /var/mail/spool/username for email. 100MB (60MB used so 40MB is available). /var/mail/username is symbolic linked via to spool/mail under /var dovecot seems to be using the quota for /home/.. and sees only 2MB so refuses to write file back. maillog is reporting (username and IP replaced). Mar 16 13:20:03 proteus2a pop3-login: Login: username [11.22.33.44] Mar 16 13:20:03 proteus2a pop3(username): Error rewriting mbox file /var/mail/username: Disk quota exceeded Mar 16 13:20:03 proteus2a pop3(username): write() failed with mbox file /var/mail/username: Disk quota exceeded i am assuming this is when pop3 login is trying to re-write file back when deleting emails. Mark -- Obantec Support www.obantec.net 0845 458 3121 WebHosting and Domains Nominet UK Tag Holder CentralNic Accredited Reseller

3 3

[Dovecot] Postfix SMTP AUTH patch updated
by Timo Sirainen 25 Mar '05

25 Mar '05

There was a small protocol change in later 1.0-test releases which made the older patches not to work. Updated the patch for Postfix 2.1.5 and added patch for Postfix 2.2.1. I also tested that it works with Dovecot 1.0-stable releases. So, if you're interested: http://dovecot.org/patches/postfix/

2 1

[Dovecot] Segfault in imap process
by Todd Burroughs 25 Mar '05

25 Mar '05

We've been testing dovecot for a while and I noticed yesterday that imap crashes quite often. It seems to be about even with SIGABRT and SIGSEGV. This one was SIGSEGV. Our system is SuSE Linux 9.2, 2.6.11.5 kernel (also happened with an older 2.6 kernel). Dovecot version is 1.0-test64 and was compiled with: "./configure --prefix=/services/dovecot --disable-ipv6" It's using mbox over NFS and I've configured "mmap_disable = yes". The mailbox that it crashed on is one of our support mailboxes and it is pretty busy. In the last 1/2 hour, it received over 100 emails. I had a look at the code, but didn't notice anything obvious. Thanks for any help... Here's the log messages: dovecot: Mar 22 18:22:23 Error: 19697 IMAP(support): UIDVALIDITY changed (1111532787 -> 1111533642) in mbox file /mailhome/new/s/support/mbox dovecot: Mar 22 18:22:26 Error: child 19697 (imap) killed with signal 11 and a backtrace: mail201:/services/dovecot/var/log # gdb /services/dovecot/libexec/dovecot/imap imap.core.pid19697 GNU gdb 6.2.1 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i586-suse-linux"...Using host libthread_db library "/lib/tls/libthread_db.so.1". Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. warning: current_sos: Can't read pathname for load map: Input/output error Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/tls/libc.so.6...done. Loaded symbols for /lib/tls/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 #0 0x08079f14 in mail_cache_sync_lost_handler (index=0x0) at mail-cache-sync-update.c:152 152 file_cache_invalidate(index->cache->file_cache, 0, (uoff_t)-1); (gdb) bt #0 0x08079f14 in mail_cache_sync_lost_handler (index=0x0) at mail-cache-sync-update.c:152 #1 0x0807bcfb in mail_index_map (index=0x80c24e8, force=0) at mail-index.c:792 #2 0x0807c870 in mail_index_try_open (index=0x80c24e8, lock_id_r=0xbffff68c) at mail-index.c:1064 #3 0x0807c9cf in mail_index_open (index=0x80c24e8, flags=5, lock_method=MAIL_INDEX_LOCK_FCNTL) at mail-index.c:1219 #4 0x08076025 in index_storage_mailbox_init (storage=0x80b7b90, box=0x80ac920, index=0x80c24e8, name=0x80a292f "INBOX", flags=Variable "flags" is not available. ) at index-storage.c:330 #5 0x08067cd8 in mbox_open (storage=0x80b7b90, name=0x80a292f "INBOX", flags=0) at mbox-storage.c:510 #6 0x08067ea4 in mbox_mailbox_open (_storage=0x80b7b90, name=0x80a292f "INBOX", flags=0) at mbox-storage.c:557 #7 0x08089305 in mailbox_open (storage=0x0, name=0x80a292f "INBOX", flags=0) at mail-storage.c:292 #8 0x08057ace in _cmd_select_full (cmd=0x80b7e80, readonly=0) at cmd-select.c:32 #9 0x08057ca1 in cmd_select (cmd=0x80b7e80) at cmd-select.c:99 #10 0x08059145 in _client_input (context=0x80b7e40) at client.c:334 #11 0x08099eca in io_loop_handler_run (ioloop=0x80b69e8) at ioloop-poll.c:184 #12 0x080995e9 in io_loop_run (ioloop=0x80b69e8) at ioloop.c:218 #13 0x0805fea7 in main (argc=1, argv=0xbffffa24, envp=0xbffffa2c) at main.c:229 (gdb) Todd Burroughs

2 2

Fw: [Dovecot] Auto Create Folders
by Chris L. Franklin 24 Mar '05

24 Mar '05

>> the problem might be: what would your mta do if: >> 1. the user never logged in via imap okay, so then they would never get there mail ? I guess I don't see where your going with this problem. >> 2. therefor no folders were created by dovecot .... Ok ?? >> 3. it has to deliver a spam message to the spam folder. Your right the filter would put it into the spam folder, witch it would created if it's not found. And as a side note the "Spam" folder was just a example folder name. Really for are needs it would be a folder called "Meetings" >> "so you have to ensure the folder existance at the user creation level >> imho. thats the logical point to do exactly that. >> checking for folder existance everytime a user might access a service is >> stupid. it costs at least a stat() call per directory." Some how you missed the part.I'd like to make sure this use always has this folder. Aka if they delete it, I'd like it to be recreated. PS. In the end all's it comes down to is i was wounder if there was a way to have dovecot auto create a folder or a list of folders at login. OR really if there was a way to tell dovecot a list of folders a user COULD NOT delete (But could delete the folders in side). -- Chris L. Franklin --

2 1

[Dovecot] dovecot-ldap with tls
by ck 24 Mar '05

24 Mar '05

hi all, Can somebody help me to find out how to use dovecot to connect to my ldap server which has the tls support? Currently I'm using my dovecot to connect to ldap without tls and soon my ldap server will apply the tls and all others server have to connect through the tls. thanks a lot. CK from Malaysia

2 1

[Dovecot] automatic flag updates
by Aaron VanDevender 24 Mar '05

24 Mar '05

Is there a way to get dovecot to send automatic flag updates? I notice that when I have two clients connected and one of them reads a new message, the server sends a status update which contains the number of unseen messages, but doesn't specifically say which ones have changed. I think the solution to this problem, while not wasting bandwidth, is to issue a unilateral FETCH FLAGS response whenever a flag changes. There doesn't seem to be a way to get dovecot (I'm using 0.99.10) to do this. Can the 1.0-test versions do this? cya .sig

2 7

[Dovecot] stable assert error
by Paul Jongsma 23 Mar '05

23 Mar '05

Hello, When moving a message from my inbox to an existing mailbox folder I get: dovecot: Mar 21 12:52:48 Error: IMAP(paulj): file istream-raw-mbox.c: line 383 (istream_raw_mbox_get_body_size): assertion failed: (rstream->body_offset != (uoff_t)-1) dovecot: Mar 21 12:52:48 Error: child 10265 (imap) killed with signal 6 This after moving from 0.99 to 1.0 stable on 5.3-RELEASE-p5 Client is Apple Mail program Anything I can do to fix or investigate? Thanks Paul

3 3

[Dovecot] Hide non-accessable folder from users
by Remy Zandwijk 22 Mar '05

22 Mar '05

Hi all, In our faculty, people keep asking about shared mail folders. With Dovecot up and running this should be no problem. I think we will have about 50 shared folders. I did take a look at the various solutions, but not all of them are useable. For example, I do not want users to create sub-folders in shared folders. This means the symlink option is unuseable. In my opinion, the easiest solution is creating a namespace and create the shared folders in the location of this namespace. Every shared folders gets his own UNIX group ID. Offcourse, this works great. The ony big disadvantage is that every users 'sees' all shared mailfolders, even if the user does not have the proper rights to access the folders. Is there a way to hide the non-accessable folders from users? Best regards, Remy Zandwijk

1 0

Re: [Dovecot] Auto Create Folders
by Chris L. Franklin 22 Mar '05

22 Mar '05

To make sure users have certain folders. -- Chris L. Franklin --

4 4

[Dovecot] strange email client problems
by Gabriel Granger 22 Mar '05

22 Mar '05

I've got some issues with dovecot, that I need to resolve, I only have about 20 users in the office, but the average disk space used by each user is anywhere from 1GB up to at the extreme end of the scale 7GB. I'm using the mailbox format. The server is a P4 2.8 with a 1GB of ram and run off 250GB SATA disks. most users have lots of structured folders going as deep as 6 levels. The problems I'm getting are odd the problems that I'm getting at the moment are "cannot copy mail to sent folder", but sends the message fine, this doesn't happen all the time but happens to everyone but me... I'm using OS X's Mail.app which seems to always work:) all my users are using W2K and either ThunderBird or Mozilla The other problem which I've been made aware of... The users get the "loading message" or "opening messages" and the egg timer goes round but never completes. I managed to clear the problem by getting the user to close their email client and then kill their IMAP processes on the server, when the user logs in again the client responds correctly. Is there something I'm doing wrong with the configuration of dovecot? would using MailDir help, I dont want to migrate from Mailbox unless this change will make things better, I understand their are benefits from using MailDir, but I dont know if I will continue to see the same problems if I migrate. Any help or advise would be great, I should add that everyone is connecting to the server over SSL Gabe

3 5

[Dovecot] emulating courier imap
by Geo Carncross 21 Mar '05

21 Mar '05

I'm trying this: default_mail_env = maildir:%h/.maildir:INDEX=%h/.indexes:INBOX=% h/.maildir namespace private { separator = . prefix = INBOX. inbox = no } namespace private { separator = . prefix = inbox = yes hidden = yes } but dovecot doesn't appear to be honoring "hidden" - am I missing something? (that is, all my folders appear twice- one under INBOX, the other under root) I tried without the second segment, and makign the first one "inbox=yes" - but then I got two inboxes... -- Internet Connection High Quality Web Hosting http://www.internetconnection.net/

3 2

[Dovecot] Mixing mbox and maildir
by Tom Alsberg 21 Mar '05

21 Mar '05

Hi there. I understood that in Dovecot 1.0 it should be possible to mix the usage of mbox and maildir mailboxes. I just downloaded, built, and am testing dovecot-stable-20050304. I'm a bit confused as to the terms of namespaces (haven't read that part of the RFC yet), but this does not seem related. Anyway, when I try specifying: default_mail_env = ~/mail/:INBOX=/var/mail/%u On login I'm immediately disconnected, seeing something like: dovecot: IMAP(user): Failed to create storage with data: ~/mail:INBOX=/var/mail/user in the log file. This seems more like a bug to me (or maybe something in permissions I haven't noticed - but I've checked...) Any way, according to the documentation, it will detect whether ~/mail/ is mbox or maildir - but would that enable having both mbox and maildir in that directory? The goal is, to deploy Dovecot 1.0 at some time, while here there are users who have both maildir and mbox mailboxes (I.E. spool is mbox, ~/mbox is mbox, ~/mail contains some mbox mailboxes for small stuff that users want to be able to access even using /usr/bin/mail, and some larger maildir mailboxes (less critical, or high volume - e.g. mailing lists). How is that possible? Thanks, -- Tom P.S. Thanks again, Timo and rest of developers for this big piece of code - I maintain Dovecot 0.99 in another place and it's by far the most useful IMAP server yet. -- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.

6 11

[Dovecot] Shared maildirs with symlinking
by Gauthier Vandemoortele 21 Mar '05

21 Mar '05

Hello, I try to set up a shared maildir with symbolink links, but it doesn't work. The main user, from which I would share a mailbox, creates a mailbox named "Commun" with thunderbird. I see on the file system from the server that a directory .Commun is created in his ~/Maildir/ and that the file ~/Maildir/.subscriptions has now such an entry. Right. In ~/Maildir/Commun the permissions are /cur 700 /new 700 /tmp 700 .customflags 600 .imap.index 600 .imap.index.data 600 .imap.index.log 600 .imap.index.tree 600 dovecot-uidlist 600 and as owner MainUser/users (I work on a slackware 10, all the users have by default the group users.) So, I change all the rights to 770 for directories and 660 for other files (I don't forget .Commun itself) Now the other user ; he creates also a folder named "Commun", so that such an entry exists in .subscriptions. As admin, I delete his folder ~/Maildir/.Commun, and create a symbolink link ~OtherUser/Maildir/.Commun pointing to ~MainUser/Maildir/.Commun Now MainUser moves a mail in his folder Commun, always with thunderbird ; OtherUser sees now a message in the "same" folder, but he can't read it. In fact, Thunderbird displays a little icon but without textuel information, like subject, or so. If OtherUser clicks on it, the mailer hangs indefinitly. It's logical, the file created in ~MainUser/Maildir/.Commun has 600 as permissions. On the other hand, OtherUser can move or create a file in his folder Commun, but MainUser does'nt see it, I suppose because his index is not updated. I had read in http://wiki.dovecot.org/SharedFolders that : It's important to have dovecot-shared file created in the shared maildir with the permissions and group ID you want to have access to the mailbox. Dovecot uses the same permissions and GID when it creates index files, dovecot-uidlist file, new mail files, etc. With my experience, it seems that Dovecot creates the file regardless of the permissions of the shared folder. Can someone say how to resolve that ? I use dovecot-0.99.11 Thanks in advance, -- Gauthier Vandemoortele <gauthier.vandemoortele(a)skynet.be> ... Un jeune sur dix qui sait pas lire, ça en fait neuf sur dix qui lisent des conneries. (Brèves de comptoir - J-M Gourio)

2 1

[Dovecot] Loading messages
by Gabriel Granger 19 Mar '05

19 Mar '05

Thanks to all for pointing out the Thunderbird bug workaround, I've got another question Some of my users are complaining that when they select a message, the email client says "Loading Message" and either takes a long time to display a small message or does not display the message at all. Its odd becuase it seems that larger message on these users machines seem to open more quickly then the small 1Kb - 15Kb messages. Looking a little further on the messages that wont open they all seem to be very small in size. Is this a common issue? or something i need to tweak on the dovecot.conf or on the client side? Gabe

5 4

[Dovecot] problems with migration to Maildir
by F. Even 19 Mar '05

19 Mar '05

I'm attempting to use Maildir and mbox together until I can finish migrating all mailboxes and figure out issues I'm having with a couple other mailboxes. But, I want to officially start using Maildir as the primary msg. store. Now...when I configure Dovecot as follows, it creates new folders in the ~/mail folder, which is where my mboxes reside: #default_mail_env = #default_mail_env = mbox:~/mail/:INBOX=~/mbox #default_mail_env = mbox:~/:INBOX=~/mbox #default_mail_env = mbox:~/mail:INBOX=~/mbox default_mail_env = maildir:~/Maildir #namespace private { # separator = / # inbox = yes # prefix = # location = mbox:~/mail:INBOX=~/mbox #} #namespace private { # separator = / # prefix = "Maildir/" # location = maildir:~/Maildir #} namespace private { separator = / inbox = yes location = maildir:~/Maildir } namespace private { separator = / location = mbox:~/mail } I would like to have access to the mbox hierarchy, but I want all new folders by default created in ~/Maildir. How do I go about acheiving this? Thanks, Frank

2 5

[Dovecot] 1.0-test65 and ldap auth
by KATOH Yasufumi 19 Mar '05

19 Mar '05

Hi, Does 1.0-test65 work with ldap auth? The log is: dovecot: Mar 15 20:59:32 Error: child 13676 (auth) killed with signal 11 Info log is: dovecot: Mar 15 20:59:19 Info: Dovecot v1.0-test65 starting up dovecot: Mar 15 20:59:32 Info: auth(default): client in: AUTH 1 PLAIN service=POP3 secured lip=127.0.0.1 rip=127.0.0.1 resp=AGthcm1hQGhhcnAuZ3I uanAAU2FncmFkbzAy dovecot: Mar 15 20:59:36 Info: pop3-login: Aborted login [127.0.0.1] linux kernel 2.6.10, glibc 2.3.2 OpenLDAP 2.2.23 -- karma(a)jazz.email.ne.jp / KATOH Yasufumi

3 4

[Dovecot] Auto Create Folders
by Chris L. Franklin 19 Mar '05

19 Mar '05

Is there any way to addon the ability to have dovecot auto create imap folders for a user ? -- Chris L. Franklin

3 2

[Dovecot] Re: Warning, newbie!
by Pete 18 Mar '05

18 Mar '05

To make things clearer, this is where I am at now when I login from Mutt. FreeBSD 4.11 Dovecot -0.99.13 Postfix current Mar 18 09:28:15 slippery dovecot: Killed with signal 15 Mar 18 11:10:38 slippery imap(pete): We couldn't drop root group privileges Mar 18 11:10:38 slippery dovecot: child 97190 (imap) returned error 89 -- Pete http://milneweb.com http://nomorevirus.com

1 0

[Dovecot] Moving from 0.99 to 1.0-stable
by Jim Trigg 18 Mar '05

18 Mar '05

What is involved in migrating from 0.99 to 1-stable? (I'd be creating a FreeBSD port to work with, but the main question I have is what would need to be done to configuration files.) Thanks, Jim -- Jim Trigg, Lord High Everything Else O- /"\ Hostmaster, Huie Kin family website \ / ASCII RIBBON CAMPAIGN Verger and System Administrator, X HELP CURE HTML MAIL All Saints Church - Sharon Chapel / \

2 1

[Dovecot] error
by Pete 18 Mar '05

18 Mar '05

Hi, I am getting this error in my syslog when I try to access with Mutt. Mar 18 09:06:55 slippery imap(pete): We couldn't drop root group privileges This is more difficult to get running that I expected but I will stick with it a little longer. -- Pete http://milneweb.com http://nomorevirus.com

2 2

[Dovecot] postfix + SMTP AUTH using DOVECOT AUTH DAEMON
by Ing. Alejandro Rodriguez 18 Mar '05

18 Mar '05

hi ppl I'm the new member of the list. Looking at recent messages look like there is a way to do SMTP AUTH in postfix using the Dovecot AUTH daemon. Currently my Dovecot installation auth again PAM (local users) and a simple shadow file (for virtual users, I plan to move to MYSQL later). I don't want to have different databases one for dovecot a one for SASL. Where I can found the POSTFIX patch, or better, some kind of helper daemon for Postfix. thx A

2 1

[Dovecot] Namespaces and subscriptions
by Chris Wakelin 17 Mar '05

17 Mar '05

I've got a problem with subscriptions in 1.0-stable when migrating from UW-IMAP. I've modified the SUBSCRIPTION_FILE_NAME entries as suggested in the Wiki http://wiki.dovecot.org/Migration and included the "~/mail/" etc. hidden namespaces. The .mailboxlist files contain entries like "~/mail/somefolder" and the clients have "~/mail/" set as a prefix. In UW-IMAP: xyz LSUB "" "*" * LSUB () "/" ~/mail/somefolder xyz LSUB "~/mail/" "*" * LSUB () "/" ~/mail/somefolder Now with Dovecot: xyz LSUB "" "*" * LSUB () "/" "~/mail/somefolder" xyz LSUB "~/mail/" "*" * LSUB () "/" "~/mail/~/mail/somefolder" In other words, Dovecot is prepending the namespace to the list of folders stored in .mailboxlist. This causes Thunderbird to show the folders as -~ - mail | somefolder which are accessible. Squirrelmail gets completely confused and tries to display "~/mail/~/mail/somefolder" (but works with the prefix set to ""). Am I missing something? I tried Geo's empty namespace patch, just in case that would help, but it didn't. Best Wishes, Chris --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

1 1

[Dovecot] Warning, newbie!
by Pete 17 Mar '05

17 Mar '05

Greetings again all, <snip> I am a Postfix/Courier-IMAP user and am interested in Dovecot. I have install Dovecot via FBSD ports. I have got to the part where I can telnet in to the server. </snip> I guess I ought to backup a little, now that I have the above resolved. I am wanting/wondering about using Dovecot with Postfix. I assume some of you have done this. Have you any thoughts, comments, how-to -- Pete http://milneweb.com http://nomorevirus.com

4 4

[Dovecot] Warning, newbie!
by Pete 17 Mar '05

17 Mar '05

Greetings All, I am a Postfix/Courier-IMAP user and am interested in Dovecot. I have install Dovecot via FBSD ports. I have got to the part where I can telnet in to the server. -bash-2.05b$ telnet 192.168.1.61 143 Trying 192.168.1.61... Connected to 192.168.1.61. Escape character is '^]'. * OK dovecot ready. x login pete testing * BAD [ALERT] Plaintext authentication is disabled, but your client sent password in plaintext anyway.If anyone was listening, the password was exposed. x NO Plaintext authentication disabled. x logout * BYE Logging out x OK Logout completed. Connection closed by foreign host. -bash-2.05b$ I am afraid I dont know what to do from here. Anyone care to assist me? Thanks, -- Pete http://milneweb.com http://nomorevirus.com

2 1

[Dovecot] 1.0-test65
by Timo Sirainen 17 Mar '05

17 Mar '05

http://dovecot.org/test/ If dovecot-auth was crashing with you, this release should fix it. I don't know when it did though, I just applied a patch from Andrey Panin with that description :) Fixed also another dovecot-auth crash with Solaris and maybe some other systems. Contains the first attempt of a Dovecot LDA. It's still in pretty ugly shape, but it should work, more or less. I wouldn't recommend using it in production yet. There are two ways to use it: 1. As a normal user. The username is taken from passwd. 2. Giving -d <username> option. This connects to dovecot-auth and requests the uid, gid, home, etc. from it. dovecot-auth's master socket is expected to be in /var/run/dovecot/auth-master but you can override this with -a parameter. To actually create the auth-master socket you'll need to add this inside auth { .. } : socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 } } Dovecot LDA also currently needs dovecot-lda.conf file. Everything that is read from it is just dumped into environment variables internally. You should be able to set pretty much all the same settings in there as exists in dovecot.conf. The most important exception is that instead of default_mail_env there's just "mail". Example dovecot-lda.conf would be: # note that namespaces aren't supported yet.. mail = mbox:~/mail:INBOX=/var/mail/%u mbox_read_locks = flock mbox_write_locks = flock # EOF All this goes away once I get the config process implemented. The actual usage goes something like: /usr/local/libexec/dovecot/deliver -d username < mail_file ie. the mail is read from standard input. Any suggestions if the "deliver" name should be changed and maybe moved to /usr/bin/? Another large change is that I created dynamically growing array implementation with possibility to do compile time type checking. The old code was using buffer_t for arrays, but that got pretty ugly. I changed most of those in lib-index/ to the new array API. I'd be happy if someone changed the rest of them since it's pretty boring and time consuming job :) See lib/array.h for explanation how it works. And finally a small advertisement: http://mjr.iki.fi/texts/patentfund

2 1

[Dovecot] corruption and errors in dovecot-stable
by Nicholas Riley 17 Mar '05

17 Mar '05

Hi, We switched from dovecot 0.99.something to 1.0-stable (on FreeBSD 4.10) a few days ago and have been seeing many errors and one corrupted mailbox so far. Almost everyone uses mbox format, and most users primarily use SquirrelMail; I use Apple Mail and Thunderbird, as well as accessing the mailboxes locally with Mutt, and have not noted any visible problems. There have been several of these messages: dovecot: Feb 21 11:40:06 Error: IMAP(njr): mbox sync: UID inserted in the middle of mailbox /usr/home/njriley/mail/lists/trac (5308 > 1151) dovecot: Feb 21 22:57:13 Error: IMAP(njr): mbox sync: UID inserted in the middle of mailbox /usr/home/njriley/mail/lists/trac (6458 > 1151) dovecot: Feb 22 08:37:03 Error: IMAP(njr): mbox sync: UID inserted in the middle of mailbox /usr/home/njriley/mail/lists/reportlab-users (5162 > 3812) Others: dovecot: Feb 22 11:44:17 Error: IMAP(njr): file mbox-sync-parse.c: line 221 (parse_x_uid): assertion failed: (!ctx->sync_ctx->sync_restart) dovecot: Feb 22 11:44:17 Error: child 19931 (imap) killed with signal 6 dovecot: Feb 25 06:26:09 Error: IMAP(kbode): file istream-raw-mbox.c: line 383 (istream_raw_mbox_get_body_size): assertion failed: (rstream->body_offset != (uoff_t)-1) dovecot: Feb 25 06:26:09 Error: child 83423 (imap) killed with signal 6 (I think this refers to the mailbox that was corrupted) dovecot: Feb 25 12:30:40 Error: IMAP(sachs): Transaction log file /home/sachs/Mail/.imap/INBOX/dovecot.index.log: invalid indexid (1109356120 != 1108933119) dovecot: Feb 25 12:30:40 Error: IMAP(sachs): Corrupted transaction log file /home/sachs/Mail/.imap/INBOX/dovecot.index.log: Extension record update update without intro prefix dovecot: Feb 25 12:30:41 Error: IMAP(sachs): Transaction log file /home/sachs/Mail/.imap/INBOX/dovecot.index.log: marked corrupted dovecot: Feb 25 12:39:34 Error: IMAP(sachs): Transaction log file /home/sachs/Mail/.imap/INBOX/dovecot.index.log: invalid indexid (1109356120 != 1108933119) dovecot: Feb 25 12:39:34 Error: IMAP(sachs): Lost transaction log file /home/sachs/Mail/.imap/INBOX/dovecot.index.log seq 2 dovecot: Feb 25 12:39:41 Error: IMAP(sachs): Transaction log file /home/sachs/Mail/.imap/INBOX/dovecot.index.log: invalid indexid (1108933119 != 1109356120) I am currently reinstalling 0.99.14, but it would be nice to be able to switch to a 1.0-derived version again - we have to run two copies of 0.99.x to get what we want. If there is any additional testing I can do to help fix these problems, please let me know. Thanks, -- Nicholas Riley <njriley(a)uiuc.edu> | 4111 Siebel Center Department of Computer Science | 201 N. Goodwin Ave. and Medical Scholars Program | Urbana, IL 61801-2302 Univ. of Illinois at Urbana-Champaign | +1 217 244 2274

3 4

[Dovecot] Minor documentation bug with 0.99.14
by John Peacock 16 Mar '05

16 Mar '05

The sample dovecot-example.conf contains these lines: > # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before > # dropping root privileges, so keep the key file unreadable by anyone but > # root. Included doc/mkcert.sh can be used to easily generate self-signed > # certificate, just make sure to update the domains in dovecot-openssl.cnf > #ssl_cert_file = /etc/ssl/certs/dovecot.pem > #ssl_key_file = /etc/ssl/private/dovecot.pem but the aforementioned doc/mkcert.sh contains these lines: > CERTFILE=$SSLDIR/certs/imapd.pem > KEYFILE=$SSLDIR/private/imapd.pem either the script should be changed to reflect the sample config file or vice versa. John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748

2 1

[Dovecot] Problems with Outlook 2002 SP3 & Dovecot 0.99.13 Redux
by Md 16 Mar '05

16 Mar '05

Hi, I posted this question a while back and didn't get much response. Since then, I've done a bit more experimenting and wonder if someone can help me move forward towards resolution. The orignal question... > I'm running Dovecot0.99.13 on Fedora Core 3 and things work fine when using either > Thunderbird 1.0 or Outlook Express as IMAP clients. Outlook (2002 SP3) on the other hand > runs incredibly slowly, or just outright hangs. I've discovered that if I delete and recrete .../Maildir in the user account such that the directory exists but is empty, then outlook seems to behave. If on the other-hand, I try to create a folder, with outlook, outlook will hang and the folder won't be created. If I create the folder with another client and then go back to using outlook, outlook will hang. I've taken some network traces and have annotated them here... Starting with an empty "Maildir" Time Source Destination Protocol Info 8.515435 192.168.73.3 192.168.73.1 IMAP Response: * OK dovecot ready. 8.516056 192.168.73.1 192.168.73.3 IMAP Request: 0000 CAPABILITY 8.516539 192.168.73.3 192.168.73.1 IMAP Response: * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE STARTTLS AUTH=PLAIN 8.516733 192.168.73.1 192.168.73.3 IMAP Request: 0001 LOGIN "xxx" "xxx" 8.594634 192.168.73.3 192.168.73.1 IMAP Response: 0001 OK Logged in. 8.640521 192.168.73.3 192.168.73.1 IMAP Response: + idling 8.640709 192.168.73.1 192.168.73.3 IMAP Request: DONE 8.640983 192.168.73.3 192.168.73.1 IMAP Response: 0002 OK Idle completed. 8.641165 192.168.73.1 192.168.73.3 IMAP Request: 0003 LIST "" "" 8.641315 192.168.73.3 192.168.73.1 IMAP Response: * LIST (\Noselect) "." "" 8.642387 192.168.73.1 192.168.73.3 IMAP Request: 0004 LIST "" "INBOX" 8.642956 192.168.73.3 192.168.73.1 IMAP Response: * LIST (\HasNoChildren) "." INBOX 8.657424 192.168.73.1 192.168.73.3 IMAP Request: 0005 LSUB "" "*" 8.657925 192.168.73.3 192.168.73.1 IMAP Response: 0005 OK Lsub completed. 8.660627 192.168.73.1 192.168.73.3 IMAP Request: 0006 IDLE 8.660973 192.168.73.3 192.168.73.1 IMAP Response: + idling Now try to create a sub-folder using outlook: 0.000000 192.168.73.1 192.168.73.3 IMAP Request: DONE 0.000587 192.168.73.3 192.168.73.1 IMAP Response: 0006 OK Idle completed. 0.000910 192.168.73.1 192.168.73.3 IMAP Request: 0008 IDLE 0.001113 192.168.73.3 192.168.73.1 IMAP Response: + idling And there outlook just hangs. Killing outlook and starting it again gives this trace: 5.110260 192.168.73.1 192.168.73.3 TCP 1953 > imap [SYN] Seq=0 Ack=0 Win=64240 Len=0 MSS=1460 5.111826 192.168.73.3 192.168.73.1 IMAP Response: * OK dovecot ready. 5.112139 192.168.73.1 192.168.73.3 IMAP Request: 0000 CAPABILITY 5.112600 192.168.73.3 192.168.73.1 IMAP Response: * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE STARTTLS AUTH=PLAIN 5.112798 192.168.73.1 192.168.73.3 IMAP Request: 0001 LOGIN "xxx" "xxx" 5.127237 192.168.73.3 192.168.73.1 IMAP Response: 0001 OK Logged in. 5.135355 192.168.73.1 192.168.73.3 IMAP Request: 0002 IDLE 5.137334 192.168.73.3 192.168.73.1 IMAP Response: + idling 5.138060 192.168.73.1 192.168.73.3 IMAP Request: DONE 5.138273 192.168.73.3 192.168.73.1 IMAP Response: 0002 OK Idle completed. 5.138505 192.168.73.1 192.168.73.3 IMAP Request: 0004 IDLE 5.138646 192.168.73.3 192.168.73.1 IMAP Response: + idling And there outlook just hangs again. Any ideas or help would be greatly appreciated. Thanks, Md

2 1

[Dovecot] imap-login zombies
by Robin Breathe 16 Mar '05

16 Mar '05

Running dovecot-0.99.13 on Solaris9/Sparc with ~25k users, we are having regularly recurring problems with large numbers imap-login/pop3-login drones, cycling on poll(). Over the course of 1-2 days, the number of such processes slowly rises to >1000, exhausts resources, and necessitates that dovecot be restarted (having killed all current active and zombie child processes). Nothing of interest seems to be logged with the possible exception of a reasonably high number of aborted logins (~10/hour). Can anyone offer any guidance as to how to track down this bug and help get it resolved? Any help would be much appreciated, as we would very much like to see this resolved in the 0.99 branch. Regards, Robin

2 1

[Dovecot] dovecot-auth hangs with IO leak
by Alan Tam 16 Mar '05

16 Mar '05

Hi dovecot, I am using the debian dovecot packages on a system running LDAP. My /etc/pam.d/common-* looks like this, which simply means try /etc/passwd first, and try LDAP using the same password if it is failed. account [success=1 default=ignore] pam_unix.so account required pam_ldap.so use_first_pass account required pam_permit.so auth [success=1 default=ignore] pam_unix.so auth required pam_ldap.so use_first_pass auth required pam_permit.so session [success=1 default=ignore] pam_unix.so session required pam_ldap.so use_first_pass session required pam_mkhomedir.so skel=/etc/skel umask=0002 session required pam_permit.so When many LDAP users login, /var/log/auth.log shows many (expected) error like: (note "pam_unix") Feb 3 18:16:15 eta dovecot-auth: (pam_unix) authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=127.0.0.1 Feb 3 18:16:19 eta dovecot-auth: (pam_unix) check pass; user unknown After recent upgrades from probably 0.99.10 to 0.99.13, these lines begin to appear in /var/log/mail.log: Feb 3 16:31:00 eta dovecot-auth: Login process has too old (123s) requests, killing it. Feb 3 16:31:00 eta dovecot-auth: Login process has too old (124s) requests, killing it. And some more like this, which shows the problem: Feb 3 16:45:23 eta dovecot-auth: I/O leak: 0x8054940 (13) Feb 3 16:45:23 eta dovecot-auth: I/O leak: 0x8054940 (14) Feb 3 16:45:23 eta dovecot-auth: I/O leak: 0x8054940 (15) The problem can be solved by changing /etc/pam.d/dovecot to: auth required pam_ldap.so account required pam_ldap.so session required pam_mkhomedir.so skel=/etc/skel umask=0002 session required pam_ldap.so This change means PAM not fail auth for /etc/passwd again. I think dovecot has some problem dealing with the pam_unix + pam_ldap configuration. Do you have any idea? I am Cc-ing this message to the corresponding bug in Debian BTS. -- Regards, Alan

2 2

[Dovecot] Bit of a Newbie Question
by Jud 16 Mar '05

16 Mar '05

Apologies in advance - I'm sure there's something quite obvious I'm not doing correctly, but since I'm unable to resolve the problem myself.... I've installed Dovecot 99.14 on FreeBSD-CURRENT using the Dovecot FreeBSD port. My "network" consists of a cable modem connected to a router which is in turn connected (only) to my computer. My ISP assigns a dynamic IP address. I have ddclient set up to sync the dynamic IP to my hostname and MX via dyndns.org. Local operations (local delivery via Postfix or copying/moving/deleting with Thunderbird) work fine. Mail delivery from remote machines does not seem to work via either IMAP or IMAP-SSL. (That is, test e-mails I send from this [Fastmail] account to my local IMAP server never reach their destination.) Enabling port forwarding on my router for ports 993 and 143 has made no difference. What should I be doing to make this work correctly? Jud

5 7

[Dovecot] Strange behaviour with moving mail
by Remy Zandwijk 15 Mar '05

15 Mar '05

Hi All, Sorry to bother you again. I am not too familiar with IMAP yet, so maybe I am asking stupid questions. Here goes anyway: In our (Dovecot 1.0-stable) setup, we have two namespaces: the default namespace, which location is '/var/mailstore/1%u/%u' and the "Mailstorage" namespace, which location is '~/.Mailstorage/'. Now we create a folder called 'Test' in the default namespace and the "Mailstorage" namespace. As far as I know this is possible and not a strange thing to do. When moving an email from the first 'Test' folder to the other 'Test' folder, it appears that everything works like expected, but when refreshing the mailbox, the message is still in the original folder. This happens with a number of different mailclients (which are configured with an empty namespace setting). I guess Dovecot doesn't look at the namespace in which the mail folder is. Is this a Dovecot bug or is this normal behaviour? Best regards, Remy B.T.W: When moving the mail, this is the IMAP conversation: 00029 UID COPY 4 TEST * 2 EXISTS * 2 RECENT 00029 OK Copy completed. 00030 UID STORE 4 +Flags.silent (\Deleted) 00030 OK Store completed.

2 3

[Dovecot] Is it possible to regenerate the index files?
by Joakim Verona 15 Mar '05

15 Mar '05

Is it possible to regenerate the index files, on other conditions than the mbox file being read? For instance, it would be nice if I could regenerate the index for a specific mbox whenever procmail delivers mail to it. If theres no existing solution, would it be possible to make a small script with something like "nc" that could send an imap command to dovecot, so that dovecot would rebuild its index for that mbox? If so, which imap command triggers an index rebuild? -- Joakim Verona www.verona.se

2 5

[Dovecot] Visibility of .subscriptions and .customflags
by justin 15 Mar '05

15 Mar '05

Hi, I upgraded to test65 from 0.99 (mostly to get the namespace feature) and now it seems my .subscriptions and .customflags are showing up as mail folders in my IMAP client (Eudora). If I try and open those folders, of course I get an error. How can I configure dovecot so that these aren't displayed to my IMAP client? I looked through about 6 months of acrhives and couldn't find it mentioned anywhere. Thanks.

2 1

[Dovecot] logging
by F. Even 15 Mar '05

15 Mar '05

I'm curious about exactly what this means in my log: Mar 13 10:56:20 cerebus dovecot: imap-login: Disconnected [130.94.242.20] Mar 13 10:56:51 cerebus last message repeated 177 times Mar 13 10:57:32 cerebus last message repeated 179 times Now...does Dovecot ONLY log the names of users on successful attempts? Is this "Disconnected" log entry an indication someone ran a username/password attack against the imap server and failed to authenticate? If so, is there any way to make this a little more verbose, so I can perhaps see what names, etc. the annoying idiot is throwing against my server....? Thanks.

2 1

[Dovecot] (no subject)
by Gabriel Granger 15 Mar '05

15 Mar '05

Hi All, Bit the bullet last night and switched off UW-IMAP and turned on Dovecot. With any migration I've got some teething problems and hoping someone might be able to point me in the right direction. I tested the system using apple's Mail.app which worked fine, no problems at all, but it seems that most of my users are getting problems, i suspect Mail.app is hiding these messages from me. All my users are using ThunderBird 1.0 lastest stable release. Some messages in their IMAP folders are producing the following error. The current command did not succeed. The mail server responded: Error in IMAP command UID: Invalid BODY[_] parameter: Missing '>' in '<16384.-14781>'. it occurs on the same messages in the users email client but happens randomly, it does not stop you from viewing the message, its just pops up with this error. I'm current using IMAP over SSL and using mbox not maildir for IMAP Any ideas or hep would be great as I'd rather not have to roll back out to UW-IMAP Gabe

6 16

Re: [Dovecot] aha! (was apple mail vs. v0.99)
by sean finney 15 Mar '05

15 Mar '05

hey timo, On Tue, Mar 15, 2005 at 07:32:35PM +0200, dovecot-request(a)dovecot.org wrote: > From: Timo Sirainen <tss(a)iki.fi> > > i set: > > > > mailbox_check_interval = 0 > > This has been the default since 0.99.5 which was released over 2 years > ago. How old version are you using? :) Or had you changed the default? i had indeed changed the default, thinking that it would be a nice feature to turn on. when the problem first surfaced, i immediately thought of this option. however, since the problem was that applemail wasn't seing the new mail, and this was an option to notify the client that there *was* new mail, i guess common sense got the better of me and i forgot this was something i had changed... > > mailbox_idle_check_interval = 0 > > This shouldn't matter because OSX Mail doesn't use IDLE. Probably better > idea to turn it back on or clients using IDLE don't see new mails (I > think?) aha. well then i'll have to try turning that back on :) thanks, sean

1 0

[Dovecot] corrupted inboxes
by Josh Burley 15 Mar '05

15 Mar '05

Hi all, Two users on our system have recently had trouble reading their inbox, and it seems to be a result of their inbox getting corrupted. In the most recent case, their Mailbox file (in /home/eric/Mailbox in this case), has the following as the first line: cnw.igmg-- Here's a piece of the logs below... if you look for "eric", there's a successfully delivery, followed a bit later by a POP attempt by "eric" that returns that the Mailbox isn't in mbox format. Any ideas? .josh Mar 11 14:59:04 core postfix/local[8203]: 27D18279857E: to=<eric(a)kuci.org>, relay=local, delay=0, status=sent (delivered to mailbox) Mar 11 14:59:04 core postfix/qmgr[7238]: 27D18279857E: removed Mar 11 14:59:06 core postfix/smtpd[8199]: disconnect from user-0c8gg6h.cable.mindspring.com[24.136.64.209] Mar 11 14:59:13 core pop3-login: Login: gtt [::ffff:67.120.76.169] Mar 11 14:59:18 core postfix/smtpd[7575]: connect from webhost2.ethr.net[208.37.25.24] Mar 11 14:59:18 core postfix/smtpd[7575]: setting up TLS connection from webhost2.ethr.net[208.37.25.24] Mar 11 14:59:18 core postfix/smtpd[7575]: TLS connection established from webhost2.ethr.net[208.37.25.24]: TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits) Mar 11 14:59:18 core postfix/smtpd[7575]: 242E2279857E: client=webhost2.ethr.net[208.37.25.24] Mar 11 14:59:18 core postfix/cleanup[8201]: 242E2279857E: message-id=<bb165712392a2b4375d6da0efa3c046c(a)www.ethr.net> Mar 11 14:59:18 core postfix/qmgr[7238]: 242E2279857E: from=<nobody(a)webhost2.ethr.net>, size=1527, nrcpt=1 (queue active) Mar 11 14:59:18 core postfix/cleanup[8201]: 6F63A2798580: message-id=<bb165712392a2b4375d6da0efa3c046c(a)www.ethr.net> Mar 11 14:59:18 core postfix/local[8203]: 242E2279857E: to=<r-ethr(a)kuci.org>, relay=local, delay=0, status=sent (forwarded as 6F63A2798580) Mar 11 14:59:18 core postfix/qmgr[7238]: 6F63A2798580: from=<nobody(a)webhost2.ethr.net>, size=1653, nrcpt=1 (queue active) Mar 11 14:59:18 core postfix/smtpd[7575]: disconnect from webhost2.ethr.net[208.37.25.24] Mar 11 14:59:18 core postfix/qmgr[7238]: 242E2279857E: removed Mar 11 14:59:18 core postfix/smtp[8250]: setting up TLS connection to blade.butterzone.net Mar 11 14:59:18 core postfix/smtp[8250]: verify error:num=19:self signed certificate in certificate chain Mar 11 14:59:18 core postfix/smtp[8250]: Peer verification: CommonName in certificate does not match: tloin.butterzone.net != blade.butterzone.net Mar 11 14:59:18 core postfix/smtp[8250]: Peer certficate could not be verified Mar 11 14:59:18 core postfix/smtp[8250]: 6F63A2798580: to=<r(a)butterzone.net>, orig_to=<r-ethr(a)kuci.org>, relay=blade.butterzone.net[208.37.27.136], delay=0, status=sent (250 Ok: queued as 4783AC2C130) Mar 11 14:59:18 core postfix/qmgr[7238]: 6F63A2798580: removed Mar 11 14:59:23 core pop3(eric): File isn't in mbox format: /home/eric/Mailbox Mar 11 14:59:24 core pop3-login: Login: eric [::ffff:128.195.131.49] Mar 11 14:59:24 core pop3(eric): File isn't in mbox format: /home/eric/Mailbox Mar 11 14:59:24 core pop3(eric): File isn't in mbox format: /home/eric/Mailbox Mar 11 14:59:24 core pop3(eric): Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-03-11 14:59:24] Mar 11 14:59:49 core pop3-login: Login: eric [::ffff:128.195.131.49] Mar 11 14:59:49 core pop3(eric): File isn't in mbox format: /home/eric/Mailbox Mar 11 14:59:49 core pop3(eric): File isn't in mbox format: /home/eric/Mailbox Mar 11 14:59:49 core pop3(eric): Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-03-11 14:59:49] Mar 11 14:59:53 core imap-login: Login: jeanie [::ffff:128.195.131.2] Mar 11 14:59:58 core last message repeated 5 times

2 4

Re: [Dovecot] aha! (was apple mail vs. v0.99)
by sean finney 15 Mar '05

15 Mar '05

hello! On Mon, Mar 14, 2005 at 11:08:39PM +0200, dovecot-request(a)dovecot.org wrote: > From: "Dominik 'Rathann' Mierzejewski" <D.Mierzejewski(a)icm.edu.pl> > > According to RFC3501 (is this the right one?), NOOP can be used to check > for new mail, but it doesn't say that the server should return status > data every time NOOP is issued. i think the problem is that when the server asynchronously reports to the client that there's new mail apple mail gets confused. then noop doesn't report new mail. also, it seems that this is also the cause of apple mail having to re-download the entire mailbox every time it checks for new mail. > From: Timo Sirainen <tss(a)iki.fi> > > How did you disable them? I think enabling oe6-fetch-no-newmail > workaround should help. i set: mailbox_check_interval = 0 mailbox_idle_check_interval = 0 which did the trick (i already had all the client workarounds enabled). thanks, sean

3 2

[Dovecot] empty namespace prefix doesn't honor hidden (PATCH)
by Geo Carncross 15 Mar '05

15 Mar '05

diff -u -r1.44 cmd-list.c --- src/imap/cmd-list.c 5 Feb 2005 18:07:26 -0000 1.44 +++ src/imap/cmd-list.c 15 Mar 2005 16:15:27 -0000 @@ -213,7 +213,7 @@ ctx->inbox && cur_ref == ctx->ref, ns->sep); if (*cur_ref != '\0' || *cur_prefix == '\0') - match = IMAP_MATCH_CHILDREN; + match = ns->hidden ? IMAP_MATCH_NO : IMAP_MATCH_CHILDREN; else { len = strlen(cur_prefix); if (cur_prefix[len-1] == ns->sep) -- Internet Connection High Quality Web Hosting http://www.internetconnection.net/

1 0

[Dovecot] Authentication to Active Directory
by Chris Wakelin 15 Mar '05

15 Mar '05

Has anybody managed to have Dovecot authenticate to Microsoft Active Directory? I've tried to get it to work using LDAP and the following settings dovecot.conf: userdb = ldap /etc/dovecot-ldap.conf passdb = ldap /etc/dovecot-ldap.conf dovecot-ldap.conf: hosts = rdg-home.ad.rdg.ac.uk dn = cn=bind-user,cn=users,dc=rdg-home,dc=ad,dc=rdg,dc=ac,dc=uk dnpass = XXXXX ldap_version = 2 base = dc=rdg-home,dc=ad,dc=rdg,dc=ac,dc=uk user_filter = (sAMAccountName=%u) pass_filter = (sAMAccountName=%u) I've also tried things like "(&(objectClass=sAMACcountName)(cn=%u))" to no avail. It appears to bind properly, but never finds the account, so login fails. I've had Active Directory authentication working with Squid and with Cyrus SASL/IMAP. Best Wishes, Chris --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 1

[Dovecot] Drac and Dovecot, almost there ...
by Jon Shoberg 15 Mar '05

15 Mar '05

I have dracd and dovecot up and running and trying to get the two connected. I'm using the FC3 rpms from callimg yum install. I've downloaded the drac patch from http://dovecot.org/patches/drac.c and compiled it with both gcc -Wall -W -shared -fPIC -DHAVE_CONFIG_H -I$dovecot -I$dovecot/src/lib drac.c -o drac.so -ldrac and gcc -Wall -W -shared -fPIC -DHAVE_CONFIG_H -I$dovecot -I$dovecot/src/lib drac.c -o drac.so I get no warnings or errors on the compiling to drac.so. In the conf file I have imap_use_modules = yes imap_modules = /usr/lib/dovecot/imap However, I don't see the module being called. Is there a way to tell. The dracd database (/etc/mail/dracd.db) is not being updated via testing with the drac utilities. Thoughts? Ideas? Below is output from a strace ... I don't see /usr/lib/dovecot/imap/drac.so being opened ... execve("/usr/sbin/dovecot", ["/usr/sbin/dovecot"], [/* 20 vars */]) = 0 uname({sys="Linux", node="masra.org", ...}) = 0 brk(0) = 0x8c85000 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=28209, ...}) = 0 old_mmap(NULL, 28209, PROT_READ, MAP_PRIVATE, 3, 0) = 0xf6ff9000 close(3) = 0 open("/lib/libssl.so.4", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\20\226"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=213600, ...}) = 0 old_mmap(0x7c0000, 212692, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7c0000 old_mmap(0x7f1000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x31000) = 0x7f1000 close(3) = 0 open("/lib/libcrypto.so.4", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\0\31d\000"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=933408, ...}) = 0 old_mmap(0x617000, 949656, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x617000 old_mmap(0x6ea000, 73728, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xd2000) = 0x6ea000 old_mmap(0x6fc000, 11672, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x6fc000 close(3) = 0 open("/usr/lib/libgssapi_krb5.so.2", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\320\214"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=82944, ...}) = 0 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf6ff8000 old_mmap(0x724000, 80272, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x724000 old_mmap(0x737000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x13000) = 0x737000 close(3) = 0 open("/usr/lib/libkrb5.so.3", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`\370[\000"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=415188, ...}) = 0 old_mmap(0x5b0000, 413000, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x5b0000 old_mmap(0x613000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x63000) = 0x613000 close(3) = 0 open("/lib/libcom_err.so.2", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\3548Y\000"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=7004, ...}) = 0 old_mmap(0x593000, 8636, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x593000 old_mmap(0x595000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1000) = 0x595000 close(3) = 0 open("/usr/lib/libk5crypto.so.3", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`Bp\000"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=136016, ...}) = 0 old_mmap(0x701000, 134560, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x701000 old_mmap(0x721000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x20000) = 0x721000 close(3) = 0 open("/lib/libresolv.so.2", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\360\363"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=81316, ...}) = 0 old_mmap(0x57d000, 80040, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x57d000 mprotect(0x58c000, 18600, PROT_NONE) = 0 old_mmap(0x58d000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xf000) = 0x58d000 old_mmap(0x58f000, 6312, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x58f000 close(3) = 0 open("/lib/libdl.so.2", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260\313"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=16908, ...}) = 0 old_mmap(0x4ec000, 12388, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x4ec000 old_mmap(0x4ee000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1000) = 0x4ee000 close(3) = 0 open("/usr/lib/libz.so.1", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260\205"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=63528, ...}) = 0 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf6ff7000 old_mmap(0x517000, 65028, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x517000 old_mmap(0x526000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xe000) = 0x526000 close(3) = 0 open("/lib/tls/libc.so.6", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0 O=\000"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=1524828, ...}) = 0 old_mmap(0x3c0000, 1219740, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x3c0000 mprotect(0x4e3000, 27804, PROT_NONE) = 0 old_mmap(0x4e4000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x123000) = 0x4e4000 old_mmap(0x4e8000, 7324, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x4e8000 close(3) = 0 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf6ff6000 mprotect(0x4e4000, 8192, PROT_READ) = 0 mprotect(0x4ee000, 4096, PROT_READ) = 0 mprotect(0x58d000, 4096, PROT_READ) = 0 mprotect(0x3bc000, 4096, PROT_READ) = 0 set_thread_area({entry_number:-1 -> 6, base_addr:0xf6ff66c0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0 munmap(0xf6ff9000, 28209) = 0 time(NULL) = 1110856826 brk(0) = 0x8c85000 brk(0x8cae000) = 0x8cae000 uname({sys="Linux", node="masra.org", ...}) = 0 getpid() = 18177 geteuid32() = 510 open("/etc/dovecot.conf", O_RDONLY|O_LARGEFILE) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=20533, ...}) = 0 pread(3, "## Dovecot 1.0 configuration fil"..., 2048, 0) = 2048 pread(3, "ges, use this logfile instead of"..., 2023, 2048) = 2023 pread(3, "g\n# we check only once in a seco"..., 1970, 4071) = 1970 pread(3, "to give \"mail\" group write acces"..., 2046, 6041) = 2046 pread(3, "STRUCTURE\n# gen"..., 1981, 8087) = 1981 pread(3, "is setting specifies the minimum"..., 2034, 10068) = 2034 pread(3, "dlinks = no\n\n# Check if mails\' c"..., 2026, 12102) = 2026 pread(3, "processes then.\n#mail_drop_priv_"..., 1986, 14128) = 1986 pread(3, " client authenticates in the IMA"..., 2029, 16114) = 2029 pread(3, "ice> | *]: PAM authentication\n# "..., 2034, 18143) = 2034 pread(3, "s, so it may be 0600-root owned "..., 356, 20177) = 356 close(3) = 0 socket(PF_FILE, SOCK_STREAM, 0) = 3 fcntl64(3, F_GETFL) = 0x2 (flags O_RDWR) fcntl64(3, F_SETFL, O_RDWR|O_NONBLOCK) = 0 connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) close(3) = 0 socket(PF_FILE, SOCK_STREAM, 0) = 3 fcntl64(3, F_GETFL) = 0x2 (flags O_RDWR) fcntl64(3, F_SETFL, O_RDWR|O_NONBLOCK) = 0 connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) close(3) = 0 open("/etc/nsswitch.conf", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=1686, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf6fff000 read(3, "#\n# /etc/nsswitch.conf\n#\n# An ex"..., 4096) = 1686 read(3, "", 4096) = 0 close(3) = 0 munmap(0xf6fff000, 4096) = 0 open("/etc/ld.so.cache", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=28209, ...}) = 0 old_mmap(NULL, 28209, PROT_READ, MAP_PRIVATE, 3, 0) = 0xf6ff9000 close(3) = 0 open("/lib/libnss_files.so.2", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\320\32"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=47496, ...}) = 0 old_mmap(NULL, 41604, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xf6feb000 old_mmap(0xf6ff4000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x8000) = 0xf6ff4000 close(3) = 0 mprotect(0xf6ff4000, 4096, PROT_READ) = 0 munmap(0xf6ff9000, 28209) = 0 open("/etc/passwd", O_RDONLY) = 3 fcntl64(3, F_GETFD) = 0 fcntl64(3, F_SETFD, FD_CLOEXEC) = 0 fstat64(3, {st_mode=S_IFREG|0644, st_size=3306, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf6fff000 read(3, "root:x:0:0:root:/root:/bin/bash\n"..., 4096) = 3306 close(3) = 0 munmap(0xf6fff000, 4096) = 0 access("/usr/libexec/dovecot/pop3-login", X_OK) = 0 open("/etc/passwd", O_RDONLY) = 3 fcntl64(3, F_GETFD) = 0 fcntl64(3, F_SETFD, FD_CLOEXEC) = 0 fstat64(3, {st_mode=S_IFREG|0644, st_size=3306, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf6fff000 read(3, "root:x:0:0:root:/root:/bin/bash\n"..., 4096) = 3306 close(3) = 0 munmap(0xf6fff000, 4096) = 0 access("/usr/libexec/dovecot/imap-login", X_OK) = 0 access("/usr/libexec/dovecot/imap", X_OK) = 0 access("/usr/lib/dovecot/imap", R_OK|X_OK) = 0 access("/usr/libexec/dovecot/pop3", X_OK) = 0 access("/usr/lib/dovecot/pop3", R_OK|X_OK) = 0 access("/usr/share/ssl/certs/dovecot.pem", R_OK) = -1 EACCES (Permission denied) write(2, "Fatal: ", 7Fatal: ) = 7 write(2, "Can\'t use SSL certificate /usr/s"..., 77Can't use SSL certificate /usr/share/ssl/certs/dovecot.pem: Permission denied) = 77 write(2, "\n", 1 ) = 1 exit_group(89) = ?

2 1

[Dovecot] Dovecot 64-bit and Pine error
by Remy Zandwijk 15 Mar '05

15 Mar '05

Hi all, I compiled a 64-bit Dovecot stable (13-03-2005) version on a Solaris 9 box with gcc 3.4.2. OpenSSL and libiconv are compiled 64-bit also. The configure I use: export CPPFLAGS="-m64 -I/var/tmp/openssl/include" export LDFLAGS="-m64 -L/var/tmp/openssl/lib" ./configure \ --prefix=/opt/dovecot \ --sysconfdir=/etc/opt/dovecot \ --disable-shared \ --with-libiconv-prefix=/var/tmp/iconv \ --without-passwd-file \ --without-shadow \ --without-vpopmail \ --without-static-userdb \ --with-ssl=openssl \ --with-ssldir=/etc/opt/dovecot/cert \ --without-pop3d Dovecot is running fine, all email clients are running fine, except for Pine (4.62). When saving a mail to another IMAP mailbox, Pine report an error message and the logfile shows: Mar 14 16:33:28 tbox dovecot: [ID 107833 local1.error] IMAP(tstud1): utime(/var/tmp/var_mailstore/ t/tstud1/.Drafts/tmp/1110814408.P2681Q0M979308.tbox) failed: Value too large for defined data type Compiling Dovecot in 32-bit, saving mail within Pine is doing just fine. I guess this is caused by maildir-save.c, line 219. Is this a bug in Solaris or Dovecot? -Remy

2 2

[Dovecot] dovecot 0.99 + apple mail.app
by sean finney 15 Mar '05

15 Mar '05

hello all, first off, a success story. after much testing and preperation, we've switched from uw-imap to dovecot. i am not kidding when i say that we have experienced an order of magnitude decrease in server load (previously load peaks were 40-60, now they are 3-4). so, suffice to say that the mail admins here are very happy :) one problem that has come up though is particular to apple's mail.app. when a client recieves a new message, they aren't notified that it's arrived, and often even when pressing "check for new mail" they don't see it come in. however, if they move from one mailbox to another, and then back, it shows up. it also shows up if thtey completely quit out of the program and start it back up. i'm going to try and get a packet dump of this to see if i can find out what's happening in the conversation, but figured in the meantime i'd put my feelers out to see if anyone else is having this problem. thanks, sean

7 9

[Dovecot] dovecot-stable mbox weirdness
by Matt Howard 14 Mar '05

14 Mar '05

I just tested dovecot-stable from 2005-03-08 and 03-12 and saw the following behavior. All of my mbox folders show is the first message's header. None of the files were truncated (whew, saves a restore). I had 0.99.12.1 installed before this, and just switched back to 0.99.14. Both 0.99.x versions work fine. I removed all of the index files to see if there was a hiccup there, with no effect. System is Slackware 10.0. My package was built with this: http://tinyurl.com/6l2vv

2 3

[Dovecot] aha! (was apple mail vs. v0.99)
by sean finney 14 Mar '05

14 Mar '05

it seems that when you say "check for new mail" in apple mail, it sends a NOOP to the imap server to get the response. in uw, the conversation is something like: 25 NOOP 25 OK NOOP completed 26 NOOP * 2796 EXISTS * 7 RECENT 26 OK NOOP completed however, with dovecot, if it has already notified the client that new mail has arrived, it will look something like: * 24 EXISTS * 2 RECENT 22 NOOP 22 OK NOOP completed. 23 NOOP 23 OK NOOP completed. (the counts are different because these are seperate accounts) so evidently, apple mail is too stupid to realize to read info from the server unless it asked for it... so now that i think i have a short-term fix (disabling notification for new mail server-side), i can breathe a sigh of relief. for a long-term fix, would it be possible to have the server always notify the client of new mail after a NOOP? thanks, sean

3 2

[Dovecot] Authentication error after authentication query (for Eudora 5.2 on Mac)
by Tim Alberts 14 Mar '05

14 Mar '05

Greetings all, I'm a new user of Dovecot and want to say thanks for the great software. I am having a problem at the moment. I run a heterogeneous network with windows and Mac clients logging into a Fedora Linux 2 box running sendmail and previously UW-IMAP, but now Dovecot. I am using strictly pop3, plain authentication with mbox format. Every computer in the network is working fine with this sytem, except 1. A mac running Eurdora mail 5.2. It gives me an Authentication error every time it tries to get mail. I telnet into the server and when I skip the AUTH process and just log in, the server works fine as follows: [talberts@localhost ~]$ telnet mail.inside.msi 110 Trying 192.168.0.3... Connected to mail.inside.msi (192.168.0.3). Escape character is '^]'. +OK dovecot ready. user tdazey +OK pass ****** +OK Logged in. quit +OK Logging out. Connection closed by foreign host. [talberts@localhost ~]$ However, when I do the following session: [talberts@localhost ~]$ telnet mail.inside.msi 110 Trying 192.168.0.3... Connected to mail.inside.msi (192.168.0.3). Escape character is '^]'. +OK dovecot ready. auth cram_md5 -ERR Unsupported authentication mechanism. auth login -ERR Unsupported authentication mechanism. auth plain + user tdazey -ERR Authentication failed. user tdazey +OK pass ****** +OK Logged in. quit +OK Logging out. Connection closed by foreign host. [talberts@localhost ~]$ I don't need any authentication except plain. However, when the client queries the settings, it fails the login. I tried this on multiple accounts with the same results. What do I do to fix this?

3 3

[Dovecot] Dovecot, pam and OpenLDAP
by Rune Hamnvik 14 Mar '05

14 Mar '05

Hello We have a Dovecot installation using only pop3 where auth data is stored in OpenLDAP and accessed using pam. With Fedora 2 everything has worked fine, but when we upgraded to Fedora 3 we started to get problems. After a while a lot of dovecot processes existed, and error messages was logged in maillog telling that the processes was too old. Then some error messages telling about memory leak was logged. Our /etc/pam.d/dovecot looks like this: #%PAM-1.0 auth required pam_nologin.so auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth session required pam_stack.so service=system-auth Any idea what is happening? Rune Hamnvik Mobinor AS Norway

1 0

Re: [Dovecot] Plain Authentication - Outlook not working
by F. Even 14 Mar '05

14 Mar '05

What problems exist with Thunderbird? Both my wife and I are using Thunderbird with no issues on both OSX and WindowsXP. (No issues that I'm noticing anyway). I'm using 1.0 Test 64: Dovecot v1.0-test64 starting up Frank Simon Windsor wrote: > Hi > > Thanks for the advice, but no luck. > > In the end, I am now using Evolution, which I do not like but it works. > It appears that Kmails IMAP and Thunderbirds IMAP are broken, > particularly kmails! > > Installing Dovecot 1.0.59 improves Dovecots IMAP software, but exposes > flaws for Kmail and Thunderbird! > > So, until the update to KDE, due at the end of March, I will endure > Evolution. > > Thanks, once again > > Simon > > On Sun, 2005-03-13 at 17:40 -0600, F. Even wrote: > >>>Hi >>> >>>I tried re-subscribing and still, I get not emails with kmail. >>> >>>Outlook appeared to pick the change in Subscription file automatically. >>> >>>Any other ideas, or should I drop the IMAP connection and re-do it? >> >>I've always had to drop my IMAP connection and reconnect to recognize >>changes I've made on the server side. A kill -1 to dovecot will only >>reload the server process and the login auth processes...it won't kill >>your already established IMAP connection, which as far as I can tell, >>keeps using old settings. >> >>If you are having that many problems, delete all of your subscriptions >>files and dovecot caches and start from scratch. I've had to do it a few >>times to get things to work as expected. >>

2 1

RE: [Dovecot] Plain Authentication - Outlook not working
by F. Even 14 Mar '05

14 Mar '05

> Hi > > I tried re-subscribing and still, I get not emails with kmail. > > Outlook appeared to pick the change in Subscription file automatically. > > Any other ideas, or should I drop the IMAP connection and re-do it? I've always had to drop my IMAP connection and reconnect to recognize changes I've made on the server side. A kill -1 to dovecot will only reload the server process and the login auth processes...it won't kill your already established IMAP connection, which as far as I can tell, keeps using old settings. If you are having that many problems, delete all of your subscriptions files and dovecot caches and start from scratch. I've had to do it a few times to get things to work as expected.

1 0

[Dovecot] Restrict Imap access
by Sergiu Zaharia 14 Mar '05

14 Mar '05

Hello. I need to restrict access to IMAP ports to a few users, so that all users can use POP3 and just a few of them will be able to access IMAP. I use secure connections POP3s and IMAPs. Is it possible? Also... When I connect to the Dovecot server using Outlook (IMAPs) I get a Warning message,something like: "The server you are connectiing to uses a non verified protection certificate. A chain of certificates ...so on ( I can't translate :) ) Continue using the server? " How can I fix that warning? Thanks

3 2

RE: [Dovecot] Plain Authentication - Outlook not working
by Timo Sirainen 13 Mar '05

13 Mar '05

On Sun, 2005-03-13 at 15:18 +0000, Simon Windsor wrote: > Hi > > I tried re-subscribing and still, I get not emails with kmail. > > Outlook appeared to pick the change in Subscription file automatically. > > Any other ideas, or should I drop the IMAP connection and re-do it? Do you even see the mailbox list? Maybe kmail got somehow confused and recreating the IMAP account entirely would be easiest way to fix it.

4 7

[Dovecot] pop before smtp with 'exact' and 'exim4'
by Jools Smyth 13 Mar '05

13 Mar '05

Hello, I just thought I would write this in case its useful to anyone. I've used dovecot for a while, as its so easy to set up, its fast and it and just "works". I recently wanted to be able to send via my server after pop3s authentication. I'm also running debian (testing) which utilises exim4 by default. I found no information about how to do it with this combination of software so went about sorting it out myself. First I got exact : (a pop before smtp daemon) http://adju.st/dist/exact/ After compiling and installing i edited its /usr/local/etc/exact-servers.conf It doesn't support dovecot's log format out of the box, so i created a regular expression entry for it. <server dovecot> order username,address match (Login): (.*) \[(.*)\] </server> I then edited its main configuration, (/usr/local/etc/exact.conf) changing only the user its running on (default mail/mail) to Debian-exim/mail. (so that the state file it creates can be read fine by exim4) I also changed the mail log ownership so that group mail can read them, /usr/local/var/state/exact to drwxr-sr-x 2 Debian-exim mail 1024 Mar 13 16:39 exact and /usr/local/var/run/exact to drwxr-sr-x 2 Debian-exim mail 1024 Mar 12 21:54 exact Exact's exim documentation is not for the most recent version, so I had to locate the correct line to modify. I went into the exim4 configuration files. I use the debian split format configuration. In the file /etc/exim4/conf.d/acl/30_exim4-config_check_rcpt there is a line near the bottom which reads accept hosts = +relay_from_hosts I changed this to accept hosts = +relay_from_hosts : net-lsearch;/usr/local/var/state/exact/rela y I then just set exact to and start/stop in /etc/init.d/exim4 thats all! Best Regards Jools -- Oxford Inspire jools(a)oxfordinspire.co.uk Tel: 01865 751879 Mob: 07966 577498

2 1

[Dovecot] Plain Authentication - Outlook not working
by Simon Windsor 13 Mar '05

13 Mar '05

Hi I have just upgraded a mail server from dovecot-0.99 to stable (dovecot-1.0.59). My normal desktop email client, kmail is working fine, but outlook keeps producing PLAIN authentication errors, and refusing to authenticate. From dovecot.log, I can see dovecot: Mar 13 10:57:30 Error: auth(default): sql(<xxxxxxxMy Detailsxxxxxxxxxxx>): Password query must return a field named "password" I have tried setting, unsetting disable_plaintext_auth in dovecot.conf, to no avail. What is happening, and what should I do to get all email cleints to work. Simon -- Simon Windsor Email: simon.windsor(a)cornfield.org.uk Tel: 01454 617689 Mob: 07720 447385

2 5

[Dovecot] "not listening" notification
by Alan Tam 13 Mar '05

13 Mar '05

Hi dovecot, My dovecot log shows this: Feb 27 03:08:38 eta imap-login: Login: sltam [X.X.X.X] Feb 27 03:09:38 eta imap-login: Disconnected: Inactivity [X.X.X.X] Feb 27 03:10:32 eta dovecot: login: received another "not listening" notification (if you can't login at all, see src/lib/fdpass.c) Feb 27 03:10:42 eta dovecot-auth: Login process has too old (124s) requests, killing it. Feb 27 03:10:42 eta dovecot-auth: Login process 8 disconnected Any clues what it means? Recently I have to restart dovecot several times a day, after I have report that all users cannot login. I am running Debian sarge (2.6.8 kernel) with dovecot version 0.99.14-1 with auth_verbose and auth_debug on. -- Regards, Alan

1 1

[Dovecot] Errors when searching large folders
by Mike Jakubik 12 Mar '05

12 Mar '05

I am getting errors from dovecot when trying to search, in large Maildir folders. The folder has 40454 messages and is 371MB in size. The email client is squirrelmail 1.4.3, running on FreeBSD-current. I've had this problem before, and i posted a message here. The author said he would fix this, but it seem the problem is still not resolved. This is the error i get: --- ERROR : Connection dropped by imap-server. Query: SEARCH CHARSET ISO-8859-1 ALL BODY {5} hello BODY {5} there --- At this point the HD led remain on for another 30 seconds or so. Thanks.

3 9

[Dovecot] Logging options
by Joebstl Thomas 12 Mar '05

12 Mar '05

Hi, is it possible to configure dovecot's logging so it logs stuff like "User x logged in from IP/Host y and had z new messages" like I'm used from qpopper? That immensely helps when debugging PEBKAC issues. Enabling auth_verbose isnt really helpfull since a failed login generates 4 lines, some even without a pid - so it's a bit hard guessing which log entry belongs to which login attempt or even writing a script which checks for those. Regards, Thomas

4 6

[Dovecot] dovecot test62 vs test64
by akolasny＠jhu.edu 12 Mar '05

12 Mar '05

Greetings: I've been using Dovecot 1.0-test62. It has been working well. I tried to upgrade to 1.0-test64 but users could not authenticate. Both versions I compiled with: ./configure --with-ssl=openssl; make; make install They compiled and installed fine. The /usr/local/etc/dovecot.conf needed to be modified due to the new syntax. 1.0-test64 with the new dovecot.conf didn't work. I'm using imaps. The error related to not being able to authenticate. I reinstalled test62 with the original dovecot.conf and everything worked fine again. My config files look like: dovecot.conf-test62 looks like: base_dir = /var/run/dovecot/ protocols = imap imaps pop3 pop3s ssl_disable = no ssl_cert_file = /usr/share/ssl/certs/dovecot.pem ssl_key_file = /usr/share/ssl/private/dovecot.pem disable_plaintext_auth = yes login_dir = /var/run/dovecot-login login = imap login = pop3 mail_extra_groups = mail default_mail_env = mbox:~/mail/:INBOX=/var/spool/mail/%u auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root dovecot.conf-test64 looks like: base_dir = /var/run/dovecot/ protocols = imap imaps ssl_disable = no ssl_cert_file = /usr/share/ssl/certs/dovecot.pem ssl_key_file = /usr/share/ssl/private/dovecot.pem disable_plaintext_auth = yes login_dir = /var/run/dovecot/login default_mail_env = mbox:~/mail/:INBOX=/var/spool/mail/%u protocol imap { } protocol pop3 { } auth default { mechanisms = plain passdb pam { } userdb passwd { } user = root } What am I doing wrong? Am I missing something in the 1.0-test64 config file? Your comments or suggestions are greatly appreciated. Thanks, Anthony

2 1

[Dovecot] more info on apple mail vs dovecot 0.99
by sean finney 11 Mar '05

11 Mar '05

hey folks, i have a little more info on this problem... about my setup: i have a mail server running dovecot imap on port 143 and uw imap on 8143. all mail is delivered directly to ~/mbox. what happens: when mail talks to dovecot, every time you check new mail, it re-downloads the entire mailbox. new mail does not show up in the inbox, even after it can be confirmed delivered (via mutt on the server). the really wierd part: even though the message doesn't show up in the list of messages in the inbox, the number of new messages floating above the dock icon (and next to the combined "In" box) *does* go up! wtf?? if you switch between mailboxes, or select "rebuild mailbox", the new message shows up of course both involve resynching the entire mailbox again... my first thought was that this was some kind of wierd application bug, but i'm not so sure. with uw-imap, when you select check new mail it does not re-download the entire mailbox, but the new message does not reliably show up until you switch from one message to another in your inbox. so it seems like there's *some* kind of difference between the two servers... and here come the questions: what would cause apple mail to always download all messages from dovecot but not from uw-imap? i found the following link, is it still relevant? http://lists.freebsd.org/pipermail/freebsd-questions/2004-April/044513.html is this something that might be resolved with 1.0-stable? is there something specific i should look for in protocol dumps? would compacting mailboxes have any effect on this? anyway, thanks to everyone who's helped so far... sean

1 0

Re: [Dovecot] Bit of a Newbie Question
by Wouter Van Hemel 11 Mar '05

11 Mar '05

On Thu, 10 Mar 2005, Jud wrote: >> You have not yet told us if you actually can receive email from outside; >> both with respect to your MTA configuration and an open (i.e. not >> firewalled) internet ip. > > I will have to investigate my MTA configuration. It's not clear to me > what is meant by an "open (not firewalled) internet ip." What > can/should I do on my system to create this condition? > Well, you should have an ip that is publicly accessible for mail servers on the internet, especially for the ones you expect will forward email. If your provider has a firewall for its customers that disallows access to certain ports (such as 25 and 80), you simply can not receive email (by SMTP). Perhaps FastMail will allow you to specify a specific port, but I doubt it. IMO, it's not a good idea to run a mailserver on a residential line with a dynamic ip; likely the contract with your isp even forbids this. Ofcourse, it's up to you to decide and try anyway. >> There is no difference for dovecot. For now, I'd say rather that the >> problem is either that your MTA doesn't accept email, or that your isp >> firewalls port 25 (which is rather likely on a dynamic ip home >> connection). > > It is probably true that my isp blocks port 25; it will be easy to > determine for sure. If so, are there any solutions you can suggest? > Do you have any accounts on remote servers? Just do a 'telnet your_internet_ip 25' ... or something along those lines. If not, try an online open relay testing service such as the one ordb provides: http://www.ordb.org/submit/ Be sure to enable test feedback. It will probably tell you enough for you to find out if it can reach your server or not. >> Read the MTA logs. See if there is any connection at all. If there is, >> check what happens with the messages (refused?). If there is not, you >> either are not accepting connections on your outside interface, or your >> provider has blocked access to port 25. >> >> Did you receive any bounces? > > Yes, though I deleted them, not even thinking to read them for > information. However, it is quite simple for me to create more bounces! > ;-) > Do so, and read the actual error message. This has very little to do with dovecot...

1 0

[Dovecot] dovecot and vpopmail
by radus＠smartpost.ro 11 Mar '05

11 Mar '05

Hello Does dovecot know to expand %d in default_mail_env to the default vpopmail domain in case the user logs without attaching the @domain in his login ? I last tried this on an old dovecot and this didn't work... Radu

1 0

[Dovecot] 1.0-test64
by Timo Sirainen 10 Mar '05

10 Mar '05

http://dovecot.org/test/ Possibly fixes the mail-cache-transaction assert. Passdb and userdb configuration changed. New format is: passdb sql { args = /etc/dovecot-sql.conf } passdb pam { } userdb passwd { } The above would first try to authenticate from SQL database, if it failed because user wasn't found, or password was wrong, it would then try PAM. The same is done for userdbs. I'll probably do some other configuration file changes still before v1.0. I'm also thinking about having a separate config process which can read the actual configuration from files or sql.

9 12

[Dovecot] Is it possible with mysql ?
by kaka 10 Mar '05

10 Mar '05

Is it possible to install dovecot imap / pop3 with mysql authentication, with postfix as mta and with squirrelmail as webmail ? Is it reliable for production state ? I'm working with courier-imap but I don't like it. Hi, kakà.

4 3

Re: [Dovecot] mail-cache-transaction.c error
by Jamie Herre 09 Mar '05

09 Mar '05

On Mar 8, 2005, at 12:50 AM, F. Even wrote: > Timo Sirainen wrote: >> On 7.3.2005, at 01:09, F. Even wrote: >>> Mar 6 16:50:59 cerebus dovecot: IMAP(problemuser): file mail-cache- >>> transaction.c: line 250 (mail_cache_transaction_reserve_more): >>> assertion failed: (size >= 2) >> I saw this a few times with my tests, but since it happened pretty >> rarely I thought it wouldn't matter much.. Guess you found a way to >> reproduce it much more easily. I'll try to look into it soon. > > Very regularly... Here's a recipe that works for me: Shutdown dovecot; Delete all "dovecot*" files from Maildir; Restart dovecot; Synchronize mailboxes. Every time I get a ton of the above exceptions.

1 1

[Dovecot] dovecot patch for TCB auth
by Thomas Hummel 08 Mar '05

08 Mar '05

Hi, I'm writing to you on behalf of the Pasteur Institute's (Paris, France) IT team. We're currently using dovecot-0.99.10.5_2 on a FreeBSD 5.3. We're planning to upgrade to dovecot-1.x with an openLDAP user and password database and patch it at the same time to include some authentication feature we're using : Since most of our user currently don't use dovecot at all and still authenticate on a DEC alpha running OSF1 [digital unix] V5.1 732, an authentication profile is maintained for each of them on the system. This user profile is kept in the protected password database, accessible only to trusted programs acting on behalf of the trusted computing base (TCB). Some TCB fields are useful to us so we're planning to use their LDAP attibute equivalents and we wrote a custom LDAP shema that includes those which were missing from the standard openLDAP distribution [see details below]. So we're planning (in fact are about to) patch dovecot-1.x in order to take those LDAP attribute (matching the TCB field of interest to us) into account. To do so, we wrote some documentation (still in a draft state) to extend our understanding of dovecot architecture and authentication process. Of course, we're going to give it (patch + doc) back to you and make it freely available. But we'd like to know if you : - were already working on such a patch or planning to do so - were interested, once done (by us or you) to include it into the official release, since it could interest some other person who runs digital unix with TCB authentication Thanks -- Thomas Hummel | Institut Pasteur, Paris, France <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau -------- Here are some details about which attribute we're planning to use and their TCB equivalents uidNumber ~ u_id uid ~ u_name userPassword ~ u_pwd shadowLastChange ~ u_succhg shadowExpire ~ u_expdate shadowMax ~ u_life shadowWarning ~ u_exp [ shadowWarning = u_life - u_exp] plus the one we wrote : maxTries ~ u_maxtries [ maximum number of consecutive unsuccessful login attempts to the account that are permitted until the account is disabled ] numUnsucLog ~ u_numunsuclog [ number of unsuccessful login attempts to the account. It is reset when a successful login to the account occurs.] Lock ~ u_lock [ A boolean indicating if the account is locked ]

2 2

[Dovecot] mail-cache-transaction.c error
by F. Even 08 Mar '05

08 Mar '05

Hello all. I've just recently (this last weekend) migrated to Dovecot on my FreeBSD 4.x box. So far, so good, I like it a lot, and plan on moving mboxes to Maildirs sometime this next weekend. BUT....I've currently run into a problem. I'm seeing an error when one user account tries to access the INBOX from Squirrelmail: Mar 6 16:50:59 cerebus dovecot: IMAP(problemuser): file mail-cache- transaction.c: line 250 (mail_cache_transaction_reserve_more): assertion failed: (size >= 2) I'm using 1.0-test63: Mar 6 04:17:47 cerebus dovecot: Dovecot v1.0-test63 starting up I've since blown away the .imap folder for this user and tried again, it still fails. Other user accounts are having no problems. Here are the relevant log snippets: Mar 6 16:18:02 cerebus dovecot: imap-login: Login: noproblems [127.0.0.1] Mar 6 16:48:48 cerebus dovecot: imap-login: Login: problemuser [127.0.0.1] Mar 6 16:48:49 cerebus dovecot: imap-login: Login: problemuser [127.0.0.1] Mar 6 16:48:52 cerebus dovecot: IMAP(problemuser): file mail-cache- transaction.c: line 250 (mail_cache_transaction_reserve_more): assertion failed: (size >= 2) Mar 6 16:48:52 cerebus dovecot: child 64331 (imap) killed with signal 6 Mar 6 16:48:52 cerebus dovecot: imap-login: Login: problemuser [127.0.0.1] Mar 6 16:50:42 cerebus dovecot: imap-login: Login: problemuser [127.0.0.1] Mar 6 16:50:59 cerebus dovecot: IMAP(problemuser): file mail-cache- transaction.c: line 250 (mail_cache_transaction_reserve_more): assertion failed: (size >= 2) Mar 6 16:50:59 cerebus dovecot: child 64391 (imap) killed with signal 6 Mar 6 16:52:54 cerebus dovecot: imap-login: Login: problemuser [127.0.0.1] Mar 6 16:52:57 cerebus last message repeated 2 times Mar 6 16:52:58 cerebus dovecot: IMAP(problemuser): file mail-cache- transaction.c: line 250 (mail_cache_transaction_reserve_more): assertion failed: (size >= 2) Mar 6 16:52:58 cerebus dovecot: child 64420 (imap) killed with signal 6 Mar 6 16:53:31 cerebus dovecot: imap-login: Login: noprob2 [127.0.0.1] Mar 6 16:53:54 cerebus last message repeated 4 times Mar 6 16:56:12 cerebus last message repeated 12 times Mar 6 16:58:12 cerebus last message repeated 11 times Mar 6 16:58:30 cerebus dovecot: imap-login: Login: noproblems [127.0.0.1] Mar 6 16:58:34 cerebus last message repeated 2 times Any help would be appreciated. Thanks, Frank

2 3

[Dovecot] Upgrade to new server question
by John Peacock 08 Mar '05

08 Mar '05

I'm vainly trying to get a new server ready to become the default mail server. We have a SAN, so I don't need to move the mailboxes (I can mount the same partition from both machines), but the question is what version of dovecot to load. I'm assuming that I cannot run both 0.99.14 and 1.00.x on the same maildirs (the indexes differ?). However, is it safe for me to mount the same maildirs from two different boxes? John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748

2 2

[Dovecot] 1.0-test63 released
by Timo Sirainen 07 Mar '05

07 Mar '05

http://dovecot.org/test/ A new test release for a change. Fixed several problems with indexes, especially related to transaction log rotating (pretty easy to find bugs when you set them to be rotated every 5 seconds and keep bombing the same mailbox with 10 test clients). Please report both new and old bugs. The changes might have fixed lots of different randomly occuring problems. The most important bugfixes were also done to dovecot-stable. The tarball is already updated. Looking at changelog, there seems to be: - Don't crash if client disconnects in the middle of APPEND - LDAP and static passdbs can return "extra parameters" (http://wiki.dovecot.org/AuthSpecials) now. Only SQL did before. - Added "nice" extra parameter for userdb to set imap/pop3 process's priority - RPA/SQL passdb patches from Andrey - Major rearrangements (again) to auth code: - Blocking passdbs (SQL) now create auth worker processes to do the actual blocking work. auth_worker_max_count setting specifies the maximum number of these processes to create. PAM and checkpassword code should be fixed to use this method as well. - Fallback to using expired records from auth cache if database lookups fail. - multiple auth setting blocks still not working - Transaction logs are now rotated when they're over 128kB and created (not updated as before) more than 5 minutes ago. So with high traffic mailboxes the log file shouldn't grow forever anymore.. - other fixes and cleanups

2 1

[Dovecot] Too many open files, etc.
by Martin Preen 07 Mar '05

07 Mar '05

Hello, a few days ago I switched out UW-server installation to dovecot 0.99.14 (Solaris 9). There were a few client issues, but mostly the migration was ok. But I have still some questions/problems: +) dovecot-auth: ... PAM: pipe() failed: Too many open files I increased the max. number of open files. Is this normal behaviour, that more than 512 open files are needed ? +) we're using mbox on NFS and index files on local disks. When building the index files for the first time, it takes (of course) a long time for large folders. But we have these users, and this will happen sometimes. Is there a way to improve performance ? +) in general dovecot saves a lot of NFS-bandwidth compared to UW-imap. Thats what I was looking for. But there also seems to be a problem with large inboxes (> 10 MB) and/or large attachments. Is this right ? One user currently gets this error from Pine when accessing a large attachment: MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR. AFAIK this error is related to some timeout problem. Has anyone seen this (and a solution for it) ? Thanks. Martin ----------------------------------------------------------------- Martin Preen, Universitaet Freiburg, Institut fuer Informatik Georges-Koehler-Allee, Geb.52, Zi.00-006, 79110 Freiburg, Germany phone: ++49 761 203-8250 preen(a)informatik.uni-freiburg.de fax: ++49 761 203-8242 www.informatik.uni-freiburg.de

4 5

[Dovecot] Can't create subfolders of my INBOX or delete folders with IMAP
by Matthew Exon 07 Mar '05

07 Mar '05

Hi, I've been using the dovecot IMAP server for about a year now, and basically it works. But there's an annoying problem, that I can't make any subfolders. I can only make folders that are at the same level as my INBOX folder. Worse, I can't delete folders once I've created them. I'm using Debian unstable on both the server machine and my client machine. The dovecot version is 0.99.13. For my mail client, I'm using Mozilla Thunderbird version 1.0. I've done a bit of investigation on my filesystem, and by googling for all kinds of stuff, but I'm really drawing a blank on this particular problem. Most of the general linux email documentation I've found either doesn't mention IMAP, or doesn't mention dovecot, or both. I can barely find any references to the concept of "subfolder" at all. I really don't want to know anything about email servers, I just want the bloody thing to work. Trying to figure out what the hell's going on is really frustrating! On the server, I seem to have various mailboxes distributed around the place. I've got a mail box in /var/spool/mail. I've got a file ~/mbox, which seems to be very old and is therefore probably a red herring. I've also got a directory ~/Mail with a bunch of files in, one for each of my folders. Having some of my mail in /var/spool, and some in my home directory, seems a really horrible way of arranging things, but anyway... Various online sources seem to suggest that maildir is better than mbox. I don't have any particular preference for one or the other, but I don't want to change if I don't have to because: 1) From experience, I don't screw with settings if I don't have to. Debian made it that way, and changing it behind Debian's back is a surefire way to cause trouble later. 2) Any other accounts on that machine (especially ones I might create in future) will probably still be mbox, causing even worse confusion later. 3) Porting mailboxes is always risky, and I don't want to lose my mail, or have incoming email dropped, or accidentally corrupt it, or anything like that. So I'm not going to do any of that unless I'm sure that it's actually going to fix the subfolder problem, and until now I haven't found any information anywhere to guarantee that that's the case. Intuitively I can guess that if a folder is just a big file full of concatenated email, then making a subfolder is going to be pretty much impossible, but I don't want to guess here. The actual symptoms in thunderbird are: When I select "New folder...", I get the "Create as a subfolder of:" dropdown hierarchy box thingy, but the "Inbox" option is greyed out (side complaint: no user interface should ever have a greyed out option without providing an explanation as to why it's not available, and what you should do if you want it to be available. Displaying it like that is just cruelly teasing the user). When I try to delete a folder, I get a dialog box saying "The current command did not succeed. The mail server responded: Mailbox doesn't exist: <name of folder>". This is pretty frustrating, because I can *see* the damn thing in thunderbird. (another side complaint: "The current command"? You're *running* the bloody command, you should have a better description than that!) For some reason though, I can rename a folder with no problems. I went into /var/log/ on the server, to see what was in the Dovecot log file about the server errors above, but there *is* no log file, nor anything in the syslog. That can't be good. How do you tell the sysadmin when there's a problem? Does anyone have any suggestions for how I can fix this? And if possible, I want to fix this the Debian way, that is by modifying a debconf setting or a /etc/default file or something like that, so that when I upgrade Debian, or uninstall dovecot and then reinstall it, it'll be handled gracefully. Thanks, Matthew Exon

6 12

[Dovecot] pop before smtp
by F. Even 07 Mar '05

07 Mar '05

I'm using the latest version of dovecot on my FreeBSD 4.x box with OpenPKG to keep other services up to date. Now...I'm able to get pbsmtp to allow relaying through postfix on this server using UW IMAP, but I would like to get dovecot working with relaying...but pbsmtp is not adding the ip when I uncomment the dovecot section after I authenticate. The log is below: [root@cerebus:/opt/sbin] ./pop-before-smtp --version version: 1.36 Mar 4 05:14:09 cerebus last message repeated 5 times Mar 4 05:19:46 cerebus dovecot: Killed with signal 15 Mar 4 05:20:00 cerebus dovecot: Dovecot v1.0-test62 starting up Mar 4 05:20:34 cerebus dovecot: imap-login: Login: user [ip.ad.dr.ess] Mar 4 05:30:21 cerebus dovecot: imap-login: Login: user [ip.ad.dr.ess] I had uncommented the stock pattern in the latest version to no avail: # For Dovecot POP3/IMAP #$pat = '^(... .. ..:..:..) \S+ (?:dovecot: )? (?:imap|pop3)-login: ' . # 'Login: \S+ \[(\d+\.\d+\.\d+\.\d+)\]'; Thanks for any help anyone might be able to provide. Frank

3 7

[Dovecot] No 'from' in messages
by Remy Zandwijk 06 Mar '05

06 Mar '05

Hi all, Over the weekend, we've migrated our old mail environment to Sendmail and Dovecot: - Dovecot 1.0 stable - Sendmail 8.13.3 - Procmail 3.22 Procmail is MDA for Sendmail and it delivers mail to Maildir boxes. Email clients like Eudora, Thunderbird, Outlook and mutt are working OK. When using Outlook Express and Pine however, in the message list the 'from' or 'sender' field is empty. This means users of these programs cannot see who did send the mail to them. When running Dovecot 0.99 in a early test period, this problem did not occur. Question: Did anyone see this behaviour before and how to fix it? Best regards, Remy Zandwijk

2 4

[Dovecot] Dovecot 1.0-stable .deb file?
by Ian R. Justman 06 Mar '05

06 Mar '05

Hi, all. I know that there's no official Dovecot 1.0-stable .deb, given Timo's recommendations. However, does anyone have even an "unofficial" deb of it for, say, Sarge? I want to use 1.0's ability to use both mbox and maildir; the latter is very helpful for dealing with mailing lists. Thanks in advance for any help. --Ian.

3 2

[Dovecot] Password scheme overides
by Andrew Hutchings 06 Mar '05

06 Mar '05

I notice in the wiki you can have password sceme overides (such as {PLAIN}password). Would this work with the password fields in SQL databases (as it isn't clear in the wiki or conf file)? Regards Andrew -- Andrew Hutchings Linux Guru Netserve Consultants Ltd. http://www.domaincity.co.uk/

1 1

[Dovecot] dovecot-pgsql.conf can't find in chroot? (debian)
by Matthew J. Harmon 06 Mar '05

06 Mar '05

In my original email I noted that the directory /usr/local/etc was in the dovecot.conf variable valid_chroot_dirs : valid_chroot_dirs = /usr/local/etc:/etc:/var/mail:/lib Is that not sufficient? Under the /var/run/dovecot directory the directories ./usr/local/etc exist with dovecot-pgsql.conf in. Is there some big RTFM item I'm missing here? -Matthew P.S. - email address changed due to problems with upstream, will jump back as soon as this is fixed so I can finish my migration :) On Sat, 2005-03-05 at 09:06 +0100, Gunter Ohrner wrote: > Am Samstag, 5. März 2005 05:27 schrieb Matthew J. Harmon: > > I have dovecot (+ssl) configured on debian in a chroot with > ^^^^^^ > > I've never run dovecot chrooted, but... > > > The file exists, and permissions look good: > > root at alfa:~# ls -la /usr/local/etc/dovecot-pgsql.conf > > ...let me guess, you're not in the chroot here? > > So, how should dovecot be able to find this file while it runs chrooted? > You need to put all needed files into the chroot. > Yep, that's how it's with 0.99.x. With 1.0-tests however Dovecot opens > the dovecot-pgsql.conf before chrooting. --- Plagued with an error I can't get past: ==> dovecot_info.log <== dovecot: Mar 04 22:09:06 Info: Dovecot starting up ==> dovecot.log <== dovecot-auth: Mar 04 22:09:07 Fatal: Can't open configuration file /usr/local/etc/dovecot-pgsql.conf: No such file or directory dovecot: Mar 04 22:09:07 Error: child 18211 (auth) returned error 89 dovecot: Mar 04 22:09:07 Error: Auth process died too early - shutting down pop3-login: Mar 04 22:09:07 Fatal: fd_send(-1) failed: Broken pipe I have dovecot (+ssl) configured on debian in a chroot with postfix+pgsql+sasl. The file exists, and permissions look good: root at alfa:~# ls -la /usr/local/etc/dovecot-pgsql.conf lrwxrwxrwx 1 root dovecot 31 2005-03-04 20:35 /usr/local/etc/dovecot-pgsql.conf -> /etc/dovecot/dovecot-pgsql.conf root at alfa:~# ls -la /etc/dovecot/dovecot-pgsql.conf -rw-r--r-- 1 root dovecot 2875 2005-03-01 23:38 /etc/dovecot/dovecot-pgsql.conf But... dovecot-auth can't see it? That's weird... root at alfa:~# strace -vffF /etc/init.d/dovecot start 1>& ~/dovecot.strace root at alfa:~# less ~/dovecot.strace [...] :/chroot [...] :/dovecot-pgsql.conf [pid 18211] open("/var/log/dovecot_info.log", O_WRONLY|O_APPEND|O_CREAT|O_LARGEFILE, 0666 <u nfinished ...> [pid 18213] fcntl64(5, F_SETFD, FD_CLOEXEC <unfinished ...> [pid 18211] <... open resumed> ) = 5 [pid 18213] <... fcntl64 resumed> ) = 0 [pid 18211] fstat64(5, <unfinished ...> [pid 18209] <... fcntl64 resumed> ) = 0 [pid 18211] <... fstat64 resumed> {st_dev=makedev(22, 1), st_ino=917830, st_mode=S_IFREG|060 0, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=16, st_size=4264, st_atime=200 5/03/04-22:09:07, st_mtime=2005/03/04-22:09:06, st_ctime=2005/03/04-22:09:06}) = 0 [pid 18211] old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0 x40019000 [pid 18211] fstat64(5, {st_dev=makedev(22, 1), st_ino=917830, st_mode=S_IFREG|0600, st_nlink =1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=16, st_size=4264, st_atime=2005/03/04-22: 09:07, st_mtime=2005/03/04-22:09:06, st_ctime=2005/03/04-22:09:06}) = 0 [pid 18211] _llseek(5, 4264, [4264], SEEK_SET) = 0 [pid 18211] fcntl64(5, F_GETFD) = 0 [pid 18211] fcntl64(5, F_SETFD, FD_CLOEXEC) = 0 [pid 18211] open("/dev/urandom", O_RDONLY|O_LARGEFILE) = 6 [pid 18211] fcntl64(6, F_GETFD) = 0 [pid 18211] fcntl64(6, F_SETFD, FD_CLOEXEC) = 0 [pid 18211] open("/etc/localtime", O_RDONLY) = 7 [pid 18211] fstat64(7, {st_dev=makedev(22, 1), st_ino=6193169, st_mode=S_IFREG|0644, st_nlin k=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=8, st_size=1279, st_atime=2005/03/04-22: 09:07, st_mtime=2004/12/26-20:19:40, st_ctime=2005/02/09-03:35:52}) = 0 [pid 18211] old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0 x4001a000 [pid 18211] read(7, "TZif\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\5\0\0\0\5\0"..., 4096) = 127 9 [pid 18211] close(7) = 0 [pid 18211] munmap(0x4001a000, 4096) = 0 ** chrooting dovecot-auth [pid 18211] chroot("/var/run/dovecot-auth") = 0 [pid 18211] chdir("/") = 0 [pid 18211] gettimeofday({1109995747, 798541}, {360, 0}) = 0 [pid 18211] rt_sigaction(SIGHUP, {0x404a07a0, [], SA_RESTORER, 0x4027e678}, NULL, 8) = 0 [pid 18211] rt_sigaction(SIGINT, {0x404a07a0, [INT], SA_RESTORER|SA_RESTART, 0x4027e678}, {SIG_DFL}, 8) = 0 [pid 18211] rt_sigaction(SIGTERM, {0x404a07a0, [TERM], SA_RESTORER|SA_RESTART, 0x4027e678}, {SIG_DFL}, 8) = 0 [pid 18211] rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0 *** lets look at dovecot-pgsql.conf! [pid 18211] open("/usr/local/etc/dovecot-pgsql.conf", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 18211] time(NULL) = 1109995747 [pid 18211] write(4, "dovecot-auth: Mar 04 22:09:07 Fa"..., 128) = 128 [pid 18211] munmap(0x40018000, 4096) = 0 [pid 18211] exit_group(89) = ? Process 18211 detached Excerpts from /etc/dovecot/dovecot.conf: auth_userdb = pgsql /usr/local/etc/dovecot-pgsql.conf auth_passdb = pgsql /usr/local/etc/dovecot-pgsql.conf login_chroot = yes valid_chroot_dirs = /usr/local/etc:/etc:/var/mail:/lib auth_chroot = /var/run/dovecot-auth Any recommended next steps? Thanks a million! -Matthew

1 0

[Dovecot] Still having problems deleting messages through IMAP
by Doug Eubanks 05 Mar '05

05 Mar '05

Hello, I am using SquirrelMail with the 1.0 releases, and I have even backed up to the latest stable release based on 1.0. I am using MailDirs. When I delete a message, the message still shows up in the message list until either I log out and back in or a new message arrives in that folder. Any ideas? Thanks Doug Eubanks doug(a)simflex.com The speed of time is one-second per second.

2 1

[Dovecot] fd_send broken pipe
by Mike Foley 05 Mar '05

05 Mar '05

Hi, I'm trying to move from UW-IMAP to Dovecot. This is on a RedHat 7.3 system and I'm using the Dovecot RPM from Dag Weirs site. dovecot-0.99.13-1.0.rh7.rf.i386.rpm http://rpmfind.net/linux/RPM/dag/redhat/7.3/i386/dovecot-0.99.13-1.0.rh7.rf… When I start up Dovecot, I get the following: dovecot: Dovecot starting up Feb 28 01:41:54 yelofsrv dovecot: Auth process died too early - shutting down Feb 28 01:41:54 yelofsrv dovecot: child 13724 (auth) returned error 127 Feb 28 01:41:54 yelofsrv imap-login: fd_send(-1) failed: Broken pipe I'm just trying to do a simple PAM/passwd type login. No MySQL/LDAP/PGSQL stuff. I've Googled till the cows came home (almost literally. I was up till 2am last night searching) and can't seem to find a straight answer. Any help/pointers? thanks, mike

2 1

[Dovecot] compile dovecot with mysql support
by Jefferson Campos 05 Mar '05

05 Mar '05

Hello! Is not possible to compile dovecot 0.99.14 version with mysql4, the dovecot configure scripts not detect the mysql4 libs. I already installed the mysql libs and devel packages... --with-mysql doesn't work! Any help or suggestion? Thanks, Jefferson

2 1

[Dovecot] dovecot-pgsql.conf can't find in chroot? (debian)
by Matthew J. Harmon 05 Mar '05

05 Mar '05

Plagued with an error I can't get past: ==> dovecot_info.log <== dovecot: Mar 04 22:09:06 Info: Dovecot starting up ==> dovecot.log <== dovecot-auth: Mar 04 22:09:07 Fatal: Can't open configuration file /usr/local/etc/dovecot-pgsql.conf: No such file or directory dovecot: Mar 04 22:09:07 Error: child 18211 (auth) returned error 89 dovecot: Mar 04 22:09:07 Error: Auth process died too early - shutting down pop3-login: Mar 04 22:09:07 Fatal: fd_send(-1) failed: Broken pipe I have dovecot (+ssl) configured on debian in a chroot with postfix+pgsql+sasl. The file exists, and permissions look good: root@alfa:~# ls -la /usr/local/etc/dovecot-pgsql.conf lrwxrwxrwx 1 root dovecot 31 2005-03-04 20:35 /usr/local/etc/dovecot-pgsql.conf -> /etc/dovecot/dovecot-pgsql.conf root@alfa:~# ls -la /etc/dovecot/dovecot-pgsql.conf -rw-r--r-- 1 root dovecot 2875 2005-03-01 23:38 /etc/dovecot/dovecot-pgsql.conf But... dovecot-auth can't see it? That's weird... root@alfa:~# strace -vffF /etc/init.d/dovecot start 1>& ~/dovecot.strace root@alfa:~# less ~/dovecot.strace [...] :/chroot [...] :/dovecot-pgsql.conf [pid 18211] open("/var/log/dovecot_info.log", O_WRONLY|O_APPEND|O_CREAT|O_LARGEFILE, 0666 <u nfinished ...> [pid 18213] fcntl64(5, F_SETFD, FD_CLOEXEC <unfinished ...> [pid 18211] <... open resumed> ) = 5 [pid 18213] <... fcntl64 resumed> ) = 0 [pid 18211] fstat64(5, <unfinished ...> [pid 18209] <... fcntl64 resumed> ) = 0 [pid 18211] <... fstat64 resumed> {st_dev=makedev(22, 1), st_ino=917830, st_mode=S_IFREG|060 0, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=16, st_size=4264, st_atime=200 5/03/04-22:09:07, st_mtime=2005/03/04-22:09:06, st_ctime=2005/03/04-22:09:06}) = 0 [pid 18211] old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0 x40019000 [pid 18211] fstat64(5, {st_dev=makedev(22, 1), st_ino=917830, st_mode=S_IFREG|0600, st_nlink =1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=16, st_size=4264, st_atime=2005/03/04-22: 09:07, st_mtime=2005/03/04-22:09:06, st_ctime=2005/03/04-22:09:06}) = 0 [pid 18211] _llseek(5, 4264, [4264], SEEK_SET) = 0 [pid 18211] fcntl64(5, F_GETFD) = 0 [pid 18211] fcntl64(5, F_SETFD, FD_CLOEXEC) = 0 [pid 18211] open("/dev/urandom", O_RDONLY|O_LARGEFILE) = 6 [pid 18211] fcntl64(6, F_GETFD) = 0 [pid 18211] fcntl64(6, F_SETFD, FD_CLOEXEC) = 0 [pid 18211] open("/etc/localtime", O_RDONLY) = 7 [pid 18211] fstat64(7, {st_dev=makedev(22, 1), st_ino=6193169, st_mode=S_IFREG|0644, st_nlin k=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=8, st_size=1279, st_atime=2005/03/04-22: 09:07, st_mtime=2004/12/26-20:19:40, st_ctime=2005/02/09-03:35:52}) = 0 [pid 18211] old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0 x4001a000 [pid 18211] read(7, "TZif\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\5\0\0\0\5\0"..., 4096) = 127 9 [pid 18211] close(7) = 0 [pid 18211] munmap(0x4001a000, 4096) = 0 ** chrooting dovecot-auth [pid 18211] chroot("/var/run/dovecot-auth") = 0 [pid 18211] chdir("/") = 0 [pid 18211] gettimeofday({1109995747, 798541}, {360, 0}) = 0 [pid 18211] rt_sigaction(SIGHUP, {0x404a07a0, [], SA_RESTORER, 0x4027e678}, NULL, 8) = 0 [pid 18211] rt_sigaction(SIGINT, {0x404a07a0, [INT], SA_RESTORER|SA_RESTART, 0x4027e678}, {SIG_DFL}, 8) = 0 [pid 18211] rt_sigaction(SIGTERM, {0x404a07a0, [TERM], SA_RESTORER|SA_RESTART, 0x4027e678}, {SIG_DFL}, 8) = 0 [pid 18211] rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0 *** lets look at dovecot-pgsql.conf! [pid 18211] open("/usr/local/etc/dovecot-pgsql.conf", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 18211] time(NULL) = 1109995747 [pid 18211] write(4, "dovecot-auth: Mar 04 22:09:07 Fa"..., 128) = 128 [pid 18211] munmap(0x40018000, 4096) = 0 [pid 18211] exit_group(89) = ? Process 18211 detached Excerpts from /etc/dovecot/dovecot.conf: auth_userdb = pgsql /usr/local/etc/dovecot-pgsql.conf auth_passdb = pgsql /usr/local/etc/dovecot-pgsql.conf login_chroot = yes valid_chroot_dirs = /usr/local/etc:/etc:/var/mail:/lib auth_chroot = /var/run/dovecot-auth Any recommended next steps? Thanks a million! -Matthew

3 2

[Dovecot] mbox or maildir?
by Brian Read 04 Mar '05

04 Mar '05

I am using dovecot in an SMEServer (aka e-smith), and recently backed-up on one system and restored on another system the imap email directories. The trouble was that dovecot "guessed" the mail type wrongly, and I ended up with "empty" ~/Mail directories (did it create or populate these?), and full, but ignored ~/Maildir directories for every user. Could someone point me to the chapter and verse of how (and when) dovecot decides which type of mail is in use, and how you can change the decision. I tried editing /etc/dovecot.conf, but that didn't seem to make any difference. Using dovecot 0.99-10 under a Redhat 7.3 base on kernel 2.4.20-18.7 -- Cheers Brian http://www.abandonmicrosoft.co.uk

3 3

[Dovecot] Dovecot response to "FETCH" command
by Alex Tang 04 Mar '05

04 Mar '05

Hi folks. I just converted my site from UW+mbox to dovecot+maildir (stable-test59, 2005/02/25). For the most part, everything is great. The server seems faster and less memory intense than the UW server (this part has made me very happy). And it's definitely more user friendly to me than Courier. There is one thing however... A few of my users are using the web based mail reader (Squirrelmail-1.2.11) that i provide for them. Once i converted to dovecot, the squirrelmail users were reporting that when viewing the folder list page, 2 things were happening: * The date for all of the messages was being displayed as "Sun 4:00 pm" * all messages were shown as being "new". they never would be transferred into the "Seen" state. After doing some IMAP protocol sniffing, i found this difference in the way that the UW server and the dovecot server handles the "FETCH" command... Squirrelmail issues a FETCH command to get message header information like this (lines broken with backslashes for readability): A009 FETCH 1:1 (FLAGS RFC822.SIZE INTERNALDATE BODY.PEEK \ [HEADER.FIELDS (Date To From Cc Subject X-Priority \ Content-Type)]) The UW server returns: * 1 FETCH (FLAGS () RFC822.SIZE 710 \ INTERNALDATE "27-Feb-2005 23:50:42 -0800" \ BODY[HEADER.FIELDS ("DATE" "TO" "FROM" "CC" "SUBJECT" \ "X-PRIORITY" "CONTENT-TYPE")] {153} Date: Sun, 27 Feb 2005 23:50:42 -0800 From: root <root(a)scorchedearth.us.proofpoint.com> To: altitude(a)scorchedearth.us.proofpoint.com Subject: asdf When the same FETCH response is returned by dovecot, the response looks like this: FLAGS () RFC822.SIZE 3358 INTERNALDATE "27-Feb-2005 07:55:27 -0800") * 1 FETCH (BODY[HEADER.FIELDS (DATE TO FROM CC SUBJECT X-PRIORITY CONTENT-TYPE)] {205} Date: Mon, 28 Feb 2005 00:04:22 +0800 From: xxx xxx <xxx(a)xxx.com> To: dovecot(a)dovecot.org Content-Type: text/plain; charset=UTF-8; format=flowed Subject: [Dovecot] "not listening" notification I noticed that in the UW response, the "* 1 FETCH ..." is the first line, and contains all of the data except for the message header info. However, in the dovecot response, the data is split into 2 lines, and the first line is not the "* 1 FETCH" line. In reading through the squirrelmail source, squirrelmail is not recognizing this as a valid response, and thus the date, size, and flags are not being properly set in the internal squirrelmail message objects. This explains why both the date as well as the "seen" status of the message is never properly set. OK, after all this blabbing on...here's my question. Is the data being sent back by dovecot a valid response? My knowledge of the IMAP protocol is weak to say the least. I tried reading the IMAP RFC (3501), in particular section 6.4.5 which defines the FETCH command), and the RFC seems to specify that the response should have the "* # FETCH" lines come first. However, the RFC seems vague, and i didn't wade through any of the other RFCs out there. I figure it is legal, since the two other clients i've used seem to understand it just fine (thunderbird/mozilla, mutt). However, could this be the reason why mozilla/thunderbird sometimes gets the message size wrong (and hence why the "tb-negative-fetch" workaround is needed). For now, i'll bang on squirrelmail to support the response sent by dovecot. Thanks. ...alex...

3 4

[Dovecot] hanging imap... and users getting other users' emails!
by Josh Burley 03 Mar '05

03 Mar '05

Hi All, We recently upgraded from UW (boy, starting to sound like a broken record, eh?)... Two problems: 1. Every two or three days users are unable to access their email via IMAP. It seems that it's because dovecot-auth has hung. Has anyone seen anything like this? 2. (the really serious one)... one of our users, "angie" has twice had her Outlook download other users' email! Once as another user, "helene", and just now as "mkarlin". The first time she got 800 of helene's email, and just now, about 30 of mkarlin's.... from our log, I noticed: Mar 2 17:27:10 core imap-login: Login: mkarlin [::ffff:128.195.131.2] Mar 2 17:27:10 core imap-login: Login: mkarlin [::ffff:128.195.131.2] Mar 2 17:27:11 core pop3-login: Login: angie [::ffff:68.231.223.128] Mar 2 17:27:11 core imap-login: Login: mkarlin [::ffff:128.195.131.2] Mar 2 17:27:11 core imap-login: Login: mkarlin [::ffff:128.195.131.2] Our server setup: Fedora Core 3. dovecot-0.99.13. OpenLDAP, and dovecot auth'ing off PAM (mostly default setup, using Mailbox, and mail/ as a subdir). Any ideas? Any more debug info I can supply? .josh

4 10

[Dovecot] Is Dovecot SMP and thread-safe?
by Peter Franck 03 Mar '05

03 Mar '05

Josh´s problem report reminds me of other multi-CPU issues. Just a guess, Peter

5 5

[Dovecot] selective POP3 user
by Barry Kwok 03 Mar '05

03 Mar '05

I want to know if it is possible to limit some users to use POP3 service only in a server running BOTH IMAP and POP3 service. In other words, some users can choose IMAP or POP3 and some users can only use POP3. Barry

3 2

[Dovecot] Several issues with 1.0-stable
by Remy Zandwijk 03 Mar '05

03 Mar '05

All, We have Dovecot 1.0-stable deployed in our 3000 users environment as of last weekend. Up untill now, I have 3 issues: - When stopping Dovecot with: kill -TERM `cat /var/run/dovecot/master.pid`, the 'dovecot' process itself dies, the 'imap-login' processes die, but the 'imap' processes (there are a lot of them) don't die, but become a zombie. I think the way I stop Dovecot is the way to do it. The zombies can be killed by doing a 'pkill -9 imap', but that's not quite elegant. - Dovecot is running in a Solaris 9 environment. It turned out that Dovecot crashes when more then 256 filedescriptors are being used. This is rather normal, since Solaris only support 256 descriptors per 32-bit process. After starting Dovecot, I do a 'plimit -n 8192, 8192 `cat /var/run/dovecot/master.pid`, which allows Dovecot to have 8192 filedescriptors. Timo, is it possible to introduce a config file option to configure the number of descriptors? - Pine and Outlook users don't see the adresses or names of the people who sent them email. In my email yesterday, I said I remembered that tests with Dovecot 0.99 showed no problems. Today, I installed both Dovecot 0.99 and 1.0-stable on my test box. It turned out that 0.99 indeed works OK and that 1.0-stable is the problem. The user mailboxes are 'Maildir'; we do not use mbox format. I like to see this problem being fixed..... We have 2 namespaces in our setup: the default namespace and a namespace which location is set to ~/.Mailstorage. When not using a prefix in the email client setup, users can make new email folders in the default namespace and the 'Mailstorage' namespace. We want users only to create mail folders in the Mailstorage namespace, not in the default namespace. Questions: - Is it possible to force a prefix to clients? - If not, is it usefull to have an option in the namespace configuration that allows or disallows the creation of mail folder? If so: consider this as a feature request. Thank you for reading, best regards, Remy Zandwijk Free University of Amsterdam The Netherlands

2 1

[Dovecot] Newby Question
by Troy Bull 03 Mar '05

03 Mar '05

Hello I just setup my IMAP server and everything works great, except for 1 small detail. I am upgrading from uwashington's imap server, and in theirs I had to put a directory "mail" in for the imap folder (this is on the client). The problem I have is with dovecot this makes an extra level (I think). So on my server ~/mail is where the mail folder is located, but when the client puts in the "mail" for the imap server directory dovecot looks in and creates folders in ~/.mail/mail. This is a problem for me because I have many clients and I would have to go reconfigure each one. My question is this, is there a way to make dovecot look in ~/ so that when combined with the imap folder from the client it ends up in ~/mail? I hope that is clear enough, I was thinking maybe I need to set default_mail_env, but i have no idea to what? Thanks in advance Troy

2 1

[Dovecot] Trigger getmail via mail-client action?
by Gert Brinkmann 03 Mar '05

03 Mar '05

Hello, I want to use dovecot on my private debian/unstable-system to have the advantages of an IMAP-Server (Access to mails from different computers, Simply changing the mail client). I decided to use dovecot, because I very often have read (in the web) that it should be more simple to configure than other servers. Now I have the following question: I want to use getmail to retrieve mails from my provider's pop3-server. I do have a dial-up-connection that is not online permanently (I do not have a flat rate). I could start a script on ppp's ip-up that periodically invokes getmail and on ip-down to kill it again. But I would prefer to invoke getmail only when I really want it to be run. The ideal solution for me was to invoke getmail when the "Get Mail"-Button of the mail client is pressed. Is this possible? Perhaps there is something like a connection- or refresh-trigger in dovecot? Thank you, Gert

4 5

[Dovecot] Dovecot started by inetd
by Peter Franck 03 Mar '05

03 Mar '05

Is anyone else starting dovecot by inetd on the list? I'm unable to get it running, stupid me. I need help by someone more experienced. Peter

2 1

Re: [Dovecot] Too many open files, etc.
by Remy Zandwijk 28 Feb '05

28 Feb '05

> a few days ago I switched out UW-server installation to > dovecot 0.99.14 (Solaris 9). There were a few client issues, > but mostly the migration was ok. > > But I have still some questions/problems: > > +) dovecot-auth: ... PAM: pipe() failed: Too many open files > I increased the max. number of open files. Is this normal > behaviour, that more than 512 open files are needed ? Martin, we're dealing with the same problem right now. We are using dovecot 1.0 stable and we migrated last weekend. 32-bit processes in Solaris 9 have 256 filedescriptors avail- able. This seems a bit to small. Using this command to get the number of file descriptors used by dovecot: ls -1 /proc/`cat /var/run/dovecot/master.pid`/fd | wc In our enviroment this is currently around 390. You can limit the number of file descriptors per process in Solaris 9. After starting Dovecot, we issued the command: plimit -n 8192,8192 `cat /var/run/dovecot/master.pid` This gives Dovecot 8192 filedescriptors. HTH, Remy

1 0

[Dovecot] UID inserted in the middle of mailbox
by Nicolas STRANSKY 28 Feb '05

28 Feb '05

I'm seeing these with latest 1.0-stable : Feb 27 16:48:12 zamok dovecot: POP3(****): mbox sync: UID inserted in the middle of mailbox /var/mail/**** (176 > 150) Feb 27 16:49:58 zamok dovecot: POP3(****): mbox sync: UID inserted in the middle of mailbox /var/mail/**** (4409 > 4237) Feb 27 16:50:04 zamok dovecot: IMAP(****): mbox sync: UID inserted in the middle of mailbox /var/mail/**** (7122 > 5116) Feb 27 16:50:16 zamok dovecot: IMAP(****): mbox sync: UID inserted in the middle of mailbox /home/****/Mail/trash (15571 > 14535) Feb 27 16:50:16 zamok dovecot: IMAP(****): mbox sync: UID inserted in the middle of mailbox /home/****/Mail/trash (16578 > 14535) Feb 27 16:50:19 zamok dovecot: IMAP(****): mbox sync: UID inserted in the middle of mailbox /var/mail/**** (23318 > 13713) -- Nico L'étude approfondie de la nature est la source la plus féconde des découvertes mathématiques. -+- Joseph Fourier -+-

2 1

[Dovecot] Protect some mailbox to remove
by FireFly 25 Feb '05

25 Feb '05

I've installed dovecot 0.99.14 (maildir, postfix, RHEL3) and I would like to create , for every user, 4 mailbox (in skel): mail-sent, spam, virus-alert and sysadm. Procmail, parsing header mail, will move mails into a specific mailbox. Every users could move, delete, read these mails but they must not delete mailbox folder (such as INBOX mail). Thanks in advance, Francesco __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

[Dovecot] APOP
by Steven Stern 25 Feb '05

25 Feb '05

I want to turn off POP3 and use POP3S in its place. So far, it's working well for Outlook and Thunderbird. But I'm running into problems with Agent: It supports APOP but not POP3S. Is there a way to have Dovecot support APOP authentication on a normal POP3 connection? I'm running 0.99.13 on Fedora Core 3. -- Steve

2 1

[Dovecot] A few words about NFS please?
by Jeff A. Earickson 25 Feb '05

25 Feb '05

Hi, Could you say a few words about Dovecot and POP/IMAP to an NFS mounted filesystem? I thought I saw on the dovecot webpage that NFS is "no way" with 0.99 and "maybe" with 1.x. I was looking for the FAQ and couldn't find it. My setup is like so: My mail server is a Solaris 9 system, running sendmail/procmail, and qpopper POP. Mail is stored in mbox format. The /var/mail filesystem is NFS exported to another Solaris 9 system that runs UW-IMAP. The user community also has login access to this second system, so there are also local email clients like Pine and emacs using the NFS /var/mail. So, POP and sendmail/procmail accesses /var/mail locally, while UW-IMAP accesses it via NFS. The user community has been warned to do either POP or IMAP, but not both. There are very few problems with this setup. I would like to use Dovecot for both POP and IMAP on the two machines. I know NFS is frowned upon, but this has worked for me. Comments and suggestions, please? Jeff Earickson Colby College

4 3

[Dovecot] Inotify
by Nicolas STRANSKY 25 Feb '05

25 Feb '05

Hi, Is there any plans to use the Linux inotify, which is a major improvement over dnotify ? (Linux mechanism for communicating filesystem events to user space) Regards, -- Nico Écrivez dans l'ivresse, mais relisez-vous à jeun. -+- André Gide (1869-1951) -+-

2 1

[Dovecot] Authentication woes
by woollettg 25 Feb '05

25 Feb '05

I having a hard time working this out, I've looked in the wiki and various other places but am still cueless (stupid me) mercury:/etc/dovecot# imtest -a graeme 203.96.154.204 S: * OK dovecot ready. C: C01 CAPABILITY S: * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE STARTTLS AUTH=PLAIN S: C01 OK Capability completed. Authentication failed. no mechanism available Security strength factor: 0 mercury:/etc/dovecot# Below is my configuration file for version 0.99-14.1 on a Debian Sarge box I'm quite happy with plaintext auth for now. Any help or suggestions much appreciated. Graeme ## Dovecot 1.0 configuration file # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc/dovecot # --localstatedir=/var --with-ssldir=/etc/ssl # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s protocols = imap # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. You can specify ports with # "host:port". #imap_listen = * #pop3_listen = * # IP or host address where to listen in for SSL connections. Defaults # to above non-SSL equilevants if not specified. #imaps_listen = #pop3s_listen = # Disable SSL/TLS support. #ssl_disable = no # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. #ssl_cert_file = /etc/ssl/certs/dovecot.pem #ssl_key_file = /etc/ssl/private/dovecot.pem # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 24 # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. disable_plaintext_auth = no # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). #log_path = # For informational messages, use this logfile instead of the default #info_log_path = # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = /var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. # http://wiki.dovecot.org/Rootless #login_chroot = yes ## ## IMAP login process ## login = imap # Executable location. login_executable = /usr/lib/dovecot/imap-login # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. # Note that this user is NOT used to access mails. # http://wiki.dovecot.org/UserIds #login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 32 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to create. If login_process_per_user is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_user # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 ## ## POP3 login process ## # Settings default to same as above, so you don't have to set anything # unless you want to override them. login = pop3 # Exception to above rule being the executable location. #login_executable = /usr/lib/dovecot/pop3-login ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. mail_extra_groups = mail # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See # /usr/share/doc/dovecot-common/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden by # giving /./ in user's home directory (eg. /home/./user chroots into /home). #mail_chroot = # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # /usr/share/doc/dovecot-common/mail-storages.txt. There's a few special # variables you can use: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if user there's no domain # %h - home directory # # You can also limit a width of string by giving the number of max. characters # after the '%' character. For example %1u gives the first character of # username. Some examples: # # default_mail_env = maildir:/var/mail/%1u/%u/Maildir # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # #default_mail_env = # Space-separated list of fields to cache for all mails. Currently these # fields are allowed followed by a list of commands they speed up: # # Envelope - FETCH ENVELOPE and SEARCH FROM, TO, CC, BCC, SUBJECT, # SENTBEFORE, SENTON, SENTSINCE, HEADER MESSAGE-ID, # HEADER IN-REPLY-TO # Body - FETCH BODY # Bodystructure - FETCH BODY, BODYSTRUCTURE # MessagePart - FETCH BODY[1.2.3] (ie. body parts), RFC822.SIZE, # SEARCH SMALLER, LARGER, also speeds up BODY/BODYSTRUCTURE # generation. This is always set with mbox mailboxes, and # also default with Maildir. # # Different IMAP clients work in different ways, that's why Dovecot by default # only caches MessagePart which speeds up most operations. Whenever client # does something where caching could be used, the field is automatically marked # to be cached later. For example after FETCH BODY the BODY will be cached # for all new messages. Normally you should leave this alone, unless you know # what most of your IMAP clients are. Caching more fields than needed makes # the index files larger and generate useless I/O. # # With maildir there's one extra optimization - if nothing is cached, indexing # the maildir becomes much faster since it's not opening any of the mail files. # This could be useful if your IMAP clients access only new mails. #mail_cache_fields = MessagePart # Space-separated list of fields that Dovecot should never set to be cached. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Workarounds for various client bugs: # oe6-fetch-no-newmail: # Never send EXISTS/RECENT when replying to FETCH command. Outlook Express # seems to think they are FETCH replies and gives user "Message no longer # in server" error. Note that OE6 still breaks even with this workaround # if synchronization is set to "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. # outlook-pop3-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. #client_workarounds = # Dovecot can notify client of new mail in selected mailbox soon after it's # received. This setting specifies the minimum interval in seconds between # new mail notifications to client - internally they may be checked more or # less often. Setting this to 0 disables the checking. # NOTE: Evolution client breaks with this option when it's trying to APPEND. #mailbox_check_interval = 0 # Like mailbox_check_interval, but used for IDLE command. #mailbox_idle_check_interval = 30 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no # Maximum allowed length for custom flag name. It's only forced when trying # to create new flags. #mail_max_flag_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. #mail_read_mmaped = no # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing messages are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's three available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # # You can use both fcntl and flock too; if you do the order they're declared # with is important to avoid deadlocks if other MTAs/MUAs are using both fcntl # and flock. Some operating systems don't allow using both of them # simultaneously, eg. BSDs. If dotlock is used, it's always created first. #mbox_locks = dotlock fcntl # Should we create dotlock file even when we want only a read-lock? Setting # this to yes hurts the performance when the mailbox is accessed simultaneously # by multiple processes, but it's needed for reliable reading if no other # locking methods are available. #mbox_read_dotlock = no # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. Note that setting # this to yes means that log file is opened as the logged in user, which # might not work. It could also be a small security risk if you use single UID # for multiple users, as the users could ptrace() each others processes then. #mail_drop_priv_before_exec = no ## ## IMAP process ## # Executable location imap_executable = /usr/lib/dovecot/imap # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #imap_process_size = 256 # Support for dynamically loadable modules. #imap_use_modules = no imap_modules = /usr/lib/dovecot/imap ## ## POP3 process ## # Executable location #pop3_executable = /usr/lib/dovecot/pop3 # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #pop3_process_size = 256 # Support for dynamically loadable modules. #pop3_use_modules = no #pop3_modules = /usr/lib/dovecot/pop3 ## ## Authentication processes ## # An Authentication process is a child process used by Dovecot that # handles the authentication steps. The steps cover an authentication # mechanism (auth_mechanisms, how the client authenticates in the IMAP or # POP3 protocol), which password database should be queried (auth_passdb), # and which user database should be queried (auth_userdb, to obtain # UID, GID, and location of the user's mailbox/home directory). # # You can have multiple processes, though a typical configuration will # have only one. Each time "auth = xx" is seen, a new process # definition is started. The point of multiple processes is to be able # to set stricter permissions. (See auth_user below.) # # Just remember that only one Authentication process is asked for the # password, so you can't have different passwords accessible through # different process definitions (unless they have different # auth_mechanisms, and you're ok with having different password for # each mechanisms). # Authentication process name. auth = default # Specifies how the client authenticates in the IMAP protocol. # Space separated list of permitted authentication mechanisms: # anonymous plain digest-md5 cram-md5 # # anonymous - No authentication required. # plain - The password is sent as plain text. All IMAP/POP3 clients # support this, and the password can be encrypted by Dovecot to match # any of the encryption schemes used in password databases. # digest-md5 and cram-md5 - both encrypt the password so it is more # secure in transit, but are not well supported by clients, and # require that the password database use a matching encryption # scheme (or be in plaintext). # # See auth.txt for more details. # # If you are using SSL there is less benefit to digest-md5 and # cram-md5 as the communication is already encrypted. auth_mechanisms = plain # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # http://wiki.dovecot.org/Authentication # http://wiki.dovecot.org/VirtualUsers # passwd: /etc/passwd or similiar, using getpwnam() # passwd-file <path>: passwd-like file with specified location # static uid=<uid> gid=<gid> home=<dir template>: static settings # vpopmail: vpopmail library # ldap <config path>: LDAP, see /etc/dovecot/dovecot-ldap.conf # mysql <config path>: a MySQL database, see /etc/dovecot/dovecot-mysql.conf # pgsql <config path>: a PostgreSQL database, see # /etc/dovecot/dovecot-pgsql.conf auth_userdb = passwd # Password database specifies only the passwords for users. # http://wiki.dovecot.org/Authentication # passwd: /etc/passwd or similiar, using getpwnam() # shadow: /etc/shadow or similiar, using getspnam() # pam [<service> | *]: PAM authentication # passwd-file <path>: passwd-like file with specified location # vpopmail: vpopmail authentication # ldap <config path>: LDAP, see /etc/dovecot/dovecot-ldap.conf # mysql <config path>: a MySQL database, see /etc/dovecot/dovecot-mysql.conf # pgsql <config path>: a PostgreSQL database, see # /etc/dovecot/dovecot-pgsql.conf auth_passdb = passwd #auth_executable = /usr/lib/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by auth_userdb above. auth_user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. #auth_chroot = # Number of authentication processes to create #auth_count = 1 # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. auth_verbose = yes # Even more verbose logging for debugging purposes. Shows for example SQL # queries. #auth_debug = no # digest-md5 authentication process. It requires special MD5 passwords which # /etc/shadow and PAM doesn't support, so we never need roots to handle it. # Note that the passwd-file is opened before chrooting and dropping root # privileges, so it may be 0600-root owned file. #auth = digest_md5 #auth_mechanisms = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = # if you plan to use only passwd-file, you don't need the two auth processes, # simply set "auth_methods = plain digest-md5"

3 2

[Dovecot] Re: Problems with MySQL/PAM authentication
by KATOH Yasufumi 25 Feb '05

25 Feb '05

> I'm using (or trying to at least) a combination of PAM/passwd and MySQL > authentication: : (snip) > MySQL authentication works without problems but authentication real > (system) users dosn't: : I have similar problem using Multiple Auth Database: auth virtual { mechanisms = plain userdb = passwd-file /etc/dovecot/passwd passdb = passwd-file /etc/dovecot/passwd user = root } auth local { mechanisms = plain userdb = passwd passdb = shadow user = root } I tested: | % telnet localhost 143 | Trying 127.0.0.1... | Connected to localhost. | Escape character is '^]'. | * OK Dovecot ready. | 1 login kato(a)harp.gr.jp password | 1 NO Authentication failed. | 1 login kato(a)harp.gr.jp password | 1 OK Logged in. | 1 logout | * BYE Logging out | 1 OK Logout completed. | Connection closed by foreign host. "kato(a)harp.gr.jp" is registered in /etc/dovecot/passwd. First time it failed, but success at second time. "auth local" works without problem. | Feb 24 11:19:24 tara dovecot: auth(local): shadow(kato(a)harp.gr.jp,127.0.0.1): unknown user | Feb 24 11:19:33 tara dovecot: auth(local): shadow(kato(a)harp.gr.jp,127.0.0.1): unknown user | Feb 24 11:19:33 tara dovecot: auth(virtual): userdb(kato(a)harp.gr.jp,127.0.0.1): uid=1000 gid=100 home=/home/kato mail= | Feb 24 11:19:33 tara dovecot: IMAP(kato(a)harp.gr.jp): mkdir(/home/kato(a)harp.gr.jp/Maildir/cur) failed: Permission denied | Feb 24 11:19:33 tara dovecot: imap-login: Login: kato(a)harp.gr.jp [127.0.0.1] | Feb 24 11:19:35 tara dovecot: auth(local): file auth-client-connection.c: line 31 (auth_client_send): assertion failed: (conn->refcount > 1) | Feb 24 11:19:35 tara dovecot: child 14884 (auth) killed with signal 6 I rewritten dovecot.conf and tested. The result is different. auth local { mechanisms = plain userdb = passwd passdb = shadow user = root } auth virtual { mechanisms = plain userdb = passwd-file /etc/dovecot/passwd passdb = passwd-file /etc/dovecot/passwd user = root } At this time, "auth virtual" work, and "auth local" doesn't work. | * OK Dovecot ready. | 1 login kato(a)harp.gr.jp password | 1 OK Logged in. | 1 logout | * BYE Logging out | 1 OK Logout completed. | * OK Dovecot ready. | 1 login kato password | 1 NO Authentication failed. | 1 login kato password | 1 OK Logged in. | 1 logout | * BYE Logging out | 1 OK Logout completed. (kato is system user) | Feb 24 11:28:52 tara dovecot: auth(virtual): passwd-file(kato,127.0.0.1): unknown user | Feb 24 11:28:59 tara dovecot: auth(virtual): passwd-file(kato,127.0.0.1): unknown user | Feb 24 11:28:59 tara dovecot: auth(local): userdb(kato,127.0.0.1): uid=1000 gid=100 home=/home/kato mail= | Feb 24 11:28:59 tara dovecot: imap-login: Login: kato [127.0.0.1] | Feb 24 11:28:59 tara dovecot: auth(virtual): file auth-client-connection.c: line 31 (auth_client_send): assertion failed: (conn->refcount > 1) | Feb 24 11:28:59 tara dovecot: child 14924 (auth) killed with signal 6 It is not worked well to write configuration previously, but worked well to write after. I tested with ldap auth instead of paswd-file auth. I got same result. Env: Plamo Linux 4.01 (kernel 2.6.10, glibc 2.3.2) dovcot-1.0-test62, dovecot-stable-20050222 -- karma @ jazz.email.ne.jp / Y.KATOH Sorry for my poor English.

2 2

[Dovecot] Limit Number of Postgres Database Connections
by Dan Fitzpatrick 25 Feb '05

25 Feb '05

I have dovecot running with postgres backend. I am exceeding my maximum database connections (currently 40) with dovecot 0.99.10.9 and postfix and was wondering if dovecot has a parameter to limit the total number of database connections that it will create. Dan

2 1

[Dovecot] mozilla, error in imap command uid
by Nicolas Kowalski 24 Feb '05

24 Feb '05

Hello. Mozilla (1.7.3) gives me the following error message when trying to view some messages: the mail server responded: Error in IMAP command UID: Invalid BODY[..] parameter: Missing '>' in '<10240.-7730>'. What's wrong ? Thanks. -- Nicolas

5 9

[Dovecot] Nightly stable & SSL-problems
by Jani Karlsson 23 Feb '05

23 Feb '05

Getting it otherwise to work, but I still can't get it to listen any SSL-ports. been testing: protocols = imap imaps pop3 pop3s listen = 193.65.59.150 ssl_listen = 193.65.59.150 doesn't help. with: ssl_disable = no of course. protocol imap { # Login executable location. login_executable = /usr/local/libexec/dovecot/imap-login # IMAP executable location mail_executable = /usr/local/libexec/dovecot/imap ssl_listen = 193.65.59.150 .... } tried it there also.. yet: tcp 0 0 193.65.59.150:110 0.0.0.0:* LISTEN 29030/dovecot tcp 0 0 193.65.59.150:143 0.0.0.0:* LISTEN 29030/dovecot is the result I get. Anyone succeeded in this? Platform is Debian/Linux, running 2.4 series kernel, compiled with openssl-support. Version is dovecot-stable-20050221. All help appreciated. Jani Karlsson

2 1

[Dovecot] Build error in stable branch
by Andrew Hutchings 23 Feb '05

23 Feb '05

Hi guys, Just tested yesterday's stable build, when including SQL into the build I am getting an error on like 86 of passdb-sql.c (passdb_result = PASSDB_RESULT_OK;) It rightly says passdb_result is undeclared. Commenting out this line fixes it and build appears to work fine after that. Regards Andrew -- Andrew Hutchings Linux Guru Netserve Consultants Ltd. http://www.domaincity.co.uk/

1 0