- dovecot - dovecot.org

[Dovecot] auth failure
by Tom Allison 11 Jun '04

11 Jun '04

well, with some help I've made a fair amount of progress on my box. It's working out much easier than I had anticipated and perhaps my notes will be useful some day. I have two questions... Here is where I am: cling:~# egrep -v "^($|\#)" /etc/dovecot.conf protocols = imap imaps login = imap login_max_processes_count = 16 login = pop3 max_mail_processes = 512 verbose_proctitle = yes default_mail_env = maildir:~/Maildir mailbox_check_interval = 1 auth = default auth_mechanisms = plain auth_passdb = pgsql /etc/dovecot-pgsql.conf auth_user = root auth_verbose = yes cling:~# egrep -v "^($|\#)" /etc/dovecot-pgsql.conf connect = dbname=dbmail user=dbmail_reader password=SECRET default_pass_scheme = PLAIN-MD5 password_query = SELECT passwd AS password FROM users WHERE userid = '%u' I've created working passwords using 'mkpasswd --hash=md5' and plugged the results into my database. I can login and everything looks pretty cool. Except, as near as I can tell, I'm sending plaintext authentication over the wire. My best guess is that my password gets munged into digest-md5 format before it goes over the wire. At this point I'm of the opinion that I'm reasonably secure. True so far? My guess is that the next step in security is to go for imaps and ssl configuration. But my debian installation doesn't appear to have the dovecot-openssl.cnf file referenced in the configuration.txt file. Is this missing from dovecot or am I looking at a debian problem?

3 4

[Dovecot] Corrupted index file
by Niilo Kajander 11 Jun '04

11 Jun '04

Hi, I've been wondering for a while if reiserfs is dovecot+maildir safe or not. I get this too often (and my imap session gets disconnected): Jun 9 08:42:32 sun imap(nk): Corrupted index file /home/nk/Maildir/.INBOX/.imap .index: UIDVALIDITY changed in uidlist This happens always when a new mail arrives in maildir. It's a Fedora Core 2 box running dovecot-0.99.10.4-4 (redhat) package. Could the reason for these corruptions be something else than reiserfs? I know there has been some problems with Fedora+dovecot but I haven't seen this one reported here. TIA, -- Niilo Kajander <nk(a)kajander.fi>

3 5

[Dovecot] bleah
by Tom Allison 11 Jun '04

11 Jun '04

Not to be a bitch, but I've asked several times about some basic questions or examples to clarify the essentials for configuration. What do some of the parameters mean? Expecially the ones that are mentioned only one in a paragraph and no where else in the documentation or wiki. (ie: login_process_per_use) And there have been a few others as well. that I won't bother to repeat. But I've been sitting on this list for a while yet and have found that when it comes to configuration, none of the emails posted have been answered or addressed. The closest I got was a suggestion to use views instead of tables in postgres. But technically nothing was ever said about dovecot itself. So I have to ask. Is the sketchy documentation in the source file, the web page, wiki, and limited reponse on the mailing list a matter of "I haven't gotten around to it yet" or a deliberate move to promote the commercial support potential for Procontrol? I've run into this kind of environment twice before (cyrus and razor) and in the case of cyrus they just didn't believe in doing the documentation but suggested I write it myself. That may be the case there as well ("I haven't gotten around to it yet". That's OK but cyrus has the difficulty of no one still not providing any answers to how anything was done, configured, functioned, or why. So documentation was kind of a reverse-engineering project in itself. In the case of razor it's a mix of no time and they would rather support the company than the project. I went back and re-read the emails that I had posted earlier and am pretty sure that they weren't too stupid (ie: how do I test an imap connection), difficult, or obscure (well, maybe one). I'm just trying to find more information on how to correctly configure this server such that I can retain the concept of keeping security in mind. I'm trolling through the archives and there doesn't seem to be much discussion from anyone else. So maybe I'm really stupid and can't do authentication schemes. I'm sure by this point I've really pissed a few people off and for that I mostly apologize. I'm a little bent here myself. It just that I didn't plan on having to set up sniffit to track my IMAP traffic in order to verify that things were actually working securely. I'm going to plug along and do it myself and probably get something to work. I have plain_text authentication working now, but was really hoping to actually get something secure. At this point I really don't expect an answer, but do hope that after 1.0 is released there will be time available to get some documentation in order. IMHO the level of documentation that is available on a software project is critical to it's use.

2 2

[Dovecot] pgsql documentation
by Tom Allison 11 Jun '04

11 Jun '04

From dovecot-pgsql.conf # Examples: # connect = host=192.168.1.1 dbname=users # connect = host=sql.example.com dbname=virtual user=virtual There is a reference to identify the rest of the parameters via libpq in the postgres documentation. From postgres, libpq says the connection environment variables are: hostname:port:database:username:password http://www.postgresql.org/docs/7.4/static/libpq-pgpass.html Should the dovecot-pgsql.conf docs be changed from "dbname=users" to "database=users" ??

1 1

[Dovecot] "virgin" mail accounts
by Christian Balzer 11 Jun '04

11 Jun '04

Hello, I'm willing to swear that with the 0.99.10.4 Debian package in my rather extensive tests with mailbox format dovecot created not only any missing parental directories but also the INBOX file, but the later I can't prove/test now as I upgraded all respective boxes. However 0.99.10.5 will still create (if needed and possible) missing directories for mbox storage, just not an empty INBOX. But with maildir, it will not even do that, from a test with pop3 and imap login attempts to a freshly created account that had not received any mails yet: --- Jun 10 12:58:03 mb01 pop3-login: Login: test [203.216.5.92] Jun 10 12:58:03 mb01 pop3: I/O leak: 0x8050ce0 (0) Jun 10 12:58:03 mb01 pop3: I/O leak: 0x8084aa0 (1) Jun 10 12:58:49 mb01 imap-login: Login: ttest [203.216.5.92] Jun 10 12:58:50 mb01 last message repeated 3 times Jun 10 12:58:50 mb01 dovecot: child 9193 (imap) killed with signal 11 --- It died not very graceful in either case, esp. the later. Unless there are very RFC'ish and imperative reasons, I'd suggest that dovecot creates all missing bits if possible no matter what the storage method or pretends to have encountered an empty mbox file or maildir cur/new respectively. The rationale should be obvious, no frantic user calls about "My mail is not working" when the answer is "Duh, that's because you never ever received one yet". ;) Regards, Christian Balzer -- Christian Balzer Network/Systems Engineer NOC chibi(a)gol.com Global OnLine Japan/Fusion Network Services http://www.gol.com/

3 4

[Dovecot] Scripting
by Nico De Beer - MWEB 10 Jun '04

10 Jun '04

You metioned previosely that one can do character translation with postgress with mysql you can also do so but can use it as the table name Is there anyway to write something outside dovecot to do the lookup in say c++ Are you ready for Telkom's 10-digit dialling? To find out how this will affect your Internet connection in the not too distant future, go to www.mweb.co.za/ten

2 1

[Dovecot] 2 problems
by Cor Bosman 10 Jun '04

10 Jun '04

Hi all, im testing dovecot as a replacement imap server and noticed 2 problems in 0.99.10.5. if you use dovecot/pop on an account who's quota is fully used, dovecot will ungracefully stop. This will only happen when the account is first accessed by dovecot (for instance, when offering IMAP to an existing userbase using dovecot, or when the index files have inadvertently been deleted). +OK dovecot ready. user scorpio +OK pass xxxxxxxx +OK Logged in. Connection closed by foreign host. The same goes for imap: * OK dovecot ready. . login "scorpio" "xxxxxxx" . OK Logged in. . select INBOX . NO Out of disk space This is a bit of a problem because one of the remedies of solving an out of disk space problem is deleting email, which you cant now. Cor

2 1

[Dovecot] mbox configuration
by Nina Pham 10 Jun '04

10 Jun '04

Hi, I change the dovecot.conf default_mail_env = mbox:/Mail/IMAP/%u/:INBOX=/var/mail/%u After I did the change, I restart dovecot with the hope that folder that I create will be stored in /Mail/IMAP/%u. Then I use Mozzila as my email client and change the IMAP server directory to ~nina/IMAP/ which is the link to /Mail/IMAP/nina/. But then I can not create folder anymore from Mozzila, or view any thing other than inbox. I am still able to see message in inbox since I haven't change the location of inbox. Please help. Nina

2 1

[Dovecot] authentication configuration
by Tom Allison 10 Jun '04

10 Jun '04

I've included the non-defaulted bits of my dovecot.conf file at the bottom of this email. As I understand my set-up it's using unix authentication methods (/etc/passwd via pam?). Considering disable_plaintext_auth and auth_mechanisms, what exactly is being passed? I was hoping to get auth_mechanism = digest-md5 but that's not working out very well right now. It seems I can only do plaintext authentication. I got stuck on the userdb/auth_passdb settings. Can someone give me an example of how to configure for md5-digest authentication? My current guess is: disable_plaintext_auth = yes auth = digest-md5 auth_mechanism = digest_md5 auth_passdb = /etc/mydigestfile How would I set this for pgsql? auth_passdb = /etc/dovecot-pgsql.conf ### non-default config settings. protocols = imap imaps disable_plaintext_auth = yes login = imap login_max_processes_count = 16 login = pop3 max_mail_processes = 512 default_mail_env = maildir:~/Maildir mailbox_check_interval = 1 auth = default auth_mechanisms = plain auth_passdb = pam auth_user = root

2 1

[Dovecot] configuration
by Tom Allison 10 Jun '04

10 Jun '04

I've noticed that there are some parameters mentioned in the docs that aren't identified therein (ie: login_process_per_use). Is there a more generic set of docs that can identify what each of the parameters and what they do, or at least something that will allow me a simple how to to avoid embarrasing situations. I supposed I should only settle for ssl based connections (imaps/pops) but I will be open to digest-md5 if I could. I'm also curious to see how I can use pgsql authentication with dovecot. I think this would be great to work with since I'm basing all my postfix settings around postgresql as well. But for now I'm not sure how to use postfix authentication with the file directories I'll need to use for the maildirs (and procmail!).

2 1