- dovecot - dovecot.org

[Dovecot] dovecot-1.1.3 failure to install
by tonj 29 Sep '08

29 Sep '08

I'm using Fedora 9 I downloaded dovecot-1.1.3.tar.gz and extracted it. I then opened a terminal in the extracted window. Your install instructions say: For most people, the usual: ./configure make sudo make install but when I did them I got [root@mydomain dovecot-1.1.3]# ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for style of include used by make... GNU checking for gcc... no checking for cc... no checking for cl.exe... no configure: error: no acceptable C compiler found in $PATH See `config.log' for more details. [root@mydomain dovecot-1.1.3]# make make: *** No targets specified and no makefile found. Stop. [root@mydomain dovecot-1.1.3]# sudo make install make: *** No rule to make target `install'. Stop. [root@mydomain dovecot-1.1.3]# can you tell me why the install won't work? thanks for any advice.

5 9

[Dovecot] Mailing list / dovecot.org down this weekend
by Timo Sirainen 27 Sep '08

27 Sep '08

Apparently the building where dovecot.org server is located will lose its electricity for something like 9-26 hours this weekend. During this time the mailing list will be down, but the web, hg and wiki will be available in another server. (Well, the wiki depends on if I can get moinmoin fixed on the server.)

1 1

[Dovecot] dovecot imap auth fails to reconnect pgsql backend
by Frank Wang 27 Sep '08

27 Sep '08

Hi, We've observed frequent auth failure recently from the SquirrelMail frontend. The imap server is the dovecot-1.0.7-2 from Centos 5.2. The auth backend is a pgsql database on another server. The only way to make it work is to restart the dovecot, though sometimes it'll recover automatically, but you don't know when. At first we thought there might be a network problem, but we can always run pgsql client from the dovecot server to connect and query the backend database during the auth failure. We then upgraded to dovecot-1.1.3 from atrpms.net yesterday, and still the same. It looks like the dovecot fails to reconnect/retry pgsql backend. The related maillog in 1.0.7 version: Sep 16 02:31:22 mail dovecot: imap-login: Disconnected: Inactivity: method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Sep 16 02:33:20 mail dovecot: imap-login: Disconnected: Inactivity: method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Sep 16 02:38:40 mail dovecot: imap-login: Disconnected: Inactivity: method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured The related maillog in 1.1.3: Sep 21 14:11:24 mail dovecot: imap-login: Disconnected: Inactivity (auth failed, 1 attempts): method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Sep 21 14:14:39 mail dovecot: imap-login: Disconnected: Inactivity (auth failed, 1 attempts): method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Sep 21 14:15:15 mail dovecot: imap-login: Disconnected: Inactivity (no auth attempts): rip=127.0.0.1, lip=127.0.0.1, secured Sep 21 14:23:49 mail dovecot: auth(default): sql(user(a)our.domain,127.0.0.1): Password query failed: Sep 21 14:23:49 mail dovecot: child 15241 (auth) killed with signal 11 Sep 21 14:23:50 mail dovecot: auth(default): pgsql: Connected to internal # dovecot -n # 1.1.3: /etc/dovecot.conf protocols: imap pop3 listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 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_location: maildir:/var/vmail/%d/%n mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota 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): delay-newmail tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login realms: our.domain1 our.domain2 default_realm: our.domain1 user: mail passdb: driver: sql args: /etc/dovecot-sql.conf userdb: driver: static args: uid=508 gid=509 home=/var/vmail/%d/%n/ quota=maildir:storage=512000 socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix plugin: quota: maildir grep -v '^ *$#.*$\?$' /etc/dovecot-sql.conf driver = pgsql connect = host=<pg_server_ip> dbname=<pg_dbname> user=<pg_user> password=<pg_password> default_pass_scheme = PLAIN password_query = SELECT jm || '@%d' as user, password FROM usera where jm = '%n' and forbid = 'N' and ( '%d' = 'our.domain1' or '%d' = 'our.domain2' ) Can someone shed a light on this? Thanks! Regards, Frank Wang

4 12

[Dovecot] problems with auth protocol
by Giorgenes Gelatti 27 Sep '08

27 Sep '08

Hello there, I have a client connecting to dovecot and comunicating like this: * OK Dovecot ready. * AUTHENTICATE MYAUTH + base64 challange base64_response {NNN} * NO Invalid base64 data in continued response The problem is that dovecot seems to reject the response because of the {NNN} in the end of the string. If I remove the {NNN} it authenticates just fine. Any idea of whether it's standard or not? Thanks you.

2 1

[Dovecot] Exim+dovecot and quota check in exim's ACL before real message routing.
by Anton 26 Sep '08

26 Sep '08

Good day. I want to migrate from cyrus-imap to dovecot but I can not find replacement of one feauture presented in the cyrus-imap. It is LMTP. All mail users are virtual and mail works like: username(a)real-domain.com -> anotherusername(a)fake-domain.local. I whould like to check "delivery is possable" in the exim's ACL. In the exim+cirus scheme I use Callout verification from exim to cyrus and if user's quota is exeeded callout returns fail and exim does not take message for queueing. Dovecot has no LMTP and I see no possability to do such callouts. I tried to turn on quotas in the dovecot. Message was taken by the exim placed into exim's queue but cannot be delivered to dovecot with "local_delivery transport output: Quota exceeded" and message stays in queue for a long time. Is any possability to chech quota usage in the exim's ACL befor taking message body ? -- Anton [WARM-RIPE] Stack ltd division head tel. 8 (3822) 555-797

2 2

[Dovecot] Problem when just .dovecot.sieve symlinks changes
by Steffen Kaiser 26 Sep '08

26 Sep '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, well, I'm sort of sure that this was raised in the past, but I do not find the patch / answer of it: I'm running dovecot v1.0.15 from hg (5567:568687e4df02) with managesieve patch v9.2 (there is one change between this and v9.3 except in regards of AUTH so this should not matter.) and dovecot-sieve v1.0.3. When an user issues just "SETACTIVE" in order to activate an _old_ script, deliver does not rebuilt the compiled file. If I peeked the correct code, CMU sieve just stat()s both .dovecot.sieve and .dovecot.sievec, but misses the fact that the symlink's .dovecot.sieve, which is used by the managesieve patch, time is newer. Actually I dimmly remember that the issue was solved somehow, but I did not found how when searching the archives. Shall deliver lstat(.dovecot.sieve) or shall managesieve delete the cache file? Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFI26+7VJMDrex4hCIRAt4GAJ9wqQ0Pvb5SRjK2KZNFuun/K/lNoQCg2Arm EB+eBxKEq/9ZpzJeB00TXOk= =X5aa -----END PGP SIGNATURE-----

2 2

[Dovecot] patch for passdb-vpopmail in v1.1.3
by James Fidell 25 Sep '08

25 Sep '08

I need pop-before-smtp to work with vpopmail (yes, yes, I know, don't ask). Enabling the code to update the relays file brings a small bug to light, fixable with the following patch: --- passdb-vpopmail.c~ 2008-09-25 15:06:47.000000000 +0100 +++ passdb-vpopmail.c 2008-09-25 15:07:14.000000000 +0100 @@ -31,9 +31,9 @@ } if (((vpw->pw_gid & NO_IMAP) != 0 && - strcmp(auth_request->service, "IMAP") == 0) || + strcasecmp(auth_request->service, "IMAP") == 0) || ((vpw->pw_gid & NO_POP) != 0 && - strcmp(auth_request->service, "POP3") == 0)) { + strcasecmp(auth_request->service, "POP3") == 0)) { auth_request_log_info(auth_request, "vpopmail", "%s disabled", auth_request->service); password = NULL; @@ -101,8 +101,8 @@ } #ifdef HAVE_VPOPMAIL_OPEN_SMTP_RELAY - if (strcmp(request->service, "POP3") == 0 || - strcmp(request->service, "IMAP") == 0) { + if (strcasecmp(request->service, "POP3") == 0 || + strcasecmp(request->service, "IMAP") == 0) { const char *host = net_ip2addr(&request->remote_ip); if (host != NULL) { /* use putenv() directly rather than env_put() which (in my case, auth_request->service and request->service are "pop3", so the comparison fails and the relays file is never updated.) James

2 1

[Dovecot] auth(default): vmysql: sql error[3]: MySQL server has gone away
by Jordi Prats 25 Sep '08

25 Sep '08

Hi all, I'm facing this error: dovecot: auth(default): vmysql: sql error[3]: MySQL server has gone away I've been reading this list archives and seems to be a resolved issue (back to 2005), so dovecot should just reconnect but it does not so. I'm using dovecot 1.1.3 with vpopmail 5.4.25 with this configuration: # 1.1.3: /usr/local/etc/dovecot.conf listen: *:143 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 89 last_valid_uid: 89 mail_location: maildir:/home/vpopmail/domains/%d/%n/Maildir auth default: passdb: driver: vpopmail userdb: driver: vpopmail Any ideas? Thanks you! -- Jordi

2 2

[Dovecot] Dovecot LDA and quota
by Jonas Christian 25 Sep '08

25 Sep '08

Hi List, I recently upgraded to Dovecot 1.1.3 on FreeBSD and got into trouble over the quotas. We implemented per-user quotas using plugin { quota = maildir } and protocol lda { mail_plugins = quota } We use a passwd-file userdb with extra fields, which used to be quota=maildir:storage:<bytes> which I changed to quota_rule=*:bytes:<bytes> What happens now is that deliver (the Dovecot LDA) only picks up the quotas set in the maildirsize file in the user's homedir. It doesn't pick up the quota set in the userdb. Also, when I delete the maildirsize file, I doesn't get recreated by the LDA and quotas don't get checked at all. Any ideas? I'd be very grateful for any pointers. Cheers, Jonas

3 7

[Dovecot] Using deliver with postfix
by Rich Winkel 25 Sep '08

25 Sep '08

Hi, I'm trying to set up dovecot 1.1.2 and postfix 2.5.4 on freebsd 7.0. I'm getting permissions problems on auth-master and I'm not sure of the correct settings to use. In postfix's main.cf I have mailbox_command=/usr/local/libexec/dovecot/deliver -d $USER In dovecot.conf I have: socket listen { master { path = /var/run/dovecot/auth-master mode = 0660 user = dovecot group = postfix } ... # ls -l /var/run/dovecot/auth-master srw-rw---- 1 dovecot postfix 0 Sep 18 18:26 /var/run/dovecot/auth-master= In maillog I'm getting: deliver(sumbuddy): Can't connect to auth server at /var/run/dovecot//auth-master: Permission denied (I'm not sure where it's getting the "//" in the path either ...) Also I'm confused about whether I need the postfix options: maildrop_destination_recipient_limit=1 dovecot_destination_concurrency_limit=1 or even whether these are current options in my version of postfix (they don't appear in main.cf.default) Does deliver require such limits on concurrency or # of recipients? Thanks!! Rich

2 4