similar to: v2.2.22 release candidate released

http://dovecot.org/releases/2.2/dovecot-2.2.22.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.22.tar.gz.sig + Added doveadm HTTP API: See http://wiki2.dovecot.org/Design/DoveadmProtocol/HTTP + virtual plugin: Mailbox filtering can now be done based on the mailbox metadata. See http://wiki2.dovecot.org/Plugins/Virtual + stats: Added doveadm stats reset to reset global stats. + stats:

http://dovecot.org/releases/2.2/dovecot-2.2.22.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.22.tar.gz.sig + Added doveadm HTTP API: See http://wiki2.dovecot.org/Design/DoveadmProtocol/HTTP + virtual plugin: Mailbox filtering can now be done based on the mailbox metadata. See http://wiki2.dovecot.org/Plugins/Virtual + stats: Added doveadm stats reset to reset global stats. + stats:

On 31/03/2016 02:06, Stephan Bosch wrote: > Hi, > > Op 3/30/2016 om 5:34 PM schreef Juan C. Blanco: >> Hello, I supose that a new version of pigeonhole is on the way because >> version 0.4.13 does not compile against dovecot 2.2.23 >> >> This is the error that I get >> >> gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../.. >>

I'm trying to understand autoexpunge, but the documentation is just not clear. Hopefully, someone can clear up a few questions. http://wiki.dovecot.org/MailboxSettings says the following: autoexpunge=<time>: (v2.2.20+) Automatically at user deinitialization expunge all mails in this mailbox whose saved-timestamp is older than <time> (e.g. autoexpunge=30d). This removes the

Hello, I supose that a new version of pigeonhole is on the way because version 0.4.13 does not compile against dovecot 2.2.23 This is the error that I get gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../.. -I../../../src/lib-sieve -I../../../src/lib-sieve/util -I../../../src/lib-sieve/plugins/environment -I/home/jc/rpmbuild/BUILD/dovecot-2.2.23/src/imap

Always I have the following lines in my mail.log (at startup and service restart) dovecot: master: Warning: Killed with signal 15 (by pid=3156 uid=0 code=kill) dovecot: log: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) dovecot: master: Dovecot v2.2.22 (fe789d2) starting up for imap, pop3 (core dumps disabled) dovecot -n output is below: # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf

Hi, Have anyone else experienced problems using Dovecot with the mail app in beta releases of iOS/iPadOS 13? TLS is failing for my, it have worked fine for years and I am on the latest Dovecot version now, it works fine with older clients but not with the ones upgraded: Sep 04 19:49:16 imap-login: Debug: SSL: where=0x10, ret=1: before/accept initialization Sep 04 19:49:16 imap-login: Debug:

Hi. Always the below log appraring log under /var/log/mail.log Is this right or How to resolve it. Ubuntu 16.04.2 LTS server edition Mar 13 06:13:20 home dovecot: master: Dovecot v2.2.22 (fe789d2) starting up for imap, pop3 (core dumps disabled) Mar 13 06:13:30 home postfix/master[1495]: daemon started -- version 3.1.0, configuration /etc/postfix dovecot -n output

I can get messages without SSL with no problems. but i need to setup server accept only SSL secured connections. I think my configuration is very proper, but cant find "obvious" problem. Postfix 2.3.3 + dovecot 2.0.13-1_129.el5 + PostfixAdmin 2.3.3 I made own CA. configured postfix and dovecot with same cert key ca. Same public cert i gave for client just converted it to PKCS#12. I cant

Recently thunderbird and Dovecot IMAPS cannot agree on SSL however Evolution, on the exact same system, is working fine with the same accounts. Tried recreating the Dovecot cert and also the thunderbird accounts from scratch. The OpenSSL raw client works fine as well. Would someone also confirm the openssl commands to create a selfsigned cert for dovecot imaps. They cert created does work

Hello, This is a selfsigned cert. Both of the below methods were used. May I ask for 1. pointer to info setting up "intermediate certs" and where the certfile goes? The objective is to generate a self-signed cert and use it for just internal use with IMAPS dovecot. Separately, what are your thoughts as to why evolution works and thunderbird does not? Thank you, ==1 openssl

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 18 December 2018 at 02:30 Adi Pircalabu via dovecot < <a href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>> wrote: </div>

Hi! We are working on including JMAP support to Dovecot. At this moment I cannot give any promise for exact version, but hopefully it will be part of v2.3 Aki Tuomi Dovecot Oy > On November 26, 2016 at 11:17 PM Andrew Jones <andrew at mykolab.com> wrote: > > > Hi Marcus > > Thanks for your helpful reply. > > Do you know what is going on with JMAP development

Unfortunately we have not been able to work on this much, but also the JMAP spec was until very recently still being worked. We have open dialogue with the Thunderbird people, they haven't so far indicated any pressing need for JMAP in Dovecot. This said, JMAP is still very much in our roadmap. Perhaps just not as close as I initially thought. Aki On 21.5.2019 16.29, Tanstaafl via dovecot

Postfix debug peer logging Dec 18 17:08:11 mail postfix/submission/smtpd[10626]: > server.example.org[XX.XX.XX.XX]: 250 2.1.5 Ok Dec 18 17:08:11 mail postfix/submission/smtpd[10626]: watchdog_pat: 0x55ef4ec020180 Dec 18 17:08:11 mail postfix/submission/smtpd[10626]: vstream_fflush_some: fd 10 flush 28 Dec 18 17:08:11 mail postfix/submission/smtpd[10626]: vstream_buf_get_ready: fd 10 got 15 Dec

Thanks for your answer, Timo! :) I send to you my configoration for reproducing. Please, follow the link, because configuration is a very big, there will be more easy to read and understand My configuration Dovecot 2.2.19 <http://www.heypasteit.com/clip/28CW> Below the same my configuration Dovecot 2.2.19 here. BEGIN of configuration --------------------- # doveconf -n # 2.2.19:

Hello, my dovecot installation has been working fine against AD till we upgrade from AD 2003 to AD 2008. As http://wiki2.dovecot.org/AuthDatabase/LDAP said, now I'm not able to connect AD through 389 port. The port 3268 works fine though. (...) Sep 7 19:02:05 <dovecotServer> dovecot: imap-login: Error: master(imap): Auth request timed out (received 0/12 bytes) Sep 7 19:02:05

Hello, After client (Thunderbird, now version 31.0) updated today, it stopped connecting to Dovecot IMAP4S. The infamous "SSL alert number 42" is reported. Mail server uses local (created for intranet) CA certificate as root. I would appreciate pieces of advice on how to handle that without enabling plaintext authentication over insecure channels. Other intranet services work with

On Wed, May 22, 2019, at 23:43, Tanstaafl via dovecot wrote: > On Wed May 22 2019 05:44:59 GMT-0400 (Eastern Standard Time), Aki Tuomi > via dovecot <dovecot at dovecot.org> wrote: > > Unfortunately we have not been able to work on this much, but also the > > JMAP spec was until very recently still being worked. We have open > > dialogue with the Thunderbird people,

On 2016-11-26 11:07:00 -0800, WJCarpenter wrote: > I don't know the answer to that question, but I am curious about something. > What client are you thinking about using with JMAP? I haven't found much. > (And much of the demo stuff at jmap.io seems to be busted in various ways.) roundcube-next builds on top of it. darix -- openSUSE - SUSE Linux is my linux