lda / postfix / dovecot -- bounced messages not working

I saw another thread about this topic, but I did not understand the solution. . . I recently discovered my bounced messages were not getting delivered. Obviously since I was not getting any messages, I thought everything was fine. Anyway, my maillog has entries similar to below for bounced

Re: 2.3.1 from ghettoforge-testing causes auth failures

On March 28, 2018 8:23:42 PM EDT, "Fabian A. Santiago" wrote: >Hello, > >I updated today to v2.3.1 from @gf-testing and it broke my imap auth >mechanism. My dovecot-imap.log reported: > >Temporary auth service failure > >I needed it back up so I downgraded

Frequentl failures to create /tmp/dovecot.imap

I am using dovecot 2.2.27 with plesk 12 and I have made no modifications to the dovecot config. my log file frequently (but not always!) reports errors that /tmp/dovecot.imap could not be created. The errors don't appear for every imap connect but for about 5% to 10% of the time. I already

Re: Release 2.3.1

Op 3/29/2018 om 12:58 PM schreef Odhiambo Washington: > > > On 29 March 2018 at 13:26, Aki Tuomi > wrote: > > > > On 29.03.2018 13:14, Odhiambo Washington wrote: >> >> >> On 29 March 2018 at 13:04, Aki Tuomi >

Re: Release 2.3.1

On 29 March 2018 at 13:26, Aki Tuomi wrote: > > > On 29.03.2018 13:14, Odhiambo Washington wrote: > > > > On 29 March 2018 at 13:04, Aki Tuomi wrote: > >> >> >> On 29.03.2018 10:36, Odhiambo Washington wrote: >> >> >> >> On 29 March 2018 at 09:43, Aki

Re: Release 2.3.1

On 29.03.2018 13:14, Odhiambo Washington wrote: > > > On 29 March 2018 at 13:04, Aki Tuomi > wrote: > > > > On 29.03.2018 10:36, Odhiambo Washington wrote: >> >> >> On 29 March 2018 at 09:43, Aki Tuomi >

Re: Release 2.3.1

On 29 March 2018 at 13:04, Aki Tuomi wrote: > > > On 29.03.2018 10:36, Odhiambo Washington wrote: > > > > On 29 March 2018 at 09:43, Aki Tuomi wrote: > >> >> >> On 28.03.2018 22:14, Odhiambo Washington wrote: >> >> >> >> On 27 March 2018 at 20:06,

Re: Release 2.3.1

On 29.03.2018 10:36, Odhiambo Washington wrote: > > > On 29 March 2018 at 09:43, Aki Tuomi > wrote: > > > > On 28.03.2018 22:14, Odhiambo Washington wrote: >> >> >> On 27 March 2018 at 20:06, >

Re: Release 2.3.1

On 29 March 2018 at 09:43, Aki Tuomi wrote: > > > On 28.03.2018 22:14, Odhiambo Washington wrote: > > > > On 27 March 2018 at 20:06, wrote: > >> Hi! >> >> We are releasing v2.3.1, which mostly consists of bug fixes for 2.3.0, >> and few improvements.

Re: murmurhash3 test failures on big-endian systems

On 15:55 Wed 28 Mar , Josef 'Jeff' Sipek wrote: > Ok, there are two commits: > > 35497604d80090a02619024aeec069b32568e4b4 and > 5522b8b3d3ed1a99c3b63bb120216af0bd427403 > > Together, they should be identical to the patch I sent the other day plus > your fixup. Let me know if you have any

Re: [sieve][pigeonhole] Can't catch stdout for pipe script after upgrade Dovecot 2.2 -> 2.3

On 03/28/2018 03:08 PM, Stephan Bosch wrote: The most common cause would be that systemd is configured with PrivateTmp for the Dovecot service, which means that the created log files are not visible from another (shell) process. Try another location outside /tmp. You 100% right, I was override

Re: Release 2.3.1

On 28.03.2018 22:14, Odhiambo Washington wrote: > > > On 27 March 2018 at 20:06, > wrote: > > Hi! > > We are releasing v2.3.1, which mostly consists of bug fixes for > 2.3.0, and few improvements. This is also available via >

Re: Dovecot 2.3 panic

Hi! Can you install debugging symbols and try get core? A backtrace would help a lot! https://dovecot.org/bugreport.html Aki On 29.03.2018 00:50, Martynas Bendorius wrote: > Dovecot version: 2.3.1 (happens with 2.3.x too) > OS: CentOS 7 64-bit > > Mar 28 16:29:24 lmtp(30383): Panic: file