similar to: v2.2.13.rc1 released

http://dovecot.org/releases/2.2/dovecot-2.2.13.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.13.tar.gz.sig A few minor changes since v2.2.13.rc1, mainly making the Pigeonhole tests pass. * Fixed a DoS attack against imap/pop3-login processes. If SSL/TLS handshake was started but wasn't finished, the login process attempted to eventually forcibly disconnect the client, but failed

http://dovecot.org/releases/2.2/dovecot-2.2.13.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.13.tar.gz.sig A few minor changes since v2.2.13.rc1, mainly making the Pigeonhole tests pass. * Fixed a DoS attack against imap/pop3-login processes. If SSL/TLS handshake was started but wasn't finished, the login process attempted to eventually forcibly disconnect the client, but failed

Server: Ubuntu 10.04 LTS 32bit There seems to be an incompatibility when compiling Pigeonhole against Dovecot v2.2.13.rc1. # make check with Pigeonhole throws up the following error message: <snip> Test case: ./tests/extensions/editheader/addheader.svtest: 1: Test 'Addheader - first' SUCCEEDED 2: Test 'Addheader - last' SUCCEEDED 3: Test 'Addheader - framed'

Hi, just saw, that v2.2.13 is still the latest version in wheezy backports. I don't really like the idea of messing around with self compiled versions, at least not, if my original problem might as well have a good possibility not to be resolved by the update. I can't find anything regarding the " file fts-search-serialize.c: line 63 (fts_search_deserialize_add_idx): assertion

Am 28.03.2015 um 10:42 schrieb zucca at systemschmiede.com: > Hi everyone, > > may i jolt this again please...still found no solution at all to this > really. > Thank you very much, i appreciate your help! > Cheers > Sascha a good idea might be upgrade to recent, before do more debug Timo Sirainen <tss at iki.fi> [Thu, 12 Mar 2015 17:41:05 +0200] rev 18340 Released

Hello again dovecot list ;) I've recently upgraded my dovecot version from 2.1.7 to 2.2.13. both versions where installed from source. I upgraded why attempting to get lmtp working. I ultimately just coped the executable lmtp to the location that dovecot was expecting it to be in. but then the above error appeared. However when I get the info from dovecot I get the following... $ dovecot

Dear all, we have succesfully configured Dovecot v2.2.13 in debian wheezy 7.8 (using backports) using Maildir structure, to use private index files for the \Seen flag on a per user basis. All users access their emails and Public Folders using IMAP protocol. The problem is that when a user moves an email from publicFolderA to publicFolderB under the same namespace the other users see this

Hi, yesterday I upgraded to version 2.2.13 under Debian Squeeze. Since today morning sometimes my logfile shows the folling error: .. Jun 24 10:14:16 mailstore dovecot: imap(user at domain.net pid:23434 session:<jf6yi5D8TADD/vzh>): Fatal: master: service(imap): child 23434 killed with signal 11 (core dumped) ... The kernel error log shows: ... Jun 24 10:14:16 mailstore kernel:

Hi List, i have tried to get fts / solr running with virtual all folder with Open-Xchange. I followed a pretty well written howto from Open-Xchanges Intranet, and i first thought everything was running smooth, as the first one or two searches were successful. However now whenever i try to search again for something in the virtual "all folders" Open-Xchange tells me: *Error*

Dear All? When the user login P0P3 more than 10 times in 1 minute that the dovecot temporary suspension all of pop3 login about 5 minutes. How to disable the setting for dovecot. Mail Log: Apr 24 16:11:14 mww dovecot: pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8767, session=<5USPZMX3/QDAqBBU> Apr 24 16:11:14 mww dovecot:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 7 Aug 2014, Ben Johnson wrote: > On 8/7/2014 11:14 AM, Steffen Kaiser wrote: >> one idea: http://www.tldp.org/LDP/abs/html/exitcodes.html >> >> exit code 134 would be in bash's meaning (if this website is >> correct all) some program died off signal 6. This would be Abort in >> Linux. >> >>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 7 Aug 2014, Ben Johnson wrote: > On 7/29/2014 11:20 AM, Ben Johnson wrote: >> On 7/29/2014 3:13 AM, Steffen Kaiser wrote: >>> On Mon, 28 Jul 2014, Ben Johnson wrote: >>> >>>> I have some debugging output in my pipe script; the output looks >>> >>> How does your script looks like?

Hello, I'm using the Debian builds of dovecot-2.2 by S[r]us. Today I started getting the following panic: log: Panic: file priorityq.c: line 122 (priorityq_remove_idx): assertion failed: (idx < count) log: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x7f1ae) [0x7fd368dc31ae] -> /usr/lib/dovecot/libdovecot.so.0(+0x7f269) [0x7fd368dc3269] ->

Hi, Dec 5 20:24:31 dovecot: imap(xx at yy.zz,7ckWZu1CuZFVTILa): Fatal: master: service(imap): child 7292 killed with signal 6 (core dumped) Dec 5 20:24:32 dovecot: imap(xx at yy.zz,LnAlZu1COBVVTILa): Panic: file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) Dec 5 20:24:32 dovecot: imap(xx at yy.zz,LnAlZu1COBVVTILa): Error: Raw backtrace:

With Dovecot-2.2.22 and enabled virtual plugin I get following error messages: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x819f0) [0x7f12330bf9f0] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x81adc) [0x7f12330bfadc] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f123306833d] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(virtual_backend_box_close+0x178)

Control: tags -1 + moreinfo upstream [Forwarding this to the Dovecot mailing list, just in case someone can help] Hi, Thanks for the report! See my comments inline. On 11:56 Thu 21 Sep , Thurgood Angelou wrote: > Package: dovecot-core > Version: 1:2.2.32-2 > > I've just discovered a bug where the sieve plugin (especially IMAP) > will not work with a virtual mailbox. I

I am getting some panics after upgrading from 2.2.13 to 2.2.14 This panic happens for one user only, he is subscribed to 86 folders, on two of them this panic happens quite often - several times a day. The mbox folders seems OK, less than 30M with 30 and 200 messages. Panic: file mail-index-sync-update.c: line 250 (sync_expunge_range): assertion failed: (count > 0) hmk GNU gdb 6.8

We are happy to announce 2.3.17.1 patch release of Dovecot. This contains some fixes for issues found after 2.3.17 release. https://dovecot.org/releases/2.3/dovecot-2.3.17.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.17.1.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy -- - dsync: Add back

We are happy to announce 2.3.17.1 patch release of Dovecot. This contains some fixes for issues found after 2.3.17 release. https://dovecot.org/releases/2.3/dovecot-2.3.17.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.17.1.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy -- - dsync: Add back

http://dovecot.org/releases/2.2/rc/dovecot-2.2.14.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.14.rc1.tar.gz.sig I've wanted to do this release for months now, but I keep being too busy all the time. This release fixes several important bugs and a lot of smaller ones. Because there are such a large number of changes I thought I'd make this release candidate release first and