- dovecot - dovecot.org

[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