- 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