- dovecot - dovecot.org

[Dovecot] Quota warning generated when crossing on both sides
by Harm van Tilborg 13 Dec '10

13 Dec '10

Hello everyone, I'm experimenting with the quota warning plugin. I have the following setting in Dovecot's general config: plugin { quota_warning = storage=75%% /var/www/contrib/doquotawarning.py 75 quota_warning2 = storage=90%% /var/www/contrib/doquotawarning.py 90 } The doquotawarning.py script is working okay -- meaning that the user gets a warning. My SQL backend uses the following query: user_query = \ SELECT m.maildir AS home, 1001 AS uid, 1001 AS gid, \ CONCAT('*:bytes=', m.quota, 'M') AS quota_rule, \ 'Trash:ignore' AS quota_rule2 \ FROM mailbox m \ INNER JOIN domain d \ ON d.id = m.domainid \ WHERE d.domain = '%d' \ AND m.user = '%n' Where m.quota is the user's personal quota (in MB). As you can see, we ignore the 'Trash' box, when considering the usage data. We are using the dict quota backend. Now this is what happens. Assume we have 'user(a)example.org', that has a quota of 10MB and he currently has 5MB in use. Now someone sends a 3MB email towards 'user(a)example.org'. Dovecot does indeed generate the warning message (75%), that arrives correctly 'together' with the 3MB email. Now the user moves the 3MB email to trash. This goes well, however: Dovecot generates the 75% warning message again. Which is not necessary: the user was cleaning his mailbox, i.e. usage is 5MB again. I have the feeling Dovecot is generating the warning event twice. When getting from e.g. 50% to 79% and when the usage is lowered from 87% to 70%. I have the feeling this is either not the correct behavior, or I'm misinformed. When looking at the source, this shouldn't be happening: if ((bytes_before < (uint64_t)warnings[i].rule.bytes_limit && bytes_current >= (uint64_t)warnings[i].rule.bytes_limit) || (count_before < (uint64_t)warnings[i].rule.count_limit && count_current >= (uint64_t)warnings[i].rule.count_limit)) { quota_warning_execute(root, warnings[i].command); break; } We're using Dovecot 1.2.9 (Ubuntu's 10.04 LTS version). -- Kind regards, Harm van Tilborg

2 1

[Dovecot] Crash in 2.0.8 dovecot/imap - information capture
by Tom Talpey 13 Dec '10

13 Dec '10

My dovecot logs revealed a crash in the dovecot/imap process a few days ago. It appears to have dereferenced 0x00000004 in the storage shared lib. Unfortunately, I didn't get a core and I'm not sure how to reproduce it. Dovecot 2.0.8 on linux32. Two questions: 1) How can I be sure I get a core next time? I think it's because I run dovecot/imap under a mail uid and didn't have write permission to the cwd. Any way to verify that was it, and be sure it works? 2) What other settings would provide more info if it happens again? Thanks! dovecot.log excerpt: Dec 10 08:43:53 master: Error: service(imap): child 30862 killed with signal 11 (core dumps disabled) Dec 10 08:43:53 imap-login: Info: Login: user=<xx(a)yy.com>, method=PLAIN, rip=169.254.100.10, lip=169.254.100.100, mpid=2243 kernel dmesg: imap[30862]: segfault at 4 ip b772ecd2 sp bfc90f90 error 4 in libdovecot-storage.so.0.0.0[b76e9000+b8000] [~] # dovecot -n # 2.0.8: /etc/dovecot/dovecot.conf # OS: Linux 2.6.33.2 i686 ext4 (not sure of exact config at time of crash, will capture next)

2 1

[Dovecot] Right auth scheme for MS clients?
by Agim Cami 13 Dec '10

13 Dec '10

What will be the right authentication scheme for a mail system with Microsoft Outlook as client and shadow passwords for Linux system users?

2 1

[Dovecot] director errors
by Cor Bosman 13 Dec '10

13 Dec '10

Hi Timo, im getting some director errors. Dec 13 10:11:25 imapdirector1 dovecot: director: Error: User hash 3608614717 is being redirected to two hosts: 194.109.26.171 and 194.109.26.141 Dec 13 10:11:25 imapdirector1 dovecot: director: Error: User hash 755231546 is being redirected to two hosts: 194.109.26.132 and 194.109.26.154 Dec 13 10:11:25 imapdirector1 dovecot: director: Error: User hash 2468924024 is being redirected to two hosts: 194.109.26.135 and 194.109.26.159 Dec 13 10:11:25 imapdirector1 dovecot: director: Error: User hash 3275820100 is being redirected to two hosts: 194.109.26.134 and 194.109.26.160 Dec 13 10:11:25 imapdirector1 dovecot: director: Error: User hash 1674197395 is being redirected to two hosts: 194.109.26.137 and 194.109.26.159 Dec 13 10:11:25 imapdirector1 dovecot: director: Error: User hash 1753370669 is being redirected to two hosts: 194.109.26.134 and 194.109.26.171 Dec 13 10:11:25 imapdirector1 dovecot: director: Error: User hash 3760447994 is being redirected to two hosts: 194.109.26.131 and 194.109.26.141 Dec 13 10:11:25 imapdirector1 dovecot: director: Error: User hash 3687955574 is being redirected to two hosts: 194.109.26.171 and 194.109.26.158 Dec 13 10:11:26 imapdirector1 dovecot: director: Error: director(194.109.26.174:444/right): Handshaking timed out Dec 13 10:11:26 imapdirector1 dovecot: director: Error: Director 194.109.26.174:444/right disconnected Ive got 37 director_mail_servers and 2 director_servers. Cor

1 0

[Dovecot] Новое сообщение
by Vovan 13 Dec '10

13 Dec '10

http://samec.org.ua/

1 0

[Dovecot] director_user_expire
by Cor Bosman 11 Dec '10

11 Dec '10

Would it be ok to set director_user_expire to a very high value? Say 1 day? This would pretty much lock a user into a specific server right? What if I set it to 1 year? :) What happens when the server a user is locked into disappears (i remove it from the pool). Then a day later, I add the server again. Is the user now locked to the new server, or will he revert back to the old server? Cor

1 0

[Dovecot] imap_logout_format don't understand %r variable
by Nikita Koshikov 10 Dec '10

10 Dec '10

Hello list, Dovecot version 1.2.16. In protocol imap section I have imap_logout_format = ip=%r bytes=%i/%o But when user disconnecting, to log file dovecot write: IMAP(user@domain): Info: Disconnected: Logged out ip= bytes=954/8644 Is this suppose to work ?

2 2

[Dovecot] Delay email!
by Henrique Fernandes 10 Dec '10

10 Dec '10

I am using postfix + dovecot 2.0.6 + mailman And others 2 serves with only postfix and dovecot writing at same storage with OCFS2. We are having problens with IOwait, and still trying to figure out why that is happen! But, problem becomes much worse when some emails are used in mailman, when it happens all 3 serves became really slow. iowait goes to 80. Does anyone have an idea how to slow down the dovecot lda ? I want it to nit to iwrite so much email, at least take a small break between each mail!! Any ideias? Thanks! []'sf.rique

2 4

Re: [Dovecot] IMAP aggregation and MUPDATE protocolo
by Timo Sirainen 10 Dec '10

10 Dec '10

(Second time already within a few days when I accidentally hit reply rather than reply-to-all and then wonder why the message isn't showing up.) On 24.11.2010, at 14.16, Ernesto Revilla Derksen wrote: > We're trying to find a solutions for aggregating data from several > backends which are: > * normal mail IMAP > * repositories like Alfresco which offer an IMAP view for repository documents I'm planning on implementing "IMAP client" backend for lib-storage, which means you could create namespaces that are proxied to remote IMAP server. Or even make Dovecot act as a caching IMAP proxy for your real IMAP server. > * issue trackers (issue + attachmentes + timeline) I guess it could be possible to implement lib-storage backend for these too. :) Or maybe create some new simpler protocol that you can easily implement for them, and then create a lib-storage backend for that.

4 6

[Dovecot] Execute Script on LMTP Deliver?
by Edward Carraro 10 Dec '10

10 Dec '10

Is it possible to have dovecot 2.0.8 using LMTP run a shell script each time it delivers a message to a users mailbox? I see there's an "execute = script /path/to/script" but when i added it to lmtp service in 10-master.conf, it didnt do anything and stopped delivering mail altogether service lmtp { executable = script /usr/local/bin/test.sh u% unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix user = postfix } inet_listener lmtp { port = 24 } } $ ls -lh | grep test -rwxrwxrwx 1 root staff 270 2010-12-09 18:05 test.sh $ cat test.sh #!/bin/sh USER=$1 echo $USER > /tmp/newfile basically when a message arrives, it will execute a shellscript which will notify another service that mail has arrived in their inbox

2 2

[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

[Dovecot] local seen flags with shared mailboxes
by Tim Mauerbach 08 Dec '10

08 Dec '10

Hello all, after recent upgrade from 2.0.5 to 2.0.8 it seems that local seen flags for mails reside in shared mailboxes doesn´t work anymore. Before the upgrade I had read mails with account #1. Account #2 (who has access via acl) saw the mails still as unread. Now, no matter who read the mails, the other account see the same flags, immediately. I read the related wiki pages again and tried to find any configuration error, unfortunately without much success. I´ve attached output from "doveconf -n" and a debug logfile. Thanks a lot! Tim

2 2

Re: [Dovecot] mail.err
by Karsten Bräckelmann 08 Dec '10

08 Dec '10

Please *do* keep the thread on the list, by replying to the list only. On Tue, 2010-12-07 at 18:07 -0500, Paul Cartwright wrote: > On 12/07/2010 05:25 PM, Karsten Bräckelmann wrote: > > Even though this *really* is not related to dovecot at all, while we're > > here, I might as well try to help nonetheless -- failing with an IPv6 > > address does look familiar. I don't recall the log messages, since I > > mostly debugged with fetchmail directly. > > I don't think I am using IPv6, actually I KNOW I'm not using it, I'm > pretty sure I turned off that functionality.. I don't think my router > supports it.. > I KNOW I didn't try to add that functionality to either fetchmail, > Postfix or Divecot! As I mentioned in another post, your log message clearly shows the IPv6 address is being used. And yes, your host obviously is capable of that. You don't need to specifically enable it with fetchmail. It will under certain circumstances default to IPv6, which in your case happened. As also mentioned, your postfix seems to not bind to the IPv6 address by default, though, or it has deliberately been disabled. Moreover, your router is not even in the picture here -- just like dovecot, FWIW. Fetchmail fetches the mail from a remote server, and tries to deliver it locally. That local delivery step is generating the log messages. A mail, sent from and to your box. Long after the data stream passed your router... [ long snip, including your fetchmailrc general settings ] > I will add what you have there, and see what happens, thanks! -- char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4"; main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1: (c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

1 0

[Dovecot] IMAP Timeout Leak
by qmail＠top-consulting.net 08 Dec '10

08 Dec '10

My Dovecot config is as follows: # 1.2.14: /usr/local/etc/dovecot.conf # OS: FreeBSD 6.3-RELEASE i386 protocols: imap pop3 imaps pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_ca_file: /usr/local/certs/gd_bundle.crt ssl_cert_file: /usr/local/certs/imap.crt ssl_key_file: /usr/local/certs/rsa.imap.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting: MAIL ready. login_processes_count: 50 login_max_processes_count: 500 max_mail_processes: 798 mail_max_userip_connections(default): 100 mail_max_userip_connections(imap): 100 mail_max_userip_connections(pop3): 10 verbose_proctitle: yes first_valid_uid: 89 first_valid_gid: 89 mail_privileged_group: mail mail_uid: 89 mail_gid: 89 mail_location: maildir:~/Maildir mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes lock_method: dotlock mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota fts fts_solr antispam virtual acl imap_acl mail_plugins(imap): quota imap_quota fts fts_solr antispam virtual acl imap_acl mail_plugins(pop3): virtual mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh 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 namespace: type: private separator: . inbox: yes list: yes subscriptions: yes namespace: type: private separator: . prefix: INBOX. hidden: yes list: no subscriptions: yes namespace: type: private separator: . prefix: Labels. location: virtual:~/Maildir/Labels:INDEX=MEMORY list: yes subscriptions: yes namespace: type: shared separator: . prefix: shared.%%n. location: maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u list: children lda: sendmail_path: /usr/sbin/sendmail auth default: mechanisms: plain login digest-md5 cram-md5 username_format: %Lu verbose: yes passdb: driver: vpopmail args: webmail=192.168.1.4 userdb: driver: vpopmail args: quota_template=quota_rule=*:backend=%q socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vpopmail plugin: fts: solr fts_solr: break-imap-search url=http://192.168.1.4:8983/solr/ quota: maildir quota_rule: ?:storage=0 antispam_signature: X-DSPAM-Signature antispam_trash: trash;Trash;Deleted Items antispam_spam: Spam antispam_dspam_binary: /usr/local/bin/dspam antispam_dspam_args: --client;--user;vpopmail acl: vfile acl_shared_dict: proxy::acl dict: acl: mysql:/usr/local/etc/dovecot-dict-sql.conf and I see the following error in the logs: Timeout leak: 0x80ff950 Running it through gdb, I get this: (gdb) x 0x80ff950 0x80ff950 <client_dict_timeout>: 0x53e58955 Is it a problem with the ACL plugin ?

2 1

[Dovecot] imap/pop proxy and filter
by Mike Korizek 07 Dec '10

07 Dec '10

Hi I use dovecot as imap/pop proxy. Is it possible to filter the messages before they get delivered to the client? Thanks for any hint how to achieve this. Mike

2 3

[Dovecot] proxy and gpg processing
by Mike 07 Dec '10

07 Dec '10

Hi I have dovecot running as pure proxy for accessing imap and pop mailboxes on other servers. How can I do the following scenario: When a client user reads a gpg signed or gpg encrypted email through the proxy, can I verify/decrypt the email before it gets delivered to the client user? Ideally I would like to write a perl program which processes the email within the proxy before it gets delivered to the user. With Sieve I can not do this, is there another way to achieve this? Thanks for any hint. Mike

1 0