- dovecot - dovecot.org

[Dovecot] Upgrade from 1.00 to 1.0.1
by Jon 09 Jul '07

09 Jul '07

Hi, I'm getting a bunch of errors since I upgraded to 1.0.0. I understand now that some of them are bug related to release 1.0.0. I'm about to upgrade to 1.0.1. Does anyone know if there are changes in the config file btwn these to versions? Also, what is the best way to do the upgrade? Can I just run ./configure : make : make install : killlall -HUP dovetcot? Best Regards - Jon

7 9

[Dovecot] Tbird-DC state problem
by Stewart Dean 09 Jul '07

09 Jul '07

A experienced sysadmin who's doing some guinea-pig use of DC just ran into the following situation: 1) He brings up SeaMonkey 2) About 30 minutes later, he's in the middle of some involved messaging, mistakenly hits the redX in the top right of the SeaMonkey window, knocking himself out of SeaMonkey. 3) He immediately reinvokes SeaMonkey, all appeared to be OK Viewed some e-mail and some web page references, tries to send a message and then the Send hung for a time with a message "Sending Authenticate Info"..after some minutes, a new E-mail window appeared stating the "Server reported a timeout". As far as the message, it was apparently sent successfully, and saved in the Sent folder successfully. 4) He calls me in. I look through the syslog logging. There is nothing in the syslog critical stuff...and everything in the maillog looks normal. 5) He starts another message, tries to save it to Drafts and that hangs 6) I look more closely at the maillog and see a lot of logins (one a minute in some cases, but all appear to have been cleanly executed) plus one bunch of disconnected messages with one disconnected in idle in the period when the write to the Drafts would have been hung. Could it be that DC was in the middle of clean up in the initial disconnect/reconnect and SeaMonkey came back in the middle of it and one or the other's state tables got messed up (or both of them)? Shutting out of SeaMonkey, waiting a minute and reconnecting seems to have gotten things working again. Any comments? Anything I should be looking for? OTOH, this is the first real problem I've seen in some person-months of testing..... -- ==== 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

[Dovecot] PHP implementation of dovecotpw passwords
by Frank Church 09 Jul '07

09 Jul '07

I am looking for PHP functions that implement passwords that much the dovecotpw implementation. I downloaded one from PEAR, Crypt_HMAC, but the passwords it generates look nothing like the dovecotpw passwords, which could be my fault because I know nothing about the field. Is there a guide or some library that implements them to match dovecotpw?

4 4

[Dovecot] Your IMAP server has closed the connection.
by Dehnert James Sr 09 Jul '07

09 Jul '07

I'm getting a large number of ... "Your IMAP server has closed the connection. This may occur if you have left the connection idle for too long." errors. These are confusing my clients. Is there a way to set the timeout on the dovecot server to help avoid this?

4 6

[Dovecot] Unable to send email out using Dovecot SASL
by dovecot＠convergenz.biz 06 Jul '07

06 Jul '07

Hi, I am currently using Dovecot 1.0.rc17 with Postfix 2.3.8 on Ubuntu. So far I'm able to receive my email using dovecot pop3 but I can't send out the email. Anybody managed to get Postfix with Dovecot SASL support so far? What do I missed out? Below is my configure: #-----------/dovecot.conf-------------- base_dir: /var/run/dovecot/ log_timestamp: .%Y-%m-%d %H:%M:%S . 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: /etc/ssl/mail-cert.pem ssl_key_file: /etc/ssl/mail-key.pem login_dir: /var/run/dovecot//login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login first_valid_uid: 150 last_valid_uid: 150 mail_extra_groups: mail mail_location: maildir:/var/vmail/%d/%u maildir_copy_with_hardlinks: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail 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: user: nobody verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: mail #-----------/dovecot.conf end-------------- #-----------/dovecot-sql.conf-------------- driver = mysql connect = host=localhost dbname=postfix user=postfix password=Password default_pass_scheme = MD5-CRYPT user_query = SELECT '/var/vmail/%d/%n' as home, 'maildir:/var/vmail/%d/%n' as mail, 150 AS uid, 8 AS gid, concat('dirsize:storage=', quota) AS quota FROM mailbox WHERE username = '%u' AND active = '1' password_query = SELECT username as user, password, '/var/vmail/%d/%n' as userdb_home, 'maildir:/var/vmail/%d/%n' as userdb_mail, 150 as userdb_uid, 8 as userdb_gid FROM mailbox WHERE username = '%u' AND active = '1' #-----------/dovecot-sql.conf end-------------- Rgds CH

4 3

[Dovecot] utime : operation not permitted
by Jim Horner 06 Jul '07

06 Jul '07

With the upgrade to 1.0.1, I am seeing some errors/warnings dovecot: IMAP(jhorner(a)arinbe.com): utime(/home/arinbe/Maildir/.info/tmp) failed: Operation not permitted: 1 Time(s) dovecot: IMAP(jhorner(a)arinbe.com): utime(/home/arinbe/Maildir/.resumes.vabch/tmp) failed: Operation not permitted: 1 Time(s) Different directories on different days. Different users on different days. Always /tmp directory. Always a /tmp of a shared namespace. The /tmp directory in question is mode 770, with group users, just like the rest of the /arinbe/Maildir hierarchy. As far as I can tell it doesn't affect anything on the client side. dovecot -n ssl_cert_file: /etc/ssl/arinbe/arinbe-godaddy.crt ssl_key_file: /etc/ssl/arinbe/arinbe.key ssl_cipher_list: ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:!LOW:!SSLv2:+EXP:@STRENGTH login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_greeting: I am the IMAP Whisperer and I am ready. mail_location: maildir:%h/Maildir umask: 7 mail_plugins: acl imap_client_workarounds: delay-newmail outlook-idle namespace: type: public separator: . prefix: COMPANY. location: maildir:/home/arinbe/Maildir:CONTROL=%h/shared-settings/company/control:INDEX=%h/shared-settings/company/index namespace: type: public separator: . prefix: ROOTMAIL. location: maildir:/home/rootmail/Maildir:CONTROL=%h/shared-settings/rootmail/control:INDEX=%h/shared-settings/rootmail/index namespace: type: private separator: . prefix: INBOX. inbox: yes auth default: mechanisms: plain login default_realm: arinbe.com user: nobody passdb: driver: ldap args: /etc/dovecot/dovecot-ldap-arinbe.conf passdb: driver: ldap args: /etc/dovecot/dovecot-ldap-domains.conf userdb: driver: prefetch userdb: driver: ldap args: /etc/dovecot/dovecot-ldap-arinbe.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap-domains.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 438 user: postfix group: postfix master: path: /usr/local/var/run/dovecot/auth-master mode: 432 user: nobody group: mail plugin: acl: vfile:/etc/dovecot/dovecot-acls

2 9

[Dovecot] Debian packages for Dovecot 1.0.1xx (sarge)
by Moritz Mertinkat 06 Jul '07

06 Jul '07

Hi there, i'm looking for Debian sarge dovecot packages (yes, still running sarge). Anyone here that has a backported package? Greetings, Moritz

2 1

[Dovecot] modules/imap/lib02_imap_quota_plugin.so: undefined symbol: quota_set
by Philipp Kolmann 06 Jul '07

06 Jul '07

Hi, I wanted to enable FS quota support in dovecot, and have configured the following directives: protocol imap { mail_plugins = imap_quota } plugin { quota = fs } With this additional settings, my normally working dovecot.conf doesn't start anymore: Starting mail server: dovecotEdlopen(/usr/lib/dovecot/modules/imap/lib02_imap_quota_plugin.so) failed: /usr/lib/dovecot/modules/imap/lib02_imap_quota_plugin.so: undefined symbol: quota_set Error: imap dump-capability process returned 89 I have tested this issue on the following versions: * Debian etch: 1.0.rc15 * RedHat AS 5: 1.0.rc15 * Debian sid: 1.0.0 Thanks for any help in this issue. Philipp Kolmann -- If you have problems in Windows: REBOOT If you have problems in Linux: BE ROOT

3 3

[Dovecot] assertion failed & invalid password field
by Ralf Hildebrandt 06 Jul '07

06 Jul '07

I'm getting these in my log: Jul 6 09:52:51 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 6 09:52:51 postamt dovecot: child 31576 (login) killed with signal 6 Jul 6 10:37:44 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 6 10:37:44 postamt dovecot: child 25241 (login) killed with signal 6 Jul 6 13:14:51 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 6 13:14:51 postamt dovecot: child 4418 (login) killed with signal 6 and I get those for accounts I deactivated using "usermod -L", maybe dovecot should log something like "account disabled" instead: Jul 6 11:07:01 postamt dovecot: auth(default): shadow(vnedwed,77.128.63.72): invalid password field Jul 6 11:07:06 postamt dovecot: auth(default): shadow(vnedwed,77.128.63.72): invalid password field Jul 6 14:12:40 postamt dovecot: auth(default): shadow(jechafch,141.42.4.251): invalid password field This is dovecot-1.0.1 -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) plonk(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de Your eyes are weary from staring at the CRT. You feel sleepy. Notice how restful it is to watch the cursor blink. Close your eyes. The opinions stated above are yours. You cannot imagine why you ever felt otherwise.

1 0

[Dovecot] Virtual servers
by John Hedges 06 Jul '07

06 Jul '07

Hello I'm migrating from Courier to Dovecot (1.0.rc15) on Debian. I am trying to set up virtual servers based on the principal in this thread: http://www.dovecot.org/list/dovecot/2006-October/017165.html which suggests something like this to support multiple certificates: server foo { listen = 1.2.3.4 ssl_cert_file = /etc/ssl/certs/foo.cer } server bar { listen = 1.2.3.5 ssl_cert_file = /etc/ssl/certs/bar.cer } My virtual configs look like this: server mail.domain1.org { listen = 1.2.3.4 protocols = pop3 pop3s imap imaps ssl_cert_file = /etc/mail/hosts/domain1.org/ssl.crt ssl_key_file = /etc/mail/hosts/domain1.org/ssl.key auth default { mechanisms = plain passdb passwd-file { args = /etc/mail/hosts/domain1.org/userdb } userdb passwd-file { args = /etc/mail/hosts/domain1.org/userdb } } } server mail.domain2.org { listen = 1.2.3.5 protocols = imap imaps ssl_cert_file = /etc/mail/hosts/domain2.org/ssl.crt ssl_key_file = /etc/mail/hosts/domain2.org/ssl.key auth default { mechanisms = plain passdb passwd-file { args = /etc/mail/hosts/domain2.org/userdb } userdb passwd-file { args = /etc/mail/hosts/domain2.org/userdb } } } but I can't get ithis to work. Dovecot starts but authorisation fails. Is this kind of setup possible - is it possible to configure different passwd-files for connections on different IPs, or am I going to have to run separate instances of Dovecot for each virtual host? Thanks John

2 1