- dovecot - dovecot.org

[Dovecot] Update Dovecot index files on maildrop delivery?
by Kārlis Repsons 19 Jan '10

19 Jan '10

Hi all, is there some easy way to inform Dovecot about a new delivery, which has happened after postfix invoked maildrop, so the index files would be updated?

3 5

[Dovecot] Socket permission 432/384 and dovecot.conf
by Seba 19 Jan '10

19 Jan '10

Sorry for that question but: when you set in dovecot.conf this for example: socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } and you run "dovecot -n" you'll see client: path: /var/spool/postfix/private/auth mode: 432 I'm wondering about the mode "432" - how is this value calculated? Same for the auth/master socket socket - the value ist "384" and in dovecot.conf it's 0600. Thanks for any info. Seba

3 2

[Dovecot] Dovecot Proxy and environment variables
by BaQs 19 Jan '10

19 Jan '10

Dear list, First of all, I am French so excuse my bad english. I am currently using dovecot proxy feature, using sql backend. I "proxy" the imap/pop requests to another server, let's say server2. On server2, I use a script to keep up to date a "pop before smtp auth" database. I used mail_executable = /path/to/this/script.sh ... My problem is: the $IP environment variable on server2 is the proxy's IP. How could I give a variable from proxy to server2, or simply get the real client public IP ? Thanks a lot in advance for your answers Pierre. PS: let me also thank very much dovecot developers and community !

3 7

[Dovecot] No filelocking at "shared-mailboxes" dictionary?
by Peer Heinlein 19 Jan '10

19 Jan '10

Using imapsync I changed many ACLs on many accounts simultaneously in four concurrent IMAP-sessions. I started with an empty file "shared-mailboxes". But after the sync the file "shared-mailboxes" has been crashed. I found broken lines and I'm missing some entrys. Is it possible that there's no filelocking on that file? I used the ext3 filesystem. That's what shred-mailboxes looks like at the moment: shared/shared-box 1 shared/shared-boxes/user/user1.example.com/user2.example.com 1 .example.com/user5.example.com 1 hared/shared-boxes/user/user6.example.com/user4.example.c2442203233424^? 1 ser/user7.example.com/user2.example.com Peer dovecot -n: # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27.39-0.2-default x86_64 openSUSE 11.1 (x86_64) protocols: imap imaps managesieve ssl_cert_file: /etc/ssl/old.pem ssl_key_file: /etc/ssl/old.pem shutdown_clients: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login login_process_per_connection: no login_max_processes_count: 512 max_mail_processes: 1024 mail_max_userip_connections(default): 40 mail_max_userip_connections(imap): 40 mail_max_userip_connections(managesieve): 10 verbose_proctitle: yes mail_uid: vmail mail_gid: vmail mail_location: maildir:~/Maildir mail_executable(default): /usr/lib/dovecot/imap-usernamenmigration mail_executable(imap): /usr/lib/dovecot/imap-usernamenmigration mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota acl imap_acl mail_plugins(imap): quota imap_quota acl imap_acl mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib64/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib64/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib64/dovecot/modules/managesieve namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: shared separator: / prefix: zz_SHARED_ACCOUNTS/%%u/ location: maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u list: yes lda: postmaster_address: postmaster(a)iea-dpc.org mail_plugins: quota acl sieve mail_plugin_dir: /usr/lib64/dovecot/modules/lda quota_full_tempfail: yes auth default: mechanisms: plain login digest-md5 cram-md5 verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /etc/dovecot/userdb userdb: driver: passwd-file args: /etc/dovecot/userdb userdb: driver: static args: uid=5001 gid=5001 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: vmail plugin: quota: maildir quota_rule: *:storage=102400 acl: vfile acl_shared_dict: file:/var/lib/dovecot/shared-mailboxes sieve: ~/.dovecot.sieve sieve_dir: ~/sieve -- Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030 / 40 50 51 - 0 Fax: 030 / 40 50 51 - 19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

2 1

[Dovecot] Fail to handle . and - in mailaddresses
by Mika 18 Jan '10

18 Jan '10

Hi, I seem to have run into a bug. Dot and dash is allowed chars in mail addresses, so a ...---...@ should work. Filtered out domainname and IP's for security reasons. And yes this works with MDaemon as example. Setup is postfix using Dovecot for deliver. Version: 1.2.9 OS: Linux ADM64 (Ubuntu 8.04LTS) Tried to deliver mail to rfc compliant mail address ...---...@domain. # 1.2.9: /opt/dovecot/etc/dovecot.conf # OS: Linux 2.6.24-25-server i686 Ubuntu 8.04.3 LTS ext3 log_path: /var/log/dovecot protocols: imaps imap listen: 127.0.0.1 ssl_listen: :943 ssl_cert_file: /etc/ssl/certs/secure.crt ssl_key_file: /etc/ssl/private/secure.key login_dir: /opt/dovecot/var/run/dovecot/login login_executable: /opt/dovecot/libexec/dovecot/imap-login mail_gid: 1005 mail_location: maildir:/opt/vmail/%d/%n/Maildir lda: postmaster_address: postmaster(a)domain.com sendmail_path: /usr/sbin/sendmail auth_socket_path: /var/run/dovecot/auth-master log_path: /opt/vmail/dovecot-deliver.log auth default: mechanisms: plain login passdb: driver: pam passdb: driver: sql args: /opt/dovecot/etc/dovecot-sql.conf userdb: driver: passwd userdb: driver: static args: uid=5000 gid=5000 home=/opt/vmail/%d/%n allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail >From Deliver logfile: deliver(...---...(a)domain.com): Jan 14 08:18:24 Info: msgid=<798c378b1001132318y4a027757m37a668f48730e6c(a)mail.gmail.com>: saved mail to INBOX # Does not seem to end up in any of the files in Maildir, new/tmp folders are empty. Maildir/cur# grep ...---...(a)domain.com * Maildir/cur# //Mika

2 2

[Dovecot] sieve: discarding vacation response
by wenjie zheng 18 Jan '10

18 Jan '10

Configuration: RHEL 5.3, Dovecot 2.0 beta1, dovecot-2.0-sieve (1week old) [wenjie@build dovecot2-2.0.beta1]$ telnet mail4a 24 Trying 172.19.1.74... Connected to mail4a.cloud.dev.mlsrvr.com (172.19.1.74). Escape character is '^]'. 220 mail4a Dovecot LMTP ready mail from:<testmail4a50(a)dev.p4nt5.com> 250 2.1.0 OK rcpt to:<testmail4a2(a)dev.p4nt5.com> 250 2.1.5 OK DATA 354 OK From: <testmail4a50(a)dev.p4nt5.com> To: foo Subject: hello Hello there . 250 2.0.0 <testmail4a2(a)dev.p4nt5.com> eMcYKg7gUEt8ewAA0TR52A Saved quit 221 2.0.0 Client quit Connection closed by foreign host. testmail4a2(a)dev.p4nt5.com has a local .dovecot.sieve file, which contains a vacation auto response. #begin require ["fileinto", "body", "vacation"]; vacation :days 1 text: I am away. . ; keep; #end In the log: Jan 15 15:38:07 mail4a dovecot: lmtp(31612, testmail4a2(a)dev.p4nt5.com) eMcYKg7gUEt8ewAA0TR52A: sieve: msgid=unspecified: discarding vacation response for message implicitly delivered to <testmail4a2(a)dev.p4nt5.com> Jan 15 15:38:07 mail4a dovecot: lmtp(31612, testmail4a2(a)dev.p4nt5.com) eMcYKg7gUEt8ewAA0TR52A: sieve: msgid=unspecified: stored mail into mailbox 'INBOX' Thanks, Wenjie

2 2

[Dovecot] Upgrade path questions
by Thomas M Goerger 18 Jan '10

18 Jan '10

Hi, We are currently running Dovecot v1.1.6 on our servers, and are contemplating an upgrade to 1.2, or 2.0 soon. We are wondering how many organizations are still running a 1.1 version of Dovecot, and if anyone has any thoughts on this transition. Have you upgraded from 1.1 to 1.2? What are your experiences with this? Have you upgraded from 1.1 to 2.0 directly? What are your experiences this way? We are also running an environment with both mbox and maildir formats. How many of you are running similarly, or are running solely maildir or mbox? We're just looking to gather information going forward, and anything you might be able to contribute would be very helpful. Thanks! ************************************************************************* * Tom Goerger - Email/Unix System Administrator * * * * University of Minnesota Email: tmg(a)umn.edu * * Operations, Infrastructure and Architecture Phone: 4-5804 * * Internet Services Office: 626J WBOB * * * *************************************************************************

4 3

[Dovecot] Inotify instance limit for user exceeded
by Lampa 18 Jan '10

18 Jan '10

Hello, i saw in my log followed messages: dovecot: 2010-01-18 13:20:54 Warning: IMAP(user1(a)domain1.com): Inotify instance limit for user exceeded, disabling. dovecot: 2010-01-18 13:21:01 Warning: IMAP(user2(a)domain2.com): Inotify instance limit for user exceeded, disabling. dovecot: 2010-01-18 13:21:23 Warning: IMAP(user2(a)domain2.com: Inotify instance limit for user exceeded, disabling. dovecot -c dovecot-domain1.com.conf -n: # 1.0.10: dovecot-domain1.com.conf remax-czech.cz base_dir: /var/run/domain1.com log_path: /var/log/dovecot/domain1.com/dovecot.log info_log_path: /var/log/dovecot/domain1.com/info.log log_timestamp: %F %T protocols: imap imaps pop3 pop3s listen: 127.0.0.1 ssl_cert_file: /usr/local/ssl/mail/domain1.comserver.crt ssl_key_file: /usr/local/ssl/mail/domain1.com/server.key disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot-domain1.com/login login_executable(default): /usr/local/dovecot/bin/dovecot/imap-login login_executable(imap): /usr/local/dovecot/bin/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/bin/dovecot/pop3-login login_max_processes_count: 40 login_max_connections: 42 max_mail_processes: 2000 verbose_proctitle: yes first_valid_uid: 507 last_valid_uid: 507 first_valid_gid: 502 last_valid_gid: 502 fsync_disable: yes mail_executable(default): /usr/local/dovecot/bin/dovecot/imap mail_executable(imap): /usr/local/dovecot/bin/dovecot/imap mail_executable(pop3): /usr/local/dovecot/bin/dovecot/pop3 mail_process_size: 300 mail_plugin_dir(default): /usr/local/dovecot-1.0.10/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot-1.0.10/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot-1.0.10/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: mechanisms: plain login user: vmail verbose: yes passdb: driver: vpopmail userdb: driver: vpopmail There is about 2500 users on domain1.com, so i should raise max_mail_processes ? -- Lampa

2 1

[Dovecot] unlinking
by David Halik 18 Jan '10

18 Jan '10

Quick question. How important are these? Are the errors recoverable and not a big deal, or are they actually a problem? I see a few of these randomly over the course of the day. Jan 15 10:04:04 gehenna13.rutgers.edu dovecot: IMAP(user): unlink(/rci/nqu/rci/u8/user/dovecot/.such and such maildir/.nfs00000000001e951000002b8d) failed: Device or resource busy Jan 15 10:04:04 gehenna13.rutgers.edu dovecot: IMAP(user): unlink(/rci/nqu/rci/u8/user/dovecot/.such and such maildir/.nfs00000000001e951000002b8d) failed: Device or resource busy Jan 15 10:04:04 gehenna13.rutgers.edu dovecot: IMAP(user): unlink_directory(/rci/nqu/rci/u8/user/dovecot/.such and such maildir) failed: Device or resource busy Jan 15 10:04:04 gehenna13.rutgers.edu dovecot: IMAP(user): unlink_directory(/rci/nqu/rci/u8/user/dovecot/.such and such maildir) failed: Device or resource busy -- ================================ David Halik System Administrator OIT-CSS Rutgers University dhalik(a)jla.rutgers.edu ================================

3 3

[Dovecot] Strange permission problem with Maildir
by tkin1t3asy 18 Jan '10

18 Jan '10

I have this very strange problem with Dovecot spitting out a file permissions error but further testing seems to show it being an inaccurate message. POP3(username): maildir: data ~/Maildir POP3(username): maildir++: root =/home/ssb201/Maildir, index=, control=, inbox=/home/ssb201/Maildir POP3(username): stat(/home/username/Maildir/tmp) failed: Permission denied (euid=500(username) egid=500(username) missing +x perm: /home/username/Maildir) POP3(username): Couldn't open INBOX... as you can see below the permissions are correct: root@host:/home/username# ls -al Maildir/ total 744 drwx------ 8 username username 220 2010-01-13 06:27 . drwxr-xr-x 18 username username 80 2010-01-13 06:14 .. drwx------ 2 username username 108480 2010-01-14 20:56 cur -rw------- 1 username username 65272 2010-01-14 20:56 dovecot.index -rw------- 1 username username 382976 2010-01-14 20:56 dovecot.index.cache -rw------- 1 username username 6836 2010-01-14 20:56 dovecot.index.log -rw------- 1 username username 309472 2010-01-14 20:56 dovecot-uidlist -rw------- 1 username username 8 2010-01-14 20:56 dovecot-uidvalidity -rw------- 1 username username 0 2010-01-14 20:56 dovecot-uidvalidity.4a090e80 drwx------ 2 username username 40 2010-01-14 20:56 new drwx------ 2 username username 40 2010-01-14 20:56 tmp if I rename ~/Maildir to ~/Maildir.orig and let dovecot create a new directory it works fine with no errors. root@host:/home/username# ls -al Maildir total 28 drwx------ 5 username username 220 2010-01-14 21:19 . drwxr-xr-x 19 username username 100 2010-01-14 21:19 .. drwx------ 2 username username 40 2010-01-14 21:19 cur -rw------- 1 username username 16384 2010-01-14 21:19 dovecot.index.cache -rw------- 1 username username 468 2010-01-14 21:19 dovecot.index.log -rw------- 1 username username 70 2010-01-14 21:19 dovecot-uidlist -rw------- 1 username username 8 2010-01-14 21:19 dovecot-uidvalidity -rw------- 1 username username 0 2010-01-14 21:19 dovecot-uidvalidity.4b4f8a6e drwx------ 2 username username 60 2010-01-14 21:19 new drwx------ 2 username username 40 2010-01-14 21:19 tmp If I rename the newly created ~/Maildir to ~/Maildir.new, and rename ~/Maildir.orig to ~/Maildir the original directory works now with no "+x perm" error. This would seem to imply that dovecot is modifying something, somewhere else on the system when it creates the mail directory. What could this be? -- View this message in context: http://old.nabble.com/Strange-permission-problem-with-Maildir-tp27168284p27… Sent from the Dovecot mailing list archive at Nabble.com.

2 1