December 2010 - dovecot

[Dovecot] Pigeonhole 0.2.2 - managesieve supports virtual namespaces?
by Tom Talpey 13 Dec '10

13 Dec '10

I got around to trying the 0.2.2 managesieve listener and it's not working for me. As soon as the client authenticates, the connection is closed and the following is logged on the server: > Dec 13 11:48:30 managesieve(xx(a)yy.com): Error: user xx(a)yy.com: Initialization failed: Namespace 'Mobile/': Unknown mail storage driver virtual > Dec 13 11:48:30 managesieve(xx(a)yy.com): Error: Invalid user settings. Refer to server log for more information. I do have such a virtual namespace defined in dovecot.conf, obviously, and it works fine with dovecot 2.0.8. Additionally, the sieve plugin is working fine for lda, dovecot's deliver is executing it perfectly. Do I need to add a setting or plugin to "protocol managesieve" for this? Combed the wiki to no avail.

2 2

[Dovecot] extra fields with "passwd" userdb
by Patrick McLean 13 Dec '10

13 Dec '10

Hi, I am planning a migration of ~600 accounts to mdbox (from maildir) and was hoping to do some initial testing of certain account. I am hoping to use extra fields to migrate certain accounts in advance for testing, and I can't find info on setting up extra fields with the "passwd" backend. Is this possible, or will I have to use another approach?

4 7

[Dovecot] Feature request
by Nikita Koshikov 13 Dec '10

13 Dec '10

Hello Timo, and all. Preface: From time to time we have problems with thunderbird. The problem is that mail client begin to sync users inbox (or other folder) and this process didn't stop. Last time we have this situation - our monitoring system shows unusual amount of imap traffic send to one of local hosts. This host was - terminal server and 20 users worked with their mailboxes that time. But normal 20 imap session can't fork that amount of traffic (5.2Gb). After measuring local thunderbird's cached mailboxes we find out that one user have local INBOX about 19Gb and size is rising. On server side - this mailbox was 89Mb. And after killing thunderbird in logs appear: Dec 10 17:35:53 IMAP(user@domain 192.168.2.92): Info: Disconnected: Logged out bytes=1133593/1175103 Dec 10 17:35:53 IMAP(user@domain 192.168.2.92): Info: Disconnected: Logged out bytes=15964/44364 Dec 10 17:35:53 IMAP(user@domain 192.168.2.92): Info: Disconnected: Logged out bytes=54758/944989 Dec 10 17:35:53 IMAP(user@domain 192.168.2.92): Info: Disconnected: Logged out bytes=6532/43930 Dec 10 17:35:53 IMAP(domain@domain 192.168.2.92): Info: Connection closed bytes=235408/4797272694 As you can see - 4.8Gb of data was send to this client - and who knows - what was that. So we have 5.2Gb send to host with 20 active sessions and 4.8Gb send to one user. Of course lifetime of this connection can be much more than last day, but problem disappeared after killing it. This is not single accident. But this one was hard to find out because of 20-25 users working at the same time from 1 server. So it will be great if dovecot has feature to limit the amount of data send per connection. For example: service imap { bytes_per_connection = 100Mb } And after limit reached - close connection and log warning. This will much simplify fights with sometimes become crazy imap clients. That do you think?

3 7

[Dovecot] limit login concurencly from different ip
by Giovanni Mancuso 13 Dec '10

13 Dec '10

Hi, can i configure dovecot to limit the max number of login concurencly? I read in documentation that there is "mail_max_userip_connections", but in this way i limit the login that come from same ip. If the same user tries to connect from different ip, he succeeds. Can i do it? Thanks

2 3

[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