similar to: 1.0-test46

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

We're in the process of moving to Dovecot. We're currently running UW-IMAP live with Dovecot 1.0rc7 on alternate ports for testing. We're set to switch to Dovecot tomorrow morning, and I'm sure I'll have lots of stupid questions once that happens. So I guess you can consider this message an introduction as well as a preemptive apology. Our setup: our mailserver is a

Thank you for your thorough report, we'll look into it. Aki On 20.03.2018 16:56, Tomas Forsman wrote: > 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

Trying to figure out how to convert an existing mbox system to maildir Below is my dovecot.conf file. Tried adding this at the bottom of the file and nothing happens. plugin { convert_mail = mbox:/vhome/%d/home/%n:INBOX=/vhome/%d/home/%n/INBOX convert_skip_broken_mailboxes=yes } What am I doing wrong? ## Dovecot 1.0 configuration file # '#' character and everything after it is

I just switched in a hurry one of our mailbox servers from UW-imapd to Dovecot in an attempt to address performance and stability problems. This server hosts ~5500 accounts, ~2000 are daily used, ~600 simultaneous IMAP connexions in rush hours, and lots of POP ones. Some accounts may be accessed simultaneously with IMAP and POP. The system is : - Debian Sarge (x86 with amd64 kernel) - MBOX files

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

Hi all, After I posted yesterday, I'm still struggling with dovecot 1.0beta1 I installed it on openbsd with no problem. But I can't get it to authenticate plaintext on Unixware. I had to add two include files <sys/types.h> and <sys/mkdev.h> in compat.h because minor and major where undefined on unixware. I doubt that could fail... What's wrong with that conf: ##

Hi, I'm trying to get dovecot set up better. I am using 1.0alpha3. It takes a long long time to move messages for some reason. It seems it may be a timeout thing, because neither the client or server is using any cpu time or disk i/o or network to speak of. (To move maybe 400 messages, it seems to take maybe half an hour, maybe longer.) With alpha 2 I was getting messages from

I'm trying to set up a pop3 server for a project for class, but it keeps giving me the following error: Error: Login user doesn't exist: dovecot Fatal: Invalid configuration in /usr/local/etc/dovecot.conf And I have no clue what's wrong. I've look and modifying the dovecot.conffile for days and I am not having any luck. ## Dovecot configuration file # If you're in a

Hi, I'm experiencing there assertions in the mail log (about 8 times during the last 2 days): Oct 5 11:20:51 web dovecot: POP3(xxxxx): file mbox-lock.c: line 493 (mbox_lock): assertion failed: (lock_type == F_RDLCK || ibox->mbox_lock_type != F_RDLCK) What is it? I'm running 1.0-test46 and sendmail on FC2. This is in dovecot.conf: #fcntl_locks_disable = no #mbox_read_locks = fcntl

Timo, I nervously ran rc6 plus the patch: http://dovecot.org/tmp/ssl-proxy-openssl.c on my Solaris 9 box, in production, this morning. My dovecot.conf file is attached. Like similar reports for BSD, rc6 fell over after an hour and a half. The final syslog message was: dovecot: [ID 920869 mail.error] Login process died too early - shutting down I rolled back to rc2 for production. BTW,

Running current CVS HEAD I get: dovecot: Dec 01 13:27:38 Info: Dovecot v1.0-test52 starting up dovecot: Dec 01 13:33:34 Info: imap-login: Login: jtl [69.162.177.245] dovecot: Dec 01 13:41:07 Error: IMAP(jtl): UIDVALIDITY changed (1100294646 -> 110192643 5) in mbox file /var/spool/mail/j/t/jtl dovecot: Dec 01 13:41:07 Error: IMAP(jtl): UIDVALIDITY changed (1100294646 -> 110192643 5) in

Hello people!! First, thanks very much to Ejay Hire and to John Peacock for your quickly answer!! Now, I've dovecot installed, I downloaded the source and I compiled them. It's running ok now. But.....as I am new in all these issues I have some problems with the configuration. I have a user called "webmaster" that have a mail into /var/spool/mail, I want to redirect these

Has anyone else encountered weird date behavior with mbox-style folders? I am nearly ready to bite the bullet and convert my UW imap hierarchy (which is in mbx format) to Dovecot. In so doing, I need to convert each UW-specific mbx-format mailboxes to the more portable mbox format, which Dovecot can read. (This is done with the 'mbxcvt' utility that's part of UW.) I am then

This is from the CVS version as of Aug. 28. It's the first time I've seen this assertion failure. Prior to this, I was using the CVS version from Aug. 15. dovecot: Aug 30 16:07:52 Error: 24929 IMAP(support): UIDVALIDITY changed (1125327213 -> 1125430510) in mbox file /mailhome/new/s/b/support/mbox dovecot: Aug 30 16:08:13 Error: 24929 IMAP(support): UIDVALIDITY changed

I've recently upgraded to 1.0.10 in hopes that this problem would go away but no luck. I've got some users at my company with large inboxes on maildir (say 22,000 messages). Their mailboxes are hosted on nfs and dovecot is configured to do dotlocking. Still I see messages like this continually in the logs (sometimes every hour or so): server dovecot: IMAP(user): dotlock

Hello, Over the last 12 hours or so, I've been wrestling with a mysterious dovecot issue. After upgrading a mail server I'm helping my friend with maintaining from Fedora Core1 to Fedora Core4, I realized that I couldn't use UW-IMAP4 anymore (well, I can compile it myself, but it turned out that UW-IMAP was the main cause of the server's having load average as high as 30 from

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

There are three applications that have their mitts on files on my mail server, which is running AIXV5.3 and UWIMAP and mbox format. The mail folders and INBOXES are native to that machine, but also are NFS exported to a login server and a mailing list server. All three machines are running the lockd daemon. Everybody wants to lock differently 1) procmail (delivering for sendmail), which

Hi All, We are running Round cube on top of dovecot and postfix as our email echo system. Main problem we are facing is that, roundcube loads really slow for big inboxes (~5000 emails). I found that, while it loads, imap process goes high in terms of CPU utilization(~90%). I asked it in some roundcube support group, They believe that it is related to dovecot not roundcube. Can you shed any