- dovecot - dovecot.org

[Dovecot] Help setting up SSL?
by Mike Matz 11 Jun '03

11 Jun '03

Hi, Sorry to bother, I don't know if this mailing list is the right place to look for help setting up dovecot.. Anyway I've got standard IMAP working fine, and I used mkcert.sh after editing the openssl config, and it seemed to work properly (I had to change some directories, I am using the FreeBSD 5.1-CURRENT port).. Anyway, when I try to connect using Outlook, here is what the log shows: (without the exact ip address shown, dont hax0r my windows machine!) imap-login: Jun 10 13:13:14 Warning: SSL_accept() failed: error:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac [12.106.77.x] imap-login: Jun 10 13:13:14 Warning: SSL_accept() syscall failed: EOF [12.106.77.x] imap-login: Jun 10 13:13:14 Panic: key not found from hash dovecot: Jun 10 13:13:14 Error: child 32935 (login) killed with signal 6 imap-login: Jun 10 13:13:14 Warning: SSL_accept() failed: error:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac [12.106.77.x] imap-login: Jun 10 13:13:14 Warning: SSL_accept() syscall failed: EOF [12.106.77.x] imap-login: Jun 10 13:13:14 Panic: key not found from hash dovecot: Jun 10 13:13:14 Error: child 32937 (login) killed with signal 6 so it says "decryption failed or bad record mac".. Does this mean I don't have my .pem files set up correctly? Or is there a problem with the OpenSSL libraries? I'd sure appreciate any help you could give me. Thanks, Mike

2 1

[Dovecot] gnutls_handshake problem
by Jacob Elder 07 Jun '03

07 Jun '03

I'm trying to bring dovecot up on Debian/stable using Christof Meerwald's unofficial packages (cmeerw.org/debian/) This package seems to work fine on Debian/testing. There error I'm getting on the stable box is: gnutls_handshake: A TLS fatal alert has been received.(Bad record MAC) Any guesses? -- Jacob Elder

4 3

[Dovecot] Dovecot for Gentoo portage
by Zach Bagnall 04 Jun '03

04 Jun '03

Hi all - I've added an ebuild for 0.99.9.1 to bugzilla: http://bugs.gentoo.org/show_bug.cgi?id=22080 It includes the CR+LF patch. Should be trivial to update for .10 when it makes an appearance :-). Feel free to fix/improve this ebuild - I'm fairly new at them. Zach. -- Services & Support Bulletin Wireless | www.bulletinwireless.com This email is digitally signed | Key ID 0x3F9AA9A2

1 0

[Dovecot] error
by Farkas Levente 03 Jun '03

03 Jun '03

hi, I've got the following alert window in mozilla (with dovecot): --------------------------------------- The current command did not succeed. The mail server responded: Error in IMAP command: Too long argument.. --------------------------------------- although there is not any messages in my imap.log file. -- Levente "Si vis pacem para bellum!"

2 1

[Dovecot] dovecot 0.99.10-test10
by Andrew Basterfield 31 May '03

31 May '03

Hiya builds fine on BSD now (thanks) Now I am getting index corruption again May 30 03:11:53 snigger imap(bob): Corrupted binary tree file /home/bob/Mail/.INBOX/.imap.index.tree: UID to be inserted isn't higher than existing (1 <= 1) and so on until the client hangs test7 is stable here. Also what are the correct permissions for /var/run/dovecot/login? I get a message about correcting the permissions every time I start dovecot --Andrew -- http://cemetery.homeunix.org

2 3

[Dovecot] the most serius problems [part 3]
by Farkas Levente 30 May '03

30 May '03

hi, so the third problem is ssl. the imaps is still not working (and I assume the same apply to pop3s too). I already send the log file which was generated when verbose ssl is set. -- Levente "Si vis pacem para bellum!"

4 3

[Dovecot] the most serius problems [part 2]
by Farkas Levente 30 May '03

30 May '03

hi, the second thing is the webmail. we use squirrelmail. actualy I don't know whose fault is, but they told that them imap server's:-) first problems is that those mails which has empty body (even if they has an attachments) simple not shown in the mail list (as they even not exists). it'd be nice to check this and find the reason of the problem. this happend with more people. -- Levente "Si vis pacem para bellum!"

2 2

[Dovecot] the most serius problems [part 1]
by Farkas Levente 30 May '03

30 May '03

hi, I try to collect out most serious problem with dovecot. so I write a series of mails:-) the first on is the load. has anybody else use dovecot in a real enviromnt with at least hundreds of users and at least 50 concurrent user at the same time? it seems to me no one else just me. the weekend I move the whole mail system to a quad P4 with 1Gb ram and this server do nothing just imap. yesterday evening I have to delete all .imap.index and other dovecot specific files. and as I wrote today morning the load was about 20-30 !!!. but even in an average day the load is over 2-3 white the cpu load is 1-2% in each of the 4 processor. the system is totaly unusable. what more today I've got other errors. of course all the time when I can't find the colution I try to escape to the latest cvs. today finally I compile a new courier install it to another port and those clients which can't connect to dovecot reconfigure to courier. but they are not compatible!!! I have to set root directory to INBOX in courier while not for dovecot and this is a real big problem. is there any way to compile dovecot to use INBOX as a root directory? since in this case at least there is a chance to switch to courier without reconfigure 300 OE6. I try to help to find out the reason for the load in any way, but it seems to me than it's better to change to courier or cyrus since our users getting angry not to mention my boss. -- Levente "Si vis pacem para bellum!"

3 7

[Dovecot] 0.99.10-test8
by Timo Sirainen 30 May '03

30 May '03

http://dovecot.procontrol.fi/test/ Again major maildir syncing updates: - uidlist file is accessed and rewritten a lot less often now than before - mail duplicates are detected and handled properly by renaming them to new base name - message flag updates and expunging before did two full syncs for cur/ directory. now it does only one. - some fixes to syncing in read-only / out-of-quota conditions - before we did always a full sync in cur/ directory when mailbox was opened. now it's done only when needed. - fixed some crash/index corruption cases I think syncing should be now very close to having perfect possible performance.

2 3

[Dovecot] new problems
by Farkas Levente 29 May '03

29 May '03

hi, so yesterday I move the whole mail system to a better machine. the only thing which is running on this system is dovect and: -------------------------------------------------- 10:44am up 6 days, 25 min, 3 users, load average: 28.03, 17.96, 9.05 233 processes: 231 sleeping, 2 running, 0 zombie, 0 stopped CPU0 states: 3.1% user, 29.4% system, 0.0% nice, 66.4% idle CPU1 states: 7.1% user, 63.2% system, 0.0% nice, 29.1% idle CPU2 states: 1.3% user, 3.1% system, 0.0% nice, 94.4% idle CPU3 states: 1.1% user, 7.4% system, 0.0% nice, 90.3% idle Mem: 1030496K av, 1021836K used, 8660K free, 0K shrd, 104064K buff Swap: 2040244K av, 55544K used, 1984700K free 776180K cached -------------------------------------------------- so the problem here is again with the load 28 (!!!)..... in the imap.log: -------------------------------------------------- imap(arvays): May 28 10:39:32 Error: Timeout while waiting for release of fcntl() lock for index file /home/arvays/Maildir/.INBOX/.imap.index imap(lfarkas): May 28 10:42:05 Panic: unreached dovecot: May 28 10:42:07 Error: child 19933 (imap) killed with signal 6 imap(ahegedus): May 28 11:05:57 Panic: file maildir-sync.c: line 472 (maildir_sync_uidlist): assertion failed: (ACTION(hash_rec) == MAILDIR_FILE_ACTION_NEW) dovecot: May 28 11:05:58 Error: child 29103 (imap) killed with signal 6 -------------------------------------------------- -- Levente "Si vis pacem para bellum!"

2 7

[Dovecot] still has error
by Farkas Levente 28 May '03

28 May '03

hi, after download the current cvs recompile, start I still has these errors: ------------------------------------- imap-login: May 28 13:49:02 Info: Login: jcsinalos [192.168.0.106] imap(jcsinalos): May 28 13:49:02 Panic: unreached dovecot: May 28 13:49:02 Error: child 31683 (imap) killed with signal 6 imap-login: May 28 13:49:03 Info: Login: jcsinalos [192.168.0.106] imap-login: May 28 13:49:03 Info: Login: jcsinalos [192.168.0.106] imap(jcsinalos): May 28 13:49:03 Panic: unreached dovecot: May 28 13:49:03 Error: child 31687 (imap) killed with signal 6 ------------------------------------- -- Levente "Si vis pacem para bellum!"

2 3

[Dovecot] 0.99.10-test7
by Timo Sirainen 28 May '03

28 May '03

- APPEND memory leak fixed - maildir syncing crash / some other errors fixed - pop3 mail fetching fixed - pop3 didn't advertise STLS in capabilities before http://dovecot.procontrol.fi/test/

1 0

[Dovecot] a few more error
by Farkas Levente 28 May '03

28 May '03

in the imap.log: imap(arvays): May 28 10:39:32 Error: Timeout while waiting for release of fcntl() lock for index file /home/arvays/Maildir/.INBOX/.imap.index imap(lfarkas): May 28 10:42:05 Panic: unreached dovecot: May 28 10:42:07 Error: child 19933 (imap) killed with signal 6 -- Levente "Si vis pacem para bellum!"

1 0

[Dovecot] serious problem
by Farkas Levente 28 May '03

28 May '03

hi, I've got dozen such errors: ---------------------------- imap-login: May 28 10:28:56 Info: Login: gpajlocz [192.168.1.182] imap(gpajlocz): May 28 10:28:56 Panic: file maildir-sync.c: line 472 (maildir_sync_uidlist): assertion failed: (ACTION(hash_rec) == MAILDIR_FILE_ACTION_NEW) dovecot: May 28 10:28:56 Error: child 17207 (imap) killed with signal 6 ---------------------------- and this users can't get into the system... -- Levente "Si vis pacem para bellum!"

1 0

[Dovecot] Dovecot 0.99.9.1 and openssl-0.9.7a-5
by Robin Whittle 28 May '03

28 May '03

Hi Timo and others, Thanks for Dovecot! I just got it running under Red Hat 9.0 after spending many hours unsuccessfully trying to get Courier IMAP to run, although I have done it in the past. Here is a compilation glitch which may already be well known: I compiled dovecot-0.99.9.1 on my newly installed and recently updated (via Red Hat Network) system and the compilation stopped due to a missing file in the SSL headers: In file included from /usr/include/openssl/ssl.h:179, from ssl-proxy-openssl.c:14: /usr/include/openssl/kssl.h:72:18: krb5.h: No such file or directory In file included from /usr/include/openssl/ssl.h:179, from ssl-proxy-openssl.c:14: The currently installed OpenSSL RPM was openssl-0.9.7a-5. This lacks the file /usr/include/openssl/krb5.h . I understand that openssl-0.9.7b is OK, but I wasn't sure about whether installing this as a tarball from http://www.openssl.org would upset any other programs on this machine, or confuse the RHN update system. I didn't really need SSL and I couldn't see a specific option for disabling it, other than a general instruction about disabling modules with a ./configure option. So I tried ./configure --help and compiled it with: ./configure --without-ssl This worked fine. I really like the report at the end of the ./configure stage saying how the program will be compiled! - Robin // Robin Whittle http://www.firstpr.com.au // Melbourne, Australia http://fondlyandfirmly.com

1 0

[Dovecot] Dovecot in OpenBSD ports system
by Andrew Basterfield 27 May '03

27 May '03

Hi I have put together dovecot port for the OpenBSD ports system. The port has yet to be submitted, but is finished awaiting testing from a wider audience. I have been using dovecot successfully on OpenBSD/sparc64 -current for months now with no problems. Would you recommend including the CR+LF patch? http://cemetery.homeunix.org/OpenBSD/dovecot.tar.gz -- http://cemetery.homeunix.org

2 6

RE: [Dovecot] Postgres "issue"
by Maikel Verheijen 27 May '03

27 May '03

Ok: a little lame to answer my own question, but I created a CRUDE patch. It does NOT check why a connection failed, it just does a PQreset, and it SEEMS to work. Kind regards, Maikel Verheijen. Ps: Timo, can something with reconnect be implemented permanently? --8<-- --- src/auth/db-pgsql.c.ORIG Tue May 27 10:06:39 2003 +++ src/auth/db-pgsql.c Tue May 27 11:16:38 2003 @@ -53,9 +53,16 @@ res = PQexec(conn->pg, query); if (PQresultStatus(res) != PGRES_TUPLES_OK) { - i_error("PGSQL: Query \"%s\" failed: %s", - query, PQresultErrorMessage(res)); - failed = TRUE; + PQreset(conn->pg); + res = PQexec(conn->pg, query); + if (PQresultStatus(res) != PGRES_TUPLES_OK) { + i_error("PGSQL: Query \"%s\" failed: %s", + query, PQresultErrorMessage(res)); + failed = TRUE; + } else { + i_error("PGSQL: Reconnected because of failure!"); + failed = FALSE; + } } else { failed = FALSE; } --8<-- -----Original Message----- From: Maikel Verheijen [mailto:maikel@ladot.com] Sent: Tuesday, May 27, 2003 9:43 AM To: 'Dovecot (E-mail)' Subject: [Dovecot] Postgres "issue" Dear list, I have a small issue with dovecot talking to a postgresql server: If my postgres server get restarted, dovecot fails to reconnect to the postgres server. I run dovecot 0.99.9.1 (which is actually a cvs version of dovecot, of may 9 2003) I have the same postgres version for the server as I use for the libraries. Is it hard to get auto-reconnect to work? Kind regards, Maikel Verheijen Ps: the log message I get is this: May 22 17:33:01 testlfw3 dovecot-auth: PGSQL: Query "SELECT password FROM aliases WHERE alias = 'maikel(a)test.com' AND password != ''" failed: FATAL 1: This connection has been terminated by the administrator. server closed the connection unexpectedly ^IThis probably means the server terminated abnormally ^Ibefore or while processing the request. Which probably describes it all :)

1 0

[Dovecot] still problem with load
by Farkas Levente 27 May '03

27 May '03

hi, we've got (and getting more) serious problem with load. I'm just calculate that ther is about 300 mailbox with 20Gb mails. and the whole system is _very_ slow and just getting slower and slower. it's a fast lan every client has 100Mb connection to the server with gigabit crad and gigabit switches. when I push the delete button in a mail I usualy have to wait 10,20 or 30 seconds (!!!) to deleted and show me the next one. dovecot eat so much io to the hard disk, that we can't do too much. currently at the same time about 100 clients are connected mostly with OE6. the server is a P4 server with 1GB ram and about 1TB hard disk. there is only one samba and dovecot on the server. and the load use to be something like this: ---------------------------------------- 10:47:38 up 3 days, 15:48, 2 users, load average: 4.64, 3.58, 3.43 230 processes: 225 sleeping, 5 running, 0 zombie, 0 stopped CPU states: 6.3% user 8.9% system 0.0% nice 0.0% iowait 84.6% idle Mem: 1022840k av, 1013588k used, 9252k free, 0k shrd, 80320k buff 826372k actv, 47324k in_d, 16904k in_c Swap: 4193608k av, 80612k used, 4112996k free 783088k cached ---------------------------------------- as you can see it use almost all ram (as the 2.4 kernmel used to do) but no cache. so the ram is enough. the more interesting part is the load while the idle usualy between 80-90% the whole system doesn't use any cpu (or just minimal). BUT at the same time the load is around 3,4,5 (!!!) which is too much, and more than acceptable. what's worse the reason is the io load on the hard disks. every process are waiting for io. in this case I usualy service dovecot stop killall imap <wait about one minutes> service dovecot start and the load goes back to 0.3-0.6. after an hour the same happend and I have to do the same.:-((( what's more in this case samba case that all (!!!) clients stops for a few seconds. since everybody use OE6 they always download all messages with huge mailboxes what's more dovecot index the whole system all the time. I assume this cause the load. IMHO 300 mailbox and 100 concurrent user is not such a big thing. is there any way to restrict dovecot not to use so much io? thanks in advance. -- Levente "Si vis pacem para bellum!"

3 8

[Dovecot] Postgres "issue"
by Maikel Verheijen 27 May '03

27 May '03

Dear list, I have a small issue with dovecot talking to a postgresql server: If my postgres server get restarted, dovecot fails to reconnect to the postgres server. I run dovecot 0.99.9.1 (which is actually a cvs version of dovecot, of may 9 2003) I have the same postgres version for the server as I use for the libraries. Is it hard to get auto-reconnect to work? Kind regards, Maikel Verheijen Ps: the log message I get is this: May 22 17:33:01 testlfw3 dovecot-auth: PGSQL: Query "SELECT password FROM aliases WHERE alias = 'maikel(a)test.com' AND password != ''" failed: FATAL 1: This connection has been terminated by the administrator. server closed the connection unexpectedly ^IThis probably means the server terminated abnormally ^Ibefore or while processing the request. Which probably describes it all :)

1 0

[Dovecot] pop3 timeout when sending first message
by Mike Brown 27 May '03

27 May '03

I'm using FreeBSD 4.8 with dovecot from the ports collection. First I am first trying to fetch mail via POP3. Clients are both OE6 and Mozilla. Both exhibit the same behavior: the client says it is receiving message 1 of (however many), but nothing happens; no message data is transferred. Mozilla seems to keep waiting forever, but OE6 times out after 60 seconds and lets me stop waiting. I tried both with and without SSL. Authentication works fine in either case, but the mail xfer just doesn't work. There's nothing of interest in the logs. By the way, there seems to be no mention of what syslog facility is used by dovecot. What is it? I'm avoiding syslog for now and writing to specific files. In the info log I get this when the client logs in: pop3-login: May 25 23:10:44 Info: Login: mike [my.IP.addr.here] In the other log I get this when OE6 disconnects, following the timeout and prompting me to wait or stop: pop3-login: May 25 23:11:53 Warning: SSL_read() syscall failed: EOF [216.241.45.45] I'm not sure what else to do to try to debug this... Help? -Mike

2 4

[Dovecot] Why dovecot is not multi-threaded?
by Ruben Alvarez 26 May '03

26 May '03

Hi, I'm looking for the most efficient OpenSource IMAP server and I am told that Dovecot Server is a good solution. Anyway, I have inspected the source code and I think Dovecot is not a multi-threaded server, but a forked server. I am surprised about this issue, because threads perfomance should be higher than creating a new process for each connection....I suppose. So, Could anybody tell me why Dovecot was not designed with multi-threaded support?. Perhaps, threads are not a good solution for Dovecot but I am very interested in which are the reasons for this. By the other hand, ¿do anybody know any multi-threaded OpenSource IMAP server?. I would like test performance of Dovecot server versus a multi-threaded one. Very thanks.

2 1

[Dovecot] logging in POP3
by Jens Laas 26 May '03

26 May '03

I have begun testing dovecot as (primarly) a POP replacement. So far the only lacking bit is the logging. It would be great if pop3 could log a line at client exit with the following info: (wishlist follows :) o nr deleted mails + total bytes deletes o nr mails left in spool + bytes left o time spent o indication if TLS was used or not If you would lika generic logging API I have one you can use: (Only tested under Linux. It is GPL) http://robur.slu.se/jensl/jellog.tar.gz Excerpt from headerfile: /* Functions for setting the destination of logger_facilities. - filename is the file to append log entries to. If file does not exist it is created with umask 0666 (modified as usual by open() call). - filestream is the FILE stream to use. - fd is the filedescriptor to use. - priority is the syslog priority to use as used in the syslog() call. - timestamp is used as a boolean. True means begin line with a timestamp. */ int logger_set_file(logger_facility facility, char *filename, int timestamp); int logger_set_iostream(logger_facility facility, FILE *filestream, int timestamp); int logger_set_fd(logger_facility facility, int fd, int timestamp); int logger_set_syslog(logger_facility facility, int priority, int timestamp); /* fmt = [sdt]+ s = string d = integer t = time-string Example: logger( LOGGER_ERROR, "sds", "Errorcode: ", -1234, ". Aborting!"); See end of logger.c for more examples. */ int logger(logger_facility facility, char *fmt, ...); Dovecot looks great! Just thought I'd send you this wishlist. If you could point me to the right places in the code I am willing to help adding this myself. Cheers, Jens Låås ----------------------------------------------------------------------- 'This mail automatically becomes portable when carried.' ----------------------------------------------------------------------- Jens Låås Email: jens.laas(a)data.slu.se Department of Computer Services, SLU Phone: +46 18 67 35 15 Vindbrovägen 1 P.O. Box 7079 S-750 07 Uppsala SWEDEN -----------------------------------------------------------------------

2 1

[Dovecot] possible dovecot problem (fwd)
by Mark E. Mallett 23 May '03

23 May '03

I'm just forwarding this verbatim from somebody who works here. Comments ? mm ----- Forwarded message from Dave Chamberlain <davec(a)mv.mv.com> ----- > Subject: possible dovecot problem > From: "Dave Chamberlain" <davec(a)mv.mv.com> > Date: Tue, 20 May 2003 21:29:48 -0400 (EDT) > To: mem(a)mv.mv.com (Mark E. Mallett) > > Ok, I'm kind of confused at what dovecot's imap implementation is doing. > > I seem to be spending more time than I need to correctly decipher the headers of > email messages. > > I have included here the text from 7.4.2 as it explains the response from a > fetch of an ENVELOPE. The last paragraph specifies that the FROM, SENDER > and REPLYTO fields cannot be nil because some of them must be present per > RFC822 and the IMAP spec will default values. I have many examples where > this is not the case, where the fetch of the envelope is returning NIL for > some of these values. > > In the example below, the message shows that the from, replyto and sender > are all set to jaentc(a)aukware.com (ok, a spelling error, but that was her > typing it in wrong). The next field after those three is NIL, that is the > TO line (more of my text after the IMAP conversation) > > a uid fetch 902 ENVELOPE > * 113 EXISTS > * 1 RECENT > * 104 FETCH (UID 902 ENVELOPE ("Tue, 20 May 2003 16:05:04 -0500" "From A Friend: > 'TheWMURChannel.com - News - Law Raises Age Children Must Be In Seat Restraints'" > (("Janet" NIL "jaentc" "aukware.com")) > (("Janet" NIL "jaentc" "aukware.com")) > (("Janet" NIL "jaentc" "aukware.com")) NIL NIL NIL NIL > "<200305202105.h4KL5xo20860(a)qbert.ibsys.com>")) > > Following is the complete header from the message. There is a valid To address > supplied, and it is in one of the allowed formats. I would have thought that > possibly it was the format that was causing the problem. I first theorized that > it didn't understand the emailaddress (personalname) format. However, the > From field is in that format, and was correctly picked up (notice that "Janet" > exists above as the Personal name, so it did understand that format). > > I have found multple cases where the FROM was NIL, the SUBJECT was NIL and > the TO is NIL, yet when looking at the header they are visible. > > This is causing problems with more than just my things, OE is having a problem > with it as well. > > > > > >From jaentc(a)aukware.com Tue May 20 21:26:43 2003 UTC > Received: (qmail 24772 invoked from network); 20 May 2003 17:52:17 -0400 > Received: from iridium.mv.net (HELO mv.mv.com) (qmailr(a)199.125.85.17) > by mercury.mv.net with SMTP; 20 May 2003 17:52:17 -0400 > X-Peer-Info: remote-ip 199.125.85.17 local-ip 199.125.85.40 > local-name mercury.mv.net > Received: (qmail 21564 invoked by uid 134); 20 May 2003 17:26:53 -0400 > Delivered-To: davec(a)mv.com > Received: (qmail 3533 invoked from network); 20 May 2003 17:06:26 -0400 > Received: from qbert.ibsys.com (66.187.197.24) > by iridium.mv.net with SMTP; 20 May 2003 17:06:26 -0400 > X-Peer-Info: remote-ip 66.187.197.24 local-ip 199.125.85.17 > local-name iridium.mv.net > Received: from 10.0.0.24 (cfusion3.ibsys.com [10.3.0.53]) > by qbert.ibsys.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id h4KL5xo20860 > for <davec(a)mv.com (Dave)> Tue, 20 May 2003 16:05:59 -0500 (CDT) > Message-Id: <200305202105.h4KL5xo20860(a)qbert.ibsys.com> > Content-type: text/plain > Date: Tue, 20 May 2003 16:05:04 -0500 > From: jaentc(a)aukware.com (Janet) > Subject: From A Friend: 'TheWMURChannel.com - News - Law Raises Age Children Must Be > In Seat Restraints' > To: davec(a)mv.com (Dave) > > > Section 7.4.2 > > ENVELOPE > A parenthesized list that describes the envelope structure of a > message. This is computed by the server by parsing the > [RFC-2822] header into the component parts, defaulting various > fields as necessary. > > The fields of the envelope structure are in the following > order: date, subject, from, sender, reply-to, to, cc, bcc, > in-reply-to, and message-id. The date, subject, in-reply-to, > and message-id fields are strings. The from, sender, reply-to, > to, cc, and bcc fields are parenthesized lists of address > structures. > > An address structure is a parenthesized list that describes an > electronic mail address. The fields of an address structure > are in the following order: personal name, [SMTP] > at-domain-list (source route), mailbox name, and host name. > > [RFC-2822] group syntax is indicated by a special form of > address structure in which the host name field is NIL. If the > mailbox name field is also NIL, this is an end of group marker > (semi-colon in RFC 822 syntax). If the mailbox name field is > non-NIL, this is a start of group marker, and the mailbox name > field holds the group name phrase. > > If the Date, Subject, In-Reply-To, and Message-ID header lines > are absent in the [RFC-2822] header, the corresponding member > of the envelope is NIL; if these header lines are present but > empty the corresponding member of the envelope is the empty > string. > > Note: some servers may return a NIL envelope member in the > "present but empty" case. Clients SHOULD treat NIL and > empty string as identical. > > Note: [RFC-2822] requires that all messages have a valid > Date header. Therefore, the date member in the envelope can > not be NIL or the empty string. > > Note: [RFC-2822] requires that the In-Reply-To and > Message-ID headers, if present, have non-empty content. > Therefore, the in-reply-to and message-id members in the > envelope can not be the empty string. > > If the From, To, cc, and bcc header lines are absent in the > [RFC-2822] header, or are present but empty, the corresponding > member of the envelope is NIL. > > If the Sender or Reply-To lines are absent in the [RFC-2822] > header, or are present but empty, the server sets the > corresponding member of the envelope to be the same value as > the from member (the client is not expected to know to do > this). > > Note: [RFC-2822] requires that all messages have a valid > From header. Therefore, the from, sender, and reply-to > members in the envelope can not be NIL. ----- End forwarded message -----

2 7

[Dovecot] Dovecot and SquirrelMail
by Ken Wilson 22 May '03

22 May '03

Hello, Does anyone know how to get dovecot working with squirrelmail v1.4? We have an existing uw-imap setup, with mail stored in ~/mail and inboxes in /var/spool/mail/user. I've tried setting $imap_server_type = other in squirrelmail, but I do not see any mail in my inbox. This is my setting in dovecot.conf default_mail_env = maildir:~/mail/:INBOX=/var/spool/mail/%n Any help would be grealty appreciated, as I want to leave uw-imap and get the speed increases that dovecot offers. Thanks Ken All e-mail from Wilberforce College is governed by our legal disclaimer which is available at http://webmail.wilberforce.ac.uk/disclaimer.txt

3 2

[Dovecot] ssl still not working
by Farkas Levente 21 May '03

21 May '03

hi, I'm just download the latest cvs and try to use imaps. in mozilla I've got the following message window: ----------------------------- mail.int.bppiac.hu received a message with incorrect Message Authentication Code. If the error occurs frequently, contact the website administrator. ----------------------------- and there is only one OK button:-) and this happens always. what can be the reason and what can I do? thanks. -- Levente "Si vis pacem para bellum!"

6 11

[Dovecot] SSL problems
by Timo Sirainen 21 May '03

21 May '03

Anyone with SSL problems, please try 0.99.10-test4 or included patch. If it fixes it, I'll make it faster by caching the generated keys. http://dovecot.procontrol.fi/test/

2 1

[Dovecot] dovecot with ssl on rhl9
by Elliot Peele 20 May '03

20 May '03

Has anyone gotten dovecot to work on Red Hat Linux 9 with ssl support? It seems to work just fine on Red Hat Linux 8.0, but doesn't seem to work Red Hat Linux 9. When I try to use openssl to connect to the server i get: [elliot@localhost elliot]$ openssl s_client -connect rktest.physics.ncsu.edu:993 CONNECTED(00000003) depth=0 /OU=IMAP server/CN=imap.example.com/emailAddress=postmaster@example.com verify error:num=18:self signed certificate verify return:1 depth=0 /OU=IMAP server/CN=imap.example.com/emailAddress=postmaster@example.com verify return:1 20949:error:140943FC:SSL routines:SSL3_READ_BYTES:sslv3 alert bad record mac:s3_pkt.c:1052:SSL alert number 20 20949:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:226: I'm trying to use evolution 1.3.3 to connect via imaps. Whenever I click on the mail folder it just says 'Scanning folders in "IMAP server imap.example.com" (100%)' and then nothing happens. Anyone have any ideas? Thanks Elliot

1 0

RE: [Dovecot] 0.99.10-test1
by Maikel Verheijen 19 May '03

19 May '03

> > Does this mean you made the .subscriptions nfs-safe already in this > > version? > Well, no, but that's not maildir-specific code :) Ah, ok, My mistake! :) Regards, Maikel.

1 0

[Dovecot] 0.99.10-test1
by Timo Sirainen 19 May '03

19 May '03

http://dovecot.procontrol.fi/test/ Maildir syncing now works pretty much as described in my earlier mail. It was quite a large change, so please test this :) So the new and great features: - It's faster. - If someone renames maildir file just before we try to use it, we now resync the maildir and try to find it again. Before we just failed. It's also possible that the filename changed again while we resynced, so we try max. 10 times before failing (yes, we know if we should try resyncing so we don't always scan it 10 times). - Read-only maildirs work now. If we don't have write access to dovecot-uidlist, we'll show only those mails which are already there. - Out of quota/disk space failures are handled well now. All except updating dovecot-uidlist file which is a bit tricky. - :CONTROL=dir in default_mail_env can specify where to save dovecot-uidlist and .customflags files. Useful for above problems. I think maildir support is getting near perfect now. Only thing left is to deal with failure to write dovecot-uidlist when out of quota. Oh, and NFS safe .customflags file.

2 1

RE: [Dovecot] 0.99.10-test1
by Maikel Verheijen 19 May '03

19 May '03

Hi Timo, > I think maildir support is getting near perfect now. Only > thing left is to deal with failure to write dovecot-uidlist > when out of quota. Oh, and NFS safe .customflags file. Does this mean you made the .subscriptions nfs-safe already in this version? Kind regards, Maikel Verheijen.

2 1

[Dovecot] Maildir synchronization
by Timo Sirainen 17 May '03

17 May '03

I thought I'd send this here too, since I spent so much time writing it as comment to maildir-sync.c :) Now only thing left to do is to write the code to match it. /* Here's a description of how we handle Maildir synchronization and it's problems: We want to be as efficient as we can. The most efficient way to check if changes have occured is to stat() the new/ and cur/ directories and uidlist file - if their mtimes hasn't changed, there's no changes and we don't need to do anything. Problem 1: Multiple changes can happen within a single second - nothing guarantees that once we synced it, someone else didn't just then make a modification. Such modifications wouldn't get noticed until a new modification occured later. Problem 2: Syncing cur/ directory is much more costly than syncing new/. Moving mails from new/ to cur/ will always change mtime of cur/ causing us to sync it as well. Problem 3: We may not be able to move mail from new/ to cur/ because we're out of quota, or simply because we're accessing a read-only mailbox. MAILDIR_SYNC_SECS ----------------- Several checks below use MAILDIR_SYNC_SECS, which should be maximum clock drift between all computers accessing the maildir (eg. via NFS), rounded up to next second. Our default is 1 second, since everyone should be using NTP. Note that setting it to 0 works only if there's only one computer accessing the maildir. It's practically impossible to make two clocks _exactly_ synchronized. cur directory ------------- We have maildir_cur_dirty variable which is set to cur/ directory's mtime when it's >= time() - MAILDIR_SYNC_SECS and we _think_ we have synchronized the directory. When maildir_cur_dirty is non-zero, we don't synchronize the cur/ directory until a) cur/'s mtime changes b) opening a mail fails with ENOENT c) time() > maildir_cur_dirty + MAILDIR_SYNC_SECS This allows us to modify the maildir multiple times without having to sync it at every change. The sync will eventually be done to make sure we didn't miss any external changes. The maildir_cur_dirty is set when: - we change message flags - we expunge messages - we move mail from new/ to cur/ - we sync cur/ directory and it's mtime is >= time() - MAILDIR_SYNC_SECS It's unset when we do the final syncing, ie. when mtime is older than time() - MAILDIR_SYNC_SECS. new directory ------------- If new/'s mtime is >= time() - MAILDIR_SYNC_SECS, always synchronize it. maildir_cur_dirty-like feature might save us a few syncs, but that might break a client which saves a mail in one connection and tries to fetch it in another one. new/ directory is almost always empty, so syncing it should be very fast anyway. Normally we move all mails from new/ to cur/ whenever we sync it. If it's not possible for some reason, we set maildir_have_new flag on which instructs synchronization to check files in new/ directory as well. maildir_keep_new flag is also set which instructs syncing to not even try to move mails to cur/ anymore. If client tries to change a flag for message in new/, we try to rename() it into cur/. If it's successful, we clear the maildir_keep_new flag so at next sync we'll try to move all of them to cur/. When all of them have been moved, maildir_have_new flag is cleared as well. Expunges will also clear maildir_keep_new flag. If rename() still fails because of ENOSPC or EDQUOT, we still save the flag changes in index with dirty-flag on. When moving the mail to cur/ directory, or when we notice it's already moved there, we apply the flag changes to the filename, rename it and remove the dirty flag. If there's dirty flags, this should be tried every time after expunge or when closing the mailbox. broken clients -------------- Originally the middle identifier in Maildir filename was specified only as <process id>_<delivery counter>. That however created a problem with randomized PIDs which made it possible that the same PID was reused within one second. So if within one second a mail was delivered, MUA moved it to cur/ and another mail was delivered by a new process using same PID as the first one, we likely ended up overwriting the first mail when the second mail was moved over it. Nowadays everyone should be giving a bit more specific identifier, for example include microseconds in it which Dovecot does. There's a simple way to prevent this from happening in some cases: Don't move the mail from new/ to cur/ if it's mtime is >= time() - MAILDIR_SYNC_SECS. The second delivery's link() call then fails because the file is already in new/, and it will then use a different filename. There's a few problems with this however: - it requires extra stat() call which is unneeded extra I/O - another MUA might still move the mail to cur/ - if first file's flags are modified by either Dovecot or another MUA, it's moved to cur/ (you _could_ just do the dirty-flagging but that'd be ugly) Because this is useful only for very few people and it requires extra I/O, I decided not to implement this. It should be however quite easy to do since we need to be able to deal with files in new/ in any case. It's also possible to never accidentally overwrite a mail by using link() + unlink() rather than rename(). This however isn't very good idea as it introduces potential race conditions when multiple clients are accessing the mailbox: Trying to move the same mail from new/ to cur/ at the same time: a) Client 1 uses slightly different filename than client 2, for example one sets read-flag on but the other doesn't. You have the same mail duplicated now. b) Client 3 sees the mail between Client 1's and 2's link() calls and changes it's flag. You have the same mail duplicated now. And it gets worse when they're unlink()ing in cur/ directory: c) Client 1 changes mails's flag and client 2 changes it back between 1's link() and unlink(). The mail is now expunged. d) If you try to deal with the duplicates by unlink()ing another one of them, you might end up unlinking both of them. So, what should we do then if we notice a duplicate? First of all, it might not be a duplicate at all, readdir() might have just returned it twice because it was just renamed. What we should do is create a completely new base name for it and rename() it to that. If the call fails with ENOENT, it only means that it wasn't a duplicate after all. */

1 0

[Dovecot] Postfix locking equivalence?
by Warren Togami 17 May '03

17 May '03

/etc/postfix/main.cf.default: mailbox_delivery_lock = flock, dotlock Is flock equivalent to dovecot's fnctl locking? For mbox what type of locking settings should I be using? (No NFS, only local filesystem.) I'm using procmail to deliver mail to my mboxes. Does the above postfix setting effect procmail's locking method? I use rules like this: :0 * ^X-BeenThere: dovecot(a)procontrol.fi DOVECOT If I understand this correctly, :0: in procmailrc would explicitly use dotlocks instead of "kernel-locks" as procmail calls it. I'm not fully understanding all this locking stuff. Warren Togami warren(a)togami.com p.s. Timo, I received your test message after my prior posting attempt bounced. I had this error message: Reporting-MTA: dns; danu.procontrol.fi Arrival-Date: Sat, 17 May 2003 12:52:08 +0300 (EEST) Final-Recipient: rfc822; dovecot(a)procontrol.fi Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; mail forwarding loop for dovecot(a)procontrol.fi

2 1

[Dovecot] test
by Timo Sirainen 17 May '03

17 May '03

..is this thing working.. I messed up a bit when adding spamassassin to postfix filter.

1 0

[Dovecot] Postfix locking equivalence?
by Warren Togami 17 May '03

17 May '03

/etc/postfix/main.cf.default: mailbox_delivery_lock = flock, dotlock Is flock equivalent to dovecot's fnctl locking? For mbox what type of locking settings should I be using? (No NFS, only local filesystem.) Warren Togami warren(a)togami.com

1 0

[Fwd: Re: [Dovecot] help: The current command did not succeed. The mail server responded: Invalid mask.]
by Timo Sirainen 16 May '03

16 May '03

Just FYI, I guess this message was meant here :)

1 0

[Dovecot] rawlog fails
by Mark E. Mallett 16 May '03

16 May '03

You mentioned --with-rawlog earlier, so I tried it. It fails with a select error. I believe it's because in some cases the timeval struct is not initialized in io_loop_get_wait_time (e.g. see sample diff below). -mm- diff -c src/lib/ioloop.c.orig src/lib/ioloop.c *** src/lib/ioloop.c.orig Sat Apr 12 11:00:10 2003 --- src/lib/ioloop.c Thu May 15 22:10:12 2003 *************** *** 223,230 **** --- 223,238 ---- int io_loop_get_wait_time(struct timeout *timeout, struct timeval *tv, struct timeval *tv_now) { + #if 0 /* mem 20030515 make sure tv contains valid data here */ if (timeout == NULL) return INT_MAX; + #else + if (timeout == NULL) { + tv->tv_sec = INT_MAX / 1000; + tv->tv_usec = 0; + return INT_MAX; + } + #endif if (tv_now == NULL) { if (gettimeofday(tv, NULL) < 0)

2 1

[Dovecot] help: The current command did not succeed. The mail server responded: Invalid mask.
by Brandon Hoult 15 May '03

15 May '03

Am tryin to move from uw-imapd to dovecot, using dovecot ver 0.99.9.1-1 on debian. Using Mozilla Mail v 1.3 currently using mbox format. I made some test accounts and they seem to be working fine, but my older existing accounts give error messages whenever I connect or subscribe to mailboxes within them. The message that appears on the client is: "The current command did not succeed. The mail server responded: Invalid mask." it appears three times in an alert box (on windows) then everything seems to work. There are no messages in any of the mail logs in /var/log which would indicate a problem. The test accounts I created don't have this problem so I tried renameing the home directory, deleting the user, then recreating the user. However even with a new homedir the problem remains unchanged. I have verified that the permissions in ~/mail and /var/mail are set identically for working and non-working users. Thanks in advance for any advice, Brandon Hoult dolt(a)lmistudios.homeip.net

2 1

[Dovecot] Creating and renaming mbox folders on NFS auto-installed partitions
by Robert Evans 14 May '03

14 May '03

I'm trying dovecot-0.99.9.1 in place of uw-imap which ground to a halt on a 500MHz SunBlade 100 Solaris 8 system which acts as our Departmental mail server. INBOXes are mbox files on the servers's local SCSI disk. But user directories are auto mounted from other Sun NFS servers and these may contain other mbox mailboxes in a ~/Mail directory. There's a problem with creating (and with renaming) mailboxes in the NFS mounted ~/Mail directory. For an arbitrary mailbox "newbox", say, dovecot tries to create the parent directory path /home/username/Mail before creating the newbox file. But /home/username is automounted and so creating directory /home or /home/username fails with errno 89 ENOSYS - unsupported file system operation. The solution is to check for the existence of the directory before trying to create it. This will work since /home and /home/username will always exist for any valid user. I've amended mbox-storage.c in src/lib-storage/index/mbox to call "access" to do this.... *** src/lib-storage/index/mbox/mbox-storage.c.orig Tue Apr 15 14:04:02 2003 --- src/lib-storage/index/mbox/mbox-storage.c Wed May 14 16:04:39 2003 *************** *** 38,44 **** p++; } ! if (mkdir(dir, CREATE_MODE) < 0 && errno != EEXIST) { t_pop(); return -1; } --- 38,44 ---- p++; } ! if ( (access(dir,F_OK) != 0) && mkdir(dir, CREATE_MODE) < 0 && errno != EEXIST) { t_pop(); return -1; } - - - (Could also remove the && errno == EEXIST part - it's redundant when access(dir,F_OK) is checking for existence). Robert -- Robert.Evans(a)cs.cf.ac.uk Tel:+44(0)29 2087 5518 Fax:+44(0)29 2087 4598 http://www.cs.cf.ac.uk/department/staff/Robert.Evans.shtml Computer Science, Cardiff University, PO Box 916, Cardiff, CF24 3XF, UK

2 1

Re: [dovecot] Re: List-id test
by Moe Wibble 13 May '03

13 May '03

On Mon, May 12, 2003 at 06:44:06AM +0300, Timo Sirainen wrote: > On Mon, 2003-05-12 at 04:21, Timo Sirainen wrote: > > Just enabled List-* headers, testing if this still works.. > > Hmm. Wondered about why List-Id header used wrong host name and started > looking at Ecartis' sources .. Wasn't it written in Perl? I had believed > so for quite a long time for some reason. So since it's C, I figured I'd > audit the code for security flaws. > > .. I think I'll switch switch the list manager. Mailman looks nice. tried ezmlm? :)

2 2

Re: [dovecot] Re: Design thought - Retention of reworked mbox files
by Tim Hunt 13 May '03

13 May '03

It's primarily for debugging, and I don't see it being used in a high volume environment. What triggered the thought is that I suspect I may have lost the bodies of a couple of messages during an expunge, but because I don't have the previous state of the mbox file, I have no way of verifying my concern, and certainly no way to try and recreate it. And yes, I'm using mbox files, because I have many years of mail stored in them, and I'm not quite ready to convert them to another format. Tim On Mon, 2003-05-12 at 11:01, Charlie Brady wrote: > On 12 May 2003, Timo Sirainen wrote: > > > On Mon, 2003-05-12 at 02:05, Tim Hunt wrote: > > > Would it be possible to keep a backup copy of an mbox mail file any time it > > > needs to be substantionally rebuilt - for an example before an expunge. This > > > behaviour could be controlled by the config file, since it would most likely > > > only be used in development and testing environments. > > > > If it's only for debugging, I guess I could then just save a copy of it. > > Presumably the other reason you'd want it would be for mailbox integrity. > But if you are concerned about that, you'd be using maildir, wouldn't you? > > -- > Charlie

1 0

[dovecot] quota
by Sebastian Pachuta 07 May '03

07 May '03

first, thx for --with-storages=maildir second, there is a problem when user exceed their quota < status INBOX (messages) > NO Internal error [2003-05-06 15:35:56] in logfile: imap(user): Can't create directory /var/mail/user/.INBOX: Disk quota exceeded 'user' is not able to get list of messages and delete some of them :( third, in logfile: imap(user2): maildir flags update: rename(/var/mail/user2/cur/1049405360.18375_0.asd, /var/mail/user2/cur/1049405360.18375_0.asd:2,T) failed: Disk quota exceeded is there any way to rename files when quota exceed?

3 2

[dovecot] dovecot.spec
by Farkas Levente 07 May '03

07 May '03

hi, I'm just recoginze that dovecot contains an rpm spec file. unfortunately it's not too useful since an rpm -ta dovecot-.x.y.tar.gz can't be used since just the dovecot.spec.in is in the tarbar and not the actual spec file (which is in this from not useful in the above form). anyway here is my patch to the spec.in. -- Levente "Si vis pacem para bellum!" --- dovecot/dovecot.spec.in.lfarkas 2003-05-05 16:36:16.000000000 +0200 +++ dovecot/dovecot.spec.in 2003-05-05 17:04:30.000000000 +0200 @@ -1,9 +1,11 @@ # DarContact: Timo Sirainen <tss(a)iki.fi> +%define uid 96 +%define gid 96 Summary: Dovecot secure IMAP server. Name: dovecot Version: @VERSION@ -Release: 0 +Release: 1 License: GPL Group: System Environment/Daemons URL: http://dovecot.procontrol.fi/ @@ -16,14 +18,12 @@ Prefix: %{_prefix} Prereq: /usr/sbin/useradd, /usr/sbin/usermod -BuildRequires: openssl-devel %{!?rh62:, pam-devel} %{?rh62: pam} +BuildRequires: openssl-devel %{!?rh62:, pam-devel} %{?rh62: pam} gettext %description Dovecot is an IMAP server for Linux/UNIX-like systems, written with security primarily in mind. Although it's written with C, it uses -several coding techniques to avoid most of the common pitfalls. Next -release will also contain a small POP3 server. - +several coding techniques to avoid most of the common pitfalls. Dovecot can work with standard mbox and maildir formats and it's fully compatible with UW-IMAP and Courier IMAP servers as well as mail clients accessing the mailboxes directly. @@ -36,7 +36,7 @@ # # Init file for Dovecot IMAP daemon # -# chkconfig: - 54 46 +# chkconfig: 345 54 46 # description: Dovecot IMAP Daemon # # processname: dovecot @@ -101,8 +101,17 @@ exit \$RETVAL EOF +%{__cat} <<EOF >dovecot.pam +#%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 +EOF + %build -export CPPFLAGS="-I/usr/kerberos/include" +export CPPFLAGS="`pkg-config --cflags-only-I openssl`" +export LDFLAGS="`pkg-config --libs-only-L openssl`" %configure \ --with-ssl="openssl" \ --with-ssldir="%{_sysconfdir}/ssl" @@ -112,27 +121,32 @@ %{__rm} -rf %{buildroot} %makeinstall %{__install} -d -m0755 %{buildroot}%{_initrddir} -%{__install} -m0755 dovecot.sysv %{buildroot}%{_initrddir}/dovecot +%{__install} -m0755 dovecot.sysv %{buildroot}%{_initrddir}/%{name} +%{__install} -m644 dovecot.pam %{buildroot}%{_sysconfdir}/pam.d/imap +%{__install} -m644 dovecot.pam %{buildroot}%{_sysconfdir}/pam.d/imaps +%{__install} -m644 dovecot.pam %{buildroot}%{_sysconfdir}/pam.d/pop3 +%{__install} -m644 dovecot.pam %{buildroot}%{_sysconfdir}/pam.d/pop3s %{__mv} -f %{buildroot}%{_sysconfdir}/dovecot-example.conf %{buildroot}%{_sysconfdir}/dovecot.conf ### Clean up buildroot -%{__rm} -rf %{buildroot}%{_datadir}/doc/dovecot/ +%{__rm} -rf %{buildroot}%{_datadir}/doc/%{name}/ %pre -/usr/sbin/useradd -M -s /sbin/nologin -r dovecot &>/dev/null || : -/usr/sbin/usermod -s /sbin/nologin dovecot &>/dev/null || : +# Add the dovecot user and group if not found +/usr/sbin/groupadd -g %{gid} -r %{name} &>/dev/null || : +/usr/sbin/useradd -d /var/run/%{name} -s /bin/false -g %{name} -M -r -u %{uid} %{name} &>/dev/null || : %post /sbin/chkconfig --add dovecot %preun if [ $1 -eq 0 ]; then - /sbin/service dovecot stop &>/dev/null || : + /sbin/service %{name} stop &>/dev/null || : /sbin/chkconfig --del dovecot fi %postun -/sbin/service dovecot condrestart &>/dev/null || : +/sbin/service %{name} condrestart &>/dev/null || : %clean %{__rm} -rf %{buildroot} @@ -142,11 +156,16 @@ %doc AUTHORS ChangeLog COPYING* NEWS README TODO %doc doc/*.conf doc/*.sh doc/*.txt %config %{_sysconfdir}/dovecot.conf -%config %{_initrddir}/dovecot +%config %{_initrddir}/%{name} +%config %{_sysconfdir}/pam.d/* %{_sbindir}/* -%{_libexecdir}/dovecot/ +%dir %{_libexecdir}/%{name} +%{_libexecdir}/%{name}/ %changelog +* Mon May 5 2003 Levente Farkas <lfarkas(a)lfarkas.org> +- update a few things in the spec file + * Tue Apr 29 2003 Dag Wieers <dag(a)wieers.com> - 0.99.9-0 - Updated to release 0.99.9.

2 2

[dovecot] KMail?
by Joakim Ryden 07 May '03

07 May '03

Hey everyone - is anyone else having problems with Dovecot and KMail? I'm having trouble seeing my INBOX using KMail (Maildir format on the server), though all subfolders show up as normal. I suspect the problem is with KMail as all the other mail clients I've tested seem to have no such problems, they see INBOX *and* subfolders just fine, just wanted to see if anyone could confirm this behaviour? --Jo

2 1

[dovecot] dovecot and squirrelmail
by Warren Togami 07 May '03

07 May '03

Is anyone using squirrelmail with dovecot? After a few minor tweaks squirrelmail seems to work great, but I can't seem to get rid of the "./" folder. SquirrelMail implements some workaround hacks for specific IMAP server quirks. The default setting is: $imap_server_type = 'uw'; What settings do you folks use? Thanks, Warren Togami warren(a)togami.com

2 1

[dovecot] 0.99.9.1 - Runaway imap-login process
by Warren Togami 07 May '03

07 May '03

PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 32116 dovecot 19 0 1464 1464 1212 R 99.9 0.1 60:58 0 imap-login service dovecot stop ps -ef |grep imap-login |grep -v grep dovecot 32116 1 98 01:27 ? 01:01:33 imap-login /etc/dovecot.conf: auth_userdb = passwd uth_passdb = pam I think this was triggered while I attempted to login to IMAP with the this dovecot configuration without adding an "imap" entry to /etc/pam.d/ (auth fails). When I attempt to strace -p this runaway process, it strangely displays nothing. kill was able to get rid of it. After I added an appropriate /etc/pam.d/imap entry, auth works and I didn't see this runaway process. This is a RH9 chroot server instance running within Linux virtual server with security contexts kernel. (Think of it as a theoretically unbreakable chroot.) Any tips on what I can do to get some debugging information out of this? Thanks, Warren Togami warren(a)togami.com

2 1

[dovecot] Re: 0.99.9.1 OpenBSD and mbox
by Alvaro Munoz-Aycuens Mtnz. 07 May '03

07 May '03

Hi all, Now it works, these are the parameters I touched, the rest remains pretty the same as the example conf: #default_mail_env =mbox:~/mail/:INBOX=/var/mail/%u #mailbox_check_interval = 1 #mbox_locks = fcntl Anyway seems that HUP doesn't fully gets dovecot to reread conf file and restart, better to use SIGUSR1?, by the way how I disable dotlocking in case I want to try. Regards Alvaro Timo Sirainen wrote: > > Right. You'd have to either disable dotlocking or make /var/mail > world-writable and sticky. Currently there's no other ways around this. > >

2 1

[dovecot] 0.99.9.1
by Timo Sirainen 05 May '03

05 May '03

Some bugfixes: v0.99.9.1 2003-05-03 Timo Sirainen <tss(a)iki.fi> - Messages having lines longer than 8192 bytes caused problems. - There was some problems when opening a mbox first time that had been empty for a while. - Didn't compile with OpenBSD. - POP3 server crashed sometimes instead of printing error message. - If cached IMAP envelope contained literals, SEARCHing in it wrote errors to log file. For example if subject contained highascii, '"' or '\' characters this happened.

3 2

[dovecot] 0.99.9 released
by Timo Sirainen 05 May '03

05 May '03

As promised yesterday :) BTW. I just found libsqlora8 library yesterday and I've been playing with Oracle mail storage support. Shouldn't take too long to get it working. And the NEWS file once more: v0.99.9 2003-04-28 Timo Sirainen <tss(a)iki.fi> * WARNING: mbox rewriting works now faster, but it's less likely to notice external message flag changes (it wasn't perfect before either). This also means that if you're not using index files, Dovecot may not notice changes made by another Dovecot process. This will be fixed later. + Message UIDs are now permanently stored outside index files. Deleting indexes is now possible without any kind of data loss and in-memory indexes are now usable. + mbox rewriting leaves extra space into X-Keywords header. It's shrinked or grown when updating message flag headers to avoid rewriting the rest of the file. + imap-login and pop3-login can now be started from inetd. Privilege separation is still used, so it executes dovecot and dovecot-auth processes which are left on the background. + PostgreSQL authentication support, patch by Alex Howansky - Large multiline headers (over 8kB) broke Dovecot before. Now they're parsed one line at a time and we try to avoid reading them fully into memory. - SEARCH OR was broken - Partial BODY[] fetches were broken - Timezones were still set wrong when parsing dates - Using non-synchronized literals (LITERAL+) broke APPEND - Renaming maildir subfolders inserted extra "." in the middle. - Subfolders were a bit broken with maildir - Invalid PLAIN auth request crashed auth process.

2 3

[dovecot] 0.99.9.1 OpenBSD and mbox
by Alvaro Munoz-Aycuens Mtnz. 04 May '03

04 May '03

Hi, compiled perfectly, so the patch of course work ;), but seems that I had the conf a bit broken, because he doesn't read the new messages in /var/mail/user, does the line: #default_mail_env = mbox:~/Mail:INBOX=/var/mail/username look good?, I also tryed with %h instead of username, the rest of the conf is pretty standard, I can create folders and so on. Regards Alvaro

3 3

[dovecot] Problems fetching messages.
by Ian Kumlien 03 May '03

03 May '03

Hi, I have problems reading some mail with the latest version of dovecot. I use maildir etc but it all worked before... It seems like dovecot sends something that throws Evolution off the track since the actual information is sent, but in a broken form it seems. I also get some odd chars (this is raw tcp packet decoding): "ïêa-è "ïêc-è* FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 609 EXISTS * 0 RECENT * OK [UIDVALIDITY 1049995962] UIDs valid * OK [UIDNEXT 1044] Predicted next UID A10891 OK [READ-WRITE] Select completed. "ïêc-î "ïêc-î* 609 FETCH (UID 1043) A10892 OK Fetch completed. "ïêg-î* 498 FETCH (UID 646 BODY[] {3434} eturn-Path: <-----email-------> etc... Any clues? -- Ian Kumlien <pomac(a)vapor.com>

2 1

[dovecot] Corrupted index
by Mark E. Mallett 03 May '03

03 May '03

Hi- Still getting a bunch of these: Apr 30 13:45:23 mercury mem[11056]: pop3(user1): Corrupted index file /users/78/user1/Maildir/.INBOX/.imap.index: used_file_size larger than real file size (4032 vs 1608) and the occasional: Apr 30 13:08:53 mercury mem[13507]: pop3(user2): Corrupted index file (in-memory index for /users/e0/user2/Maildir): Filename mismatch for UID 1: 1051720748.28556.mercury.mv.net vs 1051715695.29601.mercury.mv.net Most of the time (but not always) the .imap* files are relatively old and apparently created by the test5 or older recent release. The errors persist in the logs until I manually remove the .imap* files, which are subsequently recreated upon the next access (without the error being logged, at least not right away). I had the impression that a "Corrupted index file" would cause the index files not to be used, and in fact recreated. Apparently not? If there is an error that causes the .imap* files to be ignored, shouldn't those files be removed? mm

2 1

[dovecot] Message causing pop3 crash
by Mark E. Mallett 03 May '03

03 May '03

Hi- Found a message that will generate a pop3 coredump when using mbox format. It seems to do with the fact that it has a mime part with a line that's 10,000 bytes long. However, that doesn't seem to be the only factor. Adjusting the size of the mail header seems to cause different kinds of crashes. I'll avoid attaching the message here but I've put it at http://www.mv.com/users/mem/x/badmail Reproducing it here on a BSD/OS system involves something like: (login to a virgin account or one you don't care about) % wget http://www.mv.com/users/mem/x/badmail % rm -rf .imap % MAIL=mbox:`pwd`/badmail % limit coredump 10m % /usr/local/libexec/dovecot/pop3 quit at which point you should get some errors and/or a coredump. You may need to do it twice (i.e. let it create the .imap/ index structure first). If you can't make it happen I can send along more info. -mm- (and yes, this was a real mail message, albeit a spam, except that I simplified it some and replaced all of the content with "x" characters)

2 1

[dovecot] Debian packages for 0.99.9
by Jaldhar H. Vyas 30 Apr '03

30 Apr '03

I uploaded the new version to sid today. Apart from the new version a big change is that it has now been split into 4 pieces. dovecot-imapd and dovecot-pop3d are the imap server and the pop3 server rspectively. They are seperate so you can install one without the other. dovecot-common contains the files they both use. dovecot is just a dummy to ensure smooth upgrades for users of older versions. As there are new packages, they will take a while to show up i the archive so I'm temporarily making them available from http://src.braincells.com/debian/sid/dovecot/ or deb http://src.braincells.com/debian sid/ deb-src http://src.braincells.com/debian sid/ via apt-get. but unless you have a burning need to upgrade, I recommend you just wait a few days. A backport to woody is also available, add deb http://src.braincells.com/debian woody/ deb-src http://src.braincells.com/debian woody/ to your sources.list. One problem I found with installing on woody is that the first time you do apt-get install dovecot, it gives you an error because /etc/dovecot.conf is no owned by dovect-common instead of dovecot. It will work correctly the second time you run the command. -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

1 0

[dovecot] Dovecot RH RPM packages
by Dag Wieers 29 Apr '03

29 Apr '03

Hi, I can't remember if I already told you, but I'm building RPM packages of dovecot for RH73, RH80 and RH9. You can find these at: http://dag.wieers.com/packages/dovecot/ Or use apt as described on: http://dag.wieers.com/apt/ I also added a sysv file to the SPEC-file for use with Red Hat. If you add this SPEC-file to your tarball (probably with some custom changes) everyone can build an RPM package by issuing: rpmbuild -ta <tarball> Kind regards, -- dag wieers, dag(a)wieers.com, http://dag.wieers.com/ -- �Any errors in spelling, tact or fact are transmission errors�

1 0

[dovecot] current cvs (04.28)
by Farkas Levente 28 Apr '03

28 Apr '03

hi, after the current cvs compile: ----------------------- gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src/lib -I../../src/lib-mail -I../../src/lib-imap -I../../src/lib-storage -O2 -g -pipe -march=i386 -mcpu=i686 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -c `test -f 'mail-storage-callbacks.c' || echo './'`mail-storage-callbacks.c source='main.c' object='main.o' libtool=no \ depfile='.deps/main.Po' tmpdepfile='.deps/main.TPo' \ depmode=gcc3 /bin/sh ../../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src/lib -I../../src/lib-mail -I../../src/lib-imap -I../../src/lib-storage -O2 -g -pipe -march=i386 -mcpu=i686 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -c `test -f 'main.c' || echo './'`main.c make[3]: *** No rule to make target `../lib-index/libstorage_index.a', needed by `pop3'. Stop. ----------------------- -- Levente "Si vis pacem para bellum!"

1 0

[dovecot] 0.99.9 release candidate 1
by Timo Sirainen 28 Apr '03

28 Apr '03

0.99.9 should really be released soon. There's been quite a lot of important fixes since 0.99.8.1. There's still some recent counter strangeness, but it wasn't perfect before either. mbox still doesn't necessarily notice flag changes unless they're written into index file (ie. non-Dovecots and Dovecot without index files). But it wasn't perfect before either. dovecot-uidlist file works perfectly now as far as I know. I just noticed that mbox syncing has been somewhat broken for past month. It sometimes assigned new UIDs to messages without any reason, so it was mostly just slowdown. So unless there's something really broken, I'll release 0.99.9 tomorrow. Please get 0.99.9-rc1 from http://dovecot.procontrol.fi/rc/ and see if you can break it. NEWS file: v0.99.9 2003-04-28 Timo Sirainen <tss(a)iki.fi> * WARNING: mbox rewriting works now faster, but it's less likely to notice external message flag changes (it wasn't perfect before either). This also means that if you're not using index files, Dovecot may not notice changes made by another process. This will be fixed later. + Message UIDs are now permanently stored outside index files. Deleting indexes is now possible without any kind of data loss and in-memory indexes are now usable. + mbox rewriting leaves extra space into X-Keywords header. It's shrinked or grown when updating message flag headers to avoid rewriting the rest of the file. + imap-login and pop3-login can now be started from inetd. Privilege separation is still used, so it executes dovecot and dovecot-auth processes which are left on the background. + PostgreSQL authentication support, patch by Alex Howansky - Large multiline headers (over 8kB) broke Dovecot before. Now they're parsed one line at a time and we try to avoid reading them fully into memory. - SEARCH OR was broken - Partial BODY[] fetches were broken - Timezones were still set wrong when parsing dates - Using non-synchronized literals (LITERAL+) broke APPEND - Renaming maildir subfolders inserted extra "." in the middle. - Subfolders were a bit broken with maildir - Invalid PLAIN auth request crashed auth process.

3 4

[dovecot] shared folders?
by Moe Wibble 27 Apr '03

27 Apr '03

Any plans to implement shared folders anytime soon? greetinx -- MW

5 16

[dovecot] dovecot and grsecurity (problem with resource limits)
by Heiko Zuerker 27 Apr '03

27 Apr '03

Howdy folks ! I just added Dovecot as a standard package to Devil-Linux and ran into a problem with resource limits. Grsecurity (http://www.grsecurity.net) is used in DL to prevent problems with common exploits, it also reports violations of rlimits. The following messages show up in the log, but it seems that the IMAP Server works fine: Apr 26 19:20:04 src@gate imap-login: Login: hz [192.168.0.11] Apr 26 19:20:05 src@gate kernel: grsec: attempted resource overstep by requesting 37 for RLIMIT_NPROC against limit 0 by (dovecot:10246) UID(0) EUID(0), parent (dovecot:634) UID(0) EUID(0) Apr 26 19:22:18 src@gate kernel: grsec: attempted resource overstep by requesting 37 for RLIMIT_NPROC against limit 0 by (dovecot:19802) UID(0) EUID(0), parent (dovecot:634) UID(0) EUID(0) Apr 26 19:22:18 src@gate imap-login: Login: hz [192.168.0.11] Apr 26 19:26:36 src@gate syslog-ng[606]: STATS: dropped 0 Apr 26 19:28:19 src@gate kernel: grsec: attempted resource overstep by requesting 33 for RLIMIT_NPROC against limit 0 by (dovecot:16011) UID(0) EUID(0), parent (dovecot:634) UID(0) EUID(0) How should we proceed to analyze/fix this problem? Thanks! Heiko

2 1

[dovecot] today cvs
by Farkas Levente 25 Apr '03

25 Apr '03

hi, the today cvs has a new bug during configure (both on rh 8.0 and rh 9): ----------------------------------- checking size of long long... 8 checking type of off_t... long long ./configure: line 12009: syntax error near unexpected token `else' ./configure: line 12009: `else' ----------------------------------- -- Levente "Si vis pacem para bellum!"

3 3

[dovecot] Using on AIX
by Adam Lackorzynski 25 Apr '03

25 Apr '03

Hi, I'm trying to install dovecot-0.99.9-test6 with gcc-3.2.2 under AIX (4.3.3) and found some problems. First, I need to define _XOPEN_SOURCE_EXTENDED to 1 in src/lib/fdpass.c and src/auth/mycrypt.c or undefine it to compile successfully. When I define _XOPEN_SOURCE_EXTENDED to 1, I get the following error while connecting: dovecot: Apr 21 17:56:44 Info: Dovecot starting up imap-login: Apr 21 17:57:19 Fatal: fd_send(5) failed: Bad file number dovecot: Apr 21 17:57:19 Error: child 39504 (login) returned error 89 This happens after a successful authentication (i.e. wrong authentications are correctly denied). Something similar happens if I define _XOPEN_SOURCE to 500 in both files. When I undefine the _XOPEN_SOURCE_EXTENDEDs without modifying the original _XOPEN_SOURCE defines, it seems to come further: imap-login: Apr 21 18:24:23 Info: Login: xxx [xxx.xxx.xxx.xxx] imap(xxx): Apr 21 18:24:23 Panic: file mail-index-data.c: line 439 (mail_index_data_append): assertion failed: ((size & (MEM_ALIGN_SIZE-1)) == 0) dovecot: Apr 21 18:24:23 Error: child 95800 (imap) killed with signal 6 but this doesn't work either. Anything other I could try? Thanks, Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

2 17

[dovecot] index files
by Farkas Levente 23 Apr '03

23 Apr '03

hi, what's happend if I change the index type ie. change it back to the default # mail_cache_fields while before I use mail_cache_fields = and restart dovecot? in this case at the next login the index files are regenerated? -- Levente "Si vis pacem para bellum!"

2 6

[dovecot] errors
by Farkas Levente 23 Apr '03

23 Apr '03

hi, in the yesterday cvs, an internal error in the imap message appear in the client side and in the maillog: ------------------------- Apr 16 10:01:42 red imap(zgabor): Corrupted index file /home/zgabor/Maildir/.Lists.Bugtraq/.imap.index: Invalid seen messages count (284 < 285) Apr 16 10:01:43 red imap(zgabor): Corrupted index file /home/zgabor/Maildir/.Lists.Linux/.imap.index: Invalid seen messages count (191 < 192) Apr 16 10:01:44 red imap(zgabor): Corrupted index file (in-memory index for /home/zgabor/Maildir/.Lists.Linux): Filename mismatch for UID 1: 1050448183.2238_1.red.int.bppiac.hu vs 1050321835.21498_1.red.int.bppiac.hu ------------------------- and this version is _very_ slow!!! -- Levente "Si vis pacem para bellum!"

3 6

[dovecot] quotas again
by Mark E. Mallett 21 Apr '03

21 Apr '03

A couple of notes about quotas-- I know this has been brought up before but the negative effects that occur when a user is over quota are still disconcerting. Ideally it would be best if a user could at least delete mail when in an over-quota condition. One would think it would be enough to simply ignore errors creating the index files (and use an in-memory index). However, another problem is that the mere renaming of a file from the new/ directory to the cur/ directory can cause an over-quota error if the cur/ directory has to be expanded. We see these errors in the maillog followed by an "I/O leak" message, e.g.: Apr 21 07:42:26 mercury mem[10059]: pop3(someuser): maildir build: rename(/users/3a/someuser/Maildir/new/1049919998.23875.mercury.mv.net, /users/3a/someuser/Maildir/cur/1049919998.23875.mercury.mv.net) failed: Disc quota exceeded Apr 21 07:42:26 mercury mem[10059]: pop3(someuser): I/O leak: 0x807361c (1) Apr 21 07:42:26 mercury mem[10059]: pop3(someuser): I/O leak: 0x804a1b8 (0) and then we get a report about the server dropping the connection. BTW we seem to see quite a lot of these "I/O leak" messages in other situations too, and I think it started with the test5 release (but I am not absolutely sure). What does this mean? Yours, mm

3 4

[dovecot] 0.99.9-test6
by Timo Sirainen 21 Apr '03

21 Apr '03

Just two fixes: - dovecot-uidlist file is now assumed to be changed if it's modify time is changed. before we relied on inode changing which isn't fully reliable. - mbox dotlocks sometimes incorrectly thought someone else had overridden them Known problems that I should fix: - mbox: we don't necessarily notice message flag changes by external programs (or another dovecot without index files). It's because we don't always reparse the whole mbox file when it has changed. I think I'll have to add some X-IMAP-Changelog header which describes what changes were made by other Dovecot processes. If the change isn't listed in that header, we'll fallback to reparsing the whole file. Although that's still a bit annoying since MTA just appends the new mails, we wouldn't really need to reparse the whole file then, just the new mails. - I should use link() instead of relying on O_EXCL which doesn't work with NFSv2 (or Linux's NFSv3 client). - .subscriptions and .customflags files still aren't NFS-safe

1 0

[dovecot] Folders with mail and subfolders
by Keith Edmunds 21 Apr '03

21 Apr '03

I have a maildir hierarchy (built originally with Courier-IMAP) where some folders contain both email and subfolders. Using Dovecot I cannot see the mail in the top folders: I can only see the subfolders. Is this an RFC restriction or a Dovecot restriction? If the latter, is it planned to change? Otherwise: just started using Dovecot, and I'm very impressed with the speed of it. Thanks! Keith

4 4

[dovecot] 0.99.9-test5
by Timo Sirainen 21 Apr '03

21 Apr '03

- Fixed startup crashing in POP3 server - Several fixes to opening index file which needs to be rebuilt. Before it didn't always rebuild the index but just fallbacked to using only memory, and that could have been quite slow since all mails in the mailbox were opened and parsed. - If there's nothing in mail_cache_fields, index rebuilding doesn't open the file anymore. This should make in-memory indexes a lot faster than before, but it could also mean some performance hits later. If client wants to fetch all mails from the mailbox, the same thing has to be done anyway.. This needs more thinking actually what is the optimal behaviour. - Support /etc/shadow-like file for passdb.

3 3

[dovecot] Message with lots of attachments breaks Dovecot
by Tim Hunt 21 Apr '03

21 Apr '03

I have a message with over a 1000 embedded attachments(!), and it breaks Dovecot. The issue appears to be buffer management. There is some logic in the function message_part_deserialize_part that seems to assume that the message part structure is in a contiguous array, but that doesn't seem to be the case. I haven't been able to figure out enough about the memory management in Dovecot to fix the problem. Below is a horrible workaround that just allocates a lot more memory for the message part array, so that it remains contiguous. *** mail-index-update.c.orig Wed Mar 26 10:41:55 2003 --- mail-index-update.c Sun Apr 20 16:53:45 2003 *************** *** 498,504 **** if (cache_fields & DATA_FIELD_MESSAGEPART) { t_push(); ! buf = buffer_create_dynamic(data_stack_pool, 2048, (size_t)-1); message_part_serialize(part, buf); --- 498,504 ---- if (cache_fields & DATA_FIELD_MESSAGEPART) { t_push(); ! buf = buffer_create_dynamic(data_stack_pool, 51200, (size_t)-1); message_part_serialize(part, buf);

2 1

[dovecot] Patch for zero content-length
by Tim Hunt 21 Apr '03

21 Apr '03

mbox-index.c uses a zero content length as a flag for an invalid Content-Length: header. Unfortunately zero is also a valid value for Content-Length. The patch below attempts to address the problem. *** mbox-index.h.orig Tue Apr 15 09:04:02 2003 --- mbox-index.h Sun Apr 20 11:42:12 2003 *************** *** 19,24 **** --- 19,25 ---- struct istream *input; uoff_t content_length; int set_read_limit; + unsigned int content_length_good:1; }; int mbox_set_syscall_error(struct mail_index *index, const char *function); *** mbox-index.c.orig Mon Mar 24 05:52:44 2003 --- mbox-index.c Sun Apr 20 12:41:16 2003 *************** *** 264,277 **** start_offset = ctx->input->v_offset; i_stream_set_read_limit(ctx->input, 0); ! end_offset = start_offset + ctx->content_length; ! if (ctx->content_length == 0 || !mbox_verify_end_of_body(ctx->input, end_offset)) { ! if (ctx->content_length != 0) i_stream_seek(ctx->input, start_offset); mbox_skip_message(ctx->input); end_offset = ctx->input->v_offset; ctx->content_length = end_offset - start_offset; } i_stream_seek(ctx->input, start_offset); --- 264,280 ---- start_offset = ctx->input->v_offset; i_stream_set_read_limit(ctx->input, 0); ! end_offset = start_offset; ! if ( ctx->content_length_good ) ! end_offset += ctx->content_length; ! if (!ctx->content_length_good || !mbox_verify_end_of_body(ctx->input, end_offset)) { ! if (ctx->content_length_good ) i_stream_seek(ctx->input, start_offset); mbox_skip_message(ctx->input); end_offset = ctx->input->v_offset; ctx->content_length = end_offset - start_offset; + ctx->content_length_good = TRUE; } i_stream_seek(ctx->input, start_offset); *************** *** 301,311 **** --- 304,316 ---- strcasecmp(hdr->name, "Content-Length") == 0) { /* manual parsing, so we can deal with uoff_t */ ctx->content_length = 0; + ctx->content_length_good = TRUE; for (i = 0; i < hdr->value_len; i++) { if (hdr->value[i] < '0' || hdr->value[i] > '9') { /* invalid */ ctx->content_length = 0; + ctx->content_length_good = FALSE; break; }

1 0

[dovecot] a few small bug
by Farkas Levente 18 Apr '03

18 Apr '03

during the ./autogen.sh there is a few problem: ----------------------------------------- configure.in: installing `./install-sh' configure.in: installing `./mkinstalldirs' configure.in: installing `./missing' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : installing `./config.guess' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : installing `./config.sub' configure.in:3: required file `./config.h.in' not found aclocal.m4:916: required file `./ltmain.sh' not found src/auth/Makefile.am: installing `./depcomp' configure.in:13: warning: AC_ARG_PROGRAM invoked multiple times autoheader: `config.h.in' is created ----------------------------------------- would it be possible to not use your own libtool in the cvs? in this case I can run autogen.sh during the rpm build and doesn't have to run manulay and patch the genereated makefile. ps. this is the patch I use: --- dovecot-1.0/configure.lfarkas 2003-03-20 15:53:04.000000000 +0100 +++ dovecot-1.0/configure 2003-03-20 15:54:37.000000000 +0100 @@ -8205,7 +8205,7 @@ LIBTOOL_DEPS="$ac_aux_dir/ltmain.sh" # Always use our own libtool. -LIBTOOL='$(SHELL) $(top_builddir)/libtool' +LIBTOOL='$(SHELL) libtool' # Prevent multiple expansion -- Levente "Si vis pacem para bellum!"

2 3

[dovecot] Corrupt mbox handling
by Kristian Hoffmann 17 Apr '03

17 Apr '03

I've found that if an mbox file has two consecutive 'From' delimiters, I get the error: pop3(user): Error indexing mbox file /var/spool/mail/user: LF not found where expected UofW apparently ignores the second 'From' silently. I've been trying to run dovecot in gdb to get more details on exactly what is happening, but I haven't quite mastered the art of attaching to the pop3 process between the login process completing and it exiting. Is there some trick to doing that? If I can't work around it in dovecot, I can just write something in perl to fix all the duplicate 'From' lines. Thanks, Kristian Hoffmann PC-InTOUCH/FireToWire System Administrator khoff(a)pc-intouch.com ---

2 1

[dovecot] Changing hierarchy separator to '/'
by Charlie Brady 17 Apr '03

17 Apr '03

3 4

[dovecot] PATCH Add support for kqueue in ioloop subsystem
by Dominic Marks 16 Apr '03

16 Apr '03

Hey, I noticed that there was an ioloop "module" (if we can call it that) for select and poll and decided to add one for kqueue (aka kevent) BSDs high performance descriptor multiplexing API. I haven't done any of the configure glue stuff but the code is complete and works well. kqueue is available on all recent versions of FreeBSD, NetBSD, OpenBSD and Darwin (and therefore MacOS X). I've tested both pop3 and imap with no problems. To get it working: (bodge method) > tar zxvf dovecot-0.99.8.1.tar.gz > cp ioloop-kevent.c dovecot-0.99.8.1/src/lib/ > cd dovecot-0.99.8.1/ > ./configure > vi config.h 1. replace IOLOOP_POLL (or IOLOOP_SELECT) with IOLOOP_KEVENT > vi src/lib/Makefile 1. find liblib_a_SOURCES add ioloop-kevent.c to it 2. find liblib_a_OBJECTS add ioloop-kevent.$(OBJEXT) to it > make There is a paper on kqueue which includes a performance evaulation here: http://people.freebsd.org/~jlemon/papers/kqueue.pdf Thanks, -- Dominic <dom at cus.org.uk> <d.marks at student.umist.ac.uk>

2 1

[dovecot] current cvs
by Farkas Levente 16 Apr '03

16 Apr '03

hi, so after upgrade to the current cvs all of our problem disappear:-) but we don't have time to test the ssl part... although after I compile and install the new dovecot I stop it I do a -------------------- find /home/*/Maildir -name '.imap*' -exec rm {} \; find /home/*/Maildir -name 'dovecot-uidlist' -exec rm {} \; find /home/*/Maildir -name 'msgid.cache' -exec rm {} \; find /home/*/Maildir -name '.customflags' -exec rm {}\; -------------------- just to be sure that we use a fresh version and no other problem can be caused by the old index or any other cached files. this was a BIG mistake!!! we've got about 300 users and about 100 online at the same time. after a two minutes break (while I reinstall and delete) every user check his mail which casue a load about 90!!! the cpu usage 1-2% but the avarage load was 90 (curently about 0.22)! the reason was IO. we have to stop imap and wait for a while... I don't know the exact reason bu I assume dovecot is regenerate everybody's index a other cache at the same time. is there any way to reduce the possible number of IO load? this would be useful if never happend again!:-) this happend around 4:40. the output of sar -b: -------------------- 03:00:00 PM tps rtps wtps bread/s bwrtn/s 03:10:00 PM 48.18 29.19 18.99 1456.53 771.29 03:20:00 PM 41.66 25.80 15.86 1054.88 830.05 03:30:00 PM 42.64 25.67 16.97 1223.03 759.77 03:40:00 PM 44.98 31.95 13.03 1959.15 467.40 03:50:00 PM 26.68 14.63 12.05 741.48 424.12 04:00:00 PM 25.80 11.70 14.10 516.21 450.04 04:10:00 PM 59.55 34.91 24.64 1755.07 939.11 04:20:00 PM 95.98 61.15 34.83 4453.24 1563.25 04:30:00 PM 95.08 55.45 39.63 2182.22 1591.56 04:40:00 PM 168.85 145.99 22.86 11155.73 1037.25 04:50:00 PM 135.98 106.50 29.48 7908.21 1604.76 05:00:00 PM 125.87 97.65 28.23 5876.03 1060.50 05:10:00 PM 80.83 62.92 17.90 4321.82 590.19 05:20:00 PM 102.04 77.65 24.40 4907.27 1076.92 05:30:00 PM 129.04 106.58 22.46 6387.18 883.13 05:40:00 PM 89.44 73.20 16.24 4905.64 782.94 05:50:00 PM 88.23 73.16 15.06 5539.93 965.34 06:00:00 PM 92.49 72.67 19.81 5486.25 692.18 06:10:00 PM 45.24 32.82 12.42 1711.35 618.31 06:20:00 PM 42.17 28.16 14.01 960.11 622.33 06:30:00 PM 29.90 20.24 9.66 1538.27 376.17 06:40:00 PM 25.89 12.14 13.74 796.73 833.25 06:50:00 PM 20.50 4.98 15.52 264.91 993.62 07:00:00 PM 15.08 7.57 7.52 453.41 282.63 -------------------- the output of sar -d -------------------- 04:10:00 PM dev22-3 0.00 0.00 04:10:00 PM dev33-0 1.76 109.55 04:10:00 PM dev34-0 8.51 919.94 04:20:00 PM dev3-0 8.56 183.93 04:20:00 PM dev22-2 67.62 3798.02 04:20:00 PM dev22-3 0.00 0.00 04:20:00 PM dev33-0 4.80 463.81 04:20:00 PM dev34-0 15.01 1570.73 04:30:00 PM dev3-0 4.40 126.63 04:30:00 PM dev22-2 77.02 2440.08 04:30:00 PM dev22-3 0.00 0.00 04:30:00 PM dev33-0 1.94 124.80 04:30:00 PM dev34-0 11.73 1082.28 04:40:00 PM dev3-0 4.78 124.56 04:40:00 PM dev22-2 137.27 10306.18 04:40:00 PM dev22-3 0.00 0.00 04:40:00 PM dev33-0 13.50 410.44 04:40:00 PM dev34-0 13.29 1351.80 04:50:00 PM dev3-0 6.33 194.27 04:50:00 PM dev22-2 111.50 7961.44 04:50:00 PM dev22-3 0.00 0.00 04:50:00 PM dev33-0 5.64 156.51 -------------------- -- Levente "Si vis pacem para bellum!"

2 5

[dovecot] Shadow password file
by Jaime Medrano 16 Apr '03

16 Apr '03

¿Is there any way to make dovecot to take the passwords from a file with a shadow password format? I've tried with the passwd-file auth plugin, but it complains that users have uid=0 Thanks in advance, Jaime Medrano

2 3

[dovecot] it seems to unusable
by Farkas Levente 16 Apr '03

16 Apr '03

hi, is there any way to turn off the whole indexing stuff? unfortunately the system getting totaly unusable beacuase of the high load and the mail index generation is so slow that every users call the helpdask that his mail is not working (what's more in this case just click on OE again and start another mailer process:-() we've got about 100k mails which is about 10-20GB! -- Levente "Si vis pacem para bellum!"

1 0

[dovecot] pop3 coredump
by Mark E. Mallett 16 Apr '03

16 Apr '03

Hi- I was able to get a coredump out of the new pop3 (from 0.99.9-test4) by attempting to simulate the execution environment and simply running the pop3 program. Running the older pop3 from 0.99.8.1 works fine, repeatedly: % /usr/local/libexec/dovecot/pop3 quit +OK Logging out. However running the new one: % /usr/local/libexec/dovecot/pop3.new pop3(user9): Error: Corrupted index file /users/48/user9/Maildir/.INBOX/.imap.index: index.next_uid (4539) > uidlist.next_uid (4000) Segmentation fault (core dumped) It doesn't always dump core even with this message. The error message is not always the same, but it's usually what's above. Simply repeating the invocation a number of times I also saw: pop3(user9): Error: Corrupted index file (in-memory index for /users/48/user9/Maildir): Filename mismatch for UID 1: 1050440153.17005.mercury.mv.net vs 1050437948.5418.mercury.mv.net Here's some gdb output corresponding to the coredump above. -mm- Script started on Tue Apr 15 16:51:28 2003 % gdb pop3/pop3 pop3.core ... Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/local/lib/libiconv.so.2...done. Reading symbols from /shlib/libgcc.so.1...done. Reading symbols from /shlib/libc.so.2...done. Reading symbols from /shlib/ld-bsdi.so...done. #0 0x0 in ?? () (gdb) bt #0 0x0 in ?? () #1 0x8053439 in index_storage_init (storage=0x808f000, box=0x8080658, index=0x808c200, name=0x807660e "INBOX", readonly=0, fast=0) at index-storage.c:264 #2 0x804b8e0 in maildir_open (storage=0x808f000, name=0x807660e "INBOX", readonly=0, fast=0) at maildir-storage.c:239 #3 0x804ba20 in maildir_open_mailbox (storage=0x808f000, name=0x80765b1 "INBOX", readonly=0, fast=0) at maildir-storage.c:288 #4 0x804b1c7 in main_init () at main.c:98 #5 0x804b269 in main (argc=1, argv=0x8047d3c, envp=0x8047d44) at main.c:132 #6 0x8049cae in __start () (gdb) up 1 #1 0x8053439 in index_storage_init (storage=0x808f000, box=0x8080658, index=0x808c200, name=0x807660e "INBOX", readonly=0, fast=0) at index-storage.c:264 264 storage->callbacks->notify_no(&ibox->box, (gdb) l 259 if (!index->open(index, flags)) 260 break; 261 262 if (INDEX_IS_IN_MEMORY(index) && 263 storage->index_dir != NULL) { 264 storage->callbacks->notify_no(&ibox->box, 265 "Couldn't use index files", 266 storage->callback_context); 267 } 268 } (gdb) p index $1 = (struct mail_index *) 0x808c200 (gdb) p *index $2 = {open = 0x8054590 <maildir_index_open>, free = 0x8054abc <maildir_index_free>, set_lock = 0x805c874 <mail_index_set_lock>, try_lock = 0x805c88c <mail_index_try_lock>, set_lock_notify_callback = 0x805c8a4 <mail_index_set_lock_notify_callback>, rebuild = 0x8054f20 <maildir_index_rebuild>, fsck = 0x805de50 <mail_index_fsck>, sync_and_lock = 0x8055db4 <maildir_index_sync>, get_header = 0x805c928 <mail_index_get_header>, lookup = 0x805c968 <mail_index_lookup>, next = 0x805cac0 <mail_index_next>, lookup_uid_range = 0x805cb48 <mail_index_lookup_uid_range>, lookup_field = 0x805cc58 <mail_index_lookup_field>, lookup_field_raw = 0x805ccac <mail_index_lookup_field_raw>, cache_fields_later = 0x805cd70 <mail_index_cache_fields_later>, open_mail = 0x8054de0 <maildir_open_mail>, get_internal_date = 0x8054afc <maildir_get_internal_date>, expunge = 0x805d078 <mail_index_expunge>, update_flags = 0x8054b6c <maildir_index_update_flags>, append_begin = 0x805d3ec <mail_index_append_begin>, append_end = 0x805d4e4 <mail_index_append_end>, append_abort = 0x805d590 <mail_index_append_abort>, update_begin = 0x805f9b0 <mail_index_update_begin>, update_end = 0x805ff68 <mail_index_update_end>, update_abort = 0x8060050 <mail_index_update_abort>, update_field = 0x806022c <mail_index_update_field>, update_field_raw = 0x806025c <mail_index_update_field_raw>, get_last_error = 0x805d618 <mail_index_get_last_error>, get_last_error_text = 0x805d678 <mail_index_get_last_error_text>, data = 0x80821a0, tree = 0x80900c0, modifylog = 0x808d200, custom_flags = 0x808d100, dir = 0x8090000 "/users/48/user9/Maildir/.INBOX", filepath = 0x8090040 "(in-memory index for /users/48/user9/Maildir)", mailbox_path = 0x8082160 "/users/48/user9/Maildir", custom_flags_dir = 0x0, default_cache_fields = 0, never_cache_fields = 0, indexid = 1050439124, sync_id = 6, excl_lock_counter = 1, mbox_fd = 0, mbox_stream = 0x0, mbox_lock_type = MAIL_LOCK_UNLOCK, mbox_dotlock = { dev = 0, ino = 0, mtime = 0}, mbox_lock_counter = 0, mbox_sync_counter = 0, mbox_size = 0, mbox_dev = 0, mbox_ino = 0, uidlist_dev = 18875392, uidlist_ino = 1835546, maildir_lock_fd = -1, fd = -1, error = 0x0, mmap_base = 0x20073000, mmap_used_length = 264, mmap_full_length = 1608, header = 0x20073000, lock_type = MAIL_LOCK_EXCLUSIVE, file_sync_stamp = 1050438868, first_recent_uid = 1, lock_notify_cb = 0x8053238 <lock_notify>, lock_notify_context = 0x808c400, set_flags = 0, set_cache_fields = 0, anon_mmap = 1, opened = 0, rebuilding = 0, mail_read_mmaped = 0, inconsistent = 0, nodiskspace = 0, index_lock_timeout = 0, allow_new_custom_flags = 0, mailbox_readonly = 0, mailbox_lock_timeout = 0} (gdb) p storage $3 = (struct mail_storage *) 0x808f000 (gdb) p *storage $5 = {name = 0x8076805 "maildir", hierarchy_sep = 46 '.', create = 0x804b2c0 <maildir_create>, free = 0x804b428 <maildir_free>, autodetect = 0x804b480 <maildir_autodetect>, set_callbacks = 0x80535e4 <index_storage_set_callbacks>, open_mailbox = 0x804b940 <maildir_open_mailbox>, create_mailbox = 0x804ba5c <maildir_create_mailbox>, delete_mailbox = 0x804bb08 <maildir_delete_mailbox>, rename_mailbox = 0x804bea4 <maildir_rename_mailbox>, list_mailbox_init = 0x804c624 <maildir_list_mailbox_init>, list_mailbox_deinit = 0x804c800 <maildir_list_mailbox_deinit>, list_mailbox_next = 0x804cc48 <maildir_list_mailbox_next>, set_subscribed = 0x8064594 <subsfile_set_subscribed>, get_mailbox_name_status = 0x804bffc <maildir_get_mailbox_name_status>, get_last_error = 0x805455c <mail_storage_get_last_error>, dir = 0x8082100 "/users/48/user9/Maildir", inbox_file = 0x0, index_dir = 0x8082120 "/users/48/user9/Maildir", user = 0x808e050 "user9", error = 0x0, callbacks = 0x8082140, callback_context = 0x0, syntax_error = 0} (gdb) p ibox $6 = (struct index_mailbox *) 0x808c400 (gdb) p *ibox $7 = {box = {name = 0x808e070 "INBOX", storage = 0x808f000, close = 0x805359c <index_storage_close>, get_status = 0x8052ee4 <index_storage_get_status>, sync = 0x8053b94 <index_storage_sync>, auto_sync = 0x804c0c8 <maildir_storage_auto_sync>, expunge = 0x804fa64 <index_storage_expunge>, update_flags = 0x8053d58 <index_storage_update_flags>, copy = 0x804c3e4 <maildir_storage_copy>, fetch_init = 0x804fb00 <index_storage_fetch_init>, fetch_deinit = 0x804fbe8 <index_storage_fetch_deinit>, fetch_next = 0x804fc70 <index_storage_fetch_next>, fetch_uid = 0x804fd5c <index_storage_fetch_uid>, fetch_seq = 0x804fdc0 <index_storage_fetch_seq>, search_get_sorting = 0x8052af4 <index_storage_search_get_sorting>, search_init = 0x8052b08 <index_storage_search_init>, search_deinit = 0x8052be0 <index_storage_search_deinit>, search_next = 0x8052ca0 <index_storage_search_next>, save_init = 0x804cf4c <maildir_storage_save_init>, save_deinit = 0x804cfe0 <maildir_storage_save_deinit>, save_next = 0x804ce04 <maildir_storage_save_next>, is_inconsistency_error = 0x8054578 <mail_storage_is_inconsistency_error>, readonly = 0, allow_custom_flags = 0, inconsistent = 0}, expunge_locked = 0, index = 0x808c200, autosync_to = 0x0, autosync_files = 0x0, autosync_type = MAILBOX_SYNC_NONE, sync_last_check = 0, min_newmail_notify_interval = 0, fetch_mail = {mail = {seq = 0, uid = 0, seen_updated = 0, get_flags = 0, get_parts = 0, get_received_date = 0, get_date = 0, get_size = 0, get_header = 0, get_address = 0, get_first_mailbox = 0, get_stream = 0, get_special = 0}, data = {flags = { flags = 0, custom_flags = 0x0, custom_flags_count = 0}, received_date = 0, size = 0, sent_time = 0, sent_timezone = 0, headers = 0x0, parts = 0x0, envelope = 0x0, body = 0x0, bodystructure = 0x0, envelope_data = 0x0, rec = 0x0, stream = 0x0, hdr_size = {physical_size = 0, virtual_size = 0, lines = 0}, body_size = { physical_size = 0, virtual_size = 0, lines = 0}, parse_header = 0, save_sent_time = 0, save_envelope = 0, hdr_size_set = 0, body_size_set = 0}, pool = 0x0, ibox = 0x0, header_buf = 0x0, wanted_fields = 0, wanted_headers = 0x0}, synced_messages_count = 0, next_lock_notify = 1050439154, last_notify_type = MAIL_LOCK_NOTIFY_MAILBOX_ABORT, sent_diskspace_warning = 0} (gdb) quit % exit Script done on Tue Apr 15 16:53:06 2003

2 3

[dovecot] PATCH allow_zero_gid option
by Dominic Marks 15 Apr '03

15 Apr '03

Hey, Well, that was easy :-) Patch against CVS follows: Summary: Created a boolean option allow_zero_gid, when set to yes it will allow logins from users whose group id is zero. Tested with KMail 3.1.1 on FreeBSD 4.8. I'm not sure if my method for passing the boolean via the environment is correct, it looks a little on the ugly side. Index: src/lib/restrict-access.c =================================================================== RCS file: /home/cvs/dovecot/src/lib/restrict-access.c,v retrieving revision 1.10 diff -u -3 -p -r1.10 restrict-access.c --- src/lib/restrict-access.c 4 Mar 2003 04:00:13 -0000 1.10 +++ src/lib/restrict-access.c 15 Apr 2003 17:37:26 -0000 @@ -31,12 +31,14 @@ #include <grp.h> void restrict_access_set_env(const char *user, uid_t uid, gid_t gid, - const char *chroot_dir) + const char *chroot_dir, int allow_zg) { if (user != NULL && *user != '\0') env_put(t_strconcat("RESTRICT_USER=", user, NULL)); if (chroot_dir != NULL && *chroot_dir != '\0') env_put(t_strconcat("RESTRICT_CHROOT=", chroot_dir, NULL)); + if (allow_zg == TRUE) + env_put(t_strdup("ALLOW_ZERO_GID=TRUE")); env_put(t_strdup_printf("RESTRICT_SETUID=%s", dec2str(uid))); env_put(t_strdup_printf("RESTRICT_SETGID=%s", dec2str(gid))); @@ -45,6 +47,7 @@ void restrict_access_set_env(const char void restrict_access_by_env(int disallow_root) { const char *env; + int allow_zero_gid; gid_t gid; uid_t uid; @@ -97,8 +100,14 @@ void restrict_access_by_env(int disallow i_fatal("We couldn't drop root privileges"); } - if ((gid != 0 && uid != 0) || disallow_root) { + /* allow users with zero group id permission for BSD */ + env = getenv("ALLOW_ZERO_GID"); + allow_zero_gid = env == NULL ? FALSE : TRUE; + + if (allow_zero_gid == FALSE && + ((gid != 0 && uid != 0) || disallow_root)) { if (getgid() == 0 || getegid() == 0 || setgid(0) == 0) i_fatal("We couldn't drop root group privileges"); } + } Index: src/lib/restrict-access.h =================================================================== RCS file: /home/cvs/dovecot/src/lib/restrict-access.h,v retrieving revision 1.4 diff -u -3 -p -r1.4 restrict-access.h --- src/lib/restrict-access.h 4 Mar 2003 04:00:13 -0000 1.4 +++ src/lib/restrict-access.h 15 Apr 2003 17:37:26 -0000 @@ -4,7 +4,7 @@ /* set environment variables so they can be read with restrict_access_by_env() */ void restrict_access_set_env(const char *user, uid_t uid, gid_t gid, - const char *chroot_dir); + const char *chroot_dir, int allow_zg); /* chroot, setuid() and setgid() based on environment variables. If disallow_roots is TRUE, we'll kill ourself if we didn't have the Index: src/master/auth-process.c =================================================================== RCS file: /home/cvs/dovecot/src/master/auth-process.c,v retrieving revision 1.41 diff -u -3 -p -r1.41 auth-process.c --- src/master/auth-process.c 2 Apr 2003 02:09:41 -0000 1.41 +++ src/master/auth-process.c 15 Apr 2003 17:37:27 -0000 @@ -307,7 +307,7 @@ static pid_t create_auth_process(struct /* setup access environment */ restrict_access_set_env(group->set->user, pwd->pw_uid, pwd->pw_gid, - group->set->chroot); + group->set->chroot, set->allow_zero_gid); /* set other environment */ env_put(t_strconcat("AUTH_PROCESS=", dec2str(getpid()), NULL)); Index: src/master/login-process.c =================================================================== RCS file: /home/cvs/dovecot/src/master/login-process.c,v retrieving revision 1.40 diff -u -3 -p -r1.40 login-process.c --- src/master/login-process.c 15 Apr 2003 16:58:48 -0000 1.40 +++ src/master/login-process.c 15 Apr 2003 17:37:27 -0000 @@ -384,7 +384,8 @@ static void login_process_init_env(struc clean_child_process() since it clears environment */ restrict_access_set_env(group->set->user, group->set->uid, set->login_gid, - set->login_chroot ? set->login_dir : NULL); + set->login_chroot ? set->login_dir : NULL, + set->allow_zero_gid); env_put("DOVECOT_MASTER=1"); Index: src/master/mail-process.c =================================================================== RCS file: /home/cvs/dovecot/src/master/mail-process.c,v retrieving revision 1.13 diff -u -3 -p -r1.13 mail-process.c --- src/master/mail-process.c 15 Apr 2003 16:58:48 -0000 1.13 +++ src/master/mail-process.c 15 Apr 2003 17:37:28 -0000 @@ -25,7 +25,7 @@ static int validate_uid_gid(uid_t uid, g return FALSE; } - if (uid != 0 && gid == 0) { + if (set->allow_zero_gid == FALSE && uid != 0 && gid == 0) { i_error("mail process isn't allowed to be in group 0"); return FALSE; } @@ -38,8 +38,9 @@ static int validate_uid_gid(uid_t uid, g return FALSE; } - if (gid < (gid_t)set->first_valid_gid || - (set->last_valid_gid != 0 && gid > (gid_t)set->last_valid_gid)) { + if (set->allow_zero_gid == FALSE && + (gid < (gid_t)set->first_valid_gid || + (set->last_valid_gid != 0 && gid > (gid_t)set->last_valid_gid))) { i_error("mail process isn't allowed to use " "GID %s (UID is %s)", dec2str(gid), dec2str(uid)); return FALSE; @@ -150,7 +151,8 @@ int create_mail_process(int socket, stru (paranoia about filling up environment without noticing) */ restrict_access_set_env(data + reply->system_user_idx, reply->uid, reply->gid, - reply->chroot ? data + reply->home_idx : NULL); + reply->chroot ? data + reply->home_idx : NULL, + set->allow_zero_gid); restrict_process_size(process_size, (unsigned int)-1); Index: src/master/master-settings.c =================================================================== RCS file: /home/cvs/dovecot/src/master/master-settings.c,v retrieving revision 1.16 diff -u -3 -p -r1.16 master-settings.c --- src/master/master-settings.c 2 Apr 2003 02:09:41 -0000 1.16 +++ src/master/master-settings.c 15 Apr 2003 17:37:28 -0000 @@ -46,6 +46,7 @@ static struct setting_def setting_defs[] DEF(SET_INT, max_mail_processes), DEF(SET_BOOL, verbose_proctitle), + DEF(SET_BOOL, allow_zero_gid), DEF(SET_INT, first_valid_uid), DEF(SET_INT, last_valid_uid), DEF(SET_INT, first_valid_gid), @@ -153,6 +154,7 @@ struct settings default_settings = { MEMBER(max_mail_processes) 1024, MEMBER(verbose_proctitle) FALSE, + MEMBER(allow_zero_gid) FALSE, MEMBER(first_valid_uid) 500, MEMBER(last_valid_uid) 0, MEMBER(first_valid_gid) 1, Index: src/master/master-settings.h =================================================================== RCS file: /home/cvs/dovecot/src/master/master-settings.h,v retrieving revision 1.10 diff -u -3 -p -r1.10 master-settings.h --- src/master/master-settings.h 2 Apr 2003 02:09:41 -0000 1.10 +++ src/master/master-settings.h 15 Apr 2003 17:37:29 -0000 @@ -32,6 +32,7 @@ struct settings { unsigned int max_mail_processes; int verbose_proctitle; + int allow_zero_gid; unsigned int first_valid_uid, last_valid_uid; unsigned int first_valid_gid, last_valid_gid; Thanks, -- Dominic <dom at cus.org.uk> <d.marks at student.umist.ac.uk>

2 2

[dovecot] 0.99.9-test4
by Timo Sirainen 15 Apr '03

15 Apr '03

http://procontrol.fi/test/ - Crashfix for multipart messages - More optimized mbox rewriting, should be "good enough" for most uses I think. I've been using it for a while now, seems to work. Still some problems: imap(cras): Apr 15 01:48:48 Warning: Our dotlock file /home/cras/mail//full-disclosure.lock was overridden And I'm sure it wasn't. Or at least shouldn't have been. Have to look more into this..

4 4

[dovecot] Group ID validation and FreeBSD
by Dominic Marks 15 Apr '03

15 Apr '03

Hey, I've been working on making the Dovecot FreeBSD port resemble something which actually works this weekend, it's now much improved - one thing that I did notice is that Dovecot validates a users GID and will not accept a group id of 0. In FreeBSD the group wheel has a the id 0 and only members of the wheel group are allowed to use su and become root. Consequently there are non-root users who have group id's of 0. When you try and open the mailbox of such a user with Dovecot the connection is killed immediately. It would be excellent to have an option in dovecot.conf along the lines of allow_zero_gid which would disable these checks. From a quick look at the source I can see that the validation is being done in src/master/mail-process.c and that src/lib/restrict-access.c is also involved. If I can get a working patch ready quickly I'll pass it along. If anyone would like to take a look at the port you can get a copy at the following address: http://cus.org.uk/~dom/dovecot-0.99.8.1.shar.gz Hopefully this will go into FreeBSD CVS quite soon. Thanks, -- Dominic <dom at cus.org.uk> <d.marks at student.umist.ac.uk>

1 0

[dovecot] 0.99.9-test3
by Timo Sirainen 15 Apr '03

15 Apr '03

Expunging messages caused those "Corrupted index file" errors. That's fixed now. There's probably still some problems, at least this fix didn't fix any crashes.. test3 available from http://dovecot.procontrol.fi/test/

2 3

[dovecot] a crashy message
by Moe Wibble 15 Apr '03

15 Apr '03

Hi everyone, the attached message does reliably crash my dovecot when trying to access a folder containing it. Crash notice in mail.log: Apr 13 17:36:12 rafter dovecot: child 23215 (imap) killed with signal 11 My `dovecot --version` says: 0.99.8 Has this problem been fixed in current dovecot? For now I have just quarantined the offending message but obviously I need to upgrade my dovecot soon because I don't like such kinda things to happen. best regards! -- MW

2 2

[dovecot] Three *very* strange bugs
by Warren Togami 15 Apr '03

15 Apr '03

* Attached is a mbox file that triggers Bug #1 and #2. * Go here if you want to test dovecot for RH9: https://bugzilla.fedora.us/show_bug.cgi?id=160 * If somebody has a different IMAP server than dovecot, could you please test how Evolution reacts to reading this message? Bug #1 dovecot and #2 evolution-1.2.3 ===================================== I am using dovecot-0.99.9-test3 on RH9, reading mail with evolution-1.2.2-5 on RH9. Whenever I attempt to view this one particular spam message, evolution pops up an error like: Error while 'Retrieving message 4': Server unexpectedly disconnected: No such file or directory Simultaneously this appears in my /var/log/maillog: Apr 15 01:44:50 server dovecot: child 20328 (imap) killed with signal 11 If I attempt to keep reading mail, it logs in again to dovecot and works normally until I attempt to read that spam again. Evolution displays the error popup again though I don't see another signal 11 in maillog. After this point I am unable to log back into dovecot without restarting the daemon. Here's the strange part... I browsed the same IMAP folder from KMail, and kmail has no problem reading that spam message. dovecot's [imap] process does not segmentation fault. Does this mean an evolution bug when reading this particular spam exposed a dovecot segmentation fault? Bug #3 kernel? ============== This is an unrelated bug and perhaps not the fault of dovecot. When I attempted to use strace to get some debugging info on the [imap] process, this happened: [root@server /]# strace -p 20486 trace: ptrace(PTRACE_SYSCALL, ...): Operation not permitted detach: ptrace(PTRACE_DETACH, ...): Operation not permitted [root@server /]# This isn't normal right? After doing this, dovecot stops working and I need to restart the daemon in order to establish new connections. That [imap] process becomes unkillable, even kill -9 wont work. Unkillable process usually means kernel bug, right? warren 20345 1 7 01:46 ? 00:00:34 [imap] This is kernel-2.4.20-9 in Red Hat Linux 9. Is dovecot exposing a Red Hat kernel bug when I try to strace that process, or is strace supposed to fail, the dovecot daemon ceases to function and [imap] process becomes completely unkillable? =) Warren Togami warren(a)togami.com

2 1

DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
by Mail System Internal Data 15 Apr '03

15 Apr '03

This text is part of the internal format of your mail folder, and is not a real message. It is created automatically by the mail system software. If deleted, important folder data will be lost, and it will be re-created with the data reset to initial values.

1 0

The Discover(r) Platinum Wildlife Card - Go Wild
by Wild Life 15 Apr '03

15 Apr '03

Offer Expires April 30, 2003 X-Rcpt-To: <warren(a)togami.com> Get a 0% Intro APR* on Purchases and Balance Transfers Youve been selected for a special No-Annual-Fee Discover® Card with all of these privileges: · 0% Intro APR on Purchases and Balance Transfers* · No Annual Fee · Up to 2% Cashback Bonus® award* · Up to $50,000 Credit Limit Start Saving Today APPLY NOW! It's fast, easy and secure. http://ileadmarketing.com/mkt/lead?&l=56217&a=16cc7b&z=57366 To take advantage of this special offer, act by April 30, 2003! * Click here to see information about the APR, fees and other Important Information .................................................................... ILeadMarketing never sends unsolicited email. ILeadMarketing has been given the right to market to you through our Web site partners and their privacy policies. Specifically, you are receiving this correspondence because you have provided consent (via your registration and acceptance of the privacy policies for a newsletter, contest, web-based service or other activity on the web) to receive recurring promotions or offers from various third parties. If you feel that you are receiving this email in error or are not interested in receiving future offers please click here: http://www.ileadmarketing.com/mkt/seeya?email=warren@togami.com&c=57366 , or email us at seeya(a)ileadmarketing.com. ILeadMarketing is not responsible for third party offers, services or products and makes no representations or warranties regarding them. ..................................................................... --=-1kN4J0lqIIqLcGMke0AY--

1 0

[dovecot] dovecot RPM for Red Hat Linux
by Warren Togami 14 Apr '03

14 Apr '03

http://bugzilla.fedora.us/show_bug.cgi?id=160 This .src.rpm is dovecot with RH-specific default settings. I modified Jeremy Katz' dovecot-0.99.8.1 package a bit. When I upgraded from 0.99.8.1 it seemed to be broken until I looked at /var/log/maillog. There it indicated that the dovecot cache files were bad, so I erased /home/*/mail/.imap/ and it seemed to work subsequently. There are a few more RH specific tweaks that I plan on doing for this package. If you have any suggestions to default config tweaks for this package please reply or post in that bugzilla entry above. I would like for this package to be a drop-in replacement for RHL's uw-imapd eventually, but there are a number of migration issues that need to be addressed first. This package will eventually be included in the Fedora tree after it goes through our QA. http://www.fedora.us Fedora Linux is a project of volunteer package developers making 3rd party packages specifically for Red Hat Linux. Warren Togami warren(a)togami.com p.s. Keep up the good work. I absolutely love dovecot!

4 6

[dovecot] Something wrong in SSL ?
by Juha Ylitalo 14 Apr '03

14 Apr '03

Operating system: FreeBSD 4.7-RELEASE-p10 Dovecot: 0.99.8.1 I've used openssl to generate personal CA and I've used that one to generate certificate for my web server. When I tried to go through same pattern for generating certificate for IMAP server from CA, I ended up in situation, where both mutt and evolution keep on rejecting my certificates.

2 2

[Daniel Silverstone <dsilvers@digital-scurf.org>] Re: lua 5.0
by Per Olofsson 13 Apr '03

13 Apr '03

FYI. /Pelle

1 0

[dovecot] Maildir problem?
by Maikel Verheijen 11 Apr '03

11 Apr '03

Hey list, Today I cvs updated to the most recent dovecot, to test with the recent improvements on the dovecot-uidlist file, and came acros the following: Apr 11 12:49:36 pc-5-046 imap(): Corrupted index file (in-memory index for /var/mail/mounted/test.com/maikel/Maildir//.Sent Items): Filename mismatch for UID 1: 1050058115.P3401Q0M675362.pc-5-046.test.nl:2,S vs 1050057888.P3371Q0M138398.pc-5-046.test.nl I am using a front-end back-end construction, But I am testing on the backend only (non-nfs), because the subscriptions file isn't nfs safe yet. shouldn't the uidl files be leading over the indexes? And shouldn't the indexes be updated as well? Thank you, Maikel Verheijen.

1 0

[dovecot] Maildir syncing rewrite
by Timo Sirainen 11 Apr '03

11 Apr '03

It finally seems to be working. I've done some testing now and it seems to be working fine. If you have time, see if you can get it to break (especially with INDEX=memory or by manually modifying the maildir). The UIDs are kept in Courier-compatible dovecot-uidlist file (so "mv courierimapuiddb dovecot-uidlist" should work). The great thing about this code is that we never wait for lock. If we can't lock, we simply use the old uidlist file to sync whatever we can, which should be everything but the very newest mails just being delivered and processed by another Dovecot. Of course, if they share index files, we're still blocking there. I named the file as "dovecot-uidlist" instead of ".uidlist" because I finally realized that files beginning with dot conflict with the mailbox namespace. I should rename .customflags and .subscriptions files as well. Also if I move .imap.index* files into root dir, I'll have to rename them too. new/ directory is now scanned every time to see if there's new mail. cur/ directory is scanned if index file's timestamp differs from cur/ dir's timestamp. uidlist file is reread if it's device/inode changes. You can get the sources from either CVS, or 0.99.9-test2 from http://dovecot.procontrol.fi/test/

3 5

[dovecot] dovecot-0.99.9-test2 probs
by Mark E. Mallett 11 Apr '03

11 Apr '03

Hi- Tried 0.99.9-test2 -- had to go back. Various problems in the log. Here's one: Apr 10 08:56:25 mercury mem[10754]: imap(user0): msync() failed with index data file /users/8b/user0/Maildir/.INBOX/.imap.index.data: Cannot allocate memory Apr 10 08:56:25 mercury mem[10754]: imap(user0): Corrupted index data file /users/8b/user0/Maildir/.INBOX/.imap.index.data: Missing location field for record 156 Apr 10 08:56:25 mercury mem[10754]: imap(user0): msync() failed with index data file /users/8b/user0/Maildir/.INBOX/.imap.index.data: Cannot allocate memory Here's another: Apr 10 18:56:59 mercury mem[13376]: pop3(user1): Corrupted index file /users/30/user1/Maildir/.INBOX/.imap.index: index.next_uid (2365) > uidlist.next_uid (2364) And another: Apr 10 19:09:24 mercury mem[10892]: pop3(user2): Corrupted index file /users/39/user2/Maildir/.INBOX/.imap.index: index.next_uid (10422) > uidlist.next_uid (10420) Apr 10 19:09:24 mercury mem[10892]: pop3(user2): Corrupted index file (in-memory index for /users/39/user2/Maildir): Filename mismatch for UID 1: 1050015983.28176.mercury.mv.net vs 1046192106.460.mercury.mv.net Apr 10 19:09:24 mercury mem[10892]: pop3(user2): No INBOX for user And a ton of these, without any other entry for the process ID (which I assume is the number after "child"): Apr 10 19:09:33 mercury dovecot: child 1645 (imap) killed with signal 11

1 0

[dovecot] compilation errors
by Mark E. Mallett 11 Apr '03

11 Apr '03

Hi- I always encounter the same two minor compilation issues which are easily addressed simply by a quick edit, but this time I figured I'd mention it in case you can work around it. This is on a BSD/OS 4.2 system. First, the generated config.h always creates a definition for OFF_T_MAX which conflicts with the one in the system's limits.h config.h defines: #define OFF_T_MAX LLONG_MAX whereas /usr/include/machine/limits.h defines: #define OFF_T_MAX UQUAD_MAX /* max value for an off_t */ I simply comment out the definition from config.h . Second, in src/lib/mmap-anon.c there's a preprocessor conditional: #if SSIZE_T_MAX >= LLONG_MAX (etc) Unfortunately /usr/include/machine/limits.h defines LLONG_MAX thusly: #define LLONG_MAX (__extension__(9223372036854775807LL)) (evidently to suppress pedantic warnings about the gcc long long constant extension) but the cpp prepreprocessor stumbles over this comparison. This might be fixed in a later gcc, I dunno- it's gcc 2.95.2 here. Yours, -mm-

1 0

[dovecot] dovecot and virtual users
by Jej 10 Apr '03

10 Apr '03

Hello, I set up a virtual smtp with exim (mails stored in /var/virtual/{domain}/{user}, passwd in /etc/virtual/{domain}.passwd). I have a patched pop3 server to deal with these mail boxes. Would it be possible to use dovecot as imap server, or (even better) for imap and pop3, with this virtual domain model ? Thanks, read you. -- jej

2 1

[dovecot] Error: child 12625 (imap) killed with signal 12
by Johan Willard 09 Apr '03

09 Apr '03

Hi! I have tried to install dovecot as my imap service on my FreeBSD server. At first all looked fine and worked flawless. But after a while i started to get errors. The imap process dies with signal 12 when the client tries to check the contens of the folder. dovecot: Apr 07 09:55:17 Error: child 12625 (imap) killed with signal 12 Any ideas what may cause this problem? MvH Johan Willard

3 6

[dovecot] New installation - error 89 on connect
by David Knudsen 09 Apr '03

09 Apr '03

I've recently installed dovecot (0.99.8.1) from the Debian/woody backport at 'deb http://src.braincells.com/debian woody/' Previously, all mail have been delivered to mbox'es in ~/Mail by exim/procmail -- ~/Mail/inbox being my main mailbox. Whenever I attempt to connect with an IMAP client, the connection is closed and the following error is reported in /var/log/syslog: imap-login: Login: dk [192.168.0.2] imap(dk): Unknown client workaround: outlook-idle^I### dovecot: child 17653 (imap) returned error 89 What does error 89 signify? My current configuration is: (non-comment lines only) imap_listen = 192.168.0.2 imaps_listen = * login = imap login = pop3 verbose_proctitle = yes client_workarounds = oe6-fetch-no-newmail outlook-idle mailbox_check_interval = 60 auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root auth_verbose = yes In my confusion, I blindly tried changing settings, attempting to get a different error message at least. :-) These are the settings I have tried, without success: default_mail_env = mbox:~/Mail:INBOX=~/Mail/inbox mail_full_filesystem_access = yes mbox_locks = fcntl auth_passdb = shadow There is no subdirectories in ~/Mail, neither visible nor hidden. I did try to read the docs, and I did browse the mailing list archives, but either I missed something or it is not there. Any ideas? Thank you, David Knudsen

2 2

[dovecot] Re: command line version of dovecot?
by Timo Sirainen 09 Apr '03

09 Apr '03

On Wed, 2003-04-09 at 18:52, Kyler Laird wrote: > > There's the "imap" binary that should do exactly that. Usually installed > > into /usr/local/libexec/dovecot/imap > > Ah! That's just the kind of solution I sought. > > Unfortunately it doesn't seem to work for me. It doesn't > appear (via strace) to read any configuration file. It just > looks in /var/mail/[user] for a Maildir. I need to to go to > the Maildir in the user's home (and follow other behaviors > defined in the config file). It should look into ~/Maildir first, then ~/mail and ~/Mail unless it's overridden in MAIL environment. You probably have MAIL=/var/mail/user set, which is why it looks into there. Currently it doesn't read any configuration file, and I'm not sure if I should make it do that.. Well, it could be useful but I'd have to figure out how to prevent unneeded code duplication for config file parsing. All settings are passed via environment settings, but they're not documented (they're basically uppercased versions of the setting names in config file). > Should I have found all of this in some documentation? I > appreciate the help but I feel like I should be reading > about this on my own somewhere. doc/mail-storages.txt explains the MAIL environment.

1 0

[dovecot] command line version of dovecot?
by Timo Sirainen 09 Apr '03

09 Apr '03

> From: Kyler Laird <kyler-keyword-dovecot.a0ff9b(a)lairds.org> > I finally have dovecot mostly working and I was thinking that > I'd been saved from having to use UW-IMAPd, but I just now > noticed that there doesn't appear to be any way to run > dovecot over standard I/O; it always wants to listen on a > socket. There's the "imap" binary that should do exactly that. Usually installed into /usr/local/libexec/dovecot/imap Or did you mean you wanted to run it from inetd? CVS version supports that too if you execute imap-login.

1 0

[dovecot] message order reversed on copying
by Kimura Fuyuki 09 Apr '03

09 Apr '03

Hi, I noticed an annoying behavior of dovecot: the message order (sequence numbering) is reversed on COPYing in the maildir. I suspect that the following code in maildir-save.c is working like "pushing". mf->next = ctx->files; ... ctx->files = mf; Later ctx->files is used like this. for (mf = ctx->files; mf != NULL; mf = mf->next) { -- fuyuki

4 8

[dovecot] Patch for passdb-passwd-file.c
by Armin Wolfermann 08 Apr '03

08 Apr '03

Index: passdb-passwd-file.c =================================================================== RCS file: /home/cvs/dovecot/src/auth/passdb-passwd-file.c,v retrieving revision 1.6 diff -u -u -r1.6 passdb-passwd-file.c --- passdb-passwd-file.c 18 Feb 2003 19:24:44 -0000 1.6 +++ passdb-passwd-file.c 8 Apr 2003 15:59:53 -0000 @@ -28,7 +28,7 @@ crypted_pass = pu->password; scheme = password_get_scheme(&crypted_pass); - if (scheme == NULL) scheme = "DES"; + if (scheme == NULL) scheme = "CRYPT"; ret = password_verify(password, crypted_pass, scheme, request->user);

2 1

[dovecot] Mbox spool; dovecot rewriting and rewriting and rewriting
by Ask Bjoern Hansen 08 Apr '03

08 Apr '03

Hi, jaldhar recommended dovecot to me - http://www.askbjoernhansen.com/archives/2003/04/07/000286.html ... and so far it seems much nicer than the other imapds. yay. I use the OS X Mail.app client. I tested it with a test account with no problems, but trying to use it with my usual mail folders (~1.3GB; 120MB in the inbox) it's not working at all. It seems like dovecot keeps copying the full inbox into a temp file in mail/.imap/INBOX. It did it at least 10 times while I was watching without any noticable progress doing anything at all in Mail.app. I am running FreeBSD on an ancient box with 384MB ram (but nice SCSI drives). I tried stopping new mail deliveries to the inbox while I testing, but it didn't seem to make a difference. - ask -- ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();

2 4

[dovecot] Why can't hierarchy sep be changed?
by Timo Sirainen 08 Apr '03

08 Apr '03

>From: Charlie Brady <charlieb(a)e-smith.com> There's something wrong with manually accepting posts from non-subscribed addresses now, they're just left to queue directory for some reason.. Please try to keep the From-address the same as the subscribed one. > >From maildir-storage.c: > > ... > '.', /* hierarchy_sep - can't be changed */ > ... > > Why can't it be changed? Is this just for courier compatibility, or is > there a deeper reason why it can't be changed? Actually I'm going to change it to '/' to allow folders such as shared/timo.sirainen/mailbox. The directory names themselves will still contain '.' separator to stay compatible with Courier's Maildir++ format. So even though new IMAP separator will be '/', '.' still can't be used in mailbox names.

2 2