similar to: imap ---- LIST "" * The returned mailbox does not display quotes

Displaying 20 results from an estimated 500 matches similar to: "imap ---- LIST "" * The returned mailbox does not display quotes"

2019 Mar 21
3
imap ---- LIST "" * The returned mailbox does not display quotes
Yes, Foxmail for mac client, after dovecot upgrade from 2.1.17 to new version, imap can't receive any email, I perform packet capture test, foxmail will not have next step after sending {LIST "" *} command action. Foxmail for mac client, dovecot version 2.1.17 can receive imap mail normally, because we need to add quota_max_mail_size configuration, we must upgrade to a higher
2019 Mar 19
3
Upgrade from 2.1.17 2.2.36
I use the MAC Foxmail client, v2.2.36 can't receive mail, but v2.1.17 can receive mail. I grabbed the network package and found that Foxmail was not processing the next step after sending the D LIST "" * command. I suspect that because of the time of return, Foxmail is not recognized, so I want to remove this time. ? 2019-03-18 18:03?Aki Tuomi ??? > On 18.3.2019 12.00, lty via
2017 Apr 19
3
help
Dear Team I have faced issue with email downloading in the email client by using pop3 SSL port 995 in dovecot v2.1.17 for outlook client 2016 on production environment. As per my troubleshooting on my test environment, I have upgraded dovecot version v2.2.28, and changed paramer "ssl_dh_parameters_length = 2048" and "verbose_ssl = yes", The issue seems to be resolved in
2017 Apr 21
2
Issue with POP3s TLS/SSL on port 995 on Outlook 2016
Dear Team, I'm facing issue with POP3s TLS/SSL on port 995 only for outlook2016. It's working fine with dovecot v2.2.28 on test environment. Is the dovecot v2.2.28 is stable released? I can? upgrade the version from v2.1.17 to v2.2.28 on production if its stable version. Kindly confirm and provide the proper solution. Thanks and Regards, Bhushan Previous Mail:==========I have faced
2019 Mar 19
0
Upgrade from 2.1.17 2.2.36
Thank you for your reply But I tested it in dovecot v2.1.17, imap can receive mail normally. I want to ask if the returned data can be removed after the [ LIST "" * ] command? Or can you remove some parameters? I also observed that v2.1.17 and v2.2.36 are different. After the [ LIST "" * ] command, The v2.1.17 directory has quotes. The v2.2.36 directory has no quotes. [*
2019 Mar 05
2
Dovecot v2.3.5 released
Hi! We are happy to release dovecot v2.3.5. Please find sources at https://dovecot.org/releases/2.3/dovecot-2.3.5.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.5.tar.gz.sig You can find precompiled binaries at https://repo.dovecot.org/ NEWS: + Lua push notification driver: mail keywords and flags are provided in MessageNew and MessageAppend events. + submission: Implement support for
2019 Mar 05
2
Dovecot v2.3.5 released
Hi! We are happy to release dovecot v2.3.5. Please find sources at https://dovecot.org/releases/2.3/dovecot-2.3.5.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.5.tar.gz.sig You can find precompiled binaries at https://repo.dovecot.org/ NEWS: + Lua push notification driver: mail keywords and flags are provided in MessageNew and MessageAppend events. + submission: Implement support for
2019 Apr 02
3
FTS delays
On 2 Apr 2019, at 6.38, Joan Moreau via dovecot <dovecot at dovecot.org> wrote: > > Further on this topic: > > > > When choosing any headers in the search box, dovecot core calls the plugin TWICE (and returns the results quickly, but not immediatly after getting the IDs from the plugins) > > When choosing the BODY search, dovecot core calls the plugin ONCE (and
2014 May 11
2
questions about process_limit
Hello all! # dovecot --version 2.1.17 Sometimes I have this in the logfile: May 11 16:55:52 master: Warning: service(imap-login): process_limit (100) reached, client connections are being dropped May 11 17:35:03 master: Warning: service(imap-login): process_limit (100) reached, client connections are being dropped May 11 17:36:27 master: Warning: service(imap-login): process_limit (100)
2017 Apr 19
0
help
> What can i do to resolve this issue in dovecot v2.1.17 in Production environment? Kindly help Why don't you upgrade production and modify the settings as you did in test? Matt Pallissard On Wed, 2017-04-19 at 13:20 +0000, Bhushan Bhosale wrote: > Dear Team > > I have faced issue with email downloading in the email client by using pop3 SSL port 995 in dovecot v2.1.17 for
2017 Apr 24
0
Issue with POP3s TLS/SSL on port 995 on Outlook 2016
On 21.04.2017 12:29, Bhushan Bhosale wrote: > Dear Team, > > I'm facing issue with POP3s TLS/SSL on port 995 only for outlook2016. It's working fine with dovecot v2.2.28 on test environment. > Is the dovecot v2.2.28 is stable released? I can upgrade the version from v2.1.17 to v2.2.28 on production if its stable version. > Kindly confirm and provide the proper solution.
2010 Feb 25
0
How to use connection pool in Rails2.3.5 with WEBrick and MySQL?
We use Rails 2.3.5, MySQL, and WEBrick. ActiveRecord call ConnectionPool#checkout and create new connection to MySQL when receive a first HTTP request. At this time, register to connection pool its connection in ConnectionPool#checkout_new_connection. # http://github.com/rails/rails/blob/v2.3.5/activerecord/lib/active_record/connection_adapters/abstract/connection_pool.rb#L181 #
2017 Apr 07
2
[Dovecot-news] v2.2.29.rc1 released
On 7 Apr 2017, at 2.25, Daniel J. Luke <dluke at geeklair.net> wrote: > > On Apr 6, 2017, at 1:33 PM, Timo Sirainen <tss at iki.fi> wrote: >> Planning to release v2.2.29 on Monday. Please find and report any bugs before that. > > I'm seeing still seeing the assert that started showing up for me with 2.2.28
2017 Apr 10
4
Vpopmail Error
I'm trying to compile the latest Dovecot (v2.2.29) and when I run make I get this error: > auth-userdb-vpopmail.o: In function `userdb_vpopmail_get_quota': > /usr/local/src/dovecot-2.2.29/src/auth/userdb-vpopmail.c:64: undefined > reference to `var_expand_table_build' > collect2: error: ld returned 1 exit status > Makefile:932: recipe for target 'auth' failed
2017 Apr 06
2
v2.2.29.rc1 released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.29.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.29.rc1.tar.gz.sig Planning to release v2.2.29 on Monday. Please find and report any bugs before that. * When Dovecot encounters an internal error, it logs the real error and usually logs another line saying what function failed. Previously the second log line's error message was
2017 Apr 06
2
v2.2.29.rc1 released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.29.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.29.rc1.tar.gz.sig Planning to release v2.2.29 on Monday. Please find and report any bugs before that. * When Dovecot encounters an internal error, it logs the real error and usually logs another line saying what function failed. Previously the second log line's error message was
2017 Feb 25
3
v2.2.28: patches (to use libressl 2.4.5) and test error (strftime)
t_strftime and variants now .......................................... : ok test-time-util.c:123: Assert failed: strcmp(t_strftime(RFC2822_FMT, gmtime(&ts)), exp) == 0 test-time-util.c:124: Assert failed: strcmp(t_strfgmtime(RFC2822_FMT, ts), exp) == 0 t_strftime and variants fixed timestamp .............................. : FAILED timings 0
2019 Mar 07
0
Dovecot v2.3.5 released
Am 05.03.19 um 17:26 schrieb Aki Tuomi via dovecot: > We are happy to release dovecot v2.3.5. Hello, it build but tests fail... make[4]: Entering directory '/<<PKGBUILDDIR>>/src/lib-http' for bin in test-http-date test-http-url test-http-header-parser test-http-transfer test-http-auth test-http-response-parser test-http-request-parser test-http-payload
2019 Mar 07
2
Dovecot v2.3.5 released
> On 7 March 2019 18:02 A. Schulze via dovecot <dovecot at dovecot.org> wrote: > > > Am 05.03.19 um 17:26 schrieb Aki Tuomi via dovecot: > > We are happy to release dovecot v2.3.5. > > Hello, > > it build but tests fail... > > make[4]: Entering directory '/<<PKGBUILDDIR>>/src/lib-http' > for bin in test-http-date test-http-url
2017 Feb 25
2
v2.2.28: patches (to use libressl 2.4.5) and test error (strftime)
On 25 Feb 2017, at 21.54, Timo Sirainen <tss at iki.fi> wrote: > > Oh, I forgot to remove the #if OPENSSL_VERSION_NUMBER checks from lib-dcrypt. Will be removed in v2.2.29. Attached the planned patch that should do it. Well that didn't work with <v1.1. Maybe this one. -------------- next part -------------- A non-text attachment was scrubbed... Name: openssl.diff Type: