similar to: Upgraded my dovecot?

Hi folks, I have configured a public folder as described on the Wiki (more or less; see below), but in TB3 I see the "Public" folder grayed out. I cannot subscribe. Toggling the subscriptions flag doesn't help. What did I miss here? Any helpful comment would be highly appreciated. If this is a TB3 problem: Which MUA would you suggest? Regards Harri

Hi, I'm not sure whether the client or the server is at fault (probably the client), but it's clearly a regression for me. I'm using the LCG Profimail (http://lonelycatgames.com/?app=profimail) application for my Symbian smartphone which has quite decent IMAP capabilities. Amongst others it can do IMAP IDLE (which has to be statically enabled in the server settings, so it's not

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

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

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

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, I'm running dovecot 1.2.15 and I'm having a problem proxying a user to another host, when this user is logged in with a masteruser. I have two dovecot servers configured to serve half of the users locally and to proxy the other half to the other host. Proxying is done using the masteruser feature (username*proxy) and it works as expected as the following test shows: # nc

We're proxying using 2.2.14~rc1 (on our IMAP Proxy) to two dovecot backend servers running dovecot-2.2.13-r1 When we're using Thundebird to connect to the dovecot proxy, we're getting the message "The mail server for account ACCOUNTNAME responded: [COMPRESSIONACTIVE] TLS compression already enabled" But why? Capabilities reported by the proxy: . OK [CAPABILITY IMAP4rev1

Hi! In your case it's probably easiest to change service stats { unix_listener stats-writer { mode = 0666 } } Aki > On 31 December 2018 at 16:05 cpblpublic+dovecot at gmail.com wrote: > > > > I use a localhost dovecot imap server in order to access maildir folders from Alpine (see 2009 instructions for my set up here >

On 9.4.2019 9.41, Ludwig Wieland via dovecot wrote: > Hello, > > My Dovecot Master can login but not not select INBOX ! > What's wrong ? > > best regards > Luda > > > > 1) USER can select INBOX: OK > --------------------------------------------------- > telnet localhost imap > Trying ::1... > Connected to localhost. > Escape character is

You are still getting the connect error? Can you share your doveconf -n? Aki > On 31 December 2018 at 16:42 cpblpublic+dovecot at gmail.com wrote: > > > Hi Aki, > > Thanks. I put that in the .conf file I mentioned, and it made no > difference. > > Chris > > > Hi! > > > > In your case it's probably easiest to change > > > >

I have very strange problem with masteruser. See two logs below: # telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Welcome to our post server! x login nevorotin password x OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT

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.

Hi ! I have an old Courier IMAP and in front of it, I have put a proxy cache with Dovecot/imapc. I use Debian Wheezy (stable) which package Dovecot in version 2.1.7. I have tested the upgrade to Debian Jessie (testing) which package Dovecot in version 2.2.9 but an assertion is thrown : dovecot: imap(xxx): Panic: file imapc-list.c: line 499 (imapc_list_delete_unused_indexes): assertion failed:

Hello, i try to understand, how it works (IDLE). Try to get it successfully work with my new Palm Pre ;-) which looks like to have a lot issues wir imap... so i'll blame not dovecot for the issues. Sent a mail, from googlemail. processed by dovecot ad 12:11. what me now confusing, is, that there in the out-log is nothing visible, I expected, to see there was sent an notification, there was

Hello, I have trouble with some attachments not working on Horde and Roundcube. I made a ticket to Roundcube webmail and they tracked down it to Dovecot not responding correctly to BINARY FETCH: http://trac.roundcube.net/ticket/1490532 What is causing Dovecot to answer NIL? Is there an issue in Dovecot? If I want to disable to BINARY capability in Dovecot I need to use imap_capabilities. I

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,

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) >

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:

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