similar to: Corrupted index files

Hello, Has anyone succeeded on configuring and compiling Sieve capable Dovecot LDA on RHEL 4 x86_64 platform? I am having problems with configure script hanging on sed while creating Makefiles. # ./configure --with-dovecot=../dovecot .. checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking for library containing

Now that Redhat released GFS to GLP has anyone gotten around to test Dovecot on top of that? -- Tomi Hakala

http://dovecot.org/test/ I think this release should be quite stable one. - fixes parsing mails with header lines longer than 8192 bytes - cache file corruption fixes - fixed "corrupted offset in mbox file" errors - don't return extra INBOX replies in LIST Those mbox and cache problems were pretty tricky to figure out. Thanks to Tomi Hakala for tons of testing while I tried to

On 29/10/2020 15:22, Daniel Vetter wrote: > So ever since syzbot discovered fbcon, we have solid proof that it's > full of bugs. And often the solution is to just delete code and remove > features, e.g. 50145474f6ef ("fbcon: remove soft scrollback code"). > > Now the problem is that most modern-ish drivers really only treat > fbcon as an dumb kernel console until

Hello, I'm running an Debian etch box with unstable and ever since the last upgrade to dovecot, I've seen odd things. At times, I would see emails would go missing from the Inbox or other folders, and I couldn't move emails that were moved from the Inbox to another folder back into the Inbox. These have seen gone away since I removed all dovecot.* files and .index* files from my

Hi, On 24/09/2024 10:13, Thomas Zimmermann wrote: > Store instances of drm_fb_helper and struct omap_fbdev separately. > This will allow omapdrm to use the common fbdev client, which allocates > its own instance of struct drm_fb_helper. > > There is at most one instance of each per DRM device, so both can be > referenced directly from the omap and DRM device structures. A later

On Jan 20, 2008, at 12:15 PM, dovecot-request at dovecot.org wrote: > > Message: 5 > Date: Sun, 20 Jan 2008 15:48:09 +0200 > From: Timo Sirainen <tss at iki.fi> > Subject: [Dovecot] v1.1.beta14 released > To: dovecot at dovecot.org > Message-ID: <1200836889.12450.99.camel at hurina> > Content-Type: text/plain; charset="us-ascii" > >

Hello, Does dovecot require mysql in order to work? Fedora rpms are claiming mysql dependencies. I'm sure you're aware of the long-lived arguement of postgresql v. mysql. If it wasn't your intention to force this, then please snarl at Red Hat. If it was your intention, then grrrrr! Thanks for this product. I like it for it's speed and stability. Jim Edwards

I just upgraded my production box from 1.0-stable to 1.0.alpha1. I've noted some new errors in my dovecot logs: Aug 28 23:23:56 cliff dovecot: IMAP(rsferra): Corrupted index cache file /mail/mcad.edu/rsferra/Maildir/.Sent Items/dovecot.index.cache: indexid changed Aug 28 23:33:57 cliff dovecot: IMAP(acarr): Corrupted transaction log file /mail/mcad.edu/acarr/Maildir/.Deleted

Hi, We're trying out Dovecot to see if it's a good replacement for UW-imapd. It seems to be very slow in opening an mbox file, even after it's been indexed. (I mean way slower than UW) Here's some info on the system: Dovecot-1.0-test61 SuSE 8.1, Linux kernel 2.4 Using NFS to access mail. I've tried turning off mmap, using dotlocking, using fcntl locking (lockd, etc. are

Getting it otherwise to work, but I still can't get it to listen any SSL-ports. been testing: protocols = imap imaps pop3 pop3s listen = 193.65.59.150 ssl_listen = 193.65.59.150 doesn't help. with: ssl_disable = no of course. protocol imap { # Login executable location. login_executable = /usr/local/libexec/dovecot/imap-login # IMAP executable location mail_executable =

Cc: Tomi Valkeinen <tomi.valkeinen at ti.com> Cc: Laurent Pinchart <laurent.pinchart at ideasonboard.com> Signed-off-by: Emil Velikov <emil.l.velikov at gmail.com> --- include/uapi/drm/omap_drm.h | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/include/uapi/drm/omap_drm.h b/include/uapi/drm/omap_drm.h index 38a3bd8..407cb55 100644 --- a/include/uapi/drm/omap_drm.h +++

Without waiting for hw_done, previous atomic updates may dereference the wrong state and cause a lot of confusion. The real fix is fixing all obj->state to use the accessor macros, but for now wait indefinitely and interruptibly. Cc: Boris Brezillon <boris.brezillon at free-electrons.com> Cc: David Airlie <airlied at linux.ie> Cc: Daniel Vetter <daniel.vetter at intel.com>

I found the proxy performance page in the Wiki. It's interesting to see such good performance for the proxy! However, I was trying to duplicate the tests and am not clear how. Anyone know what a typical test setup would look like? I need to document/test that I can setup a proxy able to handle 100-200 sessions per second which the folks around here are skeptical of. I emailed Tomi directly

Hi, does anyone know where Timo is around lately? I haven't seen a post from him for some weeks now and "normally" Timo is quite active when it comes to supporting his 'dovecot' warp drive :-) Udo Rader -- bestsolution.at EDV Systemhaus GmbH http://www.bestsolution.at -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type:

Simply put: When will Oggenc accept input files with higher resolution than 16-bit? Thumbs up to all the developers - the sound quality of Vorbis just keeps amazing me! I only use Ogg Vorbis when distributing my music today. Cheers, - Tomi <p><p><p><p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To

On Tue, Nov 20, 2018 at 06:13:42PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä <ville.syrjala at linux.intel.com> > > Make life easier for drivers by simply passing the connector > to drm_hdmi_avi_infoframe_from_display_mode() and > drm_hdmi_avi_infoframe_quant_range(). That way drivers don't > need to worry about is_hdmi2_sink mess. > > Cc: Alex Deucher

Hi Ville, Thank you for the patch. On Tuesday, 20 November 2018 18:13:42 EET Ville Syrjala wrote: > From: Ville Syrjälä <ville.syrjala at linux.intel.com> > > Make life easier for drivers by simply passing the connector > to drm_hdmi_avi_infoframe_from_display_mode() and > drm_hdmi_avi_infoframe_quant_range(). That way drivers don't > need to worry about

Op 30-06-17 om 15:56 schreef Daniel Vetter: > On Wed, Jun 28, 2017 at 03:28:11PM +0200, Maarten Lankhorst wrote: >> We want to change swap_state to wait indefinitely, but to do this >> swap_state should wait interruptibly. This requires propagating >> the error to each driver. All drivers have changes to deal with the >> clean up. In order to allow easy reverting, the

On Thu, Nov 29, 2018 at 10:08:07AM +0100, Andrzej Hajda wrote: > On 21.11.2018 19:19, Laurent Pinchart wrote: > > Hi Ville, > > > > Thank you for the patch. > > > > On Tuesday, 20 November 2018 18:13:42 EET Ville Syrjala wrote: > >> From: Ville Syrjälä <ville.syrjala at linux.intel.com> > >> > >> Make life easier for drivers by