- dovecot - dovecot.org

[Dovecot] Permission denied: failed to chdir to /home/paul
by Paul Ororke 28 Sep '05

28 Sep '05

Hi, I've been trying to set up Exin and Dovecot and think I've almost gotten there. However I'm not recieving mail to my inbox and I get messages like the following in /var/log/exim/main.log: 2005-09-28 04:14:47 1EKZtf-0003gQ-26 <= users-return-105525-paul= paulororke.net(a)openoffice.org H=s002.sfo.collab.net<http://s002.sfo.collab.net>( openoffice.org <http://openoffice.org>) [64.125.133.202<http://64.125.133.202>] P=smtp S=3120 id=200509280613.08050.dlewis(a)delewis.com 2005-09-28 04:14:47 1EKZtf-0003gQ-26 == paul(a)paulororke.net R=localuser T=local_delivery defer (13): Permission denied: failed to chdir to /home/paul How do I make it so that this doesn't happen?

3 3

[Dovecot] ManageSIEVE services with Dovecot cvs-LDA?
by OpenMacNews 28 Sep '05

28 Sep '05

hi all, has anyone had any success in getting the current dovecot cvs-lda's implementation of CyrusSIEVE responding to a ManageSIEVE client? in particular, i'm hoping that one can use, e.g., Mulberry's Client- & Server-side sieve editor: <http://www.cyrusoft.com/sieve/sievescreens.html> if i telnet to my dovecot box's sieve port ( = 2000) i get no response at all ... telnet localhost 2000 Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused telnet: Unable to connect to remote host net-stat shows nothing on port 2000, and, afaik, there's no mention of a server on the wiki ... so i'm either doing something wrong, or "it" is simply not there. has a sieve server been implemented? any plans? thx! richard

4 7

[Dovecot] Problem with logging in on pop3
by michal 28 Sep '05

28 Sep '05

I switched from dovecot 0.99 to 1.0 stable alpha and now i cannot get my pop3 to work. I checked the logs and this what i`m getting when i try to login using outlook: Login: user=<michael>, method=PLAIN, rip=192.168.1.200, lip=192.168.1.20 Sep 27 17:21:26 mail dovecot: pop3(michael): Effective uid=515, gid=100 Sep 27 17:21:26 mail dovecot: pop3(michael): maildir: access(/home/michael/Maildir, rwx): failed: No such file or directory Sep 27 17:21:26 mail dovecot: pop3(michael): maildir: couldn't find root dir Sep 27 17:21:26 mail dovecot: pop3(michael): mbox: root exists (/home/michael/mail) Sep 27 17:21:26 mail dovecot: pop3(michael): mbox: INBOX exists (/var/mail/michael) Sep 27 17:21:26 mail dovecot: pop3(michael): mbox: root=/home/michael/mail, index=/home/michael/mail, inbox=/var/mail/michael Sep 27 17:21:26 mail dovecot: pop3(michael): open(/var/mail/.temp.mail.bio-world.com.18859.4e2d002619befc19) failed: Permission denied Sep 27 17:21:26 mail dovecot: pop3(michael): file_lock_dotlock() failed with mbox file /var/mail/michael: Permission denied Sep 27 17:21:26 mail dovecot: pop3(michael): Mailbox init failed top=0/0, retr=0/ del=0/0, size=0 Anybody have any idea how to fix that pls ?

1 0

[Dovecot] Dovecot Error: Master requested auth for nonexisting client
by Paul E Virgo 27 Sep '05

27 Sep '05

Hello, The subject line says it all. It seems to be happening with regards to my default auth setting in the dovecot.conf file. I currently have it set to 'plain'. Am I missing something? FWIW, I am using the latest, stable (alpha) release: 1.0.alpha3 PE Virgo

3 2

Re: [Dovecot] Misbehavior with Dovecot and Mulberry
by Jon Roma 27 Sep '05

27 Sep '05

Sorry about that last -- Windows seems to have mangled the attachment. Retrying here.

2 1

[Dovecot] stable 1.0 on FC3
by Obantec Support 27 Sep '05

27 Sep '05

Hi should this worry me dovecot: POP3(chelan): file mail-index-view-sync.c: line 60 (view_sync_get_expunges): assertion failed: (ret == 0) using mbox format under /var/spool/mail/ Mark -- Obantec Support www.obantec.net 0845 458 3121 WebHosting and Domains Nominet UK Member & IPStag Holder CentralNic Accredited Reseller

2 1

[Dovecot] mail not found
by Michael Collins 27 Sep '05

27 Sep '05

This is in my dovecot.conf default_mail_env = maildir:/var/mail/vhosts/%1u/%u/ my mail ia in/var/mail/vhosts/anawebdesigns.com/user1/cur, new, tmp As you can guess these are virtual accounts. Auth works but mail is not found. How do I need to modify the line in dovecot.conf? Thanks. -- -- Michael H. Collins It's us against them. Ride like you stole it. If you love some code, set it free. Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html

2 1

Re: Re: Re: [Dovecot] virtual domain
by Barry Kwok 27 Sep '05

27 Sep '05

>On Tue, 2005-09-27 at 13:29 +0800, Barry Kwok wrote: >> userdb static { >> args = uid=503 gid=503 mail=mbox:/var/spool/virtual/%d/%n >> } > >Drop the "mail" part from here. You already have it in default_mail_env, >and it's correct there. Here you're saying that the .../%d/%n is the >mail directory, not file. If it refuses to start up without the mail= >part, replace it with home=/tmp instead. > >> Why I need a IMAP folder in a POP3 only server > >Dovecot is mostly an IMAP server, POP3 was just an afterthought. > >> and can I change that folder to /tmp directory. > >Yes, as long as nothing actually gets written there (and with >INDEX=MEMORY and POP3 nothing should get written there). > > Thank you Timo, I have just tried. But I found that I must add the mail=mbox:/var/spool/virtual/%d/%n part. Without this part, the dovecot seems not checking the right location of mail spool and simply say that "no new email". Now I added this part together with "home=/tmp" part into userdb config and It works now with IMAP folder in /tmp directory. But I want to ask if there is any file locking problem as I am running virtual email with vmail as owner for all mbox accounts. And it seems that they are all share the same IMAP folder located in /tmp directory.

2 1

[Dovecot] Hostname passed to PAM as rhost
by Tom Alsberg 27 Sep '05

27 Sep '05

(I am sorry to bother the list with something I should have verified myself right now - I simply do not have access to the source code here) Thinking of some limit I wanted to put with authentication, I am wondering - when Dovecot authenticates a user using PAM, now that (in 1.0) it passes the rhost item to PAM, it passes a hostname, not an IP address. Does it double-verify the DNS record before it trusts this to be the hostname (first checking the IP address in in_addr.arpa and then checking that the hostname indeed maps back to the same IP address)? That is necessary in order to trust the client address when determining authentication strength in the PAM module based on the client location (specifically we want stronger authentication when the client comes outside of our network, while inside a plain password suffices), as else anybody could "spoof" the hostname by changing the IN PTR record of his IP address to point back to some "trusted" hostname (given he has control of the DNS zone his host is in, which is completely possible given the server knows nothing about it). Thanks, -- Tom -- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.

5 6

[Dovecot] POP3 problem
by michal 27 Sep '05

27 Sep '05

Hey all this is my first post to this list. I have fresh Red Hat AS 4.0 with postfix 2.1. This will be my mail server. I have one problem with pop3. My mail server is working properly. I did the following test: Sent an email to some other server(yahoo.com)->email got there fine. >From that other server(yahoo.com) replaied-> to the new server and email got there fine,checked using pine. Now in x windows on the mail server if i lunch email client software and set up the account, then i can send and receive emails fine so pop3 is working. But when i go to different machine like PC set up outlook then i cannot receive emails. I get error in outlook that the connection has failed. So i telnet 192.168.1.10 110 and I have gotten response from the server 250 dovecot OK. I really dont what to do at this time. I have been trying couple different things without any luck..... need some help? Mike

3 5

[Dovecot] How safe is mbox_very_dirty_syncs?
by Chris Wakelin 27 Sep '05

27 Sep '05

I've tried turning on mbox_very_dirty_syncs for myself (and a few other brave souls running 1.0-alpha3 rather than 1.0-stable) again to see what perfomance gain it gives (see thread http://www.dovecot.org/list/dovecot/2005-July/007956.html) Now we aren't running UW-IMAP at all, how safe is mbox_very_dirty_syncs assuming the only other process writing to mailboxes is our MTA (exim) which simply appends messages to the end? Is it safer still using Dovecot 1.0-alphas and the LDA? Does it matter if there are concurrent connections to the mailbox? Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

3 2

[Dovecot] new mailbox format v2
by Timo Sirainen 27 Sep '05

27 Sep '05

Updated version. The previous one was a bit too complicated with flag updates for pretty minimal benefits. Changes: - writing/reading mail flags can be disabled to get better performance without it requiring any changes to how the files are normally handled (so mixed more works fine). - writing flags now requires getting shared locks. so there's the overhead of locking but flag writers don't have to wait for each others. - reading requires no locking anymore. the comment in the previous version about reading only half a mail being a problem doesn't actually matter, since if a client tries to read an expunged mail Dovecot already disconnects the client immediately (since most clients can't handle such situation well anyway). - no more problems with mailbox readers locking out expungers - note about fcntl() locking being able to provide even higher concurrency - works just fine with plain dotlocks, so works fine with NFS And looks like I forgot to explain the "mail header padding" before. I'm not exactly sure if it's useful or not, but it doesn't hurt to have it there if it's wanted. The idea was anyway that if you're writing more than one flag at a time, having a 512 byte padding would make sure that when writing the few bytes the OS will only have to read one sector from disk (512 bytes in all todays OSes I believe?) to get the non-written parts of the sector instead of possibly reading two sectors. So it might help with trading disk reads for some wasted disk space. Generic ------- The point is to have a mailbox format where the mailbox can consist of one or more files. Grouping multiple files in a single file makes it faster to read, but it's slower to expunge mails from the beginning of the file. So this format would allow sysadmin to specify rules on how large the files would be allowed to grow. Index File ---------- Named "index". Index file gives a mapping between UIDs <-> filenames: Header: <uidvalidity> <last-used-uid> Record: <uid-first> <uid-last> <filename> Record: .. eg.: 1127468129 5 1 3 msg.1 4 4 msg.4 All of the UIDs don't have to actually exist in the file if they have been expunged. The record should be removed once all of the UIDs have been removed from it (and the file itself been deleted). The same file may appear multiple times in the index. For example: 1 2 msg.1 3 3 msg.3 4 5 msg.1 This means that UIDs 1, 2, 4 and 5 are in file msg.1, but UID 3 is in file msg.3. The filename doesn't matter as long as it's unique, but probably wouldn't hurt to include its first UID in the filename so humans can find mails more easily. The filename however must not end with ".lock". The file is modified by creating first exclusively owned "index.lock" file, updating it and then rename()ing it over the index file. This lock file shouldn't be held for a long time, so if it exists, and it doesn't get modified at all within 30 seconds, it can be overwritten. Before rename()ing over the index file, you should check with stat() that the index.lock file is still the same as you expect it to be (in case your process was temporarily stopped for over 30 secs). The index file's mtime timestamp must grow after each modification. This makes it easy to check if new mail has been added to the mailbox. Mail File --------- File header: Bytes Format Description 8 hex Header size 16 hex Append offset 4 hex Mail header size 4 hex Mail header padding 4 hex Keyword count in mail headers Mail header: Bytes Format Description 8 hex UID 16 hex Mail size 1 1/0 Answered flag 1 1/0 Flagged flag 1 1/0 Deleted flag 1 1/0 Seen flag 1 1/0 Draft flag 1 1/0 Expunged flag n 1/0 Keywords The file layout then goes: <File header> - possible padding due to Header size <Mail header #1> - possible padding due to Mail header size <Mail data #1> - possible padding due to Mail header padding (ie. next Mail header's offset is divisible with Mail header padding) <Mail header #2> etc.. The UIDs must be ascending within the file (but as said above, some UIDs between them may exist in other files). If mail has been marked with expunged-flag, it should be treated as if it was already expunged. The mail will really be expunged later in some nightly run. Reading the files requires no locking. If while reading you happen to hit unexpected end of file, it means that mails were expunged from the file. After that you'll look at the index file again to see which file the mail went and continue from there on. If the mail isn't found, it means it got expunged. Expunging happens by locking the file and then copying all non-expunged mails after the first expunged one to new file. Then update the index file with the new location for the UIDs, and at last ftruncate() at the position of first expunged mail in the original file. Flag updates require locking the file as well, otherwise we might try to write past the end of file when another process is expunging the mails. Shared locking can be used for flag update locking since each flag update can be atomically changed by writing one byte. Appending mails can be done by either locking existing file and appending to it, or creating a new file. If appending to a new file, create it with .lock suffix and then check that the file without .lock wasn't already just created to prevent race conditions. When appending to existing file, check "Append offset" from file's header. If that offset is at the end of file, just append there. Otherwise read the mail's header from there. If it has a non-zero UID and index file says that the same UID exists in this file, jump over the mail and do the same checks for all the rest of the mails in the file. Once the check doesn't match or you reach EOF, update the append offset in the header to that offset and write your mail there. Initially write the UID in mail's header as zeroes ('0', not NUL). Once the append is completely finished, you'll have to update it with the new UID. You'll do this by locking index file, reading the latest last-used-uid and using the next value for your UID. Once you've written it, rewrite the index file with updated last-used-uid field and your UID added to it. After this, update the append offset in the mail file and unlock it. If fcntl() locking is used, locking only specific ranges can give more concurrency. Flag updates only need to lock the part of the file they're modifying. Expunges need to lock the part which it's removing. Appending needs to lock from <end of file-1> to end of file (ie. l_len=0). Keywords file ------------- Named "index.keywords". This contains mappings between keyword numbers and names. TODO: write how it's updated Recent file ----------- "index.recent.<uid>" file tells what the last non-recent UID was. The file doesn't have any data inside it. When opening the mailbox you should find and rename() the existing index.recent.<uid> file to the new index.recent.<last-uid>. A successful rename() means the mails between <uid>+1 .. <last-uid> are recent for you. A failed rename() means that someone else managed to do it. You should look for the file again and if it was renamed to less than <last-uid>, you should try again. Nightly cleanups ---------------- Because expunged mails may be left lying around for a while, there probably should be some nightly check that cleans them up. Other cleanups that may be necessary after crashes are: - .lock files - expunged data at the end of files (can be checked with same rules as how appending determines the offset where to append) Alternative ways to use ----------------------- Expunging mails isn't very filesystem quota friendly since it requires creating another file to copy the expunged mails to. This could also be done by just moving the data within the file. This however requires that all file reads must also be shared-locked. Also it has the problem of leaving the mailbox corrupted if the copying gets aborted in the middle. For the best performance the mail flags could be stored only in Dovecot's index files. In that case the flag update locking isn't slowing down expunges (and if fcntl() locks can't be used, doesn't slow down appends either). Also there's no need for keywords/recent files. Compatibility ------------- If needed, it would be possible to create new/ and tmp/ directories under the mailbox to allow mail deliveries to be in maildir format. The maildir files would be then either just moved or maybe be appended to existing mail files.

1 0

[Dovecot] Mail directory funkiness
by Ted Kaczmarek 27 Sep '05

27 Sep '05

I am using dovecot-0.99.14-4.fc4 on FC4, was testing using mbox and than switched to using Maildir. default_mail_env = maildir:~/Maildir >From evolution when I create a folder the folder is created in ~/mail instead of ~/Maildir I am still rather new to dovecot, but this does not make sense. I made sure to restart dovecot, even added a .procmailrc. cat .procmailrc MAILDIR=/home/tedkaz/Maildir :0 ./ I am going to grab the latest version and test with that, but if if anyone has insight into how I got here it would be appreciated :-) Likely a pilot error. Regards, Ted

2 3

Re: Re: [Dovecot] virtual domain
by Barry Kwok 27 Sep '05

27 Sep '05

>On Mon, 2005-09-26 at 21:33 +0800, Barry Kwok wrote: >> we are currently using vm-pop3d to implement virtual domains. But due to some locking problem in vm-pop3d, we want to test the possibility to change to dovecot. >> Currently, in vm-pop3d, the passwd file is located in >> /etc/virtual/domain1.com/passwd >> /etc/virtual/domain2.com/passwd > >passdb passwd-file { > args = /etc/virtual/%d/passwd >} > >This requires Dovecot 1.0.alpha2 or later. > >> and the passwd format is: >> user: md5 encrpted password > >In MD5crypt format? ie. $1$something? Then it should work directly. > >> and the email is store in >> /var/spool/virtual/domain1.com/user >> /var/spool/virtual/domain2.com/user > >As mboxes? For IMAP you'll need also some directory where non-INBOXes >are stored, and with POP3 Dovecot also wants a directory where it can >store index files. > >If you don't want either, you could do something like: > >default_mail_env = mbox:/tmp:INBOX=/var/spool/virtual/%d/%u:INDEX=MEMORY Thank you. Timo. I have installed Dovecot 1.0 alpha3 and tested. It is a mbox POP3 only server. The relevent part of dovecot.conf I have changed: default_mail_env = mbox:/tmp:INBOX:/var/spool/virutal/%d/%u:INDEX=MEMORY passdb passwd-file { # Path for passwd-file args = /etc/virtual/%d/passwd } userdb static { args = uid=503 gid=503 mail=mbox:/var/spool/virtual/%d/%n } I can login with user(a)domain1.com but there is error in logfile: Sep 27 13:15:16 ns2 dovecot: pop3(user(a)domain1.com): mbox: Can't create root IMAP folder /mail: Permission denied Sep 27 13:15:16 ns2 dovecot: pop3(user(a)domain1.com): Failed to create storage with data: mbox:/var/spool/virtual/domain1.com/user Sep 27 13:15:16 ns2 dovecot: pop3-login: Login: user=<user(a)domain1.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Sep 27 13:15:16 ns2 dovecot: child 19147 (pop3) returned error 89 I then created a /mail directory with file mode 777, then it is OK. Why I need a IMAP folder in a POP3 only server and can I change that folder to /tmp directory.

2 1

[Dovecot] Misbehavior with Dovecot and Mulberry
by Jon Roma 27 Sep '05

27 Sep '05

I'm having a bit of misbehavior wherein Dovecot seems to refuse to cooperate with my Mulberry MUA. By and large, everything works great. I can move mail back and forth happily. I can compose a note and copy the outgoing mail to my Dovecot "Sent" folder using my default Mulberry settings. But if I reply or forward a mail, I get a Mulberry error popup saying that it "couldn't decode the response from the server" and that the operation was unsuccessful. This was somewhat mystifying (especially since this does work for a newly composed message as opposed to a reply/forward), so I turned on Mulberry logging. This is what I see (with unrelated operations clipped from the log). First, the first case where I create a new message, send it, and save a copy in my Sent folder: --> #6.3408 Mon Sep 5 23:24:27 2005 A00085 APPEND Sent (\Seen) {418+} * 5544 EXISTS * 1 RECENT A00085 OK Append completed. All's well there. Mulberry does a FETCH to grab the new message (reply) from my Sent folder and then does a SORT so that it can order it properly in the display. This too succeeds but is probably irrelevant to us. After a couple NOOP commands come and go in the background, I try to reply to a message in one of my mailboxes. In this case it happens to be the one in my Sent folder. So Mulberry issues a FETCH (you can see the original mail there in the FETCH response from Dovecot). It then does a STORE of the original mail, apparently to update the \Answered flag. It then tries to APPEND the reply to the Sent folder, but this time, the server comes back with a NO. See below --> #6.3408 Mon Sep 5 23:24:43 2005 A00089 FETCH 5544 (BODY[1]) * 5544 FETCH (BODY[1] {63} ) A00089 OK Fetch completed. --> #6.3408 Mon Sep 5 23:25:13 2005 A00090 FETCH 5544 (RFC822.HEADER) * 5544 FETCH (RFC822.HEADER {355} Date: Mon, 05 Sep 2005 23:24:27 -0500 From: Jon Roma <roma(a)uiuc.edu> To: Jon R Roma <roma(a)uiuc.edu> Subject: Test 1 Message-ID: <DDDD999F0F4E38F8C1510CC8(a)jrr2.isdn.uiuc.edu> X-Mailer: Mulberry/3.1.6 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline ) A00090 OK Fetch completed. --> #6.3408 Mon Sep 5 23:25:13 2005 A00091 STORE 5544 +FLAGS (\Answered) * 5544 FETCH (FLAGS (\Answered \Seen \Recent)) A00091 OK Store completed. --> #6.3408 Mon Sep 5 23:25:13 2005 A00092 APPEND Sent (\Seen) {610+} A00092 NO I am having similar problem saving a draft to my Drafts folder and suspect the same thing is behind both of these. I didn't create a Mulberry trace log for this but can do so if need be. I am running 1.0-test80 with Timo's patch to fix the "time off by 200 minutes" error with mbox. All my folders are maildir at this point -- I've converted them out of my UW mbx format store. My client is Mulberry 3.1.6 for Windows and the OS is AIX 5.1. This weird behavior is a mystery to me!

3 13

[Dovecot] Problems with alpha3 + openssl-0.9.8
by Andy Cravens 27 Sep '05

27 Sep '05

Has anybody successfully compiled alpha 3 with the newly released openssl-0.9.8? I just wasted the weekend trying to get dovecot to compile using the new openssl libs. Openssl-0.9.7d works like dream. Just wanted to know if anybody had this combo working.

3 2

[Dovecot] 1.0alpha3 packages for debian
by Jaldhar H. Vyas 26 Sep '05

26 Sep '05

Sorry this took even longer than I thought but they should be arriving in unstable this afternoon. I also have a backport for stable available at http://www.braincells.com/backports This directory is not aptable so manually install the packages for now. (Hopefully backports.org will have their sarge repository open soon. When that happens they will move there.) The configuration file format has changed so you will want to carefully check /etc/dovecot/dovecot.conf when upgrading. I forgot to put a note about that in NEWS.debian sorry. I think I might have forgotten a couple of config file tweaks people have suggested and in general, if you sent me mail in the past month or so and I didn't respond or the problem still isn't fixed, please give me a nudge. This is why you really ought to use the Debian bug tracking system rather than mailing the maintainer. Anyway, enjoy. -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

1 0

[Dovecot] Dovecot-Pop3d
by Mark Smith 26 Sep '05

26 Sep '05

What port does Dovecot-Pop3d run on? 110? If so I can't get it to work "netstat -ltnp | grep ':110'" shows nothing. and dovecot-pop3d is installed. Regards, _________________________________________________________________ The new MSN Search Toolbar now includes Desktop search! http://toolbar.msn.co.uk/

2 1

[Dovecot] virtual domain
by Barry Kwok 26 Sep '05

26 Sep '05

we are currently using vm-pop3d to implement virtual domains. But due to some locking problem in vm-pop3d, we want to test the possibility to change to dovecot. Currently, in vm-pop3d, the passwd file is located in /etc/virtual/domain1.com/passwd /etc/virtual/domain2.com/passwd and the passwd format is: user: md5 encrpted password and the email is store in /var/spool/virtual/domain1.com/user /var/spool/virtual/domain2.com/user and we login as user(a)domain1.com, user(a)domain2.com . We want to maintain this format as login id and the password format. What should be changed in dovecot.conf? Thanks.

3 2

[Dovecot] DSA support for TLS?
by OpenMacNews 25 Sep '05

25 Sep '05

hi all, i've dovecot TLS working correctly w/ locally generated *RSA* CA cert, domain privkey & self-signed domain cert. to that end, my dovecot.conf includes: ssl_key_file = /var/Security/mail.testdomain.com.privkey.rsa.pem ssl_cert_file = /var/Security/mail.testdomain.com.cert.rsa.pem ssl_ca_file = /var/Security/MyCertificateAuthority.CA.cert.rsa.pem ssl_verify_client_cert = no ssl_cipher_list = ALL:!SSLv2:!aNULL:!NULL:!EXPORT:!DES:!LOW:@STRENGTH however, if I try to setup for DSA use: ssl_key_file = /var/Security/mail.testdomain.com.privkey.dsa.pem ssl_cert_file = /var/Security/mail.testdomain.com.cert.dsa.pem ssl_ca_file = /var/Security/MyCertificateAuthority.CA.cert.dsa.pem ssl_verify_client_cert = no ssl_parameters_file = /var/Security/dsaparam.pem ssl_parameters_regenerate = 0 an attempt @ dovecot launch results in a logged error of: dovecot: Sep 11 11:58:43 Error: imap-login: Can't load private key file /var/Security/mail.testdomain.com.privkey.dsa.pem: error:0607907F:digital envelope routines:EVP_PKEY_get1_RSA:expecting an rsa key wherein it looks like dovecot is _still_ seeking an RSA key. fwiw, % cat /var/Security/mail.testdomain.com.privkey.dsa.pem -----BEGIN DSA PRIVATE KEY----- ... i've searched the dovecot wiki, and although the _only_ reference i find to dsa/diffie is @: http://wiki.dovecot.org/moin.cgi/MainConfig " ... SSL parameter file. Master process generates this file for login processes. It contains Diffie Hellman and RSA parameters. ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat ... " it does seem to imply that DSA certs are, at least, supported. comments? cheers, richard

2 4

Re: [Dovecot] ManageSIEVE services with Dovecot cvs-LDA?
by OpenMacNews 25 Sep '05

25 Sep '05

i can't find a trace of any sieve mgmt services in dovecot as yet, and haven't found anything in this list ... so, if i *am* missing it, if someone would be kind enuf to point me in the right direction, i'd appreciate it! 8-} in the meantime, a little more info for those interested ... the latest spec for sieve management, "A Protocol for Remotely Managing Sieve Scripts", can be found at: <http://www.ietf.org/internet-drafts/draft-martin-managesieve-05.txt> iiuc, one of the authors, Tim Martin / Mirapoint Inc., is the "Tim" of "timsieved" -- Cyrus' ManageSIEVE 'server' bundled with cyrus-imap. i can strip timesieved it out of a successful build of cyrus-imap, but it seems to be dependent on cyrus-sasl ... as such, i'm not sure how to integrate it with dovecot's SASL auth methods. i have a feeling that such fuctionality would have to be re-implemented in dovecot alongside of sieve itself ... and probably should, if it were to be included. the courier-imap mailing lists also have folks searching for an alternative to timsieved ... richard

1 0

[Dovecot] redirect and sieve
by Rudy Gevaert 24 Sep '05

24 Sep '05

Hello, I have set up postfix to use dove-cot lda. This works perfect. Sieve works a bit... I would like to user the redirect feature of sieve. Having followed the wiki I added the following in my .dovecot.sieve : require "redirect"; if header :contains "subject" ["order", "buy"] { redirect "orders(a)company.dom"; } With this setup I get the following error: Sep 22 11:25:38 zalm deliver: sieve parse error for rgevaert: line 1: unsupported feature Remove the require line makes a forward. But this doesn't forward the message I set, but makes a new empty message... : - From Rudy.Gevaert(a)UGent.be Thu Sep 22 14:31:46 2005 - Date: Thu, 22 Sep 2005 14:29:01 +0200 (CEST) - From: Rudy.Gevaert(a)UGent.be (Rudy Gevaert) - To: undisclosed-recipients: ; Is this a bug? Or have i missed something? Thanks in advance, -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Rudy Gevaert e-mail: Rudy.Gevaert(a)UGent.be Directie ICT, Afdeling Infrastructuur Groep Systemen tel: +32 9 264 4734 Universiteit Gent fax: +32 9 264 4994 Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

2 4

[Dovecot] v1.0.alpha2, virtual domain authentication
by Jean-Marc Pigeon 24 Sep '05

24 Sep '05

Bonjour a tous, In Dovecot v1.0.alpha2, authentication according domain seems not working passdb = passwd-file /etc/vmail/test.%d %d is not resolved as "domain.name" I browsed on mailing list post and found the problem already reported... What I can't figure out is the answer about it... > Timo Sirainen tss at iki.fi > Fri Jul 22 15:44:02 EEST 2005 > > Trying this and it doesn't work: > > > > passdb = passwd-file /etc/vmail/test.%d > > > > Apparently it doesn't expand the %d according to the log file. > > This has been asked enough now so I just implemented it in CVS. Could be > still optimized a bit, but I think it's fast enough. Could somebody on the list be kind enough to give me some light about this? (is code to do this already implemented (CVS) but not tested yet????) Thanks for your help. A bientot -- ========================================================================== Jean-Marc Pigeon Internet: Jean-Marc.Pigeon(a)safe.ca SAFE Inc. Phone: (514) 493-4280 Fax: (514) 493-1946 REGULUS, a real time accounting/billing package for ISP REGULUS' Home base <"http://www.regulus.safe.ca"> ==========================================================================

2 4

[Dovecot] Dovecot LDAP authentication not working
by Kondwani Masiye 24 Sep '05

24 Sep '05

Hie all, I am new to both Dovecot and this list. I am trying to set up a Dovecot and Sendmail mail server with OpenLDAP user database for authentication. The sendmail setup is working fine, but authentication for Dovemail is not working. When I try to authenticate using POP3, I get an "authentication failed" error, and the logs show the following: Sep 19 16:53:21 tempo slapd[6316]: conn=74 op=2 SRCH base="dc=domain,dc=net" scope=2 deref=0 filter="(&(objectClass=posixAccount)(uid=kondie))" Sep 19 16:53:21 tempo slapd[6316]: conn=74 op=2 SRCH attr=uid userPassword Sep 19 16:53:21 tempo slapd[6316]: <= bdb_equality_candidates: (uid) index_param failed (18) Sep 19 16:53:21 tempo slapd[6316]: conn=74 op=2 SEARCH RESULT tag=101 err=0 nentries=1 text= Sep 19 16:53:21 tempo dovecot: auth(default): ldap(kondie,127.0.0.1): password mismatch Sep 19 16:53:25 tempo dovecot: pop3-login: Aborted login [127.0.0.1] Sep 19 16:53:25 tempo slapd[6313]: conn=72 fd=14 closed I know the password is correct because I am using the same LDAP database from a different server using UW Imap and it works. My dovecot-ldap.conf file below: hosts = localhost dn = cn=dovecot,dc=domain,dc=net ldap_version = 3 base = dc=domain,dc=net deref = never scope = subtree user_attrs = uid,homeDirectory user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid,userPassword pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = CRYPT And the relevant parts (I think) from dovecot.conf file: I have googled all over and also the archives of this list for the last few months but I have not been able to work out what the problem is. As a matter of fact, I have tried to set it up the way it is described here: http://wiki.dovecot.org/moin.cgi/DovecotOpenLdap - but no luck. Could someone please assist in resolving this problem. Any pointers are welcome. Regards, Kondie Masiye -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.1/104 - Release Date: 16/09/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.1/104 - Release Date: 16/09/2005

2 1

[Dovecot] Fatal: EOF reading environment from master
by Marcathian Alexander 24 Sep '05

24 Sep '05

I have been running dovecot as an imap server since 22nd July 2005. The server was started from xinetd using /usr/local/libexec/dovecot/imap-auth The sever run successfully until the machine was shut down in a power outage on 12 Aug 2005. Dovecot has failed to start since the reboot. When starting it with the imap-auth it gives the following error: fatal: EOF reading environment from master I have uninstalled dovecot, downloaded, compiled, and installed the stable of 14Aug 2005 and got the same error. I then installed the 0.99.14 version ang got the same error. Can i have assistance in solving and/or diagnosing the problem? -- Marcathian Alexander SDE Assistant Sustainable Development and Environment Section Ministry of Physical Development, Environment & Housing Open Source Software Evaluation Project - WebMail/Groupware/Collaboaration [Open WebMail Project (http://openwebmail.org)

6 7

[Dovecot] LDA with postfix lock problem
by Rudy Gevaert 24 Sep '05

24 Sep '05

Hello, I'm trying to set up dovecot as the delivery agent for postfix. I configured postfix with: mailbox_command = = /usr/local/libexec/dovecot/deliver In the logs I see the following error: Sep 20 17:19:26 zalm deliver: open(/var/mail/.temp.zalm.8045.65c09c28953ea20c) failed: Permission denied Sep 20 17:19:26 zalm deliver: file_lock_dotlock() failed with mbox file /var/mail/rgevaert: Permission denied Sep 20 17:19:26 zalm postfix/local[8044]: 9790BBE4A: to=<rgevaert(a)zalm.ugent.be>, relay=local, delay=0, status=deferred (temporary failure) Info: zalm:~# ls -ld /var/mail drwxrwsr-x 2 root mail 4096 Sep 20 16:56 /var/mail Giving o write access to the folder fixed it, but not in a way it has to be :) I already added mail_extra_groups = mail to dovecot.conf But this doesn't help. What have I missed. Thanks in advance, -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Rudy Gevaert e-mail: Rudy.Gevaert(a)UGent.be Directie ICT, Afdeling Infrastructuur Groep Systemen tel: +32 9 264 4734 Universiteit Gent fax: +32 9 264 4994 Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

2 1

[Dovecot] auth protocol, buffers
by Thomas Hummel 24 Sep '05

24 Sep '05

Hello Timo, I'm curious about 2 points (I'm using alpha2 but these are general questions) : Background : . I connect to dovecot-1.0.alpha2 through thunderbird . I use ldap pass/userdb and PLAIN mech . I've only got one auth block in dovecot.conf (all pass/userdb/mech except ldap/PLAIN are commented) 1) I notice that, for one thunderbird connection trial, imap-login issues 2 AUTH messages. Why ? What info does the "resp=" hold the second time ? It goes like this : Info: Dovecot v1.0.alpha2 starting up Info: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=xxx.xxx.xxx.xxx rip=xxx.xxx.xxx.xxx Info: auth(default): client out: CONT 1 Info: auth(default): client in: CONT 1 AGRvdmV0ZXN0AGZvbw== Info: auth(default): ldap(dovetest,xxx.xxx.xxx.xxx): base=ou=personnes, dc=pasteur, dc=fr scope=subtree filter=(&(objectClass=posixAccount)(uid=dovetest)) fields=uid,userPassword Info: auth(default): ldap(dovetest,xxx.xxx.xxx.xxx): userPassword(password)={CRYPT}sa8ufSVwLUHVU uid(user)=dovetest Info: auth(default): client out: FAIL 1 user=dovetest Info: auth(default): client in: AUTH 2 PLAIN service=IMAP lip=xxx.xxx.xxx.xxx rip=xxx.xxx.xxx.xxx resp=AGRvdmV0ZXN0AGZvbw== Info: auth(default): ldap(dovetest,157.99.64.42): base=ou=personnes, dc=pasteur, dc=fr scope=subtree filter=(&(objectClass=posixAccount)(uid=dovetest)) fields=uid,userPassword Info: auth(default): ldap(dovetest,157.99.64.42): userPassword(password)={CRYPT}sa8ufSVwLUHVU uid(user)=dovetest dovecot: Sep 20 17:58:27 Info: auth(default): client out: FAIL 2 user=dovetest 2) Which buffer/string handling function (among those in your lib) should I use to safely allocate a string and/or copy a string into another ? (instead of using str[n|l]cpy for instance) ? Thank you. -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

2 1

[Dovecot] 1.0 alpha3 released
by Timo Sirainen 24 Sep '05

24 Sep '05

I'm a bit too busy nowadays because of school so I haven't had time to look at everyone's bug reports and some other mails. They're still marked as unread in my mailbox, so hopefully I'll get to them soon. And I don't mind you resend them if I don't answer in a few weeks :) Changes: - Fixed maildir syncing errors about wrong UIDs - Maildir was re-read all the time, even if we knew nothing had changed there - SSL/TLS connections used to have extra ~0.2s latencies because kernel was waiting for more data before sending it (at least with Linux). Fixed it by corking/uncorking before/after sending. I don't think the socket latencies are this bad normally though, I should probably look more into it if we're setting some socket flags badly (or does it happen specifically because we were using corking for the socket before SSL and kernel increased the timeouts because it thinks we're going to be using corking?). - Marking index file corrupted caused its recreation to still use old transaction log file, which usually caused the index to get corrupted again - Added --build-options parameter to dovecot binary (by Andrey Panin) - Parse obs-phrase correctly in mail address parser (by Chris Wakelin)

5 6

[Dovecot] dovecot with ssl only works on foreground mode
by blaq b0x 24 Sep '05

24 Sep '05

Hi, I've set up dovecot to use imaps/pops with certificates that I signed with my own CA. When I try to start it using service dovecot start it fails. I've tried disabling imaps in the config file and it starts fine so it seems it's the certificate part of the config. If,however, I start it with '/usr/sbin/dovecot -F' or even '/usr/sbin/dovecot' it starts! I've looked over the dovecot startup script but, can't seem to see anything that would hinder startup. I didn't have this problem with self-signed certs??? Can anyone shed some light on this? Thanks, __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

[Dovecot] Multiple authentication databases
by Alexander Shikoff 24 Sep '05

24 Sep '05

Hello, I'm trying to setup multimple auth. databases with Dovecot 1.0 alpha2. I wrote in dovecot.conf next lines (as was described at http://wiki.dovecot.org/moin.cgi/MultipleAuth) auth_debug = yes auth_verbose = yes auth default { mechanisms = plain user = root passdb sql { args = /usr/local/dovecot/etc/dovecot-mysql.conf } passdb pam { args = pop3 } userdb sql { args = /usr/local/dovecot/etc/dovecot-mysql.conf } userdb passwd { } } If user is virtual and placed in SQL database all works perfectly. But system users can not login: Sep 23 12:27:58 orion dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=192.168.5.23 rip=192.168.3.2 resp=AGRtaXRyeQBtb240bHVjY2tpdDQ= Sep 23 12:27:58 orion dovecot: auth-worker(default): sql(user,192.168.3.2): query: SELECT `password` FROM `users` WHERE login = 'user' Sep 23 12:27:58 orion dovecot: auth-worker(default): sql(user,192.168.3.2): unknown user Sep 23 12:27:58 orion dovecot: auth(default): client out: OK 1 user=user Sep 23 12:27:58 orion dovecot: auth(default): master in: REQUEST 19 50448 1 Sep 23 12:27:58 orion dovecot: auth-worker(default): sql(user,192.168.3.2): SELECT "mbox:/var/mail/virtual//user:INBOX=/var/mail/virtual//user:INDEX=MEMORY" AS `mail`, 101 AS `uid`, 101 AS `gid` FROM users WHERE login = 'user' Sep 23 12:27:58 orion dovecot: auth-worker(default): sql(user,192.168.3.2): User not found Sep 23 12:27:58 orion dovecot: pop3-login: Internal login failure: user=<user>, method=PLAIN, rip=192.168.3.2, lip=192.168.5.23 Sep 23 12:27:58 orion dovecot: child 50447 (auth) killed with signal 11 Sep 23 12:27:58 orion dovecot: auth-worker(default): mysql: Connected to 127.0.0.1 (exim) How can I setup multiple auth. databases correctly? Please, help! Thanks in advance, Alexander -- Kind Regards, Alexander Shikoff minotaur(a)crete.org.ua Mob.: +380 67 946 31 49

2 2

[Dovecot] Secure file messages
by zeotavio 24 Sep '05

24 Sep '05

Hi Qualquer pessoa sabe o que isto significa? dovecot-auth: pam_succeed_if: requirement "uid < 100" not met by user "marinho" This message appears for several users. (in the file /var/log/secure) I am grateful for your attention. José Otávio.

2 1

[Dovecot] Maildir and folders not under INBOX
by Oliver Schulze L. 24 Sep '05

24 Sep '05

Hi, I'm planning to migrate from dovecot/mbox to dovecot/maildir both using imap. I have read that when using the Maildir storage format, all folders are stored under the INBOX. Is this true in dovecot too? I want to have a configuration like the current: - new mail is delivered in /var/mail/USER - user folders are in /home/USER/mail I want to ask if this is posible in dovecot? Maybe using a config like this: default_mail_env = maildir:/home/%u/Maildir:INBOX=/var/mail/%u/Maildir Thanks Oliver -- Oliver Schulze L. <oliver(a)samera.com.py>

2 2

[Dovecot] Moving messages takes a longgggggg..... time. (Timeouts?) dovecot.conf help?
by Rob Frohne 23 Sep '05

23 Sep '05

Hi, I'm trying to get dovecot set up better. I am using 1.0alpha3. It takes a long long time to move messages for some reason. It seems it may be a timeout thing, because neither the client or server is using any cpu time or disk i/o or network to speak of. (To move maybe 400 messages, it seems to take maybe half an hour, maybe longer.) With alpha 2 I was getting messages from Thunderbird saying that the server was unable to move messages, would I like to continue. I haven't seen any of these lately, but when I updated to alpha3 I also made some dovecot.conf changes. I'm running this on OS X with a 450 MHz cube with 1.2 Gig of ram and a 7200 RPM hard drive. I have a lot of rules that move messages to various mailboxes and I get a lot of mail, so this is important to me. I have a very large Maildir set of mailboxes (about 40 of them with up to 70,000 messages in each mailbox). I have finally got it so that it will load the mailbox headers pretty quickly in Thunderbird. It takes about 15 to 30 seconds to load a message, but that is acceptable to me. Here is my dovecot.conf. Can anyone give me some tips? ## Dovecot 1.0 configuration file # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var # --with-ssldir=/etc/ssl # Base directory where to store runtime data. base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s #protocols = imap imaps # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. If you want to specify ports # for each service, you will need to configure these settings inside the # protocol imap/pop3 { ... } section, so you can specify different ports # for IMAP/POP3. #listen = * # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = # Disable SSL/TLS support. ssl_disable = yes # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf #ssl_cert_file = /etc/ssl/certs/dovecot.pem #ssl_key_file = /etc/ssl/private/dovecot.pem # File containing trusted SSL certificate authorities. Usually not needed. #ssl_ca_file = # Request client to send a certificate. #ssl_verify_client_cert = no # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 24 # SSL ciphers to use #ssl_cipher_list = ALL:!LOW # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. disable_plaintext_auth = no # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). #log_path = # For informational messages, use this logfile instead of the default #info_log_path = # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = /var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. # http://wiki.dovecot.org/Rootless #login_chroot = yes # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. # Note that this user is NOT used to access mails. # http://wiki.dovecot.org/UserIds #login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. login_process_size = 4096 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. login_process_per_connection = no # Number of login processes to create. If login_process_per_user is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_user # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 # Greeting message for clients. #login_greeting = Dovecot ready. # Space-separated list of elements we want to log. The elements which have # a non-empty variable value are joined together to form a comma-separated # string. #login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c # Login log format. %$ contains login_log_format_elements string, %s contains # the data we want to log. #login_log_format = %$: %s ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 max_mail_processes = 4096 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no verbose_proctitle = yes # Show protocol level SSL errors. #verbose_ssl = no verbose_ssl = yes # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. #mail_extra_groups = mail_extra_groups = mail # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See doc/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden for # specific users in user database by giving /./ in user's home directory # (eg. /home/./user chroots into /home). Note that usually there is no real # need to do chrooting, Dovecot doesn't allow users to access files outside # their mail directory anyway. #mail_chroot = # Enable mail process debugging. This can help you figure out why Dovecot # isn't finding your mails. #mail_debug = no mail_debug=yes # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # doc/mail-storages.txt. There's a few special variables you can use, eg.: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if there's no domain # %h - home directory # # See doc/variables.txt for full list. Some examples: # # default_mail_env = maildir:/var/mail/%1u/%u/Maildir # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # #default_mail_env = mbox:~/Library/Mail/Mailboxes:INBOX=/var/mail/%u default_mail_env = maildir:%h/Maildir # If you need to set multiple mailbox locations or want to change default # namespace settings, you can do it by defining namespace sections: # # You can have private, shared and public namespaces. The only difference # between them is how Dovecot announces them to client via NAMESPACE # extension. Shared namespaces are meant for user-owned mailboxes which are # shared to other users, while public namespaces are for more globally # accessible mailboxes. # # REMEMBER: If you add any namespaces, the default namespace must be added # explicitly, ie. default_mail_env does nothing unless you have a namespace # without a location setting. Default namespace is simply done by having a # namespace with empty prefix. #namespace private { # Hierarchy separator to use. You should use the same separator for all # namespaces or some clients get confused. '/' is usually a good one. #separator = / # Prefix required to access this namespace. This needs to be different for # all namespaces. For example "Public/". #prefix = # Physical location of the mailbox. This is in same format as # default_mail_env, which is also the default for it. #location = # There can be only one INBOX, and this setting defines which namespace # has it. #inbox = yes # If namespace is hidden, it's not advertised to clients via NAMESPACE # extension or shown in LIST replies. This is mostly useful when converting # from another server with different namespaces which you want to depricate # but still keep working. For example you can create hidden namespaces with # prefixes "~/mail/", "~%u/mail/" and "mail/". #hidden = yes #} # Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # # flags, date.sent, date.received, size.virtual, size.physical # mime.parts, imap.body, imap.bodystructure # # Different IMAP clients work in different ways, so they benefit from # different cached fields. Some do not benefit from them at all. Caching more # than necessary generates useless disk I/O, so you don't want to do that # either. # # Dovecot attempts to automatically figure out what client wants and it keeps # only that. However the first few times a mailbox is opened, Dovecot hasn't # yet figured out what client needs, so it may not perform optimally. If you # know what fields the majority of your clients need, it may be useful to set # these fields by hand. If client doesn't actually use them, Dovecot will # eventually drop them. # # Usually you should just leave this field alone. The potential benefits are # typically unnoticeable. #mail_cache_fields = # Space-separated list of fields that Dovecot should never save to cache file. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Like mailbox_check_interval, but used for IDLE command. #mailbox_idle_check_interval = 30 mailbox_idle_check_interval = 15 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no # Maximum allowed length for mail keyword name. It's only forced when trying # to create new keywords. #mail_max_keyword_length = 50 mail_max_keyword_length = 250 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. # Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes. #mail_read_mmaped = no # Don't use mmap() at all. This is required if you store indexes in remote # filesystems (NFS or clustered filesystem). #mmap_disable = no # Don't write() to mmaped files. This is required for some operating systems # which use separate caches for them, such as OpenBSD. #mmap_no_write = no # Locking method for index files. Alternatives are fcntl, flock and dotlock. # Dotlocking uses some tricks which may create more disk I/O than other locking # methods. #lock_method = fcntl # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no maildir_copy_with_hardlinks = yes # Which locking methods to use for locking mbox. There's four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist in all systems. Doesn't work with NFS. # # You can use multiple locking methods; if you do the order they're declared # in is important to avoid deadlocks if other MTAs/MUAs are using multiple # locking methods as well. Some operating systems don't allow using some of # them simultaneously. #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # When mbox changes unexpectedly we have to fully read it to find out what # changed. If the mbox is large this can take a long time. Since the change # is usually just a newly appended mail, it'd be faster to simply read the # new mails. If this setting is enabled, Dovecot does this but still safely # fallbacks to re-reading the whole mbox file whenever something in mbox isn't # how it's expected to be. The only real downside to this setting is that if # some other MUA changes message flags, Dovecot doesn't notice it immediately. # Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK # commands. #mbox_dirty_syncs = yes # Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE, # EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored. #mbox_very_dirty_syncs = no # Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK # commands and when closing the mailbox). This is especially useful for POP3 # where clients often delete all mails. The downside is that our changes # aren't immediately visible to other MUAs. #mbox_lazy_writes = yes # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. It could be a small # security risk if you use single UID for multiple users, as the users could # ptrace() each others processes then. #mail_drop_priv_before_exec = no # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #mail_process_size = 256 mail_process_size = 4096 # Log prefix for mail processes. See doc/variables.txt for list of possible # variables you can use. #mail_log_prefix = "%Us(%u): " ## ## IMAP specific settings ## protocol imap { # Login executable location. #login_executable = /usr/libexec/dovecot/imap-login # IMAP executable location #mail_executable = /usr/libexec/dovecot/imap # This would write rawlogs into ~/dovecot.rawlog/ directory: #mail_executable = /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap # Maximum IMAP command line length in bytes. Some clients generate very long # command lines with huge mailboxes, so you may need to raise this if you get # "Too long argument" or "IMAP command line too large" errors often. #imap_max_line_length = 65536 imap_max_line_length = 262144 # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/imap # Send IMAP capabilities in greeting message. This makes it unnecessary for # clients to request it with CAPABILITY command, so it saves one round-trip. # Many clients however don't understand it and ask the CAPABILITY anyway. #login_greeting_capability = no # Workarounds for various client bugs: # delay-newmail: # Send EXISTS/RECENT new mail notifications only when replying to NOOP # and CHECK commands. Some clients ignore them otherwise, for example # OSX Mail. Outlook Express breaks more badly though, without this it # may show user "Message no longer in server" errors. Note that OE6 still # breaks even with this workaround if synchronization is set to # "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. # netscape-eoh: # Netscape 4.x breaks if message headers don't end with the empty "end of # headers" line. Normally all messages have this, but setting this # workaround makes sure that Netscape never breaks by adding the line if # it doesn't exist. This is done only for FETCH BODY[HEADER.FIELDS..] # commands. Note that RFC says this shouldn't be done. # tb-extra-mailbox-sep: # With mbox storage a mailbox can contain either mails or submailboxes, # but not both. Thunderbird separates these two by forcing server to # accept '/' suffix in mailbox names in subscriptions list. #imap_client_workarounds = outlook-idle imap_client_workarounds = delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. #login_executable = /usr/libexec/dovecot/pop3-login # POP3 executable location #mail_executable = /usr/libexec/dovecot/pop3 # Don't try to set mails non-recent or seen with POP3 sessions. This is # mostly intended to reduce disk I/O. With maildir it doesn't move files # from new/ to cur/, with mbox it doesn't write Status-header. #pop3_no_flag_updates = no # Support LAST command which exists in old POP3 specs, but has been removed # from new ones. Some clients still wish to use this though. Enabling this # makes RSET command clear all \Seen flags from messages. #pop3_enable_last = no # POP3 UIDL format to use. You can use following variables: # # %v - Mailbox UIDVALIDITY # %u - Mail UID # %m - MD5 sum of the mailbox headers in hex (mbox only) # %f - filename (maildir only) # # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier version 0 : %f # Courier version 1 : %u # Courier version 2 : %v-%u # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # # Note that Outlook 2003 seems to have problems with %v.%u format which is # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. #pop3_uidl_format = %v.%u # POP3 logout format string: # %t - number of TOP commands # %T - number of bytes sent to client as a result of TOP command # %r - number of RETR commands # %R - number of bytes sent to client as a result of RETR command # %d - number of deleted messages # %m - number of messages (before deletion) # %s - mailbox size in bytes (before deletion) #pop3_logout_format = top=%t/%T, retr=%r/%R, del=%d/%m, size=%s # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. # oe-ns-eoh: # Outlook Express and Netscape Mail breaks if end of headers-line is # missing. This option simply sends it if it's missing. #pop3_client_workarounds = } ## ## Authentication processes ## # Executable location #auth_executable = /usr/libexec/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # Authentication cache size in kilobytes. #auth_cache_size = 0 # Time to live in seconds for cached data. After this many seconds a cached # record is forced out of cache. #auth_cache_ttl = 3600 # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username character translations before it's looked up from databases. The # value contains series of from -> to characters. For example "#@/@" means # that '#' and '/' characters are translated to '@'. #auth_username_translation = # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. auth_verbose = yes # Even more verbose logging for debugging purposes. Shows for example SQL # queries. #auth_debug = no # Maximum number of dovecot-auth worker processes. They're used to execute # blocking passdb and userdb queries (eg. MySQL and PAM). They're # automatically created and destroyed as needed. #auth_worker_max_count = 30 auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous mechanisms = plain # # Password database is used to verify user's password (and nothing more). # You can have multiple passdbs and userdbs. This is useful if you want to # allow both system users (/etc/passwd) and virtual users to login without # duplicating the system users into virtual database. # # http://wiki.dovecot.org/Authentication # # PAM authentication. Preferred nowadays by most systems. # Note that PAM can only be used to verify if user's password is correct, # so it can't be used as userdb. If you don't want to use a separate user # database (passwd usually), you can use static userdb. passdb pam { # [-session] [<service name>] # # -session makes Dovecot open and immediately close PAM session. Some # PAM plugins need this to work. # # If service name is "*", it means the authenticating service name # is used, eg. pop3 or imap. args = imap #args = dovecot } # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. #passdb passwd { #} # /etc/shadow or similiar, using getspnam(). Deprecated by PAM nowadays. #passdb shadow { #} # passwd-like file with specified location #passdb passwd-file { # Path for passwd-file #args = #} # checkpassword executable authentication #passdb checkpassword { # Path for checkpassword binary #args = #} # SQL database #passdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for example #args = #} # LDAP database #passdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example #args = #} # vpopmail authentication #passdb vpopmail { #} # # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # # http://wiki.dovecot.org/Authentication # http://wiki.dovecot.org/VirtualUsers # # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. userdb passwd { } # passwd-like file with specified location #userdb passwd-file { # Path for passwd-file #args = #} # static settings generated from template #userdb static { # Template for settings. Can return anything a userdb could normally # return, eg.: uid, gid, home, mail, nice # # A few examples: # # args = uid=500 gid=500 home=/var/mail/%u # args = uid=500 gid=500 home=/home/%u mail=mbox:%h/mail nice=10 # #args = #} # SQL database #userdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for example #args = #} # LDAP database #userdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example #args = #} # vpopmail #userdb vpopmail { #} # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by userdb above. user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. # Note that valid_chroot_dirs isn't needed to use this setting. #chroot = # Number of authentication processes to create #count = 1 # Require a valid SSL client certificate or the authentication fails. #ssl_require_client_cert = no } # It's possible to export the authentication interface to other programs, # for example SMTP server which supports talking to Dovecot. Client socket # handles the actual authentication - you give it a username and password # and it returns OK or failure. So it's pretty safe to allow anyone access to # it. Master socket is used to a) query if given client was successfully # authenticated, b) userdb lookups. # listener sockets will be created by Dovecot's master process using the # settings given inside the auth section #auth default_with_listener { # mechanisms = plain # passdb passwd { # } # userdb pam { # } # socket listen { # master { # path = /var/run/dovecot/auth-master # #mode = 0600 # # Default user/group is the one who started dovecot-auth (root) # #user = # #group = # } # client { # path = /var/run/dovecot-auth-client # mode = 0660 # } # } #} # connect sockets are assumed to be already running, Dovecot's master # process only tries to connect to them. They don't need any other settings # than path for the master socket, as the configuration is done elsewhere. # Note that the client sockets must exist in login_dir. #auth external { # socket connect { # master { # path = /var/run/dovecot/auth-master # } # } #} Thanks! Rob

1 0

[Dovecot] signing dovecot certs with own Cert. Auth.
by blaq b0x 23 Sep '05

23 Sep '05

Hi, I'm trying to get apache, sendmail , and dovecot to use SSL certs signed by my own CA. I've got the apache certs working fine. However, dovecot ( I haven't even tried sendmail yet) doesn't seem to accept any of the certificates that I create for it. There is a script that comes with dovecot that creates self-signed certificates for you but, I need certificates signed by my own CA. I found this tutorial http://homepage.mac.com/pauljlucas/personal/macmini/certs.html it shows you how to create a csr for dovecot that you can send to a CA. I signed it using CA.pl -sign. however, the certificate isn't accepted by dovecot. Unfortunately, dovecot doesn't log anything to maillog at failed startup. Just looking at the certificate contents I noticed that the self-signed certificates don't have all kinds of publisher information at the beginning of them like the apache certs. So I think what I'm missing is the difference between all the different cert types. I know that there are pem and cert ssl cert types, at least different extensions. Can anyone tell my what the difference is? are the certs suitable for apache and others for mail applications? is there a converter? Could it be the way that I'm signing the certificates? Any help would be appreciated. Thanks, Reply With Quote __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

6 8

[Dovecot] login_process_per_user referred to but not present in dovecot.conf?
by Rob Frohne 23 Sep '05

23 Sep '05

Hi, I find login_process_per_user referred to in the comments in dovecot.conf, but never set. Is this a typo and should it be login_process_per_connection or what? Thanks, Rob

2 1

[Dovecot] Lost transaction log file in alpha2
by James Berry 23 Sep '05

23 Sep '05

I had run alpha1 pretty uneventfully for several weeks. I upgraded to alpha2 a couple of days ago and have since suffered two incidents of "Lost transaction log", resulting in the client being unable to access the mailbox until I "rm dovecot.index.log*" Sep 14 10:48:35 caddy dovecot: imap(jberry): Lost transaction log file /Users/jberry/Maildir/dovecot.index.log seq 1 I should point out that this is a server with a single imap user (myself) and that I know only one imap client was trying to access the server at that point in time (though the client sw Mail.app may have had multiple connections to the server). Any suggestions/ideas/thoughts on whether something might have changed in alpha2 to start causing this? James.

2 4

[Dovecot] auth-master socket access
by Lieven Van Acker 23 Sep '05

23 Sep '05

Hey, I'm doing a setup of dovecot (cvs) + postfix + dovecot lda (cvs). Is there any solution to the /var/run/dovecot/auth-master access restrictions, prohibiting the user running dovecot-deliver from communicating with the master (aside from the dirty and unsafe hack to reset the permissions of the /var/run/dovecot dir after starting dovecot)? Thanks, Lieven

3 2

[Dovecot] Can't donwload mails with some attacchments
by Lethux 23 Sep '05

23 Sep '05

Hi. Does anyone find the same problem with attachments bigger than few Ks? The client (thunderbird) waits for the file to be downloaded. It can be waiting for several minuts and tryies before having it from dovecot. Can it be something against the lock of the file, the processes or something else? Any workaround or bugfix in the stable/alpha rel? thanks. L.

2 1

[Dovecot] Shared access to mail accounts.
by Rory Campbell-Lange 23 Sep '05

23 Sep '05

We are intending to have some project mail accounts which many people (up to 10) will share. Will this work? Our configuration uses imap only, with maildir format mail storage. Thanks Rory -- Rory Campbell-Lange <rory(a)campbell-lange.net> <www.campbell-lange.net>

3 4

[Dovecot] Is Alpha2 slower than Alpha1?
by Marc Perkel 23 Sep '05

23 Sep '05

I changed servers at the same time as changing from Alpha1 to Alpha2 but I'm on a faster server so it should be faster. But it seems slower especially deleting server side messages. Using mbox . Anyone else seeing tis?

2 1

[Dovecot] Basic namespaces question
by David King 23 Sep '05

23 Sep '05

I can't find a generalised "What the heck are namespaces all about?" anywhere, can anyone point me to a decent one? More directly, my question is this: if I set up two non-hidden private namespaces (one for mbox and one for maildir), will a well-written IMAP client automagically list folders from both as if they were part of (or below) the same hierarchy, or do I have to set up two accounts, one with a prefix of (say) #mbox and one of #maildir? One step further, I'd like to eventually get mail from /var/mail/%u in mbox format, and in "maildir:%h/.maildir" or "mbox:%h/.mail", whichever exists (I'm migrating from imap-uw, and would like the benefits of maildir without forcing users to change their mailstores in case they use pop3 or tools like mail(1)). I'm willing to do some coding for it, but I imagine that it would be non-trivial if namespaces aren't automatically integrated

2 1

[Dovecot] courier imap --> dovecot imap
by Paul 'Google' Smit 23 Sep '05

23 Sep '05

Dear Readers of tha list... Please help me out! I currenty have Dovecot Imap installed but I still have some old Courier Imap files from an old server which I want to use. Can I, in any way, import of convert them so I can use it? Regards, Millman ------------------------------- Linux: Fedora Core 4 Sendmail: 8.13.4-2 Dovecot: 0.99.14-4 Squirrelmail: 1.4.6-0 -------------------------------

3 3

[Dovecot] trying to see different files
by David Willoughby 23 Sep '05

23 Sep '05

i am wanting to sort my email into different files per the different email lists i use. i've posted this before but nobody responded. is it possible to use dovecot and sort my mail into /home/dlw/Mail/file1, file2 etc.... ? -- David Willoughby email: dlw(a)d1w.org icq: 1852393

7 8

[Dovecot] bug? Maildir ... sync: UID inserted in the middle of mailbox
by Peter Gervai 23 Sep '05

23 Sep '05

Version: 1.00alpha2 Error: imap(grin): Maildir /home/grin/Maildir sync: UID < next_uid (94 < 95, file = 1127311363.H977932P25148.gollum:2,) imap(grin): Maildir /home/grin/Maildir sync: UID inserted in the middle of mailbox (95 > 94, file = 1127311363.H977932P25148.gollum:2,) This error reappears frequently. Doesn't go away by restarting dovecot, but does go away when I delete all index and cache and whatnot (and restart dovecot). Appears in 10 minutes again... Could be sylpheed-claws-whatever-alpha imap problem, but whatever the client does dovecot shouldn't be fall apart I believe. Peter

3 2

[Dovecot] Another address-spec problem
by Chris Wakelin 23 Sep '05

23 Sep '05

I've had complaints from users about "MISSING_DOMAIN" in header fields and I've tracked it down to having "." in an unquoted display name. By my reading of RFC2822 (especially section 4.1) A N Other <a.n.other(a)somewhere.org> "A. N. Other" <a.n.other(a)somewhere.org> are legal, but A. N. Other <a.n.other(a)somewhere.org> is "obsolete", but should be supported by the server (no clients should do it). I think the relevant syntax is phrase = 1*word / obs-phrase word = atom / quoted-string obs-phrase = word *(word / "." / CFWS) and rfc822_parse_phrase() should be modified to cope with "obs-phrase". I'll have a go, but if Timo or anybody knows how to do it properly, that would be better! Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 2

[Dovecot] Debian packages of alpha2?
by Ben Beuchler 23 Sep '05

23 Sep '05

Is anyone maintaining Debian packages of alpha2? The official packages aren't even up to -stable yet. -Ben

2 1

[Dovecot] virtual passwords
by Michael Collins 22 Sep '05

22 Sep '05

I just set up postfix with some virtual domains and users. Dovecot made some dbs in /etc/dovecot. a passdb and userdb. the passdb file has passwords in there and I want to at least know what it is. I have tried to do 'echo -n mypassword | openssl md5 -hex' and insert that into them but it seems to not work. Probably something I am doing wrong. I looked at the archive and could not figure out how to search it. Anyway how do i change a password? Thanks. this is passdb: andreux@bla.com:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 andrew@bla.com:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 sikki@bla.com:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 amanda@bla.com:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 info@bla.com:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 help@bla.com:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 andrew@blu.biz:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 andreux@blu.biz:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 eric@blu.biz:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 jjenkins@blu.biz:$1$G/FqlOG5$Vj0xmc9fKY.UVr8OWr/7C1 -- -- Michael H. Collins It's us against them. Ride like you stole it. If you love some code, set it free. Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html

1 0

[Dovecot] problem with postgreSQL connect=
by octane indice 22 Sep '05

22 Sep '05

Hello I'm using dovecot with virtual accounts stored in a postgreSQL db. I use in the dovecot.conf: auth_userdb = pgsql /usr/local/etc/dovecot-pgsql-user.conf (and same for pass). In the file dovecot-pgsql-user.conf, I use: connect = host=127.0.0.1 dbname=vmail user=lecteur password=lire user_query = SELECT '/var/spool/vhosts/'||nom_domaine||'/'||nom_boite AS mail,5000 AS uid, 5000 AS gid FROM boites WHERE email = '%u' It doesn't work. If I write: connect = dbname=vmail user=lecteur user_query = SELECT '/var/spool/vhosts/'||nom_domaine||'/'||nom_boite AS mail,5000 AS uid, 5000 AS gid FROM boites WHERE email = '%u' It works. Of course the query with psql works: psql -U lecteur -h 127.0.0.1 vmail -c "SELECT '/var/spool/vhosts/'||nom_domaine||'/'||nom_boite AS mail,5000 AS uid, 5000 AS gid FROM boites WHERE email = '%u' " with the password 'lire' My question: do I make something wrong? I want to use the network, because in future, dovecot will not be on the same host than postgreSQL. Thanks --------------------------------------------- Etes vous un consom'Acteur ? Toutes les saveurs équitables sont sur http://www.epicerie-equitable.com

1 0

[Dovecot] Lost transaction log file /Users/frohro/Maildir/dovecot.index.log.2 seq 1
by Rob Frohne 22 Sep '05

22 Sep '05

Hi, I got a bunch of the following errors: Lost transaction log file /Users/frohro/Maildir/dovecot.index.log.2 seq 1 when I was trying to apply some rules to move messages from one mailbox to another. Things hadn't been working well and I had recently upgraded to alpha 2, so I moved all dovecot* files in my Maildir/. Things then seem to work better. Rob -- Rob Frohne, Ph.D., P.E. E.F. Cross School of Engineering Walla Walla College http://www.wwc.edu/~frohro/

1 0

[Dovecot] Weird series of errors with dovecot-stable
by Ben Beuchler 21 Sep '05

21 Sep '05

I'm using the dovecot-stable from 7/30, authenticating against an OpenLDAP server. From time to time, dovecot stops responding to new queries. It seems to be a self-correcting problem, lasting about 20 minutes. Here's how it starts: Aug 18 19:38:23 cliff dovecot: imap-login: Disconnected: Inactivity [150.253.42.12] Aug 18 19:38:36 cliff dovecot: pop3-login: Disconnected: Inactivity [68.46.174.217] Aug 18 19:39:35 cliff dovecot: imap-login: Disconnected: Inactivity [150.253.42.12] Normally I see almost no "Disconnected: Inactivity" messages, but when this problem shows up I get an almost non-stop barrage of them. In fact, over the 20 minutes or so, there's about 150 of those entries, so I filtered them out of the log snippets. I also filtered out any "normal" activity during the time period. Here's what's left: Aug 18 19:40:29 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:40:29 cliff dovecot: child 22347 (auth) killed with signal 6 Aug 18 19:42:04 cliff dovecot: auth(ldap): ldap(vmail,150.253.80.31): unknown user Aug 18 19:42:41 cliff dovecot: imap-login: SSL_read() syscall failed: EOF [24.26.184.219] Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:31 cliff dovecot: auth(ldap): Login process has too old (121s) requests, killing it. Aug 18 19:43:43 cliff dovecot: auth(ldap): Login process has too old (121s) requests, killing it. Aug 18 19:43:43 cliff dovecot: auth(ldap): Login process has too old (122s) requests, killing it. Aug 18 19:43:49 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:43:49 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:43:49 cliff dovecot: child 22557 (auth) killed with signal 6 Aug 18 19:43:49 cliff dovecot: child 22562 (login) returned error 89 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:32 cliff dovecot: child 22522 (login) returned error 89 Aug 18 19:45:32 cliff dovecot: child 22561 (login) returned error 89 Aug 18 19:45:32 cliff dovecot: child 22563 (login) returned error 89 Aug 18 19:45:32 cliff dovecot: child 22564 (login) returned error 89 Aug 18 19:45:32 cliff dovecot: child 22566 (login) returned error 89 Aug 18 19:47:54 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:47:54 cliff dovecot: child 22599 (auth) killed with signal 6 Aug 18 19:48:18 cliff dovecot: imap-login: SSL_read() syscall failed: EOF [69.81.39.120] Aug 18 19:48:18 cliff dovecot: imap-login: SSL_read() syscall failed: EOF [69.81.39.120] Aug 18 19:51:32 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:51:32 cliff dovecot: child 22628 (auth) killed with signal 6 Aug 18 19:54:14 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:54:14 cliff dovecot: child 22655 (login) returned error 89 Aug 18 19:54:14 cliff dovecot: child 22683 (login) returned error 89 Aug 18 19:54:14 cliff dovecot: child 22686 (auth) killed with signal 6 Aug 18 19:54:14 cliff dovecot: child 22689 (login) returned error 89 Aug 18 19:54:14 cliff dovecot: child 22690 (login) returned error 89 Aug 18 19:54:14 cliff dovecot: child 22699 (login) returned error 89 Then, magickally, it begins working again. Any thoughts? -Ben

2 1