- dovecot - dovecot.org

[Dovecot] Problems with BEFORE searches.
by Trever L. Adams 12 May '07

12 May '07

Ok, I am trying to modify some code given to me by the author of the dspam plugin for dovecot (sorry the name eludes me). I am modifying it to handle UNSEEN differently than SEEN. Below is the python code. I am not a python programmer, but I get the basic idea. ok, uids = conn.search(None, 'BEFORE', unreadsentbefore, 'SEEN') "11-May-2007 06:18:29 -0600" is the value of unreadsentbefore. However, this doesn't match any emails even though they are all dated as 5/10 and they have all been read for several hours (the time was the current to figure out why it isn't working). Is there a problem with BEFORE and SEEN together? Is there a BEFORE bug in the system? Some of the messages are -500 and others, I am not sure. Thanks, Trever Adams

4 6

[Dovecot] read only maildir subscriptions
by Nagyon Almos 11 May '07

11 May '07

Hello, I have some (possibly very simple) questions about subscriptions: I store my old mails in /home/oldmails/ in one Maildir where I have only read-only permissions (I cannot delete, create or modify any files). Under thunderbird, I can successfully log in and read my new mails, but I cannot subscribe (?) within thunderbird to oldmails (it is grey not black as other folders). What did I do wrong? What other permissions does dovecot need? Here's the relevant part of dovecot.conf: namespace private { separator = / prefix = oldmails/ location = maildir:/home/oldmails/:CONTROL=~/Maildir/control-oldmails:INDEX=~/Maildir/index-oldmails } and when I try to subscribe to it, dovecot says: dovecot: 2007-04-30 17:58:53 Info: IMAP(xxx): Effective uid=7001, gid=1000 dovecot: 2007-04-30 17:58:53 Info: IMAP(xxx): Namespace: type=private, prefix=regi/, sep=/, inbox=no, hidden=no, subscriptions=no dovecot: 2007-04-30 17:58:53 Info: IMAP(xxx): maildir: data=/home/oldmails/:CONTROL=~/Maildir/control-oldmails:INDEX=~/Maildir/index-oldmails dovecot: 2007-04-30 17:58:53 Info: IMAP(xxx): maildir: root=/home/oldmails, index=~/Maildir/index-oldmails, control=~/Maildir/control-oldmails, inbox= Thanks for any help in advance. Regards, A. <br><br>_______________________________________________________________<br> <a href="http://cthandler.adverticum.net/?cturl=http%3A%2F%2Fwww.klikkbank.hu%2Flako… " target="new">INTEZZE PÉNZÜGYEIT AZ INTERNETEN!</a> Lakossági számlacsomag havi 199 Ft-ért! Bankkártya éves kártyadíj nélkül! <a href="http://cthandler.adverticum.net/?cturl=http%3A%2F%2Fwww.klikkbank.hu%2Flako… " target="new">www.klikkbank.hu</a>

2 2

[Dovecot] Dovecot not handling r/o mailboxes completely, and problem with ACL as a workaround
by Adam McDougall 11 May '07

11 May '07

First of all, I think dovecot is really fantastic and I have thanks for all the hard work. I think it will be the best fit for my ~5000 users when I have it setup completely. We normally have approx 500 concurrent IMAP connections during the day. I am trying to convert from courier-imap to dovecot, but I have an issue with public namespace folders that are not writable by certain users. Please let me know if I need to provide more information or how I can help solve this issue. In courier-imap, we were able to take advantage of the maildir structure and standard unix users/groups to allow 'decsstaff' members to have full write access while 'decsall' members only have r/o unless also a member of 'decsstaff': -rw-rw-r-- 1 postlocal decsstaff 37597 May 5 23:37 /egr/mail/shared/decs/.support.In/cur/1178422658.M533373P54269.ice drwxrwxr-x 2 postlocal decsstaff 24576 May 5 23:37 /egr/mail/shared/decs/.support.In/cur drwxrws--- 6 postlocal decsall 4096 Apr 22 18:08 /egr/mail/shared/decs/.support.In drwxrwsr-x 34 postlocal wheel 4096 May 1 07:23 /egr/mail/shared/decs In short, upper directories are used to limit world access to just one group 'decsall', and once inside, r/o world access could be used as an anonymous substitution for 'decsall' and the group permissions would allow writing by 'decsstaff'. I don't know how courier stores and checks mail directory permissions, but it was aware when a user would not be able to delete or change messages and would return a READ-ONLY imap error when an attempt to change a message occurred (courier returns this in the IMAP response to update mail flags to reflect that the client wants to move to delete a mail). I understand that imap clients will usually only set status as read or deleted first and only try to delete an email for real on expunge, but it seems dovecot does not try to detect if a message is modifyable before it is too late for the user to find out. What happens is a user appears to be able to mark messages read, move them to another folder, or delete them (another way of moving to another folder eg. Trash). The user is clueless that the changes will not occur, and only finds out later when they reload the folder to find the messages back, or tries to expunge and get an unhelpful 'internal error' from dovecot (I can help trace this situation if it helps, but I think that stage should not be reached if things were working right). My configuration has the public folder control and indexes inside a user's home directory, so it will always be possible for dovecot to record message status changes, however I do not think dovecot should update the control and indexes to reflect an IMAP operation that is not allowed to complete due to restricted permissions on the actual email file. I suppose dovecot would have to check the permissions on mail message files. As a workaround, I wondered if I could apply dovecot ACLs to the public folders to reinforce my intentions of only allowing readonly access to certain users. If ACLs worked, I could even use it as a viable alternative to the unix permissions on the maildir contents and avoid using more unix groups than necessary. For most of our shared mailboxes, there will only be a few persons with write access, and up to a dozen people with read access, so even if I have to list every user seperately I could. However, I have not been able to get ACLs to do anything useful for me, and I hesitate to use the feature to work around might be a configuration error or bug. It is also more convenient for my migration procedure if I do not have to modify file permissions or structure during downtime to switch to dovecot. I am still not sure how dovecot ACLs affect the actual permissons of dovecot processes. I have mostly tried placing a dovecot-acl file in the maildir directory (alongside cur, tmp, new) and dovecot seems to be reading it according to the log, however I am not getting expected results from the ACLs. If the unix permissions allow a client to enter 'cur' and read mails, the mail client thinks it can delete or move them (until expunge) no matter even if I put acl entries with only 'r' permission. ACL questions (which might help others understand better as well): Is a 'user=foo rl' entry supposed to remove any possible write permissions in a maildir covered by such an ACL for user foo? If not, shouldn't it at least enforce restrictions on the available mail metadata which is more likely to be writable by the user? Is it even possible for an ACL to grant additional permissions above what is granted to a user by standard unix permissions? Does an empty ACL equate to the exact permissions granted by unix, and should an admin try to design an ACL to modify as little as possible, or should the admin try to use enough acl entries to form a complete description of the desired resulting permissions? I get the impression that broad ACLs should be listed first, and more specific ACLS listed below can add or remove ACL permissions applied earlier in the file as a 'last match' case. Should the acl plugin be able to print a summary of the resulting permissions in the log (with mail_debug=yes) when accessing a folder with an ACL? A snip from logs, I generated alot today and I'm not sure which portions would be most useful so I'll start with this: May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): acl: initializing backend with data: vfile:/usr/local/etc/dovecot-acls May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): acl: acl username = mcdouga9 May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): acl: owner username = May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): acl vfile: Global ACL directory: /usr/local/etc/dovecot-acls May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): Namespace: type=public, prefix=#shared/decs/, sep=/, inbox=no, hidden=no, subscriptions=no May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): maildir: data=/egr/mail/shared-dovecot2/decs:CONTROL=/home/mcdouga9/Maildir/dovecot/public/control/decs:INDEX=/home/mcdouga9/Maildir/dovecot/public/indexes/decs May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): maildir: root=/egr/mail/shared-dovecot2/decs, index=/home/mcdouga9/Maildir/dovecot/public/indexes/decs, control=/home/mcdouga9/Maildir/dovecot/public/control/decs, inbox= May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): opendir(/egr/mail/shared-dovecot2/decs/tmp) failed: Permission denied # dovecot --version 1.0.0 The reason I have so many public spaces below, is to match the existing directory structure we setup for courier, and also to help us keep the directory listing more tidy since otherwise we would end up with many folders all under one directory. Some of them have monthly rotation and it could get out of hand if we did not split them up. I understand it makes things more difficult for the global acl list at present, if I were to use it, but I may not have any conflicting folder names at this time. # dovecot -n # /usr/local/etc/dovecot.conf ssl_cert_file: /usr/local/etc/apache2/ssl/mail.egr.msu.edu.pem ssl_key_file: /usr/local/etc/apache2/ssl/mail.egr.msu.edu.pem login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 0 mail_location: maildir:~/Maildir:CONTROL=%h/Maildir/dovecot/private/control:INDEX=%h/Maildir/dovecot/private/indexes mail_debug: yes mmap_disable: yes maildir_copy_with_hardlinks: yes mail_plugins: acl mail_log_max_lines_per_sec: 0 imap_client_workarounds: delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep namespace: type: public separator: / prefix: #shared/be/ location: maildir:/egr/mail/shared-dovecot2/be:CONTROL=%h/Maildir/dovecot/public/control/be:INDEX=%h/Maildir/dovecot/public/indexes/be namespace: type: public separator: / prefix: #shared/cee/ location: maildir:/egr/mail/shared-dovecot2/cee:CONTROL=%h/Maildir/dovecot/public/control/cee:INDEX=%h/Maildir/dovecot/public/indexes/cee namespace: type: public separator: / prefix: #shared/chems/ location: maildir:/egr/mail/shared-dovecot2/chems:CONTROL=%h/Maildir/dovecot/public/control/chems:INDEX=%h/Maildir/dovecot/public/indexes/chems namespace: type: public separator: / prefix: #shared/decs/ location: maildir:/egr/mail/shared-dovecot2/decs:CONTROL=%h/Maildir/dovecot/public/control/decs:INDEX=%h/Maildir/dovecot/public/indexes/decs namespace: type: public separator: / prefix: #shared/egr/ location: maildir:/egr/mail/shared-dovecot2/egr:CONTROL=%h/Maildir/dovecot/public/control/egr:INDEX=%h/Maildir/dovecot/public/indexes/egr namespace: type: public separator: / prefix: #shared/me/ location: maildir:/egr/mail/shared-dovecot2/me:CONTROL=%h/Maildir/dovecot/public/control/me:INDEX=%h/Maildir/dovecot/public/indexes/me namespace: type: public separator: / prefix: #shared/org/ location: maildir:/egr/mail/shared-dovecot2/org:CONTROL=%h/Maildir/dovecot/public/control/org:INDEX=%h/Maildir/dovecot/public/indexes/org namespace: type: public separator: / prefix: #shared/toptest/ location: maildir:/egr/mail/shared-dovecot2/toptest:CONTROL=%h/Maildir/dovecot/public/control/toptest:INDEX=%h/Maildir/dovecot/public/indexes/toptest namespace: type: public separator: / prefix: #shared/ugs/ location: maildir:/egr/mail/shared-dovecot2/ugs:CONTROL=%h/Maildir/dovecot/public/control/ugs:INDEX=%h/Maildir/dovecot/public/indexes/ugs namespace: type: public separator: / prefix: #shared/vprgs/ location: maildir:/egr/mail/shared-dovecot2/vprgs:CONTROL=%h/Maildir/dovecot/public/control/vprgs:INDEX=%h/Maildir/dovecot/public/indexes/vprgs namespace: type: private separator: / prefix: mail/ hidden: yes namespace: type: private separator: / location: maildir:~/Maildir:CONTROL=%h/Maildir/dovecot/private/control:INDEX=%h/Maildir/dovecot/private/indexes inbox: yes auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth user: postfix group: postfix master: plugin: acl: vfile:/usr/local/etc/dovecot-acls Thanks.

6 13

[Dovecot] Log data on dovecot-auth socket
by Koen Vermeer 11 May '07

11 May '07

Hi, Is there any way I can monitor or log the data that is being received/sent on the dovecot-auth socket? I'm trying to debug some authentication stuff, and monitoring the conversation would be very useful. Thanks! Koen

2 2

[Dovecot] No authentication sockets found
by Stewart Dean 11 May '07

11 May '07

Thunderbird (2.0) is all of a sudden checking mail server capabilities and keep posting a popup saying: "Mail Server imap.bard.edu is not an IMAP4 mail server". To the best of my knowledge, neither Tbird nor DC have been updated, though the DC imap host was rebooted today 3 hours ago. Any info on what this is about? DC is currently serving out of a special port and in evaluation list....I can't imagine that this message would please the user community! Killing and restarting dovecot appears to have at least temporarily stopped this behavior. Also and perhaps related, I am seeing a syslog message: imap-login: No authentication sockets found child xxxxxx (login) returned error 89 using SSL encrypted IMAP service Background: DC 1.0, invoked from /etc/rc.local during boot. After stopping and restarting DC, things seem to work again. As per an old problem, I checked /var/run/dovecot, but it was empty with plenty of space. FWIW, the owner/group for login dir (/var/run/dovecot) is dovecot:dovecot, perm 755, while /var/run/dovecot/login is root:dovecot, 750. Host is running AIXV5.3 TL5 SP6 (latest level), DC is compiled with IBM's AIX for C, V6.0 dovecot -n output > # /usr/local/etc/dovecot.conf > listen: *:10143 > ssl_listen: *:10943 > disable_plaintext_auth: no > verbose_ssl: yes > login_dir: /var/run/dovecot/login > login_executable: /usr/local/libexec/dovecot/imap-login > verbose_proctitle: yes > first_valid_uid: 200 > mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=/var/dcndx/%u > mail_debug: yes > mbox_dirty_syncs: no > mbox_lazy_writes: no > auth default: > verbose: yes > debug: yes > passdb: > driver: pam > userdb: > driver: passwd Do I need to set an O/S or SSL max for authentication sockets? If so, any info would be appreciated Thanks! -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

3 2

[Dovecot] locking questions
by Stewart Dean 11 May '07

11 May '07

I have Dovecot 1.0 in trial use by the IT staff, and have some locking questions Background, the mail server runs procmail, sendmail and NFS exports the user homedir and mailbox to a) a login shell host and b) a mailing list services host. It runs UWIMAP on the usual ports and dovecot on a arbitrary port number. Because of concern with NFS and file access contention. I have the following dovecot.conf file access parms set: a) mbox_dirty_syncs = no b) mbox_lazy_writes = no 1) I am seeing these errmsgs. Are they anything I should be concerned about, or are they just the inevitable result of lock contention for mailboxes and folders by procmail, imap/dovecot and NFS? > In syslog, I am seeing this: > > Apr 23 18:46:34 mercury mail:err|error dovecot: IMAP(sdean): stat(/var/spool/mail/sdean.lock) failed: No such file or directory > Apr 23 18:46:34 mercury mail:err|error dovecot: IMAP(sdean): file_lock_dotlock() failed with mbox file /var/spool/mail/sdean: No such file or directory > > While in maillog: > > Apr 23 18:46:34 mercury mail:err|error dovecot: IMAP(sdean): stat(/var/spool/mail/sdean.lock) failed: No such file or directory > Apr 23 18:46:34 mercury mail:err|error dovecot: IMAP(sdean): file_lock_dotlock() failed with mbox file /var/spool/mail/sdean: No such file or directory 2) I earlier asked, but don't think I got an answer to this question: > Everybody wants to lock differently > 1) procmail (delivering for sendmail), which seems to want to use > dotlocking, fcntl and lockf locking; for whatever reasons, the compile > time tests seem to disallow flock. > 2) UWIMAP which according to wiki.dovecot.org/Migration/UW uses: > mbox_read_locks = flock > mbox_write_locks = dotlock flock > 3) I want to run dovecot in the same environment as I switch over, for > which the locking strategy is supposed to be (according to > http://wiki.dovecot.org/MboxLocking) > mbox_read_locks = fcntl > mbox_write_locks = dotlock fcntl > > Since that same page in the wiki says. "*It's important that all > software that's reading or writing to mboxes use the same locking > settings.",* I had recompiled procmail so it only usedotlocking and > fcntl (thus removing lockf in addition to the disallowed flock)...but > now I bumped into the Migration/UW page and there looks to be a conflict. > > I want to be able to run dovecot (for testing) and UWIMAP (for all > users/production) at the same time (but never at the same time with > the same mailbox), but UWIMAP is doc'ed to use flock and Dovecot doesn't > It's conceivable that the different locking strategies of UWIMAP and > Dovecot don't matter because they would never be going after the same > mail files (right?) but there is procmail, which has to interact with > both. It appears to not use flock OK, even though the docs say it > should since UWIMAP expects it, and I've disabled lockf as well. But > will there be a conflict with procmail and dovecot's use of fcntl, > which UWIMAP doesn't use? > > Help. 3) I occasionally see "Disconnected for inactivity" message. How long before that happens? Is the interval configurable? Thanks to all. A brother sysadmin was stunned by performance gained in Dovecot. He has to keep postmaster messages for a period and filters them into a separate folder...over a long weekend this folder could get to 1500 messages and 150MB...with UWIMAP he could only delete approx 800 at a time and then had to wait 5-10 minutes for it to process. With dc, he marked off the whole folder and it was gone in seconds. -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 1

[Dovecot] Dovecot refuses connections
by John Rowe 11 May '07

11 May '07

I have recently upgraded to dovecot 1.0.0 on two machines running Scientific Linux 4.3/4.4 x86_64 kernel 2.6.9-22.0.1.EL. The systems come with openssl 0.9.7a and I have installed openssl-0.9.8e. Everything is 64-bit. /usr/local64/sbin/dovecot -n # /usr/local64/etc/dovecot.conf disable_plaintext_auth: no login_dir: /usr/local64/var/run/dovecot/login login_executable: /usr/local64/libexec/dovecot/imap-login first_valid_uid: 100 mail_extra_groups: mail default_mail_env: mbox:%h/mail:INBOX=/var/spool/mail/%u mail_location: mbox:%h/mail:INBOX=/var/spool/mail/%u mail_debug: yes mmap_disable: yes lock_method: dotlock mbox_read_locks: lockf mbox_write_locks: lockf auth default: passdb: driver: pam userdb: driver: passwd I have two issues: 1. It won't start from xinetd. I get very little in the logs, just: Apr 7 07:07:41 xyz xinetd[2545]: START: imaps pid=17445 from=144.173.228.126 Apr 7 07:07:41 xyz xinetd[2545]: EXIT: imaps pid=17445 duration=0(sec) where 'xyz' is the host name 2. If I instead I run dovecot as a daemon then both my machines have suffered the problem where dovecot runs for several days and then disallows connections with: Apr 29 04:06:07 xyz dovecot: imap-login: opendir(.) failed when trying to get list of authentication servers: Permission denied Apr 29 04:06:07 xyz last message repeated 2 times Apr 29 04:06:07 xyz dovecot: child 5645 (login) returned error 89 Apr 29 04:06:07 xyz dovecot: child 5646 (login) returned error 89 Apr 29 04:06:07 xyz dovecot: child 5647 (login) returned error 89 Killing and restarting dovecot seems to fix it. Thanks for your help. John

2 1

[Dovecot] dovecot 1.0.0 hang on one server
by Roberto Tagliaferri 11 May '07

11 May '07

Hi, i've upgraded 5 server from dovecot beta7 or old dovecot-stable to 1.0.0 but on one server dovecot crash after few hours without any log Apr 23 18:19:32 Info: POP3(username): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 24 09:54:11 Info: Dovecot v1.0.0 starting up The startup is by hand (when i arrived at office!!) This server is a linux running on vmware, with 1.0rc7 is all ok , the other server is ok with 1.0.0 The config file are the same... -- Roberto Tagliaferri Responsabile Progettazione & Produzione TosNet s.r.l. - Internet Service Provider r.tagliaferri(a)tosnet.it www.tosnet.it

2 1

[Dovecot] Changes in authentication's???
by Boris Ivanov 11 May '07

11 May '07

HI I use dovecot-1.0.r17 on FreeBSD scat.setcom 6.2-RELEASE. Recently authentification stop working. May 10 02:56:02 scat dovecot: auth(default): passwd(test,127.0.0.1): unknown user May 10 02:56:02 scat dovecot: auth(default): client out: OK 1 user=test User= &:/home/test:/tmp/email/bin/nonexistance= May 10 02:56:02 scat dovecot: auth(default): master in: REQUEST 23 43856 1 May 10 02:56:02 scat dovecot: auth(default): passwd(test,127.0.0.1): unknown user May 10 02:56:02 scat dovecot: auth(default): master out: USER 23 test uid=1004 gid=31415 home=/home/test May 10 02:56:02 scat dovecot: imap-login: Login: user=<test>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured May 10 02:56:02 scat dovecot: IMAP(test): Effective uid=1004, gid=31415 May 10 02:56:02 scat dovecot: IMAP(test): mbox: data=/tmp/email/mbox/s/test May 10 02:56:02 scat dovecot: IMAP(test): mbox: INBOX defaulted to /tmp/email/mbox/s/test/inbox May 10 02:56:02 scat dovecot: IMAP(test): mbox: root=/tmp/email/mbox/s/test, index=/tmp/email/mbox/s/test, inbox=/tmp/email/mbox/s/test/inbox I generate passwd using next script: etc_path = /usr/local/www/data/Email/RefCont/etc pwd_mkdb -d ${etc_path} ${etc_path}master.passwd pw useradd -V ${etc_path} -n $1 -g mailusers -s /tmp/email/bin/nonexistance echo "$2" | pw usermod -V ${etc_path} -n $1 -h 0 My config: # /usr/local/etc/dovecot.conf protocols: imap pop3 listen(default): *:10143 listen(imap): *:10143 listen(pop3): *:10110 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_process_size: 64 verbose_proctitle: yes first_valid_uid: 0 first_valid_gid: 0 mail_extra_groups: mail default_mail_env: mbox:/tmp/email/mbox/s/%u mail_location: mbox:/tmp/email/mbox/s/%u mail_debug: yes mbox_min_index_size: 100000 mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login verbose: yes debug: yes debug_passwords: yes passdb: driver: pam passdb: driver: passwd passdb: driver: passwd-file args: /usr/local/www/data/Email/RefCont/etc/master.passwd userdb: driver: passwd userdb: driver: passwd-file args: /usr/local/www/data/Email/RefCont/etc/passwd Whats wrong? Can it be fixed? Thanks -- Yours Boris

3 2

[Dovecot] Tracing an IP of a user who deleted the message
by Eugene Gladchenko 11 May '07

11 May '07

Hello, Dovecot writes to the log file lines like these: May 10 13:19:04 mailserver dovecot: IMAP(office): copy -> Trash: uid=1131, msgid=<45E669BE.8090705(a)example.com>, box=Sent May 10 13:19:05 mailserver dovecot: IMAP(office): deleted: uid=1131, msgid=<45E669BE.8090705(a)example.com>, box=Sent May 10 13:53:08 mailserver dovecot: IMAP(office): copy -> Trash: uid=1719, msgid=<002701b483f5$7aa257e0$23833bda(a)example.com> May 10 13:53:08 mailserver dovecot: IMAP(office): deleted: uid=1719, msgid=<002701b483f5$7aa257e0$23833bda(a)example.com> I've got a bunch of users that work with the login 'office'. Is it possible to determine the IP of the user that deleted messages? If not, what can be done about it in the future? Thank you. -- Eugene Gladchenko EVG15-RIPE

4 3

[Dovecot] Dovecot and Outlook - IMAP Timeout error
by Phillip T. George 11 May '07

11 May '07

Hey guys, I'm having a problem with Dovecot and Outlook. I'm testing with Outlook XP (2002), but the problem occurs with Outlook 2003 as well. I'm using Dovecot 1.0.rc28. The specific error generated (for IMAP) is: "A connection to the server could not be established. <servername> is now in offline mode." In the details: "There may be a server or network problems or your timeout interval may be too short. Protocol: IMAP Server: <servername> Port: 143" It is set up with a POP3 account and an IMAP account within Outlook -- using the same physical email account. The IMAP portion is only used for spam / ham submission, while the POP3 is used for downloading the actual email. The account on the server being used is named "me2.pg.east.eacsd.com" I have a single IMAP account set up in Thunderbird, which is using the account name "me.pg.east.eacsd.com". All mail that is received at "me.pg.east.eacsd.com" is forwarded to "me2.pg.east.eacsd.com" to generate some traffic. Here is the snippet of the mail log which involves me2.pg.east.eacsd.com ( | grep me2.pg.east.eacsd.com | grep -i imap): Apr 25 02:40:11 east dovecot: imap-login: Login: user=<me2.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38 Apr 25 02:40:13 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected in IDLE Apr 25 02:41:10 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected: Logged out Apr 25 02:45:41 east dovecot: imap-login: Login: user=<me2.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38 Apr 25 02:45:41 east dovecot: imap-login: Login: user=<me2.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38 Apr 25 02:46:18 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected Apr 25 02:46:18 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected Apr 25 02:50:49 east dovecot: imap-login: Login: user=<me2.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38 Apr 25 02:50:50 east dovecot: imap-login: Login: user=<me2.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38 Apr 25 02:51:27 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected Apr 25 02:51:27 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected Apr 25 02:55:58 east dovecot: imap-login: Login: user=<me2.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38 Apr 25 02:55:58 east dovecot: imap-login: Login: user=<me2.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38 Apr 25 02:56:56 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected Apr 25 02:56:56 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected Apr 25 03:01:27 east dovecot: imap-login: Login: user=<me2.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38 Apr 25 03:01:27 east dovecot: imap-login: Login: user=<me2.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38 Apr 25 03:01:58 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected Apr 25 03:01:58 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected There's more before that, but I'd figured that would be enough: Apr 24 17:18:05 east dovecot: IMAP(me.pg.east.eacsd.com): Disconnected in IDLE Apr 24 17:19:34 east dovecot: IMAP(me.pg.east.eacsd.com): Disconnected in IDLE Apr 24 17:19:42 east dovecot: IMAP(me.pg.east.eacsd.com): Disconnected in IDLE Apr 24 17:20:27 east dovecot: IMAP(me.pg.east.eacsd.com): Disconnected in IDLE Apr 24 17:20:42 east dovecot: imap-login: Login: user=<me.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38, TLS Apr 24 17:43:18 east dovecot: imap-login: Login: user=<me.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38, TLS As you can see from the logs, Thunderbird didn't have a problem, which eliminates the possibility of a bad net connection (I'd assume...but I could be wrong). The problem occurred at 3AM. Some people during the day can get it every hour or so. I was able to get it to occur twice (the first time is not shown in these logs). My questions. . . 1. Is there any way to fix this Outlook problem? I have all of the outlook workarounds enabled (along with some for Netscape): imap_client_workarounds = delay-newmail outlook-idle netscape-eoh pop3_client_workarounds = outlook-no-nuls oe-ns-eoh 2. Should Outlook really be connecting and disconnecting that often? 3. Could the problem be occurring because of POP3 and IMAP being used by the same account, and the quick downloading of email via POP3 is eliminating the email for IMAP, thereby causing inactivity in IMAP? Is there a workaround or a known Outlook settings to fix this? Thanks, Phillip

2 1

[Dovecot] Troubleshooting - another suggestion...
by Charles Marcus 11 May '07

11 May '07

Hi Timo, I'm the one who suggested the '-n' option to capture the actual config settings that the running dovecot process was using (ala postfix), and you implemented it very quickly - so thanks for that! Now, I'd like to suggest an enhancement... Many people still do not provide basic things like dovecot version, and there are secondary config files like dovecot-ldap, whose settings are not included in the dovecot -n output. How difficult would it be to add these to the output so that the output would include the running dovecot version, as well as any extra config settings from any other files that are loaded when dovecot starts? It would sure make it easier, both for us troubleshooting on our own, and when asking for help on the list. Many thanks, and terrific job on 1.0! Now all dovecot lacks is full support for IMAP ACLs/shared folders, and support for single-instance storage, and it will have no real competition... -- Best regards, Charles

2 2

[Dovecot] lucene plug-in
by ??? 11 May '07

11 May '07

Hello, Has anyone tried the lucene plug-in? I am interested to know more about this feature , how to setup / configure it? regards, - Joe

2 1

[Dovecot] corruption?
by Neal Becker 11 May '07

11 May '07

I'm using maildir (and have been for a long time). Today I have a problem: ls -al (maildir): [...] drwx------ 5 nbecker nbecker 4096 Jan 1 2006 .;SECTION= What's this? It seems to be causing my mail client (kmail, using dimap), to hang.

2 1

[Dovecot] maildir file name flags out of order?
by Aaron Solochek 11 May '07

11 May '07

I was trying to figure out why my false-positive spam messages were being tagged as "personal" by thunderbird, and I noticed a possible problem. According to DJB: http://cr.yp.to/proto/maildir.html > New flags may be defined later. Flags must be stored in ASCII order: e.g., "2,FRS". Looking at my maildir, I am seeing flags out of order, such as "2,Sdae" Shouldn't that be "2,Sade"? -Aaron

2 1

[Dovecot] Disconnected for inactivity in reading our output top=0/0
by Chris Gosley 11 May '07

11 May '07

Would someone please help with this error. Using: dovecot-1.0-2.rc28.fc6 On: Fedora Core 6 130 users all connect remotely via ADSL to server to pop their email. None of them have any problems at all with pop3. 3 users in one office, connect to the server via a NAT'd ADSL. Intermittently those three users will get a timeout error, Logfile shows: Apr 19 12:50:53 mail dovecot: auth(default): pam(vu0095,165.228.62.107): lookup service=dovecot Apr 19 12:50:53 mail dovecot: auth(default): client out: OK 1 user=vu0095 Apr 19 12:50:53 mail dovecot: auth(default): master in: REQUEST 376 12300 1 Apr 19 12:50:53 mail dovecot: auth(default): passwd(vu0095,165.228.62.107): lookup Apr 19 12:50:53 mail dovecot: auth(default): master out: USER 376 vu0095 system_user=vu0095 uid=580 gid=580 home=/home/vu0095 Apr 19 12:50:53 mail dovecot: pop3-login: Login: user=<vu0095>, method=PLAIN, rip=165.228.62.107, lip=203.36.211.209 Apr 19 12:51:49 mail dovecot: POP3(vu0095): Disconnected for inactivity in reading our output top=0/0, retr=1/0, del=0/2, size=25266 Apr 19 12:51:49 mail dovecot: POP3(vu0095): Disconnected: Logged out top=0/0, retr=2/25393, del=2/2, size=25266 99% of the time everything is perfect, it is only the three users in the one office that get this error, it is of course the head office for the customer and so they are very upset, because they get timeout errors on their email clients. They are using different versions of outlook, and outlook express, I have deactivated all nortons email scanning etc Have set the three email clients to pop mail at different times, eg. 7, 13, 17 minutes to try an avoid the possibility of simultaneous pop requests from the one IP address. Dovecot -n # /etc/dovecot.conf protocols: pop3 pop3s listen: * ssl_disable: yes login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/pop3-login login_greeting: POP Server ready. login_processes_count: 20 mail_executable: /usr/libexec/dovecot/pop3 mail_plugin_dir: /usr/lib/dovecot/pop3 pop3_client_workarounds: outlook-no-nuls oe-ns-eoh auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: pam userdb: driver: passwd

3 2

[Dovecot] read only bug?
by Nagyon Almos 11 May '07

11 May '07

Hello All, I have been still struggling with the read only maildir and I think I found something: dovecot wants to rename a file but I/it have/has no rights to do that: dovecot: 2007-05-04 21:30:14 Error: IMAP(bela): rename(/home/store/oldmails/.personal/cur/1154939281.00005.pc1.S=1879:2,S, /home/store/oldmails/.personal/new/1178307014.P8610Q0M347618.pc1) failed: Permission denied Why dovecot wants to rename it? It is really a read only directory. Regards, A. ______________________________________________ 2600 állásból Te is találsz megfelelőt! Mérnöki, értékesítői, asszisztensi, pénzügyi és IT állások a Jobline.hu-n! http://www.jobline.hu

3 5

[Dovecot] read only maildir
by Nagyon Almos 11 May '07

11 May '07

Hello All, I try to set up a read only maildir just as in the wiki, to no avail. The extra (public) namespace shows up but I can not susbscribe to it (in thunderbird) or if I change to that "directory" (in mutt), it is empty. Is it the problem mentioned in the wiki (SharedMailboxes#Subscriptions)? If yes, how can I see/use a folder which is not subscribeable? Any help would be greatly appreciated. Regards, A. _____________________________________________________________ "Egy anya oda se bagózik a megjelenésedre. Szerinte gyönyörű vagy és punktum." Meglepetéskönyvek anyák napjára. http://ad.adverticum.net/b/cl,1,6022,162660,225668/click.prm

5 9

[Dovecot] Error: Master request X not found
by Jordi Moles 11 May '07

11 May '07

*Hi, I've been getting the following error from time to time since i started to use dovecot more than one year ago: dovecot: May 07 19:57:24 Error: auth(default): Master request 88729.43523 not found I haven't stopped upgrading dovecot with the hope that this would be a bug and would be fixed some day, but with v1.0.0, i keep getting the same error. It just happens from time to time. Some of the users of my system complain about not being able to get to see their mails, and it is always at the time when this error is logged. Surfing through many forums, i came across with a cause that many people point to: "client closed connection at the exact same time master was logging it in" i don't know if this is what happens to my system, to be honest, i don't have a clue how to check that, i just would like to know if somebody has come up with a solution for this problem, as it seems many people are still trying to face it. thank you. ***

3 2

[Dovecot] namespace
by Stefan Klatt 11 May '07

11 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, i use dovecot 1.0 and try to implement an public mbox namespace parallel to a private and a public maildir namespace. namespace: type: public separator: / prefix: Archiv/ location: mbox:/srv/imapd/shared/archiv/maildir:CONTROL=/srv/imapd/user/%u/shared-settings/archiv/ control:INDEX=/srv/imapd/user/%u/shared-settings/archiv/index Dovecot use the index statement with the correct subdirectories and indexfiles at /srv/imapd/user/%u/shared-settings/archiv but don't use the control statement and use a .subscriptions files at /srv/imapd/shared/archiv/maildir instead. :-( Has anybody a idea for this? Where is my fault? Here is the output of dovecot -n: # /etc/dovecot.conf ssl_cert_file: /etc/pki/tls/certs/cac.is-a-geek.com.cert ssl_key_file: /etc/pki/tls/private/cac.is-a-geek.com.key login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_extra_groups: email dotlock_use_excl: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins: zlib mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle tb-extra-mailbox-sep imap_client_workarounds(imap): outlook-idle tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle namespace: type: private separator: / location: maildir:/srv/imapd/user/%u/maildir inbox: yes namespace: type: public separator: / prefix: Public/ location: maildir:/srv/imapd/shared/public/maildir:CONTROL=/srv/imapd/user/%u/shared-settings/publ ic/control:INDEX=/srv/imapd/user/%u/shared-settings/public/index namespace: type: public separator: / prefix: Archiv/ location: mbox:/srv/imapd/shared/archiv/maildir:CONTROL=/srv/imapd/user/%u/shared-settings/archiv/ control:INDEX=/srv/imapd/user/%u/shared-settings/archiv/index auth default: passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: static args: uid=600 gid=600 Mfg. Stefan Klatt - -- CaC, Computer and Communication Inhaber Stefan Klatt Triftstrasse 9 60528 Frankfurt Germany Tel.: +49-(0)172-6807809 Tel.: +49-(0)69-67808-900 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGPhoB+AkeCg4UPr4RAiz0AKCV1POqMdlUwSeWzWziSDF6N+4wrQCeMY9E 4AvWqiTwaS1OnCLFYPdZwjk= =Nw4r -----END PGP SIGNATURE-----

2 1

[Dovecot] Sieve plugin
by Luigi Rosa 11 May '07

11 May '07

The Sieve plugin page of Wiki documentation (http://wiki.dovecot.org/LDA/Sieve?highlight=%28filter%29) says: "It's also not a good idea to build the plugin against self-compiled Dovecot sources, but then actually use a prebuilt binary package of Dovecot." Why isn't a good idea? Ciao, luigi -- / +--[Luigi Rosa]-- \ Every time you've heard someone say they saw a ghost, or an angel. Every story you've ever heard about vampires, werewolves, or aliens, is the system assimilating some program that's doing something they're not supposed to be doing. --The Oracle, "Matrix Reloaded"

2 1

[Dovecot] ownership/perms on DC file objects
by Stewart Dean 10 May '07

10 May '07

Back in late March I asked what ownership and permissions Dovecot's own directories and files should have; I have an obsessive nature, and wanted to get things right :(.. On April Fool's Day :), Timo responded: > Dovecot opens pretty much all the configuration etc. files as root > before dropping the privileges. So in general they could all be 0600 > owned by root In my typical turtle-crawl fashion, I got around to today, but the onership/perms came out somewhat differently, which I put down here for anyone that wants to know......... I set everything under /var/run/dovecot to 600, owned by root:dovecot > 4242 root@mercury:/var/run/dovecot ## ls -alR > total 24 > drw------- 3 root dovecot 512 Mar 06 15:27 ./ > drwxr-xr-x 3 root system 512 Apr 18 2006 ../ > drw------- 2 root dovecot 512 May 09 10:37 login/ > ./login: > total 24 > drw------- 2 root dovecot 512 May 09 10:37 ./ > drw------- 3 root dovecot 512 Mar 06 15:27 ../ > srw------- 1 root dovecot 0 May 09 10:37 default= > -rw------- 1 root dovecot 230 May 09 10:36 ssl-parameters.dat > And restarted dovecot > 4243 root@mercury:/var/run/dovecot ## dovecot > but apparently /var/run/dovecot/login should be 750, but DC dealt with that automagically > Warning: Corrected permissions for login directory /var/run/dovecot/login > 4244 root@mercury:/var/run/dovecot ## ls -alR > total 24 > drw------- 3 root dovecot 512 Mar 06 15:27 ./ > drwxr-xr-x 3 root system 512 Apr 18 2006 ../ > drwxr-x--- 2 root dovecot 512 May 10 12:47 login/ > ./login: > total 24 > drwxr-x--- 2 root dovecot 512 May 10 12:47 ./ > drw------- 3 root dovecot 512 Mar 06 15:27 ../ > srwxrwxrwx 1 root dovecot 0 May 10 12:47 default= > -rw------- 1 root dovecot 230 May 09 10:36 ssl-parameters.dat > ...but then got in the syslog > May 10 12:49:51 mercury mail:err|error dovecot: imap-login: Can't open SSL param > eter file ssl-parameters.dat: Permission denied > May 10 12:49:51 mercury mail:err|error dovecot: child 1380384 (login) returned error 89 > > So I made it 640 which seems to do. > 4246 root@mercury:/var/run/dovecot ## chmod 640 login/ssl-parameters.dat > 4247 root@mercury:/var/run/dovecot ## ls -alR login > total 24 > drwxr-x--- 2 root dovecot 512 May 10 12:47 ./ > drw------- 3 root dovecot 512 Mar 06 15:27 ../ > srwxrwxrwx 1 root dovecot 0 May 10 12:47 default= > -rw-r----- 1 root dovecot 230 May 09 10:36 ssl-parameters.dat So it seems this will do (for others who obsess over things small):: a) /var/run/dovecot can be 600, root:dovecot b) /var/run/dovecot/login should be 750, root:dovecot c) /var/run/dovecot/login/ssl-parameters.dat might be 640, root: dovecot -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

1 0

Re: [Dovecot] dovecot-dspam-integration
by Johannes Berg 10 May '07

10 May '07

Hi Trever, Please copy the mailing list too. On Mon, 2007-05-07 at 09:45 -0600, Trever L. Adams wrote: > 1) Why on line 350 of your code do you say "do (almost) everything"? > What is left out? Is it done still by dovcecot? I don't remember. You can probably find out by comparing the code. > 2) "I decided that hardlinking into special folders was too much work > (especially with removing the mails again!), so for now my plugin is > calling the dspam client directly." What exactly was the problem? Can't > the problem be as simple as: > > a) unlink the message from inappropriate folder (if moving into spam, > unlink from unlearn, if moving out unlink from learn) using the file > name below > b) link the message to the appropriate folder with the name of <MESSAGE > ID>- > > Why do a without seeing if the file exists, well, if you use the full > message ID, because if people are following the rules with their MTA's > and/or mail clients, then message ID should be unique as it must be > unique on their system and it seems that all of them append the hose > name at the end, making it globally unique (or most likely so...). If > this is the case, then the client name. If this is in question then make > it <MESSAGE ID><DATE><FROM>. That should make it globally unique. > > This keeps one from having to mess with keeping lists. If people keep > dragging the same message to their outbox from sent, then the MESSAGE ID > may not be unique, but it will fit all of the same messages, hence I > think it isn't a problem. Also, unlink will cause the os to traverse the > directory, why should we do it as well as it will be a non-fatal error > if it doesn't exist. > > If you take my suggestions, and I am not just being stupid, please > provide some example processes/cron jobs to go with your code in the top > comments. Actually, the thing we care about is the dspam signature which is unique. So that's not a problem. The point is that you have to (a) when no files exist: move into spam: create a file <sig> with contents "spam" move out of spam: create a file <sig> with contents "notspam" (b) when <sig> file exists with contents "spam": move into spam: shouldn't happen move out of spam: unlink file (c) when <sig> file exists with contents "notspam": move into spam: unlink file move out of spam: shouldn't happen the cron job would have to iterate through all these files and call dspam depending on the contents of the file. And then it all has to be atomic. It's not really all that complex, but I was too lazy to implement it. johannes

2 13

[Dovecot] Duplicate emails with several clients
by Erick Perez 10 May '07

10 May '07

Hi, I'm using Centos 4.4 (which is redhat linux but free) that comes with dovecot-0.99.11-4.EL4. I have done a clean reinstall of the server and I have users reporting that everytime they hit "send/receive" in their outlook or outlook express software, they get the same messages, as well as the new ones, over and over again. I use postfix + dovecot and only the pop3 protocol. My dovecot.conf has the following relevant entries default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u client_workarounds = oe6-fetch-no-newmail outlook-idle outlook-pop3-no-nuls mbox_locks = fcntl everything else is at default value. Also, we do not upgrade dovecot because it is not part of the upstream provider, and we do not want to break binary compatibility updates. Thanks for your guidance. -- ------------------------------------------------------------ Erick Perez Panama Sistemas Integradores de Telefonia IP y Soluciones Para Centros de Datos Panama, Republica de Panama Cel Panama. +(507) 6694-4780 ------------------------------------------------------------

2 3

[Dovecot] Managesieve: first steps
by Joseba Torre 10 May '07

10 May '07

Hi, I'm trying to get managesieve to work but, as usual, I have some issues... - First of all, the compilation process after applying the patch is a bit strange. I've used this way (i'm using centOS 4 for this pre-tests): $ tar zxvf dovecot-1.0.0.tar.gz $ cd dovecot-1.0.0 $ gzip -cd ../dovecot-1.0.rc28-MANAGESIEVE-v4.diff.gz | patch -p1 $ autoreconf (This ends with an error about missing ./ylwrap) $ automake --add-missing (This copies ylwrap to ., but fails if executed before autoreconf) $ autoreconf $ ./configure && make && sudo make install but I'm quite sure that should exist a better way... - After this, adding protocols = imap imaps pop3 pop3s managesieve and protocol managesieve { listen = *:2000 login_executable = /usr/local/libexec/dovecot/managesieve-login mail_executable = /usr/local/libexec/dovecot/managesieve } to dovecot.conf, everything seems to work fine (pop3 and imap work as usual, and I can connect to the managesieve port), but dovecot -n gives no output. (If I put out managesieve from the protocols, dovecot -n gives the normal output again). (This output is appended at the end) - Finally, I'm using Plain as the authentication mechanism, and I've been unable to connect using kmail or the sieve extension for thunderbird. As I'm not sure if any of these really work, I'll setup horde for further testing. Is there anything that I should be aware of? dovecot -n output: # /usr/local/etc/dovecot.conf syslog_facility: local1 protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_cert_file: /usr/share/ssl/certs/dovecot-beta.pem ssl_key_file: /usr/share/ssl/certs/dovecot-beta.pem login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login mail_location: maildir:~/Maildir:INDEX=/var/dovecot/%u:CONTROL=/var/dovecot/%u mmap_disable: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %v.%u auth default: master_user_separator: * passdb: driver: passwd-file args: /usr/local/etc/dovecot-master.conf master: yes passdb: driver: pam args: blocking=yes userdb: driver: passwd args: blocking=yes socket: type: listen client: master: path: /var/run/dovecot/auth-master plugin: quota: fs Thanks. -- Joseba Torre. CIDIR Bizkaia.

1 0