similar to: Auto expunge log

Hi, today we have exceprienced really major difficulties with our proxy backend servers. Everything started after enabling auth cache: auth_cache_size = 100M auth_cache_verify_password_with_worker = yes auth_cache_ttl = 1 hour auth_cache_negative_ttl = 1 hour Soon after we start receiving lots of calls from our customers about 'missing all e-mail messages'. This was in errors logs on

2.2.36 (not migrated to 2.3 yet) reports such problem: > Nov 13 15:50:58 mbox dovecot: lmtp(xxx): session=<ACYRCtLk6ltiEQAALZVUYQ>, Error: open(/var/mail/xxx/mailboxes.lock1bf6ad16b7b8b703) failed: Disk quota exceeded > Nov 13 15:50:58 mbox dovecot: lmtp(xxx): session=<ACYRCtLk6ltiEQAALZVUYQ>, Error: Couldn't create mailbox list lock /var/mail/xxx/mailboxes.lock:

There seems to be a problem with new user directories and the imapc backend. On a test setup I get the following error in the log: May 02 10:09:58 imap(user1 at domain.com): Error: Couldn't create mailbox list lock /tmp/tmp0Y5TMn/dovecot1/users/user1 at domain.com/imapc/mailboxes.lock: file_create_locked(/tmp/tmp0Y5TMn/dovecot1/users/user1 at domain.com/imapc/mailboxes.lock) failed:

> On 13 November 2018 at 22:06 Arkadiusz Mi?kiewicz <arekm at maven.pl> wrote: > > > On 13/11/2018 15:54, Arkadiusz Mi?kiewicz wrote: > > > > 2.2.36 (not migrated to 2.3 yet) reports such problem: > > > >> Nov 13 15:50:58 mbox dovecot: lmtp(xxx): session=<ACYRCtLk6ltiEQAALZVUYQ>, Error: open(/var/mail/xxx/mailboxes.lock1bf6ad16b7b8b703)

> On 13 Nov 2018, at 21.06, Arkadiusz Mi?kiewicz <arekm at maven.pl> wrote: > > On 13/11/2018 15:54, Arkadiusz Mi?kiewicz wrote: >> >> 2.2.36 (not migrated to 2.3 yet) reports such problem: >> >>> Nov 13 15:50:58 mbox dovecot: lmtp(xxx): session=<ACYRCtLk6ltiEQAALZVUYQ>, Error: open(/var/mail/xxx/mailboxes.lock1bf6ad16b7b8b703) failed: Disk quota

1) my inbox is "Posteingang". should I officially declare it somewhere? I now get the following error messages: Jun 14 00:23:32 ulmke2 dovecot[3981]: imap(ulw)<3997><4O/Xbo1uotLAqGQd>: Error: opendir(/u/ulw/Mail) failed: Permission denied (euid=503(ulw) egid=100(users) UNIX perms appear ok (ACL/MAC wrong?)) Jun 14 00:23:32 ulmke2 dovecot[3981]:

Hi, please post your doveconf -n Sami > On 16 Apr 2018, at 20.17, azurit at pobox.sk wrote: > > Hi, > > today we have exceprienced really major difficulties with our proxy backend servers. Everything started after enabling auth cache: > auth_cache_size = 100M > auth_cache_verify_password_with_worker = yes > auth_cache_ttl = 1 hour > auth_cache_negative_ttl = 1 hour

Hello, Autoexpunge is not working when used with dotlock locking. It seems to been broken since version 2.2.28. When autoexpunge is enabled and mailbox locking is set to dotlock all imap, pop and lmtp connections crash with the same error "file file-lock.c: line 287: unreached". Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SASL-IR

I'm seeing these recently: Feb 27 09:24:01 nihlus dovecot: imap(tlx at leuxner.net): Error: istream-seekable: safe_mkstemp(/tmp/dovecot.imap.) failed: No such file or directory Feb 27 09:24:01 nihlus dovecot: imap(tlx at leuxner.net): Error: istream-seekable: safe_mkstemp(/tmp/dovecot.imap.) failed: No such file or directory Feb 27 09:24:01 nihlus dovecot: imap(tlx at leuxner.net): Error:

On 02/05/16 16:51, Timo Sirainen wrote: > On 02 May 2016, at 03:47, Leon Kyneur <leon at f-m.fm> wrote: >> Was excited to see that wildcards are now possible on autoexpunge in the 2.2.24 release. >> >> However I'm trying to configure these from the userdb lookup and it doesn't appear to be working. >> >> if I set in 15-mailboxes.conf >> mailbox

When using autoexpunge = 14 days in, for example. The trash of junk folders, does that physically remove the messages from disk or simply mark them to be removed and some other action needs to be taken? I ask because my mail server crapped out today and I discovered a Junk folder with 490,000 messages in it, and the sa-spamd and mariadb processes died a horrible death. Haven't had time to

> On Feb 7, 2016, at 10:59 AM, Timo Sirainen <tss at iki.fi> wrote: >> On 07 Feb 2016, at 04:50, Tom Johnson <tj at terramar.net> wrote: >> >> I have some users where I'd like to expunge their mail at different times. >> .... >> .... >> Is there a way to do some sort of lookup for this? Or is this beyond the ability of the autoexpunge

I get: May 18 14:56:16 exodia dovecot: master: Dovecot v2.0.beta5 (4ba05c3702be) starting up (core dumps disabled) May 18 14:56:16 exodia dovecot: master: Error: service(pop3-login): safe_mkstemp(/tmp/dovecot-master) failed: Permission denied May 18 14:56:16 exodia dovecot: master: Error: service(imap-login): safe_mkstemp(/tmp/dovecot-master) failed: Permission denied "nc localhost

Hello list, After many hours I still fail to configure properly dovecot as the LDA with opensmtpd, for system users only. I don't want pop at all, jus lmtp and imap, but still haven't stripped it. Here is the info, thanks in advance for your response: ===== # doveconf -n # 2.2.14: /etc/dovecot/dovecot.conf # OS: OpenBSD 5.6 i386 auth_verbose = yes auth_verbose_passwords = yes

Hi to all of you, as I am struggling around with this a week or so I'm afraid I have to ask for help here. The problem is sitting right in front of the computer, as most of the time. ;-) So let me explain: Dovecot is working properly for IMAP with LE certificates, so I thought it's time to continue with Christoph Haas tutorial primarily and other blogs and tutorials for setting up the

There's a bug in "folder delete" for lazy expunge, type "1 namespace", as descibed on https://wiki2.dovecot.org/Plugins/Lazyexpunge When trying to delete a mailbox that still has messages in it, but that has no EXPUNGED/<name> counterpart, the process hangs after the imap "DELETE" command, and the following appears in the log file after a 60s timeout: Jun

Thanks, that fixes it for me. ? John ? From: dovecot [mailto:dovecot-bounces at dovecot.org] On Behalf Of Timo Sirainen Sent: Thursday, 3 May, 2018 13:52 To: John van der Kamp <jkamp at amazon.nl> Cc: Dovecot Mailing List <dovecot at dovecot.org> Subject: Re: v2.2.36 release candidate released ? On 2 May 2018, at 12.52, John van der Kamp <jkamp at amazon.nl <mailto:jkamp at

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 14 Jun 2018, Walter Ulmke wrote: > 1) my inbox is "Posteingang". should I officially declare it somewhere? > > I now get the following error messages: > > Jun 14 00:23:32 ulmke2 dovecot[3981]: imap(ulw)<3997><4O/Xbo1uotLAqGQd>: > Error: opendir(/u/ulw/Mail) failed: Permission denied (euid=503(ulw)

On 13/11/2018 15:54, Arkadiusz Mi?kiewicz wrote: > > 2.2.36 (not migrated to 2.3 yet) reports such problem: > >> Nov 13 15:50:58 mbox dovecot: lmtp(xxx): session=<ACYRCtLk6ltiEQAALZVUYQ>, Error: open(/var/mail/xxx/mailboxes.lock1bf6ad16b7b8b703) failed: Disk quota exceeded >> Nov 13 15:50:58 mbox dovecot: lmtp(xxx): session=<ACYRCtLk6ltiEQAALZVUYQ>, Error:

Hey all, almost 48h ago I upgraded both my instances to 2.3.1 again to see if the new patches would fix the replication issues for me. So far, the result is: great. I haven't been able to provoke any kind of I/O stall or persisting queued/failed resync requests in my replication setup. Newly added users are replicated instantly upon the first received mails and the home directory gets