similar to: Repository / builds for Debian "buster"?

Hello, I'm experiencing slow flags changes over IMAP IDLE: - If I start an IDLE session / command - Change the flags of some messages via another email app - Dovecot can take a minute or more to notify the IDLE connection about flags changes If I use another email app to add or remove a message, Dovecot sends that (EXISTS / EXPUNGE) instantly and also flushes the (so far delayed) flags

Support for Buster will be added once 10/buster is a stable release. We only provide builds for the current stable version, and the previous version, so Debian 8/jessie support will be dropped when this happens. But it is premature to do that now. michael > On March 31, 2019 at 6:04 AM Kostya Vasilyev via dovecot <dovecot at dovecot.org> wrote: > > > Speaking of

On 12 Mar 2019, at 10.21, Kostya Vasilyev via dovecot <dovecot at dovecot.org> wrote: > > It makes no difference if the IDLE connection does SELECT or SELECT (CONDSTORE) prior to going IDLE. > > But then as far as I know (?) - in Dovecot, once any connection uses CONDSTORE ever, even once, Dovecot creates data structures to track MODSEQ values, and those data structures are

Timo, On Tue, Mar 12, 2019, at 3:56 AM, Timo Sirainen via dovecot wrote: > On 10 Mar 2019, at 10.14, Kostya Vasilyev via dovecot <dovecot at dovecot.org> wrote: >> >> My mail is stored under ~/mail/.imap (not sure what this format is called), I mean not "single file mbox". >> >> I have not changed any IDLE related config settings: >> >>

Timo, On Wed, Mar 13, 2019, at 12:39 AM, Timo Sirainen wrote: > On 12 Mar 2019, at 10.21, Kostya Vasilyev via dovecot <dovecot at dovecot.org> wrote: >> >> It makes no difference if the IDLE connection does SELECT or SELECT (CONDSTORE) prior to going IDLE. >> >> But then as far as I know (?) - in Dovecot, once any connection uses CONDSTORE ever, even once,

Hello, I download and install it manual, this working now? waiting for next update to found out, yum is working correct again ;-) Thanks for answers, Am Sonntag, 31. M?rz 2019, 13:59:17 CEST schrieb Kostya Vasilyev via dovecot: > On Sun, Mar 31, 2019, at 2:30 PM, G?nther J. Niederwimmer via dovecot wrote: > > Hello, > > > > Am Samstag, 30. M?rz 2019, 21:36:12 CEST schrieb

On 17.4.2019 23.00, Kostya Vasilyev via dovecot wrote: > I'm not Aki but hope you don't mind... > > On Wed, Apr 17, 2019, at 10:42 PM, TG Servers via dovecot wrote: >> Hi, >> >> MariaDB documentation says it accepts OpenSSL cipher strings in its >> ssl_cipher parameters like ssl_cipher="TLSv1.2". >> This is also mentioned when creating or

Hi, I can no longer connect to Dovecot (IMAP). The connection is terminated by Dovecot after Client Helo. My server: Dovecot 2.3.3 Debian buster/sid Architecture: ppc My problems started in late August after upgrading Dovecot. SSL settings: ssl_dh = </etc/ssl/dh2048.pem ssl_min_protocol = TLSv1.2 ssl_cipher_list =

root at mx10:~# doveadm force-resync -u oleg.vasilyev at bgoperator.com noreply-05-08-2015 doveadm(oleg.vasilyev at bgoperator.com): Warning: fscking index file /srv/vmail/current/bgoperator.com/oleg.vasilyev/storage/dovecot.map.index doveadm(oleg.vasilyev at bgoperator.com): Warning: mdbox /srv/vmail/current/bgoperator.com/oleg.vasilyev/storage: rebuilding indexes doveadm(oleg.vasilyev at

Do you have a huge >4GB dovecot.index.cache file? > On 17 Nov 2015, at 13:04, Sergey Schwartz <sergey.schwartz at bgoperator.com> wrote: > > Gentlemen, > > imap hits the same problem > > Nov 17 14:02:06 mx10 dovecot: imap(oleg.vasilyev at bgoperator.com): Panic: file mail-index-util.c: line 37 (mail_index_uint32_to_offset): assertion failed: (offset <

Gents, I've just upgraded to the latest build of dovecot , now lmtp delivery process panics for just one user Nov 10 15:36:49 mx10 dovecot: lmtp(oleg.vasilyev at bgoperator.com): Panic: file str.c: line 22 (str_new_const): assertion failed: (str[len] == '\0') Nov 10 15:36:49 mx10 dovecot: lmtp(oleg.vasilyev at bgoperator.com): Panic: file str.c: line 22 (str_new_const):

On 23/06/17 18:23, Anton Vasilyev wrote: > The patch removes unnecessary return from void function. > > Found by Linux Driver Verification project (linuxtesting.org). > > Signed-off-by: Anton Vasilyev <vasilyev at ispras.ru> Reviewed-by: Juergen Gross <jgross at suse.com> Juergen

On 23/06/17 18:23, Anton Vasilyev wrote: > The patch removes unnecessary return from void function. > > Found by Linux Driver Verification project (linuxtesting.org). > > Signed-off-by: Anton Vasilyev <vasilyev at ispras.ru> Reviewed-by: Juergen Gross <jgross at suse.com> Juergen

Hello, Am Samstag, 30. M?rz 2019, 21:36:12 CEST schrieb Peter via dovecot: > On 30/03/19 10:56 PM, Gerald Galster via dovecot wrote: > > Maybe there is something wrong with his local yum/repo configuration. > > I'm tending to agree now. > > > CentOS 7 usually doesn't mix 32bit and 64bit packages anymore. > > > > Installiert: 2:dovecot-2.3.5-1.x86_64

Koshiro, --- Now, I changed Outlook setting of imap and I can see Draft, Trash, Sent and Sent Messages folders and I can see the mail files in there. However, I don't see mail files in the "cur or new" folder where is under .Sent Messages folder. --- Maybe Outlook isn't going to upload all old pre-existing Sent (etc) messages to server just from your setting the right server

Hai, ? Sorry for the Delay, bit overloaded with work, but the end is near. pff, finaly.. soon i take a long vacation.. ? Well, you know the drill.. Ubuntu 20.04 focal, is next. ? For the Raspbian guys, please try how the buster-samba412 works for you and let me know the results. Rapsbian will be last to build so if you in a need for the newer versions, use/try ?buster-samba412? !! and dont

Upgrading DC1 at site 3 (next site ;-)) I edited sources.list and van-belle.list (s/stretch/buster/g ...) apt-get update: ok apt-get upgrade: as well apt-get dist-upgrade: DANGER -> it tells me it would remove samba! Die folgenden Pakete werden ENTFERNT: libcurl3 libkdb5-8 libmariadbclient18 libnss-winbind libpam-winbind libsmbclient libuptimed0 python3-ldb python3-samba samba

On 3/14/19 9:55 AM, Patrick Cernko via dovecot wrote: > [...] the way we have configured exim, it neither needs reload or > restart but reads the certificate file every time it has to use it. What happens if you goof off in the middle of an opeartion, temporarily putting a wrong file instead of the new certificate, and exim starts delivering the new broken certificate right away ? or