similar to: v2.2.30.1

On 06/05/2017 11:05 AM, Angel L. Mateo wrote: > I have updated my dovecot proxy servers from 2.2.28 to 2.2.30. Since the upgrade I'm having the error: > > Jun 5 10:54:51 musio12 dovecot: auth: Fatal: master: service(auth): child 63632 killed with signal 11 (core not dumped) > > Me too, with # 2.2.30.1 (eebd877): /opt/dovecot/etc/dovecot/dovecot.conf # Pigeonhole

On 06.06.2017 14:11, Olaf Hopp wrote: > On 06/05/2017 11:05 AM, Angel L. Mateo wrote: >> I have updated my dovecot proxy servers from 2.2.28 to 2.2.30. >> Since the upgrade I'm having the error: >> >> Jun 5 10:54:51 musio12 dovecot: auth: Fatal: master: service(auth): >> child 63632 killed with signal 11 (core not dumped) >> >> > > >

I have updated my dovecot proxy servers from 2.2.28 to 2.2.30. Since the upgrade I'm having the error: Jun 5 10:54:51 musio12 dovecot: auth: Fatal: master: service(auth): child 63632 killed with signal 11 (core not dumped) -- Angel L. Mateo Mart?nez Secci?n de Telem?tica ?rea de Tecnolog?as de la Informaci?n y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150

Hello, I'm having a problem with LMTP in a proxy server since I upgraded from 2.1.16 to 2.2.28. In my logs I have: Apr 26 12:54:17 musio12 dovecot: lmtp(2082): Fatal: master: service(lmtp): child 2082 killed with signal 11 (core dumped). As far as I could check the message is delivered in a later connection. I have enabled core dumped files, but how could I debug it? -- Angel L.

https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig Due to some release process changes I didn't notice that one important bugfix wasn't included in the v2.2.30 release branch before I made the release. So fixing it here with v2.2.30.1. Also included another less important fix. - quota_warning scripts weren't

https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig Due to some release process changes I didn't notice that one important bugfix wasn't included in the v2.2.30 release branch before I made the release. So fixing it here with v2.2.30.1. Also included another less important fix. - quota_warning scripts weren't

> > We have identified a bug in auth process, and are working with a fix. > It works for me in 2.2.30-2 -- Angel L. Mateo Mart?nez Secci?n de Telem?tica ?rea de Tecnolog?as de la Informaci?n y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

Am 31.05.2017 um 15:24 schrieb Timo Sirainen: > https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz > https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig > > Due to some release process changes I didn't notice that one important bugfix wasn't included in the v2.2.30 release branch before I made the release. So fixing it here with v2.2.30.1. Also included another

On 31 May 2017, at 16.53, Reindl Harald <h.reindl at thelounge.net> wrote: > > LTO build is as broken as 2.2.30 > > libtool: link: ( cd ".libs" && rm -f "lib10_quota_plugin.la" && ln -s "../lib10_quota_plugin.la" "lib10_quota_plugin.la" ) > /tmp/ccGO7JSw.ltrans4.ltrans.o:<artificial>:function

> On April 26, 2017 at 2:03 PM "Angel L. Mateo" <amateo at um.es> wrote: > > > Hello, > > I'm having a problem with LMTP in a proxy server since I upgraded from > 2.1.16 to 2.2.28. > > In my logs I have: > > Apr 26 12:54:17 musio12 dovecot: lmtp(2082): Fatal: master: > service(lmtp): child 2082 killed with signal 11 (core dumped).

Olaf Hopp <Olaf.Hopp at kit.edu> wrote: > And I have a new one just for "unknown user" and here my bantime and findtime > are much bigger and the retries are just '2'. So here I'm much harsher. > I'll keep an eye on my logs and maybe some more twaeking is necessary. Just be careful about typos (like twaeking!): users could simply misspell their username,

Am 31.05.2017 um 16:35 schrieb Timo Sirainen: > On 31 May 2017, at 16.53, Reindl Harald <h.reindl at thelounge.net > <mailto:h.reindl at thelounge.net>> wrote: >> >> LTO build is as broken as 2.2.30 >> >> libtool: link: ( cd ".libs" && rm -f "lib10_quota_plugin.la" && ln -s >> "../lib10_quota_plugin.la"

On 2017-05-31 15:24, Timo Sirainen wrote: > https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz > https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig > > Due to some release process changes I didn't notice that one important > bugfix wasn't included in the v2.2.30 release branch before I made the > release. So fixing it here with v2.2.30.1. Also included

Built on CentOS 7 without a hitch. On 5/31/2017 7:24 AM, Timo Sirainen wrote: > https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz > https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig > > Due to some release process changes I didn't notice that one important bugfix wasn't included in the v2.2.30 release branch before I made the release. So fixing it here with

On 31 May 2017, at 18.03, Reindl Harald <h.reindl at thelounge.net> wrote: > >>> libtool: link: ( cd ".libs" && rm -f "lib10_quota_plugin.la" && ln -s "../lib10_quota_plugin.la" "lib10_quota_plugin.la" ) >>> /tmp/ccGO7JSw.ltrans4.ltrans.o:<artificial>:function imapc_quota_refresh.lto_priv.22: error: undefined

Olaf Hopp <Olaf.Hopp at kit.edu> writes: > I have dovecot shielded by fail2ban which works fine. But since a few > days I see many many IPs per day knocking on my doors with wron > password and/or users. But the rate at which they are knocking is very > very low. So fail2ban will never catch them. Slow roll distributed attacks. Really hard to stop. > And I see many many

OK, I found a solution: trusted_users = exim:dovecot in my exim.conf fixed it. Anyway this is an important change of behavour between 2.2 und 2.3 In 2.2 the "dovecot" under exims "trusted_users" was not necessary. Olaf On 04/20/2018 02:53 PM, Olaf Hopp wrote: > On 04/20/2018 02:01 PM, Olaf Hopp wrote: >> Hi (Stephan?), >> is it a new feature of dovecot 2.3

Hi Aki, On 4/4/20 8:12 PM, Aki Tuomi wrote: > Can you provide doveconf -n and try turning on mail_debug=yes on both ends and try doveadm -Dv expunge .... mail_debug=yes is on on both ends and dovecot was restarted but anyway nothing is logged when I issue "doveadm -Dv expunge " In the shell where I issue the "expunge" I see the following: # /usr/bin/doveadm -Dv expunge

On 04/23/2018 03:46 PM, Olaf Hopp wrote: > On 04/23/2018 03:22 PM, Stephan Bosch wrote: >> >> >> Op 20-4-2018 om 14:01 schreef Olaf Hopp: >>> Hi (Stephan?), >>> is it a new feature of dovecot 2.3 /pigeonhole 0.5 that a sieve "redirect" changes the envelope sender of >>> a redirected mail or simply a bug ? >>> >>> A sends

On 05/09/2018 11:10 AM, Stephan Bosch wrote: > > > Op 09/05/2018 om 10:17 schreef Ralf Hildebrandt: >> * Stephan Bosch <stephan at rename-it.nl>: >>> >>> Op 08/05/2018 om 10:34 schreef Olaf Hopp: >>>> Hi, >>>> >>>> I had an email with 58 recipients in the "To" and 13 in the "CC" >>>>