On 2019/07/16 19:46, Aki Tuomi wrote:
>
> > On 16/07/2019 18:40 Stuart Henderson via dovecot
> > wrote:
> >
> >
> > On 2019-07-13, Reio Remma via dovecot wrote:
> > > Hello!
> > >
> > > I noticed these in the logs since upgrading from 2.3.6. to 2.3.7:
> > >
> > > Jul 13 11:52:10 turin
On 12 Jul 2019, at 16:15, @lbutlr via dovecot wrote:
> I am looking for something that is similar to replication, but without a
> second server. I currently have a system setup using postfix bcc to write out
> copies of all email, but what I would rather do is just have all the mail
> written
> On 16/07/2019 18:40 Stuart Henderson via dovecot wrote:
>
>
> On 2019-07-13, Reio Remma via dovecot wrote:
> > Hello!
> >
> > I noticed these in the logs since upgrading from 2.3.6. to 2.3.7:
> >
> > Jul 13 11:52:10 turin dovecot: doveadm: Error:
> > dsync-remote(r...@mrstuudio.ee):
On 2019-07-13, Reio Remma via dovecot wrote:
> Hello!
>
> I noticed these in the logs since upgrading from 2.3.6. to 2.3.7:
>
> Jul 13 11:52:10 turin dovecot: doveadm: Error:
> dsync-remote(r...@mrstuudio.ee): Error:
> Exporting mailbox INBOX failed: Mailbox attribute
>
As a workaround (if this turns out to be a Dovecot bug) -
- you could use STATUS instead.
It would be several commands, one per folder, so you'd want to send them
pipelined for performance.
I've done this before in an email app I worked on and haven't seen any issues
with Dovecot or any
Please disregard this. My apologies.
The issue appears to have been caused by an unrelated network issue with
one of the directors, that coincidentally occurred at almost the exact
same time.
A potential improvement would be if the "Ring SYNC seq=XX appears to
have got lost" error message
Downgrading to 2.3.6 did indeed resolve the issue.
Our Directors are running Ubuntu 18.04.
Regards,
Eirik Rye
On 16/07/2019 11:17, Eirik Rye via dovecot wrote:
Version 2.3.7 appears to break director ring sync. After upgrading, our
logs are full of these kinds of messages:
Jul 14 04:09:20
Version 2.3.7 appears to break director ring sync. After upgrading, our
logs are full of these kinds of messages:
Jul 14 04:09:20 yyy dovecot: director: Error: director: User xxx host
lookup failed: Timeout because ring not synced - queued for 30 secs
(Ring not synced for 1410 secs,
On 16 Jul 2019, at 11.41, Emil Kalchev wrote:
>
> There is no error in the server logs. I checked those particular folders on
> the server and they don’t seems to have anything special about them, like
> permission or etc.
>
> Yes, calling STATUS on those particular folders returns the
There is no error in the server logs. I checked those particular folders on the
server and they don’t seems to have anything special about them, like
permission or etc.
Yes, calling STATUS on those particular folders returns the status. The folders
can be opened and they have emails in them so
* Timo Sirainen via dovecot :
> > And alas, I had a look at the monitoring and found that disk IO has
> > increase A LOT after the update:
> > https://www.arschkrebs.de/images/dovecot-disk-io-increase.png
> >
> > I zoomed in and found that the sudden increace in IO coincides with
> > the update
On 16 Jul 2019, at 9.51, Emil Kalchev via dovecot wrote:
>
> I am executing this command below to dovecot-2.3.5-6.cp1178.x86_64 server
>
> Notice that some status responses are missing (For folders INBOX.Archive,
> INBOX.spam.&-BD0EOQQ9BDkEPQ-). I wonder If this is a bug or working as
>
On 13 Jul 2019, at 14.44, Tom Sommer via dovecot wrote:
>
> LMTP is broken on director:
>
> Jul 13 13:42:41 lmtp(34824): Panic: file smtp-params.c: line 685
> (smtp_params_mail_add_body_to_event): assertion failed: ((caps &
> SMTP_CAPABILITY_8BITMIME) != 0)
Thanks, fixed:
Lately I get some errors in my logfile, saying:
dovecot[72337]: auth: Warning: Event 0x1280fe20 leaked (parent=0x0):
auth-client-connection.c:338: 1 Time(s)
Can you tell me what is going wrong here? Thanks.
On 13 Jul 2019, at 18.39, Michael Grimm via dovecot wrote:
>
> Now replication is working from my point of view, besides occational error
> messages like:
>
> | imap-login: Error: file_ostream.net_set_tcp_nodelay(, TRUE) failed:
> Connection reset by peer
Here's the final fix for it:
On 15 Jul 2019, at 23.17, Ralf Hildebrandt via dovecot
wrote:
>
> * Ralf Hildebrandt via dovecot :
>> We're using dovecot (via LMTP) as a backup for all incoming mail.
>>
>> I upgraded from 2.3.6 to 2.3.7 on the 12th:
>> 2019-07-12 14:35:44 upgrade dovecot-imapd:amd64 2:2.3.6-2~bionic
>>
I am executing this command below to dovecot-2.3.5-6.cp1178.x86_64 server
Notice that some status responses are missing (For folders INBOX.Archive,
INBOX.spam.&-BD0EOQQ9BDkEPQ-). I wonder If this is a bug or working as expected
In rfc5819 there is this:
If the server runs into unexpected
17 matches
Mail list logo
