similar to: v2.0.19 released

Hi I have a question regarding the IMAP CAPABILITY command behavior of Dovecot 2.0.rc3. While connecting to a Dovecot 1.2.4 server and requesting the supported capabilities, Dovecot returns all capabilities: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. a1 CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE

Aug 18 22:07:31 twosheds IMAP(dwmw2): : Panic: file mail-index-transaction.c: line 637 (mail_index_transaction_lookup): assertion failed: (seq >= t->first_new_seq && seq <= t->last_new_seq) * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS

Quoting RFC 5465 (NOTIFY): ?If the NOTIFY command enables MessageNew, MessageExpunge, AnnotationChange, or FlagChange notifications for a mailbox other than the currently selected mailbox, and the client has specified the STATUS indicator parameter, then the server MUST send a STATUS response for that mailbox before NOTIFY's tagged OK. [?] If either AnnotationChange or

Am I assuming correctly that you are not, in fact, running anything but imap process from Dovecot? Aki > On 31 December 2018 at 18:35 Chris BL <cpblpublic+dovecot at gmail.com> wrote: > > > > Hi Aki, > > Oops; I did not think carefully enough about your instructions. Here is the output from > > $ dovecot -n -c /home/meuser/dotfiles/auto-stanford-dovecot.conf

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

If your client directly executes imap binary, it is not mandatory for dovecot to be running, but you need to put the service section into /etc/dovecot/dovecot.conf and restart the dovecot service. Putting it to your local config file does not affect the global service. Aki > On 31 December 2018 at 22:16 Chris BL <cpblpublic+dovecot at gmail.com> wrote: > > > > Hi Aki,

Hi, I'm experiencing a problem I need some pointers to debug. I'm running Dovecot 2.0.15 and have a client which keeps causing log-entries like: Nov 4 15:10:42 mail dovecot: imap (test at aaaone.net): Error: Corrupted transaction log file /mail/3340444/.TestMails/dovecot.index.log seq 2: indexid changed 1320419300 -> 1320419441 (sync_offset=0) Nov 4 15:10:42 mail dovecot:

Did you remove the service section before taking doveconf -n? 'cos I can't see it here.. Also, did you restart dovecot after config change? Aki > On 31 December 2018 at 16:54 Chris BL <cpblpublic+dovecot at gmail.com> wrote: > > > Hi Aki, > > Yes, the same connect error: imap(meuser,)Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission

I merged all the new features and latest v1.1 changes under one tree: http://hg.dovecot.org/dovecot-1.2/ The changeset order is kind of weird though. The timestamps jump all around. Wonder if there's a way to reorder them so that it looks more sane.. The status of the new features: 1. CONDSTORE extension is probably the largest change. It adds new "modification sequences" for

We are working on fixing this. Aki > On 31 December 2018 at 23:45 Chris BL <cpblpublic+dovecot at gmail.com> wrote: > > > Hi Aki, > > Bingo! Putting that line in dovecot.conf rather than my custom file, and > then using my old custom file, unchanged, from Alpine works perfectly. > > My only remaining question, then, would be ... what was this (change) >

http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha1.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha1.tar.gz.sig This is the only v1.2.alpha announcement I'm going to send to dovecot-news list. Next announcement will be for either v1.2.beta1 or v1.2.rc1. I'm hoping that v1.2 stabilizes pretty soon. There are no huge changes like there were in 0.99->1.0 or

http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha1.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha1.tar.gz.sig This is the only v1.2.alpha announcement I'm going to send to dovecot-news list. Next announcement will be for either v1.2.beta1 or v1.2.rc1. I'm hoping that v1.2 stabilizes pretty soon. There are no huge changes like there were in 0.99->1.0 or

Hi Aki, (This message might not make it to the list; I have to switch back to the other dovecot to be able to send from that address) Oops; I did not think carefully enough about your instructions. Here is the output from $ dovecot -n -c /home/meuser/dotfiles/auto-stanford-dovecot.conf # 2.3.2.1 (0719df592): /home/meuser/dotfiles/auto-stanford-dovecot.conf # Pigeonhole version 0.5.2 () # OS:

Hi , i got trouble with master login thunderbird anounces no INBOX there at master login also telnet looks strange normal user login 1 login ...... 1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN

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

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

Hi, I had some problems connecting TB 2.x with dovecot 2.0. TB2 complained about not being an IMAP4 server. TB 3 worked. It seems that dovecot 2.0 doesn't return capabilities when queried. Maybe some wrong config, thoug? Here are the debug logs from TB2 comparing dovecot 2.0 (not working) and dovecot 1.2 (working): Dovecot 2.0: NA:CreateNewLineFromSocket: * OK [CAPABILITY IMAP4rev1

Hello, How I can share a folder with dots when the listescape plugin is enabled? In this example user001 is sharing two foders named "docs-abc" and "docs-a.b.c" to user002. The first folder (without dots) is seen by user002 but the second is not found by dovecot because it search a system folder named ".docs-a.b.c" but the system folder is

On 30 May 2017 at 21:16, Timo Sirainen <tss at iki.fi> wrote: > https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz > https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz.sig > > * auth: Use timing safe comparisons for everything related to > passwords. It's unlikely that these could have been used for > practical attacks, especially because Dovecot delays

I use a localhost dovecot imap server in order to access maildir folders from Alpine (see 2009 instructions for my set up here https://cpbl.wordpress.com/2009/11/07/alpine-offlineimap-and-gmail-under-ubuntu/ ) My configuration has worked nicely since 2009, but failed after a recent upgrade of dovecot (during basic upgrade from Ubuntu 18.04 to 18.10). The version of Alpine did not change.