- dovecot - dovecot.org

[Dovecot] Per user quotas
by David Travers 18 Oct '12

18 Oct '12

Hi All, I keep going round in circles with this. I have quotas up and running but would like to add a couple of per user exceptions but can't figure out how to do it! I am using Open Xchange community edition on top of dovecot and tha tis showing the 200MB limit, if I change it in the dovecot.conf the change is reflected in open xchange, but can't figure out how to change for 1 user. I believe I need to add to a passwd file, but I have added to that and nothing has changed. # dovecot -n # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686 i686 Debian 6.0.5 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/certs/postfix.pem ssl_key_file: /etc/ssl/private/postfix.key 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 mail_privileged_group: mail mail_location: maildir:~/mail:LAYOUT=fs:INBOX=~/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_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota 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 lda: mail_plugins: quota auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix plugin: quota: maildir:user quota quota_rule: *:storage=200M quota_rule2: Trash:storage=10%% quota_rule2: SPAM:ignore quota_warning: storage=95%% /usr/local/bin/quota-warning.sh 95 quota_warning2: storage=80%% /usr/local/bin/quota-warning.sh 80 quota_exceeded_message: Quota exceeded, Please delete some emails Any help gratefully received Dave _________________________________________ This email has been scanned for malicious content. _________________________________________

3 4

[Dovecot] Dsync clustering
by list＠airstreamcomm.net 18 Oct '12

18 Oct '12

I have not seen mention of using dsync for clustering Dovecot in some time on the mailing list, but I believe Timo was going to write a wiki page when v2.2 became more mature. Does this documentation exist yet, or are there any resources on what dsync replication is capable of at this point (looking on the wiki and google didn't reveal much)? Thank in advance.

2 1

Re: [Dovecot] Disconnected for inactivity time.
by Joseph Tam 18 Oct '12

18 Oct '12

Robert JR writes: > After 10 mins of unactivity of pop3 , dovecot disconnect the user (-ERR > Disconnected for inactivity.) > > What is the option in the config file which control the unactivity > logout time ? becuase i want to decrease the inactivity time > > To 5 mins instead of 10 mins Looks like it's set in the source code pop3-client.c:#define CLIENT_IDLE_TIMEOUT_MSECS (10*60*1000) but the output of # doveconf -a ... service pop3 { ... idle_kill = 0 ... } maybe points to the config that overrides this. Easy enough to test. It's non-RFC compliant as one poster points out, so unless you got a good reason to do this like lots of zombie pop3 processes, leave it alone. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] Dovecot sieve and duplicate email subjects
by Benjamin Thomas 17 Oct '12

17 Oct '12

Hi, I'm running a small email server with the help of iRedMail. I can manage sieve scripts from the Rouncube web interface or manually inside the user's personal sieve folder. I have an email account setup to receive automated tasks. Some of these "alerts" occur too often and they have the same subject line, but different senders. This is the rule I am currently using: ##CODE START## # rule:[AutoAlerts] if anyof ( header :matches "Subject" "AutoAlert Type1*", header :matches "Subject" "AutoAlert Type2*", header :matches "Subject" "AutoAlert Type3*" ) { fileinto "INBOX.AutoAlerts"; stop; } ##CODE END## I was wondering if it's possible to gracefully handle duplicate subjects lines (within a given time frame) with sieve filters ? Ideally, I would like the first email of the day with subject ""AutoAlert Type1..." to get moved to the subfolder given above. Subsequent "duplicate" emails would then go into a "duplicate" subfolder. Is this possible with sieve filters ? I could not find anything striking me as obvious while reading the page http://wiki.dovecot.org/LDA/Sieve. Thanks very much for your input.

2 3

[Dovecot] Disconnected for inactivity time.
by Robert JR 17 Oct '12

17 Oct '12

Hello, After 10 mins of unactivity of pop3 , dovecot disconnect the user (-ERR Disconnected for inactivity.) What is the option in the config file which control the unactivity logout time ? becuase i want to decrease the inactivity time To 5 mins instead of 10 mins Please advise Robert JR

2 1

[Dovecot] dovecot died
by Hendrik 17 Oct '12

17 Oct '12

Hi All I have been trying to get this website running for months now. I get this emails from cpanel and don't know how to fix it. If anyone can help me please contact me at pipefab(a)mweb.co.za. Kind regards Hendrik imap failed @ Fri Oct 12 05:51:18 2012. A restart was attempted automagically. Service Check Method: [check command] Number of Restart Attempts: 1 Cmd Service Check Raw Output: dovecot is not running Startup Log: /etc/init.d/dovecot: line 15: 6043 Alarm clock /usr/sbin/dovecot > /dev/null 2>&1 Syslog Messages: Oct 12 04:01:01 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__lvgws_iymiqndfmflick2pa3yjzc56ukpa2t6x3 yj43fuh...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 04:01:02 scene dovecot: IMAP(__cpanel__service__auth__imap__lvgws_iymiqndfmflick2pa3yjzc56ukpa2t6x3y j43fuhjgeiqomc3dhlkyjwdq): Disconnected: Logged out bytes=11/340 Oct 12 04:06:06 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__jxy1xcsu0koedgkhexhexpu3_idp4ynukxpaou0 jaovpdr...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 04:06:06 scene dovecot: IMAP(__cpanel__service__auth__imap__jxy1xcsu0koedgkhexhexpu3_idp4ynukxpaou0j aovpdrgqjnf0_rxyi0wncetn): Disconnected: Logged out bytes=11/313 Oct 12 04:11:01 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__6oxwycgffp_5xkysaitw4eifev2nffi_dqlhj4z k8h05nx...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 04:11:01 scene dovecot: IMAP(__cpanel__service__auth__imap__6oxwycgffp_5xkysaitw4eifev2nffi_dqlhj4zk 8h05nx2p9n4yfxhrp3a2gjhl): Disconnected: Logged out bytes=11/313 Oct 12 04:16:08 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__7zurxql5qf5whp4rupxen3viduh5kucjqtrzigs c75cnov...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 04:16:09 scene dovecot: IMAP(__cpanel__service__auth__imap__7zurxql5qf5whp4rupxen3viduh5kucjqtrzigsc 75cnovslbll4702ue2veu2n3): Disconnected: Logged out bytes=11/318 Oct 12 04:21:10 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__cq4wbk6o7svgbljnmw1hx2iiaunvzp3w1cywwsf ou8d5ky...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 04:21:11 scene dovecot: IMAP(__cpanel__service__auth__imap__cq4wbk6o7svgbljnmw1hx2iiaunvzp3w1cywwsfo u8d5kysrfeaqvlmjgx6afvnb): Disconnected: Logged out bytes=11/340 Oct 12 04:26:35 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__uhyykmmdnf31il4pn_kfci9y2gw2o9skyz7zuoe oga08za...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 04:26:36 scene dovecot: IMAP(__cpanel__service__auth__imap__uhyykmmdnf31il4pn_kfci9y2gw2o9skyz7zuoeo ga08zaq_nh6yzqsmveqpvnxi): Disconnected: Logged out bytes=11/313 Oct 12 04:31:05 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__hka0onlsdbqugjyirdyygk_d9wtw_xtkl7jgaus tpvzl1q...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 04:31:05 scene dovecot: IMAP(__cpanel__service__auth__imap__hka0onlsdbqugjyirdyygk_d9wtw_xtkl7jgaust pvzl1qjjei5uuoi1c4g8tpea): Disconnected: Logged out bytes=11/313 Oct 12 04:36:02 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__ouonjmdpliwgyj8ij6gucv6y7fxq6ojdk9hsxjj fzonng9...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 04:36:03 scene dovecot: IMAP(__cpanel__service__auth__imap__ouonjmdpliwgyj8ij6gucv6y7fxq6ojdk9hsxjjf zonng9eqrsw5l5hg7xoejer2): Disconnected: Logged out bytes=11/340 Oct 12 04:41:03 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__wpwfzoyvnb2rsz2desu10swelok4cdwrqqw70gw eibvov1...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 04:41:04 scene dovecot: IMAP(__cpanel__service__auth__imap__wpwfzoyvnb2rsz2desu10swelok4cdwrqqw70gwe ibvov1_minfh7j4_4ejaz7v2): Disconnected: Logged out bytes=11/340 Oct 12 04:46:04 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__razxoe9ffiqhzj6rahuftwwqprhj2blovjvsbhd rhafjur...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 04:46:05 scene dovecot: IMAP(__cpanel__service__auth__imap__razxoe9ffiqhzj6rahuftwwqprhj2blovjvsbhdr hafjureydiuxbtbk2jkpkvlo): Disconnected: Logged out bytes=11/340 Oct 12 04:51:06 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__as64dk7mx4gfxupigti8wwrbqpqhetm9zyhzlrq h1iztqo...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 04:51:06 scene dovecot: IMAP(__cpanel__service__auth__imap__as64dk7mx4gfxupigti8wwrbqpqhetm9zyhzlrqh 1iztqosnzfwt28kkzv4riyd9): Disconnected: Logged out bytes=11/340 Oct 12 04:56:07 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__x0do00ujo_2w89kbu0kfk6s8evtdz9u3davldan 2pdmdvg...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 04:56:07 scene dovecot: IMAP(__cpanel__service__auth__imap__x0do00ujo_2w89kbu0kfk6s8evtdz9u3davldan2 pdmdvg6jofzylncdb3ytjaaz): Disconnected: Logged out bytes=11/340 Oct 12 05:01:08 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__lkup_seowtz4xhnmf5fkihlw6hpacvnfyeyzvir quwcv1z...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 05:01:08 scene dovecot: IMAP(__cpanel__service__auth__imap__lkup_seowtz4xhnmf5fkihlw6hpacvnfyeyzvirq uwcv1zhloqt12rqni_o2pqcj): Disconnected: Logged out bytes=11/340 Oct 12 05:06:09 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__yl1ivh4akxdj7vph6nz2w8jdmeuzukqkvezokgr cpi3usb...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 05:06:09 scene dovecot: IMAP(__cpanel__service__auth__imap__yl1ivh4akxdj7vph6nz2w8jdmeuzukqkvezokgrc pi3usbdjkiy2n8zy2bbvhhny): Disconnected: Logged out bytes=11/340 Oct 12 05:11:10 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__z0jltexjylqusc5j7qrtw5t7m_tqzcjyheljxrg 4vew3df...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 05:11:10 scene dovecot: IMAP(__cpanel__service__auth__imap__z0jltexjylqusc5j7qrtw5t7m_tqzcjyheljxrg4 vew3dfbyrglsasuldldaspck): Disconnected: Logged out bytes=11/340 Oct 12 05:16:11 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__0ycn3mqrthjv1aqo7w45zy1ndeodd2xxh92y3v0 e2bwtas...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 05:16:11 scene dovecot: IMAP(__cpanel__service__auth__imap__0ycn3mqrthjv1aqo7w45zy1ndeodd2xxh92y3v0e 2bwtastu0kton3azlhmmuhwi): Disconnected: Logged out bytes=11/340 Oct 12 05:21:12 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__ofmf6ptqgyhrzgrlsx3p33fz52q7j1afid0uszq mf4h8z1...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 05:21:12 scene dovecot: IMAP(__cpanel__service__auth__imap__ofmf6ptqgyhrzgrlsx3p33fz52q7j1afid0uszqm f4h8z1shjl34q9zpid3g4gsp): Disconnected: Logged out bytes=11/340 Oct 12 05:26:13 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__awz7xewlgj6pjfdz1dogl28vm9ld5fqfwviyaog ha3yc0w...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 05:26:13 scene dovecot: IMAP(__cpanel__service__auth__imap__awz7xewlgj6pjfdz1dogl28vm9ld5fqfwviyaogh a3yc0w6t7vvgyf1snz8vechf): Disconnected: Logged out bytes=11/340 Oct 12 05:31:14 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__uyfeustvewbyjgjyyrqgrflkxhuxfloywsash62 mucudsm...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 05:31:15 scene dovecot: IMAP(__cpanel__service__auth__imap__uyfeustvewbyjgjyyrqgrflkxhuxfloywsash62m ucudsmjfmyolzcpm9shakkiw): Disconnected: Logged out bytes=11/340 Oct 12 05:36:15 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__g6g0w1ikkl7h2dx3uw8hdpin8uhjml0lgk08zxc kmn7fkd...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 05:36:16 scene dovecot: IMAP(__cpanel__service__auth__imap__g6g0w1ikkl7h2dx3uw8hdpin8uhjml0lgk08zxck mn7fkdpsvbrjptqanfuljfv2): Disconnected: Logged out bytes=11/340 Oct 12 05:41:15 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__hucgkkpt7ggbzuudcxecprlhdf_c1qenb56hqun f1neeqb...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 05:41:16 scene dovecot: IMAP(__cpanel__service__auth__imap__hucgkkpt7ggbzuudcxecprlhdf_c1qenb56hqunf 1neeqbmzas00uqbzmmjsxiab): Disconnected: Logged out bytes=11/340 Oct 12 05:46:17 scene dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__09irfuxyirdwosv6_f9prfvxpxhozr8qfauvfre yewqvxx...>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 12 05:46:17 scene dovecot: IMAP(__cpanel__service__auth__imap__09irfuxyirdwosv6_f9prfvxpxhozr8qfauvfrey ewqvxxeoo7yhyiki7ghukxss): Disconnected: Logged out bytes=11/340 Oct 12 05:47:27 scene dovecot: dovecot: Fatal: Time just moved backwards by 35 seconds. This might cause a lot of problems, so I'll just kill myself now. http://wiki.dovecot.org/TimeMovedBackwards

3 2

[Dovecot] Dovecot failed logins delay all logins
by Dominic Malolepszy 17 Oct '12

17 Oct '12

Hi all, I have observed with my Dovecot setup that unique failed logins cause legitimate correct logins to be slowed. I am running two servers, each with two Dovecot instances, a Proxy with Director, and a backend Dovecot. I suspect that the backend instance is throttling connections from the same IP, and because I am running a Proxy, the backend will only see either of the two server IPs. I confirmed this by directly connecting to the backend, to bypass the proxy and rule it. I initiated dozens of unique failed logins from one IP and separately attempted to login from the same IP, and experienced an extended delay during login. At the same time a login from a different IP suceeded imediately. I see nothing in the logs suggesting some sort of process limits were exceeded, however I do see the following proc title for the backend auth process: "dovecot/auth [7 wait, 0 passdb, 0 userdb]" I have increased the mail_max_userip_connections to a very large value however I believe that setting is a per username/ip limit. Is there any sort of setting in Dovecot that I can configure that stops this authentication throttling per IP? Below is the configuration of the backend Dovecot instance. # 2.1.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-279.5.2.el6.x86_64 x86_64 Red Hat Enterprise Linux Server release 6.3 (Santiago) auth_cache_negative_ttl = 3 secs auth_cache_size = 100 M auth_cache_ttl = 10 mins auth_default_realm = example.com auth_failure_delay = 5 secs auth_mechanisms = plain login auth_verbose_passwords = sha1 auth_worker_max_count = 25 base_dir = /var/run/dovecot/ disable_plaintext_auth = no first_valid_gid = 12 first_valid_uid = 8 last_valid_gid = 12 last_valid_uid = 8 login_greeting = Hello there. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c mail_fsync = always mail_gid = mail mail_location = maildir:%h/Maildir mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = " stats" mail_uid = mail mmap_disable = yes namespace { inbox = yes location = maildir:%h/Maildir prefix = INBOX. separator = . } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } protocols = pop3 imap service auth { unix_listener auth-userdb { group = mail mode = 0660 user = mail } } service imap-login { inet_listener imap { address = 0.0.0.0 port = 9143 } process_min_avail = 5 service_count = 0 vsz_limit = 256 M } service imap { process_limit = 1000 vsz_limit = 256 M } service pop3-login { inet_listener pop3 { address = 0.0.0.0 port = 9110 } process_min_avail = 5 service_count = 0 vsz_limit = 256 M } service pop3 { process_limit = 1000 vsz_limit = 256 M } service stats { fifo_listener stats-mail { mode = 0600 user = mail } inet_listener { address = 127.0.0.1 port = 24242 } } ssl = no stats_memory_limit = 64 M userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } verbose_proctitle = yes protocol imap { imap_logout_format = bytes_read=%i bytes_send=%o mail_max_userip_connections = 1000 mail_plugins = " stats " } protocol pop3 { mail_max_userip_connections = 1000 } Dominic

2 2

[Dovecot] LMTP userdb lookup
by list＠airstreamcomm.net 17 Oct '12

17 Oct '12

Is it possible to have separate userdb lookups for LMTP and POP/IMAP?

3 5

[Dovecot] Problem with quota update in dovecot 1.2
by tower 16 Oct '12

16 Oct '12

Hi A have a problem with quota2 table, working under postfixadmin. When I login into imap server with thunderbird client everything works fine, quota is update when i receive a message, but when I move message to trash or any other folder value for messages field in table quota2 increases +1 instead decreases or have still this same value. Only if I close my imap client value descending -2. I wish to table quota2 will be updated immediately after any operation on inbox. Is there any mistake in my configuration? Thanks for any advice. ============================================================== dovecot -n print: # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-xen-686 i686 Debian 6.0.3 ext3 log_path: /var/log/dovecot/error.log info_log_path: /var/log/dovecot/info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s disable_plaintext_auth: no 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 first_valid_uid: 100 mail_privileged_group: Debian-exim mail_uid: 101 mail_gid: 103 mail_location: maildir:/var/mail/virtual/%d/%n/Maildir mail_cache_min_mail_count: 100 mail_debug: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): autocreate quota imap_quota trash mail_plugins(imap): autocreate quota imap_quota trash mail_plugins(pop3): quota 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 imap_client_workarounds(default): tb-extra-mailbox-sep imap_client_workarounds(imap): tb-extra-mailbox-sep imap_client_workarounds(pop3): imap_id_log(default): * imap_id_log(imap): * imap_id_log(pop3): lda: postmaster_address: postmaster(a)mydomain.com mail_plugins: quota log_path: /var/log/dovecot/lda-errors.log info_log_path: /var/log/dovecot/deliver.log auth default: mechanisms: plain login verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: prefetch userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: Debian-exim plugin: autocreate: INBOX autocreate2: Sent autocreate3: Trash autocreate4: Drafts autocreate5: Junk autocreate6: Spam autosubscribe: INBOX autosubscribe2: Sent autosubscribe3: Trash autosubscribe4: Drafts autosubscribe5: Junk autosubscribe6: Spam quota: dict:user::proxy::quotadict quota_rule: Trash:storage=+20%% quota_rule2: Spam:ignore quota_rule3: Drafts:storage=+5%% quota_rule4: Sent:storage=+15%% quota_rule5: Junk:storage=+10%% quota_warning: storage=100%% quota-exceeded 100 %u quota_warning2: storage=95%% quota-warning 95 %u quota_warning3: storage=90%% quota-warning 90 %u quota_warning4: storage=85%% quota-warning 85 %u quota_warning5: storage=80%% quota-warning 80 %u quota_warning6: storage=75%% quota-warning 75 %u quota_warning7: storage=70%% quota-warning 70 %u quota_warning8: storage=65%% quota-warning 65 %u trash: /etc/dovecot/dovecot-trash.conf mail_log_events: delete undelete expunge copy mailbox_delete mailbox_rename flag_change append mail_log_group_events: no mail_log_fields: uid box msgid size subject from dict: quotadict: mysql:/etc/dovecot/dovecot-dict-quota.conf ============================================= cat /etc/dovecot/dovecot-sql.conf driver = mysql connect = host=localhost dbname=eximdb user=eximdbadm password=************* default_pass_scheme = PLAIN password_query = \ SELECT username as user, domain, password \ FROM mailbox WHERE username= '%u' AND active = 1 user_query = \ SELECT CONCAT('/var/mail/virtual/', maildir) AS home, 101 AS uid, 103 AS gid, concat('dict:storage=', CAST(ROUND(quota / 1024) AS CHAR), '::proxy::quotadict') AS quota, CONCAT('*:storage=', CAST(quota AS CHAR), 'B') AS quota_rule FROM mailbox WHERE username = '%u' AND active = '1' ============================================= cat /etc/dovecot/dovecot-dict-quota.conf connect = host=localhost dbname=eximdb user=eximdbadm password=********* map { pattern = priv/quota/storage table = quota2 username_field = username value_field = bytes } map { pattern = priv/quota/messages table = quota2 username_field = username value_field = messages } ============================================== cat /etc/dovecot/dovecot-trash.conf 1 Trash 2 Spam 3 Sent 4 Draft

2 3

[Dovecot] Plugin hooks in login process
by Simone Lazzaris 16 Oct '12

16 Oct '12

Hi all; I've setup dovecot (2.1.10) in a cluster configuration. We have two servers acting as frontend which authenticates users and proxy them to other two servers which handles the "real" work. Users credentials are on a mysql cluster; we have one master, in which read/write queries are processed, and many replicated slave, which process read-only queries. The frontend servers reads users credentials from the read-only mysql slaves. I'd like to execute a query once the client is verified to update the last login data. Right now, that query is executed on the backend servers, via a post-login service: protocols = imap service imap-postlogin { executable = script-login /usr/local/etc/dovecot/postlogin.sh unix_listener imap-postlogin { group = vchkpw mode = 0600 user = vpopmail } } service imap { executable = imap imap-postlogin process_limit = 2048 } Problem is, if I execute the update on the backend, I miss the information regarding the original IP, as I only see the IP of the proxies. I haven't been able to launch the postlogin service on the frontend, so I figured that I can try to write a plugin - that also seems to me the cleanest solution. Looking in the dovecot source code, I noticed that there aren't any hooks in the execution path used by the proxies; I am missing something ? I am the only one missing the presence of this hooks in the auth/proxy process ? I've also thought of a workaround for this problem. One way is to monitor the dovecot logs on the frontend and execute the update asyncronously. One other way is to query directly the main mysql server of the cluster and adjust the query making it call a stored procedure that updates the information in case of successful login. But I'd really prefer to create a plugin, that I'd be willing to share. I attach the configuration of the servers (front and back) generated via postfix -n. Thanks in advance for any help. -- Simone Lazzaris | Responsabile aree datacenter e VoIP Interactive Network srl | via Roggia Vignola 9, 24047 Treviglio (BG) Tel. 0363 1970352 | Fax 0363.1971971 | www.interactive.eu

2 2