- dovecot - dovecot.org

Re: Problem with permissions of the logfile
by Andreas Meyer 06 Nov '15

06 Nov '15

Hello! To stay on the list. "S. Muthu Kumar" <ksmutthu(a)gmail.com> schrieb am 06.11.15 um 21:49:32 Uhr: > log_path here means the logging channel path. It refers to the logger > daemon to use to generate logs. > > Most of the linux/unix based applications prefer to use common system > logger to take care of writing the logs preferably under /var/log/ as > there are other structures(like rotating those logs periodically). > > do refer to man pages of syslog.conf or rsyslog.conf and see how you > can generate individual log files for devecot via (r)syslog daemon > while you have delegated dovecot logging responsibility to (r)syslog. I must admit I don't understand what is going on. I am running rsyslog on two servers and on both servers version 2.2.13 of dovecot. On the first I set log_path = /var/log/dovecot1 with -rw------- 1 root root 1093533 6. Nov 17:24 dovecot1 in /var/log and everthing is fine. If I do this on the newly set up server, dovecot does not start. Ofcourse I could set it up to log to syslog and prepare rsyslog.conf but why is it so? Regards Andreas

1 0

Problem with permissions of the logfile
by Andreas Meyer 06 Nov '15

06 Nov '15

Hello! I want to have dovecot log into a separate file and set log_path = /var/log/dovecot instead of log_path = syslog Dovecot does not start if I do this. Tried to change permissions and overschip of the file, no luck, ha. Deleted it in the hope dovecot creates it but no. If I set log_path = syslog dovecot starts and I see it is running as # ps aux |grep dove root 2429 0.2 0.0 3416 2568 ? Ss 16:42 0:00 /usr/sbin/dovecot -F dovecot 2431 0.0 0.0 3100 2080 ? S 16:42 0:00 dovecot/anvil root 2432 0.0 0.0 3228 2316 ? S 16:42 0:00 dovecot/log root 2434 0.0 0.0 4220 3300 ? S 16:42 0:00 dovecot/config What must be done to have doveot log into the specified file? Greetings Andreas

1 0

Patch for Dovecot 2.2.19 compilation failure
by Hammer, Adam 06 Nov '15

06 Nov '15

I’m almost embarrassed to submit the following patch. ==== cut here ==== --- dovecot-2.2.19/src/lib/bits.h.orig Thu Mar 19 08:42:32 2015 +++ dovecot-2.2.19/src/lib/bits.h Thu Nov 5 15:10:35 2015 @@ -10,7 +10,9 @@ #include <limits.h> #include <stddef.h> -#include <stdint.h> +#ifdef HAVE_STDINT_H +# include <stdint.h> +#endif #define UINT64_SUM_OVERFLOWS(a, b) \ (a > (uint64_t)-1 - b)

2 1

replication delays
by djk 05 Nov '15

05 Nov '15

I have two dovecot instances that replicate to each other. Mail arrives into "post" and it is generally accessed via IMAP on "france". Changes (moves/expunge etc) on "france" seem to replicate back to "post" more or less immediately. But this seems to happen only for this user. (Some) other users' (e.g. me) mail generally replicates more or less immediately in both directions. Nov 5 17:40:55 post dovecot: lmtp(willem@xxx): xF9mK6eUO1YsFQAAdYyp2A: sieve: msgid=<20151105173923.14970.95605@ssa-app-xxx>: stored mail into mailbox 'SSA' Nov 5 17:41:00 post dovecot: lmtp(willem@xxx): yV9mK6eUO1YsFQAAdYyp2A: sieve: msgid=<20151105173924.14970.91073@ssa-app-xxx>: stored mail into mailbox 'SSA' Nov 5 20:39:09 france dovecot: dsync-server(willem): save: box=SSA, uid=3130, msgid=<20151105173923.14970.95605@ssa-app-xxx>, size=9724 Nov 5 20:39:09 france dovecot: dsync-server(willem): save: box=SSA, uid=3131, msgid=<20151105173924.14970.91073@ssa-app-xxx>, size=9197 Any suggestions as to where to start looking? As you can see I am using 2.2.18 with mdbox and a simple all vmail based system with not many users. I am not seeing any error messages in my mail logs that suggest there any delays happening. Although I have seen a few things like this happening from time to time a busier account: Nov 5 12:12:07 france dovecot: dsync-server(djk): Error: Couldn't lock /home/imap/djk/.dovecot-sync.lock: Timed out after 30 seconds Nov 5 12:12:13 france dovecot: dsync-server(djk(a)tobit.co.uk): Error: Couldn't lock /home/imap/djk/.dovecot-sync.lock: Timed out after 30 seconds Nov 5 12:16:49 france dovecot: dsync-server(djk): Error: Couldn't lock /home/imap/djk/.dovecot-sync.lock: Timed out after 30 seconds root@france:/var/log# dovecot -n # 2.2.18: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (0c4ae064f307+) # OS: Linux 3.13.0-66-generic x86_64 Ubuntu 14.04.3 LTS auth_verbose = yes doveadm_password = <some secret string or other> first_valid_uid = 2000 imapc_features = rfc822.size fetch-headers imapc_host = <imap hostname> imapc_port = 993 imapc_ssl = imaps imapc_ssl_verify = no imapc_user = %n lda_mailbox_autocreate = yes login_greeting = IMAP ready. mail_attachment_dir = %h/attachments mail_attachment_min_size = 64 k mail_location = mdbox:%h:INBOX=%h/mail mail_plugins = " fts fts_lucene mail_log notify notify replication" mail_prefetch_count = 20 mailbox_list_index = yes 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 index ihave duplicate mdbox_rotate_size = 10 M namespace inbox { inbox = 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 = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { fts = lucene fts_lucene = whitespace_chars=@. mail_log_events = delete undelete expunge copy save mailbox_delete mailbox_rename mailbox_create mail_log_fields = uid box msgid size mail_replica = tcps:post:<same port as doveadm port> sieve = file:~/sieve;active=~/.dovecot.sieve } postmaster_address = postmaster(a)tobit.co.uk protocols = " imap lmtp sieve sieve" service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vmail } unix_listener replication-notify { mode = 0666 user = vmail } } service auth { unix_listener exim-auth { group = Debian-exim mode = 0660 user = Debian-exim } } service config { unix_listener config { mode = 0666 user = vmail } } service doveadm { inet_listener { port = <some port or other> ssl = yes } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = <another port> } unix_listener lmtp { mode = 0666 } user = vmail } service managesieve-login { inet_listener sieve { port = <sieve port> } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service managesieve { process_limit = 100 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl_cert = </etc/dovecot/tobit.crt ssl_client_ca_dir = /etc/ssl/certs ssl_key = </etc/dovecot/private/tobit.key ssl_protocols = !SSLv3 !SSLv2 userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = sieve }

1 0

Re: ssl-params: slow startup (patch for consideration)
by Joseph Tam 05 Nov '15

05 Nov '15

A. Schulze writes: > precomputing ssl-params is also possible without patching but it's a > little bit tricky > ... > Long version in german: https://andreasschulze.de/dovecot/ssl-params Nice. (You should probably point out to ensure ssl_parameters_regenerate is zero, otherwise all this work will get wiped out!) Joseph Tam <jtam.home(a)gmail.com>

2 1

Fw: new message
by Doug Wierenga 05 Nov '15

05 Nov '15

Hello! New message, please read <http://battersandco.com/meeting.php?e> Doug Wierenga

1 0

Fw: new message
by terry＠dop.com 05 Nov '15

05 Nov '15

Hello! New message, please read <http://profi2w.com.br/forget.php?80> terry(a)dop.com

1 0

ldap and proxy/proxy_maybe
by jjhoffart 04 Nov '15

04 Nov '15

Hello, I am trying to setup dovecot director and am receiving a lot of "Aborted login (proxy dest auth failed)" and "error proxying loops to itself" messages in the dovecot log. I don't fully understand the dovecot-ldap.conf file config? could someone please let me know if the following is correct. If so what could be causing the errors mentioned above, if not what needs to be corrected? hosts = 127.0.0.1:389 ldap_version = 3 auth_bind = yes dn = cn=vmail,dc=something,dc=somewhere dnpass = hi89Dfnptc55jRWG9oLQJUfWOH0CgV base = o=domains,dc=campus,dc=local scope = subtree deref = never # Below two are required by command 'doveadm mailbox ...' iterate_attrs = mail=user iterate_filter = (&(objectClass=mailUser)(accountStatus=active)(enabledService=mail)) user_filter = (&(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=%Ls%Lc)(|(mail=%u)(&(enabledService=shadowaddress)(shadowAddress=%u)))) user_attrs = mail=user,homeDirectory=home,=mail=maildir:~/Maildir/,mailQuota=quota_rule=*:bytes=%$ # Used for dn lookup pass_filter = (&(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=%Ls%Lc)(|(mail=%u)(&(enabledService=shadowaddress)(shadowAddress=%u)))) pass_attrs = mail=user,userPassword=password,someAttribute=proxy,hostName=host default_pass_scheme = CRYPT

1 0

ssl-params: slow startup (patch for consideration)
by Joseph Tam 04 Nov '15

04 Nov '15

Based on the recent found weaknesses in DH key exchange, http://weakdh.org/ I increased ssl_dh_parameters_length to 2048 bits, and found waited for 5+ minutes for dovecot to come back online after a restart. Unless you got a fast machine, the initialization of DH parameters can exceed your patience. Regeneration may not be a problem (if ssl_parameters_regenerate=0 or if Dovecot uses old parameters until regeneration finishes), but for cold starts, the server can be tied up for a few minutes creating DH parameters while clients queue up. I ran "openssl dhparam 2048" and got wildly varying run times of 1m45s, 11m56s, 0.4s, 2m19s, 3h23s. Most of the time was spent testing primality of candidate p *and* (p-1)/2 -- so called "safe prime". If you're unlucky, this can take a long time. However, it appears "safe" primes are not what they're cracked up to be -- they offer some guarantees, but are not safer than non-safe primes. Creating DH parameters without requiring primality of (p-1)/2 (i.e. what "openssl dhparam -dsaparam" does) results in much lower run-time bounds. I cribbed some OpenSSL code to create this (untested) patch. -------------------------------------------------------------------------------- --- iostream-openssl-params.c~ Tue Nov 3 16:08:38 2015 +++ iostream-openssl-params.c Tue Nov 3 15:43:39 2015 @@ -6,5 +6,2 @@ -/* 2 or 5. Haven't seen their difference explained anywhere, but 2 is the - default.. */ -#define DH_GENERATOR 2 @@ -14,2 +11,3 @@ DH *dh; + DSA *dsa; unsigned char *p; @@ -17,3 +15,13 @@ - dh = DH_generate_parameters(bitsize, DH_GENERATOR, NULL, NULL); + dsa = DSA_generate_parameters(bitsize, NULL, 0, NULL, NULL, NULL, NULL); + if (dsa == NULL) { + *error_r = t_strdup_printf( + "DSA_generate_parameters(bits=%d) failed: %s", + bitsize, openssl_iostream_error()); + return -1; + } + + dh = DSA_dup_DH(dsa); + DSA_free(dsa); + if (dh == NULL) { @@ -20,4 +28,4 @@ *error_r = t_strdup_printf( - "DH_generate_parameters(bits=%d, gen=%d) failed: %s", - bitsize, DH_GENERATOR, openssl_iostream_error()); + "DSA_dup_DH() failed: %s", + openssl_iostream_error()); return -1; -------------------------------------------------------------------------------- The other way to prevent long startup times is to pre-compute the DH parameter using "openssl dhparam -out dh2048.pem 2048". I can contribute a patch to do this (read file, convert it into ssl-parameters.dat, then set/behave like ssl_parameters_regenerate=0), but I couldn't figure out the best place to do this. ssl_params_if_unchanged()? Joseph Tam <jtam.home(a)gmail.com>

2 1

dovecot-lda can't create /var/mail dotlocks on debian
by John Clements 03 Nov '15

03 Nov '15

I've been using dovecot+postfix happily for many years, and I'm now configuring it for a new machine. However, I'm running into an old problem again, and thinking that there must be a better solution. The problem is that dovecot-lda is unable to create dotlock files in the /var/mail directory. Dovecot version: 1:2.2.13-12~deb8u1 (I'm guessing this is upstream version 2.2.13) OS: Debian Jessie Currently, my mail directory has these permissions: clements@desmond:~$ ls -ld /var/mail drwxrwsr-x 2 root mail 4096 Nov 2 22:07 /var/mail clements@desmond:~$ ls -l /var/mail total 8 -rw------- 1 clements mail 1382 Nov 2 21:59 clements -rw------- 1 granitemon mail 530 Nov 2 22:07 granitemon I've added mail_privileged_group = mail to allow creation of the dotlock files. When I configure postfix to deliver using dovecot-lda, I get logs that look like this: Nov 3 11:12:20 desmond dovecot: lda(granitemon): Error: setegid(privileged) failed: Operation not permitted Nov 3 11:12:20 desmond dovecot: lda(granitemon): msgid=< 20151103181306.A4B5B5FF32(a)desmond.XXXDOMAIN.org>: save failed to INBOX: BUG: Unknown internal error In order to isolate the error, I took postfix out of the equation, and called dovecot-lda directly: clements@desmond:/tmp$ cat bogusmail From: clements(a)XXXDOMAIN.org To: granitemon@localhost Date: November 3 2015 Subject: graaaah this is the body clements@desmond:/tmp$ /usr/lib/dovecot/dovecot-lda -e -d clements < bogusmail BUG: Unknown internal error clements@desmond:/tmp$ In response to this, mail.log now contains this similar error: Nov 3 11:34:57 desmond dovecot: lda(clements): msgid=unspecified: save failed to INBOX: BUG: Unknown internal error Nov 3 11:34:57 desmond dovecot: lda(clements): Error: setegid(privileged) failed: Operation not permitted I've tried a number of "random internet search" solutions, including - changing perms on mail files from 660 to 600 - enabling 'mail_access_groups=mail' in 10-mail.conf - adding individual users to the mail group. I guess I'm pretty confident that if dovecot is writing "BUG: Unknown internal error" in the logs, that this is is actually a bug in dovecot. OBresearch: I read through the release notes of 2.2.14 -- 2.2.19 to see if a relevant-looking bug had been fixed, but nothing jumped out at me. OBresearch: searching the dovecot mailing list, I found one *extremely* relevant thread called "Re: [Dovecot] started with dovecot sieve <http://dovecot.markmail.org/message/kgd34wberxuvmrsa?q=setegid>", but there didn't seem to be a solution contained in the thread. Final note: this doesn't appear to be confined to debian jessie: I took a look at my existing installation, and I see that in fact I just went ahead and made /var/mail world-writeable, which seems... sub-optimal. I'm sure I could do that here, too, but I'd certainly rather not. Thanks in advance, and let me know if I've left out relevant crucial information. Best, John Clements

2 7

[dovceot-2.2.19] doveadm fts expand constantly gives Segfault
by Marcin Mirosław 03 Nov '15

03 Nov '15

Hi! When I issue: doveadm fts expand -A body xxx I'm always getting Segfault. I can't find descrption of this command in manual, is it possible to add some information to manual? # gdb -q doveadm Reading symbols from doveadm...Reading symbols from /usr/lib64/debug//usr/bin/doveadm.debug...done. done. (gdb) set args fts expand -A body XXX (gdb) run Starting program: /usr/bin/doveadm fts expand -A body XXX Warning: couldn't activate thread debugging using libthread_db: Cannot find new threads: generic error warning: File "/lib64/libthread_db-1.0.so" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". To enable execution of this file add add-auto-load-safe-path /lib64/libthread_db-1.0.so line to your configuration file "/root/.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "/root/.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: info "(gdb)Auto-loading safe path" warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. Program received signal SIGSEGV, Segmentation fault. 0x00007ffff65a61af in fts_user_get_search_tokenizer (user=<optimized out>) at fts-user.c:248 248 fts-user.c: No such file or directory. (gdb) bt #0 0x00007ffff65a61af in fts_user_get_search_tokenizer (user=<optimized out>) at fts-user.c:248 #1 0x00007ffff65a2f8a in fts_search_arg_expand (backend=0x555555802f10, argp=0x7fffffffdf10, pool=0x5555557e56e0) at fts-search-args.c:108 #2 fts_search_args_expand_tree (backend=backend@entry=0x555555802f10, pool=0x5555557e56e0, argp=argp@entry=0x7fffffffdf10) at fts-search-args.c:171 #3 0x00007ffff65a31a5 in fts_search_args_expand (backend=backend@entry=0x555555802f10, args=0x5555557e5700) at fts-search-args.c:199 #4 0x00007ffff2118b2e in cmd_fts_expand_run (ctx=0x5555557e2f10, user=<optimized out>) at doveadm-fts.c:127 #5 0x000055555557a945 in doveadm_mail_next_user (ctx=0x5555557e2f10, input=<optimized out>, error_r=0x7fffffffe028) at doveadm-mail.c:384 #6 0x000055555557bf53 in doveadm_mail_all_users (wildcard_user=0x0, argv=<optimized out>, ctx=0x5555557e2f10) at doveadm-mail.c:452 #7 doveadm_mail_cmd (argv=<optimized out>, argc=<optimized out>, cmd=<optimized out>) at doveadm-mail.c:621 #8 doveadm_mail_try_run (cmd_name=<optimized out>, argc=4, argv=0x5555557ce3a0) at doveadm-mail.c:710 #9 0x000055555556ba6a in main (argc=5, argv=0x5555557ce398) at doveadm.c:345 (gdb) mail_plugins = acl fts fts_lucene listescape quota notify mail_log stats zlib protocol lmtp { mail_plugins = acl fts fts_lucene listescape quota notify mail_log stats zlib sieve } protocol lda { mail_plugins = quota sieve } protocol imap { mail_max_userip_connections = 25 mail_plugins = acl fts fts_lucene listescape quota notify mail_log stats zlib antispam imap_acl imap_quota imap_stats imap_zlib last_login } protocol pop3 { mail_plugins = acl fts fts_lucene listescape quota notify mail_log stats zlib last_login } Thanks, Marcin

1 0

[dovceot-2.2.19] doveadm fetch with fts_squat returns random results
by Marcin Mirosław 03 Nov '15

03 Nov '15

Hi all! I've got problem with results returned by doveadm fetch. The are random and incorrect. I'll try show you: - trying to fetch emails with both: nonexistent header name and non existent value of header name: -- doveadm fetch -u user@domain uid HEADER X-Sasdasdsendasasdasdasdasaer XXtuxie |grep -c uid 0 - trying to fetch email with: non existent header name and existent value of header (value exists usually in header X-Sender) -- # doveadm fetch -u user@domain uid HEADER X-Sasdasdsendasasdasdasdasaer tuxie |grep -c uid 13743 second search: -- # doveadm fetch -u user@domain uid HEADER X-Sasdasdsendasasdasdasdasaer tuxie |grep -c uid 16639 another search with the same criteria: -- doveadm fetch -u user@domain uid HEADER X-Sasdasdsendasasdasdasdasaer tuxie |grep -c uid 20296 so the number of fetched emails is random and none of them contains such header: -- # doveadm fetch -u user@domain hdr HEADER X-Sasdasdsendasasdasdasdasaer tuxie |grep -c X-Sasdasdsendasasdasdasdasaer 0 - now I'm searching for email with existent header contained existent value: -- # doveadm fetch -u user@domain uid HEADER X-Sender tuxie |grep -c uid 50699 second search: -- # doveadm fetch -u user@domain uid HEADER X-Sender tuxie |grep -c uid 50375 It looks for me that searching is done only for value of header not for both header name with given value. Next I turn off fts_squat in config and now results are correct. If someone uses doevadm expunge with fts_squat should be carefull. I just tried fts_lucene - no problem. Regards, Marcin

1 0

Initialization Failed:
by brian 01 Nov '15

01 Nov '15

Hi dovecotters I am trying to install dovecot on a mail server I am provisioning for myself in AWS. I am following an ArsTechnica guide, and at some stage in the process the author recommends and provides instructions to configure Dovecot (http://arstechnica.com/information-technology/2014/03/taking-e-mail-back-pa…) So, now I have it installed and configured (I believe the way suggested) but when I try to connect via IMAP I am getting an error. If I try : root@ip-10-0-0-244:~# telnet mail.myactualdomain.com 143 Trying 127.0.0.1... Connected to mail.myactualdomain.com. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot (Ubuntu) ready. a1 LOGIN brian(a)myactualdomain.com plaintextpassword * BYE Internal error occurred. Refer to server log for more information. Connection closed by foreign host. root@ip-10-0-0-244:~# If I go to /var/log/syslog I can see the following lines: Oct 31 05:31:06 ip-10-0-0-244 dovecot: imap-login: Login: user=<brian(a)myactualdomain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=16934, secured, session=<oCTO2V8jUwB/AAAB> Oct 31 05:31:06 ip-10-0-0-244 dovecot: imap(brian(a)myactualdomain.com): Error: user brian(a)myactualdomain.com: Initialization failed: Namespace '': Unknown setting: /var/mail/vmail/myactualdomain.com/brian/mail Oct 31 05:31:06 ip-10-0-0-244 dovecot: imap(brian(a)myactualdomain.com): Error: Invalid user settings. Refer to server log for more information. root@ip-10-0-0-244:~# dovecot --version 2.2.9 So, I don't know why it's giving me an error about : Initialization failed: Namespace '': Unknown setting: /var/mail/vmail/myactualdomain.com/brian/mail The location is there, with the permissions with I believe the correct permissions. I'm a bit stuck as to where to even go from here. Any help would be greatly appreciated. Kind Regards Brian root@ip-10-0-0-244:~# dovecot -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-48-generic x86_64 Ubuntu 14.04.2 LTS auth_mechanisms = plain login auth_verbose = yes mail_home = /var/mail/vmail/%d/%n mail_location = maildir:~/Maildir:/var/mail/vmail/%d/%n/mail:LAYOUT=fs 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 inbox { inbox = yes location = 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 = } passdb { args = username_format=%u scheme=ssha512 /etc/dovecot/passwd.db driver = passwd-file } plugin { sieve = ~/.dovecot.sieve sieve_after = /var/mail/vmail/sieve-after sieve_before = /var/mail/vmail/sieve-before sieve_dir = ~/sieve } protocols = imap sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/ssl/private/ssl-chain-mail-myactualdomain.pem ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM ssl_client_ca_dir = /etc/ssl/certs ssl_key = </etc/ssl/private/ssl-key-decrypted-mail-myactualdomain.key userdb { args = uid=5000 gid=5000 home=/var/mail/vmail/%d/%n driver = static } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster(a)myactualdomain.com quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_max_userip_connections = 10 }

2 2

Re: Dovecot, JavaMail, UIDs and Message Numbers
by Filippo Carletti 31 Oct '15

31 Oct '15

We're using dovecot-2.1.16 on CentOS (rpm package from epel repo). Maildir format on ext4. > What exactly do you mean by "Dovecot started reindexing"? Selecting thread sort on the javamail client, the imap process opens all files in the folder and updates the following files on disk: dovecot.index dovecot.index.cache dovecot.index.log dovecot.index.log.2 dovecot.index.thread The folder has around 5000 mails and the operation takes some minutes (hw is not the bottleneck). Selecting thread view on Thunderbird or Roundcube takes less than a second, I can't see the imap process doing anything. > Dovecot's normal indexes or full text search indexes? Normal indexes. > How have you configured everything? What do you need to know in particular? doveconf output? Maildir infos: # time cat cur/* >/dev/null real 0m4.651s user 0m0.045s sys 0m0.141s # ls -f cur/ | wc -l 4170 # du -sh cur 49M cur Things go worse with a bigger maildir. > Does Dovecot log anything (especially any errors/warnings about anything)? No errors or warnings at all. I've enabled the mail_log plugin, but I think it can't log indexing operations. Thank you. -- Ciao, Filippo

1 0

Re: Webmail accessive Dovecot logins
by Joseph Tam 30 Oct '15

30 Oct '15

"A. Schulze" writes: > David Mehler: > >> Second question, in the doveconf -n there's reference to my ssl_cipher >> am I using current tls ciphers that support pfs? > >> ssl_cipher_list = ALL:!LOW:!SSLv3:!SSLv2:!EXP:!aNULL > > some non pfs cipher would be still active. check yourself: > # openssl ciphers -v 'ALL:!LOW:!SSLv3:!SSLv2:!EXP:!aNULL' | grep -v DH You'll want the 'E' variation (ephemeral) of the DH algorithms, and preferably, the ECDHE variety as they are faster and supported on more browsers. The pattern to search for (or exclude) is "DHE" openssl ciphers -v {cipher-specs} | grep DHE If the OP wants preferentially use PFS ciphers (but keep the other ciphers around for very old browsers), maybe something like ssl_cipher_list = ECDH:ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_prefer_server_ciphers = yes > finally you could use the service provided by ssllabs.com to scan your host. I second this recommendation, if you can work out the port issue. Maybe using a ncat | ncat pipe. Joseph Tam <jtam.home(a)gmail.com>

1 0

updating and wsitching repo to yum.dovecot.fi - Unknown protocol: sieve
by Götz Reinicke - IT Koordinator 30 Oct '15

30 Oct '15

Hi, winter is coming and so I start to clean up some left overs of the year. One thing is to use the yum.dovecot.fi repository. After installing the current availabel dovecot and dovecot-ee-pigeonhole package and restarting dovecot I do get the error: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: protocols: Unknown protocol: sieve Is the sieve protocol an extra package? I thought in the 2.2. tree I dont have to do bigger config changes. We run already 2.2.something from city-fan.org and the switch was also the idea of going to the most recent release. Thanks for hints and feedback . Götz -- Götz Reinicke IT-Koordinator Tel. +49 7141 969 82420 E-Mail goetz.reinicke(a)filmakademie.de Filmakademie Baden-Württemberg GmbH Akademiehof 10 71638 Ludwigsburg www.filmakademie.de Eintragung Amtsgericht Stuttgart HRB 205016 Vorsitzender des Aufsichtsrats: Jürgen Walter MdL Staatssekretär im Ministerium für Wissenschaft, Forschung und Kunst Baden-Württemberg Geschäftsführer: Prof. Thomas Schadt

3 5

Webmail accessive Dovecot logins
by David Mehler 30 Oct '15

30 Oct '15

Hello, I've seen this issue before, running a imap/smtp/database server on localhost and adding in a webmail interface, in this case Roundcube. In my maillog I'm seeing accessive Dovecot connections and logouts just from my own transaction of logging in, going to compose a message, sending, and logging out. I'm using Mysql as database backend and was wondering if there was something I could do to cut down on the amount of connections needed? I'm running 2.2.19 on a FreeBSD 10.2 system. I'm not sure what other information to provide, here's the relevant log and a doveconf -n. Second question, in the doveconf -n there's reference to my ssl_cipher am I using current tls ciphers that support pfs? Thanks. Dave. Oct 29 20:51:21 server dovecot: imap-login: Login: user=<xxx>, method=PLAIN, rip=::1, lip=::1, mpid=71405, secured, session=<6Px600cja6cAAAAAAAAAAAAAAAAAAAAB> Oct 29 20:51:21 server dovecot: imap(xxx): Disconnected: Logged out in=82 out=763 Oct 29 20:51:22 server dovecot: imap-login: Login: user=<xxx>, method=PLAIN, rip=::1, lip=::1, mpid=72189, secured, session=<c8eL00cjxXYAAAAAAAAAAAAAAAAAAAAB> Oct 29 20:51:22 server dovecot: imap(xxx): Disconnected: Logged out in=70 out=932 Oct 29 20:51:29 server dovecot: imap-login: Login: user=<xxx>, method=PLAIN, rip=::1, lip=::1, mpid=74281, secured, session=<AQz100cj378AAAAAAAAAAAAAAAAAAAAB> Oct 29 20:51:29 server dovecot: imap-login: Login: user=<xxx>, method=PLAIN, rip=::1, lip=::1, mpid=74927, secured, session=<fH3100cjQ5AAAAAAAAAAAAAAAAAAAAAB> Oct 29 20:51:29 server dovecot: imap(xxx): Disconnected: Logged out in=439 out=1702 Oct 29 20:51:29 server dovecot: imap(xxx): Disconnected: Logged out in=326 out=24327 Oct 29 20:51:45 server dovecot: imap-login: Login: user=<xxx>, method=PLAIN, rip=::1, lip=::1, mpid=75557, secured, session=<3tjm1EcjsjUAAAAAAAAAAAAAAAAAAAAB> Oct 29 20:51:45 server dovecot: imap(xxx): Disconnected: Logged out in=32 out=521 Oct 29 20:51:46 server dovecot: imap-login: Login: user=<xxx>, method=PLAIN, rip=::1, lip=::1, mpid=77051, secured, session=<N6311EcjlbQAAAAAAAAAAAAAAAAAAAAB> Oct 29 20:51:46 server dovecot: imap(xxx): Disconnected: Logged out in=44 out=799 doveconf -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: FreeBSD 10.2-RELEASE amd64 ufs auth_default_realm = domain.com auth_mechanisms = plain login dict { sqlquota = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext } first_valid_gid = 999 first_valid_uid = 999 hostname = xxx(a)domain.com imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags last_valid_gid = 999 last_valid_uid = 999 lmtp_rcpt_check_quota = yes mail_gid = vmail mail_home = /home/vmail/%d/%n/home mail_location = maildir:/home/vmail/%d/%n:LAYOUT=fs mail_plugins = acl quota zlib mail_server_admin = mailto:postmaster@domain.com mail_uid = vmail mailbox_list_index = yes maildir_broken_filename_sizes = yes maildir_empty_new = yes maildir_stat_dirs = yes maildir_very_dirty_syncs = yes 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 index ihave duplicate namespace { list = yes location = maildir:/home/vmail/public:LAYOUT=fs prefix = public/ separator = / subscriptions = yes type = public } namespace inbox { hidden = no inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / subscriptions = yes type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota = dict:User quota::proxy::sqlquota quota_grace = 10%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO sieve_default = /home/vmail/conf.d/domain.com/sieve/default.sieve } postmaster_address = postmaster(a)domain.com protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { mode = 0600 user = vmail } } service dict { unix_listener dict { mode = 0600 user = vmail } } service imap-login { inet_listener imap { address = } inet_listener imaps { ssl = yes } } service lmtp { unix_listener dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { address = 127.0.0.1 port = 12345 } } ssl = required ssl_cert = </etc/ssl/certs/server.crt ssl_cipher_list = ALL:!LOW:!SSLv3:!SSLv2:!EXP:!aNULL ssl_dh_parameters_length = 4096 ssl_key = </etc/ssl/private/server.key ssl_protocols = TLSv1 !SSLv3 !SSLv2 userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = acl quota zlib sieve } protocol lda { mail_plugins = acl quota zlib quota sieve } protocol imap { mail_plugins = acl quota zlib imap_acl imap_quota imap_zlib }

3 2

Dovecot frequently full-text reindexes the whole maildir
by vitalif＠yourcmc.ru 30 Oct '15

30 Oct '15

Hi! I'm using Dovecot 2.2.13 (Debian Jessie package 1:2.2.13-12~deb8u1) on my personal mail server (the address I'm writing from is on this server). I use Maildirs, I have fts + fts_squat enabled, and I have a problem with it for a long time - dovecot seems to not update the index always "incrementally". Yesterday I've finally made a test by telneting to imap port and issuing a search request. Dovecot started to reindex the mailbox. Full reindexing has taken around 15-20 minutes. After reindexing the fulltext searches were fast, just as they should be. And they were fast yesterday even after some new emails arrived. But I've tried to do a new search today and Dovecot started to reindex the whole maildir again! Why is it reindexing the whole maildir again? Could it be related to my anti-spam scripts removing messages from SPAM imap folder? And if yes, how to remove them correctly? -- With best regards, Vitaliy Filippov

2 2

2.2.19 crash
by Toni Mattila 29 Oct '15

29 Oct '15

Hi, I have one user constantly crashing with: Core was generated by `dovecot/imap'. Program terminated with signal 11, Segmentation fault. #0 0x007e5b7c in mailbox_list_notify_next (notify=0x0, rec_r=0xbfee8f00) at mailbox-list-notify.c:28 28 return notify->list->v.notify_next(notify, rec_r); (gdb) bt #0 0x007e5b7c in mailbox_list_notify_next (notify=0x0, rec_r=0xbfee8f00) at mailbox-list-notify.c:28 #1 0x080641f2 in imap_client_notify_ns (notify_ns=0x8859478) at imap-notify.c:248 #2 0x0806476a in imap_client_notify_more (client=<value optimized out>) at imap-notify.c:297 #3 0x080648df in imap_client_notify_newmails (client=0x88555c0) at imap-notify.c:339 #4 0x080699fe in imap_sync_notify_more (ctx=0x8858d70) at imap-sync.c:356 #5 imap_sync_more (ctx=0x8858d70) at imap-sync.c:526 #6 0x08069db2 in cmd_sync_continue (sync_cmd=0x8856008) at imap-sync.c:658 #7 0x0806a206 in cmd_sync_delayed_real (client=0x88555c0) at imap-sync.c:748 #8 cmd_sync_delayed (client=0x88555c0) at imap-sync.c:886 #9 0x007e7c25 in notify_delay_callback (box=0x8864cd0) at mailbox-watch.c:26 #10 0x00caec60 in io_loop_handle_timeouts_real (ioloop=0x883d4a0) at ioloop.c:527 #11 io_loop_handle_timeouts (ioloop=0x883d4a0) at ioloop.c:540 #12 0x00cb0299 in io_loop_handler_run_internal (ioloop=0x883d4a0) at ioloop-epoll.c:193 #13 0x00caea8b in io_loop_handler_run (ioloop=0x883d4a0) at ioloop.c:607 #14 0x00caee08 in io_loop_run (ioloop=0x883d4a0) at ioloop.c:583 #15 0x00c4216d in master_service_run (service=0x883d3d0, callback=0x806a700 <client_connected>) at master-service.c:640 #16 0x0806af22 in main (argc=Cannot access memory at address 0x0 (gdb) f 6 #6 0x08069db2 in cmd_sync_continue (sync_cmd=0x8856008) at imap-sync.c:658 658 if ((ret = imap_sync_more(ctx)) == 0) Best Regards, Toni Mattila

2 3

Acl sql dict error, dict crashes
by Christian Kivalo 29 Oct '15

29 Oct '15

Hi, I configured shared mailboxes and get an error when i use SQL as the acl_shared_dict. It works when i use a file instead. With SQL as the shared_dict, dict crashes. I have enabled sql query logs on the mariadb server, the table user_shares and anyone_shares are queried but there is no insert to the empty tables. The dovecot-acl files are created in the mailbox when i add an acl with doveadm acl add ... doveadm acl debug shows an error: doveadm acl debug -u my(a)example.net shared/other(a)example.net/INBOX doveadm(my(a)example.net): Info: Mailbox 'INBOX' is in namespace 'shared/other(a)example.net/' doveadm(my(a)example.net): Info: Mailbox path: /srv/mail/other(a)example.net/Maildir doveadm(my(a)example.net): Info: Per-user private flags in mailbox: \Seen doveadm(my(a)example.net): Info: User my(a)example.net has rights: lookup read doveadm(my(a)example.net): Info: Mailbox found from dovecot-acl-list doveadm(my(a)example.net): Error: User other(a)example.net not found from ACL shared dict, rebuilding doveadm(my(a)example.net): Error: read(/var/run/dovecot/dict) failed: Connection reset by peer doveadm(my(a)example.net): Error: acl: dict commit failed doveadm(my(a)example.net): Fatal: ACL lookup dict rebuild failed then the dict crashes Oct 29 10:12:13 uschi dovecot: auth: Debug: master in: USER#0111#011my(a)example.net#011service=doveadm Oct 29 10:12:13 uschi dovecot: auth-worker(27393): Debug: sql(my(a)example.net): SELECT CONCAT("/srv/mail/", dir) AS home, CONCAT("maildir:/srv/mail/", dir, "/Maildir:LAYOUT=fs") AS mail, 5000 AS uid, 5000 AS gid FROM virtual_users WHERE email = 'my(a)example.net'; Oct 29 10:12:13 uschi dovecot: auth: Debug: userdb out: USER#0111#011my@example.net#011home=/srv/mail/my@example.net#011mail=maildir:/srv/mail/my@example.net/Maildir:LAYOUT=fs#011uid=5000#011gid=5000 Oct 29 10:12:13 uschi dovecot: auth: Debug: master in: USER#0112#011other(a)example.net#011service=doveadm Oct 29 10:12:13 uschi dovecot: auth-worker(27393): Debug: sql(other(a)example.net): SELECT CONCAT("/srv/mail/", dir) AS home, CONCAT("maildir:/srv/mail/", dir, "/Maildir:LAYOUT=fs") AS mail, 5000 AS uid, 5000 AS gid FROM virtual_users WHERE email = 'other(a)example.net'; Oct 29 10:12:13 uschi dovecot: auth: Debug: userdb out: USER#0112#011other@example.net#011home=/srv/mail/other@example.net#011mail=maildir:/srv/mail/other@example.net/Maildir:LAYOUT=fs#011uid=5000#011gid=5000 Oct 29 10:12:13 uschi dovecot: dict(27421): Panic: file dict-sql.c: line 670 (sql_dict_iterate): assertion failed: ((ctx->flags & DICT_ITERATE_FLAG_ASYNC) != 0) Oct 29 10:12:13 uschi dovecot: dict(27421): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x7e290) [0x7f823f032290] -> /usr/lib/dovecot/libdovecot.so.0(+0x7e37c) [0x7f823f03237c] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f823efdd65d] -> dovecot/dict() [0x407e84] -> dovecot/dict() [0x405890] -> dovecot/dict() [0x405b01] -> dovecot/dict(dict_command_input+0xa1) [0x405bd1] -> dovecot/dict() [0x404d96] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7f823f044f7c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe1) [0x7f823f046231] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7f823f045005] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f823f0451a8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f823efe2c23] -> dovecot/dict(main+0x149) [0x404809] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f823e4cdb45] -> dovecot/dict() [0x40488d] Oct 29 10:12:13 uschi dovecot: dict(27421): Fatal: master: service(dict): child 27421 killed with signal 6 (core dumps disabled) The SQL query log from mariadb shows 151029 10:18:06 5318 Connect readuser(a)10.1.1.50 as anonymous on mailserver 5318 Query SELECT CONCAT("/srv/mail/", dir) AS home, CONCAT("maildir:/srv/mail/", dir, "/Maildir:LAYOUT=fs") AS mail, 5000 AS uid, 5000 AS gid FROM virtual_users WHERE email = 'my(a)example.net' 5318 Query SELECT CONCAT("/srv/mail/", dir) AS home, CONCAT("maildir:/srv/mail/", dir, "/Maildir:LAYOUT=fs") AS mail, 5000 AS uid, 5000 AS gid FROM virtual_users WHERE email = 'other(a)example.net' 5319 Connect writeuser(a)10.1.1.50 as anonymous on mailserver 5319 Query SELECT dummy,from_user FROM anyone_shares 5319 Query SELECT dummy,from_user FROM user_shares WHERE to_user = 'my(a)example.net' 5319 Query SELECT dummy,to_user,from_user FROM user_shares 5319 Query SELECT dummy,from_user FROM anyone_shares There is no insert. As far as i can tell everything works as it should with shared folders except that die sql based acl_shared_dict is not updated. The expire dict is properly updated. Is there something i can test? My Thunderbird shows me that the server does not support shareing of mailboxes so i can't share parts of my mailbox to other users. Is this a separate issue or related? doveconf -n # 2.2.19: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: Linux 4.2.1 x86_64 Debian 8.2 ext4 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes default_vsz_limit = 512 M deliver_log_format = msgid=%m, from=%f, envelope from=%{from_envelope}, envelope to=%{to_envelope}, delivery time=%{delivery_time}ms, lmtp session time=%{session_time}ms, status=%$ dict { acl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext expire = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } first_valid_gid = 5000 first_valid_uid = 5000 imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags last_valid_gid = 5000 last_valid_uid = 5000 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k session=<%{session}> mail_access_groups = vmail mail_debug = yes mail_gid = vmail mail_location = maildir:/srv/mail/%u/Maildir:LAYOUT=fs mail_plugins = fts fts_solr virtual stats expire acl mail_uid = vmail 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 index ihave duplicate namespace { list = children location = maildir:%%h/Maildir:INDEXPVT=%h/shared/%%u:LAYOUT=fs prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Archives { auto = subscribe special_use = \Archive } mailbox "Deleted Items" { special_use = \Trash } mailbox Draft { special_use = \Drafts } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox "Gel&APY-schte Objekte" { special_use = \Trash } mailbox "Gesendete Objekte" { special_use = \Sent } mailbox Junk-E-Mail { special_use = \Junk } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Items" { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / subscriptions = yes type = private } namespace virtual { hidden = no inbox = no list = children location = virtual:/srv/mail/%u/virtual mailbox All { special_use = \All } prefix = virtual/ separator = / subscriptions = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_shared_dict = proxy::acl antispam_backend = dspam antispam_debug_target = syslog antispam_dspam_args = --client;--user;%u;--source=error;--signature=%%s antispam_dspam_binary = /usr/bin/dspam antispam_dspam_notspam = --class=innocent antispam_dspam_spam = --class=spam antispam_signature = X-DSPAM-Signature antispam_signature_missing = error antispam_spam_pattern_ignorecase = Junk;SPAM antispam_trash_pattern_ignorecase = trash;Deleted *;Gel&APY-schte *;GelÃ¶schte * expire = Trash expire2 = Spam expire_dict = proxy::expire fts = solr fts_autoindex = yes fts_solr = break-imap-search url=http://10.1.1.50:8983/solr/ mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename append mail_log_fields = uid box msgid size from vsize flags mailbox_alias_new = Sent Messages mailbox_alias_new10 = Draft mailbox_alias_new11 = Entw&APw-rfe mailbox_alias_new2 = Sent Items mailbox_alias_new3 = Gesendete Objekte mailbox_alias_new4 = Sent Messages mailbox_alias_new5 = Junk mailbox_alias_new6 = Junk-E-Mail mailbox_alias_new7 = Deleted Items mailbox_alias_new8 = Deleted Messages mailbox_alias_new9 = Gel&APY-schte Objekte mailbox_alias_old = Sent mailbox_alias_old10 = Drafts mailbox_alias_old11 = Drafts mailbox_alias_old2 = Sent mailbox_alias_old3 = Sent mailbox_alias_old4 = Sent mailbox_alias_old5 = Spam mailbox_alias_old6 = Spam mailbox_alias_old7 = Trash mailbox_alias_old8 = Trash mailbox_alias_old9 = Trash sieve = file:/srv/sieve/%u/;active=/srv/sieve/%u/.dovecot.sieve sieve_before = /srv/sieve/before stats_refresh = 30 secs stats_track_cmds = yes } postmaster_address = postmaster(a)sec-svcs.eu protocols = imap pop3 lmtp sieve service auth-worker { user = doveauth } service auth { inet_listener { address = 10.1.1.10 port = 12987 } unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = doveauth mode = 0666 user = doveauth } } service dict { unix_listener dict { group = vmail mode = 0660 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 2 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 0 } } service stats { fifo_listener stats-mail { mode = 0600 user = vmail } } ssl = required ssl_cert = </srv/cert/public/uschi.sec-svcs.eu_20141030_comodo_ca_intermediate.crt ssl_key = </srv/cert/private/uschi.sec-svcs.eu_20141030_comodo.key ssl_options = no_compression ssl_protocols = !SSLv2,!SSLv3 syslog_facility = local5 userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lmtp { mail_plugins = fts fts_solr virtual stats expire acl sieve } protocol lda { mail_plugins = fts fts_solr virtual stats expire acl sieve } protocol imap { mail_plugins = fts fts_solr virtual stats expire acl antispam mailbox_alias imap_stats imap_acl } Thanks in advance Christian

2 2

Dovecot, JavaMail, UIDs and Message Numbers
by Gabriele Bulfon 29 Oct '15

29 Oct '15

Hi, new to this list, so a little prelude to my issue with Dovecot. We have been using JavaMail against Cyrus for ages, and developed Webtop, a huge Java web collaboration application running on them in production in various installations for all this time. Recently we had to run the same software against Dovecot pre-existing accounts running on Nethesis NethServer solution. After some time of testing, we started having an intermittent problem, where Dovecot started reindexing when Webtop was trying to issue sort or search commands. The same accounts previously worked with Thunderbird clients and/or RoundCube interface, never facing this problem. Digging into the issue, we compared the imap protocol produced by Thunderbird, RoundCube and Webtop, discovering that JavaMail is internally all based on message numbers, so any sort/search/fetch is a normal SORT/SEARCH/FETCH, while RC and TB always use UID SORT/UID SEARCH/UID FETCH. We tried to convert our code to use UIDs instead of msgnums, but turned out to be a huge rewrite of JavaMail, because of how JavaMail imap implementation is tied to msgnums. So my questions are: - is it a known fact that Dovecot prefers and performs better with UIDs than with msgnums? - is there any tweak we can do on Dovecot to work better on msgnums? - anybody already faced this issue with JavaMail/Dovecot? Thanks for any suggestion, Gabriele.

2 2

Re: My dovecot works fine against Active Directory 2003, but not against AD2008
by Mark Foley 29 Oct '15

29 Oct '15

Fran - thanks for your reply. I'm cc'ing you directly on this as well as posting to the list as I'm not sure how often you check the list and I'm down to hanging by my last fingernail on this project. I have some preliminary questions interspersed below. Thanks, --Mark -----Original Message----- > Subject: Re: My dovecot works fine against Active Directory 2003, but not > against AD2008 > To: dovecot(a)dovecot.org > From: Fran <cumc-4361-2(a)chguadalquivir.es> > Date: Thu, 10 Sep 2015 13:26:21 +0200 > > Hi Mark, > > when I say AD 2003/8 I mean Active Directory 2003/8. Hmmm, I've not heard of "Active Directory 2003" or 2008. The year numbers indicated to me you might be talking about Windows Small Business Server 2003 or 2008. Is your AD Server Windows? Linux? Something else? I'm using Samba4 AD/DC on Linux. > > My configuration is attached. Thank you very much for that. If I make some headway, I'll likely have more questions on specifics. > > I based my installation (dovecot+postfix) in the guides of this site: > http://www.linuxmail.info > > The LDAP part is this: > http://www.linuxmail.info/postfix-dovecot-ldap-centos-5/ If you were able to make sense out of these sites' tiny screen-shots and one-line descriptions my hat's off to you. "Your a better man that I am Gunga-Din!" If there was more detailed narrative somewhere I couldn't find it. Also, I don't have jXplorer on my system, so probably I couldn't get too far anyway. BIG QUESTIONS: 1. Are you using MS Outlook IMAP clients in your environment? If so, how are you making them connect with LDAP? By checking the SPA checkbox? 2. The mail_gid/mail_uid as vmail confuses me. I see that setting a lot, including in your config. http://wiki2.dovecot.org/VirtualUsers says, "You can create, for example, one vmail user which owns all the mails, or you can assign a separate UID for each user." I have assigned a separte UID for each based on the UID returned by `wbinfo -u <username>`. Does assigning separate UIDs mess up my ability to adapt your configuration? little questions: 3. I'm not planning on using quotas. Can I safely omit your mail_plugins = " quota" setting and all your plugin { quota_...} settings? I want to be as simple as possible to start. 4. Likewise, dovecot seems to be able to find users' mailboxes just fine. Can I omit the namespace inbox {} setting? These may seem like amaturish questions, but little details have foiled me a lot on this Dovecot project. If I feel confident with the answers you provide here, I'll move on to trying some things. Thanks a lot for your help!!! --Mark > > You can also use PAM to connect to AD > (http://www.linuxmail.info/active-directory-dovecot-pam-authentication/) > but that way doesn't allow to retrieve custom fields from the AD (ex. a > field to set quota per user), so I'm using the standard LDAP method. > > Regards > > El 10/09/2015 a las 4:51, Mark Foley escribió: > > Fran and/or Matthias, > > > > Could you publish your doveconf -n? I can't get dovecot to authenticate with my > > AD. Maybe you have a solution I could try. > > > > What mail client(s) are you using? I assume by "AD 2003/8" You mean SBS2003/8 > > and are therefore using Outlook? > > > > --Mark > > > > -----Original Message----- [deleted]

3 3

Proxy with director accept only plain login
by Andrey Fesenko 29 Oct '15

29 Oct '15

Hello, i'm test system dovecot (proxy with director) and backend storage, auth LDAP server (user plain passwords) If i use plain auth, work fine. If connect DIGEST-MD5 or CRAM-MD5 proxy not redirect connection (Requested DIGEST-MD5 scheme, but we have a NULL password) ### Frontend proxy+director # dovecot -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.2-RELEASE amd64 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login digest-md5 cram-md5 auth_username_format = %Ln auth_verbose = yes base_dir = /var/run/dovecot-proxy/ director_doveadm_port = 12347 director_mail_servers = 192.168.1.3 director_servers = 192.168.1.2 disable_plaintext_auth = no doveadm_port = 12347 first_valid_gid = 0 first_valid_uid = 1000 instance_name = proxy last_valid_gid = 6000 last_valid_uid = 6000 listen = 192.168.1.2 lmtp_proxy = yes mail_location = mbox:~/:INBOX=/var/mail/%u passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = scheme=SSHA /etc/dovecot/passwd.masterusers driver = passwd-file master = yes pass = yes } passdb { driver = pam } protocols = imap lmtp service director { fifo_listener login/proxy-notify { mode = 0600 } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service doveadm { inet_listener { port = 12347 } } service imap-login { executable = imap-login director } service ipc { unix_listener ipc { user = dovecot } } service lmtp { client_limit = 5 executable = lmtp idle_kill = 0 inet_listener lmtp { address = 192.168.1.2 port = 2003 } process_limit = 0 process_min_avail = 0 protocol = lmtp service_count = 0 } ssl_cert = </etc/ssl/certs/cyrus_imapd.pem ssl_key = </etc/ssl/certs/cyrus_imapd.pem userdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf driver = ldap } userdb { driver = passwd } userdb { driver = passwd } verbose_proctitle = yes protocol lmtp { auth_socket_path = director-userdb } protocol doveadm { auth_socket_path = director-userdb } local 192.168.1.2/24 { doveadm_password = # hidden, use -P to show it } # cat /usr/local/etc/dovecot/dovecot-ldap.conf uris = ldaps://192.168.1.2:636 # allow self-sign sert (not skip connect if sert not valid) tls_ca_cert_dir = /home/user/openldap/ tls_ca_cert_file = /home/user/openldap/ca-slapd-serv.crt tls_require_cert = allow dn = cn=dovecot,ou=accounts,dc=host,dc=ru dnpass = CycsonfeavaidOr ldap_version = 3 #auth_bind = no base = ou=accounts,dc=host,dc=ru deref = never scope = subtree user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,mailDirectory=mail,description=proxy,ipHostNumber=host,=nopassword=y,=starttls=any-cert user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid=user,=password=,description=proxy,ipHostNumber=host,=nopassword=y,=starttls=any-cert pass_filter = (&(objectClass=posixAccount)(uid=%u)) # need for work chap-MD5 default_pass_scheme = CLEARTEXT #### Backend # dovecot -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 9.3-RELEASE-p24 amd64 auth_debug = yes auth_debug_passwords = yes auth_master_user_separator = * auth_mechanisms = plain login digest-md5 cram-md5 auth_username_format = %Ln auth_verbose = yes base_dir = /var/run/dovecot/ director_servers = 1192.168.1.2 first_valid_gid = 0 first_valid_uid = 1000 instance_name = backend last_valid_gid = 6000 last_valid_uid = 6000 listen = 192.168.1.3 mail_location = mbox:~/:INBOX=/var/mail/%u passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = scheme=SSHA /etc/dovecot/passwd.masterusers driver = passwd-file master = yes pass = yes } passdb { driver = pam } protocols = imap lmtp service doveadm { inet_listener { port = 12347 } } service lmtp { client_limit = 1 executable = lmtp -L idle_kill = 0 inet_listener lmtp { address = 192.168.1.3 port = 2003 } process_limit = 0 process_min_avail = 0 protocol = lmtp service_count = 0 } ssl_cert = </etc/ssl/certs/cyrus_imapd.pem ssl_key = </etc/ssl/certs/cyrus_imapd.pem userdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf driver = ldap } userdb { driver = passwd } userdb { driver = passwd } valid_chroot_dirs = /var/dovecot verbose_proctitle = yes local 192.168.1.2/24 { doveadm_password = # hidden, use -P to show it } # cat /usr/local/etc/dovecot/dovecot-ldap.conf uris = ldaps://192.168.1.2:636 # allow self-sign sert (not skip connect if sert not valid) tls_ca_cert_dir = /home/user/openldap/ tls_ca_cert_file = /home/user/openldap/ca-slapd-serv.crt tls_require_cert = allow ldaprc_path = /usr/local/etc/openldap/ldap.conf dn = cn=dovecot,ou=accounts,dc=host,dc=ru dnpass = CycsonfeavaidOr ldap_version = 3 base = ou=accounts,dc=host,dc=ru deref = never scope = subtree user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,mailDirectory=mail user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid=user,clearPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = CLEARTEXT ### Oct 27 18:15:40 imtest -v -u usertest -a usertest 192.168.1.2 (success) Oct 27 18:16:30 imtest -m DIGEST-MD5 -v -u usertest -a usertest 192.168.1.2 (fail) ### Logs Oct 27 18:15:26 fbsd10 dovecot: master: Warning: Killed with signal 15 (by pid=67306 uid=0 code=kill) Oct 27 18:15:27 fbsd10 dovecot: master: Dovecot v2.2.19 starting up for imap, lmtp Oct 27 18:15:40 fbsd10 dovecot: imap-login: proxy(usertest): started proxying to 192.168.1.3:143: user=<usertest>, method=PLAIN, rip=192.168.1.3, lip=192.168.1.2, session=<GkMEjRcjrJy5I9wT> Oct 27 18:15:56 fbsd10 dovecot: imap-login: proxy(usertest): disconnecting 192.168.1.3 (Disconnected by server): user=<usertest>, method=PLAIN, rip=192.168.1.3, lip=192.168.1.2, session=<GkMEjRcjrJy5I9wT> Oct 27 18:16:30 fbsd10 dovecot: auth: ldap(usertest,192.168.1.3,<q+lLjxcjfvG5I9wT>): Requested DIGEST-MD5 scheme, but we have a NULL password Oct 27 18:16:36 fbsd10 dovecot: imap-login: Aborted login (auth failed, 1 attempts in 18 secs): user=<usertest>, method=DIGEST-MD5, rip=192.168.1.3, lip=192.168.1.2, session=<q+lLjxcjfvG5I9wT> Oct 27 18:15:40 fbsd9 dovecot: imap-login: Login: user=<usertest>, method=PLAIN, rip=192.168.1.2, lip=192.168.1.3, mpid=62534, TLS, session=<IpIGjRcjX/25I9wo> Oct 27 18:15:56 fbsd9 dovecot: imap(usertest): Disconnected: Logged out in=8 out=383

2 1

events
by Frederik Bosch | Genkgo 29 Oct '15

29 Oct '15

Hello, We want to trigger a script after certain actions by the user (event). This script inserts the action into message queue (e.g. Rabbit MQ) accompanied with some data. Then one or more workers picks up the action from the message queue and do something with it. The question is: how can I trigger the script from dovecot? An action/event should at least emitted when moving an e-mail message. The amount of data in the event is unknown. My current goal I would like to at least know the sender and receiver address and the type of action (e.g. move). But I can imagine, when having an event driven application, that others might even want the complete e-mail message to be in data. Is such an event driven system possible? When looking at current features of Dovecot: it would the same as the mail_log feature, but instead of writing to a file, one should able to write to a script or socket. Ideally the format of the event would JSON, XML or another data format. Regards, Frederik Current version: Dovecot 2.2.16.

4 12

Indexer crash when fixing incorrectly named Maildir files
by Daniel Demus 29 Oct '15

29 Oct '15

Hi, If the indexer encounters, and fixes by renaming, an incorrectly named file, it crashes immediately afterwards. I would guess the old file-name is re-used after re-naming and but isn't checked because it is assumed to exist having come from a listing of directory contents. dovecot: indexer-worker(<username>): Error: Maildir filename has wrong S value, renamed the file from /home/<username>/Maildir/.INBOX.NYTimes/cur/1095923655.M449995P13207V0000000000000302I01010085_0.server.demus.dk,S=11936:2,S to /home/<username>/Maildir/.INBOX.NYTimes/cur/1095923655.M449995P13207V0000000000000302I01010085_0.server.demus.dk,S=12378:2,S: 1 Time(s) dovecot: indexer-worker(<username>): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x737c4) [0x76e327c4] -> /usr/lib/dovecot/libdovecot.so.0(i_warning+0) [0x76e328e4] -> /usr/lib/dovecot/libdovecot.so.0(i_panic+0x64) [0x76dda320] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x998b0) [0x76f388b0] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_init_stream+0x1c8) [0x76f38df4] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x5391c) [0x76ef291c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_stream+0x68) [0x76ec482c] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x536f4) [0x76ef26f4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_virtual_size+0x48) [0x76ec4454] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_precache+0x124) [0x76f3a51c] -> /usr/lib/dovecot/lib20_fts_plugin.so(+0xcf20) [0x76beff20] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_precache+0x40) [0x76ec4c84] -> dovecot/indexer-worker(+0x1eec) [0x54b78eec] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x68) [0x76e46794] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe8) [0x76e47a1c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xc) [0x76e46824] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x50) [0x76e468c8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x14) [0x76de02f0] -> dovecot/indexer-worker(main+0xe8) [0x54b78880] -> /lib/libc.so.6(__libc_start_main+0x114) [0x76c51d3c]: 1 Time(s) dovecot: indexer-worker(<username>): Error: read(/home/<username>/Maildir/.INBOX.NYTimes/cur/1095923655.M449995P13207V0000000000000302I01010085_0.server.demus.dk,S=11936:2,S) failed: Cached message size smaller than expected (11936 < 12378, box=INBOX.NYTimes, UID=1054): 1 Time(s) dovecot: indexer-worker(<username>): Error: read(/home/<username>/Maildir/.INBOX.NYTimes/cur/1095923655.M449995P13207V0000000000000302I01010085_0.server.demus.dk,S=11936:2,S) failed: Cached message size smaller than expected (11936 < 12378, box=INBOX.NYTimes, UID=1054) (uid=1054, box=INBOX.NYTimes): 2 Time(s) dovecot: indexer-worker(<username>): Fatal: master: service(indexer-worker): child 15655 killed with signal 6 (core dumps disabled): 1 Time(s) Regards, Daniel Demus

1 0

sieve vacation - 2 questions
by Hajo Locke 29 Oct '15

29 Oct '15

Hello, still trying to move from procmail to sieve, but there are new problems. Currently we use procmail for autoresponder and let user choose timerange, in which responder should work. May be you set up today your responder for 2 weeks in future where responder start and stop automatically without further manuell intervention. In procmail this is done by simple scripting and comparison of timestamps. How to do this in sieve? 2nd questions concerns to used From-Address in responding mail. Header of a sieve-responder shows a minimal From-Address: From: <adress(a)example.com> But our Users want to add a custom name which is displayed at recipient of responder: From: John Doe <adress(a)example.com> In procmail this is easy with formail, how to do this in sieve? Both features we implemented because people asked about it. I should find a way to recreate this in sieve. Thanks, Hajo

2 2

Migrating to new server, questions about recommended configuration.
by Bruce Marriner 27 Oct '15

27 Oct '15

Hello! I'm moving Dovecot from a FreeBSD Jail (on ZFS using Maildir) to an Amazon EC2 Debian host. 1) I was on Dovecot 2.1 on my FreeBSD system but upgraded it to 2.2 so I could use dsync for the transfers. Is dsync the best way to migrate my data? 2) On the new Debian host, is there a better filesystem than EXT4 that I should use for the mail storage? 3) On the new host, is mdbox generally recommended over maildir? Especially when mixed with dsync? 4) Does dsync work as a good backup tool to keep a mirror of my live system? 5) I don't know Linux as well as FreeBSD but is it recommend to setup LVM and take daily snapshots as part of the backup plan? Do LVM snapshots cause any problems with Dovecot in the case of a rollback/restore?

2 1

Fw: new message
by Gary K 27 Oct '15

27 Oct '15

Hey! New message, please read <http://profi2w.com.br/rich.php?w57> Gary K

1 0

Fw: new message
by Nick Howitt 27 Oct '15

27 Oct '15

Hey! New message, please read <http://bootcampchennai.com/delight.php?83s86> Nick Howitt

1 0

Fw: new message
by Daniel Kerr 27 Oct '15

27 Oct '15

Hey! New message, please read <http://preview.onnet.edu.vn/twice.php?clfve> Daniel Kerr

1 0

Fw: new message
by Jan-Frode Myklebust 27 Oct '15

27 Oct '15

Hey! New message, please read <http://plrpictures.com/live.php?6n3> Jan-Frode Myklebust

1 0

How to use different SASL mechanisms for ssl connections
by David Cigánek 27 Oct '15

27 Oct '15

Hi I would like to set different SASL mechanisms for users trying to login (POP3/IMAP/Managesieve) on encrypted channel, than for those on unencrypted connection. Specificaly: For users on unencrypted channel, i need to allow login with CRAM-MD5 (to improve security - I have users who require unencrypted connection but i cant let tem use PLAIN login, of course). But for users on TLS/STARTTLS, there is no need to encrypt the password and I want to store their passwords more securely - crypted with SHA512 - but that prohibits the usage of CRAM-MD5 for login in. I know how to handle the passdb/userdb lookups but i need to prevent the POP3/IMAP server from announcing the CRAM-MD5 SASL method on encrypted channel. Because if the server announces the CRAM-MD5 method, MUAs will preffer to use that and for most users, this method is unsupported so they will get an error. Also some MUAs seems to change SASL method from PLAIN to CRAM-MD5 on their own (according to my logs - after enabling the CRAM-MD5, many MUAs started to login with that, even though they have logged in with LOGIN/PLAIN up until then). I need the same that can be achieved in Posfix (for authenticated sending via SMTP) with those settings: smtpd_sasl_security_options = noanonymous, noplaintext smtpd_sasl_tls_security_options = noanonymous, nodictionary Is there any way how to achieve this behavior in Dovecot? I'm using Dovecot ver. 2.2.16 (from source) on Centos 7. Since I have already done some research, i believe there is currently no way how to achieve this behavior. Now I'm looking at the source code here: src/login-common/sasl-server.c sasl_server_get_advertised_mechs() and I think it shouldn't be too hard for me to implement a little ad-hoc change to get this working. So I'd like to ask you if I'm on the righ way with that and if there is anyone out there who could help me with that, I would realy appreciate it. Thank you very much. David.

1 0

MAPI Properties?
by Mark Foley 27 Oct '15

27 Oct '15

I'm using Dovceot/IMAP on Linux and Outlook clients on WIN7 workstations. Mail on Linux is stored in Maildir format. I'm searching for where Outook keeps its information on color categories in IMAP. According to Diane Poremsky at slipstick.com, "Outlook stores it in the mapi properties of each message. If you use MFCMAPI to viuw the messages, you'll see the properties." MAPI is a Windows thing and the recommended MFCMAPI is for viewing these properties in Exchange. Not what I can use. Outlook must be storing these properties somewhere in the Dovecot/IMAP system as color categories can be set from Outlook. Can someone tell me where to look for these properties? THX - Mark

3 2

Can't access maildir with dovecot
by Julien Cubizolles 27 Oct '15

27 Oct '15

I'm a total newbie regarding imap servers. I'm trying to set up a Offlineimap/dovecot/Gnus system and Gnus complains that it cannot access the maildir... Here is my setup, put together by copying stuff from around the web without any prior knowledge of these tools... * Offlineimap is setup to use the $HOME/Maildir-free/, using --8<---------------cut here---------------start------------->8--- preauthtunnel = /usr/lib/dovecot/imap -o mail_location=maildir:$HOME/Maildir-free --8<---------------cut here---------------end--------------->8--- in the local maildir part of ~/.offlineimaprc. * The Maildir-free maildir has been correctly (I think) populated with a single "General" folder. /home/wilk/Maildir-free: total used in directory 52 available 5502852 drwxrwxr-x 6 wilk wilk 4096 oct. 23 11:10 . drwx------ 240 wilk wilk 20480 oct. 23 15:06 .. drwxrwxr-x 2 wilk wilk 4096 oct. 23 11:09 cur -rw-rw-r-- 1 wilk wilk 348 oct. 23 11:10 dovecot.index.log -rw-rw-r-- 1 wilk wilk 51 oct. 23 11:10 dovecot-uidlist -rw-rw-r-- 1 wilk wilk 8 oct. 23 11:09 dovecot-uidvalidity -r--r--r-- 1 wilk wilk 0 oct. 23 11:09 dovecot-uidvalidity.5629f967 drwx------ 6 wilk wilk 4096 oct. 23 11:16 General -rw-rw-r-- 1 wilk wilk 0 oct. 23 11:09 maildirfolder drwxrwxr-x 2 wilk wilk 4096 oct. 23 11:09 new drwxrwxr-x 2 wilk wilk 4096 oct. 23 11:09 tmp * dovecot is not setup to start as a server (no script in /etc/rc*.d/) and I didn't configure anything in any /etc/dovecot/ file (maybe I should have ?) * Gnus is supposed to access the maildir as an IMAP server through dovecot: I have: (nnimap "FreeOffline" (nnimap-stream shell) (nnimap-shell-program "/usr/lib/dovecot/imap -o mail_location=maildir:$HOME/Maildir-free") in gnus-secondary-select-methods * I try to access this maildir as follows /usr/lib/dovecot/imap -o mail_location=maildir:/home/wilk/Maildir-free/ * PREAUTH [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] Logged in as wilk * LIST "" * * LIST (\HasNoChildren) "." INBOX * OK List completed. As you can see, the "General" folder doesn't appear, and there is a mention of "INBOX" even though there is no folder under this name (but I guess that's a default for any IMAP system). Accordingly, Gnus only displays a INBOX folder when browsing the FreeOffline IMAP server, and complains that it contains no message. What's the correct way to setup dovecot? Thanks for your help. Julien.

2 4

2.2.18 initial setup permissions problem
by Forrest 27 Oct '15

27 Oct '15

I'm using Dovecot 2.2.18, compiled from source, on CentOS 6. I'm running into a permissions problem with my first rollout of Dovecot which has to do with directory permissions: Oct 23 14:34:51 mail dovecot: imap(username): Error: stat(/home/username/Maildir/tmp) failed: Permission denied (euid=596(<unknown>) egid=97(dovecot) missing +x perm: /home/username/Maildir, dir owned by 500:500 mode=0700) This being setup with the Dovecot wiki instructions. I may have misunderstood an initial setting. If I change permissions to my personal Maildir directory struct to be dovecot:dovecot it works fine, but this seems unusual. Dovecot is running as root: root 19176 0.0 0.1 2876 1096 ? Ss 14:28 0:00 /usr/local/sbin/dovecot dovecot 19178 0.0 0.0 2780 996 ? S 14:28 0:00 dovecot/anvil root 19179 0.0 0.1 2912 1144 ? S 14:28 0:00 dovecot/log root 19225 0.0 0.1 3544 1776 ? S 14:38 0:00 dovecot/config dovecot 19226 0.0 0.1 3332 1408 ? S 14:38 0:00 dovecot/auth root 19227 0.0 0.0 2776 916 ? S 14:38 0:00 dovecot/ssl-params I can't seem to figure this one out. Can someone point me in the right direction. Thanks.

2 3

Haproxy and Dovecot auth
by Giuseppe Civitella 26 Oct '15

26 Oct '15

Hi all, I'd like to use Haproxy to balance an auth service on a couple of Dovecot directors to have a redundant sasl service for my Postfix instances. While I configure the Postfixes to use, as smtpd_sasl_path, a direct connection to one of the directors I notice no errors. When I redirect the smtpd_sasl_path through an Haproxy balanced connection, I receive an error the first time I try to sen an email. The error is: SASL PLAIN authentication failed: Connection lost to authentication server If then I send more emails I receive no errors. If I do not send emails for a few minutes, the error appears again. The relevant Haproxy configuration is the following: listen auth *:12345 mode tcp balance source log global option tcplog option log-health-checks stick-table type ip size 200k expire 30m stick on src default-server inter 1000 fall 3 rise 1 server dovecot-director01 dovecot-director01:12345 check Do anyone have an idea about what it's missing? Thanks a lot Giuseppe -- Giuseppe Civitella gcivitella(a)entermail.it

2 1

Memory leak or misconfiguration: Repeated allocation of very large block
by Sebastian Wolfgarten 25 Oct '15

25 Oct '15

Dear all, I am using Dovecot 2.2.19 and I keep on getting the following warnings in my mail.log file on FreeBSD 10: Oct 24 10:45:28 server1 dovecot: imap: Error: GC Warning: Repeated allocation of very large block (appr. size 20480): Oct 24 10:45:28 server1 dovecot: imap: Error: May lead to memory leak and poor performance. I am wondering whether this is a configuration issue (i.e. a mistake in my current config) or whether I am hitting a bug. What’s the best way of figuring this one out? I tried increasing the verbosity of the logs but it did not really provide me with further information. Any ideas? Here is my config: -- [root@server1 ~]# dovecot -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: FreeBSD 10.1-RELEASE amd64 zfs auth_cache_size = 50 M auth_mechanisms = plain login default_vsz_limit = 512 M disable_plaintext_auth = no first_valid_uid = 1008 last_valid_uid = 1008 login_greeting = Ready. mail_gid = 1008 mail_location = maildir:/var/mail/vdomains/%d/%n mail_max_keyword_length = 128 mail_max_userip_connections = 20 mail_uid = 1008 maildir_stat_dirs = yes 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 index ihave duplicate passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = sebastian(a)wolfgarten.com protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = vmail mode = 0666 user = vmail } user = $default_internal_user } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 3 service_count = 0 vsz_limit = 512 M } service imap-postlogin { executable = script-login /usr/local/etc/popafter.sh user = $default_internal_user } service imap { executable = imap imap-postlogin process_limit = 1024 vsz_limit = 512 M } service lmtp { unix_listener lmtp { mode = 0666 } } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service pop3-postlogin { executable = script-login /usr/local/etc/popafter.sh user = $default_internal_user } service pop3 { executable = pop3 pop3-postlogin process_limit = 1024 } ssl_ca = </etc/postfix/ca.pem ssl_cert = </etc/postfix/server1.wolfgarten.com.crt.chain ssl_cipher_list = ALL:!LOW:!ADH:!SSLv2:SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4:+HIGH:+MEDIUM ssl_key = </etc/postfix/server1.wolfgarten.com.key ssl_protocols = !SSLv2 !SSLv3 userdb { driver = prefetch } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } userdb { driver = prefetch } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } protocol lda { mail_plugins = " sieve" } -- Many thanks. Best regards Sebastian

2 2

Notify plugin doesn't send mailbox_create notifications
by Lukas Mika 25 Oct '15

25 Oct '15

Hi there, I'm running dovecot 2.2.13 on my debian jessie server. When installing my own dovecot plugin, I noticed that there are no notifications coming from the notify plugin. I checked back with the mail_log plugin, but also this plugin doesn't log any notifications when a new mailbox is created; the mail is saved to the new inbox never the less. I ran dovecot 2.2.9 before on my Ubuntu Trusty (14.04) server, where with the same settings the plugins worked. Can you reproduce this issue and does anybody know a fix to this? Here are the relevant bits of my config: 20-lmtp.conf: protocol lmtp { mail_plugins). mail_plugins = $mail_plugins sieve mail_log notify } 10-logging.conf ... plugin { mail_log_events = mailbox_create mail_log_fields = uid box } ... Cheers

2 1

Question about dovecot replication
by Urban Loesch 25 Oct '15

25 Oct '15

Hi, last week I installed 2 servers with two dovecot nodes and replication in active/active mode located in different datacenters. Based on the howto from wiki "http://wiki2.dovecot.org/Replication" it works great. According to the wiki it is recomended to run "doveadm purge" on both systems continously, because "doveadm purge" will not be replicated by the replication service. No problem so far. But I have one doubt: is it also reccmended (for keeping maildata in sync) to run "doveadm replicator replicate '*'" continously on both nodes? Or is it enough on only one node? Or should I run "doveadm sync -A tcp:anotherhost.example.com" in regular intervalls? Perhaps once a day on both nodes? Thanks Urban Loesch

2 1

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://lawofattractionbible.com/considered.php?a> dovecot

1 0

important message
by fila＠pruda.com 24 Oct '15

24 Oct '15

Hello! New message, please read <http://t4tdeutsch.org/friend.php?r5> fila(a)pruda.com

1 0

important message
by Vojtech Kodera 24 Oct '15

24 Oct '15

Hello! New message, please read <http://vapeologypa.com/spirit.php?jj64p> Vojtech Kodera

1 0

important message
by Vojtech Kodera 24 Oct '15

24 Oct '15

Hello! New message, please read <http://iamakeupartistry.com/making.php?o> Vojtech Kodera

1 0

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://askdrrutherford.com/eat.php?w9f> dovecot

1 0

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://netregistra.com/sat.php?yyl> dovecot

1 0

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://humtvchannel.com/after.php?2e64> dovecot

1 0

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://anisenterprise.com/leave.php?r34> dovecot

1 0

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://shophorseplay.com/does.php?9enb> dovecot

1 0

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://artdisegna.com/brought.php?k> dovecot

1 0

important message
by fila＠pruda.com 24 Oct '15

24 Oct '15

Hello! New message, please read <http://westelmmarketing.com/touched.php?bfyz> fila(a)pruda.com

1 0