So, along with the problem of lots of folders ending in 1 1 1 1, I'd like
to have a strategy to delete these.
I was trying to understand if it is possible to use
http://linux.die.net/man/1/doveadm-expunge to delete empty folders, but
without also deleting messages? Is this possible and if so what
I just updated to the latest dovecot from 1.2 and it has been working great
for most of my clients. But one client,who is using Outlook, has found that
hundreds of folders have been created, e.g.
admin@domain Deleted Items 1
admin@domain Deleted Items 1 1
admin@domain Deleted Items 1 1 1
admi
On 22 Jan 2015, at 14:01, Lauri Tirkkonen wrote:
>
> Hi, with a low soft limit on file descriptors, dovecot 2.2.15 warns on
> startup:
>
>Warning: fd limit (ulimit -n) is lower than required under max. load
>(256 < 1000), because of default_client_limit
>
> It could try increasing the l
On 05 Mar 2015, at 12:46, Patrick Westenberg wrote:
>
> Hi everyone,
>
> can anybody explain the difference between Dovecots fast sync and full sync
> in replication mode?
There are actually 3 dsync modes, all explained in doveadm-sync man page:
o Full synchronization (-f
On 12 Mar 2015, at 22:55, Laeeth Isharc wrote:
>
> Hi.
>
> I am seeing the following in my logs. Happy to downgrade to an earlier
> version if you think this might be the problem, but dovecot.org is extremely
> slow (and has been for months) so I found it easier just to pull the latest
> fro
On 19 Mar 2015, at 12:25, Steffen Kaiser wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, 19 Mar 2015, Gedalya wrote:
>> On 03/18/2015 08:49 PM, Timo Sirainen wrote:
>>> There's no reason why flow and pager should write headers to stderr because
>>> it would always result
On 20 Mar 2015, at 12:40, Gedalya wrote:
>
> On 05/31/2013 04:21 PM, Timo Sirainen wrote:
>> Originally I was planning on allowing all kinds of mail settings inside
>> namespace {}, including imapc_* settings. But that's a bit difficult to
>> implement (although I think it will happen some day)
On 20 Mar 2015, at 13:59, James wrote:
>
> Connecting to dovecot with ssl3 causes imap-login to die:
>
> Mar 20 11:30:35 MAILHOST dovecot: [ID 583609 mail.crit] imap-login: Fatal:
> master: service(imap-login): child 21918 killed with signal 11 (core dumped)
> [last ip=127.0.0.1]
I can't repr
On 20 Mar 2015, at 10:37, Vu Ngoc VU wrote:
>
> But to answer your questions, I'm not really interested in purging the cache
> data.
> I just think that cache has expiration delay.
> The only point is to get this "doveadm search" answering me in minutes
> instead of hours.
> Writing my original
Connecting to dovecot with ssl3 causes imap-login to die:
$ openssl s_client -connect localhost:993 -ssl3
CONNECTED(0003)
4277630796:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert
handshake failure:s3_pkt.c:1461:SSL alert number 40
4277630796:error:1409E0E5:SSL routines:ssl3_write_
On 19/03/2015 20:59, Pascal Volk wrote:
Try this configuration:
service imap-login {
executable = imap-login -D
}
Many thanks, Pascal. That did it.
Now I have a core I can investigate the real problem - it's openssl that
is failing, ha, maybe the problem will just go away with openssl 1
On 05/31/2013 04:21 PM, Timo Sirainen wrote:
Originally I was planning on allowing all kinds of mail settings inside
namespace {}, including imapc_* settings. But that's a bit difficult to
implement (although I think it will happen some day). So for now I was thinking:
imapc foo {
host = im
Date: Fri, 20 Mar 2015 02:05:48
From: Joseph Tam
To: dovecot@dovecot.org
Subject: Re: fast doveadm search results
Steffen Kaiser writes:
e.g. put message-id into mail_always_cache_fields
- From http://dovecot.org/pipermail/dovecot-cvs/2013-May/023261.html
lib-storage: Allow mail_*cache_field
13 matches
Mail list logo
