similar to: Random flags appearing on messages

Not technically a bug, but a small waste of bandwidth: it seems (at least as of 1.2.10) that if neither CONDSTORE/QRESYNC are enabled dovecot still sends HIGHESTMODSEQ info: a examine Testing.AAA * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $Forwarded impflag0 impflag1 impflag2) * OK [PERMANENTFLAGS ()] Read-only mailbox. * 309 EXISTS * 0 RECENT * OK [UNSEEN 5] First unseen. * OK

Looked at the hg commits since 2.1.1, but didn't see anything that was exactly on-point to this... UNSEEN counts seem to be broken when done in a LIST-STATUS call. I see this, for example: >> Timestamp: Thu, 01 Mar 2012 10:55:47 -0700 [...] C: 3 LIST "" (INBOX IN.dovecot) RETURN (STATUS (UNSEEN)) S: * LIST () "." "IN.dovecot" S: * STATUS

In a mailbox that has ACL restrictions on both DELETE and EXPUNGE (i.e. no 'e' or 't' rights), I see the following: 3 UID STORE 3173 (UNCHANGEDSINCE 353) +FLAGS \deleted 3 OK Store completed. (UID 3173 is not flagged \deleted) [...] 6 UID EXPUNGE 1:* 6 OK Expunge completed. (At least 1 UID is flagged \deleted in mailbox) Shouldn't these commands be returning

Running into a weird issue in a mailbox that has 26+ keywords. In one session, I do this: S: 2 SELECT "INBOX" (QRESYNC (1255685337 78608 [...uids...])) S: [...] S: * OK [HIGHESTMODSEQ 78608] Highest S: * OK [UIDVALIDITY 1255685337] UIDs valid S: 2 OK [READ-WRITE] Select completed. C: 3 UID STORE 48386 (UNCHANGEDSINCE 78608) +FLAGS AAAAAAAA S: * 8 FETCH (UID 48386 MODSEQ (78609) FLAGS

I wrote a mostly-working CONDSTORE support for Dovecot today. You can try it with: hg clone http://hg.dovecot.org/dovecot-condstore/ There are a few problems left: - STORE FLAGS.SILENT should be sending FETCH MODSEQ updates - When SELECTing a mailbox while CONDSTORE hasn't yet been enabled in the session, Dovecot returns a higher HIGHESTMODSEQ than what's used after CONDSTORE is

5 milestones planned currently. I'll start with the always-on multi-master replication, because that's the most difficult one to get working correctly and efficiently. So if during its implementation I find some design problems, less code needs to be fixed. Milestone 0 will hopefully be done within a month. This includes reading and replying to the rest of the mails on this list and

PJ wrote: > This may or may not be CentOS related, but am out of ideas at this point and wanted to bounce this off the list. > > I'm running a CentOS 5.5 server, running the latest kernel > 2.6.18-194.32.1.el5. > > Almost everyday around 3:30 AM the server completely locks up and has to be power cycled before it will come back online. > (this means someone hat to wake up

This may or may not be CentOS related, but am out of ideas at this point and wanted to bounce this off the list. I'm running a CentOS 5.5 server, running the latest kernel 2.6.18-194.32.1.el5. Almost everyday around 3:30 AM the server completely locks up and has to be power cycled before it will come back online. (this means someone hat to wake up and reboot the server, oh how I love being

I'll probably be implementing multi-master replication this summer. My previous thoughts about it are here: http://dovecot.org/list/dovecot/2007-December/027284.html Below is a description of how the replication protocol will probably work. It should work just as well for master-slave and multi-master setups. Comments welcome. I'll write later a separate mail about how it'll be

Changes: - Added goal 8 and rewrote mailbox synchronization plan. - Added new SELECT command to change active mailbox and removed mailbox ID from command parameters Goals ----- 1. If a single (or configurable number of) server dies, no mails must be lost that have been reported to IMAP/SMTP clients as being successfully stored. 2. Must be able to automatically recover from a server

First a list of all the new features and their state: 1. http://hg.dovecot.org/dovecot-threadindexes/ THREAD=REFERENCES indexes. Missing NFS flushes, support for mmap_disable=yes, breaks when more than one session modifies at the same time. Not tested much if the replies are really correct at all. Also started THREAD=X-REFERENCES2 but it doesn't work as expected. 2.

https://bugzilla.mindrot.org/show_bug.cgi?id=2529 Bug ID: 2529 Summary: direct-streamlocal channel open doesn't match PROTOCOL documentation Product: Portable OpenSSH Version: -current Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: ssh

RFC 5162 [3.1] states that a QRESYNC should return all changes in a SELECT/EXAMINE since the given modseq. In the following case, it looks like there is an off-by-1 error somewhere: C: A64 SELECT "TestMailboxTest" (QRESYNC (1224531494 6 1,3:5)) [MMS: MODSEQ given is 6] S: * OK [CLOSED] S: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) S: * OK [PERMANENTFLAGS (\Answered \Flagged

Hello, I intend to migrate a mail server with Maildir from wu-imap to dovecot imap. Using horde/IMP, users can not access their imap forders, as wu-imap created Mail directory that holds all created folders. Dovecot could not detect the mail directory so I had to put default_mail_env = ~/Maildir in dovecot.conf. Before I begin to read the source-code of dovecot or try to migrate the the

Hello, I encounter a problem using the UPS MGE Evolution 850 VA USB with Debian Etch and the nut package available for this version. I got this error: ==syslog== Can't connect to UPS [MGE850VA] (usbhid-ups-auto): No such file or directory upsd[2767]: Startup successful upsmon[2769]: Startup successful upsd[2767]: Connection from 127.0.0.1 upsd[2767]: Client MGE at 127.0.0.1 logged

Please commit... Best Olaf Krzikalla -- Olaf Krzikalla Technische Universitaet Dresden Zentrum fuer Informationsdienste und Hochleistungsrechnen Abteilung Verteiltes und Datenintensives Rechnen Zellescher Weg 12, 01069 Dresden Willersbau, Zimmer A105 Telefonnr.: +49 351 463-32442 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: twine.patch

"Davide Marchi" <danjde at msw.it> writes: >> UW-IMAP's mailutil, imapsync, YippieMove and Larch. Whatever you use, *don't* use UW-IMAP's mailutil unless you got lots of time to kill. It is dreadfully slow -- I used it to export some of my users' mailboxes to Gmail or other remote mail servers, and I could almost cut&paste the messages faster. Like Aki

Hi Henning, note that I've cc'ed the NUT users list for info. 2015-02-04 13:47 GMT+01:00 Henning Fehrmann <henning.fehrmann at aei.mpg.de>: > Hi Arnaud, > > > the best to process the value would be to have the MIB definition for > > upsAlarmOnBattery, as for example: > > [1] >

Hi Friends, I would like to ask you a suggestion: I need to migrate a imap server to a new one and then dismiss the old one. Reading from relative Dovecot documentation page (https://wiki.dovecot.org/Migration), more tools are shown: UW-IMAP's mailutil, imapsync, YippieMove and Larch. The each mail servers are Linux based, one of this (mine) is Dovecot. Based on your experience which of

Currently mailbox names are stored in IMAP's modified-UTF-7 format in filesystem. I was wondering about changing this in v2.0. The default would still be to use mUTF-7 in filesystem, but just adding :UTF8 or something to mail_location could enable UTF-8. Any thoughts? Could this be dangerous somehow? UTF-8 enables a lot of weird characters, perhaps no one really wants to see them on