- dovecot - dovecot.org

[Dovecot] Sieve scripts in mysql?
by Simon 16 Jul '13

16 Jul '13

Hi There. We are using dovecot v2.2.4 with pigeonhole 0.4.1 (both compiled from source) Centos 6.4. We are storing our virtual user config in mysql. At the moment we are storing our sieve script configs in mysql and then running a script to write these out to a file.. But I'm wondering if there a way to store sieve scripts in mysql? Many thanks! Simon

1 1

[Dovecot] Services not starting in 2.1 (or 2.2)
by Tommy Wareing 16 Jul '13

16 Jul '13

I'm trying to install Dovecot onto my QNAP NAS. I apologise for this! It means I'm not working in a normal environment, and don't (necessarily) have the normal range of tools available (or the most up to date version of those tools). It seems that 2.0.21 works (at least, as far as I've tested), but 2.1.17 and 2.2.4 won't start up their child services. I've got the source code for all three from http://www.dovecot.org/download.html, and, for experimental purposes, I'm configuring with: ./configure --prefix=/opt The configure script ends by reporting: Install prefix . : /opt File offsets ... : 64bit I/O polling .... : epoll I/O notifys .... : inotify SSL ............ : yes (OpenSSL) GSSAPI ......... : no passdbs ........ : static passwd passwd-file shadow checkpassword : -pam -bsdauth -sia -ldap -sql -vpopmail userdbs ........ : static prefetch passwd passwd-file checkpassword nss : -ldap -sql -vpopmail SQL drivers .... : : -pgsql -mysql -sqlite The dovecot.conf I'm using, at the moment, is the absolute minimal to fire things up: protocols = imap listen = * ssl_cert = </opt/etc/ssl/certs/dovecot.pem ssl_key = </opt/etc/ssl/private/dovecot.pem dovecot -n is happy, and reports those four lines back to me. When I start this up, I get, in /var/log/messages file: Jul 10 10:09:28 QNAP mail.info dovecot: master: Dovecot v2.0.21 starting up (core dumps disabled) and ps shows: [admin@qnap dovecot]# ps -ef | grep dovecot admin 11478 1 0 10:09 ? 00:00:00 /opt/sbin/dovecot dovecot 11479 11478 0 10:09 ? 00:00:00 dovecot/anvil admin 11480 11478 0 10:09 ? 00:00:00 dovecot/log admin 11482 11478 0 10:09 ? 00:00:00 dovecot/config admin 11525 455 0 10:10 pts/5 00:00:00 grep dovecot All is right with the world! Well, until I try to use dovecot properly, at which point I'll need a full configuration. But it's alright so far! :) However, if I go through the same routine with Dovecot 2.1.17, I get the appropriate message in messages: Jul 10 10:12:45 QNAP mail.info dovecot: master: Dovecot v2.1.17 starting up (core dumps disabled) But this time, ps shows: [admin@qnap dovecot-2.1.17]# ps -ef | grep dovecot admin 15259 1 0 10:12 ? 00:00:00 /opt/sbin/dovecot admin 15294 455 0 10:12 pts/5 00:00:00 grep dovecot and the child services don't seem to have started. This is born out by the fact that no network connections work: they stall, and then eventually time out (telnet localhost 143 produces no output at all, until I disconnect it). Even dovecot stop has trouble, taking several seconds before it returns me to the prompt, and *not* killing the existing process. dovecot -n is still happy however (and in a full configuration, components which don't require the services seem to work properly, such as dovecot-lda, if it doesn't require auth). I'm not sure that I need those newer versions of dovecot, so I'll get back to version 2.0 for now. But I'd certainly like the option, and imagine that somebody else might care as to what the problem is! -- Tommy Wareing

4 8

[Dovecot] trying to configre dovecot
by Gene Heskett 15 Jul '13

15 Jul '13

Hi all; Thinking I'd like to have a bit of security, I followed the example for dovecot from allgoodthings.org Guessing between the lines I made a few substitutions to localize it for me, but when I run the line to dump the configs, the output is very short because I do not have the *.pem files. Where can a usable set of these ssl 'keyfiles' be obtained? Cheers, Gene -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) My web page: <http://coyoteden.dyndns-free.com:85/gene> is up! My views <http://www.armchairpatriot.com/What%20Has%20America%20Become.shtml> Gee, I feel kind of LIGHT in the head now, knowing I can't make my satellite dish PAYMENTS! A pen in the hand of this president is far more dangerous than 200 million guns in the hands of law-abiding citizens.

3 6

[Dovecot] User login for SMTP but not for IMAP/POP?
by Martin 15 Jul '13

15 Jul '13

Hello everybody, I have a question, though I'm not sure if it's a matter of dovecot or postfix. Or if it's even possible to do at all. If I understand it correctly, SMTP authentification is done via SASL. When a user wants to login Postfix queries an external user database (dovecot). Therefore the SMTP-users are identical to the IMAP/POP-users. I want to achieve the following: I want some user credentials (username&password) for a user that is able to login via SMTP, but who doesn't have a mailbox and therefore shouldn't be able to login via IMAP/POP. Is this even possible? How can it be achieved? Or: does this behaviour have a special name, which I can google for? Regards, Martin

2 1

[Dovecot] login_trusted_networks from webmail ?
by Jan-Frode Myklebust 15 Jul '13

15 Jul '13

I'd like to get the IP-address of the webmail-klient logged in my maillog (for being compliant with coming data retention policies). I've noticed that with login_trusted_networks pointing at my dovecot directors, we get rip=client-ip logged on the backends. How is the proxy providing this to the dovecot backends? Anybody know what magic we need to implement in our webmail-solution to be able to forward the webmail-client-ip and have it logged as rip= in dovecot? I belive it will be enough to have it logged as rip= on the directors, maybe not needed to be forwarded all the way to the backends (but that would be nice as well). -jf

3 7

[Dovecot] new user questions
by Gene Heskett 14 Jul '13

14 Jul '13

Greetings; Trying to follow along with the wiki2 setup instructions and thought I'd hit a snag with the first "send me a mail" snippet as it took several minutes to arrive, so I assume that somehow procmail was involved in the delivery and my procmail runs mail thought a whole bunch of checks before finally handing it off to a mailfile as /var/mail/gene. Then the next script seems to only try whats in my home dir, and of course doesn't find it as neither exists, yet... I assume that is because dovecot needs a kill -HUP. But I am not familiar with that, so how is it done, and as what user, me, or root, on a ubuntu 12.04.2 LTS install? Thanks. Cheers, Gene -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) My web page: <http://coyoteden.dyndns-free.com:85/gene> is up! My views <http://www.armchairpatriot.com/What%20Has%20America%20Become.shtml> Beam me up, Scotty! A pen in the hand of this president is far more dangerous than 200 million guns in the hands of law-abiding citizens.

3 4

[Dovecot] Mail replication ... totally confused !
by HL 13 Jul '13

13 Jul '13

Hello, I am totally confused configuring replication in dovecot. In my case I have 2 servers instead of running rsync as a daemon which takes a lot of time I would like SERVER-A will be the master and SERVER-B will be the slave My users directly interact with server A, Server B stands as a mails backup only I've setup SERVER-B ( backup ) like that, NO SPECIAL CONF on master SERVER-A Is this ok ?? I Don't want to miss any mails Since this is a live server service aggregator { # give enough permissions for mail processes # fifo_listener replication-notify-fifo { user = vmail mode = 0600 } unix_listener replication-notify { user = vmail mode = 0600 } } service replicator { # start replication at startup # process_min_avail = 1 } service doveadm { # if you're using a single virtual user, set this to start ssh as vmail # (not root) # user = vmail } service config { # needed to grant access to /var/run/dovecot/config for service doveadm # unix_listener config { user = vmail } } dsync_remote_cmd = ssh -p 1234 -l%{login} %{host} doveadm dsync-server -u%u -l%{lock_timeout} -n%{namespace} plugin { mail_replica = remote:vmail@master-server-a.tld replication_full_sync_interval = 1 hours }

1 0

[Dovecot] Dovecot 2.2.4 metadata-plugin not support UTF7
by Sergey Sidlyarenko 13 Jul '13

13 Jul '13

In Dovecot 2.2.4 metadata-plugin crach on setmetadata but worked on ascii folders? but not worked on utf7 (non ascii) folders. [13-Jul-2013 19:15:36 +0400]: [F537] S: A0002 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY MOVE METADATA ANNOTATEMORE] Logged in [13-Jul-2013 19:15:36 +0400]: [F537] C: A0003 CREATE &BB0EPgQyBEsEOQ-8 [13-Jul-2013 19:15:36 +0400]: [F537] S: A0003 OK Create completed. [13-Jul-2013 19:15:36 +0400]: [F537] C: A0004 SUBSCRIBE &BB0EPgQyBEsEOQ-8 [13-Jul-2013 19:15:36 +0400]: [F537] S: A0004 OK Subscribe completed. [13-Jul-2013 19:15:36 +0400]: [F537] C: A0005 SETMETADATA &BB0EPgQyBEsEOQ-8 (/shared/vendor/kolab/folder-type event /private/vendor/kolab/folder-type NIL) [13-Jul-2013 19:15:36 +0400]: [F537] S: A0005 NO Mailbox does not exist. [13-Jul-2013 19:15:36 +0400]: [F537] C: A0006 SETMETADATA &BB0EPgQyBEsEOQ-8 (/private/vendor/kolab/folder-type event) [13-Jul-2013 19:15:36 +0400]: [F537] S: A0006 NO Mailbox does not exist. [13-Jul-2013 19:15:36 +0400]: [F537] C: A0007 LIST "" "&BB0EPgQyBEsEOQ-8/*" [13-Jul-2013 19:15:36 +0400]: [F537] S: A0007 OK List completed. [13-Jul-2013 19:15:36 +0400]: [F537] C: A0008 GETMETADATA "*" (/private/vendor/kolab/folder-type /shared/vendor/kolab/folder-type) [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Drafts" ("/private/vendor/kolab/folder-type" "mail.drafts") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Drafts" ("/shared/vendor/kolab/folder-type" "mail") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Configuration" ("/private/vendor/kolab/folder-type" "configuration.default") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Configuration" ("/shared/vendor/kolab/folder-type" "configuration") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Notes" ("/private/vendor/kolab/folder-type" "note.default") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Notes" ("/shared/vendor/kolab/folder-type" "note") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Junk" ("/private/vendor/kolab/folder-type" "mail.junkemail") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Junk" ("/shared/vendor/kolab/folder-type" "mail") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "FreeBusy" ("/private/vendor/kolab/folder-type" "freebusy.default") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "FreeBusy" ("/shared/vendor/kolab/folder-type" "freebusy") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "INBOX" ("/private/vendor/kolab/folder-type" "mail.inbox") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "INBOX" ("/shared/vendor/kolab/folder-type" "mail") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Sent" ("/private/vendor/kolab/folder-type" "mail.sentitems") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Sent" ("/shared/vendor/kolab/folder-type" "mail") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "New8" ("/shared/vendor/kolab/folder-type" "event") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Tasks" ("/private/vendor/kolab/folder-type" "task.default") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Tasks" ("/shared/vendor/kolab/folder-type" "task") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Trash" ("/private/vendor/kolab/folder-type" "mail.wastebasket") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Trash" ("/shared/vendor/kolab/folder-type" "mail") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Calendar" ("/private/vendor/kolab/folder-type" "event.default") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Calendar" ("/shared/vendor/kolab/folder-type" "event") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Calendar/New" ("/shared/vendor/kolab/folder-type" "event") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Calendar/New4" ("/shared/vendor/kolab/folder-type" "event") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Calendar/New3" ("/shared/vendor/kolab/folder-type" "event") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Calendar/Home" ("/shared/vendor/kolab/folder-type" "event") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Calendar/New2" ("/shared/vendor/kolab/folder-type" "event") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Calendar/New1" ("/shared/vendor/kolab/folder-type" "event") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "New7" ("/shared/vendor/kolab/folder-type" "event") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Addressbook" ("/private/vendor/kolab/folder-type" "contact.default") [13-Jul-2013 19:15:36 +0400]: [F537] S: * METADATA "Addressbook" ("/shared/vendor/kolab/folder-type" "contact") [13-Jul-2013 19:15:36 +0400]: [F537] S: A0008 OK Completed. [13-Jul-2013 19:15:36 +0400]: [F537] C: A0009 DELETE &BB0EPgQyBEsEOQ-8 [13-Jul-2013 19:15:36 +0400]: [F537] S: A0009 OK Delete completed. [13-Jul-2013 19:15:36 +0400]: [F537] C: A0010 UNSUBSCRIBE &BB0EPgQyBEsEOQ-8 [13-Jul-2013 19:15:36 +0400]: [F537] S: A0010 OK Unsubscribe completed. [13-Jul-2013 19:15:36 +0400]: [F537] C: A0011 LOGOUT [13-Jul-2013 19:15:36 +0400]: [F537] S: * BYE Logging out [13-Jul-2013 19:15:36 +0400]: [F537] S: A0011 OK Logout completed. -- Sidlyarenko Sergey https://github.com/lefoyer

1 0

[Dovecot] Dovecot 2.2.4 metadata-plugin crached
by Sergey Sidlyarenko 13 Jul '13

13 Jul '13

Dovecot (deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main) crached after create new metadata folder (But the folder with metadata is created). Metadata plugin v14. Coredump: http://yadi.sk/d/bsBCpRS76mXpj in log: imap(admin(a)example.ru): Fatal: master: service(imap): child 14339 killed with signal 11 (core dumped) [10-Jul-2013 11:46:00 +0400]: [A4A2] S: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Welcome to TU FKP IMAP server. [10-Jul-2013 11:46:00 +0400]: [A4A2] C: A0001 ID ("name" "Roundcube" "version" "1.0-git" "php" "5.4.4-14+deb7u2" "os" "Linux" "command" "/?_task=calendar&_action=calendar") [10-Jul-2013 11:46:00 +0400]: [A4A2] S: * ID ("name" "Dovecot") [10-Jul-2013 11:46:00 +0400]: [A4A2] S: A0001 OK ID completed. [10-Jul-2013 11:46:00 +0400]: [A4A2] C: A0002 AUTHENTICATE PLAIN pass [10-Jul-2013 11:46:00 +0400]: [A4A2] S: A0002 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY MOVE METADATA ANNOTATEMORE] Logged in [10-Jul-2013 11:46:00 +0400]: [A4A2] C: A0003 CREATE Calendar/New4 [10-Jul-2013 11:46:00 +0400]: [A4A2] S: A0003 OK Create completed. [10-Jul-2013 11:46:00 +0400]: [A4A2] C: A0004 SUBSCRIBE Calendar/New4 [10-Jul-2013 11:46:00 +0400]: [A4A2] S: A0004 OK Subscribe completed. [10-Jul-2013 11:46:00 +0400]: [A4A2] C: A0005 SETMETADATA Calendar/New4 (/shared/vendor/kolab/folder-type event /private/vendor/kolab/folder-type NIL) root@mail:/var/core# gdb /usr/lib/dovecot/imap /var/core/19851 GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/lib/dovecot/imap...Reading symbols from /usr/lib/debug/usr/lib/dovecot/imap...done. done. [New LWP 19851] warning: Can't read pathname for load map: Ошибка ввода/вывода. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `dovecot/imap'. Program terminated with signal 11, Segmentation fault. #0 0x00007f0a7102686f in ?? () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt full #0 0x00007f0a7102686f in ?? () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00007f0a700ccad9 in metadata_set_entry (entry=0x1705880, user=<optimized out>) at metadata-backend.c:133 muser = 0x16f6550 key = <optimized out> dt = <optimized out> #2 0x00007f0a6fcc4c91 in setmetadata_helper (box=0x1700080, args=<optimized out>, cmd=0x16fb440) at imap-metadata-plugin.c:673 name = 0x16fffd8 "/private/vendor/kolab/folder-type" value = 0x0 entry = <optimized out> ret = <optimized out> warn_maxsize = <optimized out> warn_toomany = <optimized out> arglist = 0x16ffeb8 response = <optimized out> warn_noprivate = false #3 cmd_setmetadata (cmd=0x16fb440) at imap-metadata-plugin.c:761 args = 0x16ffca8 mailbox_name = 0x16ffe10 "Calendar/New3" box = 0x1700080 #4 0x000000000041679c in command_exec (cmd=cmd@entry=0x16fb440) at imap-commands.c:156 hook = 0x16e00b0 ret = <optimized out> #5 0x0000000000415800 in client_command_input (cmd=0x16fb440) at imap-client.c:775 client = 0x16fa910 command = <optimized out> __FUNCTION__ = "client_command_input" #6 0x00000000004158ba in client_command_input (cmd=0x16fb440) at imap-client.c:836 client = 0x16fa910 command = <optimized out> __FUNCTION__ = "client_command_input" #7 0x0000000000415b75 in client_handle_next_command (remove_io_r=<synthetic pointer>, client=0x16fa910) at imap-client.c:874 No locals. #8 client_handle_input (client=client@entry=0x16fa910) at imap-client.c:886 _data_stack_cur_id = 3 ret = false remove_io = false handled_commands = false __FUNCTION__ = "client_handle_input" #9 0x0000000000415f22 in client_input (client=0x16fa910) at imap-client.c:928 cmd = <optimized out> output = 0x16fb308 bytes = 112 __FUNCTION__ = "client_input" #10 0x00007f0a71309f66 in io_loop_call_io (io=0x16f8bd0) at ioloop.c:387 ioloop = 0x16df700 t_id = 2 #11 0x00007f0a7130add7 in io_loop_handler_run (ioloop=ioloop@entry=0x16df700) at ioloop-epoll.c:215 ctx = 0x16e0390 events = 0x0 event = 0x16e11f0 list = 0x16f8c20 io = <optimized out> tv = {tv_sec = 1799, tv_usec = 999792} events_count = <optimized out> msecs = <optimized out> ret = 1 i = <optimized out> call = <optimized out> __FUNCTION__ = "io_loop_handler_run" #12 0x00007f0a71309aa8 in io_loop_run (ioloop=0x16df700) at ioloop.c:406 No locals. ---Type <return> to continue, or q <return> to quit--- #13 0x00007f0a712bf1e3 in master_service_run (service=0x16df590, callback=callback@entry=0x41ed40 <client_connected>) at master-service.c:560 No locals. #14 0x000000000040bb58 in main (argc=1, argv=0x16df390) at main.c:400 set_roots = {0x426320, 0x0} login_set = {auth_socket_path = 0x16d7040 "\001", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x41ebf0 <login_client_connected>, failure_callback = 0x41e900 <login_client_failed>, request_auth_token = 1} service_flags = <optimized out> storage_service_flags = <optimized out> username = 0x0 c = <optimized out> (gdb) quit root@mail:/var/core# dovecot -n # 2.2.4 (620876853f6f): /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.1 ext4 auth_cache_negative_ttl = 10 secs auth_cache_size = 10 M auth_cache_ttl = 2 mins auth_master_user_separator = * auth_mechanisms = plain login auth_worker_max_count = 4096 base_dir = /var/run/dovecot/ default_client_limit = 8192 default_process_limit = 2048 default_vsz_limit = 2 G dict { expire = pgsql:/etc/dovecot/dovecot-dict-expire.conf metadata = file:/var/lib/dovecot/shared-metadata } first_valid_gid = 8 first_valid_uid = 8 info_log_path = /var/log/dovecot/dovecot.log last_valid_gid = 8 last_valid_uid = 8 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = *, [::] log_path = /var/log/dovecot/dovecot-errors.log log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = Welcome to IMAP server. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c login_trusted_networks = 127.0.0.1 mail_gid = mail mail_location = maildir:/var/mail/%d/%n:LAYOUT=fs:INBOX=/var/mail/%d/%n/maildirfolder:DIRNAME=maildirfolder:INDEX=/var/mail/indexes/%d/%n mail_max_userip_connections = 1024 mail_plugins = virtual expire metadata mail_privileged_group = mail mail_uid = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace { hidden = no inbox = yes list = yes location = maildir:/var/mail/%d/%n:LAYOUT=fs:INBOX=/var/mail/%d/%n/maildirfolder:DIRNAME=maildirfolder:INDEX=/var/mail/indexes/%d/%n:UTF-8 mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / subscriptions = yes type = private } namespace { hidden = no ignore_on_failure = no inbox = no list = yes location = virtual:/etc/dovecot/virtual:CONTROL=/var/mail/controls/%d/%n/Вся почта:INDEX=/var/mail/indexes/%d/%n/Вся почта:UTF-8 mailbox { auto = subscribe special_use = \All } prefix = Вся почта/ separator = / subscriptions = no type = private } passdb { args = /etc/dovecot/dovecot-pgsql-master.conf driver = sql master = yes } passdb { args = /etc/dovecot/dovecot-pgsql.conf driver = sql } plugin { expire = Trash expire2 = Trash/* expire3 = Junk expire_dict = proxy::expire metadata_dict = proxy::metadata sieve = /var/mail/%d/%n/dovecot.sieve sieve_before = /var/lib/dovecot/sieve/ sieve_dir = /var/mail/%d/%n/maildirfolder sieve_max_actions = 32 sieve_max_redirects = 4 sieve_max_script_size = 1M } protocols = imap sieve service auth-worker { client_limit = 4096 process_limit = 2048 process_min_avail = 10 service_count = 0 unix_listener auth-worker { mode = 0600 } vsz_limit = 1 G } service auth { client_limit = 10240 process_min_avail = 1 service_count = 0 unix_listener auth-client { group = mail mode = 0660 user = mail } unix_listener auth-master { group = mail mode = 0664 user = mail } user = dovecot vsz_limit = 1 G } service dict { unix_listener dict { group = mail mode = 0660 user = mail } } service imap-login { chroot = login client_limit = 4096 process_limit = 2048 process_min_avail = 10 service_count = 0 user = dovecot vsz_limit = 1 G } service imap { client_limit = 4096 process_limit = 2048 process_min_avail = 10 service_count = 0 vsz_limit = 1 G } service managesieve-login { chroot = login client_limit = 4096 executable = /usr/lib/dovecot/managesieve-login inet_listener sieve { port = 4190 } process_limit = 2048 process_min_avail = 10 service_count = 0 user = dovecot vsz_limit = 1 G } service managesieve { client_limit = 4096 executable = /usr/lib/dovecot/managesieve process_limit = 2048 process_min_avail = 10 service_count = 0 vsz_limit = 1 G } ssl_cert = </etc/ssl/dovecot/example.ru.ca.crt ssl_cipher_list = ALL:!LOW:!SSLv2 ssl_key = </etc/ssl/dovecot/example.ru.key ssl_parameters_regenerate = 1 hours userdb { args = /etc/dovecot/dovecot-pgsql.conf driver = sql } valid_chroot_dirs = /var/mail/ verbose_proctitle = yes protocol imap { mail_max_userip_connections = 1024 mail_plugins = expire virtual metadata imap_metadata imap_annotatemore } protocol lda { hostname = mail.example.ru info_log_path = /var/log/dovecot/dovecot-local-deliver.log log_path = /var/log/dovecot/dovecot-local-deliver-errors.log mail_plugins = expire sieve virtual postmaster_address = admin(a)example.ru } protocol sieve { managesieve_max_line_length = 65536 } -- Sidlyarenko Sergey https://github.com/lefoyer

1 0

[Dovecot] Ambiguous behavior with prefetch database?
by Axel Luttgens 13 Jul '13

13 Jul '13

Hello, Let's say dovecot.conf contains: mail_uid = dovemailer mail_gid = dovemailer mail_home = /some/path/%n mail_location = mbox:~/mboxes:INBOX=~/mboxes/inbox and that the password database query is of the form: password_query = \ SELECT \ passwd AS password, \ nickname AS user, \ mail_home AS userdb_home, \ mail_location AS userdb_mail, \ WHERE \ ... The database initially comes with NULL for both mail_home and mail_location, the goal being to be able to progressively replace legacy settings. With the above, one gets such entries in the logs upon a pop or imap connection: auth-worker(11262): Debug: auth(u12345678,127.0.0.1): username changed u12345678 -> john.doe auth: Debug: auth(u12345678,127.0.0.1,<dsNsasbgRQB/AAAB>): username changed u12345678 -> john.doe [...] auth: Debug: prefetch(john.doe,127.0.0.1,<dsNsasbgRQB/AAAB>): passdb didn't return userdb entries, trying the next userdb and, of course, the userdb_query fails since it isn't supposed to be invoked under such circumstances. Of course, the userdb_query could be adapted so as to handle pop/imap connections in addition to say, lmtp or doveadm connections, but this would anyway raise the question: why bother with a prefetch database setup? In fact, it seems that the problem comes from the fact that the password_query returns NULL values (i.e. "do not override dovecot.conf settings") for all userdb_xxx settings even if, technically speaking, it returns such columns. A slight yet somewhat silly modification of the password_query, such as this one: password_query = \ SELECT \ passwd AS password, \ nickname AS user, \ 'dovemailer' AS userdb_uid, \ mail_home AS userdb_home, \ mail_location AS userdb_mail, \ WHERE \ ... indeed seems to bring back all the expected behavior: now, the "passdb returns userdb entries" and, for example, the config's mail_home expands to the expected value /some/path/john.doe. Could it be that the case "userdb_xxx columns returned, even if all with NULL values" has been somehow overlooked in the code? Or am I erring with my interpetation of all those matters? TIA, Axel

2 5

[Dovecot] A sqlite-based quota dict
by Axel Luttgens 13 Jul '13

13 Jul '13

Hello, While experimenting with the sqlite backend, I noticed a big vacuum wrt its use for a quota dict. This is thus an opportunity to share a solution I managed to devise after some trials and errors and a (very quick and unscientific) look at the code. And also the opportunity to ask the community to check for possible flaws. Yes, nothing comes for free... ;-) TIA, Axel This is the SQL for creating the database or for adding needed table/trigger to an existing database (with many comments and few "active" lines): CREATE TABLE quota ( -- We will assume that, in the case of a sqlite DB (and probably a pgsql DB -- as well), Dovecot will *always* act along these lines: -- In case of a "row creation": -- INSERT INTO quota (subject, byte_count) -- VALUES (<some id>, <byte count>); -- INSERT INTO quota (subject, message_count) -- VALUES (<some id>, <msg count>); -- In case of a recalculation: -- UPDATE quota -- SET byte_count = byte_count + <byte count diff>, -- message_count = message_count + <msg count diff> -- WHERE subject = <some id>; -- In case of a row deletion: -- DELETE FROM quota -- WHERE subject = <some id>; -- For example, a "doveadm quota recalc" may first delete the relevant row -- if it exists, then (re-)create it. -- Clearly, the "row creation" case is a bit problematic, hence the need for -- a trigger. -- An id for the entity subjected to a quota (a user/mailbox, a domain...). subject TEXT PRIMARY KEY NOT NULL, -- The entity's size, expressed as a storage space use and as a message -- count. -- Note the NULL defaults: they allow to simplify the trigger's logics. byte_count INTEGER DEFAULT NULL, message_count INTEGER DEFAULT NULL ); CREATE TRIGGER quota_insert BEFORE INSERT ON quota FOR EACH ROW BEGIN -- If there's a row to update, that's because the first INSERT of the "row -- creation" has been performed. -- (this UPDATE could probably be simplified if the insertion order, -- byte_count then message_count, was guaranteed; anyway, since the "row -- creation" operation shouldn't be very frequent, we may afford a slight -- inefficiency). UPDATE quota SET byte_count = CASE WHEN NEW.byte_count ISNULL THEN byte_count ELSE NEW.byte_count END, message_count = CASE WHEN NEW.message_count ISNULL THEN message_count ELSE NEW.message_count END WHERE subject = NEW.subject; -- In which case we may ignore that second (current) INSERT, since the -- previously inserted row has just been updated with the value coming -- from the current INSERT statement. SELECT raise(IGNORE) WHERE EXISTS (SELECT * FROM quota WHERE subject = NEW.subject); END; The corresponding dict configuration being thus supposed to be similar to this one: connect = /path/to/database map { pattern = priv/quota/storage table = quota username_field = subject value_field = byte_count } map { pattern = priv/quota/messages table = quota username_field = subject value_field = message_count }

1 0

[Dovecot] Dovecot Virtual Folders... could these be managed by a/the Client?
by Charles Marcus 12 Jul '13

12 Jul '13

Hi all/Timo, I was thinking about Thunderbirds ability to create Virtual folders allowing you to have many different views of your messages... The downside though, is you only see these in Thunderbird. I know that dovecot supports server side virtual folders: http://wiki2.dovecot.org/Plugins/Virtual But I'm wondering about the possibility to manage these from the client side... For example, would it be possible to create an extension in Thunderbird that allowed the user to manage these (create, edit the filters for, delete, rename, etc)? Thanks, -- Best regards, Charles

2 1

[Dovecot] (no subject)
by Gab IIpop 12 Jul '13

12 Jul '13

>From the documentation, virtual users seem like a good idea if you plan on having a lot of users. Although I'm wondering about the following: What other benefits/consequences are there to using virtual over system users and vice versa? Will virtual users have the same protection as system users (system users would use linux permissions, which is pretty secure)? How easy will it be to switch from using system users to virtual users or vice versa?

2 1

[Dovecot] avoid log message when using nagios check
by lluis 12 Jul '13

12 Jul '13

Hello, I'm using a nagios check to monitor dovecot status, since dovecot v2 I see those syslog messages on every nagios check: pop3-login: Aborted login (no auth attempts in 0 secs) imap-login: Aborted login (no auth attempts in 0 secs) I tried to avoid those messages sending a logout string: check_imap -H localhost -e 'OK' -s 'a logout' check_pop -H localhost -e 'OK' -s 'quit' but now I get imap-login: Disconnected (no auth attempts in 0 secs) pop3-login: Disconnected (no auth attempts in 0 secs) what can I do to avoid a log message on every nagios check? thanks! Lluís

6 12

[Dovecot] getting quota error when accessing private namespace
by Andreas Oster 12 Jul '13

12 Jul '13

Hi all, I have run into a problem which I cannot find a solution for. I have created an additional private namespace with the following commands in dovecot.conf : namespace { disabled = no hidden = no ignore_on_failure = no inbox = no list = children location = maildir:/var/vmail/archives/%Ln/Maildir mailbox "archived mails" { auto = subscribe driver = special_use = \Archive } prefix = Archives/ separator = / subscriptions = yes type = private } plugin { quota = maildir:User quota:ns= quota2 = maildir:Archives quota:ns=Archives/ quota2_rule = *:storage=5G quota_rule = *:storage=1G quota_rule2 = Trash:storage=+200M } I can access the new namespace without any problems but every time a folder in this namespace is accessed, I get the following error messages in mail.err log: dovecot: imap(testuser): Error: quota: Unknown namespace: Archives/ dovecot: last message repeated 49 times Quota seems to work, though I have the feeling, that it only will be updated when closing and reopening the mail client, but this can also be a client issue. Quota for the INBOX is either taken from LDAP or, if there is no value defined in LDAP, will be assigned a quota of 1G The Archives/ namespace has a static quota of 5G for every user. Does anyone have idea how to get rid of these error messages ? Thank you for your kind help Andreas

2 5

[Dovecot] Multiple Folders Continually Auto-Created
by Cassidy Larson 12 Jul '13

12 Jul '13

I've had reports of a number of clients running Outlook 2011 on Mac where they have quite a few folders with the same name appended by multiple "1"s. So far I've only narrowed it down to Outlook 2011 on Mac. We've been in the process of migrating to sdbox on a new server from maildir using dsync backup. Example folder structure: INBOX INBOX 1 INBOX 1 1 INBOX 1 1 1 INBOX 1 1 1 1 INBOX 1 1 1 1 1 INBOX 1 1 1 1 1 1 INBOX 1 1 1 1 1 1 1 INBOX 1 1 1 1 1 1 1 1 INBOX 1 1 1 1 1 1 1 1 1 INBOX 1 1 1 1 1 1 1 1 1 1 Junk Junk 1 Junk 1 1 Junk 1 1 1 Junk 1 1 1 1 Junk 1 1 1 1 1 Junk 1 1 1 1 1 1 Junk 1 1 1 1 1 1 1 Junk 1 1 1 1 1 1 1 1 and so on for "Sent Messages", etc. Seems that the the default folders for these clients are getting created over and over again, each time with a new "1" at the end. Anybody else see this? I'm digging for a client I can troubleshoot with and reproduce with me watching. Thanks, -c

2 2

[Dovecot] SSL cert problem
by Peter von Nostrand 12 Jul '13

12 Jul '13

Hi, I'm running a new dovecot 2.0.9 under Centos 6.4. I'm having an issue with SSL certificate not being accepted by the email client. I have my own CA and I have generated certificates for web usage without a problem. For imaps and pop3s what I did was generate a certificate for the hostname of my dovecot server and then cat that cert with the intermediate and root CA certificates. No matter what thunderbird still complains with Unknown identity. # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-358.2.1.el6.x86_64 x86_64 CentOS release 6.4 (Final) auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-userdb auth_username_format = %n disable_plaintext_auth = no log_path = /var/log/dovecot.log mail_fsync = never mail_home = /vmail/%u mail_location = maildir:~/Maildir mail_plugins = quota managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date mbox_write_locks = fcntl passdb { driver = pam } plugin { quota = maildir:User quota quota_rule = *:storage=1G quota_rule2 = Trash:storage=+100M sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 lmtp sieve quota_full_tempfail = yes service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service lmtp { unix_listener lmtp { user = vmail } } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } ssl_cert = </etc/pki/dovecot/certs/mail.pem ssl_key = </etc/pki/dovecot/private/mail.example.com.key userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } verbose_ssl = yes protocol lmtp { mail_fsync = optimized mail_plugins = sieve quota } protocol lda { mail_plugins = sieve quota } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota This is the log: Jul 11 15:38:45 imap-login: Warning: SSL: where=0x10, ret=1: before/accept initialization [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL: where=0x2001, ret=1: before/accept initialization [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL: where=0x2002, ret=-1: SSLv2/v3 read client hello A [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 read client hello A [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write server hello A [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write certificate A [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write key exchange A [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write server done A [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 flush data [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL: where=0x2002, ret=-1: SSLv3 read client certificate A [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL: where=0x2002, ret=-1: SSLv3 read client certificate A [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 read client key exchange A [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 read finished A [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write session ticket A [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write change cipher spec A [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write finished A [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 flush data [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL: where=0x20, ret=1: SSL negotiation finished successfully [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL: where=0x2002, ret=1: SSL negotiation finished successfully [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL alert: where=0x4004, ret=558: fatal certificate unknown [192.168.0.1] Jul 11 15:38:45 imap-login: Warning: SSL alert: where=0x4008, ret=256: warning close notify [192.168.0.1] Jul 11 15:38:45 imap-login: Info: Disconnected (no auth attempts): rip=192.168.0.1, lip=192.168.1.1, TLS: SSL_read() failed: error:14094416:SSL routines:SSL3_READ_BYTES:sslv3 alert certificate unknown: SSL alert number 46 Thx in advance -- Peter

4 3

[Dovecot] dsync/imapc migration question
by Gedalya 12 Jul '13

12 Jul '13

Doing an imapc migration with the pop3 migration plugin, using doveadm backup -R. I occasionally get the following output: dsync(user(a)domain.tld): Error: imapc(mail01.domain.tld:143): Server disconnected unexpectedly dsync(user(a)domain.tld): Error: imapc(mail01.domain.tld:143): Server disconnected unexpectedly dsync(user(a)domain.tld): Error: imapc(mail01.domain.tld:143): Server disconnected unexpectedly dsync(user(a)domain.tld): Warning: I/O leak: 0xb7648650 (line 1229, fd 10) dsync(user(a)domain.tld): Warning: I/O leak: 0xb7648650 (line 1229, fd 11) dsync(user(a)domain.tld): Warning: Timeout leak: 0xb76488b0 (line 1316) dsync(user(a)domain.tld): Warning: Timeout leak: 0xb76488b0 (line 1316) The source server is really crappy, no need to look at the dovecot side for causes. My question is: is it possible that the migration did complete successfully? Dovecot does seem to continue and it's kind of vague on what went wrong, and did it re-try. This operation can take several hours on large mailboxes so this question is really meaningful in my case. (I'd try with -D but it's really hard to reproduce this on demand). Thanks Gedalya

2 3

Re: [Dovecot] SSL cert problem
by Reindl Harald 11 Jul '13

11 Jul '13

Am 11.07.2013 21:51, schrieb Peter von Nostrand: > On Thu, Jul 11, 2013 at 4:23 PM, Reindl Harald > because thunderbird does not trust your own CA by default > without import it there by hand - you can not expect to > cat your CA to the cert for the server and that is enough > to get truested by the client - if so everybody would do > this to make his DNS forgery successful > > Sorry, I should specify that I already have my root CA certificates loaded in thunderbird much more important you should reply this to the list and not off-list, fixed by me, no need to send it again

1 0

[Dovecot] Pigeonhole vacation auto-response not respecting "days" parameter
by Thomas Harold 11 Jul '13

11 Jul '13

This might be a PEBKAC on my end, but in our old server, "vacation" responses would only be sent back to an origin address once per day because we had ":days 1" in the rule. On the new server, even though we have ":days 1", pigeonhole is sending responses to every message, resulting in multiple vacation responses each day back to each origin address. The following was generated by Roundcube's web interface, it looks to be correct. ----------------------- require ["vacation"]; # rule:[vacation-reply] if allof (not header :contains "Subject" "[spam]", not exists "List-Unsubscribe") { vacation :days 1 :addresses ["email1(a)example.com","email2(a)example.com"] :subject "Out of office reply" text: I am currently out of the office July 11th and 12th, returning on July 15th. During this time I will have no access to email. Thank you. User So-And-So . ; } ----------------------- Interestingly, if I look at .dovecot.sieve.log, I see error messages like (except that the vacation responses are, in reality, being sent): error: msgid=<20130711134816.35B9A40335(a)mail.example.com>: failed to send vacation response to <originemail(a)example.com> (refer to server log for more information). And in the maillog: Jul 11 09:48:17 servername sendmail[28244]: r6BDmHem028244: SYSERR(UID1132): Who are you? Jul 11 09:48:17 servername sendmail[28244]: r6BDmHem028244: Authentication-Warning: servername .example.com: Unknown UID 1132 set sender to <> using -f Jul 11 09:48:17 servername sendmail[28244]: r6BDmHem028244: from=<>, size=725, class=-60, nrcpts=1, msgid=<dovecot-sieve-1373550497-202242-0(a)servername.example.com>, relay=Unknown UID 1132@localhost My guess at this point is that I've failed to configure pigeonhole and/or postfix's copy of the sendmail command properly so that it can create the "who I have send mail to recently" file.

1 0

[Dovecot] Fault in dovecot 2.1.17
by Adrian Stoica 11 Jul '13

11 Jul '13

The system hang, linux from scratch. I have changed the live kernel from linux-2.6.35.4 to linux-2.6.32.61 , to see if the fault still occurs. The kernel 2.6.35.4 was working fine with all version up to dovecot 2.1.12 , from which i made update to 2.1.17. dovecot -n # 2.1.17: /usr/dovecot21/etc/dovecot/dovecot.conf # OS: Linux 2.6.32.61 i686 auth_cache_negative_ttl = 1 secs auth_cache_size = 2 M auth_failure_delay = 4 secs auth_mechanisms = plain login digest-md5 cram-md5 auth_worker_max_count = 100 base_dir = /var/run/dovecot/ default_client_limit = 4096 default_internal_user = vmail default_login_user = nobody default_process_limit = 256 deliver_log_format = mail delivery from=%f subject=%s msgid=%m: %$ dict { acl = mysql:/usr/dovecot21/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no first_valid_uid = 1 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = * mail_location = maildir:~/Maildir mail_plugins = " quota acl trash notify mail_log" managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace { hidden = no list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes list = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / subscriptions = yes type = private } passdb { args = /usr/dovecot21/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_defaults_from_inbox = yes acl_shared_dict = proxy::acl autocreate = Trash autocreate2 = Drafts autocreate3 = Sent autosubscribe = Trash autosubscribe2 = Drafts autosubscribe3 = INBOX autosubscribe4 = Sent mail_log_events = delete mailbox_delete mailbox_rename mail_log_fields = box subject from msgid size quota = maildir:User quota quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=95%% quota-warning 90 %u quota_warning3 = storage=85%% quota-warning 85 %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_max_redirects = 10 trash = /usr/dovecot21/etc/dovecot/dovecot-trash.conf.ext } postmaster_address = postmaster(a)dacris.net protocols = imap quota_full_tempfail = yes rejection_subject = Rejected: %s: %r service auth { unix_listener auth-client { mode = 0666 user = vmail } unix_listener auth-userdb { mode = 0666 user = vmail } } service dict { unix_listener dict { user = vmail } } service imap-login { process_min_avail = 4 } service imap-postlogin { executable = script-login /bin/imap.sh unix_listener imap-postlogin { mode = 01232 } } service imap { executable = imap imap-postlogin process_limit = 1024 vsz_limit = 1 G } service quota-warning { executable = script /bin/quota_warning.sh unix_listener quota-warning { user = vmail } user = vmail } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = /usr/dovecot21/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = " quota acl trash notify mail_log sieve autocreate" } protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 20 mail_plugins = " quota acl trash notify mail_log imap_quota imap_acl" } Log from kernel: Jul 11 10:14:01 mail kernel: BUG: Bad page map in process imap-login pte:c926b025 pmd:4597c067 Jul 11 10:14:01 mail kernel: page:c2f2ed60 count:1 mapcount:-1 mapping:ec5a03a0 index:0x4ab Jul 11 10:14:01 mail kernel: page flags: 0x80020068(uptodate|lru|active|mappedtodisk) Jul 11 10:14:01 mail kernel: addr:b73f4000 vm_flags:08000075 anon_vma:(null) mapping:e289ec88 index:7b Jul 11 10:14:01 mail kernel: vma->vm_ops->fault: filemap_fault+0x0/0x2fa Jul 11 10:14:01 mail kernel: vma->vm_file->f_op->mmap: ext4_file_mmap+0x0/0x39 Jul 11 10:14:01 mail kernel: Pid: 22889, comm: imap-login Not tainted 2.6.35.4 #2 Jul 11 10:14:01 mail kernel: Call Trace: Jul 11 10:14:01 mail kernel: [<c1078901>] ? print_bad_pte+0x13a/0x14b Jul 11 10:14:01 mail kernel: [<c107b206>] ? unmap_vmas+0x33b/0x62d Jul 11 10:14:01 mail kernel: [<c10272cc>] ? try_to_wake_up+0x206/0x210 Jul 11 10:14:01 mail kernel: [<c107ccc7>] ? exit_mmap+0x8c/0x107 Jul 11 10:14:01 mail kernel: [<c102976f>] ? mmput+0x1c/0x8c Jul 11 10:14:01 mail kernel: [<c102c850>] ? exit_mm+0xdc/0xe4 Jul 11 10:14:01 mail kernel: [<c103da3c>] ? hrtimer_try_to_cancel+0x55/0x5b Jul 11 10:14:01 mail kernel: [<c104dd0d>] ? acct_collect+0x77/0x126 Jul 11 10:14:01 mail kernel: [<c102dccb>] ? do_exit+0x1c8/0x5bc Jul 11 10:14:01 mail kernel: [<c109fd4d>] ? mntput_no_expire+0x15/0xad Jul 11 10:14:01 mail kernel: [<c102e119>] ? do_group_exit+0x5a/0x7d Jul 11 10:14:01 mail kernel: [<c102e14d>] ? sys_exit_group+0x11/0x14 Jul 11 10:14:01 mail kernel: [<c100254c>] ? sysenter_do_call+0x12/0x22 Jul 11 10:14:01 mail kernel: Disabling lock debugging due to kernel taint Jul 11 10:14:01 mail kernel: BUG: Bad page state in process imap-login pfn:c926b Jul 11 10:14:01 mail kernel: page:c2f2ed60 count:0 mapcount:-1 mapping:ec5a03a0 index:0x4ab Jul 11 10:14:01 mail kernel: page flags: 0x80020008(uptodate|mappedtodisk) Jul 11 10:14:01 mail kernel: Pid: 22889, comm: imap-login Tainted: G B 2.6.35.4 #2 Jul 11 10:14:01 mail kernel: Call Trace: Jul 11 10:14:01 mail kernel: [<c106c916>] ? bad_page+0x9c/0xae Jul 11 10:14:01 mail kernel: [<c106d4dc>] ? free_pages_prepare+0x55/0xc5 Jul 11 10:14:01 mail kernel: [<c106d5f0>] ? free_hot_cold_page+0x20/0xef Jul 11 10:14:01 mail kernel: [<c106d739>] ? __pagevec_free+0x1a/0x21 Jul 11 10:14:01 mail kernel: [<c106fb3a>] ? release_pages+0x165/0x16d Jul 11 10:14:01 mail kernel: [<c1083302>] ? free_pages_and_swap_cache+0x68/0x74 Jul 11 10:14:01 mail kernel: [<c107b251>] ? unmap_vmas+0x386/0x62d Jul 11 10:14:01 mail kernel: [<c10272cc>] ? try_to_wake_up+0x206/0x210 Jul 11 10:14:01 mail kernel: [<c107ccc7>] ? exit_mmap+0x8c/0x107 Jul 11 10:14:01 mail kernel: [<c102976f>] ? mmput+0x1c/0x8c Jul 11 10:14:01 mail kernel: [<c102c850>] ? exit_mm+0xdc/0xe4 Jul 11 10:14:01 mail kernel: [<c103da3c>] ? hrtimer_try_to_cancel+0x55/0x5b Jul 11 10:14:01 mail kernel: [<c104dd0d>] ? acct_collect+0x77/0x126 Jul 11 10:14:01 mail kernel: [<c102dccb>] ? do_exit+0x1c8/0x5bc Jul 11 10:14:01 mail kernel: [<c109fd4d>] ? mntput_no_expire+0x15/0xad Jul 11 10:14:01 mail kernel: [<c102e119>] ? do_group_exit+0x5a/0x7d Jul 11 10:14:01 mail kernel: [<c102e14d>] ? sys_exit_group+0x11/0x14 Jul 11 10:14:01 mail kernel: [<c100254c>] ? sysenter_do_call+0x12/0x22

3 2

[Dovecot] Dovecot 2.2.4 : Panic: file pop3-client.c: line 585 (client_default_destroy): assertion failed: (client->cmd == NULL)
by Ken A 11 Jul '13

11 Jul '13

This doesn't seem to affect clients, but I'm seeing an occasional pop3 error in the log over the last week. Any ideas what is causing this? Thanks, Ken > Jul 4 15:04:03 mail dovecot: POP3(user)x.x.x.x: Connection > closed top=0/0, retr=0/0, del=0/4582, size=246709805 > Jul 4 15:04:03 mail dovecot: POP3(user)x.x.x.x: Panic: file > pop3-client.c: line 585 (client_default_destroy): assertion failed: > (client->cmd == NULL) > Jul 4 15:04:03 mail dovecot: POP3(user)x.x.x.x: Error: Raw > backtrace: /usr/lib/dovecot/libdovecot.so.0() [0x31b4c6074a] -> > /usr/lib/dovecot/libdovecot.so.0() [0x31b4c60796] -> > /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x31b4c202df] -> > dovecot/pop3() [0x404df9] -> dovecot/pop3(client_handle_input+0xd4) > [0x4051b4] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) > [0x31b4c6f6d6] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xa7) > [0x31b4c70737] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) > [0x31b4c6f678] -> > /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) > [0x31b4c24fa3] -> dovecot/pop3(main+0x257) [0x4043d7] -> > /lib64/libc.so.6(__libc_start_main+0xfd) [0x3a08e1ecdd] -> > dovecot/pop3() [0x403f29] > Jul 4 15:04:04 mail dovecot: POP3(user)x.x.x.x: Fatal: master: > service(pop3): child 9080 killed with signal 6 (core dumped) -- Ken Anderson Pacific Internet - http://www.pacific.net

2 2

[Dovecot] How to manipulate attachments with LDA?
by Piotr Szafarczyk - NetExpert 10 Jul '13

10 Jul '13

Hi All, I want to plug in a tool that will convert attachments somewhere into a mail delivery process (postfix->dovecot). I think deliver would be a good place to do it. Does it make sense? Could you direct me where I could read about how to do it please? Piotr Szafarczyk

2 4

[Dovecot] Crashes with 2.2.4 setup that worked perfectly with 2.2.2 (.2.3 also crashes)
by Trever L. Adams 10 Jul '13

10 Jul '13

I am not sure how to get the symbols necessary, however the following is the backtrace (this is Fedora 19 latest everything): Jul 8 03:23:02 MX dovecot: auth: Fatal: block_alloc(2147483648): Out of memory Jul 8 03:23:02 MX dovecot: auth: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x5f437) [0x7f97a952f437] -> /usr/lib64/dovecot/libdovecot.so.0(+0x5f4fe) [0x7f97a952f4fe] -> /usr/lib64/dovecot/libdovecot.so.0(i_error+0) [0x7f97a94f070f] -> /usr/lib64/dovecot/libdovecot.so.0(+0x72ee8) [0x7f97a9542ee8] -> /usr/lib64/dovecot/libdovecot.so.0(+0x72f1f) [0x7f97a9542f1f] -> /usr/lib64/dovecot/libdovecot.so.0(sasl_client_new+0x31) [0x7f97a9526ac1] -> /lib64/libldap-2.4.so.2(ldap_int_sasl_open+0x5c) [0x7f97a62f058c] -> /lib64/libldap-2.4.so.2(ldap_int_sasl_bind+0x5c9) [0x7f97a62f0cd9] -> /lib64/libldap-2.4.so.2(ldap_sasl_interactive_bind+0x96) [0x7f97a62f3e46] -> /lib64/libldap-2.4.so.2(ldap_sasl_interactive_bind_s+0xe1) [0x7f97a62f4041] -> /usr/lib64/dovecot/auth/libauthdb_ldap.so(db_ldap_connect+0x146) [0x7f97a652f286] -> dovecot/auth(userdb_init+0x1a) [0x7f97a99e09ea] -> dovecot/auth(auths_init+0xc9) [0x7f97a99c8e29] -> dovecot/auth(main+0x335) [0x7f97a99c8225] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f97a8ae8b75] -> dovecot/auth(+0xe43d) [0x7f97a99c843d] Jul 8 03:23:02 MX dovecot: master: Error: service(auth): command startup failed, throttling for 60 secs Jul 8 03:23:02 MX dovecot: auth: Fatal: master: service(auth): child 9650 returned error 83 (Out of memory (service auth { vsz_limit=256 MB }, you may need to increase it)) Any help would be greatly appreciated. Thank you, Trever

4 10

[Dovecot] Have an issue with catch-all - Dovecot-lda andPostfix
by Joakim Ohlsson 10 Jul '13

10 Jul '13

Hi, I run dovecot version 2.1.7 and postfix 2.9.6. I'm using dovecot-lda as local delivery. I use virtual users and need to use catch-all for some of my domains. My problem when using catch-all is that I got a separate email for each recipient. As an example: If I send mail to: test1(a)test.org, test2, test3(a)test.org, test4(a)test.org and have a catch-all which will send this mail to test(a)test.org. In this example I get 4 mails in my test(a)test.org inbox and in TO: field in the header I have all this four recipients: TO: test1(a)test.org, test2, test3(a)test.org, test4(a)test.org. In my dovecot log: 2013-07-10 13:49:25 lda(test(a)test.org): Debug: Destination address: test(a)test.org (source: user@hostname) 2013-07-10 13:49:25 lda(test(a)test.org: Info: msgid=<20130710114924.DBA3F9FA8D(a)mail2.test.org>: saved mail to INBOX 2013-07-10 13:49:25 lda(test(a)test.org): Info: msgid=<20130710114924.DBA3F9FA8D(a)mail2.test.org>: saved mail to INBOX 2013-07-10 13:49:25 lda(test(a)test.org): Info: msgid=<20130710114924.DBA3F9FA8D(a)mail2.test.org>: saved mail to INBOX 2013-07-10 13:49:25 lda(test(a)test.org): Info: msgid=<20130710114924.DBA3F9FA8D(a)mail2.test.org>: saved mail to INBOX My question is if it's possible to receive just one mail instead of four? If I send the mail via Spamassassin I'll just receive one mail to test(a)test.org with TO: test1(a)test.org, test2, test3(a)test.org, test4(a)test.org in the header. Thanks in advance Br Joakim # dovecot -n:

3 2