- dovecot - dovecot.org

[Dovecot] fedora rpm for 2.0 beta?
by joakim＠verona.se 05 Jan '10

05 Jan '10

I'm looking for a spec/rpm file suitable for fedora 11/12, for dovecot and pidgenhole sieve. Has anyone done this yet? Otherwise I will attempt to the dovecot 1.2 spec files for f11. -- Joakim Verona

1 1

[Dovecot] Moving to hardlinks?
by David Abrahams 05 Jan '10

05 Jan '10

I just discovered that dovecot supports copying messages via hard-linking. I have a huge mailbox hierarchy of existing messages that I'd prefer to store that way. Is there a simple way to transform non-hard-linked storage to hard-linked? TIA, -- Dave Abrahams Meet me at BoostCon: http://www.boostcon.com BoostPro Computing http://www.boostpro.com

2 1

[Dovecot] managesieve : unable to authenticate with cram-md5
by Arnaud 05 Jan '10

05 Jan '10

Hi, Seem i switch my dovecot authentification to cram-md5 mecanism, i'am unable to authenticate to managesieve login. log: Dec 16 23:50:16 managesieve-login: Info: Disconnected (disconnected while authenticating): method=CRAM-MD5, rip=192.168.0.100, lip=192.168.0.50 dovecot -n : # 1.2.8: /etc/mailapp/dovecot/dovecot.conf # OS: Linux 2.6.22.8 x86_64 log_path: /var/log/dovecot.log protocols: imaps managesieve listen(default): * listen(imap): * listen(managesieve): *:2000 ssl_listen: *:993 ssl_cert_file: /etc/mailapp/dovecot/certs/dovecot.pem ssl_key_file: /etc/mailapp/dovecot/private/dovecot.pem disable_plaintext_auth: yes login_dir: /usr/local/dovecot/var/run/dovecot/login login_executable(default): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(managesieve): /usr/local/dovecot-manage-sieve/libexec/dovecot/managesieve-login login_greeting: Hello, have an account here ? login_process_per_connection: no verbose_proctitle: yes dotlock_use_excl: no fsync_disable: yes mail_executable(default): /usr/local/dovecot/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot/libexec/dovecot/imap mail_executable(managesieve): /usr/local/dovecot-manage-sieve/libexec/dovecot/managesieve mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(managesieve): /usr/local/dovecot/lib/dovecot/managesieve managesieve_logout_format(default): bytes=%i/%o managesieve_logout_format(imap): bytes=%i/%o managesieve_logout_format(managesieve): bytes (in=%i:out=%o) lda: postmaster_address: postmaster(a)adlx.net hostname: adlx.net mail_plugin_dir: /usr/local/dovecot/lib/dovecot/lda mail_plugins: sieve quota sendmail_path: /usr/sbin/sendmail auth_socket_path: /var/run/dovecot/auth-master log_path: /var/log/dovecot-deliver-errors.log info_log_path: /var/log/dovecot-deliver-infos.log auth default: mechanisms: cram-md5 passdb: driver: sql args: /etc/mailapp/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/mailapp/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 438 master: path: /var/run/dovecot/auth-master mode: 384 user: arnaud group: users plugin: quota: maildir:%n quota quota_rule: *:storage=1G sieve_before: /var/imap/before.sieve sieve: /var/imap/%n.sieve sieve_dir: /var/imap/%d/%n/sieve All works fine with plain authentification and managesieve. Perhaps someone have a workaround. I use thunderbird version 2.0.0.23 as MUA. Thanks for reading !

3 3

[Dovecot] architecture to handle 1000 messages per second?
by Bob Eastbrook 04 Jan '10

04 Jan '10

Can anyone describe an architecture which can handle 1000 IMAP or POP messages per second? Ideally, it would be hosted in the cloud and additional instances could be launched to handle additional load. Bob

8 12

[Dovecot] dovecot as lda
by denlistes＠altern.org 04 Jan '10

04 Jan '10

Hi, I would like to integrate dovecot as lda for the hosting control panel alternc (http://www.alternc.org) I manage to run it for the mail but not for the alias. The problem is that in the configuration of alternc, the mails are seen as aliases in the form user_domain.tld. In a second time, a match is made to see if an "real" alias exists. postmap -q test(a)lists.test.net mysql:/etc/postfix/mydomain.cf test-owner_lists.collectifs.net postmap -q test-owner_lists.test.net mysql:/etc/postfix/myalias.cf "| /var/lib/mailman/mail/mailman owner test" With my configuration, this part is no longer working and dovecot can not find the user: test(a)lists.test.net user unknown Any ideas ? Thanks Denis # main.cf virtual_alias_maps = proxy:mysql:/etc/postfix/myalias.cf, hash:/etc/aliases virtual_mailbox_domains = mysql:/etc/postfix/mydomain.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/myvirtual.cf virtual_transport = dovecot dovecot_destination_recipient_limit = 1 # master.cf dovecot unix - n n - - pipe flags=DRhu user=www-data:www-data argv=/usr/lib/dovecot/deliver -d $(recipient)

1 0

[Dovecot] Kernel warnings
by Thomas Zajic 04 Jan '10

04 Jan '10

Hi, I've been getting these warnings in syslog since I've been running (Linux) kernels 2.6.31.x and up (I'm currently at 2.6.32.2), they do not show up on 2.6.30.x kernels. Dovecot versions involved were/are 1.2.x, I'm currently at 1.2.9. My system is running Slackware 13.0, but this also happened with 12.2. ------------[ cut here ]------------ WARNING: at fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x2a/0x4b() Hardware name: To Be Filled By O.E.M. inotify closing but id=0 for entry=f61e3334 in group=f254ce00 still in idr. Probably leaking memory Modules linked in: tcp_diag inet_diag autofs4 nfsd lockd nfs_acl sunrpc exportfs ipv6 w83627hf hwmon_vid hwmon lp fuse parport_pc 8250_pnp rtc_cmos 8250 parport rtc_core serial_core rtc_lib ohci_hcd button thermal processor evdev e1000 psmouse serio_raw i2c_i801 ide_cd_mod sg i2c_core cdrom ehci_hcd Pid: 10837, comm: imap Not tainted 2.6.32.2 #1 Call Trace: [<c1024368>] ? warn_slowpath_common+0x5e/0x8a [<c10243c6>] ? warn_slowpath_fmt+0x26/0x2a [<c10953a0>] ? idr_callback+0x2a/0x4b [<c10ed1c5>] ? idr_for_each+0x5a/0x91 [<c1095376>] ? idr_callback+0x0/0x4b [<c1095367>] ? inotify_free_group_priv+0x12/0x21 [<c1093c81>] ? fsnotify_final_destroy_group+0x16/0x1e [<c10954dc>] ? inotify_release+0x16/0x22 [<c1072f76>] ? __fput+0xc0/0x163 [<c1070a90>] ? filp_close+0x4e/0x54 [<c1070afc>] ? sys_close+0x66/0x9c [<c10028b5>] ? syscall_call+0x7/0xb ---[ end trace a2df6cbeb716721c ]--- entry->group=(null) inode=(null) wd=1024 There are no processes other than dovecot's "imap" that are ever causing these warnings. Does this indicate a problem in the kernel or rather in dovecot? The system appears to run fine except for the warnings, no actual crashes, asserts, core dumps or similar in any of dovecot's components. Mandatory 'dovecot -n' output: [root@airframe]:~# dovecot -n # 1.2.9: /usr/local/etc/dovecot.conf # OS: Linux 2.6.32.2 i686 Slackware 13.0.0.0.0 login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_max_userip_connections: 20 verbose_proctitle: yes mail_location: maildir:~/Maildir:INBOX=~/Maildir/.INBOX fsync_disable: yes mail_process_size: 2048 mail_plugins: expire fts fts_squat auth default: mechanisms: plain digest-md5 cram-md5 passdb: driver: passwd-file args: /usr/local/etc/dovecot-passwd userdb: driver: passwd socket: type: listen master: path: /usr/local/var/run/dovecot/auth-master mode: 384 plugin: expire: Trash 7 Junk 1 expire_dict: proxy::expire fts: squat fts_squat: partial=4 full=6 dict: expire: mysql:/usr/local/etc/dovecot-dict-sql-expire.conf [root@airframe]:~# Thanks & A Happy 2010, Thomas

3 6

[Dovecot] imap default separator ignored?
by Harald Dunkel 03 Jan '10

03 Jan '10

Hi folks, I have configured the imap folder separator to '/' (see below). AFAIU the separator character does not affect the internal folder representation managed by Dovecot, but just the communication between client and imap server. Question is: What is supposed to happen if I try to create a folder named "a.b" in this configuration? Since '.' is not a separator character anymore, and since the client doesn't know anything about the internals of Dovecot, I do not see why Dovecot complains about an invalid character? Shouldn't it hide its internal Maildir structure? Regards Harri ====================================================================== # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32.2 x86_64 Debian squeeze/sid log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s managesieve 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 login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_privileged_group: mail mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve 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 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve namespace: type: private separator: / location: maildir:~/Maildir inbox: yes list: yes subscriptions: yes auth default: passdb: driver: pam userdb: driver: passwd

3 2

[Dovecot] Problems getting the antispam-plugin to work
by Malte Schirmacher 03 Jan '10

03 Jan '10

Hi List, i'm running the current debian lenny dovecot-version (dpkg says it's 1.0.15-2.3+lenny1) and i'm trying to get the antispam-plugin ('1.2+20090702-1~bpo50+3') to work. Unfortunately dovecot always says "antispam plugin not configured" moving spam into the spam-folder. My config: protocol imap { mail_plugins = antispam } plugin { antispam_signature = X-DSPAM-Signature antispam_signature_missing = error antispam_trash = Trash antispam_spam = Spam antispam_dspam_binary = /usr/bin/dspam antispam_dspam_args = --deliver=;--user;%u } Thanks in advance Malte Schirmacher

2 2

[Dovecot] What auth ?
by Spyros Tsiolis 03 Jan '10

03 Jan '10

Hello people, First of all a Happy New Year and best wishes to you all. I've managed to setup dovecot v1.2.9 on a CentOS 5.4 system and I am now, trying to make it auth. I would prefer virtual users and only want to make the IMAP/ IMAPS part work. I don't need POP3 or anything else. The rest will be handled by another SMTP/POP3 application. Now, I almost managed to make dovecot auth a virtual user with his password. However, when it seems it has passed the auth stage (either via IMAP _or_ IMAPS), the command line kicks me out. Here's roughly what I did : 1. Created /etc/dovecot/users and /etc/dovecot/passwd 2. filled in a couple of usernames/passwords encrypted in MD5 format 3. Ran dovecot from command line (service dovecot start [after I created the service ofcourse]) 4. telneted to localhost via port 143 or 993 (with the help of openssl: "openssl s_client -connect the.system.name:993") 5. typed : . login username@fqdn <password> Something worth noticing for step "5". If I do this logging-in with the "user@fqdn" format, the systems kicks me out. I, then, check the latest on "/var/log/dovecot/errors" to find that the system does not complain about the auth. If I do the same logging-in but instead use "user@localhost" (and not the fqdn), the system fails the authentication stage and does _not_ drop me into the shell. Go figure !! Anyway. My question, in essence, is this; Which type of auth should I use ? The manuals (that i've been sinking my head for the last couple of weeks) suggest I should use PAM. PAM, I cannot understand. At the moment, I _think_ I am using MD5. Any pointers here ? I've been reading the /doc/wiki directory for quite some time until it made no sense to me anymore (too much info makes me loose perspective). Any help would be greatly appreciated. TIA, spyros

2 4

[Dovecot] disable lazy_expunge for some mailboxes?
by Frank Cusack 03 Jan '10

03 Jan '10

How to disable lazy_expunge for certain mailboxes? My problem is I have a public namespace, whose mail is on a different filesystem than user mails. Some users are allowed to expunge on this shared mailbox, but lazy_expunge is stopping that from working since the mail has to cross a filesystem boundary to make it into the lazy_expunge namespace (location is under the user's home directory). As a workaround can I run a daily cron job to remove messages with the \Deleted flag on them? If so how do I find them? thanks -frank

2 3