- dovecot - dovecot.org

dovecot 2.2 repo
by Bas van Rooijen 02 Sep '19

02 Sep '19

Hi, >From the v2.2.36.4 announcement message: "Binary packages are available at https://repo.dovecot.org/" My question is, where exactly? There's an instruction at repo.dovecot.org that tells you to replace 'ce-latest-2.3' with 'ce-<version>' but the given url doesn't even contain 'ce-latest-2.3' and http://repo.dovecot.org/ce-2.2.36 returns a 404. Thanks in advance! bvr.

4 3

Experimental docker images
by aki.tuomi＠dovecot.fi 02 Sep '19

02 Sep '19

Hi, you can now find experimental Docker images for dovecot CE releases (starting from 2.3.7.2) from https://hub.docker.com/r/dovecot/dovecot You can find instructions and more details on the repository page. ---- Aki

1 0

Re: Message delivered twice caused by an LMTP error "Got unexpected reply" during upgrade to 2.3
by Gabriele Nencioni 02 Sep '19

02 Sep '19

>>> On 08/09/2018 09:12 AM, Stephan Bosch wrote >>>>>> Can you make a pcap log of the LMTP communication between the two >>>>>> Dovecot hosts? That may give me a clue on which side of the >>>>>> communication is causing the issue. >>>>> Yes sure, where I can send it? >>>>> Here on list or at your address? >>>> >>>> Just send it to me. On 08/16/2018 10:21 AM, Stephan Bosch wrote: > Op 16/08/2018 om 09:46 schreef Gabriele Nencioni: >> On 08/15/2018 06:39 PM, Stephan Bosch wrote: >>> Op 15-8-2018 om 17:19 schreef Stephan Bosch: >>>> >>>> Op 13-8-2018 om 15:50 schreef Gabriele Nencioni: >>>>> So the scenario seems to be: >>>>> the error occurs between old directors and new backends >>>>> and between the new backends and the smtp submission_host (for >>>>> redirection) >>>>> and using the pipeline capability and attaching a file >>>>> >>>>> Let me know if you need more info >>>> In this case it is possible to obtain a debug log by enabling >>>> mail_debug=yes. Can you obtain a full debug log for such a failing >>>> submission session? >> Ok! It is attached. > > That is just weird. Dovecot reports that it cannot fully send the last > bits of the message and right thereafter the reply is received, which > Dovecot then interprets as out-of-sequence. The PCAP files tell me the > final CRLF.CRLF is actually sent to the other side, but somehow Dovecot > thinks it couldn't do that yet. > > Is this problem occurring for any and all SMTP client interactions, or > just every once in a while? Unfortunately it occurs just every once in a while and it is weird because at the second attempt the message is successful delivered or redirected. >>> Also, I don't see anything weird in the PCAP files: the command-reply >>> sequence is OK. This means that this is likely a bug in the current >>> Dovecot version. Those debug logs should tell me more. >> Ok! Which version of dovecot do you suggest to install? >> On debian current stable (stretch) repository there is the version >> number 2.2.27, have we to install it? > > If you're facing big trouble it is usually best to revert to the > previous version that worked I guess. Ok I'm agree! So, about you, which version can I try to install the 2.2.27 or the previous release of the 2.3 version such as v2.3.2 2018-06-29 or v2.3.1 2018-02-29? Regards, -- Gabriele Nencioni System Administrator eml gabriele.nencioni(a)register.it

2 6

purge causing reappearing mails?
by sch tel 02 Sep '19

02 Sep '19

3 3

flags not synced correctly with dovecot sync (dsync)
by Dan Christensen 31 Aug '19

31 Aug '19

I'm running dovecot 2.3.4.1 from https://repo.dovecot.org/ on Ubuntu 18.04 on three machines that I'll call server, laptop1 and laptop2. Both laptop1 and laptop2 run dovecot sync against server to keep local copies of my imap folders. Even when I initially had only two machines, laptop1 and server, I occasionally noticed that flags were lost, usually custom flags used by Gnus, but I couldn't reliably reproduce the problem. Now that I have two laptops syncing against the server, the problem has gotten worse and I figured out a way to reproduce it: - on server: create new IMAP folder test, and put two read messages in it - on laptop1: doveadm sync -u user -l 10 -m test -f user@server - on laptop2: doveadm sync -u user -l 10 -m test -f user@server At this point, all three machines show the two messages M1 and M2 as being read. - on laptop1: mark message M1 unread - on laptop2: mark message M2 unread - on laptop1: doveadm sync -u user -l 10 -m test -f user@server Both laptop1 and server have M1 unread, M2 read, as expected. - on laptop2: doveadm sync -u user -l 10 -m test -f user@server Now laptop2 and server have M1 *read*, M2 unread. - on laptop1: doveadm sync -u user -l 10 -m test -f user@server Now laptop1 and the server have both M1 and M2 *read*. - on laptop2: doveadm sync -u user -l 10 -m test -f user@server Now laptop2 has both read as well. The two lines that say "*read*" are wrong in my opinion. dsync propagated a read mark to an unread message, even though that message was marked unread more recently than it was marked read. I usually use stateful sync, and get many related problems. I just did a test in which M1 and M2 started out read, and I started with empty files named dstate.test on laptop1 and laptop2. Then I did the above procedure, using the command doveadm sync -u user -l 10 -m test -s "`cat dstate.test`" user@server > dstate.test At the end, laptop2 and server had both messages unread (which is good), but laptop1 had only M1 unread, and repeated runs of the sync command did not correct this. So the stateful sync failed to detect a change. Are these bugs in dovecot? Is there more information that I can provide? The output of doveconf -n on one machine is below, and the others are almost identical. Thanks for any help! Dan # 2.3.4.1 (3c0b8769e): /etc/dovecot/dovecot.conf # OS: Linux 4.15.0-45-generic x86_64 Ubuntu 18.04.1 LTS # Hostname: laptop2 auth_mechanisms = plain login listen = 127.0.0.1 mail_index_log2_max_age = 10 days mail_index_log_rotate_min_age = 1 days mail_index_log_rotate_min_size = 300 k mail_location = maildir:~/Maildir 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 = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } protocols = imap service imap-login { inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 943 ssl = yes } } service imap { process_limit = 25 } ssl_cert = </etc/dovecot/private/dovecot.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } protocol lda { postmaster_address = [elided] } protocol imap { mail_max_userip_connections = 20 }

3 8

Sieve Header question.
by Larry Rosenman 31 Aug '19

31 Aug '19

I'm trying to make my github processing better, but I'm missing something. I have the following: if address :all :contains "from" ["github.com"] { addflag "github"; addflag "MyFlags" "github"; set "mailbox" "GitHub"; if address :matches :user "to" "*" { set "GHUser" "${1}"; addflag "${GHUser}"; addflag "MyFlags" "${GHuser}"; } if header :matches "List-ID" "(.*/.*) <(.*)>" { set "mailbox" "github-lists/${1}"; } fileinto :flags "${MyFlags}" :create "${mailbox}"; stop; } I'm trying to match the apache-incubator-superset part of: List-ID: apache/incubator-superset <incubator-superset.apache.github.com> What am I missing? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx(a)gmail.com US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106

1 1

problems witch quota working
by Bartłomiej Solarz-Niesłuchowski 30 Aug '19

30 Aug '19

Good evening! Dear list I have problem with quota-fs (rquota) support with dovecot. I use dovecot version: dovecot --version 2.3.7.1 (0152c8b10) build options: dovecot --build-options Build options: ioloop=epoll notify=inotify openssl io_block_size=8192 SQL driver plugins: mysql postgresql sqlite Passdb: checkpassword ldap pam passwd passwd-file shadow sql Userdb: checkpassword ldap(plugin) passwd prefetch passwd-file sql the privatedevices is in service set as no: systemctl show -p PrivateDevices dovecot PrivateDevices=no but quota (rquota on nfsv4) does not work: doveadm quota get -u solarz \doveadm(solarz): Error: Failed to get quota resource STORAGE: quota-fs: quotactl(Q_GETQUOTA, oceanic:/home) failed: No such file or directory Quota name Type Value Limit % User quota STORAGE error error error quota from os works: quota solarz Disk quotas for user solarz (uid 1761): Filesystem blocks quota limit grace files quota limit grace /dev/mapper/vg01-lvol00 1588264 40480000 40480000 12383 0 0 oceanic:/home 76318340 86284030 87416830 561911 1190000 1650000 configuration: # OS: Linux 5.2.9-200.fc30.x86_64 x86_64 Fedora release 30 (Thirty) # Hostname: dervish.wsisiz.edu.pl auth_cache_size = 8 k mail_access_groups = mail mail_fsync = always mail_location = maildir:~/Maildir:INBOX=/var/spool/mail/%u mail_max_userip_connections = 500 mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = acl quota zlib trash mail_privileged_group = 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 index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl mmap_disable = yes 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/deny-users deny = yes driver = passwd-file } passdb { args = cache_key=#hidden_use-P_to_show# max_requests=256 driver = pam } passdb { args = cache_key=#hidden_use-P_to_show# max_requests=256 driver = pam } plugin { quota = fs:User quota quota_grace = 10%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = file:~/sieve;active=~/.dovecot.sieve } postmaster_address = postmaster(a)wit.edu.pl protocols = imap pop3 service anvil { client_limit = 1155 } service auth { client_limit = 5248 user = root } service imap-login { client_limit = 1024 inet_listener imap { port = 0 } inet_listener imaps { address = [::], * port = 993 } process_limit = 1024 service_count = 0 } service imap { process_limit = 2048 vsz_limit = 512 M } service pop3-login { client_limit = 1024 inet_listener pop3 { port = 0 } inet_listener pop3s { address = [::], * port = 995 } process_limit = 128 service_count = 0 } service pop3 { process_limit = 2048 } service quota-warning { executable = script /usr/local/bin/quota-warning.sh user = dovenull } ssl = required ssl_cert = </etc/pki/tls/certs/ipop3d.pem ssl_cipher_list = PROFILE=SYSTEM ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } userdb { driver = passwd } protocol imap { imap_client_workarounds = " tb-extra-mailbox-sep" mail_max_userip_connections = 200 mail_plugins = acl quota zlib trash imap_quota ssl_cert = </etc/pki/tls/certs/imapd.pem ssl_key = # hidden, use -P to show it } protocol pop3 { mail_max_userip_connections = 200 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv ssl_cert = </etc/pki/tls/certs/ipop3d.pem ssl_key = # hidden, use -P to show it } Thank for any clues. Best Regards -- Bartłomiej Solarz-Niesłuchowski, Administrator WSISiZ e-mail: Bartlomiej.Solarz-Niesluchowski(a)wit.edu.pl tel. 223486547, fax 223486501 JID: solarz(a)jabber.wit.edu.pl 01-447 Warszawa, ul. Newelska 6, pokój 421, pon.-pt. 8-16 Motto - Jak sobie pościelisz tak sie wyśpisz

1 0

doveadm backup mdbox - initial copy slow
by Gerald Galster 30 Aug '19

30 Aug '19

Hello, when calling doveadm backup like in the following example, it seems to flush every email to disk maxing out harddrives (iops) and resulting in very poor performance: Calling doveadm -o plugin/quota= backup -u "statusmails(a)domain.com" "mdbox:/backup/vmail/domain.com/statusmails" finished in 212 secs [changes:1800 copy:1800 delete:0 expunge:0] The source mdbox holds 1800 small emails and uses about 20 MB disk space only. I've tried -f (full sync) and -l 30 (locking the mailbox) which did not get faster, nor did doveadm sync -1. When using doveadm import all mails are copied in less than 3 seconds: time doveadm -o mail=mdbox:/backup/vmail/domain.com/statusmails import mdbox:/var/vmail/domain.com/statusmails "" all real 0m2.605s Are there any other options I could try to speed up doveadm backup, avoiding the flush after each email? This is doveadm from dovecot 2.2 (>= 2.2.33). Does anyone get better results with 2.3 tree? Best regards Gerald

2 2

User / Pass SQL queries
by Michael Hallager 29 Aug '19

29 Aug '19

Hi all, Is there any reason Dovecot shows the 'user' variable (ie: user(a)domain.tld) being obtained in the password query and not the (more logical) user query? Thanks, Michael

2 1

permission issue after yum update
by Voytek Eymont 29 Aug '19

29 Aug '19

I've just updated my dovecot on centos, after 'yum update' dovecot failed to work, with manual restart it worked fine, just giving a warning: # dovecot Warning: Corrected permissions for login directory /var/run/dovecot/token-login dovecot --version 2.3.7.2 (3c910f64b) all's good, just reporting in case this is relevant to rpm maintainers thanks, V

1 0

download Dovecot
by Miquel Demur 29 Aug '19

29 Aug '19

I have downloaded in MacMini MacOS X applications directory the Dovecot.tzr.gz file from Dovecot v2.3.7.2 in https://www.dovecot.org/download I have clicked on dovecot-2.3.7.2 tar.gz and it creates a dovecot-2.3.7.2 directory containung 35 files. https://wiki2.dovecot.org/FrontPage?action=show&redirect=PageD%27Accueil#Do… https://wiki2.dovecot.org/FrontPage?action=show&redirect=PageD%27Accueil#Do… I have to compile to install in Terminal Application? ./configure make sudo make install in https://wiki2.dovecot.org/CompilingSource#Compiling_Dovecot_From_Sources without reference for dovecot.

2 1

Pigeonhole release v0.4.24.2
by Aki Tuomi 29 Aug '19

29 Aug '19

Hi! We are pleased to release Pigeonhole release v0.4.24.2 Tarball is available at https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.2… https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.2… Changes ------- * CVE-2019-11500: ManageSieve protocol parser does not properly handle NUL byte when scanning data in quoted strings, leading to out of bounds heap memory writes. Found by Nick Roessler and Rafi Rubin. --- Aki Tuomi Open-Xchange oy

2 2

Feature wishlist: Allow to hide client IP/host in submission service
by Sebastian Krause 28 Aug '19

28 Aug '19

Hi, In many mail setups a required feature (for privacy reasons) is to hide the host and IP of clients (in the "Received" header) that use the authenticated submission over port 587. In Postfix that's possible (https://serverfault.com/q/413533/86332) but not very nice to configure especially if you only want want to strip the Received header for port 587 submissions, but not on port 25. As far as I can see this configuration is not possible at all in the Dovecot submission server because the function which adds the Received header with the client's IP address (smtp_server_transaction_write_trace_record) is always called in submission-commands.c. It would be very useful if the submission server could anonymize the client with a single configuration option, then all the Postfix configuration mess (and using SASL) could be skipped by simply using the Dovecot submission server instead. The anonymization would work by replacing the client's EHLO host with "submission" and the IP address with 127.0.0.1. In full the Received header would look something like this where the first line is always the same: Received: from submission (unknown [127.0.0.1]) by mail.example.com with ESMTPSA id 8bV9D+51Yl1FOwAA1ctoJQ (envelope-from <john(a)example.com>) for <jane(a)example.com>; Sun, 25 Aug 2019 13:50:06 +0200 Sebastian

4 6

Pigeonhole release v0.5.7.2
by Aki Tuomi 28 Aug '19

28 Aug '19

Hi! We are pleased to release Pigeonhole release v0.5.7.2 Tarball is available at https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.7.2.… https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.7.2.… Binary packages are available at https://repo.dovecot.org/ Changes ------- * CVE-2019-11500: ManageSieve protocol parser does not properly handle NUL byte when scanning data in quoted strings, leading to out of bounds heap memory writes. Found by Nick Roessler and Rafi Rubin. --- Aki Tuomi Open-Xchange oy

1 0

Dovecot release v2.2.36.4
by Aki Tuomi 28 Aug '19

28 Aug '19

Hi! We are pleased to release Dovecot release v2.2.36.4 Tarball is available at https://dovecot.org/releases/2.2/dovecot-2.2.36.4.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.36.4.tar.gz.sig Binary packages are available at https://repo.dovecot.org/ Changes ------- * CVE-2019-11500: IMAP protocol parser does not properly handle NUL byte when scanning data in quoted strings, leading to out of bounds heap memory writes. Found by Nick Roessler and Rafi Rubin. --- Aki Tuomi Open-Xchange oy

1 0

Dovecot release v2.3.7.2
by Aki Tuomi 28 Aug '19

28 Aug '19

Hi! We are pleased to release Dovecot release v2.3.7.2 Tarball is available at https://dovecot.org/releases/2.3/dovecot-2.3.7.2.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.7.2.tar.gz.sig Binary packages are available at https://repo.dovecot.org/ Changes ------- * CVE-2019-11500: IMAP protocol parser does not properly handle NUL byte when scanning data in quoted strings, leading to out of bounds heap memory writes. Found by Nick Roessler and Rafi Rubin. --- Aki Tuomi Open-Xchange oy

1 0

unsubscrib
by Carlos Xavier 27 Aug '19

27 Aug '19

1 0

Group emails based on custom header
by Giovanni Mancuso 27 Aug '19

27 Aug '19

Hi, Can i "group by" e-mails based on custom header in imap? According to my experience if i use "XX UID SEARCH INTHREAD REFS HEADER myheader myvalue" i receive emails UID gathers by HEADER+VALUE, but in this way i need to fetch all emails using several imap SEARCH. Has dovecot any features that would help me do this? Thank you!!

2 1

doveadm mailbox handling for directory only
by sch tel 27 Aug '19

27 Aug '19

1 1

non-terminating processes
by Randy Bush 26 Aug '19

26 Aug '19

FreeBSD psg.com 11.3-RELEASE-p3 FreeBSD 11.3-RELEASE-p3 dovecot 2.3.6 (7eab80676) (latest from binary package system) symptom: multiple imap4s users complain that they can not fetch mail stopping and restarting dovecot is a temporary workaround dovenull 3713 0.0 0.0 11036 6816 - I 02:27 0:00.17 dovecot/imap-login user19 3714 0.0 0.0 9464 4756 - S 02:27 0:00.46 dovecot/imap dovenull 6261 0.0 0.0 11036 6812 - I 02:47 0:00.12 dovecot/imap-login dovenull 6262 0.0 0.0 11036 6804 - I 02:47 0:00.09 dovecot/imap-login dovenull 6263 0.0 0.0 11036 6804 - I 02:47 0:00.08 dovecot/imap-login user00 6264 0.0 0.0 9476 4924 - S 02:47 0:00.27 dovecot/imap user00 6265 0.0 0.0 9464 5444 - S 02:47 0:00.91 dovecot/imap user1 6266 0.0 0.0 9484 4636 - S 02:47 0:00.16 dovecot/imap dovenull 6277 0.0 0.0 11036 6804 - I 02:47 0:00.08 dovecot/imap-login user1 6279 0.0 0.0 9940 5096 - S 02:47 0:00.69 dovecot/imap dovenull 54595 0.0 0.0 11036 6916 - I 09:24 0:00.04 dovecot/imap-login dovenull 54596 0.0 0.0 11036 6916 - I 09:24 0:00.04 dovecot/imap-login user19 54597 0.0 0.0 9464 4784 - S 09:24 0:00.06 dovecot/imap user19 54598 0.0 0.0 9468 4676 - S 09:24 0:00.05 dovecot/imap dovenull 67450 0.0 0.0 11036 6924 - I 11:13 0:00.05 dovecot/imap-login userid0 67453 0.0 0.0 9488 4844 - S 11:13 0:00.05 dovecot/imap dovecot 68853 0.0 0.0 11484 6920 - S 11:29 0:00.32 dovecot/auth dovenull 74048 0.0 0.0 11036 6916 - I 12:15 0:00.03 dovecot/imap-login user54 74050 0.0 0.0 9552 4944 - I 12:15 0:00.02 dovecot/imap dovenull 74054 0.0 0.0 11036 6916 - I 12:15 0:00.03 dovecot/imap-login user54 74056 0.0 0.0 9492 5152 - I 12:15 0:00.06 dovecot/imap dovenull 74582 0.0 0.0 11036 6932 - S 12:20 0:00.07 dovecot/imap-login user19 74586 0.0 0.0 13572 7632 - S 12:20 0:04.14 dovecot/imap dovenull 74670 0.0 0.0 11036 6932 - S 12:21 0:00.05 dovecot/imap-login user01 74674 0.0 0.0 16768 6500 - S 12:21 0:02.33 dovecot/imap dovenull 74770 0.0 0.0 11036 6932 - S 12:21 0:00.05 dovecot/imap-login user01 74772 0.0 0.0 11500 5756 - S 12:21 0:00.08 dovecot/imap dovenull 74782 0.0 0.0 11036 6932 - I 12:21 0:00.04 dovecot/imap-login user01 74786 0.0 0.0 9460 5516 - I 12:21 0:00.05 dovecot/imap dovenull 74893 0.0 0.0 11036 6936 - I 12:22 0:00.04 dovecot/imap-login id0 74894 0.0 0.0 10644 5552 - S 12:22 0:00.05 dovecot/imap dovenull 74952 0.0 0.0 11036 6928 - I 12:23 0:00.03 dovecot/imap-login id0en 74954 0.0 0.0 9480 4900 - S 12:23 0:00.05 dovecot/imap dovenull 74958 0.0 0.0 11036 6916 - I 12:23 0:00.03 dovecot/imap-login id002 74959 0.0 0.0 9452 4756 - S 12:23 0:00.04 dovecot/imap dovenull 74961 0.0 0.0 11036 6916 - I 12:23 0:00.03 dovecot/imap-login id0 74962 0.0 0.0 9572 5088 - S 12:23 0:00.05 dovecot/imap dovenull 74964 0.0 0.0 11036 6916 - I 12:23 0:00.03 dovecot/imap-login id0 74966 0.0 0.0 9528 4892 - S 12:23 0:00.02 dovecot/imap dovenull 76400 0.0 0.0 11036 6916 - I 12:35 0:00.03 dovecot/imap-login user19 76401 0.0 0.0 9468 4804 - I 12:35 0:00.01 dovecot/imap root 76686 0.0 0.0 11484 7072 - S 12:38 0:00.37 dovecot/auth -w dovenull 77507 0.0 0.0 11036 6940 - I 12:45 0:00.16 dovecot/imap-login user5 77511 0.0 0.1 69164 12120 - I 12:45 0:00.49 dovecot/imap dovenull 78745 0.0 0.0 11036 6932 - S 12:56 0:00.05 dovecot/imap-login dovenull 78748 0.0 0.0 11036 6932 - S 12:56 0:00.06 dovecot/imap-login user5 78761 0.0 0.0 9476 5268 - S 12:56 0:00.12 dovecot/imap user5 78766 0.0 0.0 9492 5212 - S 12:56 0:00.12 dovecot/imap dovenull 78776 0.0 0.0 11036 6916 - S 12:56 0:00.03 dovecot/imap-login usr4 78777 0.0 0.0 9452 4564 - I 12:56 0:00.01 dovecot/imap root 88537 0.0 0.0 7940 1648 - Ss 00:51 0:04.00 /usr/local/sbin/dovecot -c /usr/local/etc/dovecot/dovecot.conf dovecot 88538 0.0 0.0 7880 1832 - S 00:51 0:01.04 dovecot/anvil root 88539 0.0 0.0 7880 1820 - S 00:51 0:00.86 dovecot/log dovenull 88540 0.0 0.0 11036 3992 - S 00:51 0:00.10 dovecot/imap-login root 88541 0.0 0.0 8008 3176 - S 00:51 0:04.18 dovecot/config dovecot 88542 0.0 0.0 7880 2592 - S 00:51 0:01.57 dovecot/stats dovenull 88544 0.0 0.0 11036 4088 - S 00:51 0:00.16 dovecot/imap-login dovenull 88545 0.0 0.0 11036 4064 - S 00:51 0:00.17 dovecot/imap-login dovenull 88546 0.0 0.0 11036 4016 - I 00:51 0:00.11 dovecot/imap-login user00 88547 0.0 0.0 9476 4156 - S 00:51 0:00.45 dovecot/imap usr9 88548 0.0 0.0 9460 4168 - S 00:51 0:00.49 dovecot/imap user1 88551 0.0 0.0 9452 3148 - S 00:51 0:00.22 dovecot/imap dovenull 88557 0.0 0.0 11036 4024 - I 00:52 0:00.11 dovecot/imap-login user17 88561 0.0 0.0 9472 3128 - S 00:52 0:00.22 dovecot/imap user17 88565 0.0 0.0 9472 3120 - S 00:52 0:00.23 dovecot/imap dovenull 88576 0.0 0.0 11036 3776 - I 00:52 0:00.18 dovecot/imap-login user19 88579 0.0 0.0 9604 2872 - S 00:52 0:00.40 dovecot/imap clues? just installing 2.3.7 from source to see if that helps randy

2 2

sometimes no shared cipher after upgrade from 2.2 to 2.3
by Kristijan Savic - ratiokontakt GmbH 23 Aug '19

23 Aug '19

We recently upgraded from dovecot 2.2 to 2.3.7.1-1 Not many, but some users are experiencing difficulties. The dovecot directors log: Aug 21 14:28:49 director01 dovecot: pop3-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=redacted, lip=10.0.0.120, TLS handshaking: SSL_accept() failed: error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher, session=<EeoTt5+QXwVUl87W> Any ide what could be causing it? Thanks, Kristijan

4 6

Trying to install Mailcrypt, receive completely blank emails
by sewing 22 Aug '19

22 Aug '19

Hi - perhaps someone can help me. Starting from a good and well-functioning mailserver setup, I have installed MailCrypt as per the instructions (I think) to have the per-user passworded keys setup. dovecot.conf /Added:/ mail_attribute_dict = file:%h/Maildir/dovecot-attributes mail_plugins = $mail_plugins mail_crypt dovecot-sql.conf.ext /commented this/ #password_query = SELECT email as user, password FROM virtual_users WHERE email='%u'; /Added this/ password_query = SELECT \ email as user, password, \ '%w' AS userdb_mail_crypt_private_password \ FROM virtual_users WHERE email='%u'; 90-plugin.conf /Updated this section/ plugin { mail_crypt_curve = secp521r1 mail_crypt_save_version = 2 /Have also tried all configurations this option set /#mail_crypt_require_encrypted_user_key = yes } /The user is in the mailserver SQL database:/ | user | password | userdb_mail_crypt_private_password | +----------------------+------------------------------------------------------------------------------------------------------------+------------------------------------+ | user@domain | 4t63ttt36tttttt3rt6r763r76t8998t858t4y48ht4huu4hti.76876t847t47yt4ty478yt4wgwygfwffweggggggggggwy8yey83//FElgiApZU. | %w /I have reissued the keys as other problem resolutions have instructed to do, and I can see the new keys are active./ doveadm -o plugin/mail_crypt_private_password=(same password as user@domain when created in SQL) mailbox cryptokey generate -u user@domain -UR /I have restarted dovecot and postfix each time./ /I then send an email either from the user@domain > user@domain OR otheruser@otherdomain > user@domain from Outlook. Authentication is fine (POP and SMTP). No errors appear in any logs - the logs show the mail as being received and I can see the mail in the user@domain /cur folder. If I try to Postcat any of these messages I get:/ postcat '1*********2.M**********3.(host),S=633,W=649:2,S' *** ENVELOPE RECORDS 1*********2.M*********3.(host),S=633,W=649:2,S *** message_size: YPTED postcat: fatal: invalid size record: YPTED??? */Within a minute or so I receive the email in the Outlook Inbox - except it is completely empty of anything. There is no TO / FROM/ SUBJECT / Body or even Routing information. See screencaps from Outlook/* <http://dovecot.2317879.n4.nabble.com/file/t5785/message_list_view.jpg> <http://dovecot.2317879.n4.nabble.com/file/t5785/empty-emails.jpg> /This happens with existing user mailboxes and new test mailboxes I create. If I deactivate Mailcrypt all mailboxes/user-accounts work fine. Any ideas??? I would like to get the working - thanks in advance for your expertise and time!/ Graham -- Sent from: http://dovecot.2317879.n4.nabble.com/

1 0

imapsieve suddenly not working anymore
by Thomas Stein 21 Aug '19

21 Aug '19

Hello one and all. Dovecot version 2.3.7.1 I've configured imapsieve like https://wiki.dovecot.org/HowTo/AntispamWithSieve a while a go and it worked for years now. Suddenly i noticed moving mails to the spamfolder does not trigger the report-spam.sieve script anymore. sieve-test gives: ~/.maildir/.Spam/cur $ sieve-test /usr/share/dovecot/sieve/report-spam.sieve 1542388745.M99384P16720.meine-oma.de\,S\=8173\,W\=8373\:2\,S -D sieve-test(himbeere): Debug: sieve: Pigeonhole version 0.5.7.1 (db5c74be) initializing sieve-test(himbeere): Debug: sieve: include: sieve_global is not set; it is currently not possible to include `:global' scripts. sieve-test(himbeere): Debug: sieve: Sieve imapsieve plugin for Pigeonhole version 0.5.7.1 (db5c74be) loaded sieve-test(himbeere): Debug: sieve: Sieve Extprograms plugin for Pigeonhole version 0.5.7.1 (db5c74be) loaded debug: file storage: Using Sieve script path: /usr/share/dovecot/sieve/report-spam.sieve. debug: file script: Opened script `report-spam' from `/usr/share/dovecot/sieve/report-spam.sieve'. debug: Script binary /usr/share/dovecot/sieve/report-spam.svbin successfully loaded. debug: binary save: not saving binary /usr/share/dovecot/sieve/report-spam.svbin, because it is already stored. report-spam: error: the imapsieve extension cannot be used outside IMAP. sieve-test(himbeere): Info: final result: failed; resolved with successful implicit keep ~/.maildir/.Spam/cur $ I'm not sure the "the imapsieve extension cannot be used outside IMAP" is the error already or thats only because the sieve-test script. Any ideas on that? cheers, t.

1 3

maildir very dirty sync option
by Yousif Alkhateeb 20 Aug '19

20 Aug '19

Hello , I have an active passive dovecot setup with glusterfs as a mail storage and using maildirs, we used to have a problem when users with large mailboxes sync their folders. This caused the load average to increase in the server , after a while we have enabled the very_dirty_sync option in dovecot , things got better and the problem disappeared but we need to know if there is any thing else that we need to do or know about the very_dirty_sync option that may cause future problems . Thanks in advance

3 2

Dovecot and Oauth
by Michael Hallager 20 Aug '19

20 Aug '19

Hi all, I am considering expanding a mail server to support Oauth with Google. I have read through the following: https://wiki.dovecot.org/PasswordDatabase/oauth2 however, it doesn't work and appears to me to be missing important information, the least of which is API authorisation. Searching with Google, I can't find any more information beyond what amounts to C&P'ing of the above link. Has anyone successfully deployed Oauth with Google and could they please send me their config files? Thanks, Michael

2 1