Hi all!
I've decided to rotate the dovecot logs automatically on my freebsd
10.4 server using the system's newsyslog feature. I started with
logfile.info putting the line
/var/log/dovecot/logfile.info 600 31*@T16 ZCU
/var/run/dovecot/master.pid 30
which should send
On Wed Jan 17 2018 15:56:39 GMT-0500 (Eastern Standard Time), Joseph Tam
wrote:
> Thanks. How does this manifests itself: the client gets an inconsistent
> view of the outgoing mailbox that depends on which mailbox the client
> is using, or the optimization is broken and
Op 1/17/2018 om 2:22 PM schreef Marco Giunta:
> Hi,
> I'm using dovecot 2.3.0 installed on a new CentOS 7.4 with rpm from
> Dovecot repo. When I use LMTP to deliver an email to an overquota
> user, lmtp service hangs with a segfault:
>
> Jan 17 13:39:45 server-02.example.com kernel: lmtp[5099]:
On 19 Jan, 2018, at 4:39, Aki Tuomi wrote:
On 19.01.2018 04:35, Adam Weinberger wrote:
Since upgrading to 2.3.0 / 0.5.0.1, incoming PDFs are getting mangled.
It seems to be happening when I use vnd.dovecot.filter. When I comment
out the block, things come through fine.
Aki Tuomi writes:
https://wiki2.dovecot.org/Plugins/MailboxAlias
There is also gotcha that MailboxAlias is not compatible with
mailbox_list_index=yes setting.
Thanks. How does this manifests itself: the client gets an inconsistent
view of the outgoing mailbox that depends on which mailbox
On 19.01.2018 04:35, Adam Weinberger wrote:
> Since upgrading to 2.3.0 / 0.5.0.1, incoming PDFs are getting mangled.
> It seems to be happening when I use vnd.dovecot.filter. When I comment
> out the block, things come through fine.
>
> My filter block looks like this:
>require
Since upgrading to 2.3.0 / 0.5.0.1, incoming PDFs are getting mangled.
It seems to be happening when I use vnd.dovecot.filter. When I comment
out the block, things come through fine.
My filter block looks like this:
require "vnd.dovecot.filter";
filter "bogofilter_filter";
Hello Florent,
How did you proceed with the upgrade? Did you follow the recommended steps
guide to upgrade ceph? (mons first, then OSDs, then MDS)
Did you interrupt dovecot before upgrading the MDS specially? Did you
remount the filesystem? Did you upgrade the ceph client too?
Give people the
On 2018-01-18 08:01, Aki Tuomi wrote:
Hi!
This is fixed with
https://github.com/dovecot/core/commit/2bf919786518d138cc07d9cc21e14ad5e07e5e56.patch
Aki Tuomi
yes, it works.
Thanks,
Marco
--
On 18.01.2018 11:32, Thomas Robers wrote:
> Hi,
>
> after updating Dovecot to version 2.3 I get a lot of core-dumps like:
>
>> Jan 18 10:08:20 mail dovecot:
>> imap(b...@tutech.de)<18200>: Panic: file
>> ostream-zlib.c: line 36 (o_stream_zlib_close): assertion failed:
>>
Hi,
after updating Dovecot to version 2.3 I get a lot of core-dumps like:
Jan 18 10:08:20 mail dovecot: imap(b...@tutech.de)<18200>: Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion failed: (zstream->ostream.finished ||
zstream->ostream.ostream.stream_errno != 0)
Jan 18
On 19.01.2018 11:55, Søren Skou wrote:
> Hiya all,
>
> I'm seeing this "Fatal: nfs flush requires mail_fsync=always" error on
> my testbed. The issue is that from what I can see, mail_fsync is set
> to always :
>
> # doveconf -n | grep mail_fs
> mail_fsync = always
>
> The result is that the
On 17.01.2018 15:23, Aki Tuomi wrote:
>
> On 17.01.2018 15:22, Marco Giunta wrote:
>> Hi,
>> I'm using dovecot 2.3.0 installed on a new CentOS 7.4 with rpm from
>> Dovecot repo. When I use LMTP to deliver an email to an overquota
>> user, lmtp service hangs with a segfault:
>>
>> Jan 17 13:39:45
Hiya all,
I'm seeing this "Fatal: nfs flush requires mail_fsync=always" error on
my testbed. The issue is that from what I can see, mail_fsync is set
to always :
# doveconf -n | grep mail_fs
mail_fsync = always
The result is that the client does not connect at all, which is not
really what I
14 matches
Mail list logo