September 2013 - dovecot

[Dovecot] More fine-grained connection limitations?
by Micah Anderson 07 Sep '13

07 Sep '13

There is the mail_max_userip_connections setting, which helps for dealing with number of connections at any given time, but I'm looking for something that will help deal with users who configure their mail clients to connect too frequently. For example, I've seen users who configured their clients to check (IMAP) mail every 3 seconds. This is far too frequent and puts unnecessary load on the server. Even once per minute seems excessive to me. It would be really great if there were a way to tarpit those users to slow them down, or send them an imap message saying they are connecting to often and connections have been disabled for the next 5 minutes or something. Micah ps - what happens to a user when they hit mail_mx_userip_connections? Further connections are just denied, or dropped?

1 0

[Dovecot] Plus addressing
by LuKreme 07 Sep '13

07 Sep '13

It appease that I can enable +address filtering into separate mailboxes by simply setting $recipient_delimiter = '+'; However, is there anyway to get great control over that? For example, on one account I have a lot of +addresses I use. A few, I sort into mailboxes (like my bank, credit cards, etc). The rest are either on the “spammer => /dev/null” list or get sorted into a mailbox named “Misc” (like various newsletters and offers and sales from companies I do business with). -- Sigs are b0rk3d.

6 6

[Dovecot] Dovecot 2.1.7 not starting properly, mail not delivered
by Aldo & Caroline 07 Sep '13

07 Sep '13

On my debian box dovecot does not start properly any more, and mails don't get delivered or sent. I've googled around without finding any useful leads. Hopefully someone is willing to educate me. My guess is it must be a config problem after an upgrade, since I didn't change anything myself directly. Not sure when it started, since I this mail server is not our default machine (yet). Symptoms Upon /etc/init.d/dovecot restart my command line says [ ok ] Restarting IMAP/POP3 mail server: dovecot. But I find in /var/log/mail.log: Sep 6 11:17:36 debian2 dovecot: master: Warning: Killed with signal 15 (by pid=19112 uid=0 code=kill) Sep 6 11:17:36 debian2 dovecot: master: Dovecot v2.1.7 starting up (core dumps disabled) Sep 6 11:17:37 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:38 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:39 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:40 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:41 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:42 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:43 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:44 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:45 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:45 debian2 postfix/cleanup[18466]: warning: tcp:127.0.0.1:10001 lookup error for "aldo(a)alcatoka.nl" Sep 6 11:17:45 debian2 postfix/cleanup[18466]: warning: 57B7D3640073: sender_canonical_maps map lookup problem for aldo(a)alcatoka.nl Sep 6 11:17:45 debian2 postfix/pickup[17004]: warning: maildrop/4EA313640071: error writing 57B7D3640073: queue file write error I do NOT see a line like ... dovecot: auth-worker(default): pgsql: Connected to 127.0.0.1 (mailserver) as mentioned in this <https://workaround.org/ispmail/squeeze/setting-up-dovecot?page=1> tutorial, which I used to set up the previous Dovecot version (which worked OK). When starting Dovecot from the command line with dovecot -F -c /etc/dovecot/dovecot.conf nothing is printed (as if the process is waiting for more input), while it should at least produce some output, right? I'm running Debian 7.1 with an ext3 filesystem together with Postfix 2.9.6 on an x86 machine. CPU info: processor : 0 vendor_id : AuthenticAMD cpu family : 16 model : 6 model name : AMD Sempron(tm) 140 Processor cpu MHz : 800.000 cache size : 1024 KB As far as I can tell, Postfix is running OK. /etc/dovecot/dovecot.conf says: # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-686-pae i686 Debian 7.1 ext3 auth_mechanisms = plain login disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/var/vmail/%d/%n/Maildir mail_privileged_group = mail passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = imap pop3 service auth { unix_listener auth-master { group = vmail mode = 0600 user = vmail } user = root } ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { args = uid=3000 gid=3000 home=/var/vmail/%d/%n allow_all_users=yes driver = static } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol lda { auth_socket_path = /var/run/dovecot/auth-master log_path = mail_plugins = sieve postmaster_address = aldo(a)alcatoka.nl As far as I understand, there must be a process (dovecot-auth?) that takes care of translating mail adresses, taking a string at port 10001 and returning the translated string on 10002. This process does not seem to kick off when dovecot restarts. Please tell me if I'm thinking in the right direction, and - more importantly - what I need to do to get dovecot running. I will be happy to provide more test results if that helps, just tell me what you need. Regards, Aldo Verlinde

1 1

[Dovecot] which clients support SCRAM-SHA-1
by Reindl Harald 07 Sep '13

07 Sep '13

Hi running dovecot as IMAP/POP3-proxy with auth_mechanisms = CRAM-MD5 DIGEST-MD5 SCRAM-SHA-1 APOP LOGIN PLAIN which client supports currently "SCRAM-SHA-1" to test it?

1 0

Re: [Dovecot] doveadm expunge problems
by Joseph Tam 07 Sep '13

07 Sep '13

nicolasfo wrote: > doveadm search -u *(a)mydomain.fr MAILBOX Junk savedbefore 1d : don't lists > anything.. > > What am I missed ? > > Is this the good way to change file date (touch) and by this way, have > results to savedbefore command ? No. The date.saved value is (I think) stored in its indices, and is updated via IMAP operations. This value is not derived from file timestamps. You can use doveadm fetch to get the values that dovecot uses dovecot -ftab fetch -A 'mailbox date.saved' mailbox Junk If you actually use IMAP operations to move messages from INBOX to Junk, I think you'll find that date.saved reflects the correct value. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] userdb with LDAP
by Tobi 06 Sep '13

06 Sep '13

Hi list I currently having troubles to "connect" dovecot (for proxy) to an existing LDAP. If I got the dovecot wiki right only userdb is needed for a proxy setup where the proxy does not authenticate but just forward to the backend for authentication. So I setup the following in dovecot-ldap.conf.ext user_attrs = =password,=y=nopasswd,=y=proxy,mailHost=host user_filter = (&(objectClass=posixAccount)(uid=%u)) There is a field mailHost in LDAP which defines the correct backend for the user and defined userdb in auth-ldap.conf.ext userdb { driver = ldap args = /etc/dovecot/dovecot-ldap.conf.ext } the same config again in auth-system.conf.ext The problem is that dovecot always reports back that the user is unknown. I turned on ldap debug and got the following Sep 6 13:06:10 kolab-frontend dovecot: auth: Debug: ldap(tobi.szyndler(a)datapark.li,213.196.149.1,<88FSBrXlSQDVxJUB>): pass search: base=dc=datapark,dc=li scope=subtree filter=(&(objectClass=posixAccount)(uid=tobi.szyndler(a)datapark.li)) fields=mailHost Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_search Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: "(&(objectClass=posixAccount)(uid=tobi.szyndler(a)datapark.li))" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: AND Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter_list "(objectClass=posixAccount)(uid=tobi.szyndler(a)datapark.li)" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: "(objectClass=posixAccount)" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: simple Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_simple_filter: "objectClass=posixAccount" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: "(uid=tobi.szyndler(a)datapark.li)" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: simple Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_simple_filter: "uid=tobi.szyndler(a)datapark.li" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_build_search_req ATTRS: mailHost Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_send_initial_request Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_send_server_request Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_result ld 0x7fbc43fb4110 msgid -1 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: wait4msg ld 0x7fbc43fb4110 msgid -1 (timeout 0 usec) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: wait4msg continue ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Connections: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: * host: 213.196.149.116 port: 389 (default) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: refcnt: 2 status: Connected Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: last used: Fri Sep 6 13:06:10 2013 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Outstanding Requests: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: * msgid 4, origid 4, status InProgress Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: outstanding referrals 0, parent count 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ld 0x7fbc43fb4110 request count 1 (abandoned 0) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Response Queue: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Empty Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ld 0x7fbc43fb4110 response count 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_chkResponseList ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_chkResponseList returns ld 0x7fbc43fb4110 NULL Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_int_select Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: read1msg: ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: read1msg: ld 0x7fbc43fb4110 msgid 4 message type search-result Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: read1msg: ld 0x7fbc43fb4110 0 new referrals Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: read1msg: mark request completed, ld 0x7fbc43fb4110 msgid 4 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: request done: ld 0x7fbc43fb4110 msgid 4 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: res_errno: 0, res_error: <>, res_matched: <> Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_free_request (origid 4, msgid 4) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_parse_result Sep 6 13:06:10 kolab-frontend dovecot: auth: ldap(tobi.szyndler(a)datapark.li,213.196.149.1,<88FSBrXlSQDVxJUB>): unknown user Sep 6 13:06:10 kolab-frontend dovecot: auth: Debug: ldap(tobi.szyndler(a)datapark.li,213.196.149.1,<88FSBrXlSQDVxJUB>): pass search: base=dc=datapark,dc=li scope=subtree filter=(&(objectClass=posixAccount)(uid=tobi.szyndler(a)datapark.li)) fields=mailHost Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_search Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: "(&(objectClass=posixAccount)(uid=tobi.szyndler(a)datapark.li))" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: AND Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter_list "(objectClass=posixAccount)(uid=tobi.szyndler(a)datapark.li)" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: "(objectClass=posixAccount)" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: simple Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_simple_filter: "objectClass=posixAccount" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: "(uid=tobi.szyndler(a)datapark.li)" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: simple Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_simple_filter: "uid=tobi.szyndler(a)datapark.li" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_build_search_req ATTRS: mailHost Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_send_initial_request Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_send_server_request Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_msgfree Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_result ld 0x7fbc43fb4110 msgid -1 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: wait4msg ld 0x7fbc43fb4110 msgid -1 (timeout 0 usec) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: wait4msg continue ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Connections: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: * host: 213.196.149.116 port: 389 (default) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: refcnt: 2 status: Connected Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: last used: Fri Sep 6 13:06:10 2013 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Outstanding Requests: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: * msgid 5, origid 5, status InProgress Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: outstanding referrals 0, parent count 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ld 0x7fbc43fb4110 request count 1 (abandoned 0) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Response Queue: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Empty Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ld 0x7fbc43fb4110 response count 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_chkResponseList ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_chkResponseList returns ld 0x7fbc43fb4110 NULL Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_int_select Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_result ld 0x7fbc43fb4110 msgid -1 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: wait4msg ld 0x7fbc43fb4110 msgid -1 (timeout 0 usec) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: wait4msg continue ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Connections: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: * host: 213.196.149.116 port: 389 (default) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: refcnt: 2 status: Connected Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: last used: Fri Sep 6 13:06:10 2013 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Outstanding Requests: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: * msgid 5, origid 5, status InProgress Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: outstanding referrals 0, parent count 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ld 0x7fbc43fb4110 request count 1 (abandoned 0) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Response Queue: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Empty Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ld 0x7fbc43fb4110 response count 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_chkResponseList ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_chkResponseList returns ld 0x7fbc43fb4110 NULL Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_int_select Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: read1msg: ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: read1msg: ld 0x7fbc43fb4110 msgid 5 message type search-result Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: read1msg: ld 0x7fbc43fb4110 0 new referrals Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: read1msg: mark request completed, ld 0x7fbc43fb4110 msgid 5 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: request done: ld 0x7fbc43fb4110 msgid 5 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: res_errno: 0, res_error: <>, res_matched: <> Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_free_request (origid 5, msgid 5) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_parse_result Sep 6 13:06:10 kolab-frontend dovecot: auth: ldap(tobi.szyndler(a)datapark.li,213.196.149.1,<88FSBrXlSQDVxJUB>): unknown user Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_msgfree Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_result ld 0x7fbc43fb4110 msgid -1 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: wait4msg ld 0x7fbc43fb4110 msgid -1 (timeout 0 usec) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: wait4msg continue ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Connections: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: * host: 213.196.149.116 port: 389 (default) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: refcnt: 1 status: Connected Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: last used: Fri Sep 6 13:06:10 2013 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Outstanding Requests: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Empty Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ld 0x7fbc43fb4110 request count 0 (abandoned 0) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Response Queue: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Empty Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ld 0x7fbc43fb4110 response count 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_chkResponseList ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_chkResponseList returns ld 0x7fbc43fb4110 NULL Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_int_select I'm pretty sure that the error is 30cm in front of the screen :-) but I really don't see the problem Any help is highly appreciated Thanks tobi

1 1

[Dovecot] doveadm expunge problems
by nicolasfo 06 Sep '13

06 Sep '13

Hello there, I'm trying to use the doveadm expunge function, but it doesn't seems to work.. I have installed a mail test server using iredmail, Dovecot and postfix using mysql for authentications. I sent a email to this server, and change the timestamp using touch. the mail boxes are as follow : /home/mail/vmail1/mydomain.fr/n/i/c/nicolas-2013.09.05.14.30.49/Maildir I want to delete mails that are, let's say, 1day old from the "Junk" folder. (I put the mail I changed the date in it). I run this command : doveadm -Dv expunge -u nicolas(a)mydomain.fr mailbox "Junk" savedbefore 1d The mail is still in the "Junk" folder, and I have this output : root@mail:/home/mail/vmail1# doveadm -Dv expunge -u nicolas(a)mydomain.fr mailbox "Junk" savedbefore 1d doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm doveadm(root): Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_deinit (this is usually intentional, so just ignore this message) doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so doveadm(root): Debug: Skipping module doveadm_zlib_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_zlib_plugin.so: undefined symbol: i_stream_create_deflate (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) doveadm(nicolas(a)mydomain.fr): Debug: Added userdb setting: plugin/master_user=nicolas(a)mydomain.fr doveadm(nicolas(a)mydomain.fr): Debug: Added userdb setting: plugin/quota_rule=*:bytes=1073741824 doveadm(nicolas(a)mydomain.fr): Debug: Effective uid=2000, gid=2000, home=/home/mail/vmail1/mydomain.fr/n/i/c/nicolas-2013.09.05.14.30.49/ doveadm(nicolas(a)mydomain.fr): Debug: Quota root: name=user backend=dict args=:proxy::quotadict doveadm(nicolas(a)mydomain.fr): Debug: Quota rule: root=user mailbox=* bytes=1073741824 messages=0 doveadm(nicolas(a)mydomain.fr): Debug: Quota warning: bytes=912680550 (85%) messages=0 reverse=no command=quota-warning 85 nicolas(a)mydomain.fr doveadm(nicolas(a)mydomain.fr): Debug: Quota warning: bytes=966367641 (90%) messages=0 reverse=no command=quota-warning 90 nicolas(a)mydomain.fr doveadm(nicolas(a)mydomain.fr): Debug: Quota warning: bytes=1020054732 (95%) messages=0 reverse=no command=quota-warning 95 nicolas(a)mydomain.fr doveadm(nicolas(a)mydomain.fr): Debug: dict quota: user=nicolas(a)mydomain.fr, uri=proxy::quotadict, noenforcing=0 doveadm(nicolas(a)mydomain.fr): Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir://home/mail/vmail1/mydomain.fr/n/i/c/nicolas-2013.09.05.14.30.49//Maildir/:INDEX=//home/mail/vmail1/mydomain.fr/n/i/c/nicolas-2013.09.05.14.30.49//Maildir/ doveadm(nicolas(a)mydomain.fr): Debug: maildir++: root=//home/mail/vmail1/mydomain.fr/n/i/c/nicolas-2013.09.05.14.30.49//Maildir, index=, control=, inbox=//home/mail/vmail1/mydomain.fr/n/i/c/nicolas-2013.09.05.14.30.49//Maildir, alt= doveadm(nicolas(a)mydomain.fr): Debug: Namespace : type=shared, prefix=Shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/Shared/%u doveadm(nicolas(a)mydomain.fr): Debug: shared: root=/var/run/dovecot, index=, control=, inbox=, alt= I don't understand, the output seems to be OK, except loading modules at the begining, but I think there's no effect to expunge command... Anyone to help me, please ? Thnaks in advance Nicolas -- View this message in context: http://dovecot.2317879.n4.nabble.com/doveadm-expunge-problems-tp44200.html Sent from the Dovecot mailing list archive at Nabble.com.

1 1

[Dovecot] stopping dictionary attacks (pop3)
by other＠ahhyes.net 05 Sep '13

05 Sep '13

Hi Guys, I was really hoping a couple of years later this would be addressed... I'm running Dovecot 2.2.5 on FreeBSD. Is there anyway to limit the number of auth attempts allowed in a single session? The reason for this is because I have "fail2ban" setup to firewall out any IP addresses that repeatedly auth fails. The issue occurs when the connection is already in an "established" state and the attacker uses the existing session to hammer away, fail2ban becomes ineffective as dovecot appears to allow the person to attempt authentication ad infinitum. It would be nice if there was config option that would for example cause the software to close the connection after X failed attempts. I use "pf" as the firewall on FreeBSD. Unless there was some command I could have fail2ban run a command that would destroy any tcp sessions in an established state prior to adding the offending IP to the block list, that would be the only way around the problem. Ideally it would be nice for dovecot have an option to control the number of failed auth attempts. Any suggestions? Cheers, Alex.

2 3

[Dovecot] Received header only showing localhost
by Matt Devaney 04 Sep '13

04 Sep '13

Hi all, Im a new dovecot user and a first-time poster so please forgive me if this is a stupid question, or even (as I suspect it might be) not really a Dovecot question. My system is the fairly typical mix of postfix, amavis-new, and Dovecot. For some reason Ive noticed that when I look at the mail headers for delivered messages the Received header is missing the detail of any external servers that the mail went through, and additionally the tag appears twice; for example the Welcome to the dovecot mailing list email has: Received: from localhost (localhost [127.0.0.1]) by droplet.the-wyvern.net (Postfix) with ESMTP id DDDD163F73 for <myname(a)mydomain.net>; Mon, 26 Aug 2013 16:40:19 +0000 (UTC) Received: from droplet.the-wyvern.net ([127.0.0.1]) by localhost (droplet.the-wyvern.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6AFMiG0TAHUv for <myname(a)mydomain.net>; Mon, 26 Aug 2013 16:40:17 +0000 (UTC) Searching through the dovecot.markmail archive I can see this doesnt seem to be too unusual in that there are other examples where folk have posted message headers with the above format, however Im wondering if theres a good reason for it and if I can turn it off? I quite like being able to see where my mail came from :) If theres a man / wiki page to read somewhere that explains it then please feel free to tell me to RTM (.. long as you also point me in the right direction :p ) Thanks, Matt

2 4

[Dovecot] OT: z-Push
by Christian Rößner 04 Sep '13

04 Sep '13

Hi, just a short question: I have installed and configured z-Push to use BackendIMAP. On my iPhone I have created an account and I can see my mails. Also sending works. So far so good. Now the question: When I create a new folder i.e. Test under the root (/), then I get an error. And after resyncing the folder has been created not under /, but under /0/Test. Also I can not remove that folder over ActiveSync. Does somebody have z-Push fully working with Dovecot or is z-Push designed for Cyrus and only some features are working with Dovecot? So at the moment folder create/move/delete does not work here with z-Push-2.0.3 and Dovecot 2.1.9 Thanks in advance -Christian Rößner --- Bachelor of Science Informatik Erlenwiese 14, 36304 Alsfeld T: +49 6631 78823400, F: +49 6631 78823409, M: +49 176 93118939 USt-IdNr.: DE225643613, http://www.roessner-network-solutions.com

4 4