similar to: Dovecot 2.2.4 metadata-plugin not support UTF7

On dovecot 2.2.12 compiled from source I use ActiveSync with kolab-syncroton. When running a test i have this imap log: [29-Mar-2014 22:58:25 +0200]: [F658] S: A0004 OK Getmetadata completed. [29-Mar-2014 22:58:25 +0200]: [F658] C: A0005 SETMETADATA INBOX (/private/vendor/kolab/activesync "{\"DEVICE\":{\"601099122\":{\"ID\":

Debian Wheezy dovecot 2.2.4 (deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2.patched main) dovecot-metadata-plugin v14 /var/lib/dovecot 777 dovecot:dovecot /var/lib/dovecot/shared-metadata 700 dovecot:dovecot /var/run/dovecot 777 dovecot:dovecot /var/run/divecot/dict 666 mail:dovecot Test1 - create calendar UTF7 mailbox (no errors in

After the LOGIN do STATUS "User/somemailbox": a0007 STATUS "INBOX/Rechnung" (UIDNEXT UIDVALIDITY UNSEEN RECENT) a0008 STATUS "User/lists at example.com/Announce" (UIDNEXT UIDVALIDITY UNSEEN RECENT) a0009 STATUS "User/system at example.com/INBOX-root" (UIDNEXT UIDVALIDITY UNSEEN RECENT) a0010 STATUS "User/test at example.com/Shared" (UIDNEXT

Hi, I am still getting strange creation and mailbox lookups from 0.99.11-test7. dovecot creates in ~/Maildir/ .INBOX/ .imap.index .imap.index.cache .imap.index.log .customflags dovecot-uidlist .INBOX seems to be a reference to ~/Maildir/{cur,new,tmp} yet I

I have just verified with IMAP commands. This is the procedure: telnet localhost 143 and then type this: A0001 CAPABILITY A0002 LOGIN "bluser" "bluser" A0003 SELECT "inbox-b" A0004 EXPUNGE A0005 FETCH 1:12 RFC822.SIZE A0006 FETCH 1 RFC822.HEADER A0007 FETCH 1 BODY.PEEK[TEXT] A0008 STORE 1 +FLAGS (\Seen \Deleted) A0009 EXPUNGE A0010 FETCH 1 RFC822.HEADER A0011 FETCH

On 05/06/2015 09:57 AM, Teemu Huovila wrote: > On 05/05/2015 05:26 PM, Santiago Vila wrote: >> I have just verified with IMAP commands. This is the procedure: >> >> telnet localhost 143 >> >> and then type this: >> >> A0001 CAPABILITY >> A0002 LOGIN "bluser" "bluser" >> A0003 SELECT "inbox-b" >> A0004

Am 05.05.2015 um 16:26 schrieb Santiago Vila: > I have just verified with IMAP commands. This is the procedure: > > telnet localhost 143 > > and then type this: > > A0001 CAPABILITY > A0002 LOGIN "bluser" "bluser" > A0003 SELECT "inbox-b" > A0004 EXPUNGE > A0005 FETCH 1:12 RFC822.SIZE > A0006 FETCH 1 RFC822.HEADER > A0007

On 05/05/2015 05:26 PM, Santiago Vila wrote: > I have just verified with IMAP commands. This is the procedure: > > telnet localhost 143 > > and then type this: > > A0001 CAPABILITY > A0002 LOGIN "bluser" "bluser" > A0003 SELECT "inbox-b" > A0004 EXPUNGE > A0005 FETCH 1:12 RFC822.SIZE > A0006 FETCH 1 RFC822.HEADER > A0007 FETCH

Hello List, I have a problem with the client Roundcube. Whenever I save a draft to the Folder INBOX.Drafts a old mail in my INBOX will be marked as unread. Here are the IMAP Logs from Roundcube and Dovecot debug logs. I have no idea why it happens. The IMAP protocol looks normal to me but as you can see in the second to last line in the Dovecot log Dovecot is changing the flag of an old E-Mail

Hello, I have dovecot 2.2.13 instance and I found that (at least for polish language) folder names in GETMETADATA command response are encoded in UTF8. Shouldn't it be converted to UTF7? Both SETMETADATA and GETMETADATA arguments have to be encoded in UTF7, the problem(?) is related only to server response example: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE

Yeah, that smells bogus. You can't send the EXPUNGE right away, even if you did the EXPUNGE. As the server you're required to wait for a command which allows expunges to happen. I've double-checked the Cyrus IMAP server, and we check usinguid to decide if we can tellexpunge at the end of index_store - aka, only UID STORE will tell the client EXPUNGE responses. Unfortunately, this is

Am 04.05.2015 um 21:04 schrieb Santiago Vila: > Greetings. > > Thanks to Jelmer Vernooij, who has just uploaded version 2.2.16 for > Debian unstable, I can confirm that this bug may still be reproduced > in version 2.2.16, so it has *not* been fixed yet. > > Several months ago I was told "I can't reproduce it in dovecot hg", or > something like that. Well,

I am testing dovecot 1.1 betas on a testing system, hoping to take advantage of self repairing and NFS-capable indexes when 1.1 is sensible to put into production. I ran into a number of issues that I did not have with 1.0, and I think I'll just pick one or more at a time and report them rather than try to report every single issue at once, hoping that some of the fixes will solve more than

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

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:

Hi list I currently having troubles to "connect" dovecot (for proxy) to an existing LDAP. If I got the dovecot wiki right only userdb is needed for a proxy setup where the proxy does not authenticate but just forward to the backend for authentication. So I setup the following in dovecot-ldap.conf.ext user_attrs = =password,=y=nopasswd,=y=proxy,mailHost=host user_filter =

--Repost after subscription as list member --- I made some tests with metadata support in dovecot 2.2.10. Previously I had dovecot 2.2.4 with external metadata plugin who work well. I use dovecot with roundcube and roundcube plugins from kolab project . First, the feature activation was tricky and rather undocumented. I spent about half hour googling, after that I set: imap_metadata = yes and

Hi Timo, Hi list, I finally got along to test the current dovecot 1.2 with our Kolab Server. And I'm very excited to see all the cool ACL and shared name spaces stuff upstream, thanks a lot Timo! Anyway I just stumbled across a new bug using our metadata-plugin (which in turn uses the dict back end): Making a few annotations requests after another it stops working. dovecot.log sais

hi, I testing around with Kolab with LDAP and have some strange problems, with the auto generated packages for Wheezy. On my first test VM, I have 2:2.2.16~rc1-1~auto+4 installed, and everything works as expected. On a new VM I have 2.2.16-1~auto+13_amd64.deb packages and if I include LDAP backend, I get a segmentation fault on /usr/lib/dovecot/auth: root at kolab:/etc/dovecot/conf.d#