similar to: 2.0/2.1 - different behavior for LIST-EXTENDED

http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz.sig A few announcements first: I'm now going to start being more strict about not answering Dovecot questions sent to me privately (especially support requests, but also bug reports, feature requests, etc). Often those questions could be answered by other people in the mailing list as

http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz.sig A few announcements first: I'm now going to start being more strict about not answering Dovecot questions sent to me privately (especially support requests, but also bug reports, feature requests, etc). Often those questions could be answered by other people in the mailing list as

Hey all, I've upgraded from a working Dovecot 2.0.17 Proxy with a master user setup to Dovecot 2.1.3 and I've merged my conf settings from 2.0.17 into 2.1.3. I'm able to start up dovecot proxy and telnet localhost, however it creates the users home director on the proxy server instead of going to the backend dovecot server (which has already been successfully upgraded to 2.1.3 from

We recently upgraded our cluster to 2.1.3, to enable director proxying. Everything appears to be working fine for the most part; the only odd thing is that I'm seeing a lot of entries in the logs like this: Apr 7 02:18:05 mail-out06 dovecot: pop3-login: Fatal: master: service(pop3-login): child 75029 killed with signal 11 (core not dumped - set service pop3-login {

On 16 Jul 2019, at 9.51, Emil Kalchev via dovecot <dovecot at dovecot.org> wrote: > > I am executing this command below to dovecot-2.3.5-6.cp1178.x86_64 server > > Notice that some status responses are missing (For folders INBOX.Archive, INBOX.spam.&-BD0EOQQ9BDkEPQ-). I wonder If this is a bug or working as expected > > In rfc5819 there is this: > > If the

Hi, I was looking into the new Authentication Policy feature: https://wiki2.dovecot.org/Authentication/Policy I had kinda hoped that I would be able to enfore this in a proxy running in front of several backends. This proxy does not authenticate. It use "nopassword". But I realize that the "succes" reported in the final authpolicy req. (command=report) is not what is

On 9/2/19 3:03 PM, Sami Ketola wrote: >> On 2 Sep 2019, at 15.25, Peter Mogensen via dovecot <dovecot at dovecot.org> wrote: ... >> Is there anyway for dsync to avoid moving Gigabytes of data for could >> just be "moved" by moving the mount? > > > Not tested but you can probably do something like this in the target server: > > doveadm backup -u

http://dovecot.org/releases/2.1/dovecot-2.1.4.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.4.tar.gz.sig + Added mail_temp_scan_interval setting and changed its default value from 8 hours to 1 week. + Added pop3-migration plugin for easily doing a transparent IMAP+POP3 migration to Dovecot: http://wiki2.dovecot.org/Migration/Dsync + doveadm user:

http://dovecot.org/releases/2.1/dovecot-2.1.4.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.4.tar.gz.sig + Added mail_temp_scan_interval setting and changed its default value from 8 hours to 1 week. + Added pop3-migration plugin for easily doing a transparent IMAP+POP3 migration to Dovecot: http://wiki2.dovecot.org/Migration/Dsync + doveadm user:

Timo, I'm working with a webmail client that periodically polls unread message counts for a list of folders. It currently does this by doing a LIST or LSUB and then iterating across all of the folders, running a SEARCH ALL UNSEEN, and counting the resulting UID list. Eventually I'd like to see it using RFC5819 LIST-EXTENDED, but that requires a fair bit of work. In the mean time I'm

On 4/4/19 6:47 PM, dovecot-request at dovecot.org wrote: > For a typical Solr index, 60 seconds is an eternity. Most people aim > for query times of 100 milliseconds or less, and they often achieve > that goal. I'm pretty sure I get these while indexing, not querying. Apr 04 16:44:50 host dovecot[114690]: indexer-worker(me at example.com): Error: fts_solr: Indexing failed: Request

Hi, What's the recommended way to handling timeouts on large mailboxes given the hardwired request timeout of 60s in solr-connection.c: http_set.request_timeout_msecs = 60*1000; /Peter

I am executing this command below to dovecot-2.3.5-6.cp1178.x86_64 server Notice that some status responses are missing (For folders INBOX.Archive, INBOX.spam.&-BD0EOQQ9BDkEPQ-). I wonder If this is a bug or working as expected In rfc5819 there is this: If the server runs into unexpected problems while trying to look up the STATUS information, it MAY drop the corresponding STATUS reply. In

With the latest hg version / upcoming v2.1.4 you can do a perfect migration to Maildir using imapc/pop3c backends: http://wiki2.dovecot.org/Migration/Dsync The main new feature here is the pop3-migration plugin that matches messages from IMAP and POP3 servers together, so that when dsync needs to request POP3 UIDL for some IMAP message it's actually looked up from the POP3 server.

Hi, I was wondering... If one had mdbox ALT path set to a shared storage mount (say, on NFS) and one wanted to move a mailbox to a different host... I guess it in principle wouldn't be necessary to copy all the ALT storage through dsync, when the volume could just be mounted on the new host. Is there anyway for dsync to avoid moving Gigabytes of data for could just be "moved" by

*Christian Felsing wrote: * > Please consider to add server side private/public key encryption for incoming mails. > If client logs on, the password is used to unlock users server side private key. > If mail arrives from MTA or any other source, mail is encrypted with users public key. > Key pair should be located in LDAP or SQL server. PGP and S/MIME should be supported. >

Hi, For the upcoming 2.3 development, I'd like to re-suggest this: It seems the use of login_trusted_networks is overloaded. Example: * It's used for indicating which hosts you trust to provide XCLIENT remote IP's. (like a proxy) * It's used for indicating from which hosts you trust logins enough to disable auth penalty. (like in a webmail) Often these two uses cases have a

Hi there, RFC 5258 (IMAP4 LIST command extensions) defines a ?RECURSIVEMATCH? selection option which ?forces the server to return information about parent mailboxes that don't match other selection options, but have some submailboxes that do.? (Section 3.5 makes the requirement even clearer.) However that's not what Dovecot 2.3.7 does. AFAICT no LIST response is returned for mailboxes

There is no error in the server logs. I checked those particular folders on the server and they don?t seems to have anything special about them, like permission or etc. Yes, calling STATUS on those particular folders returns the status. The folders can be opened and they have emails in them so nothing special about those folders. # 2.3.5 (513208660): /etc/dovecot/dovecot.conf # OS: Linux

Hi All, I'm trying to configure Dovecot 2.0.9 to support Outlook 2013. As I understand it, I need to configure XLIST. I have added imap_capability = +XLIST to 20-imap.conf When I try to query the IMAP folders I get an error "An IMAP command Failed". Looking at the logs I get XLIST Command not found. I can only assume that I'm missing something in the