- dovecot - dovecot.org

[dovecot] Problems with it
by SvR Marty 16 Sep '02

16 Sep '02

i've install it, used the example config and started tryed to access my mailbox via Outlook Express here's the syslog: Sep 14 22:42:17 p133 imap-login: Logged in. [192.168.1.8] Sep 15 00:42:17 p133 imap(svrmarty): MAIL environment missing and autodetection failed (home /home/svrmarty) Sep 15 00:42:17 p133 imap-master: child 20960 (imap) returned error 98 Sep 14 22:42:19 p133 imap-login: Logged in. [192.168.1.8] Sep 15 00:42:19 p133 imap(svrmarty): MAIL environment missing and autodetection failed (home /home/svrmarty) Sep 15 00:42:19 p133 imap-master: child 20961 (imap) returned error 98 it fails and i don't see any message

2 3

[dovecot] v0.97 released
by Timo Sirainen 29 Aug '02

29 Aug '02

This is a major cleanup release. My near future goal is to make it impossible to crash Dovecot no matter what you did. This release also adds support for files larger than 2GB with Linux and Solaris. Also mbox support seems to work quite well now, except EXPUNGE and STORE are still not implemented. The "impossible to crash" should already be quite true, at least when it comes to index files. You can try to corrupt indexes in any way you want, and Dovecot should not crash. There's one exception to this: modifying the files while dovecot is reading them may crash it, this is too difficult to fix as long as shared memory maps are used, and I don't see much point in it anyway. I mostly want dovecot to survive corrupted files, not intentional crashing :) This release is the first I'd almost like to call beta-quality. But not quite. It still lacks testing and several features, but it's very close :) Changelog: v0.97 2002-08-29 Timo Sirainen <tss(a)iki.fi> + Large mails are handled in 256kB blocks, so mail size no longer has hardly any effect on memory usage + 64bit file offsets are used if supported by system. This means Dovecot is fully capable of handling >2G mails in those systems. With 32bit offsets >2G mails may not behave too well, but should not crash either. + I fixed lots of potential integer overflows. This should make us fully crash-free no matter what happens (index file corruption mostly). I didn't verify everything too carefully yet, so more auditing is still needed before we fully reach that goal. + Implemented several missing tasks / optimizations to index handling. It should now stay fast after longer usage periods. + New configuration file options: log_path, log_timestamp, imaps_listen + "Critical errors" are now hidden from users, ie. any error message that is not a direct reply to user error is written into log file and user gets only "Internal error [timestamp]". + Nonblocking SSL handshaking + Lots of code cleanups - Lots of mbox fixes, it seems to be somewhat reliable now - Year in Date-field was parsed wrong - Appending mail to mbox didn't work right - Always verify that mailbox names are valid (especially they shouldn't contain "../")

1 0

[dovecot] vpopmail authentication support
by Eero Volotinen 26 Aug '02

26 Aug '02

is nice feature to get soon if possible? -- Eero

2 1

[dovecot] status update / cvs repository
by Timo Sirainen 22 Aug '02

22 Aug '02

Past few weeks went mostly while rewriting small part of code. It really wouldn't have needed to take that long, but I always got really tired after just looking at that code for a few seconds :) Anyway, now messages are parsed in 256kB blocks (maybe I should make it configurable), so large messages don't eat all memory anymore. Maildir support seems to work with the new code, though I haven't tested it too well yet. mbox is currently broken. If you want to test it, dovecot's CVS is available with rsync. I don't think I'll bother setting up pserver since that CVS has also other sources that aren't public. With rsync you'd do it something like: # initialize new cvs repository (do it just once) cvs -d ~/cvs init # update cvs repository rsync -avz --delete dovecot.procontrol.fi::dovecotcvs ~/cvs/dovecot # checkout the sources from your cvs repository cd ~/src cvs -d ~/cvs checkout dovecot

1 0

[dovecot] SELECT
by marcelo＠carpa.ciagri.usp.br 09 Aug '02

09 Aug '02

Hi, all. Thanks Timo for answering my previous post. It's starting fine now :) I must be doing something wrong again but I can't connect from any imap client. If I telnet to the server I get: $ telnet carpa 11143 Trying 143.107.209.25... Connected to carpa.ciagri.usp.br. Escape character is '^]'. * OK dovecot ready. a001 login marcelo ##### a001 OK Logged in. a002 select INBOX a002 NO Broken INBOX: Permission denied a003 select "" * FLAGS (\Answered \Flagged \Deleted \Seen \Draft \Recent) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)] Flags permitted. * 246 EXISTS * 246 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1028760751] UIDs valid a003 OK [READ-WRITE] Select completed. a004 close a004 OK Close completed. a005 logout * BYE Logging out a005 OK Logout completed. Connection closed by foreign host. "INBOX" seems not be a valid mailbox name to Dovecot but it works with others servers (courier, at least). The server uses Maildirs and runs qmail and courier (by now). Thanks.

2 6

[dovecot] v0.96 released
by Timo Sirainen 08 Aug '02

08 Aug '02

This release was actually tested with reading my inbox (500+ messages, mbox, Solaris 8) using Outlook and Evolution v0.96 2002-08-08 Timo Sirainen <tss(a)iki.fi> * Changed to LGPL v2.1 license + STARTTLS support and optional disabling of plaintext authentication (LOGINDISABLED capability) + Support for custom message flags, each folder can have 26 different. + New configuration file options: imap_listen, max_logging_users, max_imap_processes + You can specify config file location to imap-master with -c <path> + All IMAP processes can now write to specified log file instead of syslog. Either do this by setting IMAP_LOGFILE environment, or give -l <path> parameter to imap-master. + Some cleanups to remove warnings with BSDs + Changed all %s .. strerror(errno) -> %m + Rewritten memory pool code - imap-master didn't close all the fds for executed processes - iobuffer code was buggy and caused the connection to terminate sometimes - make install overwrote the existing dovecot.conf file, so it's now named as dovecot-example.conf

1 0

[dovecot] starting
by marcelo＠carpa.ciagri.usp.br 07 Aug '02

07 Aug '02

Hi. Sorry for the basic question but... how do I start the server? From inetd or in standalone mode (which binary)? Thanks

2 2

[dovecot] mbox support
by Marcus Rueckert 07 Aug '02

07 Aug '02

hi could you explain the following sentence from the readme.txt: "mbox support is available but currently it relies a little bit on good luck, ..." what kind of luck do i need? why do you think the mbox support isnt this reliable? Marcus Rückert -- irssi - the client of the smart and beautiful people

2 1

[dovecot] spam / updates
by Timo Sirainen 06 Aug '02

06 Aug '02

I guess I underestimated the spammers :) This list is subscribers-only now. As for dovecot, I've been cleaning the code and probably will continue with that some time. I was also thinking about moving the authentication code into separate (SASL) library which could then be plugged into other software, such as postfix.

1 0

[dovecot] I have visited DOVECOT.PROCONTROL.FI and noticed that ...
by Vanessa Lintner 06 Aug '02

06 Aug '02

1 0