similar to: IMAP NOTIFY extension

Hi, I just updated my Dovecot to the new build in Fedora 26, which is based on 2.2.31. After I did that, Evolution (3.24.3) is no longer receiving notifications about new mail in folders other than inbox (the same version of Evo that worked fine against Dovecot 2.2.30.2). The only folder that still gets notifications is inbox. I see there have been changes to NOTIFY code in this release. What

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

v2.2 hg now has support for NOTIFY extension. The only thing missing is support for SubscriptionChange events. Now would be a good time for IMAP clients to start implementing and testing it. :) I remember K9 developers at least said they were just waiting for Dovecot to support it first. v2.2 implements some other extensions also: BINARY, CATENATE and MOVE. Stephan has also implemented URLAUTH

Using K-9 Mail to IDLE on a test folder "MyIncTmp". When there is a flag change on a message in the folder, which generates an untagged FETCH, K-9 Mail responds with a DONE, but dovecot does not exit IDLE state (LOG 1). However, if a new message is delivered, generating an untagged EXISTS, K-9 Mail responds the same way, with a DONE, and dovecot does exit IDLE state. (LOG 2) You

Hi Trying to finish a simple xyplot, but the key colors don't match those specified on the plot. I have only been able to change the color of the key text, but not the points. Hours <- c (25.88,32.31,24.04,23.27,16.64,19.75,27.25,17.9,20.45,29.65,20.83,27.17, 28.42,28,18.85,17.4,19.75,25.34,23.23,29.85,28.96,25.6,14.67,20.55,25.77 ,

On 29 Jun 2017, at 13.27, Bojan Smojver <bojan at rexursive.com> wrote: > > Hi, > > I just updated my Dovecot to the new build in Fedora 26, which is based > on 2.2.31. After I did that, Evolution (3.24.3) is no longer receiving > notifications about new mail in folders other than inbox (the same > version of Evo that worked fine against Dovecot 2.2.30.2). The only

On 11/23/2014 04:45 PM, Robert Schetterer wrote: > Am 23.11.2014 um 22:33 schrieb Reindl Harald: >> no idea what you are talking about >> >> K9 is a android client and works fine with TLS >> >> no idea what has "https" to do with email nor why someone needs to >> "disable K9 long enugh" whatever "long enough" is - don't get

no idea what you are talking about K9 is a android client and works fine with TLS no idea what has "https" to do with email nor why someone needs to "disable K9 long enugh" whatever "long enough" is - don't get me wrong but most technical context on several lists of you if it comes to details is cluttered and your permanently "i am working on IETF"

http://hg.dovecot.org/dovecot-2.2-notify/ contains the initial implementation of IMAP NOTIFY extension. It's less than half-working, but the difficult part of it is done I think. If I give it a command like: x notify set (personal (messagenew messageexpunge flagchange)) and then in another session I copy a message to another mailbox, it sends: * STATUS "foobar" (MESSAGES 77

Am 07.02.2015 um 10:10 schrieb SW: > I've just done a test with K9 mail on Android 4.4.2 and this is what I > see in the log: > > ECDHE-ECDSA-AES128-SHA (128/128 bits) > > But when using Thunderbird I see: > > ECDHE-ECDSA-AES128-GCM-SHA256 (128/128 bits) > > I'm happy that Thunderbird is using a secure cipher but is Android? Is > ECDHE-ECDSA-AES128-SHA

18.07.2020, 14:30, Benny Pedersen <me at junc.eu>ratatouille skrev den 2020-07-18 13:20: > Commenting just ssl_min_protocol = TLSv1.2 seems to solve the problem. > So I have the default ssl_min_protocol = TLSv1 with means that the device running k9 is not supporting TLS 1.2 yet TLS 1.2 is enabled by default in Android versions 5.0 and newer. For earlier Android versions, K9

Hi list, The NOTIFY extension (RFC 5465) works fine for mailboxes in the "virtual/" namespace, but it crashes the IMAP client when used with a mailbox in the empty "" namespace: ~$ /usr/lib/dovecot/imap * PREAUTH [CAPABILITY IMAP4rev1 ? NOTIFY SPECIAL-USE] Logged in as guilhem a NAMESPACE * NAMESPACE (("" "/")("virtual/"

Hi there, There seem to be a race condition in IMAP NOTIFY: when two events for the SELECTED mailbox are received soon after one another, sometimes only the first one is being reported to clients that enabled IMAP NOTIFY. On closer look it seems like this is most often reproducible when the delay between the two events is NOTIFY_DELAY_MSECS (500ms). This is with 2.3.4.1 from Debian sid. $

Hello! Benny Pedersen <me at junc.eu> schrieb am 18.07.20 um 13:04:37 Uhr: > ratatouille skrev den 2020-07-18 12:33: > > ssl_min_protocol = TLSv1.2 > > ssl_cipher_list = PROFILE=SYSTEM > > ssl_prefer_server_ciphers = yes > > comment this lines, then i belive k9 works > > if it still does not, then drop k9 mail Commenting just ssl_min_protocol = TLSv1.2

I am trying to monitor with Nagios that my phones are consistently checking into dovecot via IMAP. I used to be able to parse syslog for imap-login messages. I have since updated my phones, the phoness email client (k9-mail) and dovecot. Now the imap-login messages are few and far between. However, I can clearly see via tcpdump that some traffic is happening when I click refresh on k9. I enabled

Hello! On my testserver running CentOS8 I have installed dovecot v2.3.8. I can connect to the server using claws-mail on my PC but can't using K9-mail on android device. Jul 18 12:24:57 imap-login: Debug: SSL: where=0x10, ret=1: before SSL initialization Jul 18 12:24:57 imap-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization Jul 18 12:24:57 imap-login: Debug: SSL:

On 11/23/2014 05:59 PM, Reindl Harald wrote: > > Am 23.11.2014 um 23:30 schrieb Robert Moskowitz: >> On 11/23/2014 04:45 PM, Robert Schetterer wrote: >>> Am 23.11.2014 um 22:33 schrieb Reindl Harald: >>>> no idea what you are talking about >>>> >>>> K9 is a android client and works fine with TLS >>>> >>>> no idea what

Here is an example with APPEND $ /usr/lib/dovecot/imap S1: * PREAUTH [CAPABILITY IMAP4rev1 ? MOVE NOTIFY SPECIAL-USE] Logged in as guilhem C1: a1 NOTIFY SET (INBOXES (MessageNew MessageExpunge FlagChange)) S1: a1 OK NOTIFY completed (0.000 secs) $ /usr/lib/dovecot/imap S2: * PREAUTH [CAPABILITY IMAP4rev1 ? MOVE NOTIFY SPECIAL-USE] Logged in as guilhem C2: a2 APPEND

> Hey Robert, > There is a command on linux to test ssl/tls smtp server : > openssl s_client -connect mail.example.com:port -starttls smtp > > You just need openssl for windows here : > http://slproweb.com/products/Win32OpenSSL.html > > Let me know if this is working. > Regards > By the way if this isn't working, try connecting to your server via Mozilla

Hello, Testing the NOTIFY extension on imap.vivaldi.net, seems there's a bug when a mailbox is renamed or deleted. Requesting events with: A1 NOTIFY SET (inboxes (SubscriptionChange MailboxName)) Here are the sent events: - mailbox creation with automatic subscription (ok): * LIST () "." foo * LIST (\Subscribed) "." foo - mailbox renaming (bug ?): * LIST ()