similar to: Hibernation disabled when mailbox selected

> On 18 Oct 2015, at 20:25, Timo Sirainen <tss at iki.fi> wrote: > > On 18 Oct 2015, at 05:20, Joseph Tam <jtam.home at gmail.com> wrote: >> >> >> After setting imap_hibernate_timeout to 60s, I could not find any >> hibernated connections after a few hours. I tested hibernation and made >> an observation: IDLE'd imap sessions only

On 18 Oct 2015, at 05:20, Joseph Tam <jtam.home at gmail.com> wrote: > > > After setting imap_hibernate_timeout to 60s, I could not find any > hibernated connections after a few hours. I tested hibernation and made > an observation: IDLE'd imap sessions only hibernate if they don't have > a mailbox SELECT'd, otherwise they never hibernate. > > Is this

* Timo Sirainen <tss at iki.fi> 2015.08.25 22:21: > There's no good default setting here. It depends on your userdb settings and/or mail_uid setting. So for example if your imap processes are running as vmail user, you should set service imap-hibernate { unix_listener imap-hibernate { user = vmail } }. Then again if you are using system users (or otherwise multiple UIDs) it gets more

http://dovecot.org/releases/2.2/dovecot-2.2.19.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.19.tar.gz.sig * pop3_deleted_flag has been broken since v2.2.10. Using it would cause buffer overflows, which could be exploitable. However, this bug would have become visible quite soon after users had deleted some POP3 mails, because the pop3 processes would have started crashing all the

http://dovecot.org/releases/2.2/dovecot-2.2.19.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.19.tar.gz.sig * pop3_deleted_flag has been broken since v2.2.10. Using it would cause buffer overflows, which could be exploitable. However, this bug would have become visible quite soon after users had deleted some POP3 mails, because the pop3 processes would have started crashing all the

Open-Xchange Security Advisory 2021-01-04 Product: Dovecot Vendor: OX Software GmbH Internal reference: DOP-2009 (Bug ID) Vulnerability type: CWE-150: Improper Neutralization of Escape, Meta, or Control Sequences Vulnerable version: 2.2.26-2.3.11.3 Vulnerable component: imap Report confidence: Confirmed Solution status: Fixed by Vendor Fixed version: 2.3.13 Vendor notification: 2020-08-17

Open-Xchange Security Advisory 2021-01-04 Product: Dovecot Vendor: OX Software GmbH Internal reference: DOP-2009 (Bug ID) Vulnerability type: CWE-150: Improper Neutralization of Escape, Meta, or Control Sequences Vulnerable version: 2.2.26-2.3.11.3 Vulnerable component: imap Report confidence: Confirmed Solution status: Fixed by Vendor Fixed version: 2.3.13 Vendor notification: 2020-08-17

On 02 Oct 2015, at 23:28, Robert Schetterer <rs at sys4.de> wrote: > > Am 02.10.2015 um 18:13 schrieb Timo Sirainen: >> + Added imap-hibernate processes (see imap_hibernate_timeout setting). >> IDLEing IMAP connections can be hibernated, which saves memory. > > Hm, i have > > Couldn't hibernate imap client: Couldn't export state: COMPRESS enabled

I am running Samba 3.5.5 on Solaris 10. I have one machine as a PDC, one as a BDC. If I logon to the domain from a Windows 7 Pro (64-bit) laptop, hibernate the machine, unplug the network cable and wake the machine, I can not unlock the screen. I will get the message "There are currently no logon servers available to service the logon request." Other users have reported this.

http://hg.dovecot.org/dovecot-2.2/rev/64c73e6bd397 Today I finally committed the "imap-hibernate" feature that I first started developing about a year ago (and had been thinking about for several years before that). The main purpose here is to reduce the number of imap processes and the amount of memory they use by moving IDLEing connections into imap-hibernate processes where they are

* Teemu Huovila <teemu.huovila at dovecot.fi> 2015.08.27 13:58: > Did you specify a value other than zero for 'imap_hibernate_timeout'? Yes I did: $ doveconf imap_hibernate_timeout imap_hibernate_timeout = 1 mins I sometimes see one imap-hibernate process (only one), but several imap processes active which should be idling... -------------- next part -------------- A non-text

Hello, These patches are an initial attempt at supporting hibernation for virtio drivers. The default configuration of event_index=on doesn't work; i.e. restore from a hibernated image only works if the devices have event_index support turned off. I have not yet dug into this, but is most likely due to some state not being sync'ed. This could be related to the hack that is patch 3.

Hello, These patches are an initial attempt at supporting hibernation for virtio drivers. The default configuration of event_index=on doesn't work; i.e. restore from a hibernated image only works if the devices have event_index support turned off. I have not yet dug into this, but is most likely due to some state not being sync'ed. This could be related to the hack that is patch 3.

I tested with FreeBSD 11 and it worked just fine... did you follow https://wiki.dovecot.org/IMAPServer/Hibernation this to set it up? Aki > On 23 October 2018 at 10:15 Alex <alex at jili.ga> wrote: > > > Aki, is it configuration error or dovecot bug ? > Can I use imap-hibernate on FreeBSD ? > > > > Alex ????? 2018-10-19 10:31: > > Yes, > > >

Hello, Dovecot 2.2.27 (Debian Jessie backports). When issuing a "doveadm kick" for a specific user I was greeted by: --- "warning: other connections would also be kicked from following users:" --- and a list of 22odd thousand users. As it turns out, kick wants to smack the hibernation proces(ses) that have hibernated sessions for this user, obviously the wrong approach here.

Hello, as some may remember, we're running very dense IMAP cluster here, in excess of 50k IMAP sessions per node (current record holder is 68k, design is for 200k+). The first issue we ran into was that the dovecot master process (which is single thread and thus a bottleneck) was approaching 100% CPU usage (aka using a full core) when trying to spawn off new IMAP processes. This was

Yes, After I changed mode and user/group Oct 18 19:17:50 server dovecot: imap(email at example.com)<57613><VVXuZ4N4avOASO/q>: Error: kevent(-1) for notify remove fail ed: Bad file descriptor Oct 18 19:17:50 server dovecot: imap(email at example.com)<57613><VVXuZ4N4avOASO/q>: Error: close(-1) for notify remove failed: Bad file descriptor Oct 18 19:17:50 server dovecot:

Hello! I tried to use imap-hibernate. But errors in maillog: Oct 19 05:14:24 server dovecot: imap(email at example.com)<67125><Lu7ndYt4n8aASO/q>: Error: kevent(-1) for notify remove failed: Bad file descriptor Oct 19 05:14:24 server dovecot: imap(email at example.com)<67125><Lu7ndYt4n8aASO/q>: Error: close(-1) for notify remove failed: Bad file descriptor Oct 19

We've been using hibernate for about half a year with no ill effects. There were various logged errors in earlier versions of dovecot, but even with those, we never heard a reported customer-side error (almost always when transitioning from hibernate back to regular imap; in the case of those errors, presumably the mail client just reconnected silently). For no particular reason besides

Cit?t Aki Tuomi <aki.tuomi at open-xchange.com>: >> On 28 March 2019 17:46 azurit--- via dovecot < dovecot at dovecot.org> >> wrote: >> >> >> >> >> Hi, >> >> >> does hibernation works well with proxy? Are proxy connections >> hibernated or not? >> >> >> azur > > hibernation