similar to: 2.1.3: Overly lax FETCH parsing

I've been seeing the following wonky behavior with Dovecot. Currently this is with Dovecot 2.0.19, but I was also seeing it in earlier versions as well, including versions from the 1.x series. Some background, this is from Horde's ActiveSync library, when it is trying to determine what UIDs have recently been expunged. I can guarantee that when this command was sent, there was

On Tue, 04 Apr 2017 11:07:26 +0000 Luca Bertoncello <lucabert at lucabert.de> wrote: > Hi all, > > i've got a strange behaviour with a BlackBerry Classic Phone (BBOS > 10.3.2.2876) in combination with Dovecot 2.2.13 while trying to > fetch mails. > > Before burying myself into debugging sessions, i try to get an > understanding if the following is a Client-

Hi all, i've got a strange behaviour with a BlackBerry Classic Phone (BBOS 10.3.2.2876) in combination with Dovecot 2.2.13 while trying to fetch mails. Before burying myself into debugging sessions, i try to get an understanding if the following is a Client- or a Server-specific error in the behaviour: CIGA8 UID FETCH 10009:10035 (UID FLAGS) (CHANGEDSINCE NOMODSEQ) CIGA8 BAD Error

Hi there, Quoting RFC 3501 sec. 7.4.2 ?FETCH Response? (data item BODYSTRUCTURE): ?A body type of type MESSAGE and subtype RFC822 contains, immediately after the basic fields, the envelope structure, body structure, and size in text lines of the encapsulated message.? According the ABNF (RFC 3501 sec. 9) the envelope structure is that of the ENVELOPE FETCH data item, and the

Hi Timo - hope things are well :) Playing around with the CONDSTORE (RFC 4551) stuff while testing the IMAP lib I am writing and I think I have found a bug in Dovecot 1.2. RFC 4551 [4] identifies the FETCH response to a MODSEQ request as follows: fetch-mod-resp = "MODSEQ" SP "(" permsg-modsequence ")" with 'permsg-modsequence' defined as:

One more data point Timo: On Tue, Mar 12, 2019, at 9:58 AM, Kostya Vasilyev via dovecot wrote: > Timo, > > On Tue, Mar 12, 2019, at 3:56 AM, Timo Sirainen via dovecot wrote: >> On 10 Mar 2019, at 10.14, Kostya Vasilyev via dovecot <dovecot at dovecot.org> wrote: >>> >>> My mail is stored under ~/mail/.imap (not sure what this format is called), I mean not

Timo, On Tue, Mar 12, 2019, at 3:56 AM, Timo Sirainen via dovecot wrote: > On 10 Mar 2019, at 10.14, Kostya Vasilyev via dovecot <dovecot at dovecot.org> wrote: >> >> My mail is stored under ~/mail/.imap (not sure what this format is called), I mean not "single file mbox". >> >> I have not changed any IDLE related config settings: >> >>

I'm pleased to see that dovecot-2.2 includes support for RFCs 4467 and 4469 (URLAUTH and CATENATE). I have begun testing these features (in dovecot-2.2.1) and comparing their functionality against Apple's implementation. So far I have discovered a few inconsistencies. I will report each of these, and any more that I may find, in separate threads. The first issue is that using CATENATE

I am getting the following error when trying to install an application that should launch a java application: I did set my display to the localhost:0.0 but to no avail. Stack Trace: java.lang.NoClassDefFoundError at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) at java.awt.Toolkit$2.run(Unknown Source) at java.security.AccessController.doPrivileged(Native

On 10/13/07, Wayne Davison <wayned@samba.org> committed: > Added Files: > detect-renamed-lax.diff > Log Message: > My version of Matt's --trust-rename patch. The option --detect-moved should be named --detect-moved-lax because it contains the lax behavior. --detect-moved would mean "use a file with the same basename as an alternate basis". Matt

--- Marek Peteraj <marpet@naex.sk> wrote: > Hi all, > > i'd like to ask what the best options are for safe 24bit 96kHz > archiving. Currently i'm only using -8 but there are also some other > options like block size etc. Can anyone suggest? I haven't heard of anyone using FLAC for 192khz, so you'll probably just have to experiment. when you have some

Hi all, i'd like to ask what the best options are for safe 24bit 96kHz archiving. Currently i'm only using -8 but there are also some other options like block size etc. Can anyone suggest? Also i'd like to ask whether a no-lax 192kHz mode is planned in flac, seems like 192kHz isn't directly supported although flac can compress such rate in lax mode. My last question - is there

Hi Josh, On Sat, 2004-10-09 at 22:41, Josh Coalson wrote: > --- Marek Peteraj <marpet@naex.sk> wrote: > > Hi all, > > > > i'd like to ask what the best options are for safe 24bit 96kHz > > archiving. Currently i'm only using -8 but there are also some other > > options like block size etc. Can anyone suggest? > > I haven't heard of

In light of my experiences with that material and Josh's two most recent posts, I'll just stay away from encoding with either of those options and certainly from advising anyone else to use them. Thanks again to both Miroslav and Josh for their help with that question, and a long overdue thanks to Kerry Hoath for assistance with my batch file question some months back. I never shared

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

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

Hello, I'd like to follow up on someone else's old thread: http://dovecot.org/list/dovecot/2012-April/082624.html I understand that Dovecot (that 2012 discussion was about version 2.0.18) can return "HIGHESTMODSEQ 1" upon SELECT if persistent modseq tracking was never enabled for a mailbox. I'd like to get a clarification on how to enable proper persistent modseq

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

Hi folks! I have set up dsync replication with SSH according to http://wiki2.dovecot.org/Replication with the exception of having system users and calling doveadm dsync-server directly from authorized_keys, because the wrapper script posted on the above site is needless (at least in 2.2.10). However, while the two instances connect well to each other, no synchronisation is performed at all, the

Greetings, I'm new to the list. I have encountered what I believe to be a bug in the return of HIGHESTMODSEQ when talking to a IMAP client. HIGHESTMODSEQ does not appear to be incrementing when a new message arrives. The exact steps I took are: 1) Create a new mail account 2) Send a mail to the account, check that you can receive the email. Send a second mail to the account. 3) perform a