similar to: 1.0-test9 released

I've been doing some thinking on a new better mailbox format that'd be faster than mbox and maildir for most common uses. Comments welcome. It won't come to Dovecot v1.0, but I'll probably create another branch to Dovecot CVS where I'll start implementing it and some other possibly destabilizing changes. Generic ------- The point is to have a mailbox format where the mailbox

http://dovecot.procontrol.fi/test/ Again major maildir syncing updates: - uidlist file is accessed and rewritten a lot less often now than before - mail duplicates are detected and handled properly by renaming them to new base name - message flag updates and expunging before did two full syncs for cur/ directory. now it does only one. - some fixes to syncing in read-only / out-of-quota

Hi List, While testing with dovecot-1.0-test8 on our platform, I get al lot of these: May 11 11:42:50 mf1 dovecot: imap(user at domain.tld): Our dotlock file /var/mail/mounted/d/do/domain.tld/user/Maildir/.INBOX/ dovecot.index.log.lock was modified (1084268570 vs 1084268875), assuming it wasn't overridden This is probably due to some time-issues on our platform, and the load the

Updated version. The previous one was a bit too complicated with flag updates for pretty minimal benefits. Changes: - writing/reading mail flags can be disabled to get better performance without it requiring any changes to how the files are normally handled (so mixed more works fine). - writing flags now requires getting shared locks. so there's the overhead of locking but flag writers

X forwarding doesn't work for me under Linux kernels 2.4.0-test8 or test9, using OpenSSH 2.2.0p1 (as packaged in Debian woody.) When I try to ssh to my machine, the client spits out the following pieces of information: Warning: Remote host denied X11 forwarding. Last login: Tue Oct 3 15:26:19 2000 from localhost on pts/2 Linux mallard 2.4.0-test9 #3 Tue Oct 3 14:20:59 CDT 2000 i686 unknown

Hi, I'm running dovecot-1.0.beta8 from FreeBSD ports, using mbox mail store. My problem appears to have come up on the list about a month ago, "Expunge is not expunging unless it is called twice". I ran through Bill Boebel's telnet-IMAP session for myself, and I see that his test case is now fixed (as Timo said), but mutt, for whatever reason, uses +FLAGS.SILENT, and I'm

I don't think anyone uses dbox currently, so the whole format could still be redesigned. So I was thinking about doing two major changes: 1. Rely on index files a lot more. The flags are already stored in index files, so there's no need to waste I/O updating them to dbox files all the time. They could still be updated (if indexes get deleted, the flags aren't all gone), but less

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

Hi List, While (bluntly) testing the prerelease version of dovecot on our mailfarm (just for the webmail imap) we noticed some small problems: - While our OLD dovecot/imap drove the load to a maximum of 1 over a day after running, the new dovecot/imap pushes it easily to 20. This is mainly due to a LOT more disk activity. This is probably caused by the fact we a) use indexes on disk and

http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz.sig A few announcements first: I'm now going to start being more strict about not answering Dovecot questions sent to me privately (especially support requests, but also bug reports, feature requests, etc). Often those questions could be answered by other people in the mailing list as

http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz.sig A few announcements first: I'm now going to start being more strict about not answering Dovecot questions sent to me privately (especially support requests, but also bug reports, feature requests, etc). Often those questions could be answered by other people in the mailing list as

On Sat, 22 Nov 2003 20:57:44 +0530 (GMT+05:30) anand@eis.iisc.ernet.in (SVR Anand) wrote: > Hi, > > I am one of the system administrators who manage a campus network of 5000 users > that is connected to Internet. We have placed a Linux bridge to isolate the > Internet from the campus. To nullify network flooding effect, we have used > iptables. The kernel is 2.6.0-test9, the

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

ext3 is having big problems on my x86-64 system. An ext3 partition has just gone crazy, with the following messages in dmesg: EXT3-fs error (device hda3): ext3_readdir: bad entry in directory #4603905: rec_len % 4 != 0 - offset=0, inode=2507704792, rec_len=42, name_len=0 Aborting journal on device hda3. ext3_abort called. EXT3-fs abort (device hda3): ext3_journal_start: Detected aborted journal

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

Dear All, I am trying to create a empty structure that I want to fill gradually through the code. I want to use something like rbind to create the basic structure first. I am looking for a possibility to do an rbind where the columns names dont match fully (but the missing columns can be defaulted to either zero or n/a) (my actual data has a lot of columns). Please see the data frames below I

Here's my configuration. dovecot -n # 1.0.7: /usr/local/etc/dovecot.conf protocols: pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login mail_extra_groups: mail mail_location: /var/spool/mail/%u mbox_write_locks: fcntl dotlock The above setting was just added in an attempt to resolve the issue.

Dovecot is requiring two "expunge" calls before it deletes an email. It just seems to ignore the first expunge call, leaving the email file in the maildir cur/ folder. Any idea why? I even waited 10 seconds after setting the Deleted flag, but still the first expunge call did nothing.... 1 OK User logged in 2 select "INBOX" * FLAGS (\Answered \Flagged \Deleted \Seen

http://dovecot.org/releases/1.1/dovecot-1.1.15.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.15.tar.gz.sig The command pipelining fix is pretty interesting. Wonder how much it improves performance, especially when deleting lots of messages from a large mailbox. v1.1.15 2009-05-17 Timo Sirainen <tss at iki.fi> + IMAP: When multiple commands are pipelined, try harder to combine

http://dovecot.org/releases/1.1/dovecot-1.1.15.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.15.tar.gz.sig The command pipelining fix is pretty interesting. Wonder how much it improves performance, especially when deleting lots of messages from a large mailbox. v1.1.15 2009-05-17 Timo Sirainen <tss at iki.fi> + IMAP: When multiple commands are pipelined, try harder to combine