- dovecot - dovecot.org

[Dovecot] Phantom INBOX in 1.2. Is there a stable .deb of 2.0?
by ian+dovecot＠comtek.co.uk 10 Dec '10

10 Dec '10

Hi, We've been running 1.2 Dovecot for a while and are happy with it. In trying to migrate from symlinks to shared folders I see a similar problem to that shown at http://www.mail-archive.com/dovecot@dovecot.org/msg32083.html . For example: . lsub "" "*" * LSUB () "." "Users..INBOX" The advice given in the thread is to upgrade to 2.0. We currently use Debian's 1.2 package and I'm reluctant to move since I can't find a stable 2.0 .deb (http://wiki2.dovecot.org/PrebuiltBinaries only has repository heads of 2.0). Building from source is an option but I'd really prefer to be using a package. Can anybody advise on an appropriate way to go? Like the original poster I am seeing INBOX under the shared namespace when I try to share. I'm also getting an empty /var/mail/virtual/users/Maildir created (maildir:/var/mail/virtual/users/%n/Maildir/). We formerly had an INBOX prefix namespace from a Courier migration too, but it has been deleted (to no avail). Shared folders do work, though. It just requires 'anyone l' in /etc/dovecot/dovecot-acls/.DEFAULT (though I'd really rather not do this!). Thanks for any help, Ian ######## mail_location = maildir:/var/mail/virtual/users/%n/Maildir/ namespace private { separator = . prefix = inbox = yes } namespace shared { separator = . prefix = Users.%%n. location = maildir:/var/mail/virtual/users/%%n/Maildir/:INDEX=~/shared/%%u subscriptions = no list = children } namespace public { separator = . prefix = Shared. location = maildir:/var/mail/virtual/public:INDEX=~/public subscriptions = no } auth default { mechanisms = plain passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } passdb ldap { args = /etc/dovecot/dovecot-ldap-master.conf master=yes } userdb passwd { } userdb ldap { args = /etc/dovecot/dovecot-ldap-userdb.conf } userdb ldap { args = /etc/dovecot/dovecot-shared-ldap.conf } } plugin { acl = vfile:/etc/dovecot/dovecot-acls:cache_secs=3 acl_shared_dict = file:/var/mail/virtual/shared-mailboxes.db }

1 0

[Dovecot] Released Pigeonhole v0.2.2 for Dovecot v2.0.8
by Stephan Bosch 10 Dec '10

10 Dec '10

Hello Dovecot users, The new Dovecot v2.0.8 release has a few changes that prompted changes in Pigeonhole as well. This means that a new release of Pigeonhole is also necessary, because otherwise things will not compile anymore. Apart from a few rather minor bugfixes, some of which originate in Dovecot, one TODO item has finally been resolved: the reject action uses the LDA mail reject API, meaning that the associated LDA settings now also work for Pigeonhole, as would be expected. Changelog v0.2.2: * LDA Sieve plugin: started using Dovecot LDA reject API for the reject extension. This means that the LDA reject_reason and reject_subject settings now also work for Pigeonhole's LDA Sieve plugin. * Did some work on the new sieve-filter tool. It is mostly functional, but it is not finished yet. * Dovecot change: services' default vsz_limits weren't being enforced correctly in earlier v2.0 releases. Now that they are enforced, you might notice that the default limits are too low and you need to increase them. This problem will show up in logs as "out of memory" errors. See default_vsz_limit and service { vsz_limit } settings. - Imap4flags: fixed segfault bug occurring in multiscript context. - Added version checking to the ManageSieve settings plugin. This plugin was forgotten when the LDA plugin was updated with this change in the previous release. - LDA Sieve plugin: fixed memory leak at deinitialization. The release is available as follows: http://www.rename-it.nl/dovecot/2.0/dovecot-2.0-pigeonhole-0.2.2.tar.gz http://www.rename-it.nl/dovecot/2.0/dovecot-2.0-pigeonhole-0.2.2.tar.gz.sig Refer to http://pigeonhole.dovecot.org and the Dovecot v2.0 wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

2 2

[Dovecot] Dovecot as IMAP proxy to Exchange
by Hugo Monteiro 09 Dec '10

09 Dec '10

Hello list, I'm looking into the possibility to setup dovecot to act as an IMAP proxy to an Exchange server. Things i know beforehand: - I will not be able to use the ldap (Active Directory) user DN for auth binds (but i discovered that i could could use the user userPrincipalName attribute as bind DN. I tested it using ldapsearch and it worked fine.) - I will not be able to perform any unbinded searches. - The Exchange server is unique, so i can setup a static proxy route to the server. Given the above, i'd like to post some questions: 1 - Will i be able to use auth_bind = yes given the restrictions? My first guess is that this might work if i use something like "auth_bind_userdn = %u(a)example.org" 2 - Will i be able to specify a static route to the exchange server, not having to rely on that information from the AD itself? Another thing i'd like to know is if NTLM auth can be used while dovecot acts only as proxy. Thanks in advance, Hugo Monteiro. -- fct.unl.pt:~# cat .signature Hugo Monteiro Email : hugo.monteiro(a)fct.unl.pt Telefone : +351 212948300 Ext.15307 Web : http://hmonteiro.net Divisão de Informática Faculdade de Ciências e Tecnologia da Universidade Nova de Lisboa Quinta da Torre 2829-516 Caparica Portugal Telefone: +351 212948596 Fax: +351 212948548 www.fct.unl.pt apoio(a)fct.unl.pt fct.unl.pt:~# _

2 1

[Dovecot] Dovecot 1.2/2.0 coexistence guide?
by Tom Talpey 09 Dec '10

09 Dec '10

I am running Dovecot 1.2.16 and considering moving up to 2.0.8. I have found <http://wiki2.dovecot.org/Upgrading/2.0> but there's not a lot about deploying a 2.0 server alongside an existing 1.2. Any hints on a seamless approach to this, especially one that might allow me to upgrade individual users in place, without moving their maildirs into a new tree and still avoid issues with 1.2/2.0 sharing access?

4 11

[Dovecot] sieve plugin does not autocreate folder
by JM 09 Dec '10

09 Dec '10

Sieve plugin does not autocreate folder, defined in sieve filter /etc/dovecot/sieve/default.sieve require ["fileinto"]; # rule:[off] if anyof (header :contains "To" "off(a)***.com", header :contains "Cc" "off(a)****.com") { fileinto "INBOX.off"; stop; } >sievec /etc/dovecot/sieve/default.sieve sievec(root): Debug: Loading modules from directory: /usr/lib64/dovecot sievec(root): Debug: Module loaded: /usr/lib64/dovecot/lib15_notify_plugin.so sievec(root): Debug: Module loaded: /usr/lib64/dovecot/lib20_expire_plugin.so sievec(root): Debug: Effective uid=1030, gid=1030, home=/root sievec(root): Debug: maildir++: root=/root, index=, control=, inbox=/root > mail -f test(a)test.org to off(a)****.com > cat /var/log/dovecot.log : script binary /etc/dovecot/sieve/default.svbin successfully loaded : binary save: not saving binary /etc/dovecot/sieve/default.svbin, because it is already stored : executing script from /etc/dovecot/sieve/default.svbin Namepace : Permission lookup failed from /var/spool/mail/virtual/****.com/****(a)*****.com/.INBOX.off Namepace : Using permissions from /var/spool/mail/virtual/****.com/*****@*****: mode=0700 gid=-1 Namepace : Permission lookup failed from /var/spool/mail/virtual/*****.com/*****(a)****.com/.INBOX.off Namepace : Using permissions from /var/spool/mail/virtual/****.com/****(a)****.com: mode=0700 gid=-1 : msgid=<56918ca75c35458412116ec36d8e7c46(a)*****.com>: failed to store into mailbox 'INBOX.off': Mailbox doesn't exist: INBOX.off Error: sieve: execution of script /etc/dovecot/sieve/default.sieve failed, but implicit keep was successful Info: sieve: msgid=<56918ca75c35458412116ec36d8e7c46(a)*****.com>: stored mail into mailbox 'INBOX' OS - Linux gentoo 2.6.36 x64 dovecot version 2.0.8 dovecot.conf base_dir = /var/run/dovecot/ default_vsz_limit = 1 G mail_debug = yes mail_gid = vmail mail_location = maildir:%h mail_privileged_group = vmail mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation plugin { sieve = ~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/default.sieve sieve_dir = ~/sieve } protocols = imap pop3 sieve service auth { unix_listener auth-master { mode = 0600 user = vmail } } service managesieve-login { vsz_limit = 1 M } protocol lda { auth_socket_path = /var/run/dovecot/auth-master log_path = /var/log/dovecot.log mail_plugins = sieve quota }

3 4

[Dovecot] mutt freezes
by Manoel Prazeres 09 Dec '10

09 Dec '10

Hi Sometimes mutt freezes saying "Closing connection to imap.impa.br...". Any clue? Thanks Manoel === My configuration: User-Agent: Mutt/1.5.21 (2010-09-15) # dovecot -n # 2.0.8: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-194.26.1.el5xen x86_64 CentOS release 5.5 (Final) default_client_limit = 1027 default_process_limit = 512 first_valid_gid = 1000 first_valid_uid = 1001 log_path = /var/log/imapd/imapd.log log_timestamp = "%b %e %H:%M:%S markov " login_log_format_elements = user=<%u> method=%m pid=%p rip=%r lip=%l %c mail_location = mbox:%h/mail:INBOX=%h/mbox:INDEX=/var/local/imapd.indexes/%u mail_log_prefix = "%Us(%u): pid=%p, rip=%r, lip=%l, " mbox_write_locks = fcntl passdb { args = /etc/dovecot/deny-users deny = yes driver = passwd-file } passdb { driver = pam } protocols = imap service imap-login { process_min_avail = 32 } service imap { process_limit = 512 } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } protocol imap { mail_max_userip_connections = 5 }

2 2

[Dovecot] dovecot-lda segfault
by Micha Krause 09 Dec '10

09 Dec '10

Hello, dovecot-lda crashes with a segfault, if I run it as a user who has no mailbox, and no permission to create one. stat("/var/mail/mailboxes/users", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 getuid() = 21189 geteuid() = 21189 access("/var/mail/mailboxes/users", X_OK) = 0 getuid() = 21189 geteuid() = 21189 access("/var/mail/mailboxes/users", W_OK) = -1 EACCES (Permission denied) geteuid() = 21189 getegid() = 21189 --- SIGSEGV (Segmentation fault) @ 0 (0) --- +++ killed by SIGSEGV +++ dovecot --version 2.0.8 (f9d34d929c3f) Micha Krause

3 3

[Dovecot] mail.err
by Paul Cartwright 08 Dec '10

08 Dec '10

I keep getting this error, and I have no clue where it comes from. I have no localhost in my fetchmailrc file, all I have in main.cf is: mydestination = paulandcilla.homelinux.org, localhost here is some of the entries in /var/log/mail.err: Dec 7 16:00:38 paulandcilla fetchmail[16761]: connection to localhost:smtp [::1/25] failed: Connection refused. Dec 7 16:00:40 paulandcilla fetchmail[16761]: connection to localhost:smtp [::1/25] failed: Connection refused. Dec 7 16:00:43 paulandcilla fetchmail[16761]: connection to localhost:smtp [::1/25] failed: Connection refused. Dec 7 16:10:50 paulandcilla fetchmail[16761]: connection to localhost:smtp [::1/25] failed: Connection refused. Dec 7 16:10:56 paulandcilla fetchmail[16761]: connection to localhost:smtp [::1/25] failed: Connection refused. Dec 7 16:21:05 paulandcilla fetchmail[16761]: connection to localhost:smtp [::1/25] failed: Connection refused. Dec 7 16:21:07 paulandcilla fetchmail[16761]: connection to localhost:smtp [::1/25] failed: Connection refused. Dec 7 16:21:08 paulandcilla fetchmail[16761]: connection to localhost:smtp [::1/25] failed: Connection refused. Dec 7 16:31:18 paulandcilla fetchmail[16761]: connection to localhost:smtp [::1/25] failed: Connection refused. Dec 7 16:31:19 paulandcilla fetchmail[16761]: connection to localhost:smtp [::1/25] failed: Connection refused. Dec 7 16:41:25 paulandcilla fetchmail[16761]: connection to localhost:smtp [::1/25] failed: Connection refused. Dec 7 16:41:26 paulandcilla fetchmail[16761]: connection to localhost:smtp [::1/25] failed: Connection refused. Dec 7 16:41:27 paulandcilla fetchmail[16761]: connection to localhost:smtp [::1/25] failed: Connection refused. all of the mail SENDING on this box comes out of either kmail or thunderbird via my domain host, secure login. -- Paul Cartwright Registered Linux user # 367800

4 19

[Dovecot] passdb pam and userdb passwd "Authentication failure" errors
by Mark Alan 08 Dec '10

08 Dec '10

While using Ubuntu 10.10 + Dovecot 1.2.12 + Postfix 2.7.1-1: To enable virtual accounts, I am using the following /etc/dovecot/auth.d/virtualsomename.auth file: passdb passwd-file { args = /etc/dovecot/passwd } userdb static { args = uid=vmail gid=vmail home=/home/vmail/%u } EOT cat /etc/dovecot/passwd looks like this: test:{PLAIN}pass bill:{PLAIN}secret timo@example.com:{PLAIN}hello123 dave@example.com:{PLAIN}world234 Issuing a 'sudo dovecot -n' shows: .../... auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: pam passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd userdb: driver: static args: uid=vmail gid=vmail home=/home/vmail/%u .../... and while trying to connect to Dovecot as dave(a)example.com the log shows: 2010-12-04 18:15:58 auth(default): Info: new auth connection: pid=15334 2010-12-04 18:15:58 auth(default): Info: client in: AUTH 1 PLAIN service=smtp nologin lip=127.0.1.1 rip=127.0.1.1 resp=AGRhdmVAZXhhbXBsZS5jb20Ad29ybGQyMzQ= 2010-12-04 18:15:58 auth-worker(default): Info: pam(dave(a)example.com,127.0.1.1): lookup service=dovecot 2010-12-04 18:15:58 auth-worker(default): Info: pam(dave(a)example.com,127.0.1.1): #1/1 style=1 msg=Password: 2010-12-04 18:16:00 auth-worker(default): Info: pam(dave(a)example.com,127.0.1.1): pam_authenticate() failed: Authentication failure (password mismatch?) (given password: world234) 2010-12-04 18:16:00 auth(default): Info: passwd-file(dave(a)example.com,127.0.1.1): lookup: user=dave(a)example.com file=/etc/dovecot/passwd 2010-12-04 18:16:00 auth(default): Info: client out: OK 1 user=dave(a)example.com I have 2 questions: QUESTION 1: To avoid those Authentication failure errors should I also comment out the passdb pam {...} and userdb passwd {...} blocks in the main /etc/dovecot/dovecot.conf? I was thinking in something like: sudo sed -i '/passdb pam {/,/}/s/^/#/' /etc/dovecot/dovecot.conf sudo sed -i '/userdb passwd {/,/}/s/^/#/' /etc/dovecot/dovecot.conf QUESTION 2: the final email arrives with an email header that includes: Received: from desk.example.com (unknown [127.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.example.com (Postfix) with ESMTPSA id F24707FE6D for <example(a)example.com>; Sat, 4 Dec 2010 18:16:00 +0000 (WET) Does this mean that I have SSL/TLS properly configured? The "No client certificate requested" is supposed to be there? Thank you. M.

3 4

[Dovecot] How to handle "Waiting for authentication process..."
by A.L.E.C 08 Dec '10

08 Dec '10

Sometimes, when dovecot authentication processes are busy, dovecot write reply "Waiting for authentication process to respond.." to client. Roundcube webmail do not understand it and invalidate user session. My question is what is a good practise to handle this situation by client software? One Roundcube user proposes to detect such response then wait a moment and try again. Is there any standard for this? How long should we wait? More info here: http://trac.roundcube.net/ticket/1487450 -- Aleksander 'A.L.E.C' Machniak LAN Management System Developer [http://lms.org.pl] Roundcube Webmail Developer [http://roundcube.net] --------------------------------------------------- PGP: 19359DC1 @@ GG: 2275252 @@ WWW: http://alec.pl

2 2