similar to: Mail.app message numbering for deleted messages

We've been testing dovecot for a while and I noticed yesterday that imap crashes quite often. It seems to be about even with SIGABRT and SIGSEGV. This one was SIGSEGV. Our system is SuSE Linux 9.2, 2.6.11.5 kernel (also happened with an older 2.6 kernel). Dovecot version is 1.0-test64 and was compiled with: "./configure --prefix=/services/dovecot --disable-ipv6" It's using

I've got some of our busiest users now using Dovecot instead of UW-IMAP with mbox-format mailboxes and predominantly Outlook Express as the client. Doing some perfomance monitoring (with Solaris 8 process accounting), it looks like Dovecot needing to read only 30-50% of the disk blocks needed by UW-IMAP, but I was hoping for better! What seems to happen, is that most of the connections

On 21 March, 2018 - Aki Tuomi wrote: > Thank you for your thorough report, we'll look into it. Has anyone managed to reproduce this (using my transcript for example)? With mutt, I get this problem.. If I set 'imap_pipeline_depth=0' in .muttrc, I can't seem to reproduce it anymore. /Tomas -- Tomas Forsman, stric at cs.umu.se, http://people.cs.umu.se/stric/ `- SysAdmin at

Hello. I seem to have found a race condition, when setting flags on multiple emails rapidly. 5 commands including login to reproduce. Problem found using mutt in real world usage. Seems to happen both with UID STORE 1:3 and UID STORE 1,2,3 .. I have tried with the following packages, with a minimized config in a throwaway vm: https://packages.debian.org/stretch/dovecot-core Package:

I have Dovecot 1.0 in trial use by the IT staff, and have some locking questions Background, the mail server runs procmail, sendmail and NFS exports the user homedir and mailbox to a) a login shell host and b) a mailing list services host. It runs UWIMAP on the usual ports and dovecot on a arbitrary port number. Because of concern with NFS and file access contention. I have the following

Please I need some help using R to analyze my data. What I would like to do is to repeat the same basic process (e.g. linear regression between wood density and distance from pith) for at least 240 data subsets within the main data-frame. Within the main data-frame, these data subsets will be defined by three variables namely,  species, individual and core (i.e. 20 species, at least 6

Hello! I run the following environment: UW imapd pine sendmail procmail mbox format I migrated from UW imapd to dovecot. It is pretty faster than UW imapd. To ensure a compatible environment I did the following configuration changes in /etc/dovecot.conf: protocols = imaps default_mail_env = mbox:~:INBOX=/var/mail/%u mail_full_filesystem_access = yes mbox_read_locks = fcntl mbox_write_locks

I'm still collecting user feedback after moving from uw-imap to dovecot development release 1.1.rc3. What said in the subject seems the obvious result of an improper configuration. Office emails are configured and accessed on multiple clients with the same automatic filters, and sometimes the filtered emails get duplicated on the destination folder. The fact is that this was perfectly

I've got several users testing Dovecot IMAP at the moment, but some of them are also accessing their mail via UW-IMAP at other times. (I've warned them about accessing the same folder simultaneously via UW-IMAP and Dovecot!) In addition, we have special folders "AutoSpam" and "Trash" that pruned using Washington's "mailutil" automatically every so

Hi List, last time i did a lot of packaging and installing different versions of dovecot 1.0.x (rc not included ;) )and all was fine. Now a have a little problem. In this case it was an update from 1.0.13 to 1.1.1 Sometime it happens that 1 user out of x (more than 100) got this standardmessage for ~1 or ~2 thousend times in his mailbox (mbox) for example: >From MAILER_DAEMON Mon Sep 18

Hello, I've decided to switch from UW-IMAP to Dovecot and so installed 1.0.rc15-2 on a Debian/Etch system and started using it with the existing MBOX folders. My configuration is pretty much the default one, in particular I didn't touch to any of mbox_xxx options. The (hoped for) performance improvements were indeed quite noticeable and mostly it works just fine but I seem to have one

Hi, We are using mbox and UW IMAP, and are having issues because UW IMAP does not support multiple client access when you use NFS for the mail files. I've done some research (see the comments after my 2 questions below), and most of the other major IMAP servers simply don't support it (courier is about the only one that has a positive comment). How much testing have you done

Dear Dovecot list, I recently switched from uw-imapd to dovecot to manage my huge mbox files (about 1 GB). I now observe a very strange behavior, difficult to reproduce reliably, which might be related to some misunderstanding on my part on how either dovecot works or imap labeling works. What I call "labeling" is the fact of marking some e-mail, in my e-mail client (currently

hi list, i'm in the process of testing dovecot before a hopeful switchover from uw-imap/qpopper to dovecot, primarily to get off of the uw-imap/mbox combo and moved to Maildir. i think we've worked out the logistics to avoid any service downtime, with only a short window of a few minutes per user for when we convert from mbox to maildir format. however, during testing a few issues have

My Dovecot 2.2.16 server is interacting poorly with a variety of mail clients. The symptoms include disappearing messages, mismatched summaries, duplicated messages, and excessive full re-downloads. Dovecot 2.2.16 on FreeBSD 10.1-release r280247M ZFS is interacting suboptimally with various email clients. Output of "dovecot -n" further down. *Client Artifacts* Thunderbird 31.6

On Mon, 17 Feb 2003, Andreas Aardal Hanssen wrote: > >> It even recently included a POP server. What's the reasoning there? > >Someone wanted it so it'd be easy to run both POP3 and IMAP servers > >without having to configure them twice. I don't see any harm in it > >anyway, it took only few hours to write, it's optional and doesn't take >

Looking for a recommended package that handles prime number computations. Tried the following unsuccessfully: primeFactors() in the R.basic package failed to install. primes() and primlist are broken in Schoolmath pkg on CRAN. My analysis can be found here http://j.mp/9BNI9q Not sure what the procedure is for getting things fixed, so I've cross-posted to r-dev as well. --njg

Looking for a recommended package that handles prime number computations. Tried the following unsuccessfully: primeFactors() in the R.basic package failed to install. primes() and primlist are broken in Schoolmath pkg on CRAN. My analysis can be found here http://j.mp/9BNI9q Not sure what the procedure is for getting things fixed, so I've cross-posted to r-dev as well. --njg

I just migrated from a FreeBSD/Sendmail/UW-IMAP setup to RHEL 3/Postfix/Dovecot (1.0a5 currently). Both systems used Procmail as the final delivery agent (into inboxes or . Since the changeover, things have *mostly* been going ok, but I've been having some problems that I think are locking-related. I'm getting reports from users about IMAP hangs (mostly from Thunderbird). Sometimes I see

Hello! I run Dovecot on CentOS 4 (dovecot-1.1.4-0_81.el4), and I *also* run the "Alpine" mail system that comes with that OS. Alpine still writes out the 'FOLDER INTERNAL DATA' pseudo-message at the beginning of each user's mbox, but dovecot does not. I make use of that record as a simle/quick way to verify when a user actually last read their e-mail (for administrative