- dovecot - dovecot.org

[dovecot] a few other problem
by Farkas Levente 07 Apr '03

07 Apr '03

hi, I still has a few other problem with dovecot and mozilla. - when I open mozilla mail I can only see the toplevel folders in the left handside folder list and when I close the imap folder and open it again (click on the arrow left to the imap server in the folder list) mozilla show me all folders and subfolders correctly (but not at the startup). it can be mozilla's bug, but this was worked when I use courier?! - when I'd like to sort the messages by thread than the thread is usualy ok, but I'd like to see the the different threads sorted by date (as it was while using couirer or cyrus) but now it seems to me random:-(( it's very anoying. my be it's mozilla fault again, but may be mozilla use server side thread support. - in OE6 when we only select headers only sometime some message "disappear"! which means we see in OE6 a red line over the message (as it would be deleted), but no one delete it (yes I know you don't belive me, I also don't belive our users, but once I saw it). just click on it to see the message and inmediately become as deleted. while when I look at in the server the file is still there and _not_ deleted. and OE6 show "the message already removed from the server". - what about the ssl (imaps) problem? yours. -- Levente "Si vis pacem para bellum!"

2 1

[dovecot] Re: NFS mounted IMAP dirs
by Maikel Verheijen 06 Apr '03

06 Apr '03

Hi Timo, > On Sun, 2003-03-30 at 23:23, Maikel Verheijen wrote: > > While reading through the dovecot documentation, I read > that I could > > do without indexes (well: use memory indexes), > > Currently that's not really good idea, since message UIDs > aren't then stored permanently. In CVS there's support for > this with mbox format, and I've also been writing support for > Courier-like uidlist-file, but that's still not really working. Well: I am working with Maildir mailstores, so I guess I need to have a uidlist kinda file then? Sorry it wasn't clear in my post that I am using Maildir style mailboxes... But I figured maildir was better than Mbox over nfs... > > My problem is now that dovecot writes it's subscriptions to the > > mailstore. Since I want as little difference between my > frondends as > > possible, (and as static as possible), I would love to see dovecot > > handle subscriptions in a database, or perhaps a nfs-safe file. > > Database? SQL? Another problem is also .customflags file > which isn't NFS-safe. With mbox it's not really required, but > with Maildir it is if you want custom message flags. It > wouldn't be too difficult to change the code to use dotlock > files with these files anyway, I've been going to make it > configurable. My current setup is with postgresql and Maildir. So in a way, a lot of info COULD come from my database, if it isn't safe enough via nfs. Can you make all file locking configurable? Or will you do it on a "per-type" basis? (eg: mailbox locking, index locking, flag-file locking, etc). regards, Maikel Verheijen.

2 2

[dovecot] maildir_copy_with_hardlinks doesn't work
by Kimura Fuyuki 05 Apr '03

05 Apr '03

On my box maildir_copy_with_hardlinks=yes causes the following IMAP error: Some of the requested messages no longer exist. A possible fix follows. --- src/lib-storage/index/maildir/maildir-copy.c 19 Feb 2003 21:32:21 -0000 1.21 +++ src/lib-storage/index/maildir/maildir-copy.c 5 Apr 2003 09:23:34 -0000 @@ -113,7 +113,7 @@ ret2 = index_messageset_deinit(ctx); if (ret2 < 0) ret = -1; - else { + else if (ret2 == 0) { mail_storage_set_error(src->box.storage, "Some of the requested messages no longer exist."); ret = -1; -- fuyuki

1 0

[dovecot] Re: Question about the password field in a postgres ql database
by Maikel Verheijen 04 Apr '03

04 Apr '03

> Works fine with me.. Only thing I can think of is that it's > some stupid > configuration mistake, like not uncommenting the line :) Hi Timo, I just (double) checked my config files, and it LOOKS ok. My dovecot is from cvs, updated yesterday, and running on Redhat 7.3 (if that matters). Here is my dovecot-pgsql.conf: --8<-- # # Postgress connect string. Similar to PHP connect = host=A.B.C.D dbname=maildb user=mailuser password=****** password_query = SELECT password FROM aliases WHERE alias = '%u' AND password != '' AND locked='f'; user_query = SELECT maildir as home, 100 as uid,498 as gid FROM aliases where alias = '%u'; #default_pass_scheme = PLAIN #default_pass_scheme = PLAIN-MD5 default_pass_scheme = CRYPT --8<-- My NON-working DB entry is: --8<-- maildb-> default_pass_scheme = CRYPT maildb-> select * from aliases where alias = 'marc(a)test.com'; ERROR: parser: parse error at or near "#" maildb=> ; maildb=> select * from aliases where alias = 'marc(a)test.com'; alias | maildir | password | locked ---------------+------------------------+----------------------------------- -+-------- marc(a)test.com | test.com/marc/Maildir/ | $1$JJN5H82p$yKs5jnb/csQVYsZZ/4WFS0 | f (1 row) --8<-- and the one that IS working: --8<-- maildb=> select * from aliases where alias = 'maikel(a)test.com'; alias | maildir | password | locked -----------------+--------------------------+------------------------------- ------------+-------- maikel(a)test.com | test.com/maikel/Maildir/ | {CRYPT}$1$JJN5H82p$yKs5jnb/csQVYsZZ/4WFS0 | f (1 row) --8<-- Both strings are crypted versions of 'qwerty' Thank you, Maikel Verheijen

3 2

[dovecot] INBOX at /var in maildir storage format
by Sebastian Pachuta 03 Apr '03

03 Apr '03

Hi I'm trying to figure out how to set default_mail_env to support such config: INBOX is in '/var/mail/%u/' (note last slash at the end, %u is an folder with new/tmp/cur subdirs - standard maildir structure). Other imap folders are stored as files (in mbox format) in direcotry '%h/Mail/'. Please advise.

3 4

[dovecot] Question about the password field in a postgresql database
by Maikel Verheijen 03 Apr '03

03 Apr '03

Hi List, When I try to set the default_pass_scheme in dovecot-pgsql.conf to CRYPT, the dovecot does not recognize my crypted passwords. If I prepend my encrypted passwords with {CRYPT}, dovecot DOES recognize it. (even when I set default_pass_scheme to PLAIN). Is this supposed to work, or am I misinterpreting things here? Thank you! Maikel Verheijen.

2 1

[dovecot] Failure in the presence of too many connections
by Mark E. Mallett 02 Apr '03

02 Apr '03

Had an event today where dovecot refused new connections and would not accept more until restarted, whereupon it worked for a few minutes and locked up again. Looking at the logs it appeared that it had run out of file descriptors. I increased the open files limit and started it again-- which worked but it only pushes off the problem. Does dovecot keep an open file descriptor for every imap or pop3 child? If so, this would argue more towards a tcpserver sort of control. If not, perhaps something is leaking.. -mm- PS: assume you saw recent RFCs 3501 and 3502 ?

3 14

[dovecot] dovecot-0.99.8.1 @ old redhat6.2 box
by Sebastian Pachuta 01 Apr '03

01 Apr '03

Hi I have some odd problem with running dovecot. Program dies with message in maillog: Mar 31 21:04:02 test-box dovecot: Dovecot starting up Mar 31 21:04:04 test-box dovecot: execv(imap-login) failed: Resource temporarily unavailable Mar 31 21:04:04 test-box dovecot: execv(imap-login) failed: Resource temporarily unavailable Mar 31 21:04:04 test-box dovecot: Login process died too early - shutting down Mar 31 21:04:04 test-box dovecot: child 28870 (login) returned error 84 (exec() failed) Mar 31 21:04:04 test-box dovecot: child 28869 (login) returned error 84 (exec() failed) Mar 31 21:04:04 test-box dovecot: execv(imap-login) failed: Resource temporarily unavailable System is redhat6.2 (with all updates), kernel is 2.2.25 (with openwall patch). Under rh7.3 dovecot launches fine.

2 4

[dovecot] NFS mounted IMAP dirs
by Maikel Verheijen 31 Mar '03

31 Mar '03

Hi list, I am trying to build an email system that is using multiple frontends, to a clustered backend using nfs. The backend mounts his filesystems from a central storage, and will be running active-active. While reading through the dovecot documentation, I read that I could do without indexes (well: use memory indexes), and could then be able to run dovecot over NFS. Well: that was until friday, when I was reading a little bit better through nfs.txt. :) My problem is now that dovecot writes it's subscriptions to the mailstore. Since I want as little difference between my frondends as possible, (and as static as possible), I would love to see dovecot handle subscriptions in a database, or perhaps a nfs-safe file. Since I am only a junior programmer (my code is really not far from "Hello world", although I am trying to find some time to teach myself more), I might not be able to be of much assistance to you all in coding stuff, but I am willing to help out where-ever possible. Can anyone help me solve my problem in any way, and how can I contribute as well? Thank you all, Maikel Verheijen.

2 1

[dovecot] FETCH BODY[part]<partial>
by Jesse Peterson 29 Mar '03

29 Mar '03

2003-03-24 12:59 Timo Sirainen <tss(a)iki.fi> This CVS update didn't actually seem to fix the problem. I still get the problem as before, like this capture: 10 UID FETCH 60 BODY.PEEK[]<8192.1915> * 60 FETCH (UID 60 BODY[]<8192> {1915} ) 10 OK Fetch completed. Not quite 1,915 bytes =). Perhaps the "[]" (without a part) is confusing it? But still, it grabs the first chunk correctly. At any rate, any input would be great.

2 6

[dovecot] Dovecot and Quotas
by Mike Machado 26 Mar '03

26 Mar '03

Is there anything that can be done so that when users IMAP to their inbox and have reached their filesystem quota, that they can still DELETE their mail? They can login, but when they go to delete/expunge this is the error I get in syslog. I have tried mail_read_mmaped to yes and no, and same result. Mar 25 14:54:27 penguin1 imap(bob): file_set_size() failed with index data file /home/bob/mail/.imap/INBOX/.imap.index.data: Disk quota exceededMar 25 14:54:27 penguin1 imap(bob): mmap_istream.madvise(): Function not implemented Mar 25 14:54:28 penguin1 last message repeated 65 times When using UW IMAP, sometimes users can delete mail and other times they cannot. I am desperately seeking a solution to have customers be able to delete their own mail when their box is full and not have to call our support center. Any suggestions? Thanks. Debian with kernel 2.4.18. -- Mike Machado mike(a)innercite.com InnerCite Inc. Engineering Director / CTO

5 6

[dovecot] Re: mailbox problem
by Maikel Verheijen 26 Mar '03

26 Mar '03

> Hmm. Unless you're using one UID for everyone, those > directories would have be to be created as root. Also > test.com should be created with different owner as blah and > blah/Maildir. Maybe I could add a new setting for this, but > I'm not sure how to do it without making it too kludgy. There > would have to be separation of where user directory structure > starts, and uid/gid settings what to use for created > directories before them. Something like: I do use 1 UID and 1 GID for everyone. Would that be more simple? > mail_global_dir = /var/mail/t/te/%d > mail_global_uid = root > mail_global_gid = mail > mail_user_dir = /var/mail/t/te/%d/%n > > Would be better if the mail_user_dir didn't have to be set at > all since it's already in mail_default_env, but the user > directory has to be created while still root, and parsing > mail_default_env there is kludgy too. Or maybe: > > mail_global_dir = /var/mail/t/te/%d/%n > > And the last directory would always be assumed to be user > directory. That would prevent creating /var/mail-like shared > directories though, but I guess there's no need to create those.. Maybe there could be a "toggle" to do or don't create the dirs, so you don't need the mail_global_dir setting for "normal" use. My idea was to check the full path to the mailbox, and to create the nonexisting part if necessary. At that point you DO have the full path to the mailbox/maildir, and you can create it, right? Kind regards, Maikel Verheijen.

2 1

[dovecot] inetd/xinetd/tcpserver support
by Timo Sirainen 26 Mar '03

26 Mar '03

I was just thinking how they could be easily supported. This would work, right? : imap stream tcp nowait root /usr/sbin/tcpd /usr/local/libexec/dovecot/imap-login imaps stream tcp nowait root /usr/sbin/tcpd /usr/local/libexec/dovecot/imap-login --ssl imap-login would try to connect to master process using some named socket. If it couldn't, it would create the master process itself. Master process would work as usual (executes auth and imap processes), except it wouldn't be executing login processes. This wouldn't require much code changing, and it would still be using all the same privilege separations as the standalone version so it would be just a secure. Only thing I'm wondering is if any of the TCP wrappers care about the created child processes? The master process would have to stay alive after the connection that created it dies. I guess I'll implement this soon and try if it works.

7 20

[dovecot] mailbox problem
by Maikel Verheijen 26 Mar '03

26 Mar '03

Hi list! Since a week I am testing with dovecot, and I must say, I like it a lot :) Keep up the good work :) I do have one questing regarding dovecot: If I login to a mailbox, and the mailbox does NOT exist, and the parent directory does not exist either, I will get disconnected, and dovecot claims it cannot create the directory. (eg: my user blah(a)test.com has mail directory /var/mail/t/te/test.com/blah/Maildir, and all directories up to /var/mail/t/te/ exist, dovecot does not create the directory test.com/ and on.) Is this by design, or should this be created by dovecot? The problem is solved as soon as the user receives his first email, since my MTA creates the directories... Thank you, Maikel Verheijen

2 1

[dovecot] Help
by Barker, Ron, vpe 26 Mar '03

26 Mar '03

Hi to all, We are a bit of newbes to imap etc, so may be we just not doing it right. Nevertheless, We have compiled dovecot to run under Solaris 8/9 for IPv6 test. We are going crazy. After a successful compilation, the troubles really began. Solaris 9 1. Every´time we reboot- the directory /var/run/dovecot/auth is gone ???? 2. After the dir is created manually, the server starts. However!!! 1. A telnet to host 143 connect to the server fine but no commands are accepted. The server simply returns "bad command" 2. If we try to connect via a e-mail client to the server - we get a login refused - which I suspect is simply the "bad command" error being interpreted as such. We have tried every concivable combination of conf items in the conf file but nothing. Solaris8 Just does not start. Any help apprecialted Ron -- Dr. Ronald Barker Senior Technology Manager Vodafone Group Research & Development - D Vodafone Pilotentwicklung GmbH Chiemgaustrasse 116 81549 Munich Germany Fon: + 49 (89) 95 410-0 Fax: + 49 (89) 95 410-111 mailto:ron.barker@v-pe.de http://www.vodafone-rnd.com <<Barker, Ron, vpe.vcf>>

2 1

[dovecot] dovecot+Solaris 9
by Barker, Ron, vpe 26 Mar '03

26 Mar '03

Does the /dev/urandom issue apply to Solaris 9 as well??? Thanks Ron -- Dr. Ronald Barker Senior Technology Manager Vodafone Group Research & Development - D Vodafone Pilotentwicklung GmbH Chiemgaustrasse 116 81549 Munich Germany Fon: + 49 (89) 95 410-0 Fax: + 49 (89) 95 410-111 mailto:ron.barker@v-pe.de http://www.vodafone-rnd.com <<Barker, Ron, vpe.vcf>>

2 1

[dovecot] a bit better, but...
by Farkas Levente 21 Mar '03

21 Mar '03

this is the correct list the previous was too fast:-( hi, so after test the today version. works: - squirrelmail works ie. it can send mail (even with attachments) and put the sent mail into the sent folder. - mozilla see the right folder list (ie. there is no anoying empty name folder under the folders which has subfolder) and you can subcribe to these folders too. still not works: - mozilla can put sent mail into the imap server's sent folder at the first try, but at the next try (when I compose this mails) it hangs again:-( - in mozilla can't copy/move mails from local folder's sent into any of the imap folders. - in mozilla can't sem messages to Drafts (when I put the save button in the compose window it's hang). - in mozilla there is a folder called INBOX in the subscribe window:-( - in OE6 with large mailbox with large message with the default "all messages" settings in the indox outlook hang (the "headers only" still work). -- Levente "Si vis pacem para bellum!"

1 0

[dovecot] a bit better
by Farkas Levente 21 Mar '03

21 Mar '03

hi, so after test the today version. works: - squirrelmail works ie. it can send mail (even with attachments) and put the sent mail into the sent folder. - mozilla can put sent mail into the imap server's sent folder - mozilla see the right folder list (ie. there is no anoying empty name folder under the folders which has subfolder) and you can subcribe to these folders too. still not works: - in mozilla can't copy/move mails from local folder's sent into any of the imap folders. - in mozilla can't sem messages to Drafts (when I put the save button in the compose window it's hang). - in mozilla there is a folder called INBOX in the subscribe window:-( - in OE6 with large mailbox with large message with the default "all messages" settings in the indox outlook hang (the "headers only" still work). -- Levente "Si vis pacem para bellum!"

1 0

[dovecot] some problem with dovecot
by Farkas Levente 21 Mar '03

21 Mar '03

hi, yesterday we switch to courir to dovecot the whole company. there is good and bad news. the good one that about 200 people use outlook and outlook works fine (after we make some registry hack to delete the INBOX form imap root folder, which was required for courier but not for dovecot). the bad news we try most of the thing before the switch except outself. since the whole it department use linux and mozilla. and almost nothing is working with mozilla: - first of all the folder list can't be subscribed i.e. only the top level folder can be subscribed. can't subscribe to folder which has subfolders and mail inside. all folders with has subfolders shonw as an empty name folder under itself. and you can't select these folders in mozilla's subscribe window (i.e you are not able to check it even it is there). - you can't send any messages!!! since mozilla can't find the Sent folder and can't move the mail after sending!!! even if you reconfigure mozilla to use that "Sent" folder as Sent folder. - you can't see the mails in a folder which has subfolders i.e. it seem there is no message in that folders. - we store mails in ~/Maildir/. dovecot create a ~/Maildir/.INBOX and put the index files of the ~/Maildir/{cur,new,tmp} into that folder but for all other folders it keep the index files in that folder's directory. it's realy confusing. this is _very_ anoying:-((( is there any dirty trick to use mozilla? when thses will be useable? thanks.

6 12

[dovecot] debian 0.99.8.1 packages available
by Jaldhar H. Vyas 20 Mar '03

20 Mar '03

I thought I'd mention it here because a lot of people have been waiting for me on this. My personal situation is getting saner now so I finally was able to package up 0.99.8.1. The package for sid was uploaded last night and should appear in the archive today. A backport for woody is available from http://www.braincells.com/open/ I have not included POP3, LDAP or SASL2 support for now as I didn't want anything to delay the package from entering the archive. That will be the next order of business. The only bug I've seen so far is that when my mbox-format inbox was in /home/jaldhar/mail/inbox dovecot thought it ha 0 messages. It only showed up properly after I moved it back to /var/spool/mail/jaldhar but I suspect this is just a configuration error on my part. -- Jaldhar H. Vyas <jaldhar(a)debian.org> It's a girl! See the pictures - http://www.braincells.com/shailaja/

3 6

[dovecot] more problem with Sent
by Farkas Levente 20 Mar '03

20 Mar '03

hi, ok it's turn out that not just mozilla not able to put the sent mails into the Sent folder but our webmail frontend (SquirrelMail) can't do it. so those who are using the webmail no longer able to use the mail system:-((( -- Levente "Si vis pacem para bellum!"

2 4

[dovecot] Dotlocking doesn't work?
by Jaldhar H. Vyas 19 Mar '03

19 Mar '03

A Debian developer had this to say: > >> Files in the above dir are group mail, and the dir is group mail. However, > > > all binaries in /usr/lib/dovecot are root/root. I have set them all to g+s, > > > and group mail, and now the imap process can lock the INBOX. > > > > > imap should be the only one that needs to be setgid mail. > > Actually, I've looked at the dovecot source code. There is no way having > setgid on the executable will work. The source drops the privledges long > before it tries to do a dotlock. > > This is an upstream problem. > > For now, I've disable dotlock, and use fcntl instead, as that is what exim > uses anyways. Is dotlocking still a work in progress or are we missing something here? -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

3 3

[dovecot] Re: some problem with dovecot
by Marcus Rueckert 19 Mar '03

19 Mar '03

On 2003-03-19 13:52:18 +0100, Farkas Levente wrote: > >mozilla 1.3b + cvs 2003-03-18 is working well here. with the old > >0.99.8.1 i had some problems with attachments. working well after > >updating dovecot. > > we also use 1.3b but with 0.99.8.1, so I waiting for 0.100.... try CVS. maybe it solves your problems. marcus -- irssi - the client of the smart and beautiful people http://www.irssi.de/

1 0

[dovecot] big mail problems..
by Jesse Peterson 19 Mar '03

19 Mar '03

Attachments, large mails & etc. seem to have problems with my installations of dovecot. As we know, Mozilla likes to take it's mail in chunks, and after Mozilla, (or Mail.app, it likes to do this, too) takes its first chunk, it doesn't start getting the rest, even though ethereal tells me that dovecot OK'ed the 10K chunk. 9 UID fetch 4 (UID RFC822.SIZE BODY[]<0.10240>) * 4 FETCH (UID 4 RFC822.SIZE 3958069 BODY[]<0> {3958069} <snip> 9 OK Fetch completed. Nothing gets transfered beyond this point. I think this would be mozilla's fault, but I dont think this would happen with a release, and I dont think Mail.app would have the same problem, too. Thanks for any help, - Jesse

2 2

[dovecot] Configure SSL problem
by Leslie Viljoen 17 Mar '03

17 Mar '03

Hi everyone I have been trying to get Dovecot installed with OpenSSL support, but no matter what I do, when I run Configure, it says "Building with SSL support.........No". I have even tried configure --with-ssl=openssl, to no avail. I have built and installed OpenSSL, and libssl.so and libcrypto.so are in the /lib directory - what more does Dovecot want? I have tried figuring it out from the Configure script itself but it's cryptic and I am no shell script boffin! Thanks for any tips Les ______________________________________ Leslie Viljoen Africa Missions Systems Administrator Cell: 0836186100 Work: 011 6991700 Fax: 011 7945522

4 7

[dovecot] Failed to create storage with data: ::
by Jesse Peterson 17 Mar '03

17 Mar '03

# dovecot.conf: protocols = imaps login = imap login_user = mail default_mail_env = maildir:%h/ auth = default auth_mechanisms = plain auth_userdb = passwd-file /tmp/imap.passwd auth_passdb = passwd-file /tmp/imap.passwd auth_user = mail auth_verbose = yes In the log files I get: Mar 15 23:36:30 pos dovecot: Dovecot starting up Mar 15 23:36:37 pos imap-login: Login: testuser [10.0.66.1] Mar 15 23:36:37 pos imap(testuser): Failed to create storage with data: :: Mar 15 23:36:37 pos dovecot: child 23150 (imap) returned error 89 A typical entry in the imap.passwd: testuser:<md5>[34]:12345:12345::/some/home/directory/testuser:0:: -- Jesse Peterson / jesse(a)pixeltechs.com

2 6

[dovecot] missing files...
by Jesse Peterson 16 Mar '03

16 Mar '03

I'm probably missing something but.. from cvs: gmake[1]: Entering directory `/usr/home/erage/dovecot/cvs/dovecot/src/lib-index' source='mail-lockdir.c' object='mail-lockdir.o' libtool=no \ depfile='.deps/mail-lockdir.Po' tmpdepfile='.deps/mail-lockdir.TPo' \ depmode=gcc /bin/sh ../../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src/lib -I../../src/lib-mail -I../../src/lib-imap -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -c `test -f 'mail-lockdir.c' || echo './'`mail-lockdir.c gcc: ./mail-lockdir.c: No such file or directory gcc: No input files Any ideas?

1 0

[dovecot] dovecot/vpopmail auth problems
by Chris Doyle 15 Mar '03

15 Mar '03

Hello. I am having problems getting dovecot to authenticate correctly through vpopmail. I have used vpopmail for some time, and I understand how it works. vpopmail is using mysql to store it's authentication data. vpopmail's tools can access the user database just fine, and vchkpw is working so far as authentication goes. I took an "strace -f dovecot", in case it can help. It is about 900k, and can be accessed at http://www.narshe.net/~umaro/dovecot.log please help! Thanks Chris Doyle

2 1

[dovecot] Shared Folders?
by Moe Wibble 14 Mar '03

14 Mar '03

Hello everybody (esp. Timo ;)), in an attempt to replace our cyrus imapd with something less bloated I have recently evaluated some of the younger imapd implementations, namely bincimap and also dovecot. Bincimap didn't work properly with mozilla for me, dovecot hasn't failed on any test, yet. Unfornationally, since we have been using cyrus for over 1.5 yrs, we pretty much depend on the "shared folders"-feature. Are there any plans to make shared folders available in dovecot anytime soon? best regards! -- MW

2 3

[dovecot] Starting Dovecot?
by Leslie Viljoen 13 Mar '03

13 Mar '03

Hello! I have laid SSL aside for the time being, and continued compiling and installing Dovecot. Now I don't know how to start it! I have been through the config file and mostly left things as-is. I have created the dovecot user and group and put only dovecot user in the dovecot group. Then I tried imap-master, as specified in the INSTALL documentation, but there is no such file! Under src/master, "dovecot" gets built. I tried running this, and /var/log/messages says "dovecot starting", but this process seems to just end. If I run it twice very quickly, I get told that port 143 is busy - so it seems that it is starting up, but only staying up for a very short while. Messages gives no more clues as to why the server quits. Any ideas? Les PS: I am trying dovecot 0.99.8.1. ______________________________________ Leslie Viljoen Africa Missions Systems Administrator Cell: 0836186100 Work: 011 6991700 Fax: 011 7945522

2 1

[dovecot] Sorry (Starting Dovecot)
by Leslie Viljoen 13 Mar '03

13 Mar '03

Sorry, I didn't check all my logs. PAM password DB was not found - it was in syslog. Les ______________________________________ Leslie Viljoen Africa Missions Systems Administrator Cell: 0836186100 Work: 011 6991700 Fax: 011 7945522

1 0

[dovecot] SMTP options
by Jesse Peterson 13 Mar '03

13 Mar '03

I realize this is not an SMTP discussion list, but... here goes: This is my situation. We have mobile users that need a secure (SSL) SMTP+auth gateway that simply forwards rfc822's to our real MTA. All it would have to do is accept SSL connections, authenticate the user, accept his message, then send that to the MTA. Anybody know of a very minimal software package that can do this? -- Jesse Peterson / jesse(a)pixeltechs.com

2 1

[dovecot] 0.99.8.1 out
by Timo Sirainen 11 Mar '03

11 Mar '03

Nothing but bugfixes from CVS: * src/lib-storage/index/mbox/mbox-list.c: mbox: LIST "" invalid-directory/% doesn't anymore give internal error * src/lib-storage/index/index-fetch.c: FETCH: \Seen flag updating didn't work (eg. FETCH BODY[]). * src/lib-imap/imap-parser.c: Literal parser broke if \r\n wasn't in buffer at the time '}' was parsed. * src/lib-mail/message-address.c: message_address_write() didn't work. * src/lib-mail/message-address.c: message_address_parse(): allow using data_stack_pool (above two fix SEARCH FROM, TO, CC, BCC crashing) * src/lib-storage/index/index-save.c: Don't crash if something tries to write 0 bytes in headers while saving the message. This happened sometimes with mbox. * src/auth/master-connection.c: Don't crash if auth request wasn't found. * src/lib/failures.c: Handle /dev/stderr directly instead of open()ing. * src/lib-imap/imap-quote.c: Use literals for strings containing '"' and '\' characters too. This wasn't done at all before so FETCH ENVELOPE, BODY and BODYSTRUCTURE could have returned pretty broken results. * src/lib-storage/index/mbox/mbox-storage.c: Selecting INBOX didn't use index files if full_filesystem_access was yes. * src/auth/db-ldap.c: Setting user_global_uid or user_global_gid crashed. * src/lib/safe-mkdir.c: safe_mkdir(): usage fchmod() and fchown(). chmod() wasn't really safe and lchown() wasn't portable. * src/auth/mech-plain.c: Invalid PLAIN auth request crashed auth process. * src/master/main.c: [::] address wasn't treated exactly as "ipv6 any", but looks like gethostbyname() worked with it. * doc/nfs.txt: updated * doc/index.txt: update

1 0

[dovecot] Apple's Mail.app
by Scott A.McIntyre 10 Mar '03

10 Mar '03

Hi, I solved the OSX Authentication issue; I'm now reliably able to get authenticated using the Password Server with PAM with: # login: auth account password session auth required pam_nologin.so auth sufficient pam_securityserver.so auth sufficient pam_unix.so auth required pam_deny.so account required pam_permit.so password required pam_deny.so session required pam_permit.so As the /etc/pam.d/imap Anyway -- new problem. With Apple's Mail.app and how it wants to download messages into it's cache, I've found that there's a problematic interaction between Dovecot and Mail.app -- but pinning down exactly what and where is proving to be a hassle. I was running Courier-Imap with Mail.app, and that worked without incident (however, the courier-imap server was on Linux, not OSX Server, that will not work (yet) with osx-server). If I use Entourage and Dovecot, it works fine. The primary symptom is that as it downloads messages Mail.app just hangs; no response, the session just freezes. Usually it's when the status bar is saying something akin to "Caching 9 of 506" at which point it stops. The number varies, but it's always in the first couple of dozen. Messages are small, so it's not that it's hanging on a large mail download. I eventually have to forcibly kill Mail.app. The log says nothing of use: dovecot: Mar 07 17:31:23 Info: Dovecot starting up imap-login: Mar 07 16:32:50 Info: Login: scott [194.109.29.21] imap-login: Mar 07 16:33:46 Info: Login: scott [194.109.29.21] imap-login: Mar 07 16:35:38 Info: Login: scott [194.109.29.21] But perhaps there's a more verbose option somewhere. Thoughts? Scott

4 4

[dovecot] IMAP Folder paths
by Juergen Kahnert 07 Mar '03

07 Mar '03

Hello, we like to use dovecot, but our old imapd used to store the paths of the folder in the file ~/.mailboxlist. This file contains something like this: mail/read mail/dovecot .netscape/imap/mailbox .Mail/foo Each line with a path to one mbox folder. And please pay attention that there is no path to the inbox, because this is stored on the server... Is there a way to use this files with dovecot? It would be a real pain to change this for a few thousand user... Do you see a chance of using such a file? Or is it already possible and I'd overlooked it? Or is it easy / hard to implement? kind regards, Jürgen Kahnert

5 6

[dovecot] vpopmail auth failure
by Oskar Eyb 07 Mar '03

07 Mar '03

hello! when is try to use IMP with dovecot and vpopmail i receive the following error-msg: dovecot-auth: Mar 06 20:43:24 Info: vpopmail(test@$DOMAIN): unknown user But this user exists! Where i can search for the mistake? Greets, Oskar

2 3

[dovecot] OSX & Authentication
by Scott A.McIntyre 07 Mar '03

07 Mar '03

Hi, Taking a stab at getting OSX Server 10.2.4 running Dovecot -- with a minor tweak of replacing lchown() with chown() in the src/lib/sakfe-mkdir.c, it compiled and installed without any problems. However, oddness in authentication. It works once, but only once. I'm trying to use pam and have the following: auth required pam_securityserver.so auth sufficient pam_unix.so account required pam_unix.so In the dovecot.conf I have (amongst other things): auth_userdb = passwd auth_passdb = pam I start up dovecot and do: Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK dovecot ready. . login scott pass . OK Logged in. . logout * BYE Logging out . OK Logout completed. No problem. However, try it again and: Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK dovecot ready. . login scott pass . NO Authentication failed. . logout * BYE Logging out . OK Logout completed. Perhaps there's a better way to get dovecot playing under osx; I'd tried a number of ways of using pam, but perhaps there's a magic other option I've not got working yet. I do run the password server and my account name is using that as per the Workgroup Manager's settings (as opposed to Basic)... Any thoughts appreciated! Scott

2 2

[dovecot] ldap support
by Farkas Levente 06 Mar '03

06 Mar '03

hi, it seem to me that dovecot support only v2 ldap protocol but openldap2.1 support only v3 (or you can enable v2 in the conf file, but it seems they wouldn't like to support it in the future). will dovecot support v3 ldap protocal? thanks. -- Levente "Si vis pacem para bellum!"

3 4

[dovecot] problem with COPY?
by JP 05 Mar '03

05 Mar '03

hi all, I've been trying to use dovecot (from cvs 03.mar.2003, linux 2.2.20, gcc 2.96, openssl 0.9.7a) as an replacement for uw-imap, and it seems to be doing its job, except for one thing: I have my mua (sylpheed-claws from cvs) set up so that it will sort message into certain(imap) directories. so when I check the mail in the INBOX, new mails will be processed automatically and, for example spamcop related emails are moved to their own 'folder'. imap session below. [STARTTLS and LOGIN stuff not included... no errors whatsoever there.] [18:06:39] IMAP4< 5 OK Logged in. [18:06:39] IMAP4> 6 SELECT INBOX [18:06:40] IMAP4< * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) [18:06:40] IMAP4< * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. [18:06:40] IMAP4< * 49 EXISTS [18:06:40] IMAP4< * 3 RECENT [18:06:40] IMAP4< * OK [UNSEEN 47] First unseen. [18:06:40] IMAP4< * OK [UIDVALIDITY 1046109663] UIDs valid [18:06:40] IMAP4< * OK [UIDNEXT 64] Predicted next UID [18:06:40] IMAP4< 6 OK [READ-WRITE] Select completed. [18:06:40] IMAP4> 7 UID SEARCH UID 1:* [18:06:40] IMAP4< * SEARCH 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 49 52 55 56 57 58 61 62 63 [18:06:40] IMAP4< 7 OK Search completed. [18:06:40] IMAP4> 8 STATUS INBOX (MESSAGES RECENT UIDNEXT UIDVALIDITY UNSEEN) [18:06:40] IMAP4< * STATUS "INBOX" (MESSAGES 49 RECENT 3 UIDNEXT 64 UIDVALIDITY 1046109663 UNSEEN 3) [18:06:40] IMAP4< 8 OK Status completed. [18:06:40] IMAP4> 9 UID FETCH 61:63 (UID FLAGS RFC822.SIZE BODY.PEEK[HEADER.FIELDS (Date From To Cc Newsgroups Subject Message-Id References In-Reply-To Content-Type Seen Status X-Status From)]) [18:06:40] IMAP4< * 47 FETCH (UID 61 FLAGS (\Recent) RFC822.SIZE 3111 BODY[HEADER.FIELDS (DATE FROM TO CC NEWSGROUPS SUBJECT MESSAGE-ID REFERENCES IN-REPLY-TO CONTENT-TYPE SEEN STATUS X-STATUS FROM)] {322} [18:06:40] IMAP4< * 48 FETCH (UID 62 FLAGS (\Recent) RFC822.SIZE 3111 BODY[HEADER.FIELDS (DATE FROM TO CC NEWSGROUPS SUBJECT MESSAGE-ID REFERENCES IN-REPLY-TO CONTENT-TYPE SEEN STATUS X-STATUS FROM)] {322} [18:06:40] IMAP4< * 49 FETCH (UID 63 FLAGS (\Recent) RFC822.SIZE 3109 BODY[HEADER.FIELDS (DATE FROM TO CC NEWSGROUPS SUBJECT MESSAGE-ID REFERENCES IN-REPLY-TO CONTENT-TYPE SEEN STATUS X-STATUS FROM)] {322} [18:06:40] IMAP4< 9 OK Fetch completed. [18:06:40] IMAP4> 10 STATUS Spamcop (MESSAGES RECENT UIDNEXT UIDVALIDITY UNSEEN) [18:06:40] IMAP4< * STATUS "Spamcop" (MESSAGES 14 RECENT 0 UIDNEXT 51 UIDVALIDITY 1046109859 UNSEEN 0) [18:06:40] IMAP4< 10 OK Status completed. [18:06:40] IMAP4> 11 UID COPY 61 Spamcop now after this, the conenction goes unresponsive and the following appears in the server log: Mar 4 18:06:42 btp212 imap(jp): file index-save.c: line 61 (write_with_lf): assertion failed:(size > 0 && size <= SSIZE_T_MAX) Mar 4 18:06:42 btp212 dovecot: child 6022 (imap) killed with signal 6 any ideas on what might be causing this? dovecot/mua/some else? regards, JP

2 2

[dovecot] Torture tests
by Ian R. Justman 04 Mar '03

04 Mar '03

Hi, all. I've been so impressed with Dovecot, I'm in the process of moving my mail over to it. In fact, one of my mailboxes got SO huge, it'll likely literally take more than a day to move it all over (in excess of 19,000 mails, about 140 megabytes). So far, the IMAP server shows absolutely no sign of crapping out yet. It should also be noted that I'm moving all this mail out of a Cyrus mailstore into an mbox folder on the same server using Pine. And at work, for my work mail, I recently installed Dovecot 0.99.8, using the POP2 port so I can have test it out while not disturbing my coworkers' ability to retrieve mail. So far, I have yet to see anything bad happen. My IMAP test is taking place under Debian GNU/Linux Woody and my POP3 test under FreeBSD 4.7-STABLE. Though any suggestions in what to keep an eye out for in either case? --Ian.

2 1

[dovecot] pine/dovecot issues
by David E. Storey 04 Mar '03

04 Mar '03

Folks, I'm running into some issues with pine and dovecot. (dovecot is running mbox for now... plan to switch to maildir soon.) At first I thought it was a funky issue with the way I was using pine to access mailboxes. (I use rsh to invoke imap as pre-authenticated so when I switch to maildirs, I don't have to worry about pine being patched to support it.) But after switching over to using authenticated IMAP over port 143, it still had issues. I'm getting messages like: Junk in start of group Not an Address Junk at end of envelope Unknown Message property Thus far, it seems to only occur in pine. (Squirrelmail and evolution appear to be fine) Is it the client? Is it dovecot? is it easily fixable? It feels like some sort of escaping issue or parsing issue or something. I just don't know enough about IMAP to determine exactly what it is. I'm using dovecot v0.99.8, MAIL=mbox:%h/Mail/:INBOX=%h/.mailbox I've just converted off of wu-imap in hopes of someday migrating to maildirs on that box. (anyone know of a good mbox to maildir conversion tool? I used to have on that worked fine, but I've since found a ton that don't work well for me at all. I have about a gig of email to backup and convert) d!

3 4

[dovecot] ldap config
by Stefan Sels 03 Mar '03

03 Mar '03

Hi, how do I setup the config to use an ldap server for authentification ? I tried : auth_userdb = ldap:/usr/local/dovecot/etc/dovecot-ldap.conf auth_userdb = ldap:/usr/local/dovecot/etc/ auth_userdb = usr/local/dovecot/etc/dovecot-ldap.conf however I got an error. What is the correct syntax for the ldap config ? Regards, Stefan Sels

2 1

[dovecot] patch for src/auth/db-ldap.c
by Alex Howansky 01 Mar '03

01 Mar '03

*** src/auth/db-ldap.c.orig Sat Mar 1 00:20:10 2003 --- src/auth/db-ldap.c Sat Mar 1 00:20:31 2003 *************** *** 35,42 **** DEF(SET_STR, pass_attrs), DEF(SET_STR, pass_filter), DEF(SET_STR, default_pass_scheme), ! DEF(SET_STR, user_global_uid), ! DEF(SET_STR, user_global_gid) }; struct ldap_settings default_ldap_settings = { --- 35,42 ---- DEF(SET_STR, pass_attrs), DEF(SET_STR, pass_filter), DEF(SET_STR, default_pass_scheme), ! DEF(SET_INT, user_global_uid), ! DEF(SET_INT, user_global_gid) }; struct ldap_settings default_ldap_settings = { -- Alex Howansky Wankwood Associates http://www.wankwood.com/

1 0

[dovecot] Re: zlib support
by Ian R. Justman 27 Feb '03

27 Feb '03

Timo Sirainen wrote: > Yes, it's been in todo for some time now. mbox support would likely be > read-only, read-write would require recreating the whole .gz file on > updates. Actually, I wouldn't mind seeing something like this so I can compress up my old mail and perhaps store them on CD, for example. I tend to archive mailing list traffic by month (which I store in mbox format), so past months tend to not change much, if at all. :) While not an absolute necessity, it'd be nice to have. --Ian.

1 0

[dovecot] zlib support
by seth vidal 27 Feb '03

27 Feb '03

Hi, Silly idea, Ever considered zlib support so the imap server could read through gzipped mbox files or gzipped maildir entries? -sv

2 1

[dovecot] pop3: last, and auth plain
by Mark E. Mallett 27 Feb '03

27 Feb '03

Hi- A couple of comments regarding the POP3 server (I realize the POP3 server is probably low priority though..) One problem is that the "LAST" command is not supported. Some mail clients end up downloading all messages every time because of this (or so I'm told). The biggest source of these remarks is people using the yahoo webmail front end. I wonder if this could be added? Also, under BSD/OS, the "auth plain" mechanism doesn't work. Perusing the mailing list archives, I see that the symptoms appear just like those that were reported earlier for another BSD system. I'm curious as to whether there has been any progress on that front? Yours, -mm-

2 4

[dovecot] 0.99.8 released
by Timo Sirainen 25 Feb '03

25 Feb '03

Hope I didn't forget anything :) v0.99.8 2003-02-25 Timo Sirainen <tss(a)iki.fi> * NOTE: Configuration file has changed a bit: auth_userinfo was replaced by userdb and passdb. *_port were merged into *_listen. Disabling listening in imaps port is now done by changing protocols setting. * Maildir: .customflags location has changed for INBOX. If you have set any custom flags, move Maildir/.INBOX/.customflags into Maildir/.customflags or they will be lost. * mbox: Autodetect /var/mail/%u and /var/spool/mail/%u as INBOXes if they're found and mail_default_env isn't set. * passwd-file: File format changed a bit. If you used realm or mail fields, you'll have to fix the file. See doc/auth.txt for description of the format. + Fully featured POP3 server included. Disabled by default. + Support for LITERAL+, MULTIAPPEND, UNSELECT, IDLE, CHILDREN and LISTEXT extensions. + LDAP authentication support. + Internal API cleanups made Dovecot faster and take less memory + auth_verbose logs now all authentication failures + Support for Solaris 9 sendfilev() + New setting: mail_full_filesystem_access allows clients to access the whole filesystem by simply giving the path before the mailbox name (eg. SELECT ~user/mail/box, LIST "" /tmp/%). While this allows users to share mailboxes, it's not recommended since Dovecot's index files can't be safely shared. + New setting: client_workarounds. + Dynamically loadable authentication modules. Binary package builders should consider using it for at least LDAP. + mbox: Content-Length is saved now to each saved message, so it's now safe to have lines beginning with "From ". + mbox: mail_read_mmaped = no works with it now + Indexes can be kept in memory by adding :INDEX=MEMORY to MAIL environment. There's not much point to do this now though, since the UIDs won't be saved. - COPY now behaves as RFC2060 says: "If the COPY command is unsuccessful for any reason, server implementations MUST restore the destination mailbox to its state before the COPY attempt." - LIST and LSUB rewrite, should fix several bugs in them - maildir_copy_with_hardlinks = yes was broken. - mboxes in subfolders weren't selectable. - STORE didn't accept multiple flags without () around them - PLAIN SASL-authentication was a bit broken. - IMAP dates were parsed a few hours wrong - STATUS command removed \Recent flags from messages - Several bugfixes to SEARCH command, especially related to multiple search conditions - If auth/login process died unexpectedly at startup, the exit status or killing signal wasn't logged. - mbox parsing might have crashed sometimes - mbox: when saving mails, internal headers were allowed in input, sometimes causing problems (eg. duplicate headers) when appending and copying messages - mbox: X-Keywords headers were duplicated - Some small fixes to how messages are saved to Maildir - Next command after STARTTLS was ignored which left the connection stuck sometimes - Dovecot was pretty much broken with FreeBSD

1 0

[dovecot] Re: Configuration file format changes
by Timo Sirainen 25 Feb '03

25 Feb '03

On Tue, 2003-02-25 at 02:56, Brad Figg wrote: > Just my $.02 (and that's probably overcharging). Anytime I need > a config file I use XML and an open source parser. I hate XML config files. Not going to happen. Ever. :) I think they're difficult to read with standard text editor. Even more difficult to modify. And creating read-only parser for just about any config file format doesn't take hardly any time. External XML libraries would also annoy people.

2 1

[dovecot] Configuration file format changes
by Timo Sirainen 25 Feb '03

25 Feb '03

After tomorrow's 0.99.8 release I think it's time for a new config file format. It could be made backwards compatibile with the old format, but there would be new tree-like categories. I was thinking something like this: # global settings protocols = imap # "foo.server.org" is just descriptive name # settings inside server { .. } will override global ones. # groups (namespace, login settings, auth settings) aren't replaced # unless same name is used. server foo.server.org { imap_listen = 1.2.3.4 ssl_cert_file = /etc/ssl/certs/foo.cer # default namespace (no name) namespace { type = private mail = mbox:~/mail } # Have to quote so '#' won't be thought out as comment. # I think quoting should work everywhere actually.. namespace "#maildir" { type = private inbox = yes # this namespace contains INBOX mail = Maildir:~/Maildir } # override global auth default auth default { auth_mechanisms = plain digest-md5 auth_realms = foo.server.org auth_userdb = ldap /etc/dovecot-ldap.conf auth_passdb = ldap /etc/dovecot-ldap.conf } } server bar.server.org { imap_listen = 1.2.3.5 ssl_cert_file = /etc/ssl/certs/bar.cer namespace { type = private #mail = #autodetect } # shared mailboxes between users # eg. user/timo.sirainen/some-shared-folder namespace user { type = user mail = /home/%u/mail/shared } } server baz.server.org { imap_listen = 1.2.3.6 ssl_disable = yes # Only Courier-like INBOX namespace namespace INBOX { type = private } } # common namespace between all instances namespace shared { type = shared mail = mbox:/var/lists:INDEX=~/mail/.shared/ } auth default { auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam }

1 1

[dovecot] Maildir plus mbox?
by wolfgang 25 Feb '03

25 Feb '03

is it possible with dovecot to have the inbox in Maildir format and additional imap folders in mbox format? regards, wolfgang

2 2

[dovecot] Re: Trouble setting up dovecot
by Tim Snider 24 Feb '03

24 Feb '03

Thanks Timo, turns out I'm more of a rookie at sysconfiguring than I thought, so perhaps this helps identify stuff that a rookie wouldn't already know...<G> On Thu, 2003-02-20 at 19:46, Timo Sirainen wrote: > > > I've not configured up LDAP on my server yet, so it's just plain PAM for > > now. I'm able to login fine with all my other apps, so I doubt it's a > > problem with PAM, but not impossible. I haven't done anything with PAM > > on this machine yet as it's live. I've been testing things out on > > another machine(NON-SMP/RH8), which I'll try tomorrow if I get a > > chance.) > > You have to have it configured in /etc/pam.d/imap. For example: > > auth required pam_unix.so nullok > account required pam_unix.so Thanks this makes more sense than the options you provide in doc/auth.txt, so you may wish to change that. On both RH7.3 and a RH8.0 box here, I don't have pwdfile, it's apparently been replaced by other functionality. > > > each imap-login is waiting at a read(7, > > That's the problem then. It really shouldn't be blocking there. Could > you get the backtrace to see where it's hanging? ie. run as root: > > gdb /usr/local/libexec/dovecot/imap-login <pid of the imap-login> > > and "bt" in it. It's hung up in SSL_CTX_use_PrivateKey() in ssl-proxy-openssl.c, which as you correctly surmised below, is due to a password protected key. I've located and used mkcert.sh. As a note the only docs for doc/mkcert.sh are halfway through the NEWS file and rapidly receeding as you add new releases, (congrats on the fast progress by the way!), however you might consider adding a short note about it to the doc/auth.txt or doc/configuration.txt file for those new to dovecot. > > > I do call fflush() after each write to log. Killing with SIGTERM will do > > > clean exit which may log more things, maybe it's just that? Also killing > > > child processes makes master process log their exits. > > > > I usually note the messages log (watched by a tail -f) show up after I > > kill the dovecot master process.(Kill -9) > > Depends on what the messages are I guess. But if you're kill -9ing the > master process, it's quite likely that the child processes will complain > about losing it. After playing a bit, I think that those messages were due to the kill -9, SIGTERM is nicer. I still end up with little in the way of verbose debugging messages, by my standards. Usually all I see is login and logout messages. Otherwise, I get the occasional lockfile message, which is something that I need to sort out with Exim, and completely on my end. > > dovecot: Feb 20 18:11:51 Info: Dovecot starting up > > imap-login: Dec 31 16:00:00 Fatal: Can't load private key file > > /usr/local/ssl/private/cedarintkey.pem: error:0906406D:PEM > > routines:DEF_CALLBACK:problems getting password > > Err, isn't this the reason why your SSL doesn't work? :) Or was that > just an example? If your private key is crypted with some password, > Dovecot can't use it at least currently.. Correct! Doh! I have been able to use imaps, since I built a non-passworded private key. I was using passworded keys that I'd built for Apache, and would eventually like to have one set of keys that I can reference for each virtual domain. Were you planning on something like the Apache startssl option? I can live with the constraint of one 'connection' key for now. Have you considered allowing each virtual domain to have it's own keys? Kind of difficult as the secure pipe to the server is already in place by the time the login name is seen... Kinda makes it tough for a true virtual presence without explicit assigned IP's. Hmmm, any plans for at least a different keys/identity per IP? If I understand the configuration file for now, it seems to be designed for one cert per machine. Thanks for the help, I've just got to sort out the lockfile differences between Exim and Dovecot and I should then be functional. After that I'll start using LDAP. TJ

2 1

[dovecot] ./autogen.sh
by Jesse Peterson 23 Feb '03

23 Feb '03

CVS update @ Sat Feb 22 15:14:52 PST 2003 When ./autogen.sh is run, I get: src/Makefile.am:5: required directory src/lib-settings does not exist Just thought someone would want to know. - Jesse

2 2

[dovecot] Trouble setting up dovecot
by Tim Snider 21 Feb '03

21 Feb '03

Hi, I'm new to the list but have been trying to get dovecot configured for the past week and a bit. I've gone through the list archives and solved a few of my problems, but most don't seem to be addressed. First off I want to say thanks for starting this project, I've been hoping that someone would start an IMAP/POP server with some flexibility in the way it's configured and provides both packages in one.I've tried setting up Courier once and found it onerous, UW was easier but forces a bunch of assumption that don't suit the way I wanted to configure virtual mail. I'd love to run dovecot, eventually with LDAP and Jamm, and Exim to handle my virtual domains, however I'm running into a fair number of problems and haven't had any luck getting past them. I'm running a RedHat 7.3 SMP server, with iptables for a firewall, so I've got several cards and thus IPs.I started out with dovecot 99.4 but noted that it was missing the LDAP, tried 99.8-test5 and am now working with 99.8-test7, both seem to have the same problems. I'm currently trying to setup a IMAP server on the inside of the firewall, 192.168.2.X. If I use just imap, turn of SSL/TLS I'm fine, and can do plaintext authentication via shadow, but I can't get PAM authentication working. If I turn on SSL(ssl_disable = no), neither the imap or the imaps respond and a netstat -tp shows that no process owns the socket PID/process = '-', often with characters in the Recv-Q. I've tried turning on all the debugging flags for configure on, --with-rawlog --enable-debug --enable-asserts --with-ssl=openssl as well as verbose_proctitle = yes, and auth_verbose = yes, setup logfiles /var/log/dovecot/messages, yet all I get are authorization messages. And I've noted that a number of them only show up after I've killed the dovecot process, so I'm wondering if there needs to be a bit of flushing somewhere? As well I've also tried to run "dovecot -F", with the log files commented out in the .conf file, but get nothing via stderr. I note that when I try the log_timestamp option, the dates sent from imap-login are completely incorrect and don't change, so I don't think the date is being read correctly. Is log_timestamp operational? One thing I'm not clear on is what process to run it under, I've setup a user/group 'dovecot', but does dovecot have to be a member of wheel? I've also noted in earlier versions you had things running via imapd-master, but that now seems to been replaced by "dovecot", is that correct? Is anyone else running dovecot on a SMP system? Any comments or suggestions? I do have development experience, but my Linux/UNIX programming is a bit rusty. I'd love to help make this a rocking product, but need some help getting it dovecot up and running. Any help is appreciated. Thanks, TJ timsn(a)thtree.com http://www.thtree.com/People/TJ/Resume.html

2 1

[dovecot] 0.99.8-test7
by Timo Sirainen 20 Feb '03

20 Feb '03

OK, I really should release 0.99.8 final soon, but not just yet :) Mostly just documentation updates left I think. There's a few recent changes that might have some nasty bugs: - problems with copying messages from mbox to another should be fixed now - LIST and subscription handling rewritten. - "mail_read_mmaped = no" used to corrupt mboxes when expunging messages. It now enabled again by default, and it seems to be working. I did update my backups though :) Dovecot's LDAP support currently requires that it can read the userPassword field of every user. I'm not sure if I should support "authentication binds" that seems to be more standard way to do LDAP authentication. That's just slower, works only with plaintext authentication and makes my code more complex.

2 1

[dovecot] Re: IMAP folder problem
by Kevin Lee 18 Feb '03

18 Feb '03

Hi, I've tried other outlook installs and setting. When I try to copy a folder to the imap account I get... "Can't move the items. The move operation could not be completed. It is possible that the destination server is unavailable or does not support subfolders." And when I try to copy mail to the imap folder (with subscribed folders) I get: "Can't move items. This IMAP command could not be sent to the server before the connection was terminated" I get some corresponding errors in dovecots logs: " imap-master: Feb 18 18:31:41 Error: child 60038 (imap) killed with signal 6 imap((null)): Feb 18 18:33:49 Panic: file cmd-append.c: line 25 (validate_args): assertion failed: ((unsigned int) ret == count) imap-master: Feb 18 18:33:49 Error: child 60042 (imap) killed with signal 6 " related? > On Tue, 2003-02-18 at 18:56, Kevin Lee wrote: > > Hi, > > I have tried multiple dovecot versions (0.99 and CVS) and I keep > > getting the same problem. > > > > I connect to the IMAP server fine using outlook xp, but when I try to create > > folders it creates them and then they just disappear. In the Maildir on the > > IMAP server the folder are there but they don't show up using a client. I > > basically can't do anything with folders, including copying outlook folders > > to the server or create/delete folders. > > Just guessing, but maybe you also have to subscribe to the folders > before they show up in Outlook XP? Also make sure you haven't set > anything to root folder path. I know this to be the case with NS7's mail client. --Ian.

2 1

[dovecot] IMAP folder problem
by Kevin Lee 18 Feb '03

18 Feb '03

Hi, I have tried multiple dovecot versions (0.99 and CVS) and I keep getting the same problem. I connect to the IMAP server fine using outlook xp, but when I try to create folders it creates them and then they just disappear. In the Maildir on the IMAP server the folder are there but they don't show up using a client. I basically can't do anything with folders, including copying outlook folders to the server or create/delete folders. And when I move mail to specific folders using procmail it just gets put back into the inbox again... I'm using freebsd 4.7-RELEASE My config file only adds the following lines... auth = plain auth_methods = plain auth_userinfo = password-file /etc/passwd.imap auth_user = root My password file (/etc/passwd.imp) only consists of kev:XXXXXchangedXX[13]:1001:1001::/home/kev:::: I've just created a folder /home/kev/Maildir where dovecot created the MailDir hierarchies. Any help would be appreciated. Cheers Kev

3 2

[dovecot] mbox vs maildir debate (was re: subject concerning binc imap, even though my original message never touched on it or maildir)
by Ian R. Justman 18 Feb '03

18 Feb '03

Tried sending this message with the original topic On Mon, 17 Feb 2003, Andreas Aardal Hanssen wrote: > Hi, Ian. Cross-posting discussions like this is usually not appreciated > by those who subscribe to both foras, so I'll limit it to the Dovecot > list. Mea culpa. That was an inadvertent mess-up on my part; I did not see the headers, usually going by the list's reply-to headers which are usually there, but not this time. I only "cross-posted" it because the first time, it went to the wrong list (the dovecot list was a CC line). I then remailed it to the correct list. I will be more careful in future. > >Basically, if you open via IMAP using a server with a diffent locking > >Additionally, the number of mbox POP3 servers which Do Not Suck(R) is > >rather low right now. Timo finally introduced an mbox IMAP server which > > This I don't agree with. Most existing POP3 servers are quite ok, and > one POP3 Maildir server that is excellent and bug free since 1998, > qmail-pop3d, is quite a piece of art. You are missing my point. I am not talking about POP3 servers in general. See below. > >Not to mention, quite frankly, most mbox POP3 implementations suck > >pretty badly anyway. :P > > This I do agree with. Don't confuse POP3 servers in general with mbox > POP3 servers. The root, the source of the evil is the storage format > mbox. <Rest of argument re mbox vs. maildir removed> I am specifcally targeting mbox POP3 servers, of which there are several implementations; Qpopper, GNU POP3 Server, Cucipop, ipop3d to name a few. I am NOT speaking to maildir, nor to Cyrus, nor to SQL-enabled products. Solely to mbox. In fact, I even said that stuff that talks to maildir, in addition to Cyrus, offered the one thing for IMAP you could not get with mbox until Dovecot came along; something resembling robust dealing with multiple clients to the same mbox store. Nor am I particularly insterested in debating the merits of any format over mbox, a format I have stated I -KNOW- has annoying technical limitations and issues. While I would imagine other formats may have advantages over mbox, I continue to use mbox simply because of the sheer amount of stored mail I have accumulated on all my machines for the past seven years. My point is that Dovecot seems to be the most robust IMAP server I have come across at coping with mbox stores, especially if I am trying to access the same mailbox with two different clients, whether intentionally or inadvertnetly. My hope is that Dovecot's POP3 server will prove just as robust at dealing with mailboxes that may also be open by an IMAP client. Whether Dovecot, BINC IMAP, or even Courier IMAP (or whichever POP3 server for that matter) are better for maildir or anything else, I will leave that debate to those who actually use them. In the end, I have made a choice. Not necessarily the best one, but I made the choice with the full understanding of what that choice would entail. However, you never know. I may change my mind later. ;) --Ian.

1 0

[dovecot] Re: [bincimap] Re: Re: bincimap
by Ian R. Justman 18 Feb '03

18 Feb '03

On Mon, 17 Feb 2003, Andreas Aardal Hanssen wrote: > >> It even recently included a POP server. What's the reasoning there? > >Someone wanted it so it'd be easy to run both POP3 and IMAP servers > >without having to configure them twice. I don't see any harm in it > >anyway, it took only few hours to write, it's optional and doesn't take > >much space in sources. > > Here's where I would say - there are hundreds of working POP3 servers > around, both in closed and open source, so adding a POP3 server to the > Dovecot project just introduces more lines of code where bugs may appear > ;). Here is what -I- would say: I use mbox on all my servers which I have absolutely no intention of changing despite the issues concerning file locking inherent in the whole mbox format. So please, --NO-- attempts to convince me to go to maildir. My take is that if I am going to use an IMAP server, it would be VERY nice if a POP3 server also came bundled with it. Dovecot's having both IMAP and POP3 servers is great because they will likely use the same file-locking schemes (in fact, probably even share the same locking settings). That way if I inadvertently start up a POP3 session while I am connected via IMAP, if they use identical locking mechanisms, I don't screw up my mailboxes should I inadvertently tell my system that I want to delete the messages from my mailbox. Basically, if you open via IMAP using a server with a diffent locking scheme while your hung POP3 session is still running AND you modify your mailbox, you are screwed. Especially if that mailstore is NFS-shared, which is always a dicey proposition. Additionally, the number of mbox POP3 servers which Do Not Suck(R) is rather low right now. Timo finally introduced an mbox IMAP server which definitely Does Not Suck, notably it allows for multiple clients accessing the same mbox mailstore, something previously only offered by Cyrus and perhaps maildir ("perhaps" only because I do not use maildir). Not to mention, quite frankly, most mbox POP3 implementations suck pretty badly anyway. :P --Ian.

4 13

[dovecot] Re: [bincimap] bincimap
by Timo Sirainen 17 Feb '03

17 Feb '03

On Mon, 2003-02-17 at 11:33, Andreas Aardal Hanssen wrote: > Binc IMAP's approaches are to use a secure programming language with > secure well-known contructs, and with an as-simple-as-possible design, > making it very easy for everyone to grasp how the server works. This will > also help the community find and fix bugs. I kind of agree, but not at the expense of security. I have tried to keep my code clean and ugly-optimization-free anyway. > Here's where I would say - there are hundreds of working POP3 servers > around, both in closed and open source, so adding a POP3 server to the > Dovecot project just introduces more lines of code where bugs may appear > ;). Yes, and I wouldn't have done it if it hadn't been so easy. I don't really encourage people to use it anyway, it's even disabled by default. If it has bugs, it doesn't affect the IMAP side. If people really need to run both IMAP and POP3 servers, it is simpler to use the same configuration for both, especially if the configuration isn't "standard" (eg. LDAP or SQL authentication, mailboxes in special locations, etc). All other major IMAP servers provide their own POP3 servers as well, if you haven't noticed :) > Donald Knuth said in a seminar that I attended that the best way to keep a > program free from bugs it to complete it. Finish off the project, work on > fixing bugs. That's Binc IMAP's philosophy. That's the ideal situation, and even possible if you keep the original goals. But there are IMAP extensions which may require large changes, new mail storage formats and ways to deliver mail into them, clustering, etc.

1 0

[dovecot] Re: bincimap
by Timo Sirainen 17 Feb '03

17 Feb '03

On Tue, Feb 04, 2003 at 02:54:47PM +0100, Andreas Aardal Hanssen wrote: > I can change the words in the FAQ if you feel offended by it, but you'll > have to address points individually. I never made remarks about your > personal code conventions, and I never claimed that my server "focuses on > security" in the extent that Dovecot does. > > If you want to discuss our different designs, please do it seriously, > point for point, and don't just troll around like this. Sorry, I just got a bit disappointed after reading the the web page first. Your lines of code comparisions just seemed to imply that your server does everything that others would but with only a fraction of code. There was also something about Dovecot's design being too complex, so I thought you might have solved those problems more elegantly. When you write something from scratch, I think it's a good idea to design it so that it's superior to existing implementations in at least some ways, not just make a clone with slightly different coding style. If all you wanted was a clone with some changes (and better maintainer), forking the project would be much smaller job. Well, here's some design thoughts: Maildir implementation could be hidden behind a class to access it. That would keep the ugly details hidden from the rest of the code, as well as allow easily implementing other mail storages. Restricting yourself to only plaintext authentication doesn't sound very good plan. Separating the pre-login process from post-login process would probably be a good idea to keep their functionality completely separated. It would also be easier to audit the pre-login code if you knew exactly what there is. After logging in, you could just exec() the post-login process. Don't use sprintf(). > Actually I don't get why you guys CC'd me personally on this. If you have > anything in particular you want to discuss you can post it to the mailing > list. I just thought you'd rather want to see it now than months later in google. I know I would. I didn't think it was really relevant to your mailing list, but if you say so..

2 2

[dovecot] Re: [bincimap] Re: Re: bincimap
by Timo Sirainen 17 Feb '03

17 Feb '03

On Mon, 2003-02-17 at 08:28, Andreas Aardal Hanssen wrote: > I wonder what the motives for the author of Dovecot IMAP was when he > started his project. Lack of securely written code in other servers, although Courier did prove to be quite secure after all. > I wouldn't want to comment on Dovecot's design, since I'm no fan of > trolling. I don't think commenting is trolling, as long as there's truth in it, or at least honest opinions. > The project clearly has different goals than Binc. Dovecot wants > excellent features, indexing and an advanced security promoting design. Implementation security as well. I'm not sure about features. It's more about trying to be fast and light. Indexes make Dovecot comparable to Cyrus in speed, but updating them isn't required so it's still drop-in replacement for UW imapd and Courier. Index files themselves aren't really required either, but there's no option currently to disable them. > It even recently included a POP server. What's the reasoning there? Someone wanted it so it'd be easy to run both POP3 and IMAP servers without having to configure them twice. I don't see any harm in it anyway, it took only few hours to write, it's optional and doesn't take much space in sources.

1 0

[dovecot] Brain bubbles
by Mark Lancaster 17 Feb '03

17 Feb '03

Hi Bit of a newbie to imap servers re: the article on webmonkey! http://hotwired.lycos.com/webmonkey/03/04/index3a_page4.html?tw=backend Been trying to set up SSL support with the latest ver. of dovecote I'm guessing that the following line from STDOUT is the problem. How to fix it is beyond my grasp currently. checking for SSL_read in -lssl... (cached) no Any ideas. ttfn Mark

2 1

[dovecot] 0.99.8-test3
by Timo Sirainen 11 Feb '03

11 Feb '03

It includes full LDAP support now, can anyone test if it really works? It has worked with some of my tests, but I don't know too much about LDAP so I might have missed something important. The authentication problem in test1 and test2 is also fixed now.

2 1

[dovecot] 0.99.8-test2 released
by Timo Sirainen 08 Feb '03

08 Feb '03

Fixes several smaller bugs. Finally works with FreeBSD (tested with 4.7 and 5.0). I think there's still some problems with authentication failing sometimes due to memory/ipc corruption. I haven't seen those today, but I don't think I've fixed that either.. One behaviour change is that if default_mail_env isn't set and mbox format is detected (~/mail dir), /var/mail/user or /var/spool/mail/user is used as INBOX if found.

1 0

[dovecot] About the dovecot package (fwd)
by Jaldhar H. Vyas 07 Feb '03

07 Feb '03

Dear Timo, What do you think of this? Fyi, I've been getting the same thing lately and I'm wondering if gnutls is to blame? (i've had inexlicable SIGSEGVs in other apps before due to it.) Tomorrow I'll try with openssl but I was wondering if you had any other ideas? -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/ ---------- Forwarded message ---------- From: Guille -bisho- <bisho(a)eurielec.etsit.upm.es> To: jaldhar(a)debian.org Date: Mon, 3 Feb 2003 02:08:19 +0100 Subject: About the dovecot package Hello! First of all thanks for maintain such a good imap server. It's trully fast and lightweight!!! I was trying Courier, but it is not very interoperable with others linux tools like procmail and others, and uw-imapd performance was really bad. I only have one problem: If I put a lot of folders to check in mutt the imapd server closes de connection saying in the logs: Jan 31 02:50:25 www imap-login: Login: bisho Jan 31 02:50:44 www imap-master: child 22234 (imap) killed with signal 11 It only happens when mutt is configured with a lot of folders. Maybe covecot loads too much indexes in memory and reachs some limit, but I have readed carefully the conf file and hadn't found anything related. Do you have any thought about that? Thanks a lot again See you -- .,,, Guillermo Pérez -=] 03/02/2003 [=- _' .,,,, - bisho@ ( onirica.com | eurielec.etsit.upm.es ) (v)/ ,'' ( \/ :: "Nuestras mayores tonterias pueden ser muy sabias." :: bisho! ``\\ :: -- Leonardo Da Vinci ::

2 3

[dovecot] Dovecot on FreeBSD
by Karo Salminen 06 Feb '03

06 Feb '03

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I built Dovecot (0.99.5) from Ports on FreeBSD 5.0. The mail client (Kmail) cannot login and it complains that authentication process died. The only thing in the logs is: Feb 2 18:13:01 karo imap-login: Disconnected [client-ip] I tried also passwd authentication method, but its symptoms are the very same. My configure can be found at http://people.jyu.fi/~kaeesalm/dovecot.conf I also tried CVS version in hope of fix and more comprehensive debug messages. The compilation failes when it tries to look for passwd.h even though I set - --disable-passwd and --without-passwd to configure parameters. Could someone fix that. - -- Karo Salminen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+PUX0vt6lNXuj7xcRAp70AJ0R+zhmgF+WBaXaX2V2j+07eVyJRACgh6Ze Pmep2Uy2OnVe/EVuo9O3b80= =eqOO -----END PGP SIGNATURE-----

3 10

[dovecot] bincimap
by Farkas Levente 04 Feb '03

04 Feb '03

hi, what do you tyhink about it? especially the faq comment about dovecot? http://www.bincimap.andreas.hanssen.name/ -- Levente "Si vis pacem para bellum!"

3 3

[dovecot] 0.99.8-test1 released
by Timo Sirainen 04 Feb '03

04 Feb '03

I think all of the reported bugs are again fixed in CVS, so I made a tarball of it. I'd like to hear if there's any problems with it. Here's the most important changes: v0.99.8 2003-02-xx Timo Sirainen <tss(a)iki.fi> * NOTE: Configuration file has changed a bit: auth_userinfo was replaced by userdb and passdb. *_port were merged into *_listen. Disabling listening in imaps port is now done by changing protocols setting. + Fully featured POP3 server included. Disabled by default. + Support for LITERAL+, MULTIAPPEND and UNSELECT extensions. + Internal API cleanups made Dovecot faster and take less memory + auth_verbose logs now all authentication failures + Support for Solaris 9 sendfilev() (not really tested) - COPY now behaves as RFC2060 says: "If the COPY command is unsuccessful for any reason, server implementations MUST restore the destination mailbox to its state before the COPY attempt." - maildir_copy_with_hardlinks = yes was broken. - mboxes in subfolders weren't selectable. - STORE didn't accept multiple flags without () around them - PLAIN SASL-authentication was a bit broken. - IMAP dates were parsed a few hours wrong - If auth/login process died unexpectedly at startup, the exit status or killing signal wasn't logged. - mbox parsing might have crashed sometimes - Next command after STARTTLS was ignored which left the connection stuck sometimes - STATUS command removed \Recent flags from messages - Several bugfixes to SEARCH command, especially related to multiple search conditions

1 0

[dovecot] Recent messages
by Jaime Medrano 03 Feb '03

03 Feb '03

Dovecot seems to manage \Recent messages in a weird way. When a STATUS command is performed in a mailbox, then the \Recent flag of its messages disappear and latter STATUS commands report that there are no recent messagges. I don't know exactly the behavior of the RFC. But other imap servers (UW-imapd, Netscape Messenger...) report the same number of recent messages when two STATUS commands are performed together. -- Jaime.

2 1

[dovecot] Plain auth broken
by Timo Sirainen 03 Feb '03

03 Feb '03

On Fri, 2003-01-17 at 14:15, Timo Sirainen wrote: > On Thu, 2003-01-16 at 03:31, james broermann wrote: > > pine still doesn't want to work. It does detect that the server is using > > plain text passwords. I'll try the sniffer and see what turns up. > > Whops, you're right. I've tested pine only with digest-md5 > authentication before. Looks like my PLAIN authentication isn't working > properly. Normally other clients just use LOGIN command which is > different. Patch is now available at http://dovecot.procontrol.fi/

2 7

[dovecot] cvs down?
by Jesse Peterson 24 Jan '03

24 Jan '03

(Logging in to anonymous(a)dovecot.procontrol.fi) CVS password: cvs [login aborted]: connect to dovecot.procontrol.fi:2401 failed: Connection refused cvs [checkout aborted]: connect to dovecot.procontrol.fi:2401 failed: Connection refused Was the CVS server taken down? -- Jesse Peterson / jesse(a)pixeltechs.com

2 1

[dovecot] Unable to Log in on FreeBSD server?
by Mark 21 Jan '03

21 Jan '03

Hello! I recently compiled dovecot 0.99.7 on a FreeBSD 4.3 server, and have been having problems with logging in and password authentication. a. I can't seem to get it to compile MD5 support -- it only seems to support plain, plain-file, and pam. b. Whenever I try to log in, I always get something along the following lines in /var/log/messages .... Jan 16 17:52:15 akira imap-login: close(master) failed: Bad file descriptor Jan 16 17:55:33 akira imap-auth: Userinfo pam doesn't support DIGEST-MD5 method Jan 16 18:08:28 akira imap-master: Login process died too early - shutting down (I also included one about MD5 in there too! :-)) Basically, the imap-login process is dying every time I try to do a login from a remote machine (I've tried Evolution and Outlook Express ....) I've tried telling it to use port 143 and port 993 (where it correctly generates a warning about a certificate that it can't verify, since i created that certificate with mkcert.sh ) Is there something I haven't configured correctly? The only things I've changed in dovecot.conf are: Any suggestions? Thanks, Marc.

2 5

[dovecot] mbox & Maildir
by james broermann 18 Jan '03

18 Jan '03

Hi, Is it possible for a client to read both mbox and Maildir formats from one server running dovecot? Without changing default_mail_env in dovecot.conf, Maildir folders are working ... they're located in ~/Maildir. No /var/mail/username exists. I have mbox format folders in ~/mail and have been trying to get pine to find them by adding pine folder collections. I always end up back in ~/Maildir, though. Thanks, Jim

2 1

[dovecot] 0.99.7 out
by Timo Sirainen 17 Jan '03

17 Jan '03

This one seems to be actually working. Also rewrote doc/index.txt in case someone is interested.

3 7

[dovecot] 0.99.6 buggy
by Timo Sirainen 14 Jan '03

14 Jan '03

Just a note, the hash table code in it was still buggy. Especially with maildir it could leave the processes to infinite loop. Have to think a bit more how to fix this properly..

1 0

[dovecot] security audit of the code
by seth vidal 14 Jan '03

14 Jan '03

Timo, I know that you're taking an effort to make sure that dovecot is written securely, but I was wondering if you've asked any third party to audit the code yet. I don't have the skills necessary to do this but I bet there is someone out there who does and might be willing to do so. -sv

5 7

[dovecot] 0.99.6 released
by Timo Sirainen 14 Jan '03

14 Jan '03

Several bugfixes since 0.99.6rc3. Here's again the change summary since 0.99.5: v0.99.6 2003-01-13 Timo Sirainen <tss(a)iki.fi> + THREAD=REFERENCES extension support. ORDEREDSUBJECT would be easy to add, but I think it's pretty useless. + SORT is much faster now. + mbox: If ~/mail directory isn't found, create it. + Log login usernames * Some coding style changes (less typedefs) - Mails with nested MIME parts might have caused incorrect BODY and BODYSTRUCTURE fetches and sometimes might have crashed dovecot (assert at imap-bodystructure.c). If client had already successfully done the BODY fetching a couple of times, the bug couldn't happen anymore since Dovecot then began caching the BODY data. So, this mostly happened with new users. - non-UID SEARCH might gave wrong replies in certain conditions. - SORT replied always with UIDs instead of sequences. - If authentication was aborted by client ("*" reply to AUTHENTICATE), the login process crashed later. - STATUS command gave invalid reply for mailboxes with spaces in name - Timezones were parsed wrong with message dates - Digest-MD5: We used "qop-options" instead of "qop", which was incompatible with at least Cyrus SASL. - Realms in passwd-file were buggy - Literals didn't work when logging in - Crashed if it had to wait for mbox lock - With invalid configuration auth and login processes were just dying and master filling log files infinitely. - We didn't work with some 64bit systems

1 0

[dovecot] dovecot-0.99.6rc3 compilation problems on (Open|Free)BSD
by Johan Fredin 13 Jan '03

13 Jan '03

Hi there! Dovecot-0.99.6rc3 barfs at me when I try to compile it on OpenBSD 3.2 or FreeBSD 4.7, both with the same error: [ ..snip.. ] gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src/lib -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -c charset-iconv.c gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src/lib -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -c charset-utf8.c charset-utf8.c:42: storage size of `ascii_translation' isn't known charset-utf8.c:42: storage size of `utf8_translation' isn't known *** Error code 1 Stop in /usr/home/griffin/dovecot-0.99.6rc3/src/lib-charset. *** Error code 1 Stop in /usr/home/griffin/dovecot-0.99.6rc3/src (line 134 of Makefile). *** Error code 1 Stop in /usr/home/griffin/dovecot-0.99.6rc3 (line 202 of Makefile). *** Error code 1 Stop in /usr/home/griffin/dovecot-0.99.6rc3 (line 330 of Makefile). I didn't use any fancy parameters for ./configure. Any config.* files I can post to help? /Regards, Johan

2 3

[dovecot] 0.99.6rc3
by Timo Sirainen 13 Jan '03

13 Jan '03

Well, "release candidate" wasn't really right name for last two versions. Maybe not for this one either, it has a few changes that could potentially break things badly (new hash table code especially). Anyway, seems to work with me. If I don't see any problems with it for a few days it'll be the final. The really great news is that we support threading. A lot of people have not used Dovecot simply because it couldn't be used for webmails. Hmm. What's the next most important feature? .. Better mbox support? Shared folders? Quota? LDAP/MySQL/etc. authentication? Here's the change summary: v0.99.6 2003-01-xx Timo Sirainen <tss(a)iki.fi> + THREAD=REFERENCES extension support. ORDEREDSUBJECT would be easy to add, but I think it's pretty useless. + SORT is much faster now. + mbox: If ~/mail directory isn't found, create it. + Log login usernames * Some coding style changes (less typedefs) - Mails with nested MIME parts might have caused incorrect BODY and BODYSTRUCTURE fetches and sometimes might have crashed dovecot (assert at imap-bodystructure.c). If client had already successfully done the BODY fetching a couple of times, the bug couldn't happen anymore since Dovecot then began caching the BODY data. So, this mostly happened with new users. - non-UID SEARCH might gave wrong replies in certain conditions. - SORT replied always with UIDs instead of sequences. - If authentication was aborted by client ("*" reply to AUTHENTICATE), the login process crashed later. - STATUS command gave invalid reply for mailboxes with spaces in name - Timezones were parsed wrong with message dates - Digest-MD5: We used "qop-options" instead of "qop", which was incompatible with at least Cyrus SASL. - Realms in passwd-file were buggy - Literals didn't work when logging in - Crashed if it had to wait for mbox lock - With invalid configuration auth and login processes were just dying and master filling log files infinitely. - We didn't work with some 64bit systems

2 4

[dovecot] Failed to create storage
by M 10 Jan '03

10 Jan '03

Hi, I'm impressed so far, I tested this before trying to run it on a mail server and it worked find. However on the mail server with the same config I get the following message when I try and authenticate, and it drops the connection. Failed to create storage with data: mbox:/var/mail/martin The test box is running debian unstable and the mail server is running debian stable so I had to recompile and install. I'm failry sure that I got all the permissions right, I feel like I'm missing something obvious, can anyone advise? The file and permissions on the mailbox look right: -rw-rw---- 1 martin mail 14743740 Jan 10 06:29 /var/mail/martin -- Thanks, M

2 2

[dovecot] Re: Thread extension
by Timo Sirainen 10 Jan '03

10 Jan '03

On Fri, 2003-01-10 at 06:00, Jonas Smedegaard wrote: > > Also it looks like I've found a couple of bugs in uw-imap and courier's > > implementation.. > > Something you want to reveal? Well, one was just my misunderstanding of the specs, but another still exists: These should be grouped together, but aren't: Subject: =?iso-8859-1?Q?foo?= Subject: =?iso-8859-1?Q?RE=3A_foo?= UW doesn't seem to handle MIME encoded-words properly. I mentioned this already to Mark Crispin who apparently has a lot to do with UW's code. I didn't look too closely at Courier's output, except it was somewhat different from Dovecot's. Also, Crispin said it was totally broken.

1 0

[dovecot] Thread extension
by Timo Sirainen 10 Jan '03

10 Jan '03

Just figured I'd mention that CVS supports now THREAD extension. I also did a bit of benchmarking using a folder with 4685 mails (evolution mailing list): dovecot+mbox: - 0.59s user 0.01s system 98% cpu 0.608 total - malloc() memory usage 45072 -> 825685 dovecot+maildir: - 0.60s user 0.17s system 98% cpu 0.780 total - malloc() memory usage: 45003 -> 825480 Meaning it takes almost 800kbytes of memory and it's quite fast :) Comparing to other servers then: uw-imap: - 1.11s user 0.27s system 100% cpu 1.376 total - malloc() memory usage: 529408 -> ~4348k courier: - 7.27s user 0.28s system 99% cpu 7.567 total - malloc() memory usage: 181689 -> ~850k cyrus: - 1.403 total (through TCP connection, I couldn't figure out how to start it separately) Whoa, we beat everyone :) Courier uses a bit less memory though, but that's most likely because we allocate it in larger chunks which is faster. I ran the tests several times and picked the best values, although the changes were minimal once they got the messages into OS's cache. Also it looks like I've found a couple of bugs in uw-imap and courier's implementation..

1 0

[dovecot] Re: Logging suggestions?
by Jesse Peterson 09 Jan '03

09 Jan '03

-------- Original Message -------- From: - Wed Jan 08 15:28:42 2003 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00800000 Message-ID: <3E1CB429.3040704(a)attbi.com> Date: Wed, 08 Jan 2003 15:28:41 -0800 From: Jesse Peterson <jpeterson275(a)attbi.com> User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20020901 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Timo Sirainen <tss(a)iki.fi> Subject: Re: [dovecot] Re: Logging suggestions? References: <1042022871.28651.93.camel@hurina> <20030108175006.GB27418(a)dust.uchicago.edu> <20030108181142.GB12010(a)talsever.com> <1042066760.28651.144.camel@hurina> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Timo Sirainen wrote: > > Something like that, yes. I'd like to avoid adding too many (mostly) > useless options though. > Make it customizable! =) Maybe something similar to Apache LogFormat-style or similar? Just a suggestion, -- Jesse Peterson / jesse(a)pixeltechs.com -- Jesse Peterson / jesse(a)pixeltechs.com

1 0

[dovecot] Logging suggestions?
by Timo Sirainen 09 Jan '03

09 Jan '03

Any suggestions how user login/logouts should look like in log files? I was thinking: (connected to imaps port) Login: username [IP 1.2.3.4, imaps, compressed] Logout: username [IP 1.2.3.4, imaps, compressed] [1000/100000 bytes (50%), 00:00:12] Bytes being upload/download and the 50% meaning compression ratio for downloaded bytes, probably not worth it for upload. Or if uncompressed, it'd show the extra space used by SSL/TLS protocol: (using STARTTLS) Login: username [IP 1.2.3.4, TLS] Logout: username [IP 1.2.3.4, TLS] [2020/202000 bytes (101%), 00:00:12] (no SSL) Login: username [IP 1.2.3.4] Logout: username [IP 1.2.3.4] [2000/200000 bytes, 00:00:12] I think the only configuration needed would be if to log login, logout or both.

4 6

[dovecot] Bug#175509: dovecot: init.d script should add some syslog statements on startup/shutdown (fwd)
by Jaldhar H. Vyas 08 Jan '03

08 Jan '03

[Amelia and Timo. As you are both on the dovecot list, I'm replying there to avoid cluttering up your inboxes.] This bug was reported to Debian but I feel it should be fixed upstream. Adding logging in th init script itself would require adding additional dependencies to the package and not be as convenient. ---------- Forwarded message ---------- From: Amelia A Lewis <amyzing(a)talsever.com> It would be nice if the init.d script could add some statements in the system log on startup and shutdown. For postfix, postfix-script (called from the init script) uses: starting the Postfix mail system stopping the Postfix mail system These are useful; one can start the daemon and check that it's initialized (netstat works as well, I suppose, but this is still useful docco). -- Jaldhar H. Vyas <jaldhar(a)debian.org>

2 1

[dovecot] Re: Bug#175507: dovecot: Accidental denial of service via syslog
by Jaldhar H. Vyas 08 Jan '03

08 Jan '03

This bug was reported to Debian but I feel it is an upstream issue. On Sat, 4 Jan 2003, Amelia A Lewis wrote: > If dovecot is misconfigured, such that imap-auth cannot find passwd.imap > (which probably needs to get copied; maybe need more docco in the config > file? This happens if the digest-md5 auth method is uncommented and the > auth_userinfo is set to passwd-file /etc/passwd.imap), imap-auth dies once a > second with error 89, which it reports to imap-master, and both log to > syslog. > > I've got 30,000 line pairs from a ten hour run. I would think that if it > dies more than, say, a thousand times in a single hour, imap-master maybe > ought to consider that there's a serious configuration problem preventing > use, and exit instead of continuing to fill the log. > > Granted, it's a shoot-yourself sort of error. But still ... after a certain > point, the program ought to be able to die *gracefully* if the sysadmin has > shot it, by accident or not. > Personally, I would be even stricter than Amelia is suggesting. If there is a serious configuration error, dovecot should die immediately. -- Jaldhar H. Vyas <jaldhar(a)debian.org>

2 1

[dovecot] Bug reports from Debian BTS
by Jaldhar H. Vyas 08 Jan '03

08 Jan '03

Timo, Are you (or any other interested list readers for that matter) interested in directly receiving bug reports about dovecot sent to Debian? If you are, you can go to http://packages.qa.debian.org/d/dovecot.html and sign up to have notifications sent to you or the list or wherever. Or I can screen them and only send you ones I think are relevant as I'm doing now. -- Jaldhar H. Vyas <jaldhar(a)debian.org> It's a girl! See the pictures - http://www.braincells.com/shailaja/

1 0

[dovecot] 0.99.6rc1 released
by Timo Sirainen 07 Jan '03

07 Jan '03

Again rc, just in case I broke something. Or maybe I should just start creating nightly CVS snapshots. Anyway, fixes the few bugs people have reported lately: - Mails with nested MIME parts might have caused incorrect BODY and BODYSTRUCTURE fetches and sometimes might have crashed dovecot (assert at imap-bodystructure.c). If client had already successfully done the BODY fetching a couple of times, the bug couldn't happen anymore since Dovecot then began caching the BODY data. So, this mostly happened with new users. - If authentication was aborted by client ("*" reply to AUTHENTICATE), the login process crashed later. - Digest-MD5: We used "qop-options" instead of "qop", which was incompatible with at least Cyrus SASL. - We didn't work with some 64bit systems - Realms in passwd-file were buggy * Some coding style changes (less typedefs)

2 2

[dovecot] Assert in imap-bodystructure.c
by Brad Figg 06 Jan '03

06 Jan '03

First let me thank you for my initial newby question about poping from a pop3 server and delivering into my Dovecot maildir folders. Now I'm getting an assertion in imap-bodystructure.c and one of my imap folders is now inaccessable. I think the two are related. Whenever I select the folder from my email client (kmail) I get two log entries in the dovecot log of the format: "imap-master: <date>Error: child <pid> (imap) killed with signal 6" Also in the log are several lines with an assertion failure. I've included a portion of the log below. I am running dovecot 0.99.5. Thanks, Brad ---------------------------------------------------------------------------------------------- imap-master: Jan 06 08:38:44Error: child 22222 (imap) killed with signal 6 imap(brad): Jan 06 08:46:28Panic: file imap-bodystructure.c: line 346 (part_write_body): assertion failed: (part->children->next == NULL) imap-master: Jan 06 08:46:28Error: child 22262 (imap) killed with signal 6 imap(brad): Jan 06 08:53:01Panic: file imap-bodystructure.c: line 346 (part_write_body): assertion failed: (part->children->next == NULL) imap(brad): Jan 06 08:53:01Panic: file imap-bodystructure.c: line 346 (part_write_body): assertion failed: (part->children->next == NULL) imap-master: Jan 06 08:53:01Error: child 22273 (imap) killed with signal 6 imap-master: Jan 06 08:53:01Error: child 22270 (imap) killed with signal 6

2 5

[dovecot] Weird problem on Alpha
by Amelia A.Lewis 06 Jan '03

06 Jan '03

Heyas ... Hope you aren't tired of me already .... I have a very strange problem, I think. Having become happy-happy with dovecot, I decided to install it on another machine that runs on an internal network and provides mailboxes for system monitoring. The setup is, or should be, quite straightforward. TLS is disabled, plaintext is not (I'll change this later, probably; this way is in theory easier to debug). Maildir; the MAIL environment variable is correctly set. Authentication via pam, for real users on the system, auth_user root. Pretty much as-distributed, except for disabling TLS. On attempted login, the client hangs. The following two messages appear in syslog: Jan 5 21:42:43 talifane imap-master: login: received another "not listening" notification Jan 5 21:43:43 talifane imap-login: Disconnected: Inactivity [127.0.0.1] Watching on lo via tcpdump, interesting things happen. If I login with the wrong password, the disconnect is quick (the message in syslog is different, just "Disconnected [127.0.0.1]" from imap-login). The server responds to the a0001 LOGIN command with a0001 NO Authentication failed. That's as expected. If I give the correct password, though, the server never responds. Note that the 'not listening' message appears sixty seconds before the disconnection for inactivity message. In tcpdump, it's clear that the client never gets anything that would give it reason to try another command. So ... have I managed to pull a total bimbo and misconfigure? Or is this a problem with the Alpha platform? I wanted to check before reporting a bug, but this is kinda strange, since it's about the simplest configuration that I can think of. Suggestions (for testing, or for fixing) would be welcome. Is there a way to start the daemon in a particularly verbose mode? In case it's useful, here's what the debian reportbug system generates for dependencies and stuff (0.99.5-1): -- System Information: Debian Release: testing/unstable Architecture: alpha Kernel: Linux talifane 2.4.19 #1 Sat Aug 3 10:33:38 EDT 2002 alpha Locale: LANG=en_US, LC_CTYPE=en_US Versions of packages dovecot depends on: ii libc6.1 2.3.1-9 GNU C Library: Shared libraries an ii libgcrypt1 1.1.10-2 LGPL Crypto library - runtime libr ii libgnutls5 0.6.0-2 GNU TLS library - runtime library ii libpam0g 0.76-9 Pluggable Authentication Modules l ii libtasn1-0 0.1.2-1 Manage ASN.1 structures (runtime) ii openssl 0.9.6g-10 Secure Socket Layer (SSL) binary a ii zlib1g 1:1.1.4-8 compression library - runtime It's specifically a PC164LX/533, 512MB RAM. Thanks for reading. Amy! -- Amelia A. Lewis amyzing {at} talsever.com You like the taste of danger, it shines like sugar on your lips, and you like to stand in the line of fire just to show you can shoot straight from your hip. There must be a 1000 things you would die for; I can hardly think of two. -- Emily Saliers

2 1

[dovecot] wierdness with mailboxes
by David E. Storey 06 Jan '03

06 Jan '03

Mail has always been the bane of my sys-admin life. I've been looking long and hard for a small, C-based, simple IMAP server that worked well with maildirs *and* mboxes and nothing else. wu-imap is so bloated and rife with decrepit, cross-platform, insecure code that I avoid it for any new servers. Courier-imap only supports maildirs but has some wierdnesses that I've come to live with. dovecot promises to be exactly what I'm looking for with just the right footprint and feature-set. =) I was surprised when I tried creating subfolders of mbox's. woohoo! The only problem is that dovecot manages to rename the parent, appending a '.'. So when we have: folder we now have: folder. folder.subfolder Evolution freaks out and thinks it can't store folders in 'folder.' and ends up with two subfolders: null and subfolder, which can contain messages. If I rename the parent folder without the trailing '.', everything works as expected. I'm trying to test some other imap clients now. d!

2 1

[dovecot] Some experiences
by Amelia A.Lewis 06 Jan '03

06 Jan '03

Heyas ... I'm trying to use dovecot to set up a 'closed server' (actually, mixed) sort of environment, for a box to be deployed co-located. I wanted to talk about some of that, and see if some of my experience qualifies as 'bug'. Note that I'm notoriously verbose, so if that bothers you, read no further .... Since it's a more-or-less closed server, I didn't want to use pam (well, I wouldn't mind, for users with shell accounts, but I can't see a way to mix pam and passwd-file ... is there a way to do that?). It turns out that digest-md5 support for clients is, well, not very widespread. I expect this box to be used by various windoze clients, eventually, and while I'm willing to lay down the law a little, I can't find enough digest-md5 support to lay down that law. So, regretfully, I abandoned that plan. This kinda bothers me, since I think TLS/STARTTLS is absolutely the *wrong* solution for mailbox access (or for anything that deals with a store-and-forward transport). I therefore tried md5 passwords in a passwd-file, with STARTTLS enabled. Didn't work. I turned off SSL, and reenabled plain-text, and watched the login go by. Very sniffable, of course. But correct username and password ... failed. There are instructions for creating digest-md5 style secrets in auth.txt, but none for md5 passwords; I used openssl passwd -1 [password] (and cut and paste). It seems odd to me that this didn't work; does that command use a different algorithm than dovecot? Falling back ... since it *shouldn't* matter if the passwords are weak, as long as they're inside TLS (along with the entire rest of the transaction, ugh), I used mkpasswd to generate a standard unix passwd (and cut and paste). This worked. It worked with TLS, and it worked without (as long as I remembered to allow sniffable logins). One more oddity: I originally had a realm in the passwd-file, which also established the mail location and 'home' directory (most of the users can't actually log in and don't have accounts in /etc/passwd, so it's not a real home directory). There was an odd message in syslog, approximately like so (where 'user' represents the username, and 'domain.realm' represents both my domain name and the realm in the passwd-file): imap(user:@omain.realm): Failed to create storage with data: domain.realm Note the missing first letter after user:@ And I don't know what it was trying to do; the maildirs already exist. /etc/dovecot.conf sets the default mail location to /home/users/%n/Maildir (non-shell users are all inside /home/users; shell users have mail there, with symlinks to ~/Maildir); the passwd-file establishes the location of the INBOX pretty definitively, I would think. The solution was to remove the realm (which isn't useful except for digest md5, anway, right?). Hey, it's working! Wahoo! *laugh* Anyway, if someone can offer suggestions on what's up with the pieces that *aren't* working, I'd be interested to know. It might give me a greater range of options. Amy! -- Amelia A. Lewis amyzing {at} talsever.com The less I seek my source for some definitive, the closer I am to fine. -- Indigo Girls

6 12

[dovecot] Util for pop3 to dovecot?
by Brad Figg 04 Jan '03

04 Jan '03

What I want to do is pop my email off of a Pop3 server and give it to dovecot for imap serving. Does anyone know of a utility that will allow me to do this? I looked at fetchmail but it seems to want to talk to an SMTP server. Thanks, Brad -- Brad Figg - brad(a)tpi.com 503.601.0235 ext. 105 TriplePoint, Inc. - http://www.tpi.com

3 2

[dovecot] maildirmake, shared folders
by Amelia A.Lewis 03 Jan '03

03 Jan '03

Does dovecot support shared folders, maildir style? I've set it up, using the maildirmake from debian maildrop to create folders. I have a number of as-yet unresolved issues, so I haven't been able to test with many clients. It's interesting that dovecot manages to present folders as siblings (rather than children) of INBOX. But mutt, at least, doesn't seem to see the shared maildir (created per instructions in the maildirmake man page). I find in the debian archives that courier is unable to see messages delivered to new in a shared maildir. This doesn't seem to be the same set of symptoms, though. It appears, instead, that dovecot isn't recognizing (and then advertising) the shared-maildirs file (a text file that describes the name and the location). Is that the case? I don't think it's a high priority, mind, just wondering. Another question: can the dovecot distribution include a maildirmake utility? The documentation is pretty blunt about the significant advantages of maildirs, but one has to go to the courier distribution to find a utility to pre-create these (which dovecot seems to want, since it's recognizing the mail type by looking for the dir). This is most significant when setting up new users, of course. Possibly this is inappropriate, and I should instead ask the debian package maintainer to 'recommend' or 'suggest' the maildrop package in order to get the required utility. Nice stuff, though. I really like the ease of administration; dovecot looks to me like a sort of equivalent to postfix, for IMAP instead of SMTP. A request for the website: perhaps developers could supply information on clients used with the server, and what oddities are encountered? I know that IMAP client support is spotty, at best (for instance, I can't find a client that can do digest-md5; mutt is supposedly capable, but my installation doesn't even admit that that's a valid authenticator). This is partly significant because setting up a system that uses options for which there is little or no client support is, perhaps, an exercise in futility. Amy! -- Amelia A. Lewis amyzing {at} talsever.com Never imagine yourself not to be otherwise than what it might appear to others that what you were or might have been was not otherwise than what you had been would have appeared to them to be otherwise. -- The Duchess [Lewis Carroll]

3 2

[dovecot] 0.99.5 released
by Timo Sirainen 02 Jan '03

02 Jan '03

v0.99.5 2003-01-02 Timo Sirainen <tss(a)iki.fi> * This release includes a lot of code cleanups, especially related to security. Direct buffer modifying was replaced in several places with a new buffer API, which provides a safe way to do it. Code that looks unsafe contains @UNSAFE tag to make auditing easier. + Support for SORT extension. Originally I thought about not implementing any extensions before 1.0, but too many people want webmails which want SORT. THREAD is another extension which they want, but we don't support it yet. + imap_listen and imaps_listen settings now accept "*" and "::" to specify if we want to listen in IPv4 or IPv6 addresses. "::" may also listen in all IPv4 addresses depending on the OS (Linux does, BSD doesn't) + New setting: default_mail_env can be used to specify where to find users mailbox. Default is still to use autodetection. + New setting: imap_log_path to log logins etc. informational messages to different file. + We support now separate mbox file for INBOX folder, no need for symlink kludging anymore. + Support for keeping index files in different location than actual mailboxes. ? Disabled mailbox_check_interval setting by default, it breaks Evolution. - SEARCH was still somewhat buggy, especially with laggy networks. Also body/header searches might have crashed or at least used memory too much - Deleting messages in the middle of mbox caused dovecot to reindex the following messages as new messages (ie. change UIDs and set \Recent flag). - Digest-MD5 auth: Initial server challenge packet was missing a comma, which might have made it incompatible with some implementations. - Some more fixes to unnecessarily high memory usage - SELECT and EXAMINE often printed UNSEEN reply or maybe complained about corrupted indexes. Happened usually only with mbox. - FETCH BODYSTRUCTURE gave incorrect reply, breaking pine - LIST was pretty buggy with mbox subfolders - CHECK command returned just "missing parameters" error - DELETE didn't work with mbox folders - CREATE mailbox<hierarchy separator> failed always. - CREATE and RENAME didn't create required hierarchies with mbox - RFC822 date parser didn't handle single digit days correctly. - login_process_per_connection = yes didn't work with imaps port connections which is exactly where it was mostly wanted. - ssl_disabled = yes didn't disable listening in imaps port - process limiting code didn't compile everywhere (eg. FreeBSD). - Linux sendfile() was never detected - We didn't work at all with gcc/PowerPC

1 0

[dovecot] Re: Maildir format
by Timo Sirainen 30 Dec '02

30 Dec '02

On Mon, 2002-12-30 at 09:25, Gareth J. Greenaway wrote: > On Mon, Dec 30, 2002 at 08:51:21AM +0200, Timo Sirainen wrote: > > Dovecot wants the folders directory names to begin with a dot, so name > > it ".test". Subfolders would be named as ".test.subfolder". This is > > compatible with Courier's Maildir++ format. > > Right. that is what I have as im using the Maildir folders from > Courier but I still do not see mail showing up in them. The folder > itself shows up but no mail. Oh, I think then you're just using mutt a bit wrong :) Enter-key goes inside a subfolder, space-key selects the folder. A folder can itself contain mail but it can also contain subfolders, so this is needed. With Courier you probably got away with just enter-key because you didn't have such subfolders and Courier gives mutt hints about if folders have subfolders. Dovecot doesn't yet support that extension so mutt always assumes they have subfolders.

1 0

[dovecot] Maildir format
by gareth＠wiked.org 30 Dec '02

30 Dec '02

Started using dovecot and I am very impressed by its speed. I am confused by what it is expecting the format of the Maildir directory to be in. I currently have ~/Maildir which contains new, cur, and tmp all containing email that should be in my inbox and it pops up correctly as such when I connect to dovecot using Mutt. After the connection a new .INBOX is created under ~/Maildir with sym links back to new, cur, and tmp. The problem arrises when I want to view email from another folder, I have a folder called "test" which contains some email also in Maildir format, however when I attempt to view this email I only get an empty listing with the ".." to go one directory up. Thanks. Gareth Greenaway -- "My friends say I should act my age, What's my age again?" Gareth J. Greenaway | gareth(a)wiked.org

2 1

[dovecot] passwd-file; configure args..
by Jesse Peterson 28 Dec '02

28 Dec '02

I couldn't reproduce this again (because i can't get imap-master running due to problem below..) but.. When compiling without shadow, passwd, or pam, when logging in I get after a successful login (in my syslog): Dec 28 22:39:38 badcase imap(username): MAIL environment missing and autodetection failed (home /some/home/directory) Now I thought this was covered in a previous fix before (ChangeLog: "2002-12-17 03:00 Timo Sirainen <tss(a)iki.fi>") but for some reason it's broken again..? The configure args problem has to do with --localstatedir. If i leave it default (PREFIX/var) it forces me (even with non-relative pathnames in the config file) for the socket-files (ssl_parameters_file, login_dir) that should go in /var/run to be put under PREFIX, (/usr/local for NetBSD 1.6). Not too bad, if I could override it in the config file, which I can't. So I ./configure'd with --localstatedir=/, and when I run imap-master I now get: Fatal: Can't create directory //run/dovecot: No such file or directory Somewhat odd. Any clues on either of these would be helpful, thanks. -- Jesse Peterson erage(a)softhome.net

2 7

[dovecot] o.99rc2 works on PowerPC - sort of...
by Jonas Smedegaard 27 Dec '02

27 Dec '02

Hi all, The new release starts on PowerPC now. On to the next problem... :-) When accessing my folders through Pine (setup to always go through IMAP, even local mboxes) I get "kicked out" it seems, pretty often. Here's what shows in the logfile: imap(jonas): file imap-bodystructure.c: line 342 (part_write_body): assertion failed: (part->children->next == NULL) - Jonas -- Debian GNU/Linux developer http://www.debian.org/ Jonas Smedegaard +45 40843136 http://dr.jones.dk/ Consulting for machines and humans: Spiff ApS

2 1

[dovecot] RLIMIT_AS patch for FreeBSD
by Dominic Marks 27 Dec '02

27 Dec '02

Hey, I've just updated the FreeBSD dovecot port to the 0.99.4 beta release, the following patch was needed as FreeBSD has setrlimit(2) but does not define RLIMIT_AS (I believe). I switched the code the require both, alternatively find a parallel option in the FreeBSD setrlimit(2) manual page. ( http://www.freebsd.org/cgi/man.cgi?setrlimit ) You may be interested in integrating this patch. --- src/lib/restrict-process-size.c Fri Dec 27 18:19:41 2002 +++ src/lib/restrict-process-size.c-new Fri Dec 27 18:19:22 2002 @@ -32,7 +32,8 @@ void restrict_process_size(unsigned int size __attr_unused__) { -#ifdef HAVE_SETRLIMIT +#if defined(HAVE_SETRLIMIT) && defined(RLIMIT_AS) +/* FreeBSD has setrlimit(2) but does not define RLIMIT_AS */ struct rlimit rlim; rlim.rlim_max = rlim.rlim_cur = Thanks, -- Dominic <dom at cus.org.uk> <d.marks at student.umist.ac.uk>

2 1