- dovecot - dovecot.org

[Dovecot] mysql
by Jim Edwards 12 Jul '05

12 Jul '05

Hello, Does dovecot require mysql in order to work? Fedora rpms are claiming mysql dependencies. I'm sure you're aware of the long-lived arguement of postgresql v. mysql. If it wasn't your intention to force this, then please snarl at Red Hat. If it was your intention, then grrrrr! Thanks for this product. I like it for it's speed and stability. Jim Edwards

4 3

[Dovecot] bug: very strange behavior with pop3
by Yannick Majoros 12 Jul '05

12 Jul '05

Hello, We have some strange problem which could be related to authentication here. All our user info is in an openldap directory. We normally use pam/getpwent in dovecot to access our user accounts, via nss_ldap/pam_ldap, but we tried to connect directly to the ldap server, with the very same results. We have one user (out of 100) which just cannot use dovecot with pop3. His login/password are accepted, and then dovecot doesn't say anything. I am sure it isn't a client issue: same result with Eudora, Thunderbird and while directly connecting through openssl to POP3s port and "talking POP3". Here is some session transcript: +OK dovecot ready. USER rinstalle +OK PASS M=/)p365 +OK Logged in. And it then stops responding (without giving a reason, breaking the connection). Nothing in the logs, it sees this as a regular login and that's all... Now, it seems that when I copy this user in ldap, the new one occasionaly works. I first thought it did depend on the user name (uid or dn), but it doesn't seem to be the case. I think it is just random. Here is an ldif of this user: dn: uid=rinstalle,ou=divers,ou=login,ou=Autres,ou=Personnes,dc=inma,dc=ucl,dc= ac,dc=be uid: rinstalle cn: compte foireux homeDirectory: /home/xx sn: xxxx uidNumber: 9999 objectClass: top objectClass: person objectClass: inetOrgPerson objectClass: posixAccount gidNumber: 999 ... And getent result (with nss_ldap): #getent passwd rinstalle rinstalle:x:9999:999:compte foireux:/home/xx: To be complete, I should mention that it _does_ work when using local password files... I solved the user problem just by copying his entry a few times. Now, I don't think it is purely ldap-related, as the login _is_ accepted. Is there some guru out here who could help us? Thank you, -- ---------------------------------------------------------------------- Yannick Majoros http://www.inma.ucl.ac.be/~majoros Informaticien AUTO-INMA/FSA/UCL CSAM 4, avenue G. Lemaître B-1348 Louvain-la-Neuve Belgium Tel: +32-10-47.80.10 Fax: +32-10-47.21.80 #JAPH : http://www.inma.ucl.ac.be/~majoros/japh.txt Si vous avez des problèmes pour afficher ce message (accents qui ne passent pas, signature électronique, ...) votre système de mail n'est pas conforme aux standards, voir http://www.inma.ucl.ac.be/~majoros/email.html ----------------------------------------------------------------------

2 4

[Dovecot] weird IDLE behaviour
by Johannes Berg 12 Jul '05

12 Jul '05

Hi, So I was testing things with inotify notifications enabled and noticed that when I a) select a mailbox other than the inbox b) IDLE c) copy mail into the /new folder in that mailbox nothing happens! So I straced it and it always opens the inbox's new/ and cur/ directories for notifications. Is that the correct behaviour? I assumed that if I select some mailbox other than the inbox, IDLE should inform me of status updates in that box, since RFC 2177 says: The Internet Message Access Protocol [IMAP4] requires a client to poll the server for changes to the selected mailbox (new mail, deletions). Now, I get this behaviour by applying the attached patch. But even if I'm wrong, dovecot doesn't implement any sensible behaviour, as it only ever creates *any* notifications during IDLE when the INBOX is selected. [hm. note that I'm only testing maildir] johannes

2 1

[Dovecot] xinetd + dovecot
by vlad 12 Jul '05

12 Jul '05

Hello dovecot, Help me running imapd & pop3d server on xinetd. My file: # cat /etc/xinetd.d/pop-3 service pop3 { disable = no socket_type = stream protocol = tcp wait = no user = root server = /usr/libexec/dovecot/pop3-login } ####################################### # cat /etc/xinetd.d/imap service imap { disable = no socket_type = stream protocol = tcp wait = no user = root server = /usr/libexec/dovecot/imap-login flags = IPv4 log_type = FILE /var/log/mail/dovecot log_on_success = PID HOST USERID } ####################################### But... # nmap 192.168.1.1 Starting nmap 3.70 ( http://www.insecure.org/nmap/ ) at 2005-07-12 16:53 YEKST Interesting ports on myhost.ru (192.168.1.1): (The 1653 ports scanned but not shown below are in state: closed) PORT STATE SERVICE 25/tcp open smtp 80/tcp open http 110/tcp open pop3 143/tcp open imap 3128/tcp open squid-http ########### # telnet 192.168.1.1 143 Trying 192.168.1.1... Connected to 192.168.1.1. Escape character is '^]'. Fatal: EOF while reading environment from master Connection closed by foreign host. # telnet 192.168.1.1 110 Trying 192.168.1.1... Connected to 192.168.1.1. Escape character is '^]'. Fatal: EOF while reading environment from master Connection closed by foreign host. Help :) -- With best wishes, vlad mailto:faktroot@mail.ru System/Network Administrator TV/Video Engineer ICQ 163227020 ---------------------------------------------- В любом из нас спит гений. И с каждым днем все крепче...

2 1

[Dovecot] POP retrieval, then reading, of mail does not udpate server status.
by Paul Vatta 12 Jul '05

12 Jul '05

We are currently using the version of Dovecot (0.99.11) that comes with Redhat Enterpise Linux version 4, running on an IBM x445 server (8 CPU, hyperthreading on, 14GB RAM) using the maildir format. We have had to patch this with a change from 0.99.12 so that it doesn't incorrectly report SASL capability upon connection but otherwise it is the version supplied with the OS (we do this to ensure that we don't deviate from the supplied packages too much). The problem encountered is the status of emails on the server isn't being updated. The POP client (Eudora 6.2 in this instance) will retrieve the message, have the message read, apparently update the status on the server (via the "Check Mail" function), but yet the status on the server has not been updated as read (verified by going into our IMP Webmail client, and looking at the mail message in the mailstore - there is no ".S" extension). Using the IMAP protocol doesn't bring about this behaviour. The inconsistency The inconsistency between POP clients and the server status doesn't occur when it comes to deleting messages. Is this a bug, or have we misunderstood how the POP protocol works. Looking at the following: http://www.eudora.com/techsupport/kb/2587hq.html I'm guessing that the POP protocol doesn't update the status? Your confirmation would be most appreciated. Thanks, Paul P.S. As an aside, if you are hesitant about the move from mbox to maildir, don't consider this an obstacle. Our migration was painless and the benefits far outweigh the conversion effort. Dovecot has introduced huge improvements over our Qpopper/UW-IMAP configuration.

2 1

[Dovecot] Calypso or Opera Mail problem?
by Obantec Support 12 Jul '05

12 Jul '05

Hi Are there any know issues with dovecot using pop3 & (Calypso or Opera Mail) ? Jul 11 09:14:47 proteus2a pop3(cambcom_brianlj): File isn't in mbox format: /var/spool/mail/cambcom_brianlj Jul 11 09:14:47 proteus2a pop3(cambcom_brianlj): Couldn't open INBOX: Internal error occurred. Error report written to server log. [2005-07-11 09:14:47 there is a file cambcom_brianlj and using webmin or neomail the mails can be read. Mark -- Obantec Support

2 1

Re: [Dovecot] mysql
by Dominic Marks 12 Jul '05

12 Jul '05

On Tuesday 12 July 2005 14:55, Peter Evans wrote: > Tomi Hakala (tomi.hakala(a)clinet.fi) wrote: > > Jim Edwards wrote: > > > Does dovecot require mysql in order to work? > > > > For common email serving with IMAP and POP3, no. > > For IMAP and POP3 session proxying with 1.0-test releases, yes. > > Ew, YUCK. > Why does everyone think $DATABASE is the panacea for all ills? Why you think this is a misuse of a database? Shared network storage might not have been the original purpose, but most DBs can do a pretty good job of this. > Just because they can't/won't cope with multiplicity, does not > mean that X megabytes of general purpose database and all the > overheads have to be used. I can't tell if you have a problem with databases in general, or just the MySQL implementation from this. I guess that you could modify the code easily to use another DBMS which is much smaller such as sqlite. > If it's just proxying, why can't it speak LDAP, or even just a > plain file ... Why write code from scratch when you can use an API for a trusted piece of software which is likely to be available on most systems already? > P > > (I haven't looked at 1.0-test-903 yet, I think I'm still on 70 > something, but no way am I installing mysql ...) Cheers, -- Dominic Marks

1 0

[Dovecot] Mail spools keep getting corrupted with .99.x
by Matt Juszczak 12 Jul '05

12 Jul '05

Hi all, My mail spools (mbox format) keep getting corrupted with .99.x. I was thinking of running dovecot-stable-20050709.tar.gz ... is this fairly stable? Also, can I use the .99 config file with that code? Thanks! -MAtt

2 1

[Dovecot] Dovecot without a chroot
by Matt Juszczak 12 Jul '05

12 Jul '05

Hi all, We're running dovecot without a chroot (mail admin's request), but we're running it as a non-priv'd user with proper firewall setup. Does this seem to be an OK and average setup? Or is it considered a MUST to chroot something like the imapd daemon, etc. Thanks! -Matt

2 1

[Dovecot] multiple instances of dovecot ?
by Flavien 12 Jul '05

12 Jul '05

Hello, I got a dovecot server running on a Debian Linux machine. I'd like to run another instance of it. I start it with another config file with debug output on stderr. The auth parameters are different : dovecot1: Imapd only, listens on 143, auth=/etc/passwd dovecot2: Imapd only, listens on 144, auth=mysql It kinda works... But... How does one instance of it recognizes the right "imap-login" it should talk to ? What happens in my tests, you guess it: dovecot1 talks to imap-login2, trying to authenticate users that are in /etc/password against mysql... # dovecot -F -c dovecot-config2.conf dovecot: Jul 05 22:49:03 Info: Dovecot starting up dovecot-auth: Jul 05 22:49:04 Info: MySQL: connected to localhost dovecot-auth: Jul 05 22:49:04 Info: Login process 6 connected dovecot-auth: Jul 05 22:49:04 Info: Login process 7 connected dovecot-auth: Jul 05 22:49:04 Info: Login process 6 sent handshake: PID 26368 dovecot-auth: Jul 05 22:49:04 Info: Login process 8 connected dovecot-auth: Jul 05 22:49:04 Info: Login process 7 sent handshake: PID 26369 dovecot-auth: Jul 05 22:49:04 Info: Login process 8 sent handshake: PID 26370 dovecot-auth: Jul 05 22:49:27 Info: Login process 9 connected dovecot-auth: Jul 05 22:49:27 Info: Login process 9 sent handshake: PID 26374 dovecot-auth: Jul 05 22:50:02 Info: Login process 10 connected dovecot-auth: Jul 05 22:50:02 Info: Login process 10 sent handshake: PID 26402 dovecot-auth: Jul 05 22:50:02 Info: MySQL: Performing query: SELECT password FROM users WHERE uid='flavien' dovecot-auth: Jul 05 22:50:02 Info: mysql(flavien): Unknown user 'flavien' is not known to the sql db. It's thunderbird trying to get my regular mail using the config1 on port 143, and it has nothing to do with the instance 2 whose output I'm just looking at !!! Any hint ? A+ Flavien.

2 1

[Dovecot] Connection dropped by imap server Query: CAPABILITY
by Srinivas 12 Jul '05

12 Jul '05

Hi all, I have installed squirrelmail-1.4.4 and dovecot 0.9.11 on a debian sarge machine. The tls/ssl support is disabled from both squirrelmail and dovecot imap server. When i try to login i get the following error message: ERROR: ERROR : Connection dropped by imap-server. Query: CAPABILITY If i give wrong password, it gives the message Unknown user or password incorrect. which is fine. The file /var/log/mail.err, is appended with the following message: Jul 5 18:40:20 server dovecot: chdir(/home/username) failed with uid 1240: Permission denied Jul 5 18:40:20 server dovecot: child 20807 (imap) returned error 89 when i run the command: dovecot -c /etc/dovecot.conf it gives the following error: Fatal: listen(143) failed: Address already in use Later i enabled tls in squirrelmail and dovecot.conf. i got the following error: Warning: fgets(): SSL: fatal protocol error in /usr/share/squirrelmail/functions/imap_general.php on line 88 ERROR: ERROR : Connection dropped by imap-server. Query: CAPABILITY Any suggestions? Thank you Srinivas _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

2 1

[Dovecot] cannot download eMails from POP3
by Bastian 12 Jul '05

12 Jul '05

Hi dovecot users, IŽve got a problem with downloading emails: dovecot is installed and configured, I can login but I cannot download mails wich are at my harddisc. After trying to download an email thatŽs in the logfile: pop3-login: Jul 05 10:41:00 Info: Login: webmaster(a)myDomain.de [xx.xxx.xx.xxx] dovecot-auth: Jul 05 10:41:00 Info: Login process 9 disconnected dovecot-auth: Jul 05 10:41:00 Info: Login process 9 connected dovecot-auth: Jul 05 10:41:00 Info: Login process 9 sent handshake: PID 5754 QueryŽs are successfully, like they are required in dovecot-mysql.conf: First password clear, then home directory (/var/opt/vmail/myDomain.de/webmaster), uid and gid. My eMails are at /var/opt/vmail/myDomain.de/webmaster/Maildir/new, does dovecot automatically search for emails in Maildir/new? IŽve no idea, why I cannot download any eMails :( Can you help me? Thank you Bye, Bastian

2 1

[Dovecot] Altering newly created mailboxes
by Thomas Wouters 12 Jul '05

12 Jul '05

There seems to be a bug in updating uid/uidvalidity when copying mail to an empty or newly created mailbox: <new connection> . OK Logged in. . CREATE testfolder4 . OK Create completed. . SUBSCRIBE testfolder4 . OK Subscribe completed. . SELECT otherfolder * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 3 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1121171128] UIDs valid * OK [UIDNEXT 4] Predicted next UID . OK [READ-WRITE] Select completed. . UID COPY 1 testfolder4 . NO Internal error occured. Refer to server log for more information. [2005-07-12 15:05:45] . SELECT testfolder4 . NO Internal error occured. Refer to server log for more information. [2005-07-12 15:05:49] <wait a while, doing nothing else> . SELECT testfolder4 * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 1 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1121173545] UIDs valid * OK [UIDNEXT 2] Predicted next UID . OK [READ-WRITE] Select completed. The errorlog entries for those two errors are: Jul 12 15:05:45 dovecot0 dovecot: IMAP(ynnoz): Corrupted index file /var/run/dovecot-index/ynnoz/.testfolder4/dovecot.index: uid_validity = 0, next_uid = 2 Jul 12 15:05:49 dovecot0 dovecot: IMAP(ynnoz): Corrupted index file /var/run/dovecot-index/ynnoz/.testfolder4/dovecot.index: uid_validity = 0, next_uid = 2 I also managed to trigger an assertion failure this way, by trying another COPY after that first failure: . UID COPY 1 testfolder6 . NO Internal error occured. Refer to server log for more information. [2005-07-12 15:16:54] . UID COPY 1 testfolder6 Connection closed by foreign host. The errors for that connection are: Jul 12 15:16:54 dovecot0 dovecot: IMAP(ynnoz): Corrupted index file /var/run/dovecot-index/ynnoz/.testfolder6/dovecot.index: uid_validity = 0, next_uid = 2 Jul 12 15:17:01 dovecot0 dovecot: IMAP(ynnoz): Corrupted index file /var/run/dovecot-index/ynnoz/.testfolder6/dovecot.index: uid_validity = 0, next_uid = 2 Jul 12 15:17:01 dovecot0 dovecot: IMAP(ynnoz): file mail-index-transaction.c: line 128 (mail_index_buffer_convert_to_uids): assertion failed: (*seq != 0) Jul 12 15:17:01 dovecot0 dovecot: child 6666 (imap) killed with signal 6 Another assertion error I triggered was by trying another SELECT right after the failed SELECT (after the failed COPY): Jul 12 15:14:04 dovecot0 dovecot: IMAP(ynnoz): Maildir /var/spool/mail/.4a/S/tmp/ynnoz/.testfolder5 sync: UIDVALIDITY changed (1121174026 -> 1121174044) Jul 12 15:14:09 dovecot0 dovecot: IMAP(ynnoz): Corrupted transaction log file /var/run/dovecot-index/ynnoz/.testfolder5/dovecot.index.log: Append with UID 1, but next_uid = 2 Jul 12 15:14:12 dovecot0 dovecot: IMAP(ynnoz): file mail-index-view.c: line 595 (mail_index_view_open): assertion failed: (index->map != NULL) Jul 12 15:14:12 dovecot0 dovecot: child 6654 (imap) killed with signal 6 I was able to reproduce this on a near-virgin test76 -- it has one patch that should not interfere; we use default_mail_env = maildir:%Nu:INDEX=/var/run/dovecot-index/%u where %N is a new var_expand character that looks up the argument in a NIS map (we store actual maildir location there, for scalability.) The INDEX setting we use might matter, though. But it feels like a missing update-uid or invalidate-uid call somewhere, I just don't know where :) -- Thomas Wouters <thomas(a)xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!

1 0

[Dovecot] Re: separate SSL certificates for pop3s and imaps
by sean finney 11 Jul '05

11 Jul '05

On Thu, Jul 07, 2005 at 08:58:35PM +0300, dovecot-request(a)dovecot.org wrote: > Hi, > > I'm migrating a uw-imap installation to dovecot. With uw-imap I had > different SSL certificates and keys for ipop3d and imapd. How can I > configure dovecot to do the same with its pop3s and imaps services? i run dovecot in a multihomed server with three different names: mail.foo.edu smtp.foo.edu imap.foo.edu which, for ssl purposes, means we need three different certs to keep applications happy. my approach is to start a seperate dovecot process for each address, and manage the configuration in three seperate files, each one telling dovecot to specifically bind to only one address, and use a seperate runtime directory specific to that address. so for example, in my initscript, instead of just doing something like: start() { echo -n $"Starting $prog: " daemon $prog -c /etc/dovecot.conf RETVAL=$? echo [ $RETVAL -eq 0 ] && touch /var/lock/subsys/$prog return $RETVAL } i do something like: start() { echo -n $"Starting $prog: " for s in imap mail smtp; do mkdir -p /var/run/dovecot/${s}.foo.edu daemon $prog -c /etc/dovecot/${s}.foo.edu.conf done RETVAL=$? echo [ $RETVAL -eq 0 ] && touch /var/lock/subsys/$prog return $RETVAL } where the value of the ssl cert config is different in each of the files. you could extend this to also have one config file to only listen for pop and the other only for imap. hth, sean

4 5

[Dovecot] Creating encrypted passwords for new users /etc/imap.passwd
by John_R._McWade 09 Jul '05

09 Jul '05

Hello. I've been attempting to locate information on how to actually create the encrypted passwords for a new user in /etc/imap.passwd file. Im really going into this blindly, not having ever used dovecot before, and really just need to be pointed to any existing resources on this topic. This is a setup of dovecot (w/ sendmail,squirrelmail) on FC2. I've got one successful auth so far as a test user, with their info cut/pasted directly from /etc/passwd (it works) whereas using {PLAIN}password causes dovecot to drop the connection with an aborted login. So what I'm actually looking for is a resource or a quick response regarding the actual creation of the encrypted password in /etc/passwd style. Any clues on where I should look for this info? John

2 1

[Dovecot] io leak when dnotify is enabled but not available
by Johannes Berg 08 Jul '05

08 Jul '05

Hi, When dnotify is enabled, but not in the kernel, there's an io leak: $ /sbin/dovecot --exec-mail imap * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS] Logged in as johannes a select inbox * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 787 EXISTS * 0 RECENT * OK [UIDVALIDITY 1106061449] UIDs valid * OK [UIDNEXT 790] Predicted next UID a OK [READ-WRITE] Select completed. b IDLE imap(johannes): Error: fcntl(F_NOTIFY) failed: Invalid argument imap(johannes): Error: fcntl(F_NOTIFY) failed: Invalid argument + idling DONE b OK Idle completed. q logout * BYE Logging out q OK Logout completed. imap(johannes): Warning: I/O leak: 0x10068ff0 (8) Attached patch fixes it, I hope the patch is correct :) johannes

1 0

[Dovecot] stat() failed with mbox /var/mail/%u
by Jungshik Shin 08 Jul '05

08 Jul '05

Hello, Over the last 12 hours or so, I've been wrestling with a mysterious dovecot issue. After upgrading a mail server I'm helping my friend with maintaining from Fedora Core1 to Fedora Core4, I realized that I couldn't use UW-IMAP4 anymore (well, I can compile it myself, but it turned out that UW-IMAP was the main cause of the server's having load average as high as 30 from time to time so that I decided to move onto dovecot). Although I loved to migrate to maildir, I didn't dare to tackle the migration (I have a lot more important things to do :-)) to maildir. Instead, I thought that dovecot's indexing of mbox files should make the performance of the server a lot better than UW-IMAP. (in addition, we upgraded the HW from P3 800MHz single to P4 dual 3GHz). Last night, I experimented with several mboxes of one user's account (INBOX in /var/mail/<userid> and others in ~/mail/) and it worked perfectly well. So, I moved mboxes of other users and launched 'dovecot' informing users that the mail server is back up again. However, it didn't work with inbox (for IMAP) and POP3. There's no problem accessing mail folders in '~/mail', but accessing /var/mail/%u (inbox for IMAP) and using the same folder with POP3 didn't work. The error I got in the log file is: Jul 8 01:17:24 biosoft dovecot: pop3-login: Login: xyz123 [::ffff:1xx.2yy.zz.178] Jul 8 01:17:24 biosoft dovecot: POP3(xyz123): stat() failed with mbox file /var/mail/xyz123: Permission denied Jul 8 00:34:45 biosoft dovecot: imap-login: Login: xyz123 [::ffff:1xx.2yy.zz.178] Jul 8 00:34:45 biosoft dovecot: auth(default): Error sending status request (Operation not permitted) Jul 8 00:34:45 biosoft dovecot: imap-login: Login: xyz123 [::ffff:1xx.2yy.zz.178] Jul 8 00:34:45 biosoft dovecot: IMAP(xyz123): stat() failed with mbox file /var/mail/xyz123: Permission denied ls -ld / /var /var/mail/ /var/mail/xyz123 drwxr-xr-x 23 root root 4096 Jul 7 19:28 / drwxr-xr-x 26 root root 4096 Jul 7 23:35 /var drwxrwxrwt 2 root mail 4096 Jul 8 00:36 /var/mail/ -rw-rw---- 1 xyz123 mail 130751237 Jul 7 23:37 /var/mail/xyz123 I tried various combinations of permissions and ownerships for /var/mail (1777, 2775) and /var/mail/<userid>, but nothing made any difference. I also tweaked mbox locking methods ('dotlock fcntl' or 'fcntl' alone) When I came across this problem with the latest stable (2005-07-06), I went back to FC4's default package (0.99??), but with a slightly different error message in the log file, basically I had the same problem. I kept the default values for most configuration parameters. What I changed are listed below: mail_extra_groups = mail pop3_uidl_format = %08Xv%08Xu protocols = imap imaps pop3s default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u Also attached is the entire /etc/dovecot.conf I'm really desperate to get some enlightening answers on this problem, for which I'll really appreciate you. Thanks tons in advance, Jungshik ## 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=/usr/share/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 pop3s # 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. You can specify ports with # "host:port", although with multiple protocols you probably want to move this # setting inside 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 = no # 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 = /usr/share/ssl/certs/dovecot.pem #ssl_key_file = /usr/share/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 = yes # 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 = 32 # 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 = yes # 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. ## ## 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 # 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 # Show protocol level SSL errors. #verbose_ssl = no # 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 = # 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 = default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # 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 # 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 # 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 # 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 mbox_read_locks = fcntl mbox_write_locks = 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 # 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 # 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: # oe6-fetch-no-newmail: # Never send EXISTS/RECENT when replying to FETCH command. Outlook Express # seems to think they are FETCH replies and gives user "Message no longer # in server" error. 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-negative-fetch: # Thunderbird sometimes messed up some calculations and wants to read # the message past it's end, giving negative size to FETCH BODY[]<..> # command. This workaround just hides the error message. #imap_client_workarounds = outlook-idle } ## ## 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 = %08Xv%08Xu # 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 ## # You can have multiple authentication processes. With plaintext authentication # the password is checked against each process, the first one which succeeds is # used. 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. # 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 = no # Even more verbose logging for debugging purposes. Shows for example SQL # queries. #auth_debug = no auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous mechanisms = plain # Password database specifies only the passwords for users. # http://wiki.dovecot.org/Authentication # passwd: /etc/passwd or similiar, using getpwnam() # shadow: /etc/shadow or similiar, using getspnam() # pam [<service> | *]: PAM authentication # checkpassword <path>: checkpassword executable authentication # passwd-file <path>: passwd-like file with specified location # vpopmail: vpopmail authentication # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # sql <config path>: SQL database, see doc/dovecot-sql.conf passdb = pam # 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 # passwd: /etc/passwd or similiar, using getpwnam() # passwd-file <path>: passwd-like file with specified location # static uid=<uid> gid=<gid> home=<dir template>: static settings # vpopmail: vpopmail library # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # sql <config path>: SQL database, see doc/dovecot-sql.conf userdb = passwd # 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. #chroot = # Number of authentication processes to create #count = 1 # Require a valid SSL client certificate or the authentication fails. #ssl_require_client_cert = no } # PAM doesn't provide a way to get uid, gid or home directory. If you don't # want to use a separate user database (passwd usually), you can use static # userdb. #auth onlypam { # mechanisms = plain # userdb = static uid=500 gid=500 home=/var/mail/%u # passdb = pam # user = dovecot-auth #} #auth ldap { # mechanisms = plain # userdb = ldap /etc/dovecot-ldap.conf # passdb = ldap /etc/dovecot-ldap.conf # user = dovecot-auth #} #auth virtualfile { # mechanisms = plain digest-md5 # userdb = passwd-file /etc/passwd.imap # passdb = passwd-file /etc/passwd.imap # user = dovecot-auth #} # 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 # } # } #}

2 2

[Dovecot] "Leave a copy on server" not marking messages as read...
by Matt Juszczak 07 Jul '05

07 Jul '05

Hi all, Our customers who have "Leave a copy on server" with POP3 continue to check their email, and each time they check it it re-downloads all emails (so it doesn't seem to be updating those messages already downloaded). Any ideas? Thanks! -Matt

1 0

[Dovecot] IMAP Folders
by Matt Juszczak 07 Jul '05

07 Jul '05

Hi all, We're using the mbox format and I tried setting up IMAP on my boss's computer tonight. He likes subfolders, and although they work, he can't seem to remove subfolders once he created them, nor create new folders without using something other than his mail client (like mkdir from the command line). Any ideas on this? Does dovecot just not officially support IMAP and subfolders with the mbox format? Or could it be a permissions issue? -Matt

2 1

[Dovecot] RE: dovecot not able to access sentmail folder in home directory(chdir)
by vineet 07 Jul '05

07 Jul '05

problem is solved the problem was with the access permissions to the folder having the users' folders make sure that dovecot has the permission to access the folders containg the users' folders vineet _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

1 0

[Dovecot] test76 segfaults?
by Johannes Berg 06 Jul '05

06 Jul '05

Hi, I was just trying to port my dspam plugin to the latest test release but ran into trouble so I decided to test the code itself first. I have the following maildir: johannes:~/.mail$ find . ./cur ./new ./new/test ./tmp ./.SPAM ./.SPAM/cur ./.SPAM/new ./.SPAM/tmp Now I run $ exec /usr/sbin/dovecot --exec-mail imap * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS] Logged in as johannes A SELECT INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 1 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1120680468] UIDs valid * OK [UIDNEXT 2] Predicted next UID A OK [READ-WRITE] Select completed. B COPY 1 SPAM imap(johannes): Error: Corrupted index file /home/johannes/.mail/.SPAM/dovecot.index: uid_validity = 0, next_uid = 2 Segmentation fault However, it actually did copy something: johannes:~/.mail$ find . ./cur ./cur/test:2, ./new ./tmp ./.SPAM ./.SPAM/cur ./.SPAM/new ./.SPAM/new/1120680473.P1535Q0M900310.johannes ./.SPAM/tmp ./.SPAM/dovecot.index ./.SPAM/dovecot-uidlist ./.SPAM/dovecot-uidlist.lock ./.SPAM/dovecot.index.log.2 ./.SPAM/dovecot.index.log ./dovecot.index.log ./dovecot.index ./dovecot.index.cache ./dovecot-uidlist The mail in that, for reference, is just this: --- A: xxx Subject: hallo! From: johannes X-DSPAM-Signature: asdf wow! --- johannes

1 1

[Dovecot] I need sleep (dovecot auth / postfix 2.3)
by /dev/rob0 06 Jul '05

06 Jul '05

I need the new sleep feature (smtpd_*_restrictions) of Postfix 2.3 snapshots, but I'm using the Dovecot auth patch. The 2.2.1 patch had problems in the snapshots I tried. Fortunately the problems were very simple. rob0@room101:~/src/mail/postfix-2.3-20050630$ patch -p1 < ~/dl/postfix-2.2.1-dovecot-auth.patch [snip] patching file src/smtpd/Makefile.in Hunk #1 FAILED at 1. Hunk #2 FAILED at 296. 2 out of 2 hunks FAILED -- saving rejects to file src/smtpd/Makefile.in.rej patching file src/smtpd/smtpd.c Hunk #1 FAILED at 854. Hunk #2 succeeded at 1006 (offset 16 lines). Hunk #3 succeeded at 1173 (offset 1 line). Hunk #4 succeeded at 1306 (offset 20 lines). Hunk #5 succeeded at 1562 (offset 33 lines). Hunk #6 succeeded at 1692 (offset 54 lines). Hunk #7 succeeded at 1834 (offset 72 lines). Hunk #8 succeeded at 2918 (offset 135 lines). Hunk #9 succeeded at 2952 (offset 73 lines). Hunk #10 succeeded at 3262 (offset 152 lines). Hunk #11 succeeded at 3301 (offset 73 lines). Hunk #12 succeeded at 3551 (offset 154 lines). 1 out of 12 hunks FAILED -- saving rejects to file src/smtpd/smtpd.c.rej [snip] I fixed the failures manually. Attached is a patch which only changes those two files ... it's a supplement to the existing patch as provided by Timo: http://dovecot.org/patches/postfix/postfix-2.2.1-dovecot-auth.patch I have not yet tested either sleep or AUTH, because I *do* need sleep for real. :) But it did compile with no errors nor [noted] warnings. I do have this running. -- mail to this address is discarded unless "/dev/rob0" or "not-spam" is in Subject: header

1 1

[Dovecot] Username mapping
by nodata 06 Jul '05

06 Jul '05

Hello. We're using dovecot with mysql for authentication, with postfixadmin for the admin web interface. We are moving users from passwd file usernames to email@domain style logins. Is there a better way to allow both sets of usernames (old and new) to work with dovecot than by adding extra copies of rows to the mailboxes table and changing the username? i.e. does dovecot support some kind of username mapping or aliasing? Thanks a lot

3 2

[Dovecot] dovecot not able to access sentmail folder in home directory(chdir)
by vineet 06 Jul '05

06 Jul '05

using dovecot version 0.99.11 while accessing through squirrelmail or even connecting manually(using openssl) to the server dovecot is not able to access the folder the mail.err log file has the following entry: dovecot: (/home/user) permission denied error no 89 returned by child process the squirrel mail error was connection dropped by imap server Query capability thanks vineet _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

1 0

[Dovecot] dovecot 1 for production? which one?
by Jeff A. Earickson 06 Jul '05

06 Jul '05

Hi, I've been lurking on the list since Spring, planning to replace UW-IMAP with dovecot 1.0 sometime this summer. The recent thread on "1.0" has not given me a good feeling about seeing it before summer's end. So I wonder if I should use dovecot-1.0-test-xx code or dovecot-stable-[date] code (which seems to change every day, how stable is that???). This is confusing, advice please. My setup: Solaris 9, mbox format. Jeff Earickson Colby College

2 1